Error data fc2

General SAN troubleshooting steps

Step 1 Obtain information on problems in your fabric.

Step 2 Verify physical connectivity between your switches and end devices.

Step 3 Verify registration to your fabric for all SAN elements.

Step 4 Verify the configuration for your end devices (storage subsystems and servers).

Step 5 Verify end-to-end connectivity and fabric configuration.

NP Uplink ports on NPV edge switch are stuck in initializing state

NP uplink ports connected to the core NPIV switch do not come online and are stuck in an initializing state.

Possible Cause

The core switch might not have been enabled for NPIV.

Example:

Solution

• Check the status of the NPV external interfaces.
  Check that the NPIV is enabled on the core switch.

Example:

• If NPIV is disabled, then enable NPIV on the core switch.

Example:

Server interface does not come up and “NPV upstream port not available” message appears

A server port connected to the NPV edge switch does not come online, and the show interface command indicates a status of NPV upstream port not available.

Possible Cause

The upstream NP_Port(s) and the downstream server F_Port(s) on the NPV edge switch may not be in the same VSAN.

Example:

Solution

• Check the VSAN membership of the upstream port and the server port.

Example:

• In the example above, notice that the upstream ports (fc2/1-2) are in VSAN 1, and the server ports (fc2/7-8) are in VSAN 99.
  Move the NP ports on the NPV edge, and the F ports on the NPIV core into the same VSAN as the server ports.

Example:

Note Alternatively, if the NPIV core and NPV edge switch are F_Port Trunking capable switches, then that would be the recommended configuration.

Uneven load balancing on the NPV NP ports

An examination of NP upstream ports that are members in the same VSAN reveals that uneven load balancing is occurring.

Possible Cause

This may be normal and a direct result of the default SID/DID load balancing that is done before the Nexus 5000 4.2(1)N1 release.

Solution

If the upstream switch is an MDS switch that is running 4.1(3) code or above, and it is a NPV F_Port Trunking capable switch, the preferred configuration would be to run the F_Port Trunking Port Channeling feature.

Example (NPIV core):

In this example, fc2/13 and fc2/19 are added to port channel 100 and are disabled. Do the same operation on the switch at the other end of the port channel, then do no shutdown at both ends to bring them up.

Example:

Example (NPV Edge):

In this example, fc2/1 and fc2/2 are added to port channel 1 and are disabled. Do the same operation on the switch at the other end of the port channel, then do no shutdown at both ends to bring them up

Example:

Server on downstream NPV edge switch does not login to the fabric

The server connected to the downstream NPV edge switch does not log in to the fabric.

Possible Cause

The server on the downstream NPV edge switch does not log in to the fabric, and/or you see a “waiting for FLOGI” message.

Example:

Solution

• Verify the configuration of both the NPV edge and core switches. If you are not running the F_Port trunking feature, then verify that there are no VSAN mismatches and that the server ports, NPV NP ports, NPIV Core F_Ports, and storage ports are all in the same VSAN and all are online.
• If the configuration is correct and you can determine where the problem might be, you can collect an Ethanalyzer trace and verify that the Fabric Login (FLOGI) frame is being received and sent to the NPIV core as a Fabric Discovery (FDISC) command.

Example Ethanalyzer trace:

• Recreate the problem by flapping the NPV-attached server port. The trace will be written to bootflash and can be copied off the switch by using the following:

• After the trace has been copied, you can now open and verify the flow using Wireshark.

Example normal NPV login flow:

Locating exact port that server is physically attached to

NPIV switches lose visibility into the physical port that a downstream NPV-connected server is attached to. The following process can be used to identify that physical port.

Possible Cause

When you have an NPIV core switch that has several downstream NPV edge switches attached, you might want to locate the exact port that a server is physically attached to.

Solution

• Identify the PWWN of the server and the corresponding switch that it is attached to.

Example:

In the example, the server is identified by this address:

and the switch is identified by this address

• Identify the IP address of the NPV edge switch.

Example:

• Telnet to the NPV edge switch.

Example:

• Identify the PWWN of the server.

Example:

• If the interface is a FCoE (VFC) interface as shown in the previous example, use the show interface vfc3 command to see which port that the VFC is physically bound to.

VSANs stuck in initializing state after configuring the 4.2(1)N1 F_Port trunking feature

Using the show interface command of the F_Port trunking port channel or trunking member of the port channel indicates that certain VSANs are in an initializing state and do not come online.

Possible Cause

After configuring the 4.2(1)N1 F_Port Trunking feature, VSANs on the trunk ports appear to be stuck in an initializing state.

Example:

Under the Trunk Failures tab of Fabric Manager, you might also see the trunk VSAN listed. However, this may be normal. If no downstream devices are logged in for a particular VSAN, that VSAN stays in initializing state.

Solution

For the VSANs that you are working with, verify by using the following command:

Example:

In this example, no devices are logged into VSAN 200.

Cannot activate zoneset and cannot configure zoning in enhanced zoning mode

The zone set cannot be activated and zoning cannot be configured in enhanced zoning mode. The error message “Zoning database update in progress, command rejected” might be received.

Possible Cause

Another user on the same switch or on a different switch is holding the enhanced zoning configuration lock.

Solution

Release the zoning lock with the following:

Step 1 Determine which switch (domain/ip address) has the lock.

Step 2 Determine which user has the lock on that switch.

Step 3 Clear the lock for that user on that switch.

• On the same switch, enter the show zone status vsan <vsan-id> command to determine which user holds the lock.

Example:

In this example the remote switch with the IP address of 171.165.98.20 has the lock.

• Connect to the remote switch and enter the show zone status vsan command.

Example:

In the example, user Remi is holding the enhanced zoning lock.

• On the remote switch (N5K2 in the example), release the lock with the no zone commit vsan <vsan-id> command.
• To confirm that the lock had been cleared, enter the show zone status vsan <vsan-id> command.

At this point, the session parameter should appear as none.

• If the lock still persists, remove the lock from the switch that holds the lock with the clear zone lock command.
• If the lock continues to persist, use the following commands to collect information to aid further analysis:

Host cannot communicate with storage

In initial SAN deployments or after topology changes in the SAN, some hosts might not be able to communicate with storage. The initiator cannot access the LUNs that were allocated for them in the storage array.

Possible Cause

If the host and storage are connected to two different switches, the ISL link, (the xE port connecting both switches) might be isolated.

The xE port might be isolated in a specific VSAN for possible reasons:

• Misconfigured fabric timers
• Misconfigured port parameters
• Mismatched zoning

Solution

To resolve the VSAN isolation on the TE port:

• Use the show interface fc <slot/port> command on the TE port to determine the VSAN number.

The isolated VSAN number must match the VSAN number where the host and the storage are connected to.

In the display output, you see the Trunk vsans (isolated) (Vsan <vsan-id>).

• Use the show port internal info interface fc <slot/port> command to determine the root cause of the VSAN isolation.

Possible Cause

Host and storage are not in the same VSAN.

Solution

• Use the show vsan membership command to verify that both the host and the storage are in the same VSAN.
• If the host and the storage are in different VSANs, in the configuration mode use the commands vsan database and vsan <vsan-id> interface fc <slot/port> to move the interface connected to the host and storage devices into the same VSAN.

Possible Cause

The host and storage are not in the same zone. The zone is not in the active zone set. There is no active zone set and default zone policy is set to deny.

Solution

• Use the command show zone status <vsan-id> to determine if the default zone policy is set to deny.

Example:

The state default zone policy permit means all nodes can see all other nodes. Deny means all nodes are isolated when not explicitly placed in a zone.

If you are not using zoning, you can change the default zone policy with zone default-zone permit, but this is not a best practice.

• Use the show zone member command for host and storage to verify that they are both in the same zone. If they are not in the same zone, use the zone name <zonename> <vsan-id> command to create a zone in that VSAN.

Example:

Use the show zone vsan <vsan-id> command to verify that host and storage are now in the same zone.

• Use the show zoneset active vsan <vsan-id> command to verify the name of the active zone set.

If the zone that has the host and storage is not in the active zoneset, use the zoneset name command from the configuration mode to enter the zoneset sub-mode and use the member command to add the zone to the active zone set.

Example:

• Use the zoneset activate command to activate the zone set.

Example:

Zone merge failure when two switches connect using E or TE port

A zone merge failure can occur when two switches connect using the E or TE port.

Possible log messages that can be seen in the show logging log are shown in the example.

Example:

Possible Cause

Two switches may have the same zone set name and the same zone names, but different zone members.

When merging switch fabrics, you must ensure that the zones in both active zone sets have unique names, or that any zones with the same name have exactly the same members. If either of these conditions are not met, then the E port connecting the two fabrics will appear in an isolated state.

The process to merge switch fabrics is as follows:

• The software compares the protocol versions. If the protocol versions differ, then the ISL is isolated.
• If the protocol versions are the same, then the zone policies are compared. If the zone policies differ, then the ISL is isolated.
• If the zone merge options are the same, then the comparison is implemented based on the merge control setting.

– If the setting is restrict, the active zone set and the full zone set should be identical. Otherwise the link is isolated.

– If the setting is allow, then the merge rules are used to perform the merge. The host and storage are not in the same zone. The zone is not in the active zoneset. There is no active zoneset and default zone policy is set to deny.

Solution

If there is a zone merge failure, the issue can be resolved by using one of the following methods:

• Modify the zone members in both zone sets to match and eliminate the conflict.

– Use the show zoneset active vsan <vsan-id> command on both switches to compare the zones and their respective members.

– Change the membership of one of the zones to match the other zone of the same name.

• Deactivate the zone set on one of the switches and restart the zone merge process.

– Use the no zoneset activate name <zonesetname> <vsan-id> command to deactivate the zone set configuration from one of the switch.

– Use the show zoneset active command to confirm that the zone set has been removed.

– Use the shutdown command to shut down the connection to the zone to be merged, and use the no shutdown command to reactivate the connection to the zone to be merged.

– Use the show zoneset active <vsan-id> to verify that all the members are correct and use the show interface fc <slot/port> to verify that the VSAN is not isolated.

• Explicitly import or export a zone set between the switches to synchronize them.

– Use the zoneset import interface <interface-number> vsan <vsan-id> command or the zoneset export interface <interface-number> vsan <vsan-id> command to overwrite the active zone set on one of the switches.

– Use the show interface fc <slot/port> to verify that the VSAN is not isolated after this disruptive operation.

Zone set activation failure

When a zone set activation failure occurs, the possible log messages that can be seen in the show logging log are shown in the example.

Example:

Possible Cause

Zone set activation can fail if a new switch joins the fabric when the size of the zone database is larger than 2048 KB.

Solution

• Use the show zone analysis active vsan <vsan-id> command to analyze the active zone set database. Verify that the formatted size does not exceed 2048 KB.

If the 2048 KB limit is exceeded, then some zones or devices within a zone must be removed.

Example:

Number of devices zoned in vsan: 1/9 (Unzoned:

• Use the show zone internal change event-history vsan <vsan-id> command to determine the zone set activation problem.
• To further troubleshoot this issue, capture the output from the show tech-support zone command and the show logging log command.

Full zone database synchronization failure across two switches

A full zone database synchronization failure may occur when two switches connect using the E or TE port and have different zone set distribution policies. As a result of a fabric isolation/merge, one fabric might not have the full zone set database in the running configuration.

Possible Cause

The zone set distribution takes effect while sending merge requests to the adjacent switch or while activating a zone set.

The zone distribute policy can be set differently on two switches and that could cause synchronization failure.

Solution

Use the show zone status command to verify the distribution policy on both switches.

Example:

When the distribute policy is set to active only the active zone set is distributed. Also verify that the distribute policy is set to full.

To enable the full zone set and active zone set distribution to all switches on a per-VSAN basis in the configuration mode, use the zoneset distribute full vsan <vsan-id> command.

Mismatched default zone policy in switches in VSAN causes unexpected results when accessing storage

A mismatched default zone policy in all switches in the VSAN in the basic zone mode might cause unexpected results for any hosts accessing storage.

Possible Cause

If the default zone policy is set to permit and if there is no active zone set for VSAN, then all the members of the VSAN can see all the other nodes.

Solution

One approach is to migrate the zone operation mode from basic to enhanced. Enhanced zoning synchronizes the zone configuration across all switches in the VSAN. This eliminates the possibility of mismatched default zone policies.

• Use the show zone status command to display the status of the zone.

• Use the zone default-zone command to set the default zone policy and use the zone mode enhanced <vsan-id> command to set the operation to enhanced zoning mode.

Another approach is the foillowing:

• Use the show zone status command in all switches in the VSAN to verify the operation mode and the default-zone policy.
• Use the zone mode basic command to change any switches that are not in basic mode.
• Use the zone default-zone command on each switch in the VSAN to set the same default zone policy.

Fibre channel port is down when trying to connect switches via SAN Port Channel

When trying to connect switches using SAN port channel, the Fibre Channel port is down.

The show interface brief command produces

Possible Cause

One of the SAN port channel compatibility parameters is misconfigured in the configuration.

A compatibility check ensures that the same parameter settings are used in all physical ports in the channel. Otherwise, they cannot become part of a port channel. The compatibility check is performed before a port is added to the port channel.

The check ensures that the following parameters and settings match at both ends of a port channel:

• Capability parameters:
  type of interface, Gigabit Ethernet at both ends, or Fibre Channel at both ends.
• Administrative compatibility parameters:
  speed, mode, rate mode, port VSAN, allowed VSAN list, and port security..
• Operational parameters:
  remote switch WWN and trunking mode.

Solution

• Use show san-port-channel compatibility-parameters to verify which parameters need to be checked in the configuration.

Generally, if the configuration is fixed and the FC port is shut or no shut, the port recovers normally.

• If the issue persists with a different error message, debug further by running one or more of the following commands:

Newly added Fibre Channel interface does not come online in a SAN Port Channel

When a new Fibre Channel interface is added, it does not come online in a SAN port channel.

The following error message during the configuration operation may appear.

Command failed: port not compatible [reason]

Possible Cause

Port channel mode is configured as on.

If you use the default ON mode to avoid inconsistent states across switches and to maintain consistency across switches, then the ports shut down.

Solution

Explicitly enable the ports again using the no shutdown command.

Possible Cause

Interface parameters are not compatible with the existing SAN port channel.

Solution

Use the force option to force the physical interface to take on the parameters of the SAN port channel. In the interface sub-configuration mode, use the channel-group <channel-group number> force command.

Cannot configure trunking

Trunking cannot be configured under the interface configuration mode.

The following error message may appear in the CLI output:

Possible Cause

Trunking protocol is disabled.

Solution

Enable trunking by using the trunk protocol enable CLI command.

VSAN traffic does not traverse trunk

The VSAN traffic is not able to traverse the trunk.

A host cannot gain access to a target that is on the same VSAN and connected to two different switches using TE ports. The VSAN traffic is not able to traverse the trunk. Depending on the path from host to target, you may observe a performance degradation or you may not be able to access any disks.

Possible Cause

VSAN is not listed in the allowed-active VSAN list.

Solution

Add VSAN to the allowed-active list by using the switchport trunk allowed vsan command.

xE port is isolated in a specific VSAN under interface of SAN Port Channel

The xE port is isolated in a specific VSAN that is under an interface of a SAN port channel.

The following error message may appear in the logging log:

Possible Cause

The xE port can be isolated in a specific VSAN for many reasons:

• Fabric timers might be misconfigured.
• Port parameters might be misconfigured.
• Zoning mismatch.

Solution

To resolve the VSAN isolation on the TE port, use the show interface fc <slot/port> command on the TE port to determine the VSAN number. The isolated VSAN number must match the VSAN number where the host and the storage are connected to.

In the output of the command, look for information such as Trunk vsans (isolated) (Vsan <number>).

Use the show port internal info interface san-port-channel <number> command to determine the cause of the VSAN isolation.

Cannot create a san-port-channel interface

A SAN port channel interface cannot be created.

The following error message may appear while in configuration mode:

Possible Cause

The user receives the following message:

Note You can create a maximum of four SAN port channels (including Release NX-OS 4.2(1)N1(1)). This is a software limitation.

Solution

If you need to create a SAN port channel with a specific number, but four SAN port channels were already configured, then you have to delete one of the SAN port channels that is not actively used. Use the no interface san-port-channel <x> command to delete one of the SAN port channels.

Possible Cause

You receive the following message:

Solution

You need to choose another number between 1 to 256 to configure the SAN port channel.

Use the show port-channel usage command to determine the numbers that were used for the existing port channels.

Example:

Overview

Fibre Channel fabrics provide a set of services for its clients, which are the Fibre Channel nodes. These Fibre Channel services (FC services) allow the nodes to interact with the storage network to exchange information, such as connection state, connection parameters, configuration, topology changes, and so on.

The FC services can be accessed through login into ports that hold a well known address (WKA). WKAs are port FC IDs that are reserved for internal use of the fabric, usually fabric services.

The following table describes the well-known addresses and the service associated with each:
(Source: www.t11.org)

Fibre channel port remains in initializing state

A fibre channel F type port does not come online and is stuck in an initializing state.

The show interface fc <slot/port> command displays the following message.

A Fibre Channel port goes into the initialization state after a successful completion of link-level initialization. For F type ports, the next step is to complete the FLOGI (fabric login) process. The port remains in the initialization state until the FLOGI process completes.

Possible Cause

The port is up because the link partner has put itself into a bypass mode.

Solution

Use the show hardware internal fc-mac <slot-number> port <port-number> statistics command to check whether the Class-3 input counter is increasing after the successful completion of link initialization.

Example:

Possible Cause

The FLOGI packet was dropped somewhere in the data path, starting from FC-MAC to FLOGI server.

Solution

Consider the following solutions:

• Use the show hardware internal fc-mac <slot-number> port <port-number> statistics command to check for Class-3 packet counters.
• Analyze the output of the show flogi internal all interface fc <slot/port> command for a possible drop of FLOGI packets somewhere in the path.
• Check the Fport server fault-injection table for any Invalid, Drop FLOGI packets.
• Use the shut CLI command followed by the no shut command to disable and enable the FC slot/port.
• If this does not clear the problem, try moving the connection to a different port on the same or another FC module.
• If the problem continues to persist, use the following commands to collect information to aid in further analysis:

Capture debug Flogi with the following:

Specific VSAN traffic is not being routed through SAN fabric

Each configured VSAN needs to support a separate set of fabric services. One such service is the FSPF routing protocol, which can be independently configured per VSAN. You may see that specific VSAN traffic is not being routed if inappropriate traffic engineering capabilities are used.

Possible Cause

The FSPF hello interval is misconfigured.

The following example shows possible log messages from the show logging command log.

Example:

Solution

To resolve a wrong hello interval on an ISL using the NX-OS CLI, perform the following steps.

Step 1 Either use the debug fspf all command and look for wrong hello interval messages
or check the last messages in the show logging command log for an error message.

The debug output generates the following messages:

Step 2 Use the undebug all command to turn off debugging.

Tip Open a second Telnet or SSH session before entering any debug commands. If the debug output overwhelms the current session, you can use the second session to enter the undebug all command to stop the debug message output.

Step 3 Use the show fspf vsan <vsan-id> interface command to view the FSPF configuration on both switches.

Example:

Note In the Example:

• The hello timer is not set to the default (20 seconds) on the first switch. Check the neighboring switch (Nexus 5000) configuration to make sure it matches.
• FSPF is not in FULL state. This indicates a problem.

Step 4 In the interface configuration mode, change the fspf hello-interval value to match the same values on both switches.

Example:

Step 5 Verify that the FSPF is in FULL state after the change.

Possible Cause

The FSPF dead interval is misconfigured.

The following example shows possible log messages from the show logging command:

Example:

Solution

To identify a mismatch of dead intervals on an ISL using the NX-OS CLI, perform the following steps:

Step 1 Either use the debug fspf all command and look for wrong dead interval messages
or check the last messages in the show logging command log for an error message.

The debug output generates the following messages:

Step 2 Use the undebug all command to turn off debugging.

Tip Open a second Telnet or SSH session before entering any debug commands. If the debug output overwhelms the current session, you can use the second session to enter the undebug all command to stop the debug message output.

Step 3 Use the show fspf vsan <vsan-id> interface command to view the FSPF configuration on both switches.

Example:

Note In the example:

• The dead timer is not set to the default (80 seconds) on the first switch. Check the neighboring switch (MDS) configuration to make sure it matches.
• FSPF is not in FULL state. This indicates a problem.

Step 4 In the interface configuration mode, change the fspf dead-interval value so that the same values match on both switches.

Step 5 Verify that the FSPF is in FULL state after the change. Ensure that there is a route for VSAN traffic with the show fspf internal route vsan <vsan-id> command.

Example:

Possible Cause

There is a region mismatch on the switch.

The following example shows possible log messages from the show logging command log:

Example:

Solution

To identify a region mismatch problem on a switch using the NX-OS CLI, perform the following.

Step 1 Use the show fspf vsan <vsan-id> command to display the currently configured region in a VSAN.

Example (region value is 2; default region value is 0):

Step 2 Use the debug fspf all command and look for nonexistent region messages.

Example:

The neighboring switch-advertising region is 0. FSPF is in the init state for each ISL.

Example:

Step 3 Use the undebug all command to turn off debugging.

Step 4 Use the show fspf vsan <vsan-id> command to show FSPF configuration and check the autonomous region.

Example:

Step 5 Use the fspf config vsan command to enter the FSPF configuration mode and use the region command to change the region. The region must match on all switches in the VSAN.

Example:

Fibre channel port is suspended due to too many invalid FLOGIs

A Fibre Channel node that is connected to an NPV feature-enabled Cisco Nexus 5000 switch or a Cisco Nexus 5000 switch that is running in fabric mode cannot log into the SAN fabric due to a FLOGI rejection.

The following example shows possible log messages from the show logging command log.

Example:

The status of the interface shows invalidFlogis.

Possible Cause

The FC ID persistency table for that VSAN might be full. If the Nexus 5000 Series switch is configured as an NPV edge switch, the FC ID persistency table of the NPV core switch might be full.

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).

Persistent FC IDs can be purged selectively. Static entries and FC IDs currently in use cannot be deleted.

Solution

Check for FLOGI error messages with the show flogi internal command.

Example:

Use the show fcdomain address-allocation command to check the FC domain address allocation table for any free FC IDs: (If NPV is enabled, enter the command on the NPV core switch.)

Example:

To find the auto area-list and the persistent FCIDs, use the show flogi auto-area-list command and the show fcdomain fcid persistent command.

Example:

If there are not enough FCIDs, you can purge dynamic and unused FC IDs in the specified VSAN with the purge fcdomain command.

Example:

The ports will soon come up.

It is also possible that HBAs are trying to login with S_ID != 0x0.

If this is the situation and there is nothing in the persistency table for the WWN of the HBA, try to assign the S_ID used by HBA to the HBA itself.

If the S_ID is already in use or is in the wrong domain, the request is rejected by fcdomain. After a number of retries, the port is suspended.

When HBAs get into this mode, they try to log in with every FCID in the FCID space, from 0x00.00.01 up to all the 0xDD.AA.PP numbers.

This behavior can be seen in the show flogi internal event-history msgs command output

{HBA is trying to login with different FCIDs}

Example:

In this case, the solution is to manually configure an entry in the persistency table for the WWN of the HBA as shown in the following example. An alternative is to power-cycle the device. This usually makes the HBA start with a normal FLOGI with S_ID=0x0.

Example:

If the problem continues to persist, use the following commands to collect information to aid further analysis.

Capture debug flogi and debug fcdomain via following below steps:

Having stale FCNS entries for Fibre Channel nodes

The Fibre Channel nodes are able to be logged (FLOGI) in to the SAN fabric, but the FCNS entries for those nodes are incomplete. Serves cannot reach their targets.

As a result, fc4-types:fc4_features will be empty in FCNS database.

Possible Cause

The Fibre Channel nodes may not be registering their FC4 types and FC4 features in the FCNS database in a topology where Nexus 5000 Series switches are configured as NPV core (feature NPIV) and connected to legacy gateway switches. The fc4-types:fc4_features can be verified by the show fcns database detail command as shown in the following example:

Example:

Some legacy gateway switches might require that the area part of the FCID be the same for the switch and for all the blades logged in through that port.

However, because of an old issue with Qlogic HBAs, the Cisco Nexus 5000 domain server assigns a separate area for each Qlogic HBA that matches a certain OUI by default. Therefore, a conflict between legacy gateway requirements and the Cisco domain allocation scheme exists. Cisco still implements this set up to support old existing Qlogic HBAs in the field.

Solution

Configure no fcid-allocation area company <oui> for all used Qlogic OUIs (ensuring flat FCID allocation in the future), force all affected blades to log out of the fabric, delete the already created persistent FCID entry from the Nexus 5000 switch configuration, and allow the blade to log in again.

In the following show flogi database command output, all devices obtain a unique area id (x01, x08, x0c):

Example:

Because of the specific area ID requirement of the legacy switch, the last two blades must also have area x01. To force the Qlogic adapters to log in again and obtain FCID in 0x6201xx range, do the following steps:

Step 1 Configure (force) the future FCID allocation scheme to be flat for all WWNs matching the OUIs that are in this situation.

Step 2 Force the FCID under reconfiguration to log out of the fabric.

Note If you shut down the Nexus 5000 interface that serves as the primary uplink for that server, it only will log in through another one. The appropriate method is to shut down the affected blade and ensure that the FLOGI for the WWN is gone.

Step 3 Delete the automatically created configuration entry for persistent FCID allocation as shown in the following example:

Example:

Step 4 Bring up the blade and ensure that it gets a proper fcid.

Example:

Interface is isolated because of FC Domain ID overlap

The Fibre Channel or SAN port channel interface of a Cisco Nexus 5000 switch (in fabric mode) that is connected to an FC switch with the xE port type is isolated because of a domain overlap. The following example shows possible logging messages in the show logging command log:

Example:

Possible Cause

Two switch fabrics might not merge. If two fabrics with two or more switches are connected, have at least one assigned domain ID in common, and the auto-reconfigure option is disabled (this option is disabled by default), then the E ports that are used to connect the two fabrics will be isolated due to domain ID overlap.

In a Fibre Channel network, the principal switch assigns domain IDs when a new switch is added to an existing fabric. However, when two fabrics merge, the principal switch selection process determines which one of the preexisting switches becomes the principal switch for the merged fabric.

The election of the new principal switch is characterized by the following rules:

• A switch with a populated domain ID list takes priority over a switch that has an empty domain ID list. The principal switch becomes the one in the fabric with the populated domain ID list.
• If both fabrics have a domain ID list, the priority between the two principal switches is determined by the configured switch priority. This is a parameter that can be set by the user. The lower the value of the parameter, the higher the priority.
• If the principal switch cannot be determined by the two previous criteria, the principal switch is then determined by the WWNs of the two switches. The lower the value of the WWN, the higher the switch priority.

Solution

To resolve an FC domain ID overlap, you can change the overlapping static domain ID by manually configuring a new static domain ID for the isolated switch, or disable the static domain assignment and allow the switch to request a new domain ID after a fabric reconfiguration.

To assign a static domain ID using the NX-OS CLI

All devices attached to the switch in the VSAN get a new FC ID when a new domain ID is assigned. Some hosts or storage devices may not function as expected if the FC ID of the host or storage device changes.

To verify FC domain ID overlap and reassign a new domain ID using the CLI, perform the following steps:

Step 1 Enter the show interface fc <slot/port> command to view the isolation error message for the E port.

Example:

Enter the show interface san-port-channel <channel-id> command to view the isolation error for the specific VSAN.

Example:

Step 2 Use the show fcdomain domain-list vsan <vsan-id> command to view which domains are currently in your fabric.

Example (switch is isolated because of a domain ID 44 overlap):

If the isolation occurred for a specific VSAN under a SAN port channel interface, you can view the error with the show port internal info interface san-port-channel <channel-id> vsan <vsan-id> as shown in the following example:

Example:

Step 3 Use the fcdomain domain <domain-id> [ static | preferred ] vsan <vsan-id> command to change the domain ID for one of the overlapping domain IDs.

• The static option tells the switch to request that particular domain ID. If it does not obtain that particular address, it will isolate itself from the fabric.
• The preferred option has the switch request a specified domain ID. If that ID is unavailable, it will accept another ID.

Step 4 Use the fcdomain restart vsan command to restart Domain Manager.

While the static option can be applied to runtime after a disruptive or nondisruptive restart, the preferred option is applied to runtime only after a disruptive restart.

Note A domain ID restart is disruptive. The Fibre Channel nodes that are logged into that domain will be logged out and logged back in. A disruptive reconfiguration might affect data traffic.

To assign a dynamic domain ID after a fabric reconfiguration

You can use fabric reconfiguration to reassign domain IDs and resolve any overlapping domain IDs. If you enable the auto-reconfigure option on both switches before connecting the fabric, a disruptive reconfiguration (RCF) occurs. The RCF functionality automatically forces a new principal switch selection and causes new domain IDs to be assigned to the different switches.

To use fabric reconfiguration to reassign domain IDs for a particular VSAN using the NX-OS CLI, perform the following these steps:

Step 1 Use the show fcdomain domain-list command to determine if you have statically assigned domain IDs on the switches.

Step 2 If you have statically assigned domain IDs, use the no fcdomain domain command to remove the static assignments.

Step 3 Use the show fcdomain vsan <vsan-id> command to determine if you have the RCF reject option enabled.

Example:

Step 4 If you have the rcf-reject option enabled, use the interface command and then the no fcdomain rcf-reject vsan <vsan-id> command in interface mode.

Example:

Step 5 Use the fcdomain auto-reconfigure vsan <vsan-id> command in the EXEC mode on both switches to enable auto-reconfiguration after a Domain Manager restart.

Step 6 Use the fcdomain restart vsan <vsan-id> command to restart Domain Manager.

This is a disruptive operation and disruptive reconfiguration and can affect data traffic.

Overview

Begin troubleshooting CFS issues by checking the following:

• Verify that CFS is enabled for the same applications on all affected switches.
• Verify that CFS distribution is enabled for the same applications on all affected switches.

If the CFS Regions feature is in use, verify that the application is in the same region on all the affected switches.

• Verify that there are no pending changes for an application and that a CFS commit was issued for any configuration changes in a CFS-enabled application.
• Verify that there are no unexpected CFS locked sessions.

Clear any unexpected locked sessions.

Verifying CFS using CLI

To verify CFS using the CLI, follow these steps:

Step 1 By default, CFS distribution is enabled. Applications can distribute data and configuration information to all CFS-capable switches in the fabric where the applications exist. This is the normal mode of operation. To determine the state of CFS distribution on a switch, enter the show cfs status command.

Example:

Step 2 To verify that an application is listed and enabled, issue the show cfs application command to all switches.

Example:

Note The Physical scope means that CFS applies the configuration for that application to the entire switch. The Logical scope means that CFS applies the configuration for that application to a specific VSAN.

Step 3 Verify the set of switches in which an application is registered with CFS, using the show cfs peers name application-name command for physical scope applications, and the show cfs peers name <application-name> vsan <vsan-id> command for logical scope applications.

Example:

Note The show cfs peers name <application-name> command displays the peers for all VSANs when applied to a logical application.

Example:

Step 4 To determine if all the switches in the fabric constitute one CFS fabric, or a multitude of partitioned CFS fabrics, enter the show cfs merge status name <application-name> command and the show cfs peers name <application-name> command and compare the outputs. If the two outputs contain the same list of switches, the entire set of switches constitutes one CFS fabric. When this is the case, the merge status should always show success at all switches.

Example:

If the list of switches in the show cfs merge status name command output is shorter than that of the show cfs peers name command output, then the fabric is partitioned into multiple CFS fabrics and the merge status may show that the merge has failed, is pending, or is waiting.

Merge failure troubleshooting

During a merge, the merge managers in the merging fabrics exchange their configuration databases with each other. The application on one of the fabrics merges the information, decides if the merge is successful, and informs all switches in the combined fabric of the status of the merge.

When a merge is successful, the merged database is distributed to all switches in the combined fabric and the entire new fabric remains in a consistent state. A merge failure indicates that the merged fabrics contain inconsistent data that could not be merged.

If a new switch is added to the fabric and the merge status for any application shows In Progress for a prolonged period of time, then there may be an active session for that application in a switch. Check the lock status for that application on all the switches by using the show cfs lock command. If any locks exist, the merge does not proceed. Commit the changes or clear the session lock so that the merge proceeds.

Note Merge failures must be analyzed correctly. Exercise caution when choosing a switch for blank commit. Small configurations may wipe out the large configurations.

Recovering from a Merge Failure with the CLI

To recover from a merge failure using the CLI, perform the following steps:

Step 1 To identify a switch that shows a merge failure, enter the show cfs merge status name <application-name> command.

Example:

Step 2 For a more detailed description of the merge failure, enter the show cfs internal session-history name <application name> detail command.

Example:

Step 3 Enter configuration mode and enter the commit command for the application to restore all peers in the fabric to the same configuration database.

Example:

Lock failure troubleshooting

In order to distribute a configuration in the fabric, a lock must first be acquired on all switches in the fabric. Once accomplished, a commit can be issued which distributes the data to all switches in the fabric before releasing the lock.

When a lock has been acquired by another application peer, you cannot commit new configuration changes. This is a normal situation and you should postpone any changes to an application until the lock is released. Use the troubleshooting steps in this section only if you believe the lock has not been properly released.

A lock occurs when an administrator configures a change for a CFS-enabled application. If two administrators on the same switch attempt to configure the same application, only one administrator is given the lock. The other administrator is prevented from making changes to that application until the first administrator commits a change or discards any changes. Use the show cfs lock name command to determine the name of the administrator who holds the lock for an application. You should check with that administrator before clearing the lock.

A CFS lock can also be held by another switch in your fabric. Use the show cfs peers name command to determine all the switches that participate in the CFS distribution for the application. Then use the show cfs lock name command on each switch to determine who owns the CFS lock for that application. You should check with that administrator before clearing the lock. Use the CFS abort option to release the lock without distributing the data to the fabric.

Resolving lock failure issues using the CLI

To resolve a lock failure using the CLI, perform the following steps:

Step 1 Enter the show cfs lock name <name> command to determine the lock holder.

Example:

Step 2 For a detailed description of the lock failure, enter the show cfs internal session-history name application <name> detail command.

Example:

Step 3 If the lock is being held by a remote peer, eneter the application-name commit command or an application-name abort command at that switch.

Example:

An example of the <application-name> commit command follows:

Example:

An example of the <application-name> abort command follows:

System state inconsistent and locks being held

An inconsistent system state occurs for one of the following situations:

• When locks are not held on all of the switches in the fabric.
• When locks are held on all switches in the fabric, but a session does not exist with the lock holding the switch.

In either case, it is necessary to use the clear option to release the locks.

Clearing locks using the CLI

When a lock is being held on a remote peer and entering the <application-name> commit command or the <application-name> abort command does not clear the lock, issue the clear <application-name> session command to clear all locks in the fabric. After all locks are cleared, a new distribution must be started to restore all the switches in the fabric to the same state.

Example:

Distribution status verification

After configuring an application and committing the changes, you may want to verify that CFS is distributing the configuration change throughout the fabric or VSAN.

Verifying distribution using the CLI

Use the show cfs lock name <application-name> command to determine if a distribution is in progress on the fabric. If the application does not show in the output, the distribution has completed.

Example:

CFS regions troubleshooting

The following rules apply to CFS Regions:

• When using CFS Regions, an application on a given switch can only belong to one region at a time.
• CFS Regions are only applicable to applications within the physical scope. You cannot create a CFS Region in the logical scope of an application.
• Assigning a region to an application takes precedence in distribution over its initial physical scope.
• CFS Regions configuration is not supported for deregistered applications (conditional services) or a physical scope application that is currently locked.
• Regions 1 through 200 are available for user configuration. Regions 201 through 255 are reserved regions and are not available for user configuration.

Distribution failure

To resolve a configuration distribution failure to all switches for a CFS Region, perform the following steps:

Step 1 Verify that application distribution is enabled. For more information, see “Overview” section.

Step 2 Verify that the application is in the same region on all switches.

Using the CLI from each switch, enter the show cfs <application> name <application-name> command.

Example (for device-alias application):

Example (application is capable of being merged; application is in Region Default):

Example (application is capable of being merged; application is in Region 1):

Regions for conditional service

When a conditional service goes down (deregisters with CFS), it loses its region configuration. When the conditional service is restarted, it is automatically placed into the default region. To avoid this situation, reconfigure the appropriate region information for the conditional service before starting it again.

Changing regions

If you move an application from one region to another, you might encounter a database mismatch when attempting a merge. To identify and resolve the conflicts, see “Merge failure troubleshooting” section.

Note When an application is moved from one region to another (including the default region), it loses all history.

Overview

Most VSAN problems can be avoided by following the best practices for VSAN implementation.

However, if necessary, you can use the fabric analysis tool in Fabric Manager to verify different categories of problems such as VSANs, zoning, FC domain, admin issues, or switch-specific or fabric-specific issues.

Fabric Manager provides the configuration consistency check tool.

To use the Fabric Configuration option to analyze the configuration of a switch, follow these steps:

Step 1 From the Fabric Manager tools menu, choose Health > Fabric Configuration.

The Fabric Configuration Analysis dialog box appears.

Step 2 Determine whether you want to compare the selected switch to another switch or to a policy file.

• To compare the selected switch to another switch, select Policy Switch and then select a switch from the drop-down list of switches.
• To make a policy file comparison, select Policy File and then click the button on the right to browse your file system and select a policy file (*.XML).

Step 3 Click Rules to set the rules to apply when running the Fabric Configuration Analysis tool.

The Rules window appears.

Step 4 Change the existing rules as appropriate and click OK.

Step 5 Click Compare to have the system to compare the configuration.

The results of the analysis are displayed.

Step 6 In the Resolve column, select the issues that you want to resolve.

Step 7 Click Resolve Issues to resolve the identified issues.

Step 8 Click Clear to remove the contents of the window.

Step 9 Click Close to complete the operation and close the window.

For more information about the configuration consistency check tool, see the Cisco DCNM Fundamentals Guide, Release 5.x.

Note When suspending or deleting VSANs, make sure that you suspend and unsuspend one VSAN at a time. You should wait a minimum of 60 seconds after you enter the vsan suspend command before you enter any other configuration command. If you fail to wait, some Fibre Channel interfaces or member ports in a port channel might become suspended or error-disabled.

Troubleshooting a SAN problem involves gathering information about the configuration and connectivity of individual devices as well as the status of the entire SAN fabric.

VSAN Troubleshooting Activities

Common troubleshooting tools in Fabric Manager

Verify the VSAN with the following Fabric Manager procedures:

• To view the VSAN configuration in the Information pane, select Fabricxx > VSANxx.
• To view the VSAN members, select Fabricxx > VSANxx, then click the Host or Storage tab in the Information pane.
• To view the FC domain configuration in the Information pane, select Fabricxx > VSANxx > Domain Manager.

Common troubleshooting CLI commands

Use the following CLI commands to display VSAN, FC domain, and FSPF information:

Checklist

Check for the following:

• Verify the domain parameters for switches in the VSAN.
• Verify the physical connectivity for any problem ports or VSANs.
• Verify that both devices are in the name server.
• Verify that both end devices are in the same VSAN.
• Verify that both end devices are in the same zone.

Nexus 5000 trunk port does not connect to upstream SAN switch

The Nexus 5000 trunk port does not connect to the upstream SAN switch because:

• Status of the trunk port connected to the upstream switch is isolated.
• The switch port trunk mode is enabled on both sides.
• Physical cabling has been checked and verified.
• Ports are up on both switches.

By examining the interface state and querying the interface, the issue is displayed as shown in the following example.

Example:

Possible Cause

The VSAN allow list for both interfaces is not the same. Specifically, there is no common VSAN allowed on both interfaces.

This situation might be caused by the following:

• No common VSANs on both switches.
• The trunk allowed VSAN members that do not contain common members.

In the example, the trunk VSAN allow list on the Nexus 5000 and MDS FC interfaces do not match.

Solution

Determine the connected ports and resolve the allowed VSANs on the trunk for both FC interfaces.

Example:

Nexus 5000 E port (non-trunking) does not connect to upstream SAN switch

The Nexus 5000 E port does not connect to the upstream SAN switch because:

• The status of the interconnected non-trunking E ports shows that the status is up. However, all Fibre Channel services are not working between the switches.
• Devices in the same VSAN do not appear in the FCNS database for both switches.
• The show topology command does not list peer switch information.
• Zones show members are not logged in.

Example:

The FC topology does not show a valid peer interface.

Example:

The storage and hosts are in the correct VSAN.

Example:

Possible Cause

The error is displayed by the show interface brief command and the show vsan membership command. They show that the E port on one switch is in the wrong VSAN.

The non-trunking E port on one switch is in the wrong VSAN. (VSAN 100 is the correct VSAN.)

Example:

Solution

Move the non-trunking E-port into VSAN 100.

Example:

The zone set is now active and the FC topology is correct.

Example:

Communication problem between host and storage devices

The communication problem between host and storage devices is because:

• Zones are active.
• Both host and storage are logged into the SAN.
• The storage port is not logged into the active zone set.

Example:

Possible Cause

The host or storage port are in the wrong VSAN.

Example:

Solution

Move the storage port to the correct VSAN. (VSAN 100 is the correct VSAN in the example.).

Example:

VSAN is down between switches

The VSAN is down between switches because:

• VSAN is configured on both switches.
• Trunk allow list allows the VSAN.
• VSAN reported to be down (Initializing state).
• Zones are active.
• Both host and storage are logged into the SAN.

In this failure, the storage port is not logged into the active zone set.

After examining the interface, the error can be seen as in the following example.

Example:

Possible Cause

The VSANs might have the same static Domain ID configured.

Example:

Solution

Change the Domain ID on one of the VSANSs.

Example:

Identifying physical layer issues

To troubleshoot physical layer issues with Fibre Channel SFP optics, use the following command:

In the following example, you can see that the results of the command contains useful information such as supported speed, nominal bit rate, and link lengths supported for the SFP.

Example:

The command also provides detailed SFP diagnostic information and warnings and alarms, if any.

Example:

Two example outputs from the command follow. The first shows a low alarm for Rx Power. The second shows low alarms for Tx, Rx, and Current. The interface for the second example was in an Error Disabled state due to the bit error rate being too high.

Low Alarm for RxPower

Low Alarms for Current, Tx Power and R x Power

In the following example that the command does not provide detailed transceiver information for Twinax (copper).

Displaying FcoE bound Ethernet interface counters

The show interface ethernet command, has two versions, brief and detailed. Examples of each follow.

Brief Version

Example:

Note Ensure that the jumbo frames are incrementing, as well as RX or TX pause frames counters, if any. Tx might indicate a congestion problem.

Detailed Version

The output of the detailed version of the show interface ethernet command is shown in different parts in the following example. It includes both normal traffic counters, as well as counters for physical layer and protocol errors. These counters should be monitored anytime there is a connectivity or performance issue.

Example:

Understanding Fibre Channel interface counters

The show interface command is very useful when troubleshooting physical layer or performance issues with a Fibre Channel interface.

In the output of the command, observe the input/output counters and any input/output discards or errors.

When input discards increment, the FC packet does not have a valid route in the Forwarding Information Base (FIB). All packets not having a route are considered discards and sent to the supervisor. These packets are NOT dropped; however, they are policed before being sent to the supervisor. You should also check the MAC ASIC for errors.

When output discards increment, packets are timing out in egress because the egress is too slow. Check the attached device because it may be a slow draining receiver that is not responding, or not replenishing buffer credits. This causes back pressure to occur on the Nexus 5000 FC interface.

Example:

Troubleshooting Fibre Channel MAC issues

The show hardware command is very useful when troubleshooting FC physical layer issues.

The output of the command contains the following useful information:

• Physical layer information

• Performance information

• Class 3 normal traffic counters

• Fibre Channel primitive sequences

Example:

When troubleshooting FC performance problems, review the R_RDY, Link Reset, and Link Reset Response counters. These help determine buffer to buffer credit problems that could lead to performance issues.

Troubleshooting Fibre Channel forwarding issues

To troubleshoot Fibre Channel forwarding issues, it is important to know that GATOS is the MAC/Forwarding ASIC on the Nexus 5000 switch. This section describes commands specific to this ASIC.

Each Fibre Channel interface is assigned a GATOS number. To understand forwarding issues, you must find the GATOS number for the specific FC interface.

Consider the following example:

In the following part of the example, notice that gatos_num 13 is the GATOS instance for Fibre Channel interface 2/1:

In the following part of the example, notice that the command also provides forwarding drop and discard informatio:

You can also display GATOS errors for the GATOS instance that corresponds to the FC interface. In the following part of the example, notice that the command only shows non-zero counters.

In the first of the two parts, drops and discards were described. Notice that the drop and discard counters are separate for vEthernet and VFC interfaces. Review the output in the second example to help correlate the reason for the drops.

In the following part of the example, notice the drops in the second line:

In the following part of the example, notice that the FcoE counters are separate:

In the following part of the example, notice that the command helps find the cause of the drops: