IVR between VSANs not working

[Artem Troitsky]

Hi there!

We're using MDS9513 with NX-OS 5.0(8) with server in VSAN 223 and storage in VSAN 227. There is no way to put them in the same VSAN, so IVR must be put in place.

switchA# sh ivr zone n ServerA_CX4-960_2 a
zone name ServerA_CX4-960_2
  * pwwn XX:XX:XX:XX:XX:XX:XX:XX            vsan  223 autonomous-fabric-id  1
         [ServerAQLA1]
  * pwwn YY:YY:YY:YY:YY:YY:YY:YY            vsan  227 autonomous-fabric-id  1
         [CLAR960-A6]
  * pwwn ZZ:ZZ:ZZ:ZZ:ZZ:ZZ:ZZ:ZZ            vsan  227 autonomous-fabric-id  1
         [CLAR960-B6]

VSAN-topology is set to manual, all VSANs (223 and 227) are added, but server doesn't see storage nor vice versa

Does someone has similar issues? Any advice is greatly appreciated

[Walter Dey]

Hi Artem

Something basic seems to be wrong.

Check with

http://www.cisco.com/c/en/us/td/docs/switches/datacenter/mds9000/sw/nx-os/configuration/guides/ivr/nx-os_ivr/nxos_ivr/ivrbasic.html#wp1965808

This has been done before many times, and should work.

Did you check the error log ?

Walter.

[Artem Troitsky]

Hi Walter!

Thanks for the answer. Error log is empty, at least with no errors on IVR or VSAN related stuff

show ivr tech-support

shows nothing strange. Besides, we have tons of IVRs between other VSANs and they're working perfectly

[Walter Dey]

Hi Artem

From your output above, it seems that server and storage have done flogi (* in front of the pwwn); could it be, that something with lun masking / mapping is wrong ?

Btw. is this a dual fabric design ? and therefore a possible cabling issue ? in the output I see Clariion A6 B6 ?

Walter.

[Artem Troitsky]

Hi Walter,

The problem is that there is no LUN Z at server side nor array sees server's WWPNs. Yes, it is a dual fabric, second fabric includes VSANs 224 and 228 and they're working perfectly. As far as we see FLOGI as you mentioned, there couldn't be any cabling issue as it lies far lower than the logical level at which devices were able to log in to fabric. Yes, it is CLARiiON CX4-960 we're trying to reach

[Walter Dey]

Hi Artem

So one fabric is working ok !

What is the OS ?

Are you using dual homed HBA's and what brand ?

Could it be a Multipathing issue ? active - standby ? ....

[Artem Troitsky]

Hi Walter,

OS is Windows 2003, not sure about HBA - will check tomorrow, as well as multipathing, but I doubt that it could be MP - we're using EMC PowerPath with license and in any case second port should've been logged on array side

[Walter Dey]

Then I would swap fabric A and B, and see if the error moves as well ! ok, I know its a pain, zoning must be changed.

Btw. are all the MDS versions in both fabrics identical ?

[Artem Troitsky]

Yes, versions between MDSes are the same. Not sure that swapping fabrics will help - we had similar issue couple of months ago, that time we just took ports in different VSAN, so it seems that problem is not local to the server

[Walter Dey]

This is weird.

Can you please check the vsan's 223 and 227, and verify their domain id's, and if they have any overlap with other domain id's ?

Must be a trivial problem.

[Artem Troitsky]

Hi all,

Checked domains - no overlapping, anyway, the traffic is localized on one switch

mds-c9513-sm22-1-261# sh ivr zone n Dumanoir_CX4-960_2 ac

zone name Dumanoir_CX4-960_2
  * pwwn 50:06:0b:00:00:ec:d9:b2            vsan  223 autonomous-fabric-id  1
         [DumanoirQLA1]
  * pwwn 50:06:01:66:3b:20:74:39            vsan  227 autonomous-fabric-id  1
         [CLAR960-A6]
  * pwwn 50:06:01:6e:3b:20:74:39            vsan  227 autonomous-fabric-id  1
         [CLAR960-B6]
mds-c9513-sm22-1-261# sh fl d | i 50:06:0b:00:00:ec:d9:b2|50:06:01:66:3b:20:74:39|50:06:01:6e:3b:20:74:39 n 1
fc3/21           227   0xd301ef  50:06:01:66:3b:20:74:39 50:06:01:60:bb:20:74:39
                           [CLAR960-A6]
--
fc6/24           223   0xd11100  50:06:0b:00:00:ec:d9:b2 50:06:0b:00:00:ec:d9:b0
                           [DumanoirQLA1]
--
fc11/21          227   0xd300ef  50:06:01:6e:3b:20:74:39 50:06:01:60:bb:20:74:39
                           [CLAR960-B6]
mds-c9513-sm22-1-261# show ivr vsan-top

AFID  SWITCH WWN                 Active   Cfg. VSANS
-----------------------------------------------------------
   1  20:00:00:05:73:fa:54:00 *   yes     yes  219,221,223,225,227,229,231,301
   1  20:00:00:0d:ec:87:ed:40     yes     yes  220-230,302,666
   1  20:00:00:2a:6a:77:06:00     yes     yes  701,703,705,709,2207
   1  20:00:00:2a:6a:84:cc:80     yes     yes  666,2201,2203,2205,2207,2209

[wendra pesliko]

Hi Artem,

I have the same problem,
how do you solve this problem?

I'd appreciate it if you can provide me procedures as detail as possible.

 
Thank you!

[dynamoxxx]

can we see your ivr topology ?

[Walter Dey]

I mean "sho fcdomain domainlist vsan xyz...." (maybe there is typo) for all the VSAN in your IVR list.

[Artem Troitsky]

See the output below

mds-c9513-sm22-1-261# sh fcdomain domain-list vsan 223

Number of domains: 9
Domain ID              WWN
---------    -----------------------
0xd1(209)    20:df:00:05:73:fa:54:01 [Local] [Principal]
 0x54(84)    20:df:00:05:73:cf:7f:41
0x6a(106)    20:df:00:0d:ec:c8:e5:01
 0x56(86)    20:df:00:05:73:d0:27:41
 0x23(35)    20:df:00:05:73:b3:04:41
 0x5b(91)    20:df:00:0d:ec:e5:e0:41
0xcf(207)    20:df:00:05:9b:23:20:81
0xdf(223)    20:df:00:0d:ec:87:ed:41
 0x61(97)    20:df:00:0d:ec:60:a5:01
mds-c9513-sm22-1-261# sh fcdomain domain-list vsan 227

Number of domains: 4
Domain ID              WWN
---------    -----------------------
0xd3(211)    20:e3:00:05:73:fa:54:01 [Local] [Principal]
0xda(218)    20:e3:00:0d:ec:87:ed:41
 0x13(19)    20:e3:00:05:73:da:b1:e1
0xee(238)    20:e3:00:05:9b:23:20:81