Cisco Nexus 5000 Series Operation Manual
Cisco Nexus 5000 Series Operation Manual

Cisco Nexus 5000 Series Operation Manual

Release 5.0(3)n2(1) cisco nexus 5000 series switches, cisco nexus 2000 series fabric extenders
Hide thumbs Also See for Nexus 5000 Series:
Table of Contents

Advertisement

S e n d d o c u m e n t a t i o n c o m m e n t s t o n 5 k d o c f e e d b a c k @ c i s c o . c o m
Preface
This preface describes the audience, organization, and conventions of the Cisco Nexus 5000
Series NX-OS Interfaces Operations Guide, Release 5.0(3)N2(1). It also provides
information on how to obtain related documentation.
This chapter includes the following topics:
Audience
This publication is for experienced network administrators who configure and maintain Cisco NX-OS
on Cisco Nexus 5000 Platform switches and Cisco Nexus 5500 Platform switches.

Document Conventions

Command descriptions use the following conventions:
Convention
bold
Italic
[x]
[x | y]
{x | y}
Audience, page iii
Document Conventions, page iii
Related Documentation, page v
Obtaining Documentation and Submitting a Service Request, page v
Cisco Nexus 5000 Series NX-OS Interfaces Operations Guide, Release 5.0(3)N2(1)
Description
Bold text indicates the commands and keywords
that you enter literally as shown.
Italic text indicates arguments for which the user
supplies the values.
Square brackets enclose an optional
element(keyword or argument).
Square brackets enclosing keywords or arguments
separated by a vertical bar indicate an optional
choice.
Braces enclosing keywords or arguments
separated by a vertical bar indicate a required
choice.
iii

Advertisement

Table of Contents
loading

Summary of Contents for Cisco Nexus 5000 Series

  • Page 1: Document Conventions

    S e n d d o c u m e n t a t i o n c o m m e n t s t o n 5 k d o c f e e d b a c k @ c i s c o . c o m Preface This preface describes the audience, organization, and conventions of the Cisco Nexus 5000 Series NX-OS Interfaces Operations Guide, Release 5.0(3)N2(1). It also provides information on how to obtain related documentation.
  • Page 2 Means reader take note. Notes contain helpful suggestions or references to material not covered in the manual. Caution Means reader be careful. In this situation, you might do something that could result in equipment damage or loss of data. Cisco Nexus 5000 Series NX-OS Interfaces Operations Guide, Release 5.0(3)N2(1)
  • Page 3: Related Documentation

    Cisco technical documentation: http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html Subscribe to the What’s New in Cisco Product Documentation as an RSS feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service. Cisco currently supports RSS Version 2.0.
  • Page 4 S e n d d o c u m e n t a t i o n c o m m e n t s t o n 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 NX-OS Interfaces Operations Guide, Release 5.0(3)N2(1)
  • Page 5: Virtual Port Channel Operations

    A vPC allows links that are physically connected to two different Cisco Nexus 5000 Series switches to appear as a single port channel to a third switch. The third switch can be a Cisco Nexus 2000 Series Fabric Extender or a switch, server, or any other networking device. A vPC can provide Layer 2 multipath capability which allows you to create redundancy by increasing bandwidth, enabling multiple parallel paths between nodes, and load-balancing traffic where alternative paths exist.
  • Page 6: Type 1 And Type 2 Consistency Check Parameters

    Type 1 and Type 2 Consistency Check Parameters Before a Cisco Nexus 5000 Series switch brings up a vPC, the two Cisco Nexus 5000 Series switches in the same vPC domain exchange configuration information to verify if both switches have compatible configurations for a vPC topology.
  • Page 7: Graceful Consistency Check

    Allowed VLANs 1-999,1001-3967,4048-4 1-3967,4048-4093 The Cisco Nexus 5000 Series switch conducts vPC consistency checks when it attempts to bring up a vPC or when you make a configuration change. In the interface consistency parameters shown in the above output, all configurations except the Allowed VLANs are considered as Type 1 consistency check parameters.
  • Page 8 This example shows that the vPC ports and the VLANs remain up on the primary switch when an STP mode mismatch occurs: This example shows that the vPC ports are down on a secondary switch when an interface-level Type 1 inconsistency occurs: Cisco Nexus 5000 Series NX-OS Interfaces Operations Guide, Release 5.0(3)N2(1)
  • Page 9: Configuring Per-Vlan Consistency Checks

    Type 1 inconsistency occurs: Configuring Per-VLAN Consistency Checks Beginning with Cisco NX-OS Release 5.0(2)N2(1), the Cisco Nexus 5000 Series switch performs Type-1 consistency checks on a per-VLAN basis when you enable or disable STP on a VLAN. VLANs that do not pass this consistency check are brought down on the primary and secondary switches while other VLANs are not affected.
  • Page 10: Identifying Inconsistent Vpc Configurations

    You can use the show vpc consistency-parameters global command to identify the configuration difference between two vPC peer switches. This example shows the global consistency check failed because the STP mode was configured differently on the two vPC switches: Cisco Nexus 5000 Series NX-OS Interfaces Operations Guide, Release 5.0(3)N2(1)
  • Page 11 This example shows how to display configuration differences that lead to consistency check failures. Cisco Nexus 5000 Series NX-OS Interfaces Operations Guide, Release 5.0(3)N2(1)
  • Page 12: Bypassing A Vpc Consistency Check When A Peer Link Is Lost

    This feature is similar to the reload restore feature in Cisco NX-OS Release 5.0(2)N1(1) and earlier releases. The reload delay period can range from 240 to 3600 seconds.
  • Page 13: Configuring Changes In Vpc Topologies

    Beginning with Cisco NX-OS Release 5.0(2)N2(1), you can use the following procedure to make configuration changes for Type 1 consistency check parameters on a Cisco Nexus 5000 Series switch. We recommend that you perform the following procedure during a maintenance window because it might reduce the vPC bandwidth by half for a short duration.
  • Page 14: Fabric Extender

    Replacing a Cisco Nexus 5000 Series Switch or Cisco Nexus 2000 Fabric Extender This section describes how to replace a Cisco Nexus 5000 Series switch or Cisco Nexus 2000 Series Fabric Extender in a vPC topology with minimal disruption. This section include the following topics: •...
  • Page 15: Replacing A Cisco Nexus 5000 Series Switch

    S e n d d o c u m e n t a t i o n c o m m e n t s t o n 5 k d o c f e e d b a c k @ c i s c o . c o m Replacing a Cisco Nexus 5000 Series Switch When you replace a Cisco Nexus 5000 Series switch, you must perform the following procedure on the replacement switch to synchronize the configuration with the existing Cisco Nexus 5000 Series switch.
  • Page 16 Virtual Port Channel Operations Replacing a Cisco Nexus 5000 Series Switch or Cisco Nexus 2000 Fabric Extender S e n d d o c u m e n t a t i o n c o m m e n t s t o n 5 k d o c f e e d b a c k @ c i s c o . c o m •...
  • Page 17: Replacing A Cisco Nexus 2000 Series Fabric Extender

    If the replacement Fabric Extender is a different model, the Cisco Nexus 5000 Series switch does not allow you to pre-provision a new type until you disconnect the old Fabric Extender.
  • Page 18: Installing A New Cisco Nexus 2000 Series Fabric Extender

    Cisco Nexus 5000 Series switch, depending on the port-channel hash algorithm of the top switch. For those flows that traverse the right-side Cisco Nexus 5000 Series switch (the red line), the Cisco Nexus 5000 Series switch passes the traffic to the left-side Cisco Nexus 5000 Series switch, because it no longer has the local connection to host MAC_A.
  • Page 19 As a result, the hosts or switches that are connected to the Cisco Nexus 5000 Series switch or Cisco Nexus 2000 Series Fabric Extender vPC pair redistributes all the flows to the vPC member ports that are connected to the vPC primary switch.
  • Page 20: Vpc Peer Keepalive Link Failure

    Use the reload restore feature that was introduced in Cisco NX-OS Release 5.0(2)N1(1) to fix this problem. The reload restore feature allows a switch to bypass the vPC consistency check and bring up vPC ports when the peer-link or peer switch fails.
  • Page 21: Vpc Peer Switch Failure

    In either case, since the vPC primary election cannot proceed, the Cisco Nexus 5000 Series switch keeps the vPC ports in suspend mode.
  • Page 22: Tracing Traffic Flow In A Vpc Topology

    The Cisco NX-OS and Cisco IOS software includes commands to identify the port channel member that carries a particular flow.
  • Page 23 While using the SPAN feature to monitor the traffic flow, the communications between two hosts can be split between two vPC switches. Therefore, you may need to enable SPAN on both vPC switches to obtain a complete trace. Cisco Nexus 5000 Series NX-OS Interfaces Operations Guide, Release 5.0(3)N2(1) 1-19...
  • Page 24 S e n d d o c u m e n t a t i o n c o m m e n t s t o n 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 NX-OS Interfaces Operations Guide, Release 5.0(3)N2(1)
  • Page 25: Cisco Nexus 5500 Platform Layer 3 And Vpc Operations

    Software Upgrade and Downgrade Impact, page 2-14 vPC and First Hop Redundancy Protocol When you use a Cisco Nexus 5548 switch or Cisco Nexus 5596UP switch as a default gateway for hosts, you can deploy the First Hop Redundancy Protocol (FHRP) to provide default gateway redundancy.
  • Page 26: Arp Processing With Vpc

    ARP request to a host, the ARP reply might be sent to another switch. In such a case, the ARP reply is forwarded as a Layer 2 frame to the Cisco Nexus 5500 Platform switch that originated the ARP request.
  • Page 27 HSRP HSRP Active Standby Another scenario that could lead to this situation is when a router is connected to a Cisco Nexus 5500 Platform in a vPC topology. Figure 2-3 Connecting to a Router in a vPC Topology VPC Topology...
  • Page 28: Improved Convergence With A Vpc Topology And Layer 3 Routing

    Beginning in Cisco NX-OS Release 5.0(3)N1(1b), a delay timer was introduced to avoid the situation where a vPC member port is brought up before the Layer 3 is converged. For example, when one Cisco Nexus 5500 Platform switch is reloaded, the switch starts to receive traffic from hosts once the vPC member ports are up.
  • Page 29: Vpc Peer Link Failure

    Layer 3 Module Failure When a Layer 3 module fails on a Cisco Nexus 5500 Platform switch all Layer 3 interfaces are suspended, including Layer 3 port channel and SVI interfaces. As a result, the Layer 3 routing table on the neighboring routers is updated which results in the north to south traffic to be directed towards the peer Nexus 5500 Platform switch.
  • Page 30: Connecting To A Router In A Vpc Topology

    Connecting to a Router in a vPC Topology When you connect a router to a pair of Cisco Nexus 5500 Platform switches in a vPC topology and enable routing, traffic forwarding may result in suboptimal traffic paths crossing the peer link similar to the situation described in the “Layer 3 Forwarding for Packets to a Peer Switch MAC Address”...
  • Page 31: Dedicated Vrf For A Keepalive Interface

    Routing protocol peer This topology is supported for unicast traffic but not for multicast traffic. In this topology, we recommend that you use Layer 3 interfaces instead of vPC interfaces to connect routers to Cisco Nexus 5500 Platform switches whenever possible.
  • Page 32 --Keepalive tos : 192 The services provided by the Cisco Nexus 5500 Platform switch, such as Ping, SSH, Telnet, and RADIUS, are VRF-aware. You must specify the VRF name in the CLI in order to use the correct routing table.
  • Page 33: Vpc Consistency Check For Layer 3 Parameters

    N5k-2 PIM peer When a PIM router is connected to Cisco Nexus 5500 Platform switches in a vPC topology, the PIM join messages are received only by one switch. The multicast data might be received by the other switch. Cisco Nexus 5000 Series NX-OS Interfaces Operations Guide, Release 5.0(3)N2(1)
  • Page 34: Multicast Routing Table Size

    In a non-vPC topology, only the designated router (DR) can join the source tree. In a vPC topology, when a receiver is connected to a Cisco Nexus 5500 Platform switch or Fabric Extender (FEX) via vPC, both peer switches initiate a PIM (S,G) join toward the source DR. In a topology where both vPC peer switches have equal costs to the source, the vPC primary switch wins the assert and forwards multicast traffic for receivers connected to the Nexus 5500 Platform switch or FEX using the vPC.
  • Page 35 Outgoing interface list: (count: 1) Vlan10, uptime: 00:55:14, mrib The multicast forwarding algorithm applies to all hosts that are connected to the Cisco Nexus 5500 Platform switch or the FEX in a VPC topology, including hosts directly connected to the switch or hosts connected to straight-through FEX topology.
  • Page 36: Using A Vpc Switch As A Designated Router (Pim Dr)

    DR switch using a Cisco Fabric Services (CFS) message about the source and group address. The DR generates source registration packets to the rendezvous point (RP).
  • Page 37 VLAN 10 and receivers in VLAN 11 and VLAN 12 are the vPC hosts (although in this example they are hosts behind a dual-homed FEX topology where the same rule applies to hosts directly to a Cisco Nexus 5500 Platform switch in a vPC topology). VLAN 13 is a non-vPC VLAN and resides only on N5k-2.
  • Page 38: Software Upgrade And Downgrade Impact

    VLAN 10, VLAN 11, and VLAN 12, the packets are bridged to the orphan ports. Software Upgrade and Downgrade Impact In Cisco NX-OS Release 5.0(3)N1(1b), the Cisco Nexus 5500 Platform switch does not support ISSUs when Layer 3 modules are installed and Layer 3 features are enabled. Use the install all command and...
  • Page 39: Show Spanning-Tree Issu-Impact

    3. There should not be any Non Edge Designated Forwarding port (except MCT) 4. ISSU criteria must be met on the VPC Peer Switch as well Following are the statistics on this switch Cisco Nexus 5000 Series NX-OS Interfaces Operations Guide, Release 5.0(3)N2(1) 2-15...
  • Page 40 No Non-Edge Designated Forwarding Ports Found! Criteria 3 PASSED !! ISSU Can Proceed! Check Peer Switch. For information on upgrade procedures, see the Cisco Nexus 5000 Series NX-OS Upgrade and Downgrade Guide. Cisco Nexus 5000 Series NX-OS Interfaces Operations Guide, Release 5.0(3)N2(1)
  • Page 41 ISSUs successful 2-14 not supported consistency checks 2-15 supported configuring per-VLAN control traffic forwarding in a vPC topology Cisco Nexus 5000 Series NX-OS Interfaces Operations Guide, Release 5.0(3)N2(1) IN-1...
  • Page 42 2-12 not routed unsupported multicast topology peer-gateway command peer link 1-16 failure followed by a peer keepalive link failure VLAN peer links Cisco Nexus 5000 Series NX-OS Interfaces Operations Guide, Release 5.0(3)N2(1) IN-2...
  • Page 43 1-13 vPC failure scenarios vPC operations about vPC peer link failure vPC topologies configuration changes vPC topology multicast interaction services that are recognized Cisco Nexus 5000 Series NX-OS Interfaces Operations Guide, Release 5.0(3)N2(1) IN-3...
  • Page 44 S e n d d o c u m e n t a t i o n c o m m e n t s t o n 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 NX-OS Interfaces Operations Guide, Release 5.0(3)N2(1)

This manual is also suitable for:

Nexus 2000 series

Table of Contents