-
Cisco MDS 9000 Family Fabric Manager Configuration Guide, Release 3.x
-
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 and Managing Zones
-
Configuring Fibre Channel Routing Services and Protocols
-
Dense Wavelength Division Multiplexing
-
Managing FLOGI, Name Server, FDMI, and RSCN Databases
-
Discovering SCSI Targets
-
Configuring FICON
-
Advanced Features and Concepts
-
-
Security
-
Configuring FIPS
-
Configuring Users and Common Roles
-
Configuring SNMP
-
Configuring RADIUS and TACACS+
-
Configuring IPv4 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
-
Launching Fabric Manager in Cisco SAN-OS Releases Prior to 3.2(1)
-
Cisco Fabric Manager Unsupported Feature List
-
Interface Nonoperational Reason Codes
-
Managing Cisco FabricWare
-
Configuration Limits for Cisco MDS SAN-OS Release 3.1(x) and 3.2(x)
-
Feedback
Table Of Contents
Enabling or Disabling fcdomains
About Autoreconfiguring Merged Fabrics
Specifying Static or Preferred Domain IDs
Configuring Allowed Domain ID Lists
About CFS Distribution of Allowed Domain ID Lists
About Contiguous Domain ID Assignments
Enabling Contiguous Domain ID Assignments
Enabling the Persistent FC ID Feature
About Persistent FC ID Configuration
About Unique Area FC IDs for HBAs
Configuring Unique Area FC IDs for an HBA
About Persistent FC ID Selective Purging
Displaying fcdomain Statistics
Configuring Domain Parameters
The Fibre Channel domain (fcdomain) feature performs principal switch selection, domain ID distribution, FC ID allocation, and fabric reconfiguration functions as described in the FC-SW-2 standards. The domains are configured on a per VSAN basis. If you do not configure a domain ID, the local switch uses a random ID.
CautionChanges to fcdomain parameters should not be performed on a daily basis. These changes should be made by an administrator or individual who is completely familiar with switch operations.
Tip
This chapter includes the following sections:
•
Fibre Channel Domains
This section describes each fcdomain phase:
•
•
•
•
See Figure 25-1.
Figure 25-1 Sample fcdomain Configuration
Note
This section describes the fcdomain feature and includes the following topics:
•
•
About Domain Restart
Fibre Channel domains can be started disruptively or nondisruptively. If you perform a disruptive restart, reconfigure fabric (RCF) frames are sent to other switches in the fabric and data traffic is disrupted on all the switches in the VSAN (including remotely segmented ISLs). If you perform a nondisruptive restart, build fabric (BF) frames are sent to other switches in the fabric and data traffic is disrupted only on the switch.
If you are attempting to resolve a domain ID conflict, you must manually assign domain IDs. A disruptive restart is required to apply most configuration changes-including manually assigned domain IDs. Non-disruptive domain restarts are acceptable only when changing a preferred domain ID into a static one (and the actual domain ID remains the same).
Note
Tip
You can apply most of the configurations to their corresponding runtime values. Each of the following sections provide further details on how the fcdomain parameters are applied to the runtime values.
Restarting a Domain
To restart the fabric disruptively or nondisruptively using Fabric Manager, follow these steps:
Step 1
You see the Running tab configuration of the domain in the Information pane.
Figure 25-2 Running Domain Configuration
Step 2
You see the switch configuration shown in Figure 25-3.
Figure 25-3 Configuring Domains
Step 3
Step 4
About Switch Priority
By default, the configured priority is 128. The valid range to set the priority is between 1 and 254. Priority 1 has the highest priority. Value 255 is accepted from other switches, but cannot be locally configured.
Any new switch can become the principal switch when it joins a stable fabric. During the principal switch selection phase, the switch with the highest priority becomes the principal switch. If two switches have the same configured priority, the switch with the lower WWN becomes the principal switch.
The priority configuration is applied to runtime when the fcdomain is restarted (see the "About Domain Restart" section). This configuration is applicable to both disruptive and nondisruptive restarts.
Configuring Switch Priority
To configure the priority for the principal switch using Fabric Manager, follow these steps:
Step 1
You see the domain's running configuration in the Information pane shown in Figure 25-4.
Figure 25-4 Running Domain Configuration
Step 2
Step 3
About fcdomain Initiation
By default, the fcdomain feature is enabled on each switch. If you disable the fcdomain feature in a switch, that switch can no longer participate with other switches in the fabric. The fcdomain configuration is applied to runtime through a disruptive restart.
Enabling or Disabling fcdomains
To disable fcdomains in a single VSAN or a range of VSANs using Fabric Manager, follow these steps:
Step 1
You see the domain's running configuration in the Information pane.
Step 2
Figure 25-5 Configuring Domains
Step 3
Setting Fabric Names
To set the fabric name value for a disabled fcdomain using Fabric Manager, follow these steps:
Step 1
You see the running configuration of the domain in the Information pane.
Step 2
Step 3
About Incoming RCFs
You can choose to reject RCF request frames on a per-interface, per-VSAN basis. By default, the RCF reject option is disabled (that is, RCF request frames are not automatically rejected).
The RCF reject option takes immediate effect to runtime through a disruptive restart (see the "About Domain Restart" section).
Rejecting Incoming RCFs
To reject incoming RCF request frames using Fabric Manager, follow these steps:
Step 1
You see the Fibre Channel configuration in the Information pane.
Step 2
You see the information in Figure 25-6.
Figure 25-6 Rejecting Incoming RCF Request Frames
Step 3
Step 4
About Autoreconfiguring Merged Fabrics
By default, the autoreconfigure option is disabled. When you join two switches belonging to two different stable fabrics that have overlapping domains, the following cases apply:
•
•
The autoreconfigure option takes immediate effect at runtime. You do not need to restart the fcdomain. If a domain is currently isolated due to domain overlap, and you later enable the autoreconfigure option on both switches, the fabric continues to be isolated. If you enabled the autoreconfigure option on both switches before connecting the fabric, a disruptive reconfiguration (RCF) will occur. A disruptive reconfiguration may affect data traffic. You can nondisruptively reconfigure the fcdomain by changing the configured domains on the overlapping links and getting rid of the domain overlap.
Enabling Autoreconfiguration
To enable automatic reconfiguration in a specific VSAN (or range of VSANs) using Fabric Manager, follow these steps:
Step 1
You see the running configuration of the domain in the Information pane.
Step 2
Step 3
Domain IDs
Domain IDs uniquely identify a switch in a VSAN. A switch may have different domain IDs in different VSANs. The domain ID is part of the overall FC ID.
This section describes how to configure domain IDs and includes the following topics:
•
•
•
•
•
•
About Domain IDs
The configured domain ID can be preferred or static. By default, the configured domain ID is 0 (zero) and the configured type is preferred.
Note
If you do not configure a domain ID, the local switch sends a random ID in its request. We recommend that you use static domain IDs.
When a subordinate switch requests a domain, the following process takes place (see Figure 25-7):
1.
2.
Figure 25-7 Configuration Process Using the preferred Option
The behavior for a subordinate switch changes based on three factors:
•
•
•
In specific situations, the changes are as follows:
•
•
•
–
–
If you change the configured domain ID, the change is only accepted if the new domain ID is included in all the allowed domain ID lists currently configured in the VSAN. Alternatively, you can also configure zero-preferred domain ID.
Tip
Note
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.
Caution
Note
Specifying Static or Preferred Domain IDs
When you assign a static domain ID type, you are requesting a particular domain ID. If the switch does not get the requested address, it will isolate itself from the fabric. When you specify a preferred domain ID, you are also requesting a particular domain ID; however, if the requested domain ID is unavailable, then the switch will accept another domain ID.
While the static option can be applied at runtime after a disruptive or non-disruptive restart, the preferred option is applied at runtime only after a disruptive restart (see the "About Domain Restart" section).
Note
To specify a static or preferred domain ID using Fabric Manager, follow these steps:
Step 1
You see the running configuration of the domain in the Information pane.
Step 2
Step 3
About Allowed Domain ID Lists
By default, the valid range for an assigned domain ID list is from 1 to 239. You can specify a list of ranges to be in the allowed domain ID list and separate each range with a comma. The principal switch assigns domain IDs that are available in the locally configured allowed domain list.
Use allowed domain ID lists to design your VSANs with non-overlapping domain IDs. This helps you in the future if you need to implement IVR without the NAT feature.
Tip
An allowed domain ID list must satisfy the following conditions:
•
•
•
•
Configuring Allowed Domain ID Lists
To configure the allowed domain ID list using Fabric Manager, follow these steps:
Step 1
You see the CFS configuration in the Information pane (see Figure 25-8).
Figure 25-8 Allowed CFS Configuration Information
Step 2
Step 3
Step 4
You see the Allowed Domain ID screen shown in Figure 25-9.
Figure 25-9 Allowed Domain ID List
Step 5
Step 6
Step 7
About CFS Distribution of Allowed Domain ID Lists
You can enable the distribution of the allowed domain ID list s configuration information to all Cisco MDS switches in the fabric using the Cisco Fabric Services (CFS) infrastructure. This feature allows you to synchronize the configuration across the fabric from the console of a single MDS switch. Since the same configuration is distributed to the entire VSAN, you avoid possible misconfiguration and the likelihood that two switches in the same VSAN have configured incompatible allowed domains.
Note
Use CFS to distribute the allowed domain ID list to ensure consistency in the allowed domain ID lists on all switches in the VSAN.
Note
For more information about CFS, see Chapter 13, "Using the CFS Infrastructure."
Enabling Distribution
CFS distribution of allowed domain ID lists is disabled by default. You must enable distribution on all switches to which you want to distribute the allowed domain ID lists.
To enable (or disable) allowed domain ID list configuration distribution using Fabric Manager, follow these steps:
Step 1
You see the CFS configuration in the Information pane.
Step 2
Step 3
Locking the Fabric
The first action that modifies the existing configuration creates the pending configuration and locks the feature in the fabric. Once you lock the fabric, the following conditions apply:
•
•
Committing Changes
To apply the pending domain configuration changes to other MDS switches in the VSAN, you must commit the changes. The pending configuration changes are distributed and, on a successful commit, the configuration changes are applied to the active configuration in the MDS switches throughout the VSAN and the fabric lock is released.
To commit pending domain configuration changes and release the lock using Fabric Manager, follow these steps:
Step 1
You see the CFS configuration in the Information pane.
Step 2
Step 3
Discarding Changes
At any time, you can discard the pending changes to the domain configuration and release the fabric lock. If you discard (abort) the pending changes, the configuration remains unaffected and the lock is released.
To discard pending domain configuration changes and release the lock using Fabric Manager, follow these steps:
Step 1
You see the CFS configuration in the Information pane.
Step 2
Step 3
Clearing a Fabric Lock
If you have performed a domain configuration task and have not released 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 pending changes are discarded and the fabric lock is released.
Tip
To release a fabric lock using Fabric Manager, follow these steps:
Step 1
You see the CFS configuration in the Information pane.
Step 2
Step 3
Displaying Pending Changes
To display the pending configuration changes using Fabric Manager, follow these steps:
Step 1
You see the CFS configuration in the Information pane.
Step 2
Step 3
Step 4
You see the pending configuration for the allowed domain IDs list.
Displaying Session Status
To display the status of the distribution session using Fabric Manager, follow these steps:
Step 1
Step 2
About Contiguous Domain ID Assignments
By default, the contiguous domain assignment is disabled. When a subordinate switch requests the principal switch for two or more domains and the domains are not contiguous, the following cases apply:
•
•
Enabling Contiguous Domain ID Assignments
To enable contiguous domains in a specific VSAN (or a range of VSANs) using Fabric Manager, follow these steps:
Step 1
You see the running configuration of the domain in the Information pane.
Step 2
Step 3
FC IDs
When an N or NL port logs into a Cisco MDS 9000 Family switch, it is assigned an FC ID. By default, the persistent FC ID feature is enabled. If this feature is disabled, the following consequences apply:
•
•
•
•
–
–
This section describes configuring FC IDs and includes the following topics:
•
•
•
•
•
•
About Persistent FC IDs
When persistent FC IDs are enabled, the following consequences apply:
•
•
Note
Note
A persistent FC ID assigned to an F port can be moved across interfaces and can continue to maintain the same persistent FC ID.
Note
Note
Enabling the Persistent FC ID Feature
To enable the persistent FC ID feature using Fabric Manager, follow these steps:
Step 1
You see the running configuration of the domain in the Information pane.
Step 2
Step 3
About Persistent FC ID Configuration
When the persistent FC ID feature is enabled, you can enter the persistent FC ID submode and add static or dynamic entries in the FC ID database. By default, all added entries are static. Persistent FC IDs are configured on a per-VSAN basis. Follow these requirements to manually configure a persistent FC ID:
•
•
•
•
Note
Configuring Persistent FC IDs
To configure persistent FC IDs using Fabric Manager, follow these steps:
Step 1
You see the running configuration of the domain in the Information pane.
Step 2
You see the Create Persistent FC IDs dialog box shown in Figure 25-10.
Figure 25-10 Create Persistent FC IDs Dialog Box
Step 3
Step 4
Step 5
Step 6
About Unique Area FC IDs for HBAs
Note
Some HBA ports require a different area ID than storage ports when they are both connected to the same switch. For example, if the storage port FC ID is 0x6f7704, the area for this port is 77. In this case, the HBA port's area can be anything other than 77. The HBA port's FC ID must be manually configured to be different from the storage port's FC ID.
Switches in the Cisco MDS 9000 Family facilitate this requirement with the FC ID persistence feature. You can use this feature to preassign an FC ID with a different area to either the storage port or the HBA port. The procedure in this example uses a switch domain of 111(6f hex). The HBA port connects to interface fc1/9 and the storage port connects to interface fc 1/10 in the same switch.
Configuring Unique Area FC IDs for an HBA
To configure a different area ID for the HBA port using Fabric Manager, follow these steps:
Step 1
Figure 25-11 FLOGI Database Information in Fabric Manager
Note
Step 2
Step 3
This shuts down the HBA interface in the MDS switch.
Step 4
Step 5
Figure 25-12 Persistent FC ID Information in Fabric Manager
If this feature is disabled, continue with this procedure to enable persistent FC ID.
If this feature is already enabled, skip to Step 7.
Step 6
Step 7
Figure 25-13 Setting the FC ID in Fabric Manager
Step 8
Step 9
Note
Step 10
Step 11
About Persistent FC ID Selective Purging
Persistent FC IDs can be purged selectively. Static entries and FC IDs currently in use cannot be deleted. Table 25-1 identifies the FC ID entries that are deleted or retained when persistent FC IDs are purged.
Table 25-1 Purged FC IDs
Static
In use
Not deleted
Static
Not in use
Not deleted
Dynamic
In use
Not deleted
Dynamic
Not in use
Deleted
Purging Persistent FC IDs
To purge persistent FC IDs using Fabric Manager, follow these steps:
Step 1
Step 2
You see the persistent FC ID setup in the Information pane shown in Figure 25-14.
Figure 25-14 Persistent FC ID Information in Fabric Manager
Step 3
Step 4
Displaying fcdomain Statistics
Fabric Manager collects statistics for fcdomain and displays them in the Information pane.
To display fcdomain statistics using Fabric Manager, follow these steps:
Step 1
You see the running configuration of the domain in the Information pane.
Step 2
Default Settings
Table 25-2 lists the default settings for all fcdomain parameters.
