-
Cisco MDS 9000 Family CLI Configuration Guide, Release 3.3(3)
-
Index
-
New and Changed Information
-
Preface
- Getting Started
- Installation and Switch Management
- Switch Configuration
-
Fabric Configuration
-
Configuring and Managing VSANs
-
SAN Device Virtualization
-
Creating Dynamic VSANs
-
Configuring Inter-VSAN Routing
-
Distributing Device Alias Services
-
Configuring Fibre Channel Routing Services and Protocols
-
Managing FLOGI, Name Server, FDMI, and RSCN Databases
-
Discovering SCSI Targets
-
Configuring FICON
-
Advanced Features and Concepts
-
Configuring and Managing Zones
-
-
Security
-
Configuring FIPS
-
Configuring Users and Common Roles
-
Configuring SNMP
-
Configuring RADIUS and TACACS+
-
Configuring IPv4 and IPv6 Access Control Lists
-
Configuring Certificate Authorities and Digital Certificates
-
Configuring IPsec Network Security
-
Configuring FC-SP and DHCHAP
-
Configuring Port Security
-
Configuring Fabric Binding
-
- IP Services
- Intelligent Storage Services
- Network and Switch Monitoring
- Traffic Management
- Troubleshooting
-
Configuration Limits for Cisco MDS SAN-OS Release 3.x
-
Feedback
Table Of Contents
Configuring Inter-VSAN Routing
Fibre Channel Header Modifications
IVR NAT Requirements and Guidelines
Distributing the IVR Configuration using CFS
Enabling Configuration Distribution
About IVR NAT and Auto Topology
Configuring IVR Topology Automatic Mode
Configuring IVR Service Groups
Copying the Active IVR Service Group Database
Clearing IVR Service Group Database
Verifying IVR Service Group Configuration
Verifying the AFID Database Configuration
About IVR Without IVR NAT or Auto Topology
Manually Configuring the IVR Topology
Activating a Manually Configured IVR Topology
Adding an IVR-Enabled Switch to an Existing IVR Topology
Adding VSANs to an Existing IVR Topology
Copying the Active IVR Topology
Clearing the Configured IVR Topology Database
Migrating from IVR Auto Topology Mode to Manual Mode
Configuring IVR Virtual Domains
Verifying the IVR Virtual Domain Configuration
Clearing the IVR fcdomain Database
About Persistent FC IDs for IVR
Configuring Persistent FC IDs for IVR
Verifying the Persistent FC ID Configuration
Configuring IVR Logging Levels
Verifying Logging Level Configuration
Configuring IVR Zones and IVR Zone Sets
About Activating Zone Sets and Using the force Option
Activating or Deactivating IVR Zone Sets
Verifying IVR Zone and IVR Zone Set Configuration
Configuring LUNs in IVR Zoning
Verifying the QoS Attribute Configuration
Renaming IVR Zones and IVR Zone Sets
Clearing the IVR Zone Database
Configuring IVR Using Read-Only Zoning
System Image Downgrading Considerations
Resolving Database Merge Failures
Configuring Inter-VSAN Routing
This chapter explains the Inter-VSAN routing (IVR) feature and provides details on sharing resources across VSANs using IVR management interfaces provided in the switch.
This chapter includes the following sections:
Inter-VSAN Routing
Virtual SANs (VSANs) improve storage area network (SAN) scalability, availability, and security by allowing multiple Fibre Channel SANs to share a common physical infrastructure of switches and ISLs. These benefits are derived from the separation of Fibre Channel services in each VSAN and isolation of traffic between VSANs. Data traffic isolation between the VSANs also inherently prevents sharing of resources attached to a VSAN, such as robotic tape libraries. Using IVR, you can access resources across VSANs without compromising other VSAN benefits.
This section includes the following topics:
•
Fibre Channel Header Modifications
About IVR
Note
Data traffic is transported between specific initiators and targets on different VSANs without merging VSANs into a single logical fabric. Fibre Channel control traffic does not flow between VSANs, nor can initiators access any resource across VSANs other than the designated ones. Valuable resources such as tape libraries are easily shared across VSANs without compromise.
IVR is in compliance with Fibre Channel standards and incorporates third-party switches, however, IVR-enabled VSANs may have to be configured in one of the interop modes.
IVR is not limited to VSANs present on a common switch. Routes that traverse one or more VSANs across multiple switches can be established, if necessary, to establish proper interconnections. IVR used in conjunction with FCIP provides more efficient business continuity or disaster recovery solutions (see Figure 23-1).
Note
Figure 23-1 Traffic Continuity Using IVR and FCIP
Note
IVR Features
IVR supports the following features:
•
•
•
•
•
•
IVR Terminology
The following IVR-related terms are used in this chapter.:
•
•
•
•
•
•
•
Note
•
Note
•
•
•
•
IVR Limits Summary
Table 23-1 summarizes the configuration limits for IVR. See Appendix A, "Configuration Limits for Cisco MDS SAN-OS Release 3.1(x) and 3.2(x)," for a complete list of Cisco MDS SAN-OS feature configuration limits.
Fibre Channel Header Modifications
IVR works by virtualizing the remote end devices in the native VSAN using a virtual domain. When IVR is configured to link end devices in two disparate VSANs, the IVR border switches are responsible for modifying the Fibre Channel headers for all communication between the end devices. The sections of the Fibre Channel frame headers that are modified include:
•
•
•
When a frame goes from the initiator to the target, the Fibre Channel frame header is modified such that the initiator VSAN number is changed to the target VSAN number. If IVR Network Address Translation (NAT) is enabled, then the source and destination FCIDs are also translated at the edge border switch. If IVR NAT is not enabled, then you must configure unique domain IDs for all switches involved in the IVR path.
IVR NAT
Without Network Address Translation (NAT), IVR requires unique domain IDs for all switches in the fabric. You can enable IVR NAT to allow non-unique domain IDs. This feature simplifies the deployment of IVR in an existing fabric where non-unique domain IDs might be present.
To use IVR NAT, it must be enabled in all IVR-enabled switches in the fabric IVR configuration distribution (see the "Distributing the IVR Configuration using CFS" section). By default, IVR NAT and IVR configuration distribution are disabled in all switches in the Cisco MDS 9000 Family.
IVR NAT Requirements and Guidelines
Following are requirements and guidelines for using IVR NAT:
•
•
•
•
IVR NAT allows you to set up IVR in a fabric without needing unique domain IDs on every switch in the IVR path. IVR NAT virtualizes the switches in other VSANs by using local VSAN for the destination IDs in the Fibre Channel headers. In some Extended Link Service message types, the destinations IDs are part of the payload. In these cases, IVR NAT replaces the actual destination ID with the virtualized destination ID. IVR NAT supports destination ID replacement in the Extended Link Service messages described in Table 23-2.
If you have a message that is not recognized by IVR NAT and contains the destination ID in the payload, you cannot use IVR with NAT in your topology. You can still use IVR with unique domain IDs.
IVR VSAN Topology
IVR uses a configured IVR VSAN topology to determine how to route traffic between the initiator and the target across the fabric. You can configure this IVR VSAN topology manually on an IVR-enabled switch and distribute the configuration using CFS in Cisco MDS SAN-OS Release 2.0(1b) or later. Alternately, in Cisco MDS SAN-OS Release 2.1(1a) or later, you can configure IVR topology in auto mode. Prior to Cisco MDS SAN-OS Release 2.0(1b), you need to manually copy the IVR VSAN topology to each switch in the fabric.
Auto mode automatically builds the IVR VSAN topology and maintains the topology database when fabric reconfigurations occur. Auto mode distributes the IVR VSAN topology to IVR-enabled switches using CFS.
Using auto mode, you no longer need to manually update the IVR VSAN topology when reconfigurations occur in your fabric. If a manually configured IVR topology database exists, auto mode initially uses that topology information. This reduces disruption in the network by gradually migrating from the user-specified topology database to the automatically learned topology database. User configured topology entries that are not part of the network are aged out in about three minutes. New entries that are not part of the user configured database are added as they are discovered in the network.
When auto IVR topology is turned on it starts with the previously active, if any, manual IVR topology. Auto topology then commences its discovery process, and may come up with new, alternate or better paths. If the traffic is switched to an alternate or better path, there may be temporary traffic disruptions that are normally associated with switching paths.
Note
Autonomous Fabric ID
The autonomous fabric ID (AFID) distinguishes segmented VSANS (that is, two VSANs that are logically and physically separate but have the same VSAN number). Cisco MDS SAN-OS supports AFIDs from 1 through 64. AFIDs are used in conjunction with auto mode to allow segmented VSANS in the IVR VSAN topology database. You can configure up to 64 AFIDs.
The AFID can be configured individually for each switch and list of VSANs, or the default AFID can be configured for each switch.
Note
IVR Service Groups
IVR service groups have the following characteristics:
•
•
•
•
•
•
•
•
•
•
•
Default Service Group
All AFID/VSAN combinations that are part of 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. The default policy is not part of ASCII configuration.
Service Group Activation
A configured service group must be activated for it take effect. Like zoneset activation or VSAN topology activation, the activation of a configured service group replaces the currently activate 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.
IVR Interoperability
When using the IVR feature, all border switches in a given fabric must be Cisco MDS switches. However, other switches in the fabric may be non-MDS switches. For example, end devices that are members of the active IVR zone set may be connected to non-MDS switches. Non-MDS switches may also be present in the transit VSAN(s) or in the edge VSANs if one of the interop modes is enabled.
See the "Switch Interoperability" section on page 30-12.
IVR Configuration Task List
To configure IVR in a SAN fabric, follow these steps:
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Configuring IVR
This section describe how to configure IVR and contains the following sections:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Enabling IVR
The IVR feature must be enabled in all border switches in the fabric that participate in the IVR. By default, this feature is disabled in all switches in the Cisco MDS 9000 Family. You can manually enable IVR on all required switches in the fabric or configure fabric-wide distribution of the IVR configuration ("Distributing the IVR Configuration using CFS" section).
Note
To enable IVR on any participating switch, follow these steps:
Step 1
switch# config t
Enters configuration mode.
Step 2
switch(config)# ivr enable
Enables IVR on the switch.
switch(config)# no ivr enable
Disables (default) IVR on the switch.
Distributing the IVR Configuration using CFS
The IVR feature uses the Cisco Fabric Services (CFS) infrastructure to enable efficient configuration management and to provide a single point of configuration for the entire fabric in the VSAN (see Chapter 7, "Using the CFS Infrastructure").
The following configurations are distributed:
•
•
•
•
•
•
Note
This section includes the following topics:
•
Database Implementation
The IVR feature uses three databases to accept and implement configurations.
•
•
•
Enabling Configuration Distribution
To enable IVR configuration distribution, follow these steps:
Locking the Fabric
The first action that modifies the database creates the pending database and locks the feature in the VSAN. Once you lock the fabric, the following situations apply:
•
•
Committing the Changes
If you commit the changes made to the active database, the configuration is committed to all the switches in the fabric. On a successful commit, the configuration change is applied throughout the fabric and the lock is released.
To commit IVR configuration changes, follow these steps:
Step 1
switch# config t
switch(config)#
Enters configuration mode.
Step 2
switch(config)# ivr commit
Commits the IVR changes.
Discarding the Changes
If you discard (abort) the changes made to the pending database, the configuration database remains unaffected and the lock is released.
To discard IVR configuration changes, follow these steps:
Step 1
switch# config t
switch(config)#
Enters configuration mode.
Step 2
switch(config)# ivr abort
Discards the IVR changes and clears the pending configuration database.
Clearing a Locked Session
If you have performed an IVR task and have forgotten to release the lock by either committing or discarding the changes, an administrator can release the lock from any switch in the fabric. If the administrator performs this task, your changes to the pending database are discarded and the fabric lock is released.
Tip
To use administrative privileges and release a locked IVR session, use the clear ivr session command in EXEC mode.
switch# clear ivr sessionAbout IVR NAT and Auto Topology
Before configuring an IVR SAN fabric to use IVR NAT and auto-topology, consider the following guidelines:
•
•
•
•
Note
Tip
Note
Transit VSAN Guidelines
Consider the following guidelines for transit VSANs:
•
–
–
•
•
Border Switch Guidelines
Before configuring border switches, consider the following guidelines:
•
•
•
•
The VSAN topology configuration updates automatically when a border switch is added or removed.
Service Group Guidelines
If you use service groups with IVR auto topology, you should enable IVR and configure your service groups first, then distribute them with CFS before setting the IVR topology in auto mode.
Configuring IVR Topology Automatic Mode
Note
To configure IVR topology automatic mode, follow these steps:
View automatically discovered IVR topology using the show ivr vsan-topology command.
switch# show ivr vsan-topologyAFID SWITCH WWN Active Cfg. VSANS--------------------------------------------------------------1 20:00:00:05:30:01:1b:c2 * yes yes 1-21 20:02:00:44:22:00:4a:05 yes yes 1-2,61 20:02:00:44:22:00:4a:07 yes yes 2-5Total: 3 entries in active and configured IVR VSAN-TopologyCurrent Status: Inter-VSAN topology is AUTOLast activation time: Mon Mar 24 07:19:53 1980
Note
Enabling IVR NAT
To configure IVR NAT, follow these steps:
Step 1
switch# config t
Enters configuration mode.
Step 2
switch(config)# ivr nat
Enables IVR NAT on the switch.
switch(config)# no ivr nat
Disables (default) IVR NAT on the switch.
About IVR Service Groups
In a complex network topology, you might have only 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.
CFS distribution of IVR information is restricted within the service group only when IVR VSAN topology is in automatic mode. See the "IVR VSAN Topology" section
Configuring IVR Service Groups
To configure an IVR service group, follow these steps:
Copying the Active IVR Service Group Database
You cannot modify the active IVR service group database. However, you can modify the configured IVR service group database. To copy the active IVR service group database to the manually configure service group database, use the following command in EXEC mode:
switch# ivr copy active-service-group user-configured-service-groupClearing IVR Service Group Database
You can clear all entries in the IVR service group database using the clear ivr service-group database command in EXEC mode. This command only clears the configured database, not the active database.
switch# clear ivr service-group databaseVerifying IVR Service Group Configuration
Use the show ivr service-group active command to view the active IVR service group database.
switch# show ivr service-group activeIVR ACTIVE Service Group====================================SG-ID SG-NAME AFID VSANS------------------------------------------------------------------------------1 IVR-SG1 10 1-2,6-101 IVR-SG1 11 12 IVR-SG2 20 3-5Total: 3 entries in active service group tableUse the show ivr service-group configured command to view the configured IVR service group database.
switch# show ivr service-group configuredIVR CONFIGURED Service Group====================================SG-ID SG-NAME AFID VSANS------------------------------------------------------------------------------1 IVR-SG1 10 1-2,6-101 IVR-SG1 11 12 IVR-SG2 20 3-5Total: 3 entries in configured service group tableAbout AFIDs
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. IVR supports a maximum of 64 AFIDs.
Note
Configuring Default AFIDs
To configure the default AFID, follow these steps:
Configuring Individual AFIDs
To configure individual AFIDs, follow these steps:
Verifying the AFID Database Configuration
View the contents of the AFID database using the show autonomous-fabric-id database command.
switch# show autonomous-fabric-id databaseSWITCH WWN Default-AFID--------------------------------------------------------------20:00:00:0c:91:90:3e:80 5Total: 1 entry in default AFID tableSWITCH WWN AFID VSANS--------------------------------------------------------------20:00:00:0c:91:90:3e:80 10 1,2,5-8Total: 1 entry in AFID tableAbout IVR Without IVR NAT or Auto Topology
Before configuring an IVR SAN fabric without IVR in NAT mode or IVR topology in auto mode, consider the following guidelines:
•
–
–
•
•
Tip
Note
Domain ID Guidelines
Domain IDs must be unique across inter-connected VSANs when not using IVR NAT. To ensure unique domain IDs across inter-connected VSANs, consider these guidelines:
•
•
You can configure domain IDs using one of two options:
•
•
Note
Transit VSAN Guidelines
Before configuring transit VSANS, consider the following guidelines:
•
–
–
•
•
Border Switch Guidelines
Before configuring border switches, consider the following guidelines:
•
•
•
•
•
Configuring IVR Without NAT
You must create the IVR topology in every IVR-enabled switch in the fabric if you have not configured IVR topology in auto mode. You can have up to 128 VSANs in an IVR topology. Specify the IVR topology using the following information:
•
•
•
Figure 23-2 Example IVR Topology with Non-Unique VSAN IDs Using AFIDs
Note
Note
Caution
Manually Configuring the IVR Topology
Use the show wwn switch command to obtain the switch WWNs of the IVR-enabled switches.
To configure a user-defined IVR topology database, follow these steps:
View your configured IVR topology using the show ivr vsan-topology command. In the following example output, VSAN 2 is the transit VSAN between VSANs 1, 5, and 6.
switch# show ivr vsan-topologyAFID SWITCH WWN Active Cfg. VSANS--------------------------------------------------------------1 20:00:00:05:30:01:1b:c2 * no yes 1-21 20:02:00:44:22:00:4a:05 no yes 1-2,61 20:02:00:44:22:00:4a:07 no yes 2-5Total: 3 entries in active and configured IVR VSAN-TopologyCurrent Status: Inter-VSAN topology is INACTIVE
Note
Tip
Activating a Manually Configured IVR Topology
After manually configuring the IVR topology database, you must activate it.
Caution
To activate the manually configured IVR topology database, follow these steps:
Step 1
switch# config t
switch(config)#
Enters configuration mode.
Step 2
switch(config)# ivr vsan-topology activate
Activates the configured IVR topology.
View your active IVR topology using the show ivr vsan-topology command.
switch# show ivr vsan-topologyAFID SWITCH WWN Active Cfg. VSANS--------------------------------------------------------------1 20:00:00:05:30:01:1b:c2 * yes yes 1-21 20:02:00:44:22:00:4a:05 yes yes 1-2,61 20:02:00:44:22:00:4a:07 yes yes 2-5Total: 3 entries in active and configured IVR VSAN-TopologyCurrent Status: Inter-VSAN topology is ACTIVELast activation time: Mon Mar 24 07:19:53 1980
Note
Adding an IVR-Enabled Switch to an Existing IVR Topology
Before adding an IVR-enabled switch to an existing fabric with manual IVR topology and CFS distribution enabled (see the "Distributing the IVR Configuration using CFS" section), you must add an entry to the IVR topology for the new switch and activate the new IVR topology.
To add the IVR-enabled switch to the existing IVR topology on the IVR-enabled switch where you update the IVR configuration, follow these steps:
After adding the switch to the IVR topology, you then enable IVR and CFS for the IVR application on the new switch (see the"Enabling IVR" section and the "Distributing the IVR Configuration using CFS" section).
Adding VSANs to an Existing IVR Topology
To add VSANs to an existing IVR topology you need to specify all VSANs in the command syntax.
The following are the example that shows an IVR configuration with VSANs 1101-1102 and VSANs 2101-2102.
switch(config)# ivr enableswitch(config)# ivr distributeswitch(config)# ivr vsan-topology databaseswitch(config-ivr-topology-db)# autonomous-fabric-id 1 switch-wwn20:00:00:0d:ec:4a:5e:00 vsan-ranges 1101-1102,1199,3100,3150switch(config-ivr-topology-db)# autonomous-fabric-id 1 switch-wwn20:00:00:0d:ec:4a:5f:00 vsan-ranges 2101-2102,2199,3100,3150switch(config)# ivr vsan-topology activateThe following are the example that shows the addition of VSANs 1103 and 2103 to the IVR topology.
switch(config)# ivr enableswitch(config)# ivr distributeswitch(config)# ivr vsan-topology databaseswitch(config-ivr-topology-db)# autonomous-fabric-id 1 switch-wwn20:00:00:0d:ec:4a:5e:00 vsan-ranges 1101-1103,1199,3100,3150switch(config-ivr-topology-db)# autonomous-fabric-id 1 switch-wwn20:00:00:0d:ec:4a:5f:00 vsan-ranges 2101-2103,2199,3100,3150switch(config)# ivr vsan-topology activateCopying the Active IVR Topology
You cannot edit the active IVR topology. However, you can edit the manually configured topology. To copy the active IVR topology database to the manually configure topology, use the following command in EXEC mode:
switch# ivr copy active-topology user-configured-topologyClearing the Configured IVR Topology Database
You can only clear manually created IVR VSAN topology entries from the configured database.
To clear the manually configured IVR VSAN topology database, follow these steps:
Step 1
switch# config t
switch(config)#
Enters configuration mode.
Step 2
switch(config)# no ivr vsan-topology database
Clears the previously created IVR topology.
Verifying the IVR Topology
You can verify the IVR topology by using the show ivr vsan-topology command. See Example 23-1 to Example 23-3.
Example 23-1 Displays the Configured IVR VSAN Topology
switch# show ivr vsan-topologyAFID SWITCH WWN Active Cfg. VSANS--------------------------------------------------------------1 20:00:00:05:30:01:1b:c2 * yes yes 1-21 20:02:00:44:22:00:4a:05 yes yes 1-2,61 20:02:00:44:22:00:4a:07 yes yes 2-5Total: 5 entries in active and configured IVR VSAN-TopologyCurrent Status: Inter-VSAN topology is ACTIVELast activation time: Sat Mar 22 21:46:15 1980
Note
Example 23-2 Displays the Active IVR VSAN Topology
switch# show ivr vsan-topology activeAFID SWITCH WWN Active Cfg. VSANS--------------------------------------------------------------1 20:00:00:05:30:01:1b:c2 * yes yes 1-21 20:02:00:44:22:00:4a:05 yes yes 1-2,61 20:02:00:44:22:00:4a:07 yes yes 2-5Total: 5 entries in active IVR VSAN-TopologyCurrent Status: Inter-VSAN topology is ACTIVELast activation time: Sat Mar 22 21:46:15Example 23-3 Displays the Configured IVR VSAN Topology
switch# show ivr vsan-topology configuredAFID SWITCH WWN Active Cfg. VSANS--------------------------------------------------------------1 20:00:00:05:30:01:1b:c2 * yes yes 1-21 20:02:00:44:22:00:4a:05 yes yes 1-2,61 20:02:00:44:22:00:4a:07 yes yes 2-5Total: 5 entries in configured IVR VSAN-TopologyMigrating from IVR Auto Topology Mode to Manual Mode
If you want to migrate the active IVR VSAN topology database from automatic mode to user-configured mode, first copy the active IVR VSAN topology database to the user-configured IVR VSAN topology database before switching modes.
To migrate from automatic mode to manual mode, follow these steps:
About IVR Virtual Domains
In a remote VSAN, the IVR application does not automatically add the virtual domain to the assigned domains list. Some switches (for example, the Cisco SN5428) do not query the remote name server until the remote domain appears in the assigned domains list in the fabric. In such cases, add the IVR virtual domains in a specific VSAN(s) to the assigned domains list in that VSAN. When adding IVR domains, all IVR virtual domains that are currently present in the fabric (and any virtual domain that is created in the future) will appear in the assigned domain list for that VSAN.
Tip
When you enable the IVR virtual domains, links may fail to come up due to overlapping virtual domain identifiers. If so, temporarily withdraw the overlapping virtual domain from that VSAN.
Note
Use the ivr withdraw domain command in EXEC mode to temporarily withdraw the overlapping virtual domain interfaces from the affected VSAN.
Tip
Configuring IVR Virtual Domains
To configure an IVR virtual domain in a specified VSAN, follow these steps:
Note
Verifying the IVR Virtual Domain Configuration
View the status of the IVR virtual domain configuration using the show ivr virtual-fcdomain-add-status command.
switch# show ivr virtual-fcdomain-add-statusIVR virtual domains are added to fcdomain list in VSANS: 1(As well as to VSANs in interoperability mode 2 or 3)Clearing the IVR fcdomain Database
You might want to clear the IVR fcdomain database. You can do this using the following command:
switch# clear ivr fcdomain databaseAbout Persistent FC IDs for IVR
You can configure persistent FC IDs for IVR. FC ID persistence across reboot improves IVR management by providing the following features:
•
•
The benefits of persistent FC IDs for IVR are as follows:
•
•
•
You can configure two types of database entries for persistent IVR FC IDs:
•
–
–
–
–
–
•
–
–
–
–
Note
Note
Note
Configuring Persistent FC IDs for IVR
To configure persistent FC IDs for IVR, follow these steps:
Verifying the Persistent FC ID Configuration
Verify the persistent FC ID configuration using the show ivr fcdomain database command. See Example 23-4 and Example 23-5
Example 23-4 Displays All IVR fcdomain Database Entries
switch# show ivr fcdomain database----------------------------------------------------AFID Vsan Native-AFID Native-Vsan Virtual-domain----------------------------------------------------1 2 10 11 0xc(12)21 22 20 11 0xc(12)Number of Virtual-domain entries: 2----------------------------------------------------AFID Vsan Pwwn Virtual-fcid----------------------------------------------------21 22 11:22:33:44:55:66:77:88 0x11446621 22 21:22:33:44:55:66:77:88 0x0c446621 22 21:22:33:44:55:66:78:88 0x0c4466Number of Virtual-fcid entries: 3Example 23-5 Displays the IVR fcdomain Database Entries for a Specific AFID and VSAN
switch# show ivr fcdomain database autonomous-fabric-num 21 vsan 22----------------------------------------------------AFID Vsan Native-AFID Native-Vsan Virtual-domain----------------------------------------------------21 22 20 11 0xc(12)Number of Virtual-domain entries: 1----------------------------------------------------AFID Vsan Pwwn Virtual-fcid----------------------------------------------------21 22 11:22:33:44:55:66:77:88 0x11446621 22 21:22:33:44:55:66:77:88 0x0c446621 22 21:22:33:44:55:66:78:88 0x0c4466Number of Virtual-fcid entries: 3Configuring IVR Logging Levels
To configure the severity level for logging messages from the IVR feature, follow these steps:
Verifying Logging Level Configuration
Use the show logging level command to view the configured logging level for the IVR feature.
switch# show logging levelFacility Default Severity Current Session Severity-------- ---------------- ------------------------...ivr 5 4...0(emergencies) 1(alerts) 2(critical)3(errors) 4(warnings) 5(notifications)6(information) 7(debugging)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 result, you must specify each IVR zone as a set of (pWWN, VSAN) entries. Like zones, several IVR zone sets can be configured to belong to an IVR zone. You can define several IVR zone sets and activate only one of the defined IVR zone sets.
Note
Caution
This section describes configuring IVR zones and IVR zone sets and includes the following topics:
•
•
•
•
•
•
•
•
•
•
•
About IVR Zones
Table 23-3 identifies the key differences between IVR zones and zones.
Automatic IVR Zone Creation
Figure 23-3 depicts an IVR zone consisting of four members. To allow pwwn1 to communicate with pwwn2, they must be in the same zone in VSAN 1, as well as in VSAN 2. If they are not in the same zone, then the hard-zoning ACL entries will prohibit pwwn1 from communicating with pwwn2.
A zone corresponding to each active IVR zone is automatically created in each edge VSAN specified in the active IVR zone. All pWWNs in the IVR zone are members of these zones in each VSAN.
Figure 23-3 Creating Zones Upon IVR Zone Activation
The zones are created automatically by the IVR process when an IVR zone set is activated. They are not stored in a full zone set database and are lost when the switch reboots or when a new zone set is activated. The IVR feature monitors these events and adds the zones corresponding to the active IVR zone set configuration when a new zone set is activated. Like zone sets, IVR zone sets are also activated nondisruptively.
Note
IVR zone and IVR zone set names are restricted to 64 alphanumeric characters.
Caution
Configuring IVR Zones and IVR Zone Sets
To create IVR zones and IVR zone sets, follow these steps:
About Activating Zone Sets and Using the force Option
Once the zone sets have been created and populated, you must activate the zone set. When you activate an IVR zone set, IVR automatically adds an IVR zone to the regular active zone set of each edge VSAN. If a VSAN does not have an active zone set, IVR can only activate an IVR zone set using the force option, which causes IVR to create an active zone set called "nozoneset" and adds the IVR zone to that active zone set.
Caution
Note
You can also use the force option to activate IVR zone sets. Table 23-4 lists the various scenarios with and without the force option.
Table 23-4 IVR Scenarios with and without theforce Option.
1
Deny
No active zone set
No
Failure
No
No
2
Yes
Success
Yes
No
31
Deny
Active zone set present
No/Yes
Success
Yes
No
4
Permit
No active zone set
or
Active zone set presentNo
Failure
No
No
5
Yes
Success
Yes
Yes
1 We recommend that you use the Case 3 scenario.
Caution
Activating or Deactivating IVR Zone Sets
To activate or deactivate an existing IVR zone set, follow these steps:
Note
Verifying IVR Zone and IVR Zone Set Configuration
Verify the IVR zone and IVR zone set configurations using the show ivr zone and show ivr zoneset commands. See Example 23-6 to Example 23-14.
Example 23-6 Displays the IVR Zone Configuration
switch# show ivr zonezone name sample_vsan2-3pwwn 21:00:00:e0:8b:02:ca:4a vsan 3pwwn 21:00:00:20:37:c8:5c:6b vsan 2zone name ivr_qa_z_allpwwn 21:00:00:e0:8b:06:d9:1d vsan 1pwwn 21:01:00:e0:8b:2e:80:93 vsan 4pwwn 10:00:00:00:c9:2d:5a:dd vsan 1pwwn 10:00:00:00:c9:2d:5a:de vsan 2pwwn 21:00:00:20:37:5b:ce:af vsan 6pwwn 21:00:00:20:37:39:6b:dd vsan 6pwwn 22:00:00:20:37:39:6b:dd vsan 3pwwn 22:00:00:20:37:5b:ce:af vsan 3pwwn 50:06:04:82:bc:01:c3:84 vsan 5Example 23-7 Displays Information for a Specified IVR Zone
switch# show ivr zone name sample_vsan2-3zone name sample_vsan2-3pwwn 21:00:00:e0:8b:02:ca:4a vsan 3pwwn 21:00:00:20:37:c8:5c:6b vsan 2Example 23-8 Displays the Specified Zone in the Active IVR Zone
switch# show ivr zone name sample_vsan2-3 activezone name sample_vsan2-3pwwn 21:00:00:e0:8b:02:ca:4a vsan 3pwwn 21:00:00:20:37:c8:5c:6b vsan 2Example 23-9 Displays the IVR Zone Set Configuration
switch# show ivr zonesetzoneset name ivr_qa_zs_allzone name ivr_qa_z_allpwwn 21:00:00:e0:8b:06:d9:1d vsan 1pwwn 21:01:00:e0:8b:2e:80:93 vsan 4pwwn 10:00:00:00:c9:2d:5a:dd vsan 1pwwn 10:00:00:00:c9:2d:5a:de vsan 2pwwn 21:00:00:20:37:5b:ce:af vsan 6pwwn 21:00:00:20:37:39:6b:dd vsan 6pwwn 22:00:00:20:37:39:6b:dd vsan 3pwwn 22:00:00:20:37:5b:ce:af vsan 3pwwn 50:06:04:82:bc:01:c3:84 vsan 5zoneset name IVR_ZoneSet1zone name sample_vsan2-3pwwn 21:00:00:e0:8b:02:ca:4a vsan 3pwwn 21:00:00:20:37:c8:5c:6b vsan 2Example 23-10 Displays the Active IVR Zone Set Configuration
switch# show ivr zoneset activezoneset name IVR_ZoneSet1zone name sample_vsan2-3pwwn 21:00:00:e0:8b:02:ca:4a vsan 3pwwn 21:00:00:20:37:c8:5c:6b vsan 2Example 23-11 Displays the Specified IVR Zone Set Configuration
switch# show ivr zoneset name IVR_ZoneSet1zoneset name IVR_ZoneSet1zone name sample_vsan2-3pwwn 21:00:00:e0:8b:02:ca:4a vsan 3pwwn 21:00:00:20:37:c8:5c:6b vsan 2Example 23-12 Displays Brief Information for All IVR Zone Sets
switch# show ivr zoneset brief Activezoneset name IVR_ZoneSet1zone name sample_vsan2-3Example 23-13 Displays Brief Information for the Active IVR Zone Set
switch# show ivr zoneset brief Activezoneset name IVR_ZoneSet1zone name sample_vsan2-3Example 23-14 Displays Status Information for the IVR Zone Set
switch# show ivr zoneset statusZoneset Status_______________name : IVR_ZoneSet1state : activation successlast activate time : Sat Mar 22 21:38:46 1980force option : offstatus per vsan:__________________vsan status____ ______1 active2 active
Tip
Note
About LUNs in IVR Zoning
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, see the "About LUN Zoning" section on page 24-21.
Configuring LUNs in IVR Zoning
To configure LUNs in IVR zoning, follow these steps:
Note
About QoS in IVR Zones
You can configure a QoS attribute for an IVR zone. The default QoS attribute setting is low.
Configuring the QoS Attribute
To configure the QoS attribute for an IVR zone, follow these steps:
Note
Verifying the QoS Attribute Configuration
Verify the QoS attribute configuration for an IVR zone using the show ivr zone command.
switch(config)# show ivr zonezone name IvrZoneattribute qos priority mediumRenaming IVR Zones and IVR Zone Sets
You can rename IVR zones and IVR zone sets.
To rename an IVR zone, use the ivr zone rename command in EXEC mode.
switch# ivr zone rename ivrzone1 ivrzone2To rename an IVR zone set, use the ivr zoneset rename command in EXEC mode.
switch# ivr zoneset rename ivrzone1 ivrzone2Clearing the IVR Zone Database
Clearing a zone set only erases the configured zone database, not the active zone database.
To clear the IVR zone database, use the clear ivr zone database command.
switch# clear ivr zone databaseThis command clears all configured IVR zone information.
Note
Configuring IVR Using Read-Only Zoning
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
System Image Downgrading Considerations
As of Cisco MDS SAN-OS Release 3.0(3), you can configure 8000 IVR zones and 20,000 IVR zone members. If you want to downgrade to a release prior to Cisco SAN-OS Release 3.0(3), the number of IVR zones cannot exceed 2000 and the number of IVR zone members cannot exceed 10,000.
Database Merge Guidelines
A database merge refers to a union of the configuration database and static (unlearned) entries in the active database. See the "CFS Merge Support" section on page 7-8 for detailed concepts.
•
–
–
Figure 23-4 Fabric Merge Consequences
•
•
–
–
–
–
–
Note
–
–
Note
–
Note
–
Table 23-5 describes the results of a CFS merge of two IVR-enabled fabrics under different conditions.
Caution
Resolving Database Merge Failures
If a merge failure occurs, use the following commands to display the error conditions:
•
•
•
Depending on the failure indicated in the show command outputs, you can perform the following:
•
•
•
After a successful CFS commit, the merge will be successful.
Example Configurations
This section provides IVR configurations examples and includes the following topics:
•
Manual Topology Configuration
This section provides the configuration steps to manually configure the example illustrated in Figure 23-1.
Step 1
mds# config tEnter configuration commands, one per line. End with CNTL/Z.mds(config)# ivr enablemds(config)# exitmds#Step 2
mds# show ivrInter-VSAN Routing is enabledInter-VSAN enabled switches---------------------------No IVR-enabled VSAN is active. Check VSAN-Topology configuration.Inter-VSAN topology status--------------------------Current Status: Inter-VSAN topology is INACTIVEInter-VSAN zoneset status-------------------------name :state : idlelast activate time :Fabric distribution status-----------------------fabric distribution disabledLast Action : NoneLast Action Result : NoneLast Action Failure Reason : NoneInter-VSAN NAT mode status--------------------------FCID-NAT is disabledLicense status-----------------IVR is running based on the following license(s)ENTERPRISE_PKGStep 3
mds# config tEnter configuration commands, one per line. End with CNTL/Z.mds(config)# ivr distributionStep 4
mds(config)# ivr vsan-topology databasemds(config-ivr-topology-db)# autonomous-fabric-id 1 switch-wwn 20:00:00:05:40:01:1b:c2 vsan-ranges 1,4mds(config-ivr-topology-db)# autonomous-fabric-id 1 switch-wwn 20:02:00:44:22:00:4a:08 vsan-ranges 1,4mds(config-ivr-topology-db)# autonomous-fabric-id 1 switch-wwn 20:00:00:44:22:02:8a:04 vsan-ranges 2-4mds(config-ivr-topology-db)# autonomous-fabric-id 1 switch-wwn 20:00:00:44:22:40:aa:16 vsan-ranges 2-4mds(config-ivr-topology-db)# exitmds(config)#Step 5
Note
mds(config)# do show ivr vsan-topologyAFID SWITCH WWN Active Cfg. VSANS--------------------------------------------------------------1 20:00:00:05:40:01:1b:c2 * no yes 1,41 20:00:00:44:22:00:4a:08 no yes 1,41 20:00:00:44:22:02:8a:04 no yes 2-41 20:00:00:44:22:40:aa:16 no yes 2-4Total: 4 entries in active and configured IVR VSAN-TopologyCurrent Status: Inter-VSAN topology is INACTIVEStep 6
mds(config)# ivr vsan-topology activateStep 7
mds(config)# do show ivr vsan-topologyAFID SWITCH WWN Active Cfg. VSANS--------------------------------------------------------------1 20:00:00:05:40:01:1b:c2 * yes yes 1,41 20:00:00:44:22:00:4a:08 yes yes 1,41 20:00:00:44:22:02:8a:04 yes yes 2-41 20:00:00:44:22:40:aa:16 yes yes 2-4Total: 4 entries in active and configured IVR VSAN-TopologyCurrent Status: Inter-VSAN topology is ACTIVELast activation time: Tue May 20 23:14:59 1980Step 8
•
•
Tip
mds(config)# ivr zoneset name tape_server1_server2mds(config-ivr-zoneset)# zone name tape_server1mds(config-ivr-zoneset-zone)# member pwwn 10:02:50:45:32:20:7a:52 vsan 1mds(config-ivr-zoneset-zone)# member pwwn 10:02:66:45:00:20:89:04 vsan 2mds(config-ivr-zoneset-zone)# exitmds(config-ivr-zoneset)# zone name tape_server2mds(config-ivr-zoneset-zone)# member pwwn 10:02:50:45:32:20:7a:52 vsan 1mds(config-ivr-zoneset-zone)# member pwwn 10:00:ad:51:78:33:f9:86 vsan 3mds(config-ivr-zoneset-zone)# exitStep 9
mds(config)# do show ivr zonesetzoneset name tape_server1_server2zone name tape_server1pwwn 10:02:50:45:32:20:7a:52 vsan 1pwwn 10:02:66:45:00:20:89:04 vsan 2zone name tape_server2pwwn 10:02:50:45:32:20:7a:52 vsan 1pwwn 10:00:ad:51:78:33:f9:86 vsan 3Step 10
mds(config)# do show zoneset active vsan 1zoneset name finance_dept vsan 1zone name accounts_database vsan 1pwwn 10:00:23:11:ed:f6:23:12pwwn 10:00:56:43:11:56:fe:eezone name $default_zone$ vsan 1Step 11
mds(config)# ivr zoneset activate name tape_server1_server2zoneset activation initiated. check inter-VSAN zoneset statusmds(config)# exitmds#Step 12
mds# show ivr zoneset activezoneset name tape_server1_server2zone name tape_server1pwwn 10:02:50:45:32:20:7a:52 vsan 1pwwn 10:02:66:45:00:20:89:04 vsan 2zone name tape_server2pwwn 10:02:50:45:32:20:7a:52 vsan 1pwwn 10:00:ad:51:78:33:f9:86 vsan 3Step 13
mds# show zoneset active vsan 1zoneset name finance_dept vsan 1zone name accounts_database vsan 1pwwn 10:00:23:11:ed:f6:23:12pwwn 10:00:56:43:11:56:fe:eezone name IVRZ_tape_server1 vsan 1pwwn 10:02:66:45:00:20:89:04pwwn 10:02:50:45:32:20:7a:52zone name IVRZ_tape_server2 vsan 1pwwn 10:02:50:45:32:20:7a:52pwwn 10:00:ad:51:78:33:f9:86zone name $default_zone$ vsan 1mds# show ivr zoneset statusZoneset Status______________name : tape_server1_server2state : activation successlast activate time : Tue May 20 23:23:01 1980force option : onstatus per vsan:__________________vsan status____ ______1 active
Auto-Topology Configuration
This section provides example configuration steps for configuring IVR auto-topology.
Step 1
switch# config tEnter configuration commands, one per line. End with CNTL/Z.switch(config)# ivr enableswitch(config)# exitswitch#Step 2
switch# show ivrInter-VSAN Routing is enabledInter-VSAN enabled switches---------------------------No IVR-enabled VSAN is active. Check VSAN-Topology configuration.Inter-VSAN topology status--------------------------Current Status: Inter-VSAN topology is INACTIVEInter-VSAN zoneset status-------------------------name :state : idlelast activate time :Fabric distribution status-----------------------fabric distribution disabledLast Action : NoneLast Action Result : NoneLast Action Failure Reason : NoneInter-VSAN NAT mode status--------------------------FCID-NAT is disabledLicense status-----------------IVR is running based on the following license(s)ENTERPRISE_PKGStep 3
switch# config tEnter configuration commands, one per line. End with CNTL/Z.switch(config)# ivr distributionStep 4
switch(config)# ivr vsan-topology autofabric is locked for configuration. Please commit after configuration is done.Step 5
switch(config)# ivr commitswitch(config)# exitswitch#Step 6
switch# show ivr session statusLast Action : CommitLast Action Result : SuccessLast Action Failure Reason : NoneStep 7
switch# show ivr vsan-topology activeAFID SWITCH WWN Active Cfg. VSANS--------------------------------------------------------------1 20:00:00:0d:ec:08:6e:40 * yes no 1,336-3381 20:00:00:0d:ec:0c:99:40 yes no 336,339
Default Settings
Table 23-6 lists the default settings for IVR parameters.
Table 23-6 Default IVR Parameters
IVR feature
Disabled.
IVR VSANs
Not added to virtual domains.
IVR NAT
Disabled.
QoS for IVR zones
Low.
Configuration distribution
Disabled.
