Configuring Persistent FC IDs for IVR

Question

Has anybody configured this for  IVR ? I use persistent FC IDs for my regular VSANs because i have a  couple of AIX boxes. I will also have a couple of them access storage  via IVR, dynamic tracking is not enabled on the host so i am wondering  if i should enabled persistent fc id for IVR ?
Thanks

Answer 1

Sure
Assuming a single MDS using vsan 1 and vsan 2, both vsans using domain ID 0x12.
HBA is pwwn1, Storage is pwwn2
config term
This is to export the storage array that resides in vsan 2, into vsan 1 as fcid 0xaa3344
ivr fcdomain database autonomous-fabric-num 1 vsan 1
native-autonomous-fabric-num 1 native-vsan 2 domain 0xAA
  pwwn pwwn2 fcid 0xAA3344
This is to export the hba that resides in vsan 1, into vsan 2 as fcid 0x232323
ivr fcdomain database autonomous-fabric-num 1 vsan 2
native-autonomous-fabric-num  1 native-vsan 1 domain 0x23
  pwwn pwwn1 fcid 0x232323
If there are multiple MDS in the IVR topology, these entries would need to be included in each of the IVR enabled MDS.
You can use CFS to form peers amongst the IVR enabled switches and then use the 'ivr commit' to propagate the config command to the other MDS.
In this example, domain ID 0x23 can not already exist in vsan 2, nor can any switch join vsan 2 using domain ID 0x23.  The same is true for vsan 1 and domain 0xAA.
Lastly, this example does reflect overlapping vsan IDs.  That is why both vsan 1 and 2 are in autonomous-fabric (AFID).  Had there been multiple MDS, and overlapping VSAN numbers (IDs), then to use IVR, those overlapping VSANs must be configured in different AFIDs.  Basically you can have a device in vsan 1, domain ID 0x12 and using IVR NAT have it zoned with another device, in another MDS, in vsan 1, using domain ID 0x12, as long as the vsans are in different AFIDs.
The intent is not to design SANs this way, but if you have case where 2 existing SANs need to have some devices communicate, and neither SAN can change the existing vsan numbers and domain IDs, there is a way to connect the 2 devices and let them remain in the same vsan keeping the same FCID.
I would always recommend putting these static entries in place, before creating and activating the IVR zoneset.  I would not recommend adding in the static entries (unless they matched what was currently in use) , as I am not sure if the MDS would log out the devices to enforce the new static mappings.  It may only use the database when the zoneset is activated, or it could put it into effect immediately.
-now you know what I know
  Mike