Turn on suggestions
![]() Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
|
09-06-2012 12:59 PM
Hi all,
I have this message in my errshow:
2012/09/06-16:33:08, , 432639, SLOT 4 | FID 128, WARNING, FL-D-PRD-CORE01-D23, NPIV port 2/19 has same Port WWN with old port 2/43 with pid 0x176b08 as part of duplicate Port WWN detection policy
On output from portshow shows the same WWN on these ports:
------------------------------------------------------
FL-D-PRD-CORE01-D23:FID128:nt\waraujo> portshow 2/19
portIndex: 83
portName: slot2 port19
portHealth: No Fabric Watch License
Authentication: None
portDisableReason: None
portCFlags: 0x1
portFlags: 0x24b03 PRESENT ACTIVE F_PORT G_PORT U_PORT LOGICAL_ONLINE LOGIN NOELP LED ACCEPT FLOGI
LocalSwcFlags: 0x0
portType: 17.0
portState: 1 Online
Protocol: FC
portPhys: 6 In_Sync portScn: 32 F_Port
port generation number: 0
state transition count: 1
portId: 175300
portIfId: 4322001a
portWwn: 20:53:00:05:33:02:ac:00
portWwn of device(s) connected:
20:00:b4:99:ba:28:3d:a2
Distance: normal
portSpeed: N8Gbps
------------------------------------------------------
FL-D-PRD-CORE01-D23:FID128:nt\waraujo> portshow 2/43
portIndex: 107
portName: slot2 port43
portHealth: No Fabric Watch License
Authentication: None
portDisableReason: None
portCFlags: 0x1
portFlags: 0x24b03 PRESENT ACTIVE F_PORT G_PORT U_PORT NPIV LOGICAL_ONLINE LOGIN NOELP LED ACCEPT FLOGI
LocalSwcFlags: 0x0
portType: 17.0
portState: 1 Online
Protocol: FC
portPhys: 6 In_Sync portScn: 32 F_Port
port generation number: 0
state transition count: 1
portId: 176b00
portIfId: 43220022
portWwn: 20:6b:00:05:33:02:ac:00
portWwn of device(s) connected:
10:00:00:00:c9:c8:b2:6c
10:00:00:00:c9:c8:b4:5e
10:00:00:00:c9:c8:17:c6
10:00:00:00:c9:c8:18:b6
10:00:00:00:c9:c4:a5:2e
10:00:00:00:c9:cd:ec:2e
10:00:00:00:c9:cd:ed:56
10:00:00:00:c9:cd:ee:aa
20:11:b4:99:ba:28:3d:a2
Distance: normal
portSpeed: N8Gbps
------------------------------------------------------
How can I fix this?
Is possible ESX Server generate 2 equal WWNs?
Thanks,
Wellington
09-07-2012 01:19 AM
Hi,
With command portloginshow <slot/port> you can check which wwn matchs with PID 0x176b08.
I do not think that ESX is responsible of generating 2 equal WWNs... It looks that ports 2/19 and 2/43 are connected to the same Blade switch. In environments like yours, I have seen that when a host is moved from an upstream port to another, the blade switch does not update the switch, FL-D-PRD-CORE01-D23 in this case, and the switch does not update the Name server properly. I would bet that this is the reason why you get this event. I would blame Firmware version in the Blade switch as the originator of the issue.
Rgds