The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This chapter provides advanced configuration information and instructions. Before setting up advanced IVR configurations, see “Configuring Basic Inter-VSAN Routing,” which includes basic configuration instructions and descriptions of IVR features, limits, and terminology.
This section includes the following topics:
In a complex network topology, you might only have a few IVR-enabled VSANs. To reduce the amount of traffic to non-IVR-enabled VSANs, you can configure service groups that restrict the traffic to the IVR-enabled VSANs. A maximum of 16 IVR service groups are allowed in a network. When a new IVR-enabled switch is added to the network, you must update the service groups to include the new VSANs.
All AFID and VSAN combinations that are part of an IVR VSAN topology but are not part of any user-defined service group are members of the default service group. The identifier of the default service group is 0.
By default, IVR communication is permitted between members of the default service group. You can change the default policy to deny. To change the default policy, see Configuring IVR Service Groups. The default policy is not part of ASCII configuration.
A configured service group must be activated. Like zone set activation or VSAN topology activation, the activation of a configured service group replaces the currently active service group, if any, with the configured one. There is only one configured service group database and one active service group database. Each of these databases can have up to 16 service groups.
The autonomous fabric ID (AFID) distinguishes segmented VSANS (for example, two VSANs that are logically and physically separate but have the same VSAN number). Cisco Fabric Manager Release 4.2(1) supports AFIDs 1 through 64. AFIDs are used in conjunction with IVR auto topology mode to allow segmented VSANs in the IVR VSAN topology database.
FC ID persistence improves IVR management by providing the following features:
The benefits of persistent FC IDs for IVR are as follows:
This section describes advanced configuration information for IVR zones and IVR zone sets. For basic information on configuring IVR zones and zone sets, see Configuring IVR Zones and IVR Zone Sets.
As part of the IVR configuration, you need to configure one or more IVR zone to enable cross-VSAN communication. To achieve this, you must specify each IVR zone as a set of (pWWN, VSAN) entries. Different IVR zone sets can contain the same IVR zone, because IVR zones can be members of one or more IVR zone sets.
Note The same IVR zone set must be activated on all of the IVR-enabled switches.
IVR is used for devices from different VSANs to communicate with each other. As the fabric size increases, there is a need to create IVR islands. The IVR data communication is limited only within the islands. By creating various IVR CFS regions, the data communication can be limited to the regions.
Currently, DCNM-SAN only supports a single IVR CFS region.
Beginning with Release 5.2, DCNM-SAN supports multiple IVR regions and has the following features:
Advanced fabric services (such as SME and IOA) use a fabric-wide FC-Redirect infrastructure to redirect the traffic flows. These services can now be enabled on IVR flows using an internal feature, Abstract ACL Manager (AAM).
This section includes the following topics:
When configuring IVR service groups, consider these guidelines:
You can configure AFIDs individually for VSANs, or you can set the default AFIDs for all VSANs on a switch. If you configure an individual AFID for a subset of the VSANs on a switch that has a default AFID, that subset uses the configured AFID while all other VSANs on that switch use the default AFID.
You can only use an AFID configuration when the VSAN topology is in IVR auto topology mode. In IVR manual topology mode, the AFIDs are specified in the VSAN topology configuration itself and a separate AFID configuration is not needed.
Note Two VSANs with the same VSAN number but different AFIDs are counted as two VSANs out of the total 128 VSANs allowed in the fabric.
When devices attached to multiple switches belong to one VSAN, they cannot communicate with each other by configuring the regular zone set because the AFIDs are different. You can consider that the different AFIDs are different fabrics; therefore, the three switches represent three separate fabrics.
Before configuring an IVR SAN fabric without IVR in NAT mode or IVR auto topology mode, consider the following general guidelines:
Before configuring domain IDs, consider the following guidelines:
– All edge switches in the edge VSANs (source and destination)
– All switches in transit VSANs
You can configure domain IDs using one of two options:
Note In a configuration involving IVR without NAT, if one VSAN in the IVR topology is configured with static domain IDs, then the other VSANs (edge or transit) in the topology must be configured with static domain IDs.
Before configuring transit VSANS, consider the following guidelines:
– If two edge VSANs in an IVR zone overlap, then a transit VSAN is not required (though, not prohibited) to provide connectivity.
– If two edge VSANs in an IVR zone do not overlap, you may need one or more transit VSANs to provide connectivity. Two edge VSANs in an IVR zone will not overlap if IVR is not enabled on a switch that is a member of both the source and destination edge VSANs.
Before configuring border switches, consider the following guidelines:
You must create the IVR topology on every IVR-enabled switch in the fabric if you have not enabled IVR auto topology mode. Consider the following guidelines when using IVR manual topology mode:
– The switch WWNs of the IVR-enabled switches.
– A minimum of two VSANs to which the IVR-enabled switch belongs.
– The AFID, which distinguishes two VSANs that are logically and physically separate, but have the same VSAN number. You can specify up to 64 AFIDs. See Figure 1-1.
Figure 1-1 Example IVR Topology with Non-Unique VSAN IDs Using AFIDs
Before configuring persistent FC IDs, consider the following:
– 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:
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:
Virtual FC ID to be used to represent a device for the given pWWN in the current AFID and VSAN
When interop mode is enabled, consider the following IVR configuration guidelines:
The following guidelines and limitations must be considered before enabling AAM for IVR:
This section includes the following topics:
To configure an advanced IVR topology in a SAN fabric, follow these steps:
|
|
|
---|---|---|
Determine whether or not to use IVR Network Address Translation (NAT). |
See IVR Network Address Translation and IVR NAT Requirements and Guidelines. |
|
If you do not plan to use IVR NAT, verify that unique domain IDs are configured in all switches and VSANs participating in IVR. |
See Domain ID Guidelines. |
|
See IVR Service Groups. |
||
Configure the IVR topology, either manually or automatically. |
See Manually Configuring an IVR Topology and Configuring Basic Inter-VSAN Routing. |
|
Create and activate IVR zone sets in all of the IVR-enabled border switches, either manually or using fabric distribution. |
To configure an IVR service group, follow these steps:
Step 1 Expand All VSANs, and then select IVR in the Logical Domains pane.
You see the IVR configuration in the Information pane.
Step 2 Click the Service Group tab to display the existing service groups.
Step 3 Click the Create Row icon to make a new service group.
You see the service group dialog box.
Step 4 Check the switch check box for each switch involved in IVR.
Step 5 Complete the Name field for the service group and fill in the Fabric ID field for this entry.
Step 6 Enter a comma-separated list of VSAN IDs in the VSAN List text box.
Step 7 Click Create to create this entry or click Cancel to discard all changes.
Step 8 Repeat Step 1 through Step 7 for all switches and AFIDs associated with your IVR topology.
To configure default AFIDs, follow these steps:
Step 1 Expand All VSANs and then select IVR in the Logical Domains pane.
You see the IVR configuration in the Information pane.
Step 2 Click the Default Fabric ID tab to display the existing default AFIDs.
Step 3 Click the Create Row icon to create a default AFID.
Step 4 Check the check boxes next to each switch involved in IVR that you want to use this default AFID.
Step 5 Provide a name for each switch WWN and set the default fabric ID.
Step 6 Click Create to create this entry.
Step 7 Repeat Step 1 through Step 6 for all default AFIDs that you want to configure in your IVR topology.
To configure individual AFIDs, follow these steps:
Step 1 Expand All VSANs and then select IVR in the Logical Domains pane.
You see the IVR configuration in the Information pane.
Step 2 Click the Fabric ID tab to display the existing AFIDs.
Step 3 Click the Create Row icon to create an AFID.
Step 4 Check the check box next to each switch involved in IVR that you want to use this default AFID.
Step 5 Provide a name for each switch WWN and set the fabric ID.
Step 6 Enter a comma-separated list of VSAN IDs in the VSAN List text box.
Step 7 Click Create to create this entry.
Step 8 Repeat Step 1 through Step 6 for all switches and AFIDs you want to configure in your IVR topology.
To enable IVR without NAT, follow these steps:
Step 1 Expand All VSANs and then select IVR in the Logical Domains pane.
You see the IVR configuration in the Information pane.
Step 3 Uncheck the Enable IVR NAT check box.
Step 4 Click the Apply Changes icon to distribute this change to all switches in the fabric.
To manually configure an IVR topology, follow these steps:
Step 1 Expand All VSANs and then select IVR in the Logical Domains pane.
You see the IVR configuration in the Information pane.
Step 2 Click the Local Topology tab to display the existing IVR topology.
Step 3 Click the Create Row icon to create rows in the IVR topology.
Step 4 Select the switch, switch WWN, and a comma-separated list of VSAN IDs for this topology.
Step 5 Click Create to create this new row.
Step 6 Click the Apply Changes icon to create the IVR topology.
Repeat this configuration on all IVR-enabled switches or distribute the IVR configuration using CFS.
After manually configuring the IVR topology, you must activate it.
To activate a manually configured IVR topology, follow these steps:
Step 1 Expand All VSANs and then select IVR in the Logical Domains pane.
You see the IVR configuration in the Information pane.
Step 2 Click the Action tab to display the existing IVR topology.
Step 3 Check the Activate Local Topology check box.
Step 4 Click the Apply Changes icon to activate the IVR topology.
To clear a manually created IVR topology database, follow these steps:
Step 1 Expand All VSANs and then select IVR in the Logical Domains pane.
Step 2 Click the Control tab if it is not already displayed.
Step 3 Highlight the rows you want to delete from the IVR topology.
Step 4 Click the Delete Row icon to delete these rows from the IVR topology.
Step 5 Click the Apply Changes icon to delete the IVR topology.
To migrate from IVR auto topology mode to IVR manual topology mode, follow these steps:
Step 1 Expand All VSANs and then select IVR in the Logical Domains pane.
You see the IVR configuration in the Information pane.
Step 3 Highlight the switch on which you want to disable IVR auto topology mode.
Step 4 Uncheck the Auto Discover Topology check box.
Step 5 Click the Apply Changes icon.
To configure persistent FC IDs for IVR, follow these steps:
Step 1 Expand All VSANs and then select IVR in the Logical Domains pane.
You see the IVR configuration in the Information pane.
Step 3 Click the Create Row icon to create an FC ID.
Step 4 Select the switch for which you are configuring the virtual FC ID to be used to represent a device in a specific VSAN (current VSAN).
Step 5 Enter the current fabric in the Current Fabric ID field for the fcdomain database.
Step 6 Enter the current VSAN in the Current VSAN ID field for the fcdomain database.
Step 8 Click the drop-down menu to select the FC ID to map to the pWWN you selected.
Step 9 Click Create to create this new row.
LUN zoning can be used between members of active IVR zones.You can configure the service by creating and activating LUN zones between the desired IVR zone members in all relevant edge VSANs using the zoning interface or you can use LUN zoning directly supported by IVR. For more details on the advantages of LUN zoning, refer to the Cisco MDS 9000 Family NX-OS Fabric Configuration Guide or the Fabric Configuration Guide, Cisco DCNM for SAN.
Note You can configure LUN zoning in an IVR zone set setup.
Note The default QoS attribute setting is low.
To configure QoS for an IVR zone, follow these steps:
Step 1 Choose Zone > Edit Local Full Zone Database.
You see the Edit IVR Local Full Zone Database dialog box for the VSAN you selected.
Step 2 Select Zones or a zone set.
Step 3 Check the QoS check box and set the QoS priority.
Step 4 Click Activate to make the changes.
To rename an IVR zone or IVR zone set, follow these steps:
Step 1 Choose Zone > Edit Local Full Zone Database.
You see the Edit IVR Local Full Zone Database dialog box for the VSAN you selected.
Step 2 Click a zone or zone set in the left pane.
An edit box appears around the zone or zone set name.
Step 5 Click Activate or Commit Changes.
To configure IVR CFS region, follow these steps:
Step 1 Expand All VSANs, and then select IVR in the Logical Domains pane.
You see the IVR configuration in the Information pane.
Step 2 Click the Control tab to enable the feature on the switch.
You see only the switches in the selected region. All switches without the IVR region configuration are a part of a default region.
Step 3 Expand Switches and select CFS in the Physical Attributes pane.
If the feature is enabled correctly, the switch appears in the CFS tab.
Step 4 Select All Regions and click Create Row.
Step 5 Enter the Region ID for the switch.
Step 6 Click Activate or Commit Changes.
Read-only zoning (with or without LUNs) can be used between members of active IVR zones. To configure this service, you must create and activate read-only zones between the desired IVR zone members in all relevant edge VSANs using the zoning interface.
Note Read-only zoning cannot be configured in an IVR zone set setup.