Cisco Nexus 5000 Series Fabric Manager Configuration Guide, Release 3.4(1a)

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.

Caution Changes 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 When you change the configuration, be sure to save the running configuration. The next time you reboot the switch, the saved configuration is used. If you do not save the configuration, the previously saved startup configuration is used.

This chapter includes the following sections:

•Information About Fibre Channel Domains

•Domain IDs

•FC IDs

•Displaying fcdomain Statistics

•Default Settings

Information About Fibre Channel Domains

This section describes each fcdomain phase:

•Principal switch selection—This phase guarantees the selection of a unique principal switch across the fabric.

•Domain ID distribution—This phase guarantees each switch in the fabric obtains a unique domain ID.

•FC ID allocation—This phase guarantees a unique FC ID assignment to each device attached to the corresponding switch in the fabric.

•Fabric reconfiguration—This phase guarantees a resynchronization of all switches in the fabric to ensure they simultaneously restart a new principal switch selection phase.

See Figure 11-1 for an example fcdomain configuration.

Figure 11-1 Sample fcdomain Configuration

Note Domain IDs and VSAN values used in all procedures are only provided as examples. Be sure to use IDs and values that apply to your configuration.

This section describes the fcdomain feature and includes the following topics:

•About Domain Restart

•Restarting a Domain

•About Switch Priority

•Configuring Switch Priority

•About fcdomain Initiation

•Enabling or Disabling fcdomains

•Setting Fabric Names

•About Incoming RCFs

•Rejecting Incoming RCFs

•About Autoreconfiguring Merged Fabrics

•Enabling Autoreconfiguration

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. Nondisruptive domain restarts are acceptable only when changing a preferred domain ID into a static one (and the actual domain ID remains the same).

Note A static domain is specifically configured by the user and may be different from the runtime domain. If the domain IDs are different, the runtime domain ID changes to take on the static domain ID after the next restart, either disruptive or nondisruptive.

Tip If a VSAN is in interop mode, you cannot disruptively restart the fcdomain for that VSAN.

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, perform this task:

Step 1 Expand Fabricxx > VSANxx, and then choose Domain Manager in the Logical Domains pane for the fabric and VSAN that you want to restart.

You see the Running tab configuration of the domain in the Information pane as shown in Figure 11-2.

Figure 11-2 Running Domain Configuration

Step 2 Click the Configuration tab.

You see the switch configuration as shown in Figure 11-3.

Figure 11-3 Configuring Domains

Step 3 Choose disruptive or nonDisruptive in the Restart drop-down list for any switch in the fabric that you want to restart the fcdomain.

Step 4 Click the Apply Changes icon to initiate the fcdomain restart.

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 cannot 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 world-wide name (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, perform this task:

Step 1 Expand Fabricxx > VSANxx, and then choose Domain Manager in the Logical Domains pane for the fabric and VSAN that you want to set the principal switch priority for.

You see the domain's running configuration in the Information pane as shown in Figure 11-4.

Figure 11-4 Running Domain Configuration

Step 2 Click the Configuration tab.

You see the switch configuration as shown in Figure 11-3.

Step 3 Set Priority to a high value for the switch in the fabric that you want to be the principal switch.

Step 4 Click the Apply Changes icon to save these changes.

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, perform this task:

Step 1 Expand Fabricxx > VSANxx, and then choose Domain Manager in the Logical Domains pane for the fabric and VSAN that you want to disable fcdomain for.

You see the domain's running configuration in the Information pane.

Step 2 Click the Configuration tab and uncheck the Enable check box (see Figure 11-5) for each switch in the fabric that you want to disable fcdomain on.

Figure 11-5 Configuring Domains

Step 3 Click the Apply Changes icon to save these changes.

Setting Fabric Names

To set the fabric name value for a disabled fcdomain using Fabric Manager, perform this task:

Step 1 Expand Fabricxx > VSANxx, and then choose Domain Manager in the Logical Domains pane for the fabric and VSAN that you want to set the fabric name for.

You see the running configuration of the domain in the Information pane.

Step 2 Click the Configuration tab and set the fabric name for each switch in the fabric.

Step 3 Click the Apply Changes icon to save these changes.

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 effect immediately.

No fcdomain restart (see the "About Domain Restart" section).

Note You do not need to configure the RFC reject option on virtual Fibre Channel interfaces, because these interfaces operate only in F port mode.

Rejecting Incoming RCFs

To reject incoming RCF request frames using Fabric Manager, perform this task:

Step 1 In the Physical Attributes pane, expand Switches > Interfaces, and then choose FC Physical.

You see the Fibre Channel configuration in the Information pane.

Step 2 Click the Domain Mgr tab.

You see the information in Figure 11-6.

Figure 11-6 Rejecting Incoming RCF Request Frames

Step 3 Check the RcfReject check box for each interface that you want to reject RCF request frames on.

Step 4 Click the Apply Changes icon to save these changes.

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 situations can occur:

•If the autoreconfigure option is enabled on both switches, a disruptive reconfiguration phase is started.

•If the autoreconfigure option is disabled on either or both switches, the links between the two switches become isolated.

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 eliminating the domain overlap.

Enabling Autoreconfiguration

To enable automatic reconfiguration in a specific VSAN (or range of VSANs) using Fabric Manager, perform this task:

Step 1 Expand Fabricxx > VSANxx, and then choose Domain Manager in the Logical Domains pane for the fabric and VSAN that you want to enable automatic reconfiguration for.

You see the running configuration of the domain in the Information pane.

Step 2 Click the Configuration tab and check the Auto Reconfigure check box for each switch in the fabric that you want to automatically reconfigure.

Step 3 Click the Apply Changes icon to save these changes.

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

•Specifying Static or Preferred Domain IDs

•About Allowed Domain ID Lists

•Configuring Allowed Domain ID Lists

•About CFS Distribution of Allowed Domain ID Lists

•Enabling Distribution

•Locking the Fabric

•Committing Changes

•Discarding Changes

•Clearing a Fabric Lock

•Displaying Pending Changes

•Displaying Session Status

•About Contiguous Domain ID Assignments

•Enabling Contiguous Domain ID Assignments

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 The 0 (zero) value can be configured only if you use the preferred option.

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 11-7):

1. The local switch sends a configured domain ID request to the principal switch.

2. The principal switch assigns the requested domain ID if available. Otherwise, it assigns another available domain ID.

Figure 11-7 Configuration Process Using the Preferred Option

The operation of a subordinate switch changes based on three factors:

•The allowed domain ID lists.

•The configured domain ID.

•The domain ID that the principal switch has assigned to the requesting switch.

In specific situations, the changes are as follows:

•When the received domain ID is not within the allowed list, the requested domain ID becomes the runtime domain ID and all interfaces on that VSAN are isolated.

•When the assigned and requested domain IDs are the same, the preferred and static options are not relevant, and the assigned domain ID becomes the runtime domain ID.

•When the assigned and requested domain IDs are different, the following cases apply:

–If the configured type is static, the assigned domain ID is discarded, all local interfaces are isolated, and the local switch assigns itself the configured domain ID, which becomes the runtime domain ID.

–If the configured type is preferred, the local switch accepts the domain ID assigned by the principal switch and the assigned domain ID becomes the runtime domain ID.

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.

Caution You must restart the fcdomain if you want to apply the configured domain changes to the runtime domain.

Note If you have configured an allow domain ID list, the domain IDs that you add must be in that range for the VSAN. See the "About Allowed Domain ID Lists" section.

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 obtain 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 nondisruptive restart, the preferred option is applied at runtime only after a disruptive restart (see the "About Domain Restart" section).

Note Within a VSAN all switches should have the same domain ID type (either static or preferred). If a configuration is mixed (some switches with static domain types and others with preferred), you may experience link isolation.

To specify a static or preferred domain ID using Fabric Manager, perform this task:

Step 1 Expand Fabricxx > VSANxx, and then choose Domain Manager in the Logical Domains pane for the fabric and VSAN that you want to configure the domain ID for.

You see the running configuration of the domain in the Information pane.

Step 2 Enter a value for the Config DomainID and click static or preferred from the Config Type drop-down list to set the domain ID for switches in the fabric.

Step 3 Click the Apply Changes icon to save these changes.

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 nonoverlapping domain IDs. This helps you in the future if you need to implement IVR without the NAT feature.

Tip If you configure an allowed list on one switch in the fabric, we recommend that you configure the same list in all other switches in the fabric to ensure consistency or use CFS to distribute the configuration.

An allowed domain ID list must satisfy the following conditions:

•If this switch is a principal switch, all the currently assigned domain IDs must be in the allowed list.

•If this switch is a subordinate switch, the local runtime domain ID must be in the allowed list.

•The locally configured domain ID of the switch must be in the allowed list.

•The intersection of the assigned domain IDs with other already configured domain ID lists must not be empty.

Configuring Allowed Domain ID Lists

To configure the allowed domain ID list using Fabric Manager, perform this task:

Step 1 Expand Fabricxx > VSANxx > Domain Manager, and then choose Allowed in the Logical Domains pane for the fabric and VSAN for which you want to set the allowed domain ID list.

You see the CFS configuration in the Information pane (see Figure 11-8).

Figure 11-8 Allowed CFS Configuration Information

Step 2 Set the Admin drop-down list to enable and set the Global drop-down list to enable.

Step 3 Click Apply Changes to enable CFS distribution for the allowed domain ID list.

Step 4 Click the Allowed DomainIds tab.

You see the Allowed Domain ID screen as shown in Figure 11-9.

Figure 11-9 Allowed Domain ID List

Step 5 Set the list to the allowed domain IDs list for this domain.

Step 6 Click the CFS tab and set Config Action to commit.

Step 7 Click the Apply Changes icon to commit this allowed domain ID list and distribute it throughout the VSAN.

About CFS Distribution of Allowed Domain ID Lists

You can enable the distribution of the allowed domain ID list configuration information to all Cisco SAN 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 switch. Because the same configuration is distributed to the entire VSAN, you can avoid possible misconfiguration and the possibility that two switches in the same VSAN have configured incompatible allowed domains.

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 We recommend configuring the allowed domain ID list and committing it on the principal switch.

For more information about CFS, see Chapter 7, "Using Cisco Fabric Services."

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, perform this task:

Step 1 Expand Fabricxx > VSANxx > Domain Manager, and then choose Allowed in the Logical Domains pane for the fabric and VSAN that you want to set the allowed domain ID list for.

You see the CFS configuration in the Information pane.

Step 2 Set the Admin drop-down list to enable and the Global drop-down list to enable to enable CFS distribution for the allowed domain ID list.

Step 3 Click the Apply Changes icon to enable CFS distribution for the allowed domain ID list.

Locking the Fabric

The first action that modifies the existing configuration creates the pending configuration and locks the feature in the fabric. After you lock the fabric, the following conditions apply:

•No other user can make any configuration changes to this feature.

•A pending configuration is created by copying the active configuration. Subsequent modifications are made to the pending configuration and remain there until you commit the changes to the active configuration (and other switches in the fabric) or discard them.

Committing Changes

To apply the pending domain configuration changes to other SAN 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 SAN switches throughout the VSAN and the fabric lock is released.

To commit pending domain configuration changes and release the lock using Fabric Manager, perform this task:

Step 1 Expand Fabricxx > VSANxx > Domain Manager, and then choose Allowed in the Logical Domains pane for the fabric and VSAN that you want to set the allowed domain ID list for.

You see the CFS configuration in the Information pane.

Step 2 Set the Config Action drop-down list to commit.

Step 3 Click the Apply Changes icon to commit the allowed domain ID list and distribute it throughout the VSAN.

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, perform this task:

Step 1 Expand Fabricxx > VSANxx > Domain Manager, and then choose Allowed in the Logical Domains pane for the fabric and VSAN that you want to set the allowed domain ID list for.

You see the CFS configuration in the Information pane.

Step 2 Set the Config Action drop-down list to abort.

Step 3 Click the Apply Changes icon to discard any pending changes to the allowed domain ID list.

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 The pending changes are only available in the volatile directory and are discarded if the switch is restarted.

To release a fabric lock using Fabric Manager, perform this task:

Step 1 Expand Fabricxx > VSANxx > Domain Manager, and then choose Allowed in the Logical Domains pane for the fabric and VSAN for which you want the allowed domain ID list.

You see the CFS configuration in the Information pane.

Step 2 Set the Config Action drop-down list to clear.

Step 3 Click the Apply Changes icon to clear the fabric lock.

Displaying Pending Changes

To display the pending configuration changes using Fabric Manager, perform this task:

Step 1 Expand Fabricxx > VSANxx > Domain Manager > Allowed in the Logical Domains pane for the fabric and VSAN that you want to set the allowed domain ID list for.

You see the CFS configuration in the Information pane.

Step 2 Set the Config View As drop-down list to pending.

Step 3 Click the Apply Changes icon to clear the fabric lock.

Step 4 Click the AllowedDomainIds tab.

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, perform this task:

Step 1 Expand Fabricxx > VSANxx > Domain Manager, and then choose Allowed in the Logical Domains pane for the fabric and VSAN for which you want to set the allowed domain ID list.

Step 2 View the CFS configuration and session status in the Information pane.

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 situations can occur:

•If the contiguous domain assignment is enabled in the principal switch, the principal switch locates contiguous domains and assigns them to the subordinate switches. If contiguous domains are not available, the switch software rejects this request.

•If the contiguous domain assignment is disabled in the principal switch, the principal switch assigns the available domains to the subordinate switch.

Enabling Contiguous Domain ID Assignments

To enable contiguous domains in a specific VSAN (or a range of VSANs) using Fabric Manager, perform this task:

Step 1 Expand Fabricxx > VSANxx, and then choose Domain Manager in the Logical Domains pane for the fabric and VSAN that you want to enable contiguous domains for.

You see the running configuration of the domain in the Information pane.

Step 2 Click the Configuration tab and check the Contiguous Allocation check box for each switch in the fabric that will have contiguous allocation.

Step 3 Click the Apply Changes icon to save these changes.

FC IDs

When an N port logs into a Cisco Nexus 5000 Series switch, it is assigned an FC ID. By default, the persistent FC ID feature is enabled. If this feature is disabled, the following situations can occur:

•An N port logs into a Cisco Nexus 5000 Series switch. The WWN of the requesting N port and the assigned FC ID are retained and stored in a volatile cache. The contents of this volatile cache are not saved across reboots.

•The switch is designed to preserve the binding FC ID to the WWN on a best-effort basis. For example, if one N port disconnects from the switch and its FC ID is requested by another device, this request is granted and the WWN with the initial FC ID association is released.

•The volatile cache stores up to 4000 entries of WWN to FC ID binding. If this cache is full, a new (more recent) entry overwrites the oldest entry in the cache. In this case, the corresponding WWN to FC ID association for the oldest entry is lost.

•N ports receive the same FC IDs if disconnected and reconnected to any port within the same switch (as long as it belongs to the same VSAN).

This section describes configuring FC IDs and includes the following topics:

•About Persistent FC IDs

•Enabling the Persistent FC ID Feature

•Persistent FC ID Configuration Guidelines

•Configuring Persistent FC IDs

•About Unique Area FC IDs for HBAs

•Configuring Unique Area FC IDs for an HBA

•About Persistent FC ID Selective Purging

•Purging Persistent FC IDs

About Persistent FC IDs

When persistent FC IDs are enabled, the following occurs:

•The current FC IDs in use in the fcdomain are saved across reboots.

•The fcdomain automatically populates the database with dynamic entries that the switch has learned about after a device (host or disk) is plugged into a port interface.

Note If you connect to the switch from an AIX or HP-UX host, be sure to enable the persistent FC ID feature in the VSAN that connects these hosts.

Note When persistent FC IDs are enabled, FC IDs cannot be changed after a reboot. FC IDs are enabled by default, but can be disabled for each VSAN.

A persistent FC ID assigned to an F port can be moved across interfaces and can continue to maintain the same persistent FC ID.

Enabling the Persistent FC ID Feature

To enable the persistent FC ID feature using Fabric Manager, perform this task:

Step 1 Expand Fabricxx > VSANxx, and then choose Domain Manager in the Logical Domains pane for the fabric and VSAN that you want to enable the Persistent FC ID feature for.

You see the running configuration of the domain in the Information pane.

Step 2 Click the Persistent Setup tab and check the enable check box for each switch in the fabric that will have persistent FC ID enabled.

Step 3 Click the Apply Changes icon to save these changes.

Persistent FC ID Configuration Guidelines

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.

When manually configuring a persistent FC ID, follow these requirements:

•Ensure that the persistent FC ID feature is enabled in the required VSAN.

•Ensure that the required VSAN is an active VSAN. Persistent FC IDs can only be configured on active VSANs.

•Verify that the domain part of the FC ID is the same as the runtime domain ID in the required VSAN. If the software detects a domain mismatch, the command is rejected.

•Verify that the port field of the FC ID is 0 (zero) when configuring an area.

Configuring Persistent FC IDs

To configure persistent FC IDs using Fabric Manager, perform this task:

Step 1 Expand Fabricxx > VSANxx, and then choose Domain Manager in the Logical Domains pane for the fabric and VSAN that you want to configure the Persistent FC ID list for.

You see the running configuration of the domain in the Information pane.

Step 2 Click the Persistent FcIds tab and click Create Row.

You see the Create Persistent FC IDs dialog box as shown in Figure 11-10.

Figure 11-10 Create Persistent FC IDs Dialog Box

Step 3 Choose the switch, WWN, and FC ID that you want to make persistent.

Step 4 Click either the single or area radio button in the Mask field.

Step 5 Click either the static or dynamic radio button in the Assignment field.

Step 6 Click the Apply Changes icon to save these changes.

About Unique Area FC IDs for HBAs

Note Only read this section if the Host Bus Adapter (HBA) port and the storage port are connected to the same switch.

Some HBA ports require a different area ID than for the 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.

Cisco Nexus 5000 Series switches 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.

Configuring Unique Area FC IDs for an HBA

The following task uses an example configuration with a switch domain of 111(6f hex). The server connects to the switch over FCoE. The HBA port connects to interface vfc20/1 and the storage port connects to interface fc2/3 on the same switch.

To configure a different area ID for the HBA port using Fabric Manager, perform this task:

Step 1 Expand End Device in the Physical Attributes pane and then choose the Summary tab to obtain the port WWN (Port Name field) of the HBA (see Figure 11-11).

Figure 11-11 FLOGI Database Information in Fabric Manager

Note Both FC IDs in this setup have the same area 00 assignment.

Step 2 In the Physical Attributes pane, expand Switches > Interfaces, and then choose FC Physical.

You see the Fibre Channel Interfaces information pane.

Step 3 Set the Status Admin drop-down list to down for the interface that the HBA is connected to.

This shuts down the HBA interface in the MDS switch.

Step 4 Expand Fabricxx > VSANxx, and then choose Domain Manager.

Step 5 Click the Persistent Setup tab in the Information pane to verify that the FC ID feature is enabled (see Figure 11-12).

Figure 11-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 Check the Enable check box to enable the persistent FC ID feature in the switch (see Figure 11-13).

Step 7 Click the Persistent FcIds tab and assign a new FC ID with a different area allocation in the FcId field.

For example, in Figure 11-13 we replace 00 with ee.

Figure 11-13 Setting the FC ID in Fabric Manager

Step 8 Click Apply Changes to save the new FC ID.

Step 9 Compare the FC ID values to verify the FC ID of the HBA.

Note Both FC IDs now have different area assignments.

Step 10 In the Physical Attributes pane, expand Switches > Interfaces, and then choose FC Physical. Set the Status Admin drop-down list to up for the interface that the HBA is connected to.

This enables the HBA interface in the Cisco Nexus 5000 Series switch.

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 11-1 identifies the FC ID entries that are deleted or retained when persistent FC IDs are purged.

Purging Persistent FC IDs

To purge persistent FC IDs using Fabric Manager, perform this task:

Step 1 Expand Fabricxx > All VSANs > Domain Manager in the Logical Domains pane for the fabric that you want to purge the Persistent FC IDs for.

You see the running configuration of the domain in the Information pane.

Step 2 Click the Persistent Setup tab.

You see the persistent FC ID setup in the Information pane as shown in Figure 11-14.

Figure 11-14 Persistent FC ID Information in Fabric Manager

Step 3 Check the Purge check box for the switch that you want to purge persistent FC IDs on (see Figure 11-14).

Step 4 Click the Apply Changes icon to save these changes.

Displaying fcdomain Statistics

Fabric Manager collects statistics for fcdomain and displays them in the Information pane.

To display fcdomain statistics using Fabric Manager, perform this task:

Step 1 Expand Fabricxx > All VSANs, and then choose Domain Manager in the Logical Domains pane for the fabric that you want to display statistics for.

You see the running configuration of the domain in the Information pane.

Step 2 Click the Statistics tab.

You see the FC ID statistics in the Information pane.

Default Settings

Table 11-2 lists the default settings for all fcdomain parameters.