Sun ZFS Storage 7120
 
Sun ZFS Storage 7320
 
Sun ZFS Storage 7420
 

PLA-Support>Sun Systems>DISK>NAS>SN-DK: 7xxx NAS
 

In this Document

Symptoms

Changes

Cause

Solution

References

Created from <SR 3-5873450561>

Applies to:

Symptoms

when the support bundle [ak.5bfe9cb5-299e-e554-9f0e-8cf0c7c53ab9.tar.gz] arrives on the analysis server

Datalink Devices. BUI shows devices e1000g0 thru e1000g3, whereas command line showing e1000g1 thru e1000g4

1. check net directory and all information related to the devices
2. check Appliance Kit version, BIOs and SP
3. check known bugs or issues with this discrepancy
4. escalate to backline engineer to review support bundle and work in shared shell/webex
5. document information found related to BUI e1000g0 thru e1000g3 and CLI e1000g1 thru e1000g4
6. Open a bug if the code is current, problem is reproducible and collect data for development

Changes

 Escalate to L2 with a collaboration SR to resolve this problem

Cause

path to inst was not configured with the correct paths

Nothing has changed on the network infrastructure side of things.  All cables are plugged in and working as confirmed by the interfaces being UP.   The issue we seem to be facing is that somehow the device names changed. And that seems to be causing the problem.  The device names in the BUI used to be e1000g1 thru e1000g4.  Now the device names are e1000g0 thru e1000g3.  Because of the name changes in the BUI, our  interfaces are having anomalies.   NOTE:  on all of our other 7000 series arrays, the device  are e1000g1 thru e1000g4 in  both the BUI and the command line.   Something happened to this 7420  causing the devices to change.  (Note, both heads are showing the same discrepancy between the command line and the BUI.  The BUI is e1000g0 thru e1000g3 and the command line is e1000g1 thru e1000g4).
 
customer comment : The only change that occurred recently was that we purchased an additional 8 disk shelves which just got cabled up last week. This required installing an additional SAS hba in each head.

bash-4.1$ grep -i e1000g *.sys
debug.sys:Jun 21 18:45:39 nas02-b-mm3 in.routed[17068]: [ID 238047 daemon.warning] interface e1000g4 to 10.40.24.59 turned off
debug.sys:Jun 21 18:46:44 nas02-b-mm3 in.routed[17068]: [ID 238047 daemon.warning] interface e1000g4 to 10.40.24.59 turned off
debug.sys:Jun 21 18:51:19 nas02-b-mm3 in.routed[17068]: [ID 238047 daemon.warning] interface e1000g4 to 10.40.24.59 turned off
debug.sys:Jun 21 19:29:19 nas02-b-mm3 in.routed[17068]: [ID 238047 daemon.warning] interface e1000g4 to 10.40.24.59 turned off
debug.sys:Jun 21 19:31:31 nas02-b-mm3 in.routed[17068]: [ID 238047 daemon.warning] interface e1000g4 to 10.40.24.59 turned off
debug.sys:Jun 21 19:31:33 nas02-b-mm3 in.routed[17068]: [ID 300549 daemon.warning] interface e1000g4 to 10.40.24.59 restored
debug.sys:Jun 21 19:31:44 nas02-b-mm3 in.routed[17068]: [ID 238047 daemon.warning] interface e1000g4 to 10.40.24.59 turned off
debug.sys:Jun 21 19:32:47 nas02-b-mm3 in.routed[17068]: [ID 238047 daemon.warning] interface e1000g4 to 10.40.24.59 turned off
debug.sys:Jun 21 19:53:41 nas02-b-mm3 in.mpathd[2081]: [ID 341557 daemon.error] IP interface repair detected on e1000g1 of group ipmp1
system.sys:Jun 21 19:53:41 nas02-b-mm3 in.mpathd[2081]: [ID 341557 daemon.error] IP interface repair detected on e1000g1 of group ipmp1

bash-4.1$ grep -i e1000g *.txt
rm.ak.txt:Mon Jun 25 14:55:05 2012: update_svc ak:/svc/datalink:e1000g2
rm.ak.txt:Mon Jun 25 14:55:05 2012: update_svc ak:/svc/interface:e1000g2
rm.ak.txt:Mon Jun 25 14:55:05 2012: update_svc ak:/svc/datalink:e1000g4
rm.ak.txt:Mon Jun 25 14:55:05 2012: update_svc ak:/svc/interface:e1000g4
rm.ak.txt:Mon Jun 25 14:55:06 2012: update_svc ak:/svc/datalink:e1000g1
rm.ak.txt:Mon Jun 25 14:55:06 2012: update_svc ak:/svc/interface:e1000g1
rm.ak.txt:Mon Jun 25 14:55:06 2012: update_svc ak:/svc/datalink:e1000g3
rm.ak.txt:Mon Jun 25 14:55:06 2012: update_svc ak:/svc/interface:e1000g3
rm.ak.txt:Mon Jun 25 14:55:10 2012: update_svc ak:/net/e1000g1
rm.ak.txt:Mon Jun 25 14:55:10 2012: update_svc ak:/net/e1000g2
rm.ak.txt:Mon Jun 25 14:55:10 2012: update_svc ak:/net/e1000g3
rm.ak.txt:Mon Jun 25 14:55:10 2012: update_svc ak:/net/e1000g4
rm.ak.txt:Mon Jun 25 14:55:18 2012: update_svc ak:/smb/e1000g1
rm.ak.txt:Mon Jun 25 14:55:18 2012: update_svc ak:/smb/e1000g2
rm.ak.txt:Mon Jun 25 14:55:18 2012: update_svc ak:/smb/e1000g3
rm.ak.txt:Mon Jun 25 14:55:18 2012: update_svc ak:/smb/e1000g4
 

Solution

Solution:
Proposed Solution was to escalate to backline engineer and perform a pathing correction to the network devices
on the passive node corrected path_to_inst then updated the boot archive. Performed a takeover and rebooted the node. Did this for each head in the cluster.

Action Plan:
path to inst was not configured with the correct paths

nas02-a:> configuration net devices ls
Devices:
  
DEVICE UP SPEED MAC
e1000g1 true 1000 Mbit/s 0:1b:21:aa:75:1
e1000g2 true 1000 Mbit/s 0:1b:21:aa:75:0
e1000g3 true 1000 Mbit/s 0:1b:21:aa:75:3
e1000g4 true 1000 Mbit/s 0:1b:21:aa:75:2
igb0 true 1000 Mbit/s 0:21:28:bc:9d:ac
igb1 false 0 Mbit/s 0:21:28:bc:9d:ad
igb2 true 1000 Mbit/s 0:21:28:bc:9d:ae
igb3 true 1000 Mbit/s 0:21:28:bc:9d:af

nas02-b:> configuration net devices ls
Devices:
  
DEVICE UP SPEED MAC
e1000g1 true 1000 Mbit/s 0:1b:21:aa:75:69
e1000g2 true 1000 Mbit/s 0:1b:21:aa:75:68
e1000g3 true 1000 Mbit/s 0:1b:21:aa:75:6b
e1000g4 true 1000 Mbit/s 0:1b:21:aa:75:6a
igb0 false 0 Mbit/s 0:21:28:3d:e7:c0
igb1 true 1000 Mbit/s 0:21:28:3d:e7:c1
igb2 true 1000 Mbit/s 0:21:28:3d:e7:c2
igb3 true 1000 Mbit/s 0:21:28:3d:e7:c3
 

References

This solution has no attachment