Cisco Systems N5KC5596TFA manuel d'utilisation

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122

Aller à la page of

Un bon manuel d’utilisation

Les règles imposent au revendeur l'obligation de fournir à l'acheteur, avec des marchandises, le manuel d’utilisation Cisco Systems N5KC5596TFA. Le manque du manuel d’utilisation ou les informations incorrectes fournies au consommateur sont à la base d'une plainte pour non-conformité du dispositif avec le contrat. Conformément à la loi, l’inclusion du manuel d’utilisation sous une forme autre que le papier est autorisée, ce qui est souvent utilisé récemment, en incluant la forme graphique ou électronique du manuel Cisco Systems N5KC5596TFA ou les vidéos d'instruction pour les utilisateurs. La condition est son caractère lisible et compréhensible.

Qu'est ce que le manuel d’utilisation?

Le mot vient du latin "Instructio", à savoir organiser. Ainsi, le manuel d’utilisation Cisco Systems N5KC5596TFA décrit les étapes de la procédure. Le but du manuel d’utilisation est d’instruire, de faciliter le démarrage, l'utilisation de l'équipement ou l'exécution des actions spécifiques. Le manuel d’utilisation est une collection d'informations sur l'objet/service, une indice.

Malheureusement, peu d'utilisateurs prennent le temps de lire le manuel d’utilisation, et un bon manuel permet non seulement d’apprendre à connaître un certain nombre de fonctionnalités supplémentaires du dispositif acheté, mais aussi éviter la majorité des défaillances.

Donc, ce qui devrait contenir le manuel parfait?

Tout d'abord, le manuel d’utilisation Cisco Systems N5KC5596TFA devrait contenir:
- informations sur les caractéristiques techniques du dispositif Cisco Systems N5KC5596TFA
- nom du fabricant et année de fabrication Cisco Systems N5KC5596TFA
- instructions d'utilisation, de réglage et d’entretien de l'équipement Cisco Systems N5KC5596TFA
- signes de sécurité et attestations confirmant la conformité avec les normes pertinentes

Pourquoi nous ne lisons pas les manuels d’utilisation?

Habituellement, cela est dû au manque de temps et de certitude quant à la fonctionnalité spécifique de l'équipement acheté. Malheureusement, la connexion et le démarrage Cisco Systems N5KC5596TFA ne suffisent pas. Le manuel d’utilisation contient un certain nombre de lignes directrices concernant les fonctionnalités spécifiques, la sécurité, les méthodes d'entretien (même les moyens qui doivent être utilisés), les défauts possibles Cisco Systems N5KC5596TFA et les moyens de résoudre des problèmes communs lors de l'utilisation. Enfin, le manuel contient les coordonnées du service Cisco Systems en l'absence de l'efficacité des solutions proposées. Actuellement, les manuels d’utilisation sous la forme d'animations intéressantes et de vidéos pédagogiques qui sont meilleurs que la brochure, sont très populaires. Ce type de manuel permet à l'utilisateur de voir toute la vidéo d'instruction sans sauter les spécifications et les descriptions techniques compliquées Cisco Systems N5KC5596TFA, comme c’est le cas pour la version papier.

Pourquoi lire le manuel d’utilisation?

Tout d'abord, il contient la réponse sur la structure, les possibilités du dispositif Cisco Systems N5KC5596TFA, l'utilisation de divers accessoires et une gamme d'informations pour profiter pleinement de toutes les fonctionnalités et commodités.

Après un achat réussi de l’équipement/dispositif, prenez un moment pour vous familiariser avec toutes les parties du manuel d'utilisation Cisco Systems N5KC5596TFA. À l'heure actuelle, ils sont soigneusement préparés et traduits pour qu'ils soient non seulement compréhensibles pour les utilisateurs, mais pour qu’ils remplissent leur fonction de base de l'information et d’aide.

Table des matières du manuel d’utilisation

  • Page 1

    Cisco Nexus 5000 Series NX-OS Interfaces Configuration Guide, Release 5.2(1)N1(1) First Published: July 02, 2012 Last Modified: July 02, 2012 Americas Headquarters Cisco Systems, Inc. 170 W est T asman Drive San Jose, CA 95134-1706 USA http://www .cisco.com T el: 408 526-4000 800 553-NETS (6387) Fax: 408 527-0883 T ext Part Number: 78-26881-OL[...]

  • Page 2

    THE SPECIFICA TIONS AND INFORMA TION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL ST A TEMENTS, INFORMA TION, AND RECOMMENDA TIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURA TE BUT ARE PRESENTED WITHOUT W ARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST T AKE FULL RESPONSIBILITY FOR THEIR APPLICA TION OF ANY PROD[...]

  • Page 3

    CONTENTS Preface Preface ix Audience ix Document Conventions ix Documentation Feedback x Obtaining Documentation and Submitting a Service Request xi CHAPTER 1 New and Changed Information for this Release 1 New and Changed Information for this Release 1 CHAPTER 2 Configuring Layer 2 Interfaces 3 Information About Ethernet Interfaces 3 About the Inte[...]

  • Page 4

    Configuring Unified Ports 10 Configuring the UDLD Mode 12 Configuring Interface Speed 13 Disabling Link Negotiation 14 Configuring the CDP Characteristics 14 Enabling or Disabling CDP 15 Enabling the Error-Disabled Detection 16 Enabling the Error-Disabled Recovery 17 Configuring the Error-Disabled Recovery Interval 18 Port Profiles 19 Creating a Po[...]

  • Page 5

    Configuring a Routed Interface 36 Configuring a Subinterface 37 Configuring the Bandwidth on an Interface 38 Configuring a VLAN Interface 39 Configuring a Loopback Interface 40 Assigning an Interface to a VRF 40 V erifying the Layer 3 Interfaces Configuration 41 Monitoring Layer 3 Interfaces 42 Configuration Examples for Layer 3 Interfaces 43 Relat[...]

  • Page 6

    Disabling LACP Graceful Convergence 61 Reenabling LACP Graceful Convergence 62 V erifying Port Channel Configuration 63 V erifying the Load-Balancing Outgoing Port ID 64 CHAPTER 5 Configuring V irtual Port Channels 65 Information About vPCs 65 vPC Overview 65 T erminology 67 vPC T erminology 67 Fabric Extender T erminology 67 Supported vPC T opolog[...]

  • Page 7

    Enabling vPCs 80 Disabling vPCs 80 Creating a vPC Domain 81 Configuring a vPC Keepalive Link and Messages 82 Creating a vPC Peer Link 84 Checking the Configuration Compatibility 85 Enabling vPC Auto-Recovery 86 Suspending Orphan Ports on a Secondary Switch in a vPC T opology 87 Creating an EtherChannel Host Interface 88 Moving Other Port Channels i[...]

  • Page 8

    Cisco Nexus 5000 Series NX-OS Interfaces Configuration Guide, Release 5.2(1)N1(1) viii 78-26881-OL Contents[...]

  • Page 9

    Preface This preface contains the following sections: • Audience, page ix • Document Conventions, page ix • Documentation Feedback , page x • Obtaining Documentation and Submitting a Service Request, page xi Audience This publication is for experienced network administrators who configure and maintain Cisco Nexus devices and Cisco Nexus 200[...]

  • Page 10

    Description Convention Nested set of square brackets or braces indicate optional or required choices within optional or required elements. Braces and a vertical bar within square brackets indicate a required choice within an optional element. [x {y | z}] Indicates a variable for which you supply values, in context where italics cannot be used. vari[...]

  • Page 11

    Obtaining Documentation and Submitting a Service Request For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Pr oduct Documentation , which also lists all new and revised Cisco technical documentation, at: http://www .cisco.com/en/US/docs/general/wh[...]

  • Page 12

    Cisco Nexus 5000 Series NX-OS Interfaces Configuration Guide, Release 5.2(1)N1(1) xii 78-26881-OL Preface Obtaining Documentation and Submitting a Service Request[...]

  • Page 13

    CHAPTER 1 New and Changed Information for this Release The following table provides an overview of the significant changes to this guide for this current release. The table does not provide an exhaustive list of all changes made to the configuration guides or of the new features in this release. • New and Changed Information for this Release, pag[...]

  • Page 14

    Cisco Nexus 5000 Series NX-OS Interfaces Configuration Guide, Release 5.2(1)N1(1) 2 78-26881-OL New and Changed Information for this Release New and Changed Information for this Release[...]

  • Page 15

    CHAPTER 2 Configuring Layer 2 Interfaces This chapter contains the following sections: • Information About Ethernet Interfaces, page 3 • Configuring Ethernet Interfaces, page 10 • Displaying Interface Information, page 29 • Default Physical Ethernet Settings , page 31 Information About Ethernet Interfaces The Ethernet ports can operate as s[...]

  • Page 16

    The interface numbering convention is extended to support use with a Cisco Nexus 2000 Series Fabric Extender as follows: switch(config)# interface ethernet [ chassis /] slot / port • Chassis ID is an optional entry to address the ports of a connected Fabric Extender. The chassis ID is configured on a physical Ethernet or EtherChannel interface on[...]

  • Page 17

    About the Unidirectional Link Detection Parameter The Cisco-proprietary Unidirectional Link Detection (UDLD) protocol allows ports that are connected through fiber optics or copper (for example, Category 5 cabling) Ethernet cables to monitor the physical configuration of the cables and detect when a unidirectional link exists. When the switch detec[...]

  • Page 18

    T able 2: UDLD Default Configuration Default V alue Feature Globally disabled UDLD global enable state Disabled UDLD aggressive mode Enabled on all Ethernet fiber-optic LAN ports UDLD per-port enable state for fiber-optic media Disabled on all Ethernet 10/100 and 1000BASE-TX LAN ports UDLD per-port enable state for twisted-pair (copper) media UDLD [...]

  • Page 19

    CDP runs on all media that support Subnetwork Access Protocol (SNAP). Because CDP runs over the data-link layer only , two systems that support different network-layer protocols can learn about each other . Each CDP-configured device sends periodic messages to a multicast address, advertising at least one address at which it can receive SNMP messag[...]

  • Page 20

    About Port Profiles Y ou can create a port profile that contains many interface commands and apply that port profile to a range of interfaces on the Cisco Nexus device. Port profiles can be applied to the following interface types: • Ethernet • VLAN network interface • Port channel A command that is included in a port profile can be configure[...]

  • Page 21

    Guidelines and Limitations for Port Profiles Port profiles have the following configuration guidelines and limitations: • Each port profile must have a unique name across interface types and the network. • Commands that you enter under the interface mode take precedence over the port profile’ s commands if there is a conflict. However , the p[...]

  • Page 22

    Configuring Ethernet Interfaces The section includes the following topics: Configuring a Layer 3 Interface on a Cisco Nexus 5500 Platform Switch On Cisco Nexus devices, you can configure a Layer 3 interface. Y ou can change a Layer 3 interface into a Layer 2 interface by using the switchport command. Y ou can change a Layer 2 interface into a Layer[...]

  • Page 23

    If you're configuring a unified port as Fibre Channel or FCoE, confirm that you have enabled the feature fcoe command. Procedure Purpose Command or Action Enters global configuration mode. switch# configure terminal Step 1 Identifies the slot on the switch. switch(config) # slot slot number Step 2 Configures a unified port as a native Fibre Ch[...]

  • Page 24

    Configuring the UDLD Mode Y ou can configure normal or aggressive unidirectional link detection (UDLD) modes for Ethernet interfaces on devices configured to run UDLD. Before you can enable a UDLD mode for an interface, you must make sure that UDLD is already enabled on the device that includes the interface. UDLD must also be enabled on the other [...]

  • Page 25

    switch(config)# interface ethernet 1/4 switch(config-if)# udld disable This example shows how to disable UDLD for the switch: switch# configure terminal switch(config)# no feature udld Configuring Interface Speed The first 32 ports of a Cisco Nexus 5596T switch are switchable 1-Gigabit and 10-Gigabit ports. Y ou can also configure them to auto-nego[...]

  • Page 26

    Disabling Link Negotiation Y ou can disable link negotiation using the no negotiate auto command. By default, auto-negotiation is enabled on 1-Gigabit ports and disabled on 10-Gigabit ports. This command is equivalent to the Cisco IOS speed non-negotiate command. W e do not recommend that you enable auto negotiation on 10-Gigabit ports. Enabling au[...]

  • Page 27

    Procedure Purpose Command or Action Enters configuration mode. switch# configure terminal Step 1 (Optional) Configures the version to use to send CDP advertisements. V ersion-2 is the default state. switch(config)# [ no ] cdp advertise { v1 | v2 } Step 2 Use the no form of the command to return to its default setting. (Optional) Configures the form[...]

  • Page 28

    Procedure Purpose Command or Action Enters configuration mode. switch# configure terminal Step 1 Enters interface configuration mode for the specified interface. switch(config)# interface type slot / port Step 2 Enables CDP for the interface. switch(config-if)# cdp enable Step 3 T o work correctly , this parameter must be enabled for both interface[...]

  • Page 29

    Purpose Command or Action Brings the interface up administratively and enables the interface to recover manually from the err-disabled state. no shutdown Example: switch(config)# no shutdown switch(config)# Step 4 Displays information about err-disabled interfaces. show interface status err-disabled Example: switch(config)# show interface status er[...]

  • Page 30

    Purpose Command or Action Displays information about err-disabled interfaces. show interface status err-disabled Example: switch(config)#show interface status err-disabled Step 3 (Optional) Copies the running configuration to the startup configuration. copy running-config startup-config Example: switch(config)#copy running-config startup-config Ste[...]

  • Page 31

    This example shows how to enable err-disabled recovery under all conditions: switch(config)# errdisable recovery cause all switch(config)# Port Profiles Creating a Port Profile Y ou can create a port profile on the switch. Each port profile must have a unique name across interface types and the network. Procedure Purpose Command or Action Enters co[...]

  • Page 32

    This example shows how to add the interface commands to a port profile named ppEth configured for Ethernet interfaces: switch# configure terminal switch(config)# port-profile ppEth switch(config-port-prof)# switchport mode trunk switch(config-port-prof)# switchport trunk allowed vlan 300-400 switch(config-port-prof)# flowcontrol receive on switch(c[...]

  • Page 33

    This example shows how to remove commands from the port profile named ppEth configured for an Ethernet interface: switch# configure terminal switch(config)# port-profile ppEth switch(config-port-prof)# switchport mode trunk switch(config-port-prof)# switchport trunk allowed vlan 300-400 switch(config-port-prof)# flowcontrol receive on switch(config[...]

  • Page 34

    This example shows how to enter port profile configuration mode and enable the port profile: switch# configure terminal switch(config)# port-profile type ethernet test switch(config-port-prof)# state enabled switch(config-port-prof)# Inheriting a Port Profile Y ou can inherit a port profile onto an existing port profile. The switch supports four le[...]

  • Page 35

    This example shows how to add the interface commands to a port profile named ppEth configured for Ethernet interfaces: switch# configure terminal switch(config)# port-profile ppEth switch(config-port-prof)# switchport mode trunk switch(config-port-prof)# switchport trunk allowed vlan 300-400 switch(config-port-prof)# flowcontrol receive on switch(c[...]

  • Page 36

    Purpose Command or Action Exits the port profile configuration mode. exit Example: switch(config-port-prof)# exit switch(config)# Step 4 (Optional) Displays the port profile configuration. show port-profile Example: switch(config)# show port-profile name Step 5 (Optional) Copies the running configuration to the startup configuration. copy running-c[...]

  • Page 37

    Purpose Command or Action Exits port profile configuration mode. exit Example: switch(config-port-prof)# exit switch(config)# Step 4 (Optional) Displays the port profile configuration. show port-profile Example: switch(config)# show port-profile name Step 5 (Optional) Copies the running configuration to the startup configuration. copy running-confi[...]

  • Page 38

    Purpose Command or Action Exits port profile configuration mode. exit Example: switch(config-port-prof)# exit switch(config)# Step 4 (Optional) Displays the port profile configuration. show port-profile Example: switch(config)# show port-profile name Step 5 (Optional) Copies the running configuration to the startup configuration. copy running-confi[...]

  • Page 39

    switch(config-port-prof)# sh running-config interface ethernet 1/14 !Command: show running-config interface Ethernet1/14 !Time: Thu Aug 26 07:03:17 2010 version 5.0(2)N1(1) interface Ethernet1/14 inherit port-profile alpha switch(config-port-prof)# sh running-config interface ethernet 1/14 expand-port-profile !Command: show running-config interface[...]

  • Page 40

    Configuring the Description Parameter Y ou can provide textual interface descriptions for the Ethernet ports. Procedure Purpose Command or Action Enters configuration mode. switch# configure terminal Step 1 Enters interface configuration mode for the specified interface. switch(config)# interface type slot / port Step 2 Specifies the description fo[...]

  • Page 41

    This example shows how to restart an Ethernet interface: switch# configure terminal switch(config)# interface ethernet 1/4 switch(config-if)# no shutdown Displaying Interface Information T o view configuration information about the defined interfaces, perform one of these tasks: Purpose Command Displays the detailed configuration of the specified i[...]

  • Page 42

    0 crc 0 Ignored 0 Bad etype drop 0 Bad proto drop Tx 119038487241 output packets 119038487245 multicast packets 0 broadcast packets 0 jumbo packets 7618463256471 bytes 0 output CRC 0 ecc 0 underrun 0 if down drop 0 output error 0 collision 0 deferred 0 late collision 0 lost carrier 0 no carrier 0 babble 0 Rx pause 8031547972 Tx pause 0 reset This e[...]

  • Page 43

    Eth1/3 enable 100 ... This example shows how to display the CDP neighbors: The default device ID field for CDP advertisement is the hostname and serial number , as in the example above. Note switch# show cdp neighbors Capability Codes: R - Router, T - Trans-Bridge, B - Source-Route-Bridge S - Switch, H - Host, I - IGMP, r - Repeater, V - VoIP-Phone[...]

  • Page 44

    Cisco Nexus 5000 Series NX-OS Interfaces Configuration Guide, Release 5.2(1)N1(1) 32 78-26881-OL Configuring Layer 2 Interfaces Default Physical Ethernet Settings[...]

  • Page 45

    CHAPTER 3 Configuring Layer 3 Interfaces This chapter contains the following sections: • Information About Layer 3 Interfaces, page 33 • Licensing Requirements for Layer 3 Interfaces, page 36 • Guidelines and Limitations for Layer 3 Interfaces, page 36 • Default Settings for Layer 3 Interfaces, page 36 • Configuring Layer 3 Interfaces, pa[...]

  • Page 46

    Y ou can assign an IP address to the port, enable routing, and assign routing protocol characteristics to this routed interface. Y ou can assign a static MAC address to a Layer 3 interface. For information on configuring MAC addresses, see the Layer 2 Switching Configuration Guide for your device. Y ou can also create a Layer 3 port channel from ro[...]

  • Page 47

    VLAN Interfaces A VLAN interface or a switch virtual interface (SVI) is a virtual routed interface that connects a VLAN on the device to the Layer 3 router engine on the same device. Only one VLAN interface can be associated with a VLAN, but you need to configure a VLAN interface for a VLAN only when you want to route between VLANs or to provide IP[...]

  • Page 48

    Y ou can use loopback interfaces for performance analysis, testing, and local communications. Loopback interfaces can act as a termination address for routing protocol sessions. This loopback configuration allows routing protocol sessions to stay up even if some of the outbound interfaces are down. T unnel Interfaces Cisco NX-OS supports tunnel int[...]

  • Page 49

    Purpose Command or Action T o convert a Layer 3 interface back into a Layer 2 interface, use the switchport command. Note Configures an IP address for this interface. switch(config-if)# [ ip | ipv6 ] ip-addr ess/length Step 4 (Optional) Configures the interface medium as either point to point or broadcast. switch(config-if)# medium { broadcast | p2[...]

  • Page 50

    Purpose Command or Action Enters interface configuration mode. The range for the slot is from 1 to 255. The range for the port is from 1 to 128. switch(config)# interface ethernet slot/port . number Step 2 Configures IP address for this interface. switch(config-if)# [ ip | ipv6 ] address ip-addr ess/length Step 3 Configures IEEE 802.1Q VLAN encapsu[...]

  • Page 51

    Purpose Command or Action (Optional) Saves the change persistently through reboots and restarts by copying the running configuration to the startup configuration. switch(config-if)# copy running-config startup-config Step 4 This example shows how to configure Ethernet interface 2/1 with a bandwidth value of 80000: switch# configure terminal switch([...]

  • Page 52

    Configuring a Loopback Interface Before Y ou Begin Ensure that the IP address of the loopback interface is unique across all routers on the network. Procedure Purpose Command or Action Enters global configuration mode. switch# configure terminal Step 1 Creates a loopback interface. The instance range is from 0 to 1023. switch(config)# interface loo[...]

  • Page 53

    Purpose Command or Action Adds this interface to a VRF . switch(conifg-if)# vrf member vrf-name Step 3 Configures an IP address for this interface. Y ou must do this step after you assign this interface to a VRF . switch(config-if)# [ ip | ipv6 ] ip-addr ess/length Step 4 (Optional) Displays VRF information. switch(config-if)# show vrf [ vrf-name ][...]

  • Page 54

    Purpose Command Displays the subinterface configuration, status, and counters (including the f-minute exponentially decayed moving average of inbound and outbound packet and byte rates). show interface ethernet slot/port . number Displays the port-channel subinterface configuration, status, and counters (including the 5-minute exponentially decayed[...]

  • Page 55

    Purpose Command Displays the Layer 3 interface statistics. Y ou can optionally include all 32-bit and 64-bit packet and byte counters (including errors). show interface ethernet slot / port counters detailed [ all ] Displays the Layer 3 interface input and output errors. show interface ethernet slot / port counters error Displays the Layer 3 interf[...]

  • Page 56

    This example shows how to configure a VLAN interface: switch# configuration terminal switch(config)# interface vlan 100 switch(config-if)# no switchport switch(config-if)# ipv6 address 33:0DB::2/8 switch(config-if)# copy running-config startup-config This example shows how to configure a loopback interface: switch# configuration terminal switch(con[...]

  • Page 57

    CHAPTER 4 Configuring Port Channels This chapter contains the following sections: • Information About Port Channels, page 45 • Configuring Port Channels, page 54 • V erifying Port Channel Configuration, page 63 • V erifying the Load-Balancing Outgoing Port ID , page 64 Information About Port Channels A port channel bundles individual interf[...]

  • Page 58

    channels. For information on port channel configuration limits, see the V erified Scalability document for your platform. For more information about load balancing, see Load Balancing Using Port Channels, on page 48 . Cisco NX-OS does not support Port Aggregation Protocol (P AgP) for port channels. Note A port channel bundles individual links into [...]

  • Page 59

    • If a port channel is created in global configuration mode, channel groups including member interfaces must also be created using global configuration mode. • Port channels that are configured within switch profile mode may have members both inside and outside of a switch profile. • If you want to import a member interface to a switch profil[...]

  • Page 60

    • Description • CDP • LACP port priority • Debounce After you enable forcing a port to be added to a channel group by entering the channel-group force command, the following two conditions occur: • When an interface joins a port channel the following parameters are removed and they are operationally replaced with the values on the port ch[...]

  • Page 61

    • For a Layer 4 frame, it uses the source and destination MAC addresses and the source and destination IP addresses. Y ou have the option to include the source and destination port number for the Layer 4 frame. Note Y ou can configure the switch to use one of the following methods (see the following table for more details) to load balance across [...]

  • Page 62

    Layer 4 Criteria Layer 3 Criteria Layer 2 Criteria Configuration Source and destination MAC, source and destination IP , source and destination port Source and destination MAC, source and destination IP Source and destination MAC Source and destination TCP/UDP port Fabric Extenders are not configurable individually . Fabric extender configurations [...]

  • Page 63

    Layer 4 Criteria Layer 3 Criteria Layer 2 Criteria Configuration Source and destination MAC, source and destination IP , and source and destination port Source and destination MAC, source and destination IP Source and destination MAC Source and destination TCP/UDP port Use the option that provides the balance criteria with the greatest variety in y[...]

  • Page 64

    LACP ID Parameters LACP uses the following parameters: • LACP system priority—Each system that runs LACP has an LACP system priority value. Y ou can accept the default value of 32768 for this parameter , or you can configure a value between 1 and 65535. LACP uses the system priority with the MAC address to form the system ID and also uses the s[...]

  • Page 65

    T able 6: Channel Modes for Individual Links in a Port channel Description Channel Mode LACP mode that places a port into a passive negotiating state, in which the port responds to LACP packets that it receives but does not initiate LACP negotiation. passive LACP mode that places a port into an active negotiating state, in which the port initiates [...]

  • Page 66

    LACP-Enabled and Static Port Channel Differences The following table provides a brief summary of major differences between port channels with LACP enabled and static port channels. For information about the maximum configuration limits, see the V erified Scalability document for your device. T able 7: Port channels with LACP Enabled and Static Port[...]

  • Page 67

    Adding a Port to a Port Channel Y ou can add a port to a new channel group or to a channel group that already contains ports. Cisco NX-OS creates the port channel associated with this channel group if the port channel does not already exist. If you want LACP-based port channels, you need to enable LACP . Note Procedure Purpose Command or Action Ent[...]

  • Page 68

    Procedure Purpose Command or Action Enters configuration mode. switch# configure terminal Step 1 Specifies the load-balancing algorithm for the device. The range depends on the device. The default is source-dest-mac. switch(config)# port-channel load-balance ethernet {[ destination-ip | destination-mac | Step 2 destination-port | source-dest-ip | B[...]

  • Page 69

    Configuring Hardware Hashing for Multicast T raffic By default, ingress multicast traf fic on any port in the switch selects a particular port channel member to egress the traffic. Y ou can configure hardware hashing for multicast traf fic to reduce potential bandwidth issues and to provide effective load balancing of the ingress multicast traffic.[...]

  • Page 70

    This example shows how to enable LACP: switch# configure terminal switch(config)# feature lacp Configuring the Channel Mode for a Port Y ou can configure the channel mode for each individual link in the LACP port channel as active or passive. This channel configuration mode allows the link to operate with LACP . When you configure port channels wit[...]

  • Page 71

    This example shows how to set the LACP-enabled interface to active port-channel mode for Ethernet interface 1/4 in channel group 5: switch# configure terminal switch (config)# interface ethernet 1/4 switch(config-if)# channel-group 5 mode active This example shows how to forcefully add an interface to the channel group 5: switch(config)# interface [...]

  • Page 72

    Configuring the LACP System Priority and System ID The LACP system ID is the combination of the LACP system priority value and the MAC address. Before Y ou Begin Ensure that you have enabled the LACP feature. Procedure Purpose Command or Action Enters configuration mode. switch# configure terminal Step 1 Configures the system priority for use with [...]

  • Page 73

    This example shows how to set the LACP port priority for Ethernet interface 1/4 to 40000: switch# configure terminal switch (config)# interface ethernet 1/4 switch(config-if)# lacp port priority 40000 Disabling LACP Graceful Convergence Before Y ou Begin • Enable the LACP feature. • Confirm that the port channel is in the administratively down [...]

  • Page 74

    Purpose Command or Action (Optional) Saves the change persistently through reboots and restarts by copying the running configuration to the startup configuration. copy running-config startup-config Example: switch(config-if)# copy running-config startup-config Step 6 The following example disables LACP graceful convergence on a port channel: switch[...]

  • Page 75

    Purpose Command or Action Enables LACP graceful convergence on the specified port channel. lacp graceful-convergence Example: switch(config-if)# lacp graceful-convergence switch(config-if) # Step 4 Administratively brings the port channel up. no shutdown Example: switch(config-if)# no shutdown switch(config-if) # Step 5 (Optional) Saves the change [...]

  • Page 76

    Purpose Command Displays a summary for the port channel interfaces. switch# show port-channel summary Displays the traffic statistics for port channels. switch# show port-channel traffic Displays the range of used and unused channel numbers. switch# show port-channel usage Displays information on current running of the port channel feature. switch#[...]

  • Page 77

    CHAPTER 5 Configuring V irtual Port Channels This chapter contains the following sections: • Information About vPCs, page 65 • Guidelines and Limitations for vPCs, page 79 • Configuring vPCs, page 80 • Configuring the vPC Peer Switch, page 93 • V erifying the vPC Configuration, page 95 • vPC Example Configurations, page 101 • vPC Defa[...]

  • Page 78

    which allows you to create redundancy by enabling multiple parallel paths between nodes and load balancing traffic where alternative paths exist. Figure 5: vPC Architecture Y ou configure the EtherChannels by using one of the following: • No protocol • Link Aggregation Control Protocol (LACP) When you configure the EtherChannels in a vPC—incl[...]

  • Page 79

    A vPC provides the following benefits: • Allows a single device to use an EtherChannel across two upstream devices • Eliminates Spanning T ree Protocol (STP) blocked ports • Provides a loop-free topology • Uses all available uplink bandwidth • Provides fast convergence if either the link or a switch fails • Provides link-level resilienc[...]

  • Page 80

    • Host interface—An Ethernet interface for server or host connectivity . These ports are 1-Gigabit Ethernet interfaces or 10-Gigabit Ethernet interfaces, depending on the fabric extender model. • EtherChannel host interface—An EtherChannel downlink connection from the Fabric Extender host interface to a server port. An EtherChannel host int[...]

  • Page 81

    Single Homed Fabric Extender vPC T opology Y ou can connect a server with dual or quad or more network adapters that are configured in a vPC to a pair of Cisco Nexus Fabric Extenders which are connected to the Cisco Nexus devices as depicted. Depending on the FEX model, you may be able to connect one or more network adapter interfaces to each fabri[...]

  • Page 82

    Dual Homed Fabric Extender vPC T opology Y ou can connect the Cisco Nexus Fabric Extender to two upstream Cisco Nexus devices and downstream to a number of single homed servers. The topology shown in the following figure provides the vPC functionality to singly connected servers with 1-Gigabit Ethernet uplink interfaces. Figure 8: Dual Homed Fabric[...]

  • Page 83

    If you manually configure the system priority , you must ensure that you assign the same priority value on both vPC peer switches. If the vPC peer switches have dif ferent system priority values, the vPC will not come up. Note Peer -Keepalive Link and Messages The Cisco NX-OS software uses a peer-keepalive link between the vPC peers to transmit per[...]

  • Page 84

    Y ou must ensure that all interfaces in the vPC have the identical operational and configuration parameters listed in this section. Enter the show vpc consistency-parameters command to display the configured values on all interfaces in the vPC. The displayed configurations are only those configurations that would limit the vPC peer link and vPC fro[...]

  • Page 85

    T o ensure that none of the vPC interfaces are in the suspend mode, enter the show vpc brief and show vpc consistency-parameters commands and check the syslog messages. Note Configuration Parameters That Should Be Identical When any of the following parameters are not configured identically on both vPC peer switches, a misconfiguration may cause un[...]

  • Page 86

    Per -VLAN Consistency Check Beginning with Cisco NX-OS Release 5.0(2)N2(1), some T ype-1 consistency checks are performed on a per-VLAN basis when spanning tree is enabled or disabled on a VLAN. VLANs that do not pass the consistency check are brought down on both the primary and secondary switches while other VLANs are not affected. vPC Auto-Recov[...]

  • Page 87

    Y ou must ensure that the two switches connected by the vPC peer link have certain identical operational and configuration parameters. Note When you configure the vPC peer link, the vPC peer switches negotiate that one of the connected switches is the primary switch and the other connected switch is the secondary switch. By default, the Cisco NX-OS[...]

  • Page 88

    vPC Interactions with Other Features Configuring vPC Peer Links and Links to the Core Configure the command line interface by using a track object and a track list that is associated with the Layer 3 link to the core and on all vPC peer links on both vPC peer devices. Y ou use this configuration to avoid dropping traffic if that particular module g[...]

  • Page 89

    Purpose Command or Action Exits track configuration mode. switch(config-track)# end Step 8 Enters vPC domain configuration. switch(config)# vpc domain domain-id Step 9 Adds the track object to the vPC domain. switch(config-vpc-domain)# track number Step 10 (Optional) Displays the track object. switch(config)# show vpc brief Step 11 (Optional) Saves[...]

  • Page 90

    W e recommend that you set all the vPC peer link interfaces to the STP network port type so that Bridge Assurance is automatically enabled on all vPC peer links. W e also recommend that you do not enable any of the STP enhancement features on VPC peer links. Y ou must configure a list of parameters to be identical on the vPC peer switches on both s[...]

  • Page 91

    Do not enter the no cfs eth distribute or the no cfs distribute command. CFSoE must be enabled for vPC functionality . If you do enter either of these commands when vPC is enabled, the system displays an error message. Note When you enter the show cfs application command, the output displays "Physical-eth," which shows the applications th[...]

  • Page 92

    • A Fabric Extender can be a member of a Host Interface vPC topology or a Fabric Extender vPC topology but not both simultaneously . • Y ou must configure both vPC peer switches; the configuration is not automatically synchronized between the vPC peer devices. • Check that the necessary configuration parameters are compatible on both sides of[...]

  • Page 93

    When you disable the vPC feature, the Cisco Nexus device clears all the vPC configurations. Note Procedure Purpose Command or Action Enters configuration mode. switch# configure terminal Step 1 Disables vPCs on the switch. switch(config)# no featur e vpc Step 2 (Optional) Displays which features are enabled on the switch. switch# show feature Step [...]

  • Page 94

    Purpose Command or Action (Optional) Displays brief information about each vPC domain. switch# show vpc brief Step 3 (Optional) Copies the running configuration to the startup configuration. switch# copy running-config startup-config Step 4 This example shows how to create a vPC domain: switch# configure terminal switch(config)# vpc domain 5 Config[...]

  • Page 95

    Procedure Purpose Command or Action Enters configuration mode. switch# configure terminal Step 1 Creates a vPC domain on the switch if it does not already exist, and enters the vpc-domain configuration mode. switch(config)# vpc domain domain-id Step 2 Configures the IPv4 address for the remote end of the vPC peer-keepalive link. switch(config-vpc-d[...]

  • Page 96

    interface Ethernet1/31 switchport access vlan 123 interface Vlan123 vrf member vpc_keepalive ip address 123.1.1.2/30 no shutdown vpc domain 1 peer-keepalive destination 123.1.1.1 source 123.1.1.2 vrf vpc_keepalive L3-NEXUS-2# sh vpc peer-keepalive vPC keep-alive status : peer is alive --Peer is alive for : (154477) seconds, (908) msec --Send status[...]

  • Page 97

    Procedure Purpose Command or Action Enters configuration mode. switch# configure terminal Step 1 Selects the EtherChannel that you want to use as the vPC peer link for this switch, and enters the interface configuration mode. switch(config)# interface port-channel channel-number Step 2 Configures the selected EtherChannel as the vPC peer link, and [...]

  • Page 98

    This example shows how to check that the required configurations are compatible across all the vPC interfaces: switch# show vpc consistency-parameters global Legend: Type 1 : vPC will be suspended in case of mismatch Name Type Local Value Peer Value ------------- ---- ---------------------- ----------------------- QoS 2 ([], [], [], [], [], ([], [][...]

  • Page 99

    Purpose Command or Action Enables the auto-recovery feature and sets the reload delay period. The default is disabled. switch(config-vpc-domain)# auto-recovery reload-delay delay Step 3 This example shows how to enable the auto-recovery feature in vPC domain 10 and set the delay period for 240 seconds. switch(config)# vpc domain 10 switch(config-vp[...]

  • Page 100

    Purpose Command or Action The vpc-orphan-port suspend command is supported only on physical ports. Note Exits interface configuration mode. switch(config-if)# exit Step 4 (Optional) Displays the orphan port configuration. switch# show vpc orphan-port Step 5 (Optional) Copies the running configuration to the startup configuration. switch# copy runni[...]

  • Page 101

    Y ou must configure both switches on either side of the vPC peer link with the following procedure. Procedure Purpose Command or Action Enters configuration mode. switch# configure terminal Step 1 Specifies an interface to configure, and enters interface configuration mode. switch(config)# interface ethernet chassis / slot / port Step 2 Creates an [...]

  • Page 102

    Purpose Command or Action Configures the selected port channel into the vPC to connect to the downstream switch. The range is from 1 to 4096. switch(config-if)# vpc number Step 3 The vPC number that you assign to the port channel connecting to the downstream switch from the vPC peer switch must be identical on both vPC peer switches. (Optional) Dis[...]

  • Page 103

    Purpose Command or Action (Optional) Copies the running configuration to the startup configuration. switch# copy running-config startup-config Step 5 This example shows how to configure a vPC domain MAC address: switch# configure terminal switch(config)# vpc domain 5 switch(config-if)# system-mac 23fb.4ab5.4c4e Manually Configuring the System Prior[...]

  • Page 104

    This example shows how to configure a vPC peer link: switch# configure terminal switch(config)# vpc domain 5 switch(config-if)# system-priority 4000 Manually Configuring a vPC Peer Switch Role By default, the Cisco NX-OS software elects a primary and secondary vPC peer switch after you configure the vPC domain and both sides of the vPC peer link. H[...]

  • Page 105

    Configuring the vPC Peer Switch Configuring a Pure vPC Peer Switch T opology Y ou can configure a pure vPC peer switch topology using the peer-switch command and then you set the best possible (lowest) spanning tree bridge priority value. The values you apply for the spanning tree priority must be identical on both vPC peers. Note Before Y ou Begin[...]

  • Page 106

    This example shows how to configure a pure vPC peer switch topology: switch# configure terminal Enter configuration commands, one per line. End with CNTL/Z. switch(config)# vpc domain 5 switch(config-vpc-domain)# peer-switch 2010 Apr 28 14:44:44 switch %STP-2-VPC_PEERSWITCH_CONFIG_ENABLED: vPC peer-switch configuration is enabled. Please make sure [...]

  • Page 107

    Purpose Command or Action Configures the designated bridge priority of the VLAN. V alid values are multiples of 4096 from 0 to 61440. switch(config-pseudo)# vlan vlan-id designated priority priority Step 3 Configures the root bridge priority of the VLAN. V alid values are multiples of 4096 from 0 to 61440. switch(config-pseudo)# vlan vlan-id root p[...]

  • Page 108

    Purpose Command Displays whether vPC is enabled or not. switch# show feature Displays how many EtherChannels are configured and how many are still available on the switch. switch# show port-channel capacity Displays running configuration information for vPCs. switch# show running-config vpc Displays brief information on the vPCs. switch# show vpc b[...]

  • Page 109

    V iewing A Global T ype-1 Inconsistency When a global T ype-1 inconsistency occurs, the vPCs on the secondary switch are brought down. The following example shows this type of inconsistency when there is a spanning-tree mode mismatch. The example shows how to display the status of the suspended vPC VLANs on the secondary switch: switch(config)# sho[...]

  • Page 110

    20 Po20 up failed Global compat check failed 1-10 30 Po30 up failed Global compat check failed 1-10 V iewing An Interface-Specific T ype-1 Inconsistency When an interface-specific T ype-1 inconsistency occurs, the vPC port on the secondary switch is brought down while the primary switch vPC ports remain up.The following example shows this type of i[...]

  • Page 111

    ---------------------------------------------------------------------------- id Port Status Consistency Reason Active vlans ------ ----------- ------ ----------- -------------------------- ----------- 20 Po20 up success success 1 30 Po30 up failed Compatibility check failed 1 for port mode V iewing a Per -VLAN Consistency Status T o view the per-VL[...]

  • Page 112

    -- ---- ------ -------------------------------------------------- 1 Po1 up 1-4,6-10 vPC status ---------------------------------------------------------------------------- id Port Status Consistency Reason Active vlans ------ ----------- ------ ----------- -------------------------- ----------- 20 Po20 up success success 1-4,6-10 30 Po30 up success[...]

  • Page 113

    vPC Example Configurations Dual Homed Fabric Extender vPC Configuration Example The following example shows how to configure the dual homed Fabric Extender vPC topology using the management VRF to carry the peer-keepalive messages on switch NX-5000-1 as shown in following figure: Figure 9: vPC Configuration Example Before Y ou Begin Ensure that the[...]

  • Page 114

    Step 4 Create a Fabric Extender identifier (for example, "100"). NX-5000-1(config)# fex 100 NX-5000-1(config-fex)# pinning max-links 1 NX-5000-1(fex)# exit Step 5 Configure the fabric EtherChannel links for the Fabric Extender 100. NX-5000-1(config)# interface ethernet 1/20 NX-5000-1(config-if)# channel-group 100 NX-5000-1(config-if)# exi[...]

  • Page 115

    Single Homed Fabric Extender vPC Configuration Example The following example shows how to configure the single homed Fabric Extender vPC topology using the default VRF to carry the peer-keepalive messages on switch NX-5000-1 as shown in following figure: Figure 10: vPC Configuration Example The following example only shows the configuration of NX-5[...]

  • Page 116

    Step 2 Enable SVI interfaces, create the VLAN and SVI to be used by the vPC peer-keepalive link. NX-5000-1(config)# feature interface-vlan NX-5000-1(config)# vlan 900 NX-5000-1(config-vlan)# int vlan 900 NX-5000-1(config-if)# ip address 10.10.10.236 255.255.255.0 NX-5000-1(config-if)# no shutdown NX-5000-1(config-if)# exit Step 3 Create the vPC dom[...]

  • Page 117

    Step 7 Configure a vPC server port on on the Fabric Extender NX-2000-100. NX-5000-1(config-if)# interface ethernet 100/1/1 NX-5000-1(config-if)# switchport mode trunk NX-5000-1(config-if)# switchport trunk native vlan 100 NX-5000-1(config-if)# switchport trunk allowed vlan 100-105 NX-5000-1(config-if)# channel-group 600 NX-5000-1(config-if)# no shu[...]

  • Page 118

    Cisco Nexus 5000 Series NX-OS Interfaces Configuration Guide, Release 5.2(1)N1(1) 106 78-26881-OL Configuring Virtual Port Channels vPC Default Settings[...]

  • Page 119

    INDEX A adding ports 55 port channels 55 B bandwidth 38 configuring 38 C changed information 1 description 1 channel mode 58 port channels 58 channel modes 52 port channels 52 configuration 41 Layer 3 interfaces 41 verifying 41 configuration examples 43 Layer 3 interfaces 43 configuring 36, 37, 38, 39, 40 interface bandwidth 38 loopback interfaces [...]

  • Page 120

    I interface information, displaying 29 layer 2 29 interface speed 6, 13 configuring 13 interfaces 3, 5, 33, 35, 36, 38, 39, 40, 42, 43 assigning to a VRF 40 chassis ID 3 configuring bandwidth 38 Layer 3 33, 42, 43 configuration examples 43 monitoring 42 loopback 35, 40 options 3 routed 33 tunnel 36 UDLD 5 VLAN 35, 39 configuring 39 L LACP 45, 51, 5[...]

  • Page 121

    port profiles 8, 9 about 8 guidelines and limitations 9 port profiles 9 R related documents 44 Layer 3 interfaces 44 routed interfaces 33, 36, 38 configuring 36 configuring bandwidth 38 S SFP+ transceiver 6 Small form-factor pluggable (plus) transceiver 6 standards 44 Layer 3 interfaces 44 STP 45 port channel 45 subinterfaces 34, 37, 38 configuring[...]

  • Page 122

    Cisco Nexus 5000 Series NX-OS Interfaces Configuration Guide, Release 5.2(1)N1(1) IN-4 78-26881-OL Index[...]