IVR virtual domain in fcdomain domain-list interop mode 2 and 3

MDS2# show ivr vsan-topology AFID SWITCH WWN Active Cfg. VSANS Switch-Name-------------------------------------------------------------------------1 20:00:00:0d:ec:0e:b2:40 yes yes 502 20:00:00:0d:ec:0e:b2:40 yes yes 512 20:00:00:0d:ec:19:c9:00 * yes yes 513 20:00:00:0d:ec:19:c9:00 * yes yes 50 Total: 4 entries in active and configured IVR VSAN-Topology On MDS1 I am seeing the virtual domain in the fcdomain domain-list. This normally would not happen unless you explicitly configure the ivr virtual-fcdomain-add command.  However this is added by SAN-OS in interop modes 2 and 3. This is known as RDI Mode. Observe the following:

MDS1# show ivr virtual-fcdomain-add-statusIVR virtual domains are added to fcdomain list in VSANS: 50Force Option : Off I did not configure ivr virtual-fcdomain-add vsan 50, yet it's behaving as if I did.  It is automatically added by SAN-OS.

MDS1# show fcdomain domain-list vsan 50 Number of domains: 3Domain ID WWN--------- -----------------------0x62(98) 20:32:00:0d:ec:0e:b2:41 0x63(99) 10:00:00:60:69:20:28:97 0x6a(106) 10:00:08:00:88:30:01:8a You can clearly see from the above output the virtual-domain of 0x6a being added to the fcdomain domain-list on MDS1.

MDS1# show ivr virtual-domVSAN # Domains IVR Virtual Domains---- --------- ----------------------------------------------50 1 10651 2 99,106---- --------- ---------------------------------------------- Now take a look at MDS2, which is behaving in a regular fashion since its in interop mode 1:

MDS2# show ivr virtual-fcdomain-add-statusIVR virtual domains are not added to fcdomain listForce Option : OffMDS2# show fcdomain domain-list vsan 50 Number of domains: 2Domain ID WWN--------- -----------------------0x64(100) 20:32:00:0d:ec:19:c9:01 0x6a(106) 10:00:08:00:88:30:01:8a MDS2# show ivr virtual-domVSAN # Domains IVR Virtual Domains---- --------- ----------------------------------------------50 1 9951 2 99,106---- --------- ---------------------------------------------- Thanks to Cisco TAC for pointing this behavior out to me. It's documented in the Cisco MDS9000 Interoperability Configuration Guide