Cisco Nexus 7. 00. Series NX- OS Troubleshooting Guide - - Troubleshooting Overview. From Doc. Wiki This article introduces the basic concepts, methodology, and general troubleshooting guidelines for problems that may occur when configuring and using Cisco NX- OS. Overview of the Troubleshooting Process To troubleshoot your network, follow these general steps.
© 2015-2016 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. Page 1 of 129 Design and Configuration Guide. Command-Line Interface Troubleshooting Commands. The command-line interface (CLI) allows you to configure and monitor Cisco NX-OS using a local console or remotely.
Maintain a consistent Cisco NX- OS release across all your devices. See the Cisco NX- OS release notes for your Cisco NX- OS release for the latest features, limitations, and caveats. Enable system message logging. See System Messages.
Cisco Nexus 7000 Series NX-OS Verified Scalability Guide; Cisco Nexus 7000 Series Switches Configuration Guide: The Catena Solution; Cisco Nexus 7000 Series NX-OS.
Troubleshoot any new configuration changes after implementing the change. Gather information that defines the specific symptoms. See Gathering Information.
Verify the physical connectivity between your device and end devices. See Verifying Ports. Verify the Layer 2 connectivity. See Verifying Layer 2 Connectivity. Verify the end- to- end connectivity and the routing configuration. See Verifying Layer 3 Connectivity.
After you have determined that your troubleshooting attempts have not resolved the problem, contact Cisco TAC or your technical support representative. Gathering Information This section describes the tools that are commonly used to troubleshoot problems within your network. Specific troubleshooting articles may include additional tools and commands specific to the symptoms and possible problems covered in that article. Use the following commands to gather general information on your device.
ERshow accounting log Verifying Ports Answer the following questions to verify that your ports are connected correctly and are operational. Are you using the correct media (copper, optical, fiber type)? Is the media broken or damaged? Is the port LED green on the module? Is the interface in the correct VDC? Use the show vdc membership command to check which VDC that the interface is a member of. You must log into the device with the network- admin role to use this command.
Is the interface operational? Use the show interface brief command. The status should be up. See Troubleshooting Ports for more troubleshooting tips for ports. Verifying Layer 2 Connectivity Use the following commands to verify Layer 2 connectivity. Use the show vlan all- ports command to verify that all the necessary interfaces are in the same VLAN. The status should be active for the VLAN.
Use the show port- channel compatibility- parameters command to verify that all the ports in a port channel are configured the same for the speed, the duplex, and the trunk mode. Use the show running- config spanning- tree command to verify that the Spanning Tree Protocol (STP) is configured the same on all devices in the network.
Use the show processes | include ER command to verify that no essential Layer 2 processes are in the error state. Use the show spanning- tree blockedports command to display the ports that are blocked by STP. Use the show mac address- table dynamic vlan command to determine if learning or aging is occurring at each node. See Troubleshooting VLANs and Troubleshooting STP for more information on troubleshooting Layer 2 issues. Verifying Layer 3 Connectivity Answer the following questions to verify Layer 3 connectivity. Have you configured a default gateway?
Have you configured the same dynamic routing protocol parameters throughout your routing domain or configured static routes? Are any IP access lists, filters, or route maps blocking route updates? Use the following commands to verify your routing configuration.
See Ping and Traceroute to verify Layer 3 connectivity. See Troubleshooting Routing for more information on troubleshooting Layer 3 issues. Overview of Symptoms This article uses a symptom- based troubleshooting approach that allows you to diagnose and resolve your Cisco NX- OS problems by comparing the symptoms that you observed in your network with the symptoms listed in each chapter. By comparing the symptoms in this publication to the symptoms that you observe in your own network, you should be able to diagnose and correct software configuration issues and inoperable hardware components so that the problems are resolved with minimal disruption to the network. Those problems and corrective actions include the following. Identify key Cisco NX- OS troubleshooting tools. Obtain and analyze protocol traces using SPAN and RSPAN or Ethanalyzer on the CLI.
Identify or rule out physical port issues. Identify or rule out switch module issues. Diagnose and correct Layer 2 issues. Diagnose and correct Layer 3 issues. Recover from switch upgrade failures. Obtain core dumps and other diagnostic data for use by Cisco TAC or your customer support representative. System Messages The system software sends syslog (system) messages to the console (and, optionally, to a logging server on another device).
Not all messages indicate a problem with your device. Some messages are purely informational, while others might help diagnose problems with links, internal hardware, or the device software. System Message Text Message text is a text string that describes the condition. This portion of the message might contain detailed information about the event, including terminal port numbers, network addresses, or addresses that correspond to locations in the system memory address space. Because the information in these variable fields changes from message to message, it is represented here by short strings enclosed in square brackets ([ ]).
A decimal number, for example, is represented as [dec ]. PORT- 3- IF_UNSUPPORTED_TRANSCEIVER: Transceiver for interface [chars] is not supported. Use this string to find the matching system message in the NX- OS System Messages Reference or in the Error Message Decoder. Each system message is followed by an explanation and recommended action. The action may be as simple as "No action is required." It may involve a fix or a recommendation to contact technical support as shown in the following example.
Error Message PORT- 3- IF_UNSUPPORTED_TRANSCEIVER: Transceiver for interface [chars] is not supported. Explanation Transceiver (SFP) is not from an authorized vendor. Recommended Action Enter the show interface transceiver CLI command or similar DCNM command to determine the transceiver being used. Please contact your customer support representative for a list of authorized transceiver vendors.
Server Implementation The syslog facility allows the Cisco NX- OS device to send a copy of the message log to a host for more permanent storage. This feature allows you to examine the logs over a long period of time or if the Cisco NX- OS device is not accessible. This example shows how to configure a Cisco NX- OS device to use the syslog facility on a Solaris platform. Although a Solaris host is being used, the syslog configuration on all UNIX and Linux systems is very similar. Solaris system in this example) and the message severity. Different message severities are handled differently by the syslog server.
They could be logged to different files or e- mailed to a particular user. Specifying a severity level on the syslog server determines that all messages of that level and greater severity (lower number) will be acted upon as you configure the syslog server. To configure the syslog feature on Cisco NX- OS, follow these steps. Use the show logging server command to verify the syslog configuration. Logging server: enabled. VRF: management.
To configure a syslog server, follow these steps. Modify /etc/syslog. For Solaris, you must allow at least one tab between the facility. Create the log file. Restart the syslog process. Verify that the syslog process has started.
Test the syslog server by creating an event in Cisco NX- OS. In this case, port e. The IP address of the switch is listed in brackets. MDS_logs. Sep 1. 7 1.
Sep 1. 7 1. 1: 1. PORT- 5- IF_DOWN_INITIALIZING: %$VLAN 1%$ Interface e 1/2 is down (Initializing). Sep 1. 7 1. 1: 0. Sep 1. 7 1. 1: 1. PORT- 5- IF_UP: %$VLAN 1%$ Interface e 1/2 is up in mode access.
Sep 1. 7 1. 1: 0. Sep 1. 7 1. 1: 1. VSHD- 5- VSHD_SYSLOG_CONFIG_I: Configuring console from pts/0 (dhcp- 1. Troubleshooting with Logs Cisco NX- OS generates many types of system messages on the device and sends them to a syslog server. You can view these messages to determine what events may have led up to the current problem condition that you are facing. Use the following commands to access and view logs in Cisco NX- OS. Show console logging configuration.
Show logging configuration. IP configuration. Show last few lines of logfile.
Next- Generation Data Center Architectures, 2nd Edition. Copyright 2. 01. 3Dimensions: 7- 3/8" x 9- 1/8"Pages: 8.
Edition: 2nd. Book ISBN- 1. ISBN- 1. 3: 9. 78- 1- 5. NX- OS and Cisco Nexus Switching. Next- Generation Data Center Architectures. Second Edition. The complete guide to planning, configuring, managing, and troubleshooting NX- OS in the enterprise–updated with new technologies and examples. Using Cisco Nexus switches and the NX- OS operating system, data center professionals can build unified core networks that deliver unprecedented scalability, resilience, operational continuity, flexibility, and performance. NX- OS and Cisco Nexus Switching, Second Edition, is the definitive guide to applying these breakthrough technologies in real- world environments.
This extensively updated edition contains five new chapters addressing a wide range of new technologies, including Fabric.Path, OTV, IPv. 6, Qo.S, VSG, Multi- Hop FCo. Resident Evil 4 Keygen Download Youtube . E, LISP, MPLS, Layer 3 on Nexus 5.Config sync. It also presents a start- to- finish, step- by- step case study of an enterprise customer who migrated from Cisco Catalyst to a Nexus- based architecture, illuminated with insights that are applicable in virtually any enterprise data center.
Drawing on decades of experience with enterprise customers, the authors cover every facet of deploying, configuring, operating, and troubleshooting NX- OS in today’s data center. You’ll find updated best practices for high availability, virtualization, security, L2/L3 protocol and network support, multicast, serviceability, provision of networking and storage services, and more. Best of all, the authors present all the proven commands, sample configurations, and tips you need to apply these best practices in your data center. Ron Fuller, CCIE No.
Routing and Switching/Storage Networking), Technical Marketing Engineer on Cisco’s Nexus 7. Ron has 2. 1 years of industry experience, including 7 at Cisco.
He has spoken at Cisco Live on VDCs, NX- OS multicast, and general design. David Jansen, CCIE No. Routing/Switching), is a Cisco Technical Solutions Architect specializing in enterprise data center architecture. He has 2. 0 years of industry experience, 1. Cisco (6 as a solution architect); and has delivered several Cisco Live presentations on NX- OS and data center solutions. Matthew Mc. Pherson, senior systems engineer and solutions architect for the Cisco Central Select Operation, specializes in data center architectures. He has 1. 2 years of experience working with service providers and large finance and manufacturing enterprises, and possesses deep technical knowledge of routing, switching, and security.
Understand the NX- OS command line, virtualization features, and file system Utilize the NX- OS comprehensive Layer 2/Layer 3 support: v. PC, Spanning Tree Protocol, Cisco Fabric. Path, EIGRP, OSPF, BGP, HSRP, GLBP, and VRRP Configure IP multicast with PIM, Auto- RP, and MSDP Secure your network with CTS, SGTs, ACLs, Co. PP, and DAI Establish a trusted set of network devices with Cisco Trust.
Sec Maximize availability with ISSU, stateful process restart/switchover, and non- stop forwarding Improve serviceability with SPAN, ERSPAN, configuration checkpoints/rollback, packet analysis, Smart Call Home, Python, and Po. AP Unify storage and Ethernet fabrics with FCo. E, NPV, and NPIV Take full advantage of Nexus 1. V in a virtualized environment Achieve superior Qo. S with MQ CLI, queuing, and marking Extend L2 networks across L3 infrastructure with Overlay Transport Virtualization (OTV) Deliver on SLAs by integrating MPLS application components such as L3 VPNs, traffic engineering, Qo. S, and m. VPN Support mobility via the new Locator ID Separation Protocol (LISP) Walk step- by- step through a realistic Nexus and NX- OS data center migration. Online Sample Chapter.
Cisco NX- OS and Cisco Nexus Switching: Unified Fabric. Sample Pages. Download the sample pages (includes Chapter 8 and Index)Table of Contents. Foreword xxiii. Introduction xxiv. Chapter 1 Introduction to Cisco NX- OS 1. NX- OS Overview 1 NX- OS Supported Platforms 3 NX- OS Licensing 7 Nexus 7. Nexus 5. 50. 0 8 Nexus 3. Nexus 2. 00. 0 9 Nexus 1.
Installing the NX- OS License File 9 Cisco NX- OS and Cisco IOS Comparison 1. NX- OS User Modes 1. EXEC Command Mode 1.
Global Configuration Command Mode 1. Interface Configuration Command Mode 1. Management Interfaces 1. Controller Processor (Supervisor Module) 1.
Connectivity Management Processor (CMP) 1. Telnet 1. 8 SSH 1. SNMP 2. 3 DCNM 2. Managing System Files 2. File Systems 2. 8 Configuration Files: Configuration Rollback 3.
Operating System Files 3. Virtual Device Contexts 3. VDC Configuration 4. VDC Interface Allocation 4.
Interface Allocation: N7. K- M1. 32. XP- 1. L 4. 6 Interface Allocation: N7. K- F1. 32. XP- 1. Interface Allocation: N7.
K- M1. 08. X2- 1. L 4. 8 Interface Allocation: 1. Modules 4. 8 Interface Allocation on M2 Modules 5. Troubleshooting 5. Commands 5. 4 debug Commands 5.
Topology 5. 6Further Reading 5. Chapter 2 Layer 2 Support and Configurations 5. Layer 2 Overview 5. Store- and- Forward Switching 6. Cut- Through Switching 6.
Fabric Extension via the Nexus 2. Configuring Nexus 2. Using Static Pinning 6. Nexus 2. 00. 0 Static Pinning Verification 6.
Configuring Nexus 2. Using Port- Channels 6.
Nexus 2. 00. 0 Static Pinning Verification 6. Layer 2 Forwarding on a Nexus 7. L2 Forwarding Verification 7. VLANs 7. 1 Configuring VLANs 7. VLAN Trunking Protocol 7.
Assigning VLAN Membership 7. Verifying VLAN Configuration 7. Private VLANs 7. 6 Configuring PVLANs 7.
Verifying PVLAN Configuration 8.Spanning Tree Protocol 8.Rapid- PVST+ Configuration 8.Verifying Spanning Tree State for a VLAN 8.Spanning Tree Timers 8.MST Configuration 8. Agency Management Software For Ms Crm Goals here.
Additional Spanning Tree Configuration 9. Port Cost 9. 1 Port Priority 9. Spanning Tree Toolkit 9. BPDUGuard 9. 4 BPDUFilter 9. Root. Guard 9. 6 Loop. Guard 9. 7 Dispute Mechanism 9. Bridge Assurance 9.
Spanning Tree Port Types 9. Virtualization Hosts 1. Configuring Layer 2 Interfaces 1. Trunk Ports 1. 00 Standard Host 1. Link to Virtualization Host 1. Port- Profiles 1. Port- Channels 1.
Assigning Physical Ports to a Port- Channel 1. Port- Channel Flow Control 1.
Verifying Load Distribution Across a Port- Channel 1.Virtual Port- Channels 1.PC Peer- Gateway 1.PC Peer- Switch 1.ARP Synchronization 1.Unidirectional Link Detection 1. Best 3D Rendering Software For Sketchup 2016 . Cisco Fabric. Path 1.
PC+ 1. 27 Configuring v. PC+ 1. 27. Summary 1.
Chapter 3 Layer 3 Support and Configurations 1. EIGRP 1. 35 EIGRP Operation 1. Configuring EIGRP 1. EIGRP Summarization 1.
EIGRP Stub Routing 1. Securing EIGRP 1. EIGRP Redistribution 1. OSPF 1. 54 OSPFv. Configuration 1. 54 OSPF Summarization 1. OSPF Stub Routing 1. Securing OSPF 1. 67 OSPF Redistribution 1.
OSPFv. 3 Configuration 1. IS- IS 1. 78 IS- IS Configuration 1. BGP 1. 83 BGP Configuration 1. BGP Neighbors 1. 87 Securing BGP 1. BGP Peer Templates 1. Advertising BGP Networks 1.
Modifying BGP Routing Metrics 1. Verifying BGP- Specific Configuration 1. First Hop Redundancy Protocols 1. HSRP 1. 99 HSRP Configuration 1.
HSRP Priority and Preempt 2. Verifying the HSRP Configuration 2. Securing HSRP 2. 02 HSRP Secondary Support 2. HSRP Support for IPv. VRRP 2. 05 VRRP Configuration 2. VRRP Priority and Preempt 2. Verifying VRRP Configuration 2.
Securing VRRP 2. 08 VRRP Secondary Support 2. HSRP, VRRP, and v.
PC Interactions 2. GLBP 2. 12 GLBP Configuration 2. GLBP Priority and Preempt 2.
Verifying GLBP Configuration 2. Securing GLBP 2. 15 GLBP Secondary Support 2.
Summary 2. 20. Chapter 4 IP Multicast Configuration 2. Multicast Operation 2. Multicast Distribution Trees 2.
Reverse Path Forwarding 2. Protocol Independent Multicast (PIM) 2. RPs 2. 26. PIM Configuration on Nexus 7. Nexus 5. 50. 0 2. Configuring Static RPs 2. Configuring BSRs 2. Configuring Auto- RP 2.
Configuring Anycast- RP 2. Configuring SSM and Static RPF 2. IGMP Operation 2. IGMP Configuration on Nexus 7. IGMP Configuration on Nexus 5. IGMP Configuration on Nexus 1. V 2. 46. MSDP Configuration on Nexus 7.
Administrative Scoping of Multicast RPs in PIM 2. Configuring PIM Join and Prune Policies 2. Multicast and Control Plane Policing (Co. PP) 2. 53. Summary 2.
Chapter 5 Security 2. Configuring RADIUS 2. RADIUS Configuration Distribution 2. Configuring TACACS+ 2. Enabling TACACS+ 2. TACACS+ Configuration Distribution 2.
Configuring the Global TACACS+ Keys 2. Configuring the TACACS+ Server Hosts 2.