Sun Microsystems, Inc.  Sun System Handbook - ISO 4.1 October 2012 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-72-1331984.1
Update Date:2011-10-18
Keywords:

Solution Type  Problem Resolution Sure

Solution  1331984.1 :   Sun Storage 7000 Unified Storage System: Unable To ssh Into Sun 7310 after switch reconfigure of VLANs  


Related Items
  • Sun Storage 7410 Unified Storage System
  •  
  • Sun ZFS Storage 7320
  •  
  • Sun Storage 7310 Unified Storage System
  •  
  • Sun Storage 7210 Unified Storage System
  •  
  • Sun Storage 7110 Unified Storage System
  •  
  • Sun ZFS Storage 7120
  •  
  • Sun ZFS Storage 7420
  •  
Related Categories
  • PLA-Support>Sun Systems>DISK>NAS>SN-DK: 7xxx NAS
  •  
  • .Old GCS Categories>Sun Microsystems>Storage - Disk>Unified Storage
  •  




In this Document
  Symptoms
  Changes
  Cause
  Solution


Created from <SR 3-3824453171>

Applies to:

Sun Storage 7310 Unified Storage System - Version: Not Applicable and later   [Release: N/A and later ]
Sun Storage 7410 Unified Storage System - Version: Not Applicable and later    [Release: N/A and later]
Sun Storage 7210 Unified Storage System - Version: Not Applicable and later    [Release: N/A and later]
Sun Storage 7110 Unified Storage System - Version: Not Applicable and later    [Release: N/A and later]
Sun ZFS Storage 7120 - Version: Not Applicable and later    [Release: N/A and later]
Information in this document applies to any platform.

Symptoms

  • Unable to access the appliance via ssh as root user and data ports are not pinging
  • IP assigned to admin port appears pingable
  • Data ports cannot be accessed via VLANs

Changes

Appliance network configuration and troubleshooting

Cause

A new switch and cables over the weekend
  • the network was cutover and this is when access was lost
  • problem has remained when trying to cut back over to the old switch

Network switch addition and reconfiguration
  • so changes have been introduced with the new switch

Solution

After further investigation and discussion with the customer, it was realized the SP had the same IP address as the BUI (management) IP address.
  • changed IP for the service processor to a unique IP
  • still could not log into the BUI so, to simplify things, unconfigured the problem interfaces (ipmp1, nge0, nge1)
  • rebuilt the interfaces and added a default route

Confirmed creation and status of interfaces:

sfospmgv01:configuration net interfaces ipmp1> get
state = up
curaddrs = 10.1.10.23/24
class = ipmp
label = Public
enable = true
admin = true
links = nge1,nge0
v4addrs = 10.1.10.23/24
v4dhcp = false
v6addrs =
v6dhcp = false
key = 1
standbys =
sfospmgv01:configuration net interfaces ipmp1> done

sfospmgv01:configuration net interfaces> get
Interfaces:

INTERFACE STATE CLASS LINKS ADDRS LABEL
ipmp1 up ipmp nge1 10.1.10.23/24 Public
nge0
ipmp2 up ipmp nxge0 10.1.23.2/24 Private
nxge1
nge0 up ip nge0 0.0.0.0/8 Pub IPMP 0
nge1 up ip nge1 0.0.0.0/8 Pub IPMP 1
nxge0 up ip nxge0 0.0.0.0/8 Priv IPMP 0
nxge1 up ip nxge1 0.0.0.0/8 Priv IPMP 1



Add a default route:

sfospmgv01:configuration net routing> show
Properties:
multihoming = loose

Routes:

ROUTE DESTINATION GATEWAY INTERFACE TYPE
route-000 10.1.10.0/24 10.1.10.23 ipmp1 system
route-001 10.1.23.0/24 10.1.23.2 ipmp2 system

sfospmgv01:configuration net routing> create
sfospmgv01:configuration net route (uncommitted)> set family=<tab key>
IPv4 IPv6
sfospmgv01:configuration net route (uncommitted)> set family=IPv4
family = IPv4 (uncommitted)
sfospmgv01:configuration net route (uncommitted)> set destination=0.0.0.0
destination = 0.0.0.0 (uncommitted)
sfospmgv01:configuration net route (uncommitted)> semt mask=0
mask = 0 (uncommitted)
sfospmgv01:configuration net route (uncommitted)> set interface=ipmp1
interface = ipmp1 (uncommitted)
sfospmgv01:configuration net route (uncommitted)> set gateway=10.1.10.1
gateway = 10.1.10.1 (uncommitted)
sfospmgv01:configuration net route (uncommitted)> commit

sfospmgv01:configuration net routing> show
Properties:
multihoming = loose

Routes:

ROUTE DESTINATION GATEWAY INTERFACE TYPE
route-000 0.0.0.0/0 10.1.10.1 ipmp1 static     <---------- default route added
route-001 10.1.10.0/24 10.1.10.23 ipmp1 system
route-002 10.1.23.0/24 10.1.23.2 ipmp2 system
-----

Still could not ping the default gateway ...
  • ran a snoop on nge0 and nge1 and noticed vlan67 but no output in snoop for vlan10
  • it was then clear we needed vlan tags for this network set 10.1.10.0

Added vlan id's to nge0 nge1 and pinged default route

sfospmgv01:configuration net datalinks> show

Datalinks:

DATALINK CLASS LINKS STATE LABEL
nge0 device nge0 up GbE0
nge1 device nge1 up GbE1
nge10000 vlan nge0 up Servers-Video1 <---- added  this vlan tag and can now ping ipmp1 address
nxge0 device nxge0 up 10GbE0
nxge1 device nxge1 up 10GbE1

sfospmgv01:configuration net datalinks> vlan
sfospmgv01:configuration net datalinks vlan (uncommitted)> set label=Servers-Video2
label = Servers-Video2 (uncommitted)
sfospmgv01:configuration net datalinks vlan (uncommitted)> set links=<tab key>
nge0 nge1 nxge0 nxge1
sfospmgv01:configuration net datalinks vlan (uncommitted)> set links=nge1
links = nge1 (uncommitted)
sfospmgv01:configuration net datalinks vlan (uncommitted)> set id=10
id = 10 (uncommitted)
sfospmgv01:configuration net datalinks vlan (uncommitted)> commit

sfospmgv01:configuration net datalinks> get
Datalinks:

DATALINK CLASS LINKS STATE LABEL
nge0 device nge0 up GbE0
nge1 device nge1 up GbE1
nge10000 vlan nge0 up Servers-Video1
nge10001 vlan nge1 up Servers-Video2
nxge0 device nxge0 up 10GbE0
nxge1 device nxge1 up 10GbE1

sfospmgv01:configuration net datalinks> ping 10.1.10.1
10.1.10.1 is alive


Attachments
This solution has no attachment
  Copyright © 2012 Sun Microsystems, Inc.  All rights reserved.
 Feedback