Contents

• Persistent FCIDs
• Information About Persistent FCIDs
• Licensing Requirements
• Guidelines and Limitations for Persistent FCIDs
• Default Settings
• Configuring Persistent FCIDs
• Verifying IVR Configuration
• Feature History

Persistent FCIDs

---

• Information About Persistent FCIDs
• Licensing Requirements
• Guidelines and Limitations for Persistent FCIDs
• Default Settings
• Configuring Persistent FCIDs
• Verifying IVR Configuration
• Feature History

Information About Persistent FCIDs

FC ID persistence improves IVR management by providing the following features:

• Allows you to control and assign a specific virtual domain to use in a native VSAN.
• Allows you to control and assign a specific virtual FC ID for a device.

The benefits of persistent FC IDs for IVR are as follows:

• Host devices always see the same FC ID for targets.
• FC IDs help you plan your SAN layout better by assigning virtual domains for IVR to use.
• FC IDs can make SAN monitoring and management easier. When you see the same domain or FC ID consistently assigned, you can readily determine the native VSAN or device to which it refers.

Licensing Requirements

Product	License
Cisco Nexus 7000 Series.	IVR requires the FCoE license for each F-series module. FCoE enabled in a storage VDC does not require the Advanced Services License. IVR also requires the Storage Enterprise License. For a complete explanation of the Cisco NX-OS licensing scheme and how to obtain and apply licenses, see the Cisco NX-OS Licensing Guide.

Guidelines and Limitations for Persistent FCIDs

You can configure two types of database entries for persistent IVR FC IDs:

• Virtual domain entries
• Virtual FC ID entries

Virtual domain entries contain the virtual domain that should be used to represent a native VSAN in a specific VSAN (current VSAN). Virtual domain entries contain the following information:

• Native AFID
• Native VSAN
• Current AFID
• Current VSAN
• Virtual domain to be used for the native AFID and VSAN in current AFID and VSAN

Virtual FC ID entries contain the virtual FC ID that should be used to represent a device in a specific VSAN (current VSAN). Virtual FC ID entries contain the following information:

• Port WWN
• Current AFID
• Current VSAN
• Virtual FC ID to be used to represent a device for the given pWWN in the current AFID and VSAN

If you use persistent FC IDs for IVR, we recommend that you use them for all the devices in the IVR zone set. We do not recommend using persistent FC IDs for some of the IVR devices while using automatic allocation for other devices.

IVR NAT must be enabled to use IVR persistent FC IDs.

In an IVR NAT configuration, if one VSAN in the IVR topology is configured with static domain IDs, then the IVR domains that can be exported to that VSAN must also be assigned static domains.

Default Settings

Parameters	Default
IVR feature	Disabled
IVR NAT	Disabled
IVR distribution	Disabled
IVR Autotopology	Disabled
IVR VSANs	Not added to virtual domains
QoS for IVR Zones	Low

Configuring Persistent FCIDs

SUMMARY STEPS

1.    ivr fcdomain database autonomous-fabric-num fabric-num vsan vsan-id


2.    native-autonomous-fabric-num fabric-num native-vsan vsan-id domain domain-id


3.    pwwn pwwn fcid fcid


4.    device-alias alias-name fcid fcid

DETAILED STEPS

	Command or Action	Purpose
Step 1	ivr fcdomain database autonomous-fabric-num fabric-num vsan vsan-id Example: switch(config)# ivr fcdomain database autonomous-fabric-num 21 vsan 22 switch(config-fcdomain)#	Enters IVR fcdomain database configuration submode for current AFID and VSAN.
Step 2	native-autonomous-fabric-num fabric-num native-vsan vsan-id domain domain-id Example: switch(config-fcdomain)# native-autonomous-fabric-num 20 native-vsan 11 domain 12 switch(config-fcdomain-db)#	Adds or replaces a database entry for native AFID, native VSAN, and domain, and enters IVR fcdomain FC ID configuration submode. Domains of all the corresponding persistent FC ID entries, if any, are also changed to the configured domain ID.
Step 3	pwwn pwwn fcid fcid Example: switch(config-fcdomain-db)# pwwn 11:22:33:44:55:66:77:88 fcid 0x114466	Adds or replaces a database entry for mapping the pWWN to the FC ID.
Step 4	device-alias alias-name fcid fcid Example: switch(config-fcdomain-db)# device-alias SampleName fcid 0x123456	Adds a database entry for mapping the device alias to the FC ID.

Verifying IVR Configuration

To display the IVR configuration, perform one of the following tasks:

Command	Purpose
show ivr	Displays the status for the IVR configuration.
show ivr diagnostics	Displays information about IVR diagnostics.
show ivr merge status	Displays information the last IVR merge event.
show ivr pending	Displays information about the IVR pending database.
show ivr pending-diff	Displays the differences between the pending database and the config database.
show ivr vsan-topology [active | configured]	Displays the IVR VSAN topology.
show ivr session status	Displays information about IVR CFS session.
show ivr virtual-domains	Displays information about IVR virtual domains for all local VSANs.
show ivr zone	Displays information about IVR zones.
show ivr zoneset	Displays information about IVR zone sets.
show ivr service-group active	Displays information about the active service group.
show ivr service-group configured	Displays information about the configured service group.
show autonomous-fabric-id database	Displays information about the AFIDs.
show ivr virtual-fcdomain-add-status	Displays the status of the IVR virtual domain configuration.

Related Concepts

Information about IVR Zones and Zonesets

Related Tasks

Configuring IVR Zones

Configuring IVR Zone Sets

Feature History

Table 1  Feature History IVR

Feature Name	Releases	Feature Information
IVR	5.2(1)	This feature was introduced.