Solved!
Go to SolutionConnectivity with MDS9509 and NPIV
I have reviewed some discussions about this and haven't been able to address my problem. I have a blade system connected to a MDS9509. NPIV is enable and have more systems connected and logged successfully, but I have some connections that I can't get to work. From the blade side we have rebuild the configuration, and still can't connect. I see the physical ports in the fabric manager with errors (last seen 2011/09/14), and cannot see them in the flogi.
Reviewing the logs I saw that in some point of time the wwn's were succesfully logged in the switch and added to an alias, then removed (one of them):
Thu Aug 25 13:28:33 2011:update:snmp_2009_10.100.0.36:admin:Added member [ WWN: 50:06:0b:00:00:c2:92:16 ID: 1 ] to alias ESDC1SRP00010_HBA2 on VSAN 2
Thu Aug 25 13:28:10 2011:update:snmp_2009_10.100.0.36:admin:Added member [ WWN: 50:06:0b:00:00:c2:92:14 ID: 2 ] to alias ESDC1SRP00010_HBA1 on VSAN 2
Thu Aug 25 13:28:14 2011:update:snmp_2009_10.100.0.36:admin:Removed member [ WWN: 50:06:0b:00:00:c2:92:14 ID: 2 ] from alias ESDC1SRP00010_HBA1 on VSAN 2
Thu Aug 25 13:28:20 2011:update:snmp_2009_10.100.0.36:admin:Removed member [ WWN: 50:06:0b:00:00:c2:92:14 ID: 2 ] from alias ESDC1SRP00010_HBA2 on VSAN 2
Strange thing is that WWN 50:06:0b:00:00:c2:92:16 is not in the alias as it should be, and it was not removed (at least not in log), while WWN 50:06:0b:00:00:c2:92:14 was removed from alias "_HBA2" when I see no entry in the log that shows that it has been added.
Is there a way to clean the information for this WWN's? what can I do to try to get those WWN's in the flogi?
Sorry for the delay... the tech guy decided that today was a good day to change my laptop.
Anyway... The host is an HP BladeSystem c7000 Enclosure G2, which has two Cisco Interconnect Bays (HP VC 8Gb 20-Port FC Module). I have already in production and with VMAX discs 6 blades, and I have problems connecting the other 3 blades.
I've checked the logs and found out this:
-----------------------------------------------------
0007. VSAN 2 966621 after Tue Sep 13 14:26:30 2011
0007. VSAN 2 Oper REGULAR-GET(1) [SUCCESS]
0007. VSAN 2 WWN 50:06:0b:00:00:c2:92:1c
0007. VSAN 2 Req 0x000000 Mask 8 Intf fc3/35 UUID 17
0007. VSAN 2 Res 0x011d00 Mask 8
-----------------------------------------------------
-----------------------------------------------------
0008. VSAN 2 573972 after Tue Sep 13 14:26:29 2011
0008. VSAN 2 Oper REGULAR-GET(1) [SUCCESS]
0008. VSAN 2 WWN 50:06:0b:00:00:c2:92:1e
0008. VSAN 2 Req 0x000000 Mask 8 Intf fc3/36 UUID 17
0008. VSAN 2 Res 0x011c00 Mask 8
-----------------------------------------------------
-----------------------------------------------------
0342. VSAN 2 170373 after Wed Aug 24 10:56:52 2011
0342. VSAN 2 Oper REGULAR-GET(1) [SUCCESS]
0342. VSAN 2 WWN 50:06:0b:00:00:c2:92:14
0342. VSAN 2 Req 0x000000 Mask 8 Intf fc3/35 UUID 17
0342. VSAN 2 Res 0x011600 Mask 8
-----------------------------------------------------
0341. VSAN 2 212360 after Wed Aug 24 10:56:52 2011
0341. VSAN 2 Oper REGULAR-GET(1) [SUCCESS]
0341. VSAN 2 WWN 50:06:0b:00:00:c2:92:16
0341. VSAN 2 Req 0x000000 Mask 8 Intf fc3/36 UUID 17
0341. VSAN 2 Res 0x011700 Mask 8
-----------------------------------------------------
I think that there's a problem while doing the FLOGI, or whilst the switch assigns the FCID, which I think that could be wrong because the switch has the persistent FCID enabled, and this should be the FCID for each connection (I think):
MDS9509-prosegur# show fcdomain fcid persistent
Total entries 356.
Persistent FCIDs table contents:
VSAN WWN FCID Mask Used Assignment
---- ----------------------- -------- ----------- ---- ----------
2 50:06:0b:00:00:c2:92:14 0x011600 ENTIRE AREA NO DYNAMIC
2 50:06:0b:00:00:c2:92:16 0x011700 ENTIRE AREA NO DYNAMIC
2 50:06:0b:00:00:c2:92:1e 0x011c00 ENTIRE AREA NO DYNAMIC
2 50:06:0b:00:00:c2:92:1c 0x011d00 ENTIRE AREA NO DYNAMIC
Any ideas?
jvtv
42 Posts
475
0
Posted September 19th, 2011 09:00
Found out that the problem was actually the persistent FCID, for some reason the WWN got stucked with the ID and can't lose it. We created more profiles in the HP Rack to have new WWN's, disconnect the previous to delete the FCID from the switch and set it free so that the new WWN could use them.
Still don't know why the original WWN could not connect to the switch, even if I delete the persistent FCID it doesn't get online.