Page 1 S e n d d o c u m e n t c o m m e n t s t o n e x u s 5 k - d o c f e e d b a c k @ c i s c o . c o m . Cisco Nexus 5000 Series Troubleshooting...
Page 2 Cisco and/or its affiliates in the United States and certain other countries. Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at www.cisco.com/go/trademarks.
Page 3: Table Of Contents
Troubleshooting QoS Issues Policy Maps Improper Configurations Registers and Counters 4-10 Troubleshooting SAN Switching Issues Overview Zoning SAN Port Channels 5-13 FC Services 5-16 Cisco Fabric Services 5-31 VSANs 5-40 Registers and Counters 5-48 Cisco Nexus 5000 Series Troubleshooting Guide OL-25300-01...
Page 4 S e n d d o c u m e n t c o m m e n t s t o n e x u s 5 k - d o c f e e d b a c k @ c i s c o . c o m . Troubleshooting Security Issues Roles Troubleshooting System Management Issues SNMP Logging Traps Troubleshooting Virtual Port Channel Issues Improper Configurations Troubleshooting Config-Sync Issues Commit Failure Import Failure Merge Failure Switch-profile Deletion Failure Verify Failure Cisco Nexus 5000 Series Troubleshooting Guide OL-25300-01...
Page 5 Organization, page v • Document Conventions, page vi Related Documentation, page vii • Audience This publication is for experienced users who configure and maintain Cisco Nexus 1000V Series switch. Organization This reference is organized as follows: Chapter Description Troubleshooting Overview...
Page 6: Document Conventions
Chapter Description Troubleshooting Security Issues Describes how to identify and resolve problems that can occur with security in the Cisco Nexus 5000 Series switch. Troubleshooting System Management Describes how to identify and resolve problems that can Issues occur with system management and the Cisco Nexus 5000 Series switch.
Page 7: Related Documentation
Preface Related Documentation Documentation for Cisco Nexus 5000 Series Switches and Cisco Nexus 2000 Series Fabric Extenders is available at the following URL: http://www.cisco.com/en/US/products/ps9670/tsd_products_support_series_home.html The following are related Cisco Nexus 5000 Series and Cisco Nexus 2000 Series Fabric Extender documents:...
Page 8 Preface Regulatory Compliance and Safety Information for the Cisco Nexus 5000 Series Switches and Cisco Nexus 2000 Series Fabric Extenders Licensing Guide Cisco NX-OS Licensing Guide Command References Cisco Nexus 5000 Series Command Reference Technical References Cisco Nexus 5000 Series and Cisco Nexus 2000 Series Fabric Extender MIBs Reference...
Page 9: Troubleshooting Overview
C H A P T E R Troubleshooting Overview This chapter introduces the basic concepts, methodology, and general troubleshooting guidelines for problems that may occur when configuring and using the Cisco Nexus 5000 Series switch. This chapter includes the following sections: Troubleshooting Basics •...
Page 10 6 08:00:51 TTPSW-5020SF1 %$ VDC-1 %$ %ETHPORT-2-IF_DOWN_ERROR_DISABLED: Interface Ethernet103/1/1 is down (Error disabled. Reason:BPDUGuard) 2010 Nov 6 14:56:18 TTPSW-5020SF1 %$ VDC-1 %$ %SYSMGR-2-SERVICE_CRASHED: Service "clis" (PID 4155) hasn't caught signal 11 (core will be saved). Cisco Nexus 5000 Series Troubleshooting Guide OL-25300-01...
Page 11: Best Practices
Best practices are the recommended steps you should take to ensure the proper operation of your switch. Maintain a consistent Cisco NX-OS release across all your Cisco Nexus 5000 switches. • • Refer to the release notes for your Cisco SAN-OS release for the latest features, limitations, and caveats. • Enable system message logging.
Page 12: Fabric Manager Tools And Cli Commands
Turn-off pagination for command output Stream Editor Count words, lines, characters begin Begin with the line that matches count Count number of lines exclude Exclude lines that match include Include lines that match Cisco Nexus 5000 Series Troubleshooting Guide OL-25300-01...
Page 13 Jan 01 00:03:26 2005 routing-sw/ Redirecting output of the show tech-support details command Use the tac-pac filename command to redirect the output of the show tech-support details command to a file and then gzip the file. Cisco Nexus 5000 Series Troubleshooting Guide OL-25300-01...
Page 14 You can use logging through the CLI or Device Manager. In the following examples, the logging command and the Device Manager display severity information: Viewing Severity Information with the CLI switch(config)# show logging Cisco Nexus 5000 Series Troubleshooting Guide OL-25300-01...
Page 15 Node to switch or node to node traffic can be seen via this method. Ethanalyzer Ethanalyzer is a Cisco NX-OS protocol analyzer tool based on the Wireshark open source code. This tool is a command-line version of Wireshark that captures and decodes packets. You can use Ethanalyzer to troubleshoot your network and analyze the control-plane traffic.
Page 16 Filters the types of packets to capture. ethanalyzer local sniff-interface display-filter Filters the types of captured packets to display. ethanalyzer local sniff-interface decode-internal Decodes the internal frame header for Cisco NX-OS. Do not use this option if you plan to Note analyze the data using Wireshark instead of NX-OS Ethanalyzer.
Page 17 Cisco SwitchProbe, a Fibre Channel Analyzer, or other Remote Monitoring (RMON) probes. SPAN sources refer to the interfaces from which traffic can be monitored. The Cisco Nexus 5000 Series switch supports Ethernet, virtual Ethernet, Fibre Channel, virtual Fibre Channel, port channels, SAN port channels, VLANs, and VSANs as SPAN sources.
Page 18 For VLAN or VSAN SPAN sources, all active ports in the source VLAN or VSAN are included as source ports. The Cisco Nexus 5010 switch supports a maximum of two egress SPAN source ports. This limit does • not apply to the Cisco Nexus 5020 Switch and the Cisco Nexus 5548 switch.
Page 19 Nexus 5020 DS-PAA FC3/1 FC3/2 Verifying the SPAN Session Example: switch# show monitor session SESSION STATE REASON DESCRIPTION ------- ----------- ---------------------- -------------------------------- The session is up Cisco Nexus 5000 Series Troubleshooting Guide 1-11 OL-25300-01...
Page 20 You must have administrator privileges to run debugs. Debugs can only be run from the CLI. Debug Logging Set the log file as CiscoLive_debugs, using the debug logfile command. Then, use the show debug command to see name of the debug file. Cisco Nexus 5000 Series Troubleshooting Guide 1-12 OL-25300-01...
Page 21 • Cisco Discover Protocol Cisco Discover Protocol (CDP) version 2 is applied to the physical Ethernet interface and only works when enabled at both ends of the link. LLDP standard is derived from CDP. CDP is used to verify proper connectivity to correct network devices, very useful at switch deployment.
Page 22: Failover
S e n d d o c u m e n t c o m m e n t s t o n e x u s 5 k - d o c f e e d b a c k @ c i s c o . c o m . Device ID:TM-6506-1 System Name: Interface address(es): IPv4 Address: 11.1.1.1 Platform: cisco WS-C6506, Capabilities: Router Switch IGMP Filtering Interface: Ethernet1/4, Port ID (outgoing port): TenGigabitEthernet1/2 ? Verifies proper port connections Holdtime: 133 sec...
Page 23 When LAN connectivity is lost for a particular VLAN on the uplinks, the VLAN is also brought down on the host-facing link. Dedicating a VLAN solely for FCoE traffic helps with shutting down non-FCoE traffic to and from the host-facing link without disrupting FCoE traffic from the same host. Cisco Nexus 5000 Series Troubleshooting Guide 1-15 OL-25300-01...
Page 24 S e n d d o c u m e n t c o m m e n t s t o n e x u s 5 k - d o c f e e d b a c k @ c i s c o . c o m . Cisco Nexus 5000 Series Troubleshooting Guide...
Page 25: Troubleshooting Fcoe Issues
Ethernet connection. FCoE requires that the underlying Ethernet be full duplex and provides lossless behavior for Fibre Channel traffic. This chapter describes how to identify and resolve problems that can occur with FCoE in the Cisco Nexus 5000 Series switch.
Page 26 Use the show lldp interface ethernet 1/4 command. Example: switch# show lldp interface ethernet 1/4 Interface Information: Enable (tx/rx/dcbx): Y/Y/Y Port Mac address: 00:0d:ec:d5:a3:8b Peer's LLDP TLVs: Type Length Value ---- ------ ----- Cisco Nexus 5000 Series Troubleshooting Guide OL-25300-01...
Page 27 00 01 00 00 32 32 00 00 00 00 00 00 02 06 06 00 00 c0 00 08 01 08 10 00 00 c0 00 89 06 00 1b 21 08 89 14 00 1b 21 08 LLDP TLV type:END of LLDP PDU LLDP TLV Length: 0 Cisco Nexus 5000 Series Troubleshooting Guide OL-25300-01...
Page 28 DCBX pkt stats: Total frames out: 15383 Total Entries aged: 97 Total frames in: 15039 DCBX frames in: 15033 Total frames received in error: 6 Total frames discarded: 6 Total TLVs unrecognized: 0 Cisco Nexus 5000 Series Troubleshooting Guide OL-25300-01...
Page 29 An option exists to force PFC mode on an interface. Use the inerfacet ethernet 1/21 command and the priority-flow-control mode command to force the PFC mode. Example: switch(config)# int eth1/21 switch(config-if)# priority-flow-control mode ? Cisco Nexus 5000 Series Troubleshooting Guide OL-25300-01...
Page 30 The FCoE class-fcoe system class is not enabled in the QoS configuration. Solution For a Cisco Nexus 5548 switch, the FCoE class-fcoe system class is not enabled by default in the QoS configuration. Before enabling FCoE, you must include class-fcoe in each of the following policy types: Network-QoS •...
Page 31 MAC address descriptor may be incorrect. (This is the address the CNA uses as the DMAC when it • sends responses.) Use the show platform software fcoe_mgr info interface vfc<id> command to view the status of the FIP solicitation. Cisco Nexus 5000 Series Troubleshooting Guide OL-25300-01...
Page 32 When FIP keepalives (FKA) are missed for a period of approximately 22 seconds, this means that approximately three FKAs are not continuously received from the host. Missed FKAs can occur for many reasons, including congestion or link issues. Cisco Nexus 5000 Series Troubleshooting Guide OL-25300-01...
Page 33 FCoE VLANs from membership. This ensures to limit the scope of the Spanning Tree Protocol for FCoE VLANs to UF links only. Separate FCoE VLANs must be used for FCoE in SAN-A and SAN-B. • Cisco Nexus 5000 Series Troubleshooting Guide OL-25300-01...
Page 34 Determine if an existing driver is already installed on the host OS. Step 3 Ensure that the latest driver is installed from the CNA vendor support page or the host OS support page. Step 4 Cisco Nexus 5000 Series Troubleshooting Guide 2-10 OL-25300-01...
Page 35 Priority flow control (PFC) is not negotiated with FCOE-capable adapters (CNA). This causes packet drop to be noticed on FCoE traffic from the servers. Possible Causes The CNA may not support DCBX and the PFC TLV is not negotiated. Solution Cisco Nexus 5000 Series Troubleshooting Guide 2-11 OL-25300-01...
Page 36 For a few iterations, use the show queuing interface ethx/x command to check the pause status. • Example: Per-priority-pause status : Rx (Inactive), Tx (Inactive) Cisco Nexus 5000 Series Troubleshooting Guide 2-12 OL-25300-01...
Page 37 For a few iterations, check using the show queuing interface ethx/x command to check the pause status. PFC frames are a MAC-level type of packet and cannot be viewed using the SPAN feature. Analyzer Note in-line is required to actually see the PFC frames on the wire. Cisco Nexus 5000 Series Troubleshooting Guide 2-13 OL-25300-01...
Page 38 The error-disable recovery interval is 30. • If there is a consistent port error-disable condition due to the pause rate limit, determine if the issue is that the server is too slow. Replace the slow server. Cisco Nexus 5000 Series Troubleshooting Guide 2-14 OL-25300-01...
Page 39: Registers And Counters
The PFC frame count is incremented using the show int ethx/x flowcontrol command. This is a known Note bug. Registers and Counters Interface level errors To view any interface level errors, use the show interface counters errors command. Example: switch# show interface counters errors ------------------------------------------------------------------------------- Cisco Nexus 5000 Series Troubleshooting Guide 2-15 OL-25300-01...
Page 40 Tx Packets from 0 to 64 bytes: Tx Packets from 65 to 127 bytes: 112452 Tx Packets from 128 to 255 bytes: 60461 Tx Packets from 256 to 511 bytes: Tx Packets from 512 to 1023 bytes: Cisco Nexus 5000 Series Troubleshooting Guide 2-16 OL-25300-01...
Page 41 1/11 counters brief ------------------------------------------------------------------------------------ Interface Input Rate (avg) Output Rate (avg) ---------------- ----------------- Rate Total Rate Total Rate averaging MB/s Frames MB/s Frames interval (seconds) ------------------------------------------------------------------------------------ Ethernet 1/11 Cisco Nexus 5000 Series Troubleshooting Guide 2-17 OL-25300-01...
Page 42 S e n d d o c u m e n t c o m m e n t s t o n e x u s 5 k - d o c f e e d b a c k @ c i s c o . c o m . Cisco Nexus 5000 Series Troubleshooting Guide...
Page 43: Troubleshooting Layer 2 Switching Issues
Layer 2 is the Data Link Layer of the Open Systems Interconnection model (OSI model) of computer networking. This chapter describes how to identify and resolve problems that can occur with Layer 2 switching in the Cisco Nexus 5000 Series switch. This chapter includes the following sections: MAC Address Table •...
Page 44 For example, the VLAN may not have been enabled on any of the interfaces other than the one on which data is coming in on. Alternatively, the outgoing interfaces may be down. If this is the case, you need to bring up those interfaces. Cisco Nexus 5000 Series Troubleshooting Guide OL-25300-01...
Page 45: Spanning Tree Protocol
<id> • Solution Check for a correct STP convergence and for STP port states across all switches in the topography. • Also confirm that there are no disputes or incorrect port states. Cisco Nexus 5000 Series Troubleshooting Guide OL-25300-01...
Page 46 This is supposed to prevent loops when unidirectional link failures occur. However, the port is put into a BLK* (Loop_Inc) state. Use the following commands to confirm the details of the STP port state for the port: show spanning-tree interface <id> detail • show spanning-tree interface <id> • Cisco Nexus 5000 Series Troubleshooting Guide OL-25300-01...
Page 47: Multicast
Review the output from the following commands: show ip igmp snooping groups vlan 1001 • show mac address-table multicast vlan 1001 igmp-snooping • • show platform fwm info vlan 1001 all_macgs verbose Solution Cisco Nexus 5000 Series Troubleshooting Guide OL-25300-01...
Page 48: Vlans
An internal VLAN range is used. Solution Use a VLAN number that is not being reserved for internal use. The VLAN range of 3968 to 4047 is reserved for internal use. Note Example: switch(config)# vlan ? Cisco Nexus 5000 Series Troubleshooting Guide OL-25300-01...
Page 49 Otherwise, fix the configuration mismatch on the Nexus 5000 pair: Example: switch# sh vpc consistency-parameters global Legend: Type 1 : vPC will be suspended in case of mismatch Name Type Local Value Peer Value ------------- ---- ---------------------- ----------------------- Cisco Nexus 5000 Series Troubleshooting Guide OL-25300-01...
Page 50 For the Nexus 5000, the maximum number of active VLANs and VSANs per switch is 512 (31 reserved for VSAN; remainder reserved for VLAN). Use the show resource vlan command to determine the number of available VLANs. Example: switch(config)# show resource vlan Cisco Nexus 5000 Series Troubleshooting Guide OL-25300-01...
Page 51 Use the show feature command to determine which features are enabled. Example: switch(config)# feature private-vlan switch(config)# show feature Feature Name Instance State -------------------- -------- -------- tacacs disabled lacp enabled interface-vlan enabled private-vlan enabled udld enabled enabled fcoe disabled enabled Cisco Nexus 5000 Series Troubleshooting Guide OL-25300-01...
Page 52: Registers And Counters
The error counter, shown in the following example, increments when the ingress port is the only port in the VLAN. Example (same Gatos instance as in earlier example): switch# show platform fwm info gatos-errors 7 Printing non zero Gatos error registers: DROP_SRC_MASK_TO_NULL Cisco Nexus 5000 Series Troubleshooting Guide 3-10 OL-25300-01...
Page 53 Mcast pkts sent to the cross-bar Ucast pkts received from the cross-bar Pkts sent to the port <b> Pkts discarded on ingress : 0 </b> Per-priority-pause status : Rx (Inactive), Tx (Inactive) Cisco Nexus 5000 Series Troubleshooting Guide 3-11 OL-25300-01...
Page 54 A good frame is a frame that does not have a CRC error or other kind of error • A bad frame is a frame that has a CRC error or other kind of error • All counters include MAC Control frames where applicable. Cisco Nexus 5000 Series Troubleshooting Guide 3-12 OL-25300-01...
Page 55 Number of 802.3x PAUSE frames transmitted. TX_USER_PAUSE Number of transmitted priority flow control frames. TX_FRM_ERROR Number of frames with cl_im_tx_err set to 1 at EOP. TX_OCTETSOK Total byte count of good frames. Cisco Nexus 5000 Series Troubleshooting Guide 3-13 OL-25300-01...
Page 56 Number of good frames received that are greater than CFG_xg_rx_stats_max_frame_len. RX_TOOLONG Number of frames (good and bad frames) received that are greater than CFG_xg_rx_stats_max_frame_len. RX_DISCARD The value of this counter is always 0. Cisco Nexus 5000 Series Troubleshooting Guide 3-14 OL-25300-01...
Page 57 Number of bad frames received with frame length greater than CFG_xg_rx_stats_max_frame_len. RX_PAUSE Number of good 802.3x MAC control frames received. RX_USER_PAUSE Number of good priority flow control frames received. RX_OCTETSOK Total byte count of good frames. Cisco Nexus 5000 Series Troubleshooting Guide 3-15 OL-25300-01...
Page 58 S e n d d o c u m e n t c o m m e n t s t o n e x u s 5 k - d o c f e e d b a c k @ c i s c o . c o m . Cisco Nexus 5000 Series Troubleshooting Guide...
Page 59: Troubleshooting Qos Issues
QoS uses policies and flow control to classify the network traffic, police and prioritize the traffic flow, and provide congestion avoidance. This chapter describes how to identify and resolve problems that can occur with QoS in the Cisco Nexus 5000 Series switch.
Page 60: Improper Configurations
The MTU value for the traffic with CoS 7 is set to a fixed value. You must check that the incoming traffic is marked with CoS 7. Use any CoS value other than 7 to avoid this limitation. Cisco Nexus 5000 Series Troubleshooting Guide OL-25300-01...
Page 61 Nexus 5000. Example: //class-map for global qos policy-map, which will be used to create CoS-queue mapping.// class-map type qos voice-global match cos 5 class-map type qos critical-global match cos 6 class-map type qos scavenger-global Cisco Nexus 5000 Series Troubleshooting Guide OL-25300-01...
Page 62 //This policy-map type network-qos will be applied under “system qos” to define the MTU, marking and queue-limit(not configured here).// policy-map type network-qos NetworkQoS-5020 class type network-qos Voice set cos 5 class type network-qos Video-Signalling set cos 4 mtu 9216 class type network-qos Scavenger Cisco Nexus 5000 Series Troubleshooting Guide OL-25300-01...
Page 63 100/1/1 Ethernet100/1/1 queuing information: Input buffer allocation: Qos-group: 0 (shared) frh: 2 drop-type: drop cos: 0 1 2 3 4 5 6 Cisco Nexus 5000 Series Troubleshooting Guide OL-25300-01...
Page 64 NetworkQoS-5020 class type network-qos Voice set cos 5 pause no-drop class type network-qos Video-Signalling set cos 4 mtu 9216 class type network-qos Scavenger set cos 1 mtu 9216 class type network-qos Critical Cisco Nexus 5000 Series Troubleshooting Guide OL-25300-01...
Page 65 1600 Buffer threshold: 271360 bytes Queue limit: Disabled Queue Statistics: queue ------+--------------- 241439087 Port Statistics: tx queue drop --------------- Priority-flow-control enabled: no Flow-control status: qos-group rx pause tx pause masked rx pause -------+-----------+---------+---------+--------------- Cisco Nexus 5000 Series Troubleshooting Guide OL-25300-01...
Page 66 You will get an error if not enough buffers exist to enable the no-drop. Example: class type network-qos s4 pause no-drop ERROR: Module 1 returned status "Not enough buffer space available. Please change your configuration and re-apply" Solution Cisco Nexus 5000 Series Troubleshooting Guide OL-25300-01...
Page 67 Use the following commands to enable PFC on CoS 4 only, instead of on all CoS values under the class-ip-multicast class. Policy-map type network-qos system • Class type network-qos class-ip-multicast • Pause no-drop pfc-cos 4 • Cisco Nexus 5000 Series Troubleshooting Guide OL-25300-01...
Page 68: Registers And Counters
Use the following commands under interface ethx/y to enable link pause: flowcontrol receive on • flowcontrol send on • Registers and Counters The following are the commands to access various registers and counters: Cisco Nexus 5000 Series Troubleshooting Guide 4-10 OL-25300-01...
Page 69 X asic Y ASIC/GATOS. Shows the internal mapping tables, such as the ext-cos to qos-group, show platform afm in map-tbls qos-group to int-cos, and int-cos to class_id maps. Cisco Nexus 5000 Series Troubleshooting Guide 4-11 OL-25300-01...
Page 70 Displays statistics of MAC level traffic and pause statistics of NIF of show plat soft redwood rmon 6 nif0 eth103/1/37. Displays statistics of MAC level traffic and pause statistics of iHIF for show plat soft redwood rmon 6 hif5 eth103/1/37. Cisco Nexus 5000 Series Troubleshooting Guide 4-12 OL-25300-01...
Page 71 <gatos> index <fc num> pifTable Nexus 5000 MTU programming Use the following command: show hardware internal gatos asic 0 registers match bm_port_CFG.*_max Nexus 5000 interrupt Use the following commands: debug hardware internal gatos asic 0 clear-interrupt Cisco Nexus 5000 Series Troubleshooting Guide 4-13 OL-25300-01...
Page 72 Buffer usage and packet drop debugging on N2K-C2232P FEX Use the following command: show platform software qosctrl asic 0 0 Cisco Nexus 5000 Series Troubleshooting Guide 4-14 OL-25300-01...
Page 73: Troubleshooting San Switching Issues
Troubleshooting SAN Switching Issues A storage area network (SAN) is a network of storage devices that provide data storage for servers. This chapter describes how to identify and resolve problems that can occur with a SAN and the Cisco Nexus 5000 Series switch.
Page 74 Interface: fc2/1, State: Failed(NPIV is not enabled in upstream switch) Interface: fc2/2, State: Failed(NPIV is not enabled in upstream switch) Interface: san-port-channel 200, State: Down If NPIV is disabled, then enable NPIV on the core switch. • Example: switch(config)# feature npiv Cisco Nexus 5000 Series Troubleshooting Guide OL-25300-01...
Page 75 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 Cisco Nexus 5000 Series Troubleshooting Guide OL-25300-01...
Page 76 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: switch# show npv status npiv is enabled Cisco Nexus 5000 Series Troubleshooting Guide OL-25300-01...
Page 77 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 Cisco Nexus 5000 Series Troubleshooting Guide OL-25300-01...
Page 78 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 Cisco Nexus 5000 Series Troubleshooting Guide OL-25300-01...
Page 79: Zoning
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: Determine which switch (domain/ip address) has the lock. Step 1 Cisco Nexus 5000 Series Troubleshooting Guide OL-25300-01...
Page 80 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: Cisco Nexus 5000 Series Troubleshooting Guide OL-25300-01...
Page 81 100 switch(config-zone)# member pwwn 21:00:00:20:37:9e:02:3e switch(config-zone)# member pwwn 21:00:00:c0:dd:12:04:ce Use the show zone vsan <vsan-id> command to verify that host and storage are now in the same zone. Cisco Nexus 5000 Series Troubleshooting Guide OL-25300-01...
Page 82 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. Cisco Nexus 5000 Series Troubleshooting Guide 5-10 OL-25300-01...
Page 83 Number of IVR zones: 0 Number of IPS zones: 0 Formatted size: 92 bytes / 2048 Kb • Use the show zone internal change event-history vsan <vsan-id> command to determine the zone set activation problem. Cisco Nexus 5000 Series Troubleshooting Guide 5-11 OL-25300-01...
Page 84 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: Cisco Nexus 5000 Series Troubleshooting Guide 5-12 OL-25300-01...
Page 85: San Port Channels
<slot/port> show port internal event-history interface fc <slot/port> show san-port-channel internal event-history errors show logging log | grep fc <slot/port> show san-port-channel internal event-history all show tech-support detail > bootflash:showtechdet Cisco Nexus 5000 Series Troubleshooting Guide 5-13 OL-25300-01...
Page 86 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 Cisco Nexus 5000 Series Troubleshooting Guide 5-14 OL-25300-01...
Page 87 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: Cisco Nexus 5000 Series Troubleshooting Guide 5-15 OL-25300-01...
Page 88: Fc Services
Unused: 1 - 197 , 200 - 499 , 501 - 4096 (some numbers may be in use by SAN port channels) FC Services This section includes an overview of troubleshooting Cisco Fibre Channel Services followed by a description of common problems and their solutions. Overview Fibre Channel fabrics provide a set of services for its clients, which are the Fibre Channel nodes.
Page 89 0xffffffff FCP_CNTR_NOS_IN 0xffffffff FCP_CNTR_LRR_IN 0xffffffff FCP_CNTR_LINK_RESET_OUT 0xffffffff FCP_CNTR_OLS_OUT 0xffffffff FCP_CNTR_NOS_OUT 0xffffffff FCP_CNTR_LRR_OUT 0xffffffff FCP_CNTR_LINK_FAILURE Possible Cause The FLOGI packet was dropped somewhere in the data path, starting from FC-MAC to FLOGI server. Cisco Nexus 5000 Series Troubleshooting Guide 5-17 OL-25300-01...
Page 90 %FSPF-3-FC2_PROC_ERR: %$VSAN <vsan-id>%$ Error in processing HELLO packet on interface san-port-channel <channel-id>, Error = Bad packet received Solution To resolve a wrong hello interval on an ISL using the NX-OS CLI, perform the following steps. Cisco Nexus 5000 Series Troubleshooting Guide 5-18 OL-25300-01...
Page 91 In the interface configuration mode, change the fspf hello-interval value to match the same values on Step 4 both switches. Example: switch(config)# interface san-port-channel 200 switch(config-if)# fspf hello-interval 40 vsan 200 Verify that the FSPF is in FULL state after the change. Step 5 Cisco Nexus 5000 Series Troubleshooting Guide 5-19 OL-25300-01...
Page 92 Number of packets received : LSU Hello 27 Error packets 4 Number of packets transmitted : LSU Hello 38 Retransmitted LSU Number of times inactivity timer expired for the interface = 0 Cisco Nexus 5000 Series Troubleshooting Guide 5-20 OL-25300-01...
Page 93 Number of times inactivity timer expired for the interface = 0 Possible Cause There is a region mismatch on the switch. The following example shows possible log messages from the show logging command log: Example: Cisco Nexus 5000 Series Troubleshooting Guide 5-21 OL-25300-01...
Page 94 Use the undebug all command to turn off debugging. Step 3 Use the show fspf vsan <vsan-id> command to show FSPF configuration and check the autonomous Step 4 region. Example: switch# show fspf vsan 200 Cisco Nexus 5000 Series Troubleshooting Guide 5-22 OL-25300-01...
Page 95 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:...
Page 96 S e n d d o c u m e n t c o m m e n t s t o n e x u s 5 k - d o c f e e d b a c k @ c i s c o . c o m . • 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.
Page 97 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: Cisco Nexus 5000 Series Troubleshooting Guide 5-25 OL-25300-01...
Page 98 0x621400 detail vsan 2 ------------------------ VSAN:2 FCID:0x621400 ------------------------ port-wwn (vendor) :21:01:00:1b:32:a3:d7:2c [z7095ib-1_T] node-wwn :20:01:00:1b:32:a3:d7:2c class node-ip-addr :0.0.0.0 :ff ff ff ff ff ff ff ff fc4-types:fc4_features symbolic-port-name symbolic-node-name port-type port-ip-addr :0.0.0.0 fabric-port-wwn :20:d9:00:0d:ec:e0:0e:80 Cisco Nexus 5000 Series Troubleshooting Guide 5-26 OL-25300-01...
Page 99 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.
Page 100 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...
Page 101 FREE @ 159964 usecs after Thu Aug 5 13:35:00 2010 type[2] p_gwrap[(nil)] FREE @ 450507 usecs after Tue Aug 3 14:14:08 2010 0x50c8efc7 current state [TE_FSM_ST_ISOLATED_DM_ZS] RNID info not found. first time elp: 0 Peer ELP Revision: 3 Cisco Nexus 5000 Series Troubleshooting Guide 5-29 OL-25300-01...
Page 102 Current domain ID: 0x2c(44) Local switch configuration information: State: Enabled FCID persistence: Enabled Auto-reconfiguration: Disabled Contiguous-allocation: Disabled Configured fabric name: 20:01:00:05:30:00:28:df Optimize Mode: Disabled Configured priority: 128 Configured domain ID: 0x2c(44) (preferred) Cisco Nexus 5000 Series Troubleshooting Guide 5-30 OL-25300-01...
Page 103: Cisco Fabric Services
Step 6 This is a disruptive operation and disruptive reconfiguration and can affect data traffic. Cisco Fabric Services This section includes an overview of troubleshooting Cisco Fabric Services (CFS) followed by a description of common problems and their solutions. Overview Begin troubleshooting CFS issues by checking the following: •...
Page 104 [Local] 20:00:00:0d:ec:24:5b:c0 172.25.183.123 20:00:00:0d:ec:50:09:00 172.25.183.42 Total number of entries = 3 Note The show cfs peers name <application-name> command displays the peers for all VSANs when applied to a logical application. Example: Cisco Nexus 5000 Series Troubleshooting Guide 5-32 OL-25300-01...
Page 105 Logical [VSAN 1] Merge Status: Success [ Thu Aug 5 11:33:50 2010 ] Local Fabric -------------------------------------------------------------------------------- Domain Switch WWN IP Address -------------------------------------------------------------------------------- 20:00:00:0d:ec:24:5b:c0 172.25.183.123 [Merge Master] 20:00:00:0d:ec:50:09:00 172.25.183.42 20:00:00:0d:ec:da:6e:00 172.25.183.124 Cisco Nexus 5000 Series Troubleshooting Guide 5-33 OL-25300-01...
Page 106 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. Cisco Nexus 5000 Series Troubleshooting Guide 5-34 OL-25300-01...
Page 107 Source WWN Event User Name Session ID -------------------------------------------------------------------------------- Thu Aug 5 11:45:19 2010 20:00:00:0d:ec:da:6e:00 LOCK_ACQUIRED admin 34684 Thu Aug 5 11:45:19 2010 20:00:00:0d:ec:da:6e:00 COMMIT[2] admin 34689 Thu Aug 5 11:45:20 2010 20:00:00:0d:ec:da:6e:00 LOCK_RELEASED Cisco Nexus 5000 Series Troubleshooting Guide 5-35 OL-25300-01...
Page 108 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. Cisco Nexus 5000 Series Troubleshooting Guide 5-36 OL-25300-01...
Page 109 End with CNTL/Z. switch(config)# ntp commit switch(config)# Example: An example of the <application-name> abort command follows: switch# configure terminal Enter configuration commands, one per line. End with CNTL/Z. switch(config)# ntp abort switch(config)# Cisco Nexus 5000 Series Troubleshooting Guide 5-37 OL-25300-01...
Page 110 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. Cisco Nexus 5000 Series Troubleshooting Guide 5-38 OL-25300-01...
Page 111 Example (application is capable of being merged; application is in Region 1): switch# show cfs application name device-alias Enabled : Yes Timeout : 20s Merge Capable : Yes Scope : Physical-fc Region : 1 Cisco Nexus 5000 Series Troubleshooting Guide 5-39 OL-25300-01...
Page 112: Vsans
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. Cisco Nexus 5000 Series Troubleshooting Guide 5-40 OL-25300-01...
Page 113 Click Close to complete the operation and close the window. Step 9 For more information about the configuration consistency check tool, see the Cisco DCNM Fundamentals Guide, Release 5.x. When suspending or deleting VSANs, make sure that you suspend and unsuspend one VSAN at a time.
Page 114 4 16:06:04 2010 version 4.2(1)N1(1) interface fc2/3 switchport mode E switchport trunk allowed vsan 1 no shutdown switch(config-if)# show run interface fc 1/1 !Command: show running-config interface fc1/1 !Time: Wed Aug 4 16:20:07 2010 Cisco Nexus 5000 Series Troubleshooting Guide 5-42 OL-25300-01...
Page 115 Trunk vsans (admin allowed and active) (1,100) Trunk vsans (up) (1,100) Trunk vsans (isolated) Trunk vsans (initializing) switch(config-if)# show interface brief ------------------------------------------------------------------------------- Interface Vsan Admin Admin Status Oper Oper Port Mode Trunk Mode Speed Channel Cisco Nexus 5000 Series Troubleshooting Guide 5-43 OL-25300-01...
Page 116 20:00:00:25:b5:00:20:0e [Host] * fcid 0x5a0000 [pwwn 50:0a:09:81:86:78:39:66] [Storage] switch(config-if)# show zoneset active vsan 100 zoneset name ZoneSet_Host_Storage vsan 100 zone name Zone_Host_Storage vsan 100 * fcid 0x640114 [pwwn 20:00:00:25:b5:00:20:0e] [Host] pwwn 50:0a:09:81:86:78:39:66 [Storage] Cisco Nexus 5000 Series Troubleshooting Guide 5-44 OL-25300-01...
Page 117 * fcid 0x640114 [pwwn 20:00:00:25:b5:00:20:0e] [Host] * fcid 0x5a0000 [pwwn 50:0a:09:81:86:78:39:66] [Storage] switch(config-if)# show topology FC Topology for VSAN 100 : -------------------------------------------------------------------------------- Interface Peer Domain Peer Interface Peer IP Address -------------------------------------------------------------------------------- fc1/2 0x5a(90) fc2/4 172.25.183.124 Cisco Nexus 5000 Series Troubleshooting Guide 5-45 OL-25300-01...
Page 118 * fcid 0x5a0000 [pwwn 50:0a:09:81:86:78:39:66] [Storage] VSAN is down between switches The VSAN is down between switches because: • VSAN is configured on both switches. • Trunk allow list allows the VSAN. Cisco Nexus 5000 Series Troubleshooting Guide 5-46 OL-25300-01...
Page 119 Domain ID --------- ----------------------- 0x52(82) 20:0a:00:0d:ec:da:6e:01 [Local] [Principal] switch(config-vsan-db)# sho interface fc 2/4 | begin Trunk Trunk vsans (admin allowed and active) (1,10,50,100) Trunk vsans (up) (1,10,50,100) Trunk vsans (isolated) Trunk vsans (initializing) Cisco Nexus 5000 Series Troubleshooting Guide 5-47 OL-25300-01...
Page 120: Registers And Counters
Link length supported for 50/125mm fiber is 150 m(s) Link length supported for 62.5/125mm fiber is 70 m(s) cisco extended id is unknown (0x0) no tx fault, no rx loss, in sync state, Diag mon type 104 The command also provides detailed SFP diagnostic information and warnings and alarms, if any.
Page 121 Link length supported for 50/125mm fiber is 0 m(s) Link length supported for 62.5/125mm fiber is 0 m(s) cisco id is -- cisco extended id number is 4 Invalid calibration Displaying FcoE bound Ethernet interface counters The show interface ethernet command, has two versions, brief and detailed. Examples of each follow.
Page 122 = 30742 rxTxHCpkts1024to1518Octets = 88 rxTxHCpkts1519to1548Octets = 0 rxHCTrunkFrames = 895722 txHCTrunkFrames = 69387 rxHCDropEvents = 0 All Port Counters: InPackets = 931881 InOctets = 76228116 InUcastPkts = 9507 InMcastPkts = 918901 Cisco Nexus 5000 Series Troubleshooting Guide 5-50 OL-25300-01...
Page 123 Jabbers = 0 NoBuffer = 0 Ignored = 0 bpduOutLost = 0 cos0OutLost = 0 cos1OutLost = 0 cos2OutLost = 0 cos3OutLost = 0 cos4OutLost = 0 cos5OutLost = 0 cos6OutLost = 0 Cisco Nexus 5000 Series Troubleshooting Guide 5-51 OL-25300-01...
Page 124 1 output OLS, 2 LRR, 0 NOS, 0 loop inits 16 receive B2B credit remaining 250 transmit B2B credit remaining 0 low priority transmit B2B credit remaining Interface last changed at Thu Jan 28 18:26:30 2010 Cisco Nexus 5000 Series Troubleshooting Guide 5-52 OL-25300-01...
Page 125 0x5d2 0x00000062 FCP_CNTR_MAC_DATA_RX_CLASSF_FRAMES 0x1a 0x00000069 FCP_CNTR_MAC_DATA_RX_CLASS3_WORDS 0x140b14 0x0000006a FCP_CNTR_MAC_DATA_RX_CLASSF_WORDS 0xdcc 0x00000065 FCP_CNTR_MAC_DATA_TX_CLASS3_FRAMES 0xc24 0x00000066 FCP_CNTR_MAC_DATA_TX_CLASSF_FRAMES 0x1d 0x0000006d FCP_CNTR_MAC_DATA_TX_CLASS3_WORDS 0x4b9538 0x0000006e FCP_CNTR_MAC_DATA_TX_CLASSF_WORDS 0xabc 0xffffffff FCP_CNTR_LINK_RESET_IN 0xffffffff FCP_CNTR_OLS_OUT 0xffffffff FCP_CNTR_NOS_OUT 0xffffffff FCP_CNTR_LRR_OUT 0xffffffff FCP_CNTR_LINK_FAILURE Cisco Nexus 5000 Series Troubleshooting Guide 5-53 OL-25300-01...
Page 126 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. Cisco Nexus 5000 Series Troubleshooting Guide 5-54 OL-25300-01...
Page 127 DROP_FCF_SW_DOMAIN_IDX_MISS: res0 = 2445 res1 = 0 DROP_FCF_SW_TBL_MISS: res0 = 2445 res1 = 0 DROP_NO_FABRIC_SELECTED: res0 = 2556 res1 = 0 DROP_VLAN_MASK_TO_NULL: res0 = 2556 res1 = 0 DROP_SRC_MASK_TO_NULL: res0 = 522 res1 = 0 Cisco Nexus 5000 Series Troubleshooting Guide 5-55 OL-25300-01...
Page 128 S e n d d o c u m e n t c o m m e n t s t o n e x u s 5 k - d o c f e e d b a c k @ c i s c o . c o m . Cisco Nexus 5000 Series Troubleshooting Guide...
Page 129: Troubleshooting Security Issues
This chapter describes how to identify and resolve problems that can occur with security in the Cisco Nexus 5000 Series switch. This chapter includes the following sections: Roles •...
Page 130 Use the following menu paths to access the settings: • Network Configuration > AAA > AAA Servers > svi,20.1.1.2,CiscoSecure ACS Network Configuration > AAA > AAA Client > 20.1.1.1 20.1.1.1 RADIUS (Cisco IOS/PIX 6.0) > SharedSecret=test1234, Authenticate Using=RADIUS (Cisco IOS/PIX 6.0) Interface Configuration > RADIUS (Cisco IOS/PIX 6.0) Select User for cisco-av-pair.
Page 131 While a user account is logged in and has been assigned to role A, the administrator makes some changes to role A with the expectation that the change would immediately affect the user that is logged in. However, the user is not assigned to the role properly. Cisco Nexus 5000 Series Troubleshooting Guide OL-25300-01...
Page 132: Aaa
If the test aaa command returns the error, “user has failed authentication", then the server is • accessable but the credentials for the user account are incorrect. Verify that the user configuration is correct on the server. Cisco Nexus 5000 Series Troubleshooting Guide OL-25300-01...
Page 133 Role assignment fails when the user logs in. (From the perspective of the Nexus 5000 switch AAA.) Possible Cause Assuming that the ACS or TACACS+ and RADIUS has the Cisco av pair configured correctly, then the problem might be that the internal or local VRF assignment for the user login is not working correctly.
Page 134 Starting with Release 4.2(1), NX-OS only supports ASCII (PAP) authentication for TACACS+. Solution In NX-OS, ASCII authentication is equivalent to PAP authentication. By default, both TACACS+ and RADIUS use CHAP. You can switch to PAP authentication with the aaa authentication login ascii-authentication command. Cisco Nexus 5000 Series Troubleshooting Guide OL-25300-01...
Page 135 REMOTE authentication. A user account that was created with REMOTE authentication cannot be used for a local (fallback) login. Create local user accounts with the username <username> password <password> role <role • name> command until the remote AAA servers become accessible. Cisco Nexus 5000 Series Troubleshooting Guide OL-25300-01...
Page 136 S e n d d o c u m e n t c o m m e n t s t o n e x u s 5 k - d o c f e e d b a c k @ c i s c o . c o m . Cisco Nexus 5000 Series Troubleshooting Guide...
Page 137: Troubleshooting System Management Issues
C H A P T E R Troubleshooting System Management Issues The system management features of the Cisco Nexus 5000 Series switch allow you to monitor and manage your network for efficient device use, role-based access control, SNMP communications, diagnostics, and logging.
Page 138 The SNMP community does not have write permission. Solution Check the output of the show snmp community command to ensure that the write permission is enabled. Example: Community Group / Access context acl_filter Cisco Nexus 5000 Series Troubleshooting Guide OL-25300-01...
Page 139: Logging
Although the syslog server is configured, the destination syslog server is not receiving messages from DUT. Possible Cause Syslog server might not be accessible or the logging level might not be appropriate. Solution Cisco Nexus 5000 Series Troubleshooting Guide OL-25300-01...
Page 140: Traps
When specifying a host name using DNS or VRF, the host name is not resolved and an error occurs. Possible Cause The DNS client is not configured correctly. Solution Use the following commands to configure the DNS client: Cisco Nexus 5000 Series Troubleshooting Guide OL-25300-01...
Page 141 Then you must add back the temporarily removed domains to the domain-list. An alternative approach is to copy the startup-config and delete the desired domain with a text editor. • Then you must load the edited startup-config back onto the device. Cisco Nexus 5000 Series Troubleshooting Guide OL-25300-01...
Page 142 S e n d d o c u m e n t c o m m e n t s t o n e x u s 5 k - d o c f e e d b a c k @ c i s c o . c o m . Cisco Nexus 5000 Series Troubleshooting Guide...
Page 143: Troubleshooting Virtual Port Channel Issues
This chapter describes how to identify and resolve problems that can occur with vPC in the Cisco Nexus 5000 Series switch. This chapter includes the following section: •...
Page 144 : peer link is down vPC keep-alive status : Suspended (Destination IP not reachable) Configuration consistency status: success vPC role : primary Number of vPCs configured Peer Gateway : Disabled Dual-active excluded VLANs vPC Peer-link status --------------------------------------------------------------------- Cisco Nexus 5000 Series Troubleshooting Guide OL-25300-01...
Page 145 0 Example: switch2# sh run int mgmt 0 !Command: show running-config interface mgmt0 !Time: Tue Mar 8 03:20:58 2011 version 4.2(1)N2(1) interface mgmt0 ip address 172.18.118.162/24 Ensure there is reachability from switch1: Cisco Nexus 5000 Series Troubleshooting Guide OL-25300-01...
Page 146 !Command: show running-config vpc !Time: Tue Mar 8 03:53:57 2011 version 4.2(1)N2(1) feature vpc vpc domain 500 peer-keepalive destination 172.18.118.162 switch2# show run int mgmt 0 !Command: show running-config interface mgmt0 Cisco Nexus 5000 Series Troubleshooting Guide OL-25300-01...
Page 147 S - Switch, H - Host, I - IGMP, r - Repeater, V - VoIP-Phone, D - Remotely-Managed-Device, s - Supports-STP-Dispute Device-ID Local Intrfce Hldtme Capability Platform Port ID switch2(SSI1324033X)Eth1/25 S I s N5K-C5020P-BF Eth1/25 switch2(SSI1324033X)Eth1/26 S I s N5K-C5020P-BF Eth1/26 Cisco Nexus 5000 Series Troubleshooting Guide OL-25300-01...
Page 148 10000 Create a port-channel 500 on switch1 and associate it to the ports connecting to e1/25 and e1/26 on switch2. switch1(config)# int po 500 switch1(config-if)# int e1/25-26 Cisco Nexus 5000 Series Troubleshooting Guide OL-25300-01...
Page 149 To check for a mismatch, display the consistency parameters. switch1# show vpc consistency-parameters global Legend: Type 1 : vPC will be suspended in case of mismatch Name Type Local Value Peer Value ------------- ---- ---------------------- ----------------------- Cisco Nexus 5000 Series Troubleshooting Guide OL-25300-01...
Page 150 In this example, there are different MTU values for Network QoS. The value for the peer switch is 9216 on the peer switch (switch2) and the value for the local switch is 1538 (switch1). vPC will not be operational until the Network QoS values match on both switches. Cisco Nexus 5000 Series Troubleshooting Guide OL-25300-01...
Page 151: Troubleshooting Config-Sync Issues
S e n d d o c u m e n t c o m m e n t s t o n e x u s 5 k - d o c f e e d b a c k @ c i s c o . c o m . C H A P T E R Troubleshooting Config-Sync Issues This chapter describes how to identify and resolve problems that can occur with config-sync in the Cisco Nexus 5000 Series switch. This chapter includes the following sections: Commit Failure •...
Page 152 If conf-t has taken a lock and not released it, command output, similar to the following example, is • displayed. The client type should be set to 2 as shown in the example. Note Cisco Nexus 5000 Series Troubleshooting Guide OL-25300-01...
Page 153: Import Failure
Import failure has many possible causes: Failed to collect running-config • Command does not exist in global-db • Mutual exclusion check failed on peer • The following describes import options and best practices. Cisco Nexus 5000 Series Troubleshooting Guide OL-25300-01...
Page 154 Failure occurs if the system is too busy and the show running command did not complete. Solution Determine if a system resource utilization problem exists. Correct the problem and retry the operation. Command does not exist in global-db Possible Cause Command is missing from the global-db. Solution Cisco Nexus 5000 Series Troubleshooting Guide OL-25300-01...
Page 155: Merge Failure
For a merge to succeed, the configuration in the switch-profile on both peers must match exactly. Note Merge failure has many possible causes: First time merge failure • Merge after peers that were in sync previously • Merge after reload • Cisco Nexus 5000 Series Troubleshooting Guide OL-25300-01...
Page 156: Switch-Profile Deletion Failure
Use the show switch-profile status command to view which commands failed the merge. Correct the configurations and reissue the commit. Switch-profile Deletion Failure A rollback is used to delete the configurations during a switch-profile deletion. Cisco Nexus 5000 Series Troubleshooting Guide OL-25300-01...
Page 157 Correct the commands, references, and reissue the delete. Application does not respond Possible Cause The deletion fails because the application does not respond due to the application owning the command. Solution Correct the commands and reissue the delete. Cisco Nexus 5000 Series Troubleshooting Guide OL-25300-01...
Page 158: Verify Failure
Delete the command from conf-t mode on the peer and run verify from config-sync mode. Rollback/ISSU in progress Possible Cause Verify cannot be performed when rollback/ISSU is in progress. Solution Stop rollback or wait for it to complete and run verify. Cisco Nexus 5000 Series Troubleshooting Guide OL-25300-01...
Page 159 It can also show the mapping to the csm transactions displayed with the show switch-profile session-history command. Cisco Nexus 5000 Series Troubleshooting Guide OL-25300-01...
Page 160 S e n d d o c u m e n t c o m m e n t s t o n e x u s 5 k - d o c f e e d b a c k @ c i s c o . c o m . Cisco Nexus 5000 Series Troubleshooting Guide...
Page 161 Registers and Counters FCoE 2-15 Layer 2 switching 3-10 FC Services 5-16 4-10 SAN switching 5-48 Logging SAN Port Channels 5-13 Security Roles SNMP MAC address table Spanning Tree Protocol Multicast Traps Cisco Nexus 5000 Series Troubleshooting Guide IN-1 OL-25300-01...
Page 162 S e n d d o c u m e n t c o m m e n t s t o n e x u s 5 k - d o c f e e d b a c k @ c i s c o . c o m . VLAN Improper configuration VSAN 5-40 Zoning Cisco Nexus 5000 Series Troubleshooting Guide IN-2 OL-25300-01...

This manual is also suitable for:

N5k-pac-550w= - power supply - hot-plug N5k-c5010p-bf - nexus 5010 switch N5k-c5020p-bf - nexus 5020 switch Nexus 5000 series

Cisco N5K-M1600 - Expansion Module - 6 Ports Troubleshooting Manual

Troubleshooting Overview

Troubleshooting Fcoe Issues

Troubleshooting Layer 2 Switching Issues

Troubleshooting Qos Issues

Troubleshooting SAN Switching Issues

Troubleshooting Security Issues

Aaa

Troubleshooting System Management Issues

Snmp

Dns

Troubleshooting Virtual Port Channel Issues

Troubleshooting Config-Sync Issues

Quick Links

Troubleshooting

Related Manuals for Cisco N5K-M1600 - Expansion Module - 6 Ports

Summary of Contents for Cisco N5K-M1600 - Expansion Module - 6 Ports

This manual is also suitable for:

Table of Contents