You are on page 1of 46

Nexus 7000 Lab Guide

To have a successful E-Learning lab, it is important to go through page 1 – 4 before starting lab exercise!!!

System Verification
Identify Your Pod Number: Pod number can be found on the left upper corner Nexus7k_elearning – Nexus-7000-X , where X is your pod number. Make a note of your pod number on a paper.
Note:

In this doc, the interfaces referred in most of the output shown in these steps refer to Pod5. If you are on a different pod, please refer to the next session, Accounts and Password.

1

Accounts and Password
Once your pod number is identified, locate the Login/Password for your pod. Make a note of the credential and interfaces assigned to your pod on a paper for your pod. Don’t try to ping these IP addresses, the system are in a DMZ that doesn’t allow ping. Table 1 POD Information and Access Account
POD Information Login/Password Assigned Interfaces

POD 5
N7K-1 N7K-2 CAT 6K

admin/pod5nxos
n/a

9/1-8 10/1-5 6/1-2

POD 6
N7K-1 N7K-2 CAT 6K

admin/pod6nxos
n/a

9/9-16 10/13-17 6/1-2

POD 7
N7K-1 N7K-2 CAT 6K

admin/pod7nxos
n/a

9/17-24 10/25-29 6/1-2

POD 8
N7K-1 N7K-2 CAT 6K

admin/pod8nxos
n/a

9/25-32 10/37-41 6/1-2

2

Lab Topology and Access
Lab Topology
The diagram below represents the logical lab setup 0the diagram shows only your POD for simplicity)

Lab Access
Nexus 7000 requires console access to perform the initial configuration of the system. After performing the initial configuration, the system can be completely managed from the management interface. To Access Nexus 7000, click on the device icon and select Telnet.

3

For Cat6K, click on the device icon and select ClearLine first to make sure the line is cleared for Telnet.

Once the line is cleared, you will see “Clear Line success” message.

4

cisco.1(5) 4. N7K-C1-1-pod5# show version Cisco Nexus Operating System (NX-OS) Software TAC support: http://www. The copyrights to certain works contained in this software are owned by other third parties and used and distributed under license.904 1.903 Model -----------------N7K-SUP1 N7K-M132XP-12 N7K-M148GT-11 Status -----------active * ok ok Sw -------------4. Inc.com/tac Copyright (c) 2002-2009.1(5) 4.1(5) Mod --5 9 10 Mod --5 9 10 Xbar --1 2 Xbar --1 2 MAC-Address(es) -------------------------------------00-1b-54-c1-20-58 to 00-1b-54-c1-20-60 00-22-55-77-63-bc to 00-22-55-77-63-e0 00-1b-54-c1-29-40 to 00-1b-54-c1-29-74 Online Diag Status -----------------Pass Pass Pass Ports ----0 0 Module-Type -------------------------------Fabric Module 1 Fabric Module 1 Hw -----0. Cisco Systems.405 Serial-Num ---------JAB115200YK JAB122400HY JAB115101BV Model -----------------N7K-C7010-FAB-1 N7K-C7010-FAB-1 Status -----------ok ok Sw -------------NA NA Xbar --1 2 MAC-Address(es) -------------------------------------NA NA Serial-Num ---------JAB11520127 JAB1152012X Letʼs check now the software the system is running.3 0. Certain components of this software are licensed under the GNU General Public License (GPL) version 2.405 0.Lab Exercise N7K-C1-1-pod5# show module Mod --5 9 10 Mod --5 9 10 Ports ----0 32 48 Module-Type -------------------------------Supervisor module-1X 10 Gbps Ethernet Module 10/100/1000 Mbps Ethernet Module Hw -----0. All rights reserved. A copy of each 5 .0 or the GNU Lesser General Public License (LGPL) Version 2.1.

5-labops. 4 second(s) Last reset at 493509 usecs after Sat Apr 18 23:03:39 2009 Reason: Reset Requested by CLI command reload System version: 4. Ethernet Plugin Active Plug-in NX-OS is composed by two images: a kickstart image that contains the Linux Kernel and a system image that contain most of the NX-OS software components.4.1(5) [gdb] BIOS compile time: 01/31/08 kickstart image file is: bootflash:/n7000-s1-kickstart.4.gbin system compile time: 3/21/2009 12:00:00 [04/09/2009 09:06:08] Images Location Hardware cisco Nexus7000 C7010 (10 Slot) Chassis ("Supervisor module-1X") Intel(R) Xeon(R) CPU with 4135600 kB of memory. 21 minute(s).1(5) Service: plugin Core Plugin.org/licenses/lgpl-2.1.1.php and http://www.1. like the “Storage” plug-in for FCoE Letʼs now take a look at the running configuration.5-labops. 0 hour(s).opensource.such license is available at http://www.14. They both show up in the configuration. Note: Note: In future release we will be adding other plug-ins. N7K-C1-1-pod5# show running-config version 4.opensource. Processor Board ID JAB115200YK Device name: N7K-C1-1 bootflash: 2030616 kB slot0: 0 kB (expansion flash) Storage Devices CPU Kernel uptime is 0 day(s).1(5) <omitted config> vrf context management vlan 1-4 interface Ethernet9/1 These are the interfaces available to your Pod (Virtual Device Context) 6 .org/licenses/gpl-2.0.0 loader: version N/A NX-OS Version kickstart: version 4.php Software BIOS: version 3.1(5) [gdb] system: version 4.gbin kickstart compile time: 3/21/2009 12:00:00 [04/09/2009 08:01:41] system image file is: bootflash:/n7000-s1-dk9.

The keyword to be used is “all”. providing total isolation between the VDCs. As explained earlier each Pod runs within a Virtual Device Context (VDC).221.105/26 Management Interface Config This is the configuration of the first Pod.107. One of the improvements consists in the ability to not only look at the running-config but to also at the defaults values.255.105/26 ip redirects ip port-unreachable ip arp gratuitous update ip arp gratuitous request line vty session-limit 32 no exec-timeout line console no exec-timeout terminal length 24 terminal width 80 cfs distribute no cfs eth distribute cfs ipv4 mcast-address 239.107. Note: The “show running-config” has been improved. we can segment the physical Nexus 7000 in multiple logical switches each of which runs in a separate memory space and has visibility only of the hardware resources that it owns. which do not show up in the base config.83 cfs ipv6 mcast-address ff15::efff:4653 no cfs ipv4 distribute no cfs ipv6 distribute ip source-route <omitted output> 7 .interface Ethernet9/2 <omitted interface config> interface Ethernet2/16 interface mgmt0 ip address 128.70. N7K-C1-1-pod5# show running-config all | begin mgmt0 interface mgmt0 cdp enable description speed auto duplex auto no shutdown ip address 128. By using the VDC feature.221.

Verify that only the mgmt0 interface is part of the management VRF . by default. no.. Pod8 = 9/25 FastEthernet? GigabitEthernet?. part of the management VRF. DLY 10 usec..107.5577. Pod7 = 9/17. In this step we will: .5e50) Internet Address is 128. reliability 255/255. Management VRF and Basic Connectivity The management interface is. The management interface “mgmt0” is the only interface allowed to be part of this VRF. just “ethernet” interfaces N7K-C1-1-pod5(config-if)# show int mgmt0 mgmt0 is up Hardware: GigabitEthernet.5577. Note: N7K-C1-1-pod5# conf t N7K-C1-1-pod5(config)# interface ethernet 9/1 N7K-C1-1-pod5(config-if)# vrf member management % VRF management is reserved only for mgmt0 Pod6 = 9/9.2. BW 1000000 Kbit. The philosophy beyond Management VRF is to provide total isolation for the management traffic from the rest of the traffic flowing through the box by confining the former to its own forwarding table. Letʼs verify it.221. 1000 Mb/s 8 .Verify that no other interface can be part of the management VRF .Verify that the default gateway is reachable only using the management VRF N7K-C1-1-pod5# show vrf VRF-Name default management VRF-ID 1 2 State Up Up Reason --- N7K-C1-1-pod5# show vrf interface Interface mgmt0 Ethernet1/1 Ethernet1/2 Ethernet1/3 Ethernet1/4 Ethernet1/5 <omitted output> N7K-C1-1-pod5# show vrf management interface Interface mgmt0 VRF-Name management VRF-ID 2 VRF-Name management default default default default default VRF-ID 2 1 1 1 1 1 The management VRF interface is part of the default configuration and the management interface “mgmt0” is the only interface that can be made member of this VRF. rxload 1/255 Encapsulation ARPA full-duplex.5e50 (bia 0022.105/26 MTU 1500 bytes. address: 0022. txload 1/255.

107.107.65 64 chars.107.107.848 Linux-like output ms ms ms ms --.107.65 (128.107. Request 2 timed out ping: sendto 128.65 (128. Request 1 timed out ping: sendto 128.65 64 chars.816 time=0.65 ping statistics --5 packets transmitted.128.107.221.221.943 ms N7K-C1-1-pod5# 9 .65 64 chars.887 time=0.00% packet loss round-trip min/avg/max = 0.107. N7K-C1-1-pod5(config-if)# ping 128.816/0.221.107.221.65 64 chars.65 vrf management PING 128.65: icmp_seq=4 data bytes ttl=254 ttl=254 ttl=254 ttl=254 time=0.221.65: icmp_seq=3 64 bytes from 128. Request 3 timed out ping: sendto 128.221.221.221.221.128.221.65): 56 Request 0 timed out 64 bytes from 128.107.221.00% packet loss N7K-C1-1-pod5(config-if)# The ping fails because we are trying to reach a system on the out-of-band management network without specifying the correct VRF.65: icmp_seq=2 64 bytes from 128. Request 4 timed out 56 data bytes No route to host No route to host No route to host No route to host No route to host --.873/0.221.221.107.221.Auto-Negotiation is turned on 1 minute input rate 1264 bits/sec. 0 packets received. 0 packets/sec Rx 743 input packets 679 unicast packets 60 multicast packets 4 broadcast packets 70900 bytes Tx 567 output packets 542 unicast packets 23 multicast packets 2 broadcast packets 66407 bytes Try to reach the out-of-bound management networkʼs default gateway with a ping.107.65 ping statistics --5 packets transmitted. 1 packets/sec 1 minute output rate 1136 bits/sec.65: icmp_seq=1 64 bytes from 128.65): ping: sendto 128.107.221.107.107.943 time=0.65 64 chars.107.65 PING 128.107. 4 packets received.221.221. 100. Request 0 timed out ping: sendto 128. Note: N7K-C1-1-pod5# ping 128. 20.

D or Hostname WORD multicast IP address of remote system Enter Hostname Multicast ping CLI Hierarchy Independent N7K-C1-1-pod5(config-if)# ping 128. Every command can in fact be issued from anywhere in the configuration. However there are differences.221.C. One of the main differences consists in NX-OS implementing a hierarchy independent CLI.107. matching in (exec) mode *** <CR> A. As you may have already noticed.221.65 vrf management PING 128.65): 56 data bytes 64 bytes from 128.B.107.107.65 (128.107.65): 56 data bytes 64 bytes from 128.3. Pod8 = 9/25 *** No matches in current mode.221.733/0.221.Verify the CLI hierarchy independence by issuing a ping from different places in the chain . 0.65 vrf management CLI Hierarchy Independent PING 128.C.65: icmp_seq=1 ttl=254 time=0. NXOS gives the user a very IOS look and feel sensation.787/0.221.107. 4 packets received.733 ms <omitted output> --.107.65 (128.221.Verify the CLI piping functionality N7K-C1-1-pod5# conf t N7K-C1-1-pod5(config)# ping ? *** No matches in current mode.221.221.107. matching in (exec) mode *** <CR> A. Pod7 = 9/17. which we consider improvements.943 ms <omitted output> N7K-C1-1-pod5(config-if)# Note: You can use the up-arrow and get the command history from the exec mode 10 .107.D or Hostname IP address of remote system WORD Enter Hostname multicast Multicast ping N7K-C1-1-pod5(config)# ping 128.00% packet loss round-trip min/avg/max = 0.221.874 ms N7K-C1-1-pod5(config)# int e9/1 N7K-C1-1-pod5(config-if)# ping ? Pod6 = 9/9. In this step we will: .874 ms 64 bytes from 128.65: icmp_seq=0 ttl=254 time=0. when configuring the system. CLI Familiarization NX-OS CLI is very IOS-like.65: icmp_seq=0 ttl=254 time=0.128.221.65 ping statistics --4 packets transmitted.107.107.B.

N7K-C1-1-pod5# show running-config | ? cut egrep grep head last less no-more sed sort tr uniq vsh wc begin count end exclude include Print selected parts of lines. but also it shows the available keywords.221.print lines matching a pattern Display first lines Display last lines Filter for paging Turn-off pagination for command output Stream Editor Stream Sorter Translate. Note: N7K-C1-1-pod5(config-if)# ? cdp description end exit Configure CDP interface parameters Enter description of maximum 80 characters Go to exec mode Exit from command interpreter 11 .107.105/26 N7K-C1-1-pod5# conf t N7K-C1-1-pod5(config)# int mgmt 0 N7K-C1-1-pod5(config-if)# [TAB] cdp exit no description ip pop end ipv6 push shutdown vrf where The [TAB] does not only complete the command.print lines matching a pattern Improved CLI Piping Grep . characters Begin with the line that matches Count number of lines End with the line that matches Exclude lines that match Include lines that match N7K-C1-1-pod5# sh running-config | grep ? WORD count ignore-case invert-match line-exp line-number next prev word-exp Search for the expression Print a total count of matching lines only Ignore case difference when comparing strings Print only lines that contain no matches for <expr> Print only lines where the match is a whole line Print each match preceded by its line number Print <num> lines of context after every matching line Print <num> lines of context before every matching line Print only lines where the match is a complete word The following command will grab the instance of a line with “mgmt0” and print the following 3 lines after that match. Egrep . lines. N7K-C1-1-pod5# sh running-config | grep next 3 mgmt0 interface mgmt0 ip address 128. and/or delete characters Discard all but one of successive identical lines The shell than understands cli command Count words.Note: Any command can be issued from anywhere within the configuration The output piping has also been improved and itʼs now very similar to the one on Linux machines. squeeze.

In this step we will: . NX-OS.ip ipv6 no pop push shutdown vrf where Configure IP features Configure IPv6 features Negate a command or set its defaults Pop mode from stack or restore from name Push current mode to stack or save it under name Enable/disable an interface Configure VRF parameters Shows the cli context you are in If you want to know the CLI context you are in use the “where” command. Since the students are logged into a non-default VDC.Display the default roles . N7K-C1-1-pod5# show role Not visible on your Pod role: network-admin description: Predefined network admin role has access to all commands on the switch attribute: global ------------------------------------------------------------------Rule Perm Type Scope Entity ------------------------------------------------------------------1 permit read-write Not visible on your Pod role: network-operator description: Predefined network operator role has access to all read commands on the switch attribute: global ------------------------------------------------------------------- 12 .Create a new role and apply the role to a newly created user . N7K-C1-1-pod5(config-if)# where conf. The roles are groups of rules that permit or deny a set of operations on NX-OS components.Display the newly created role . provides a very flexible and powerful framework to create ad hoc roles for any type of user.Test the role NX-OS implements 4 default roles for the default VDC. only the two VDC default roles will be visible.Display the features and the feature-groups that can be used as part of the role . through the RABC feature. Role Based Access Control (RBAC) RBAC stands for “Role Based Access Control”. Upon login. every user gets assigned a “role” that defines the privileges of the user that gained access to system. interface mgmt0 admin@N7K-C1-1-pod5%default 4. For completeness the CLI output below shows all of them but on the studentsʼ Pods only the last two (in bold here) will be visible.

It can be one of the default pre-configured roles or a user-made role. Creating a role is very easy.Rule Perm Type Scope Entity ------------------------------------------------------------------1 permit read Super-user within the Pod role: vdc-admin description: Predefined vdc admin role has access to all commands within a VDC instance attribute: local ------------------------------------------------------------------Rule Perm Type Scope Entity ------------------------------------------------------------------1 permit read-write Only show commands for the vdc-operator role: vdc-operator description: Predefined vdc operator role has access to all read commands within a VDC instance attribute: local ------------------------------------------------------------------Rule Perm Type Scope Entity ------------------------------------------------------------------1 permit read N7K-C1-1-pod5# Step 4a. up to the single CLI command! Ability to deny access to interfaces 13 . Very granular access control. issue the following commands. A role is a set of rules that define what operations the user can perform on individual CLI commands. Feature and Feature-groups. You can group features in feature-groups and assign read/read-write permission to the whole group of features. All users when they login are associated to a particular role. After creating the role we will define a new user and associate the role to the newly created user. features and feature-groups basis. Feature-groups are essentially groups of related features. To see the set of features and the feature groups available to be defined as part of a role. We will create a new role that is allowed to issue all the “show” commands. such as the “L3” feature group (defined by default). Create a new role. N7K-C1-1-pod5# show role feature feature: feature: feature: feature: feature: <omitted aaa access-list arp callhome cdp output> N7K-C1-1-pod5# sh role feature-group feature group: L3 feature: router-bgp feature: router-eigrp feature: router-isis feature: router-ospf feature: router-rip N7K-C1-1-pod5# Step 4b. to check basic connectivity using “ping” and to configure just the Cisco Discovery Protocol: “cdp”.

Pod7 = 9/17. interface * 3 permit command ping * 2 permit read-write feature cdp 1 permit read Step4c. N7K-C1-1-pod5# conf t 14 . Pod8 = 9/25 role. After that. Create a new user and attach the role. N7K-C1-1-pod5(config-role)# interface ? policy Configure the interface policy for this role N7K-C1-1-pod5(config-role)# interface policy deny N7K-C1-1-pod5(config-role-interface)# permit interface ethernet 9/1 Note: Letʼs verify the role and create a user to who attach the Pod6 = 9/9. interface * Note: Note: The rules are applied in descending order. A role can also specify what resources in terms of Interfaces. VLANs and VRFs the user is entitled to access.N7K-C1-1-pod5# config t N7K-C1-1-pod5(config)# role name nxos N7K-C1-1-pod5(config-role)# ? description Add a description for the role end Go to exec mode exit Exit from command interpreter interface Configure the interface policy for this role no Negate a command or set its defaults pop Pop mode from stack or restore from name push Push current mode to stack or save it under name rule Enter the rule number vlan Configure the vlan policy for this role vrf Configure the vrf policy for this role where Shows the cli context you are in N7K-C1-1-pod5(config-role)# N7K-C1-1-pod5(config-role)# N7K-C1-1-pod5(config-role)# N7K-C1-1-pod5(config-role)# rule rule rule rule 1 2 3 4 permit permit permit permit read read-write feature cdp command ping * command conf t . please log out and login as the rbac user and test the RBAC configuration. N7K-C1-1-pod5# show role name nxos role: test description: new role vlan policy: permit (default) interface policy: deny permitted interface Ethernet2/1 vrf policy: permit (default) ------------------------------------------------------------------Rule Perm Type Scope Entity ------------------------------------------------------------------4 permit command conf t . Letʼs exercise the interface restriction. Attach the role.

107.107.897 ms ms ms ms ms --.cisco. click again on the the system icon in the “Topology” tab.65: icmp_seq=0 64 bytes from 128.107.107.com/tac <omitted output> N7K-C1-1-pod5# ? clear Reset functions configure Enter configuration mode debug Debugging functions debug Debugging function end Go to exec mode exit Exit from command interpreter ping Test network reachability show Show running system information Most of the commands are missing.65: icmp_seq=4 data bytes ttl=127 time=1.221.65 ping statistics --5 packets transmitted.128.935 ttl=127 time=0.221.008/1.221.387 ttl=127 time=0.107.107. 15 .65 vrf management PING 128. Itʼs now time to login as the “rbac” user.221.221.107.65: icmp_seq=3 64 bytes from 128.221. 5 packets received.107.65): 56 64 bytes from 128. Login: rbac Password: rbac Cisco Data Center Operating System (NX-OS) Software TAC support: http://www.221.65 (128.221.927 ttl=127 time=0.65: icmp_seq=2 64 bytes from 128.N7K-C1-1-pod5(config)#username rbac password rbac role nxos N7K-C1-1-pod5(config)#end N7K-C1-1-pod5# exit Step4d.899 ttl=127 time=0.221. Letʼs check the commands this user has been allowed to use.897/1.65: icmp_seq=1 64 bytes from 128.00% packet loss round-trip min/avg/max = 0. Note: N7K-C1-1-pod5# ping 128.107.387 ms N7K-C1-1-pod5# debug ? cdp Configure CDP debugging Note: Only the CDP debug is actually available. 0. N7K-C1-1-pod5# conf t N7K-C1-1-pod5(config)# ? cdp CDP Configuration parameters end Exit configuration mode exit Exit from command interpreter interface Configure Interfaces Note: Only the “cdp” commands are available.

N7K-C1-1-pod5(config)# cdp ? advertise enable format holdtime timer Highest CDP version supported on the switch Enable/disable CDP on all interfaces Device ID format for CDP CDP hold time advertised (in seconds) CDP refresh time interval (in seconds) Note: Letʼs try to access an interface for which we donʼt have the permission. Letʼs verify its functionality within NX-OS. Configuration Rollback NX-OS fully supports Configuration Rollback. Pod8 = 9/25 The step is completed you can now close the terminal you were just using. Please Wait ..Done N7K-C1-1-pod5# N7K-C1-1-pod5# show checkpoint summary Checkpoint Summary --------------------------------------------------------------------------1) nxos: Created by admin Created at Wed.Rollback the configuration .. effectively rolling back configuration changes.. Pod7 = 9/17.. Pod7 = 9/17. ------- Pod6 = 9/9.Verify the interface configuration N7K-C1-1-pod5# checkpoint ? <CR> WORD Checkpoint name (Max Size 75) file Create configuration rollback checkpoint to file N7K-C1-1-pod5# checkpoint nxos Note: Processing the Request.Modify the configuration for an interface . Pod8 = 9/25 N7K-C1-1-pod5(config)# interface ethernet 9/2 % Interface permission denied N7K-C1-1-pod5(config)# interface ethernet 9/1 N7K-C1-1-pod5(config-if)# no shut N7K-C1-1-pod5(config-if)# Pod6 = 9/9. 5...Create a checkpoint for the current configuration . 01:04:48 31 March 2009 Size is 7...021 bytes 16 .. This functionality allows you to revert to a previous configuration state. In this step we will: .

N7K-C1-1-pod5# conf t N7K-C1-1-pod5(config)# interface e9/1 N7K-C1-1-pod5(config-if)# ip address 1.1..1.1.1(5) interface Ethernet9/1 During the rollback process the CLI commands are undone and shown to the user Pod6 = 9/9.1/24 no ip redirects ip proxy-arp no shutdown Letʼs now rollback the configuration… N7K-C1-1-pod5# rollback running-config checkpoint nxos Processing the Request.1.1..1/24` N7K-C1-1-pod5# sh running-config int e9/1 version 4. Pod8 = 9/25 17 ..1.Letʼs now modify the configuration of an interface. Please Wait `conf t` `interface Ethernet9/1` `shutdown` `no ip proxy-arp` `ip redirects` `no ip address 1.1/24 N7K-C1-1-pod5(config-if)# no ip redirects N7K-C1-1-pod5(config-if)# ip proxy-arp N7K-C1-1-pod5(config-if)# no shutdown N7K-C1-1-pod5(config-if)# end N7K-C1-1-pod5# sh running-config int e9/1 version 4.1(5) interface Ethernet9/1 ip address 1.1. Please Wait Generating the Rollbackpatch... Please Wait Executing the patch.1/24 no ip redirects ip proxy-arp no shutdown N7K-C1-1-pod5# Finally the slash notation Letʼs check the difference between the current configuration and the checkpoint we created before.1... Please Wait !! ! interface Ethernet9/1 ip address 1.. Pod7 = 9/17. N7K-C1-1-pod5# show diff rollback-patch checkpoint nxos ? checkpoint running-config startup-config Use checkpoint as destination configuration Use running configuration as destination Use startup configuration as destination N7K-C1-1-pod5# show diff rollback-patch checkpoint nxos running-config Processing the Request.

. If a neighbor port stops receiving BPDUs. including alternate and backup ports for each hello time period. most software modules donʼt run unless the correspondent service is enabled. This implementation is also referred to as Rapid Per-VLAN Spanning Tree (Rapid-PVST).1Q trunking.> N7K-C1-1-pod5(config)# int po 10 N7K-C1-1-pod5(config-if)# switchport N7K-C1-1-pod5(config-if)# switchport mode trunk N7K-C1-1-pod5(config-if)# switchport trunk allowed vlan 1-4 4096 for N7K1 (Student 1) 8192 for N7K2 (Student 2) N7K-C1-1-pod5(config-if)# spanning-tree port type network N7K-C1-1-pod5(config-if)# description link to the other Nexus7000 N7K-C1-1-pod5(config-if)# no shutdown The “spanning-tree port type network” command enables Bridge Assurance on that link. N7K-C1-1-pod5(config)# vlan 1-4 N7K-C1-1-pod5(config)# spanning-tree vlan 1-4 priority <. Best practices dictate controlling the placement of the spanning tree root switch in the network for each VLAN to ensure that it does not inadvertently end up by the election process on a small switch in the access layer that creates a sub-optimal topology or may be more prone to failure. Once the service is enabled. so it does not need to be explicitly enabled. We will bring up few port-channels so we first need to enable the service for the LACP protocol. LACP is a conditional service N7K-C1-1-pod5(config)# feature lacp Note: NX-OS is a fully modular operating system. Cisco's implementation of RSTP in both NX-OS and IOS provides a separate spanning tree instance for each active VLAN.6. If the blocked port begins receiving BPDUs again. RapidPVST is the default spanning tree mode for NX-OS. the port is moved into the blocking state. We refer to these features that need to be specifically enabled as “conditional services”. Bridge assurance causes the switch to send BPDUs on all operational ports that carry a port type setting of “network”. it is removed from bridge assurance blocking. This bidirectional hello mechanism helps prevent looping conditions caused by unidirectional links or a malfunctioning switch Note: 9/9-10 for Pod6 N7K-C1-1-pod5(config-if)# int e9/1-2 9/17-18 for Pod7 N7K-C1-1-pod3(config-if-range)# rate-mode dedicated 9/25-26 for Pod8 N7K-C1-1-pod5(config-if-range)# switchport N7K-C1-1-pod5(config-if-range)# switchport mode trunk N7K-C1-1-pod5(config-if-range)# switchport trunk allowed vlan 1-4 N7K-C1-1-pod5(config-if-range)# no shutdown 18 .1w. Rapid Spanning Tree Protocol (RSTP) is standardized in IEEE 802. which permits greater flexibility of Layer 2 topologies in conjunction with IEEE 802. Links up with Spanning Tree It is time to bring up the interfaces and configure the Spanning Tree Protocol. and goes through normal Rapid-PVST transition. the CLI becomes visible and the feature can be used and configured.

2944 This bridge is the root Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec Bridge ID Priority Address Hello Time Role ---Desg Desg 4099 (priority 4096 sys-id-ext 3) 001b.Routed U . N7K-C1-1-pod5(config-if)# show spanning-tree vlan 3 VLAN0003 Spanning tree enabled protocol rstp Root ID Priority 4099 Address 001b.d2c2 Cost 2 Port 129 (Ethernet1/1) Hello Time 2 sec Max Age 20 sec Bridge ID Priority Address Hello Time Forward Delay 15 sec 32771 (priority 32768 sys-id-ext 3) 000d.Suspended r .4105 128.1306 Type -------------------------------Network P2p P2p Peer(STP) Interface ---------------Po10 Eth10/2 Sts --FWD FWD Cat6K-1# show spanning-tree vlan 3 VLAN0003 Spanning tree enabled protocol rstp Root ID Priority 4099 Address 0022.0081 2 sec Max Age 20 sec Forward Delay 15 sec 19 .Up in port-channel (members) I .Module-removed S .Hot-standby (LACP only) s .Switched R .Up (port-channel) --------------------------------------------------------------------------Group PortType Protocol Member Ports Channel --------------------------------------------------------------------------10 Po10(SU) Eth LACP Eth2/1(P) Eth2/2(P) Bring up the interfaces facing the Access Layer… 10/14 for Pod6 10/26 for Pod7 10/38 for Pod8 N7K-C1-1-pod5(config-if-range)# int e10/2 N7K-C1-1-pod5(config-if# switchport N7K-C1-1-pod5(config-if)# switchport mode trunk N7K-C1-1-pod5(config-if)# switchport trunk allowed vlan 1-4 N7K-C1-1-pod5(config-if)# no shutdown Check the spanning-tree from both the Nexus 7000 and the Catalyst 6500.5579.54c2.54c2.Nbr -------128.N7K-C1-1-pod5(config-if-range)# channel-group 10 mode active Check the status of the port-channel… N7K-C1-1-pod5(config-if-range)# show port-channel summary Flags: D .eca4.Individual H .Down P .2944 2 sec Max Age 20 sec Forward Delay 15 sec Cost --------1 19 Prio.

. several protocols exist. Note: N7K-C1-1-pod5(config)# int vlan 2 N7K-C1-1-pod5(config-if)# ip address 192.Nbr -------128.203.202.168. You will configure HSRP in this step.130 Type ----------------------------The link between the Cat6K P2p and the N7K-2 is blocked as P2p expected 7. Cisco NX-OS supports implementations of multiple FHRPs: Hot Standby Router Protocol (HSRP).Interface ---------------Eth2/1 Eth2/2 Role ---Root Altn Sts --FWD BLK Cost --------2 2 Prio.> 20 for N7K2 (Student 2) N7K-C1-1-pod5(config-if-hsrp)# timers 1 3 N7K-C1-1-pod5(config-if-hsrp)# ip 192.168.3 N7K-C1-1-pod5# show hsrp brief P indicates configured to preempt.168. and Virtual Router Redundancy Protocol (VRRP).2 Group addr 192..129 128.> 20 for N7K2 (Student 2) N7K-C1-1-pod5(config-if-hsrp)# timers 1 3 N7K-C1-1-pod5(config-if-hsrp)# ip 192.<Student #>/24 N7K-C1-1-pod5(config-if)# no shutdown N7K-C1-1-pod5(config-if)# N7K-C1-1-pod5(config-if)# hsrp 1 N7K-C1-1-pod5(config-if-hsrp)# preempt delay minimum 180 40 for N7K1 (Student 1) N7K-C1-1-pod5(config-if-hsrp)# priority <.168. Gateway Load Balancing Protocol (GLBP).168. | Interface Grp Prio P State Active addr Standby addr Vlan2 1 40 P Active local 192.3 20 .203.2 Vlan3 1 40 P Active local 192.3 N7K-C1-1-pod5(config-if-hsrp)# int vlan 3 N7K-C1-1-pod5(config-if)# ip address 192.203.202.<Student #>/24 N7K-C1-1-pod5(config-if)# no shutdown N7K-C1-1-pod5(config-if)# N7K-C1-1-pod5(config-if)# hsrp 1 N7K-C1-1-pod5(config-if-hsrp)# preempt delay minimum 180 40 for N7K1 (Student 1) N7K-C1-1-pod5(config-if-hsrp)# priority <.168.3 192. which are commonly referred to together as First Hop Redundancy Protocols (FHRPs)..202.202. Their code does not run unless the feature is explicitly enabled with the “feature” command. HSRP To provide redundancy for the IP default gateway services. Letʼs create an SVI for VLAN 2 and VLAN 3 and configure HSRP: N7K-C1-1-pod5(config)# feature interface-vlan N7K-C1-1-pod5(config)# feature hsrp Both the SVI service and the service for the HSRP protocol are “conditional”.168.168..203.

Moving the Topology from STP-based to vPC-based The “virtual Port Channel” (vPC) functionality provides the following benefits: • • • • • • • Allows a single device to use a port channel across two upstream devices Eliminates Spanning Tree Protocol (STP) blocked ports Provides a loop-free topology Uses all available uplink bandwidth Provides fast convergence if either the link or a device fails Provides link-level resiliency Assures high availability The topology will change as follow: The terminology used for vPCs is as follows: • • • • • vPC — The combined port channel between the vPC peer devices and the downstream device. vPC member port — Interfaces that belong to the vPCs. The fault-tolerant link sends configurable.8. • 21 . vPC domain — This domain is formed by the two vPC peer link devices. It is also a configuration mode for configuring some of the vPC peer link parameters. periodic keepalive messages between devices connected by the vPC peer link on an out-of-band link. vPC peer keep-alive link — The peer keep-alive link is a Layer3 link between the vPC peer devices used to ensure that both devices are up. vPC peer link — The link used to synchronize states between the vPC peer devices. vPC peer device — One of a pair of devices that are connected with the special port channel known as the vPC peer link. Both ends must be on 10-Gigabit Ethernet interfaces.

221. N7K-C1-1-pod5(config-vpc-domain)# show vpc peer-keepalive vPC keep-alive status --Send status --Last send at --Sent on interface --Receive status --Last receive at --Received on interface --Last update from peer vPC Keep-alive parameters --Destination --Keepalive interval --Keepalive timeout --Keepalive hold timeout --Keepalive vrf : : : : : : : : peer is alive Success 2009. This is the recommended configuration 1000 for Student 1 2000 for Student 2 N7K-C1-1-pod5(config)# vpc domain 1 N7K-C1-1-pod5(config-vpc-domain)# role priority <..04.19 20:49:43 767 ms mgmt0 (0) seconds. preferably 1GigE.> source 128.During this step you will: . First thing to setup is the fault-tolerant link connection..221. This domain ID is used to differentiate multiple vPC tiers.Create the vPC domain . and place them in vPC mode N7K-C1-1-pod5# conf t N7K-C1-1-pod5(config)# feature vpc Next weʼll enable the vPC domain..<.116 1000 msec 5 seconds 3 seconds management 22 . This port should belong to a separate VRF. Another alternative is to use the Out-of-Band management network through the Supervisorʼs management interface and this is what weʼll do in this lab.> Enter your mgmt0 IP address Enter your partner’s mgmt0 IP address Letʼs check the status of the fault-tolerant link (peer-keepalive). allowing for an L2 unique Link Aggregation ID for LACP based configuration.107. We will also configure the “role” so that the primary vPC device is the same device which is also the STP root and the HSRP primary device.> The lower priority wins. between the vPC peer devices (it does NOT need to be a direct link). (568) msec : : : : : 128.107..Configure the access layer facing port channels. N7K-C1-1-pod5(config-vpc-domain)# peer-keepalive dest 128.04.107.<.. For the faulttolerant link we recommend a separate port. and place it in vpc peer-link mode ..Enable the vPC .Configure the peer-link port channel.19 20:49:43 584 ms mgmt0 Success 2009.221.

129 128. N7K-C1-1-pod5(config-int)# int port-channel 10 N7K-C1-1-pod5(config-int)# vpc peer-link N7K-C1-1-pod5(config-int)# show vpc brief Legend: (*) .b1c2 Cost 2 Port 129 (Ethernet1/1) Hello Time 2 sec Max Age 20 sec Bridge ID Priority Address Hello Time Role ---Root Altn Forward Delay 15 sec 32771 (priority 32768 sys-id-ext 3) 000d.130 Type ---------------------------P2p P2p Interface ---------------Eth2/1 Eth2/2 Sts --FWD BLK Now that the peer-link is running and the vPC is up.-------------------------------------------------1 Po10 up 1-4 The STP status hasnʼt changed on the Catalyst 6500. and then we can validate that the base vPC infrastructure is running (assuming your Partner has done the same configuration steps on the other Nexus7000 in your Pod).54c2. N7K-C1-1-pod5(config)# int N7K-C1-1-pod5(config-int)# N7K-C1-1-pod5(config-int)# N7K-C1-1-pod5(config-int)# N7K-C1-1-pod5(config-int)# N7K-C1-1-pod5(config-int)# po 20 switchport switchport mode trunk switchport trunk allowed vlan 1-4 no sh vpc 20 23 . we can configure the peer-link. forwarding via vPC peer-link vPC domain id : 1 Peer status : peer adjacency formed ok vPC keep-alive status : peer is alive Configuration consistency status: success vPC role : primary vPC Peer-link status --------------------------------------------------------------------id Port Status Active vlans ---------.--Keepalive udp port --Keepalive tos : 3200 : 192 Now that the base vPC domain is configured.Nbr -------128. we can add in the access facing “vPC” links.0481 2 sec Max Age 20 sec Forward Delay 15 sec Cost --------2 2 Prio. Cat6K-1# show spanning-tree vlan 3 VLAN0003 Spanning tree enabled protocol rstp Root ID Priority 4099 Address 001b.eca4.local vPC is down.

Suspended r .Individual H .Routed U .2 24 . Cat6K-1(config-if)# int range f2/1 . forwarding via vPC peer-link vPC domain id : 1 Peer status : peer adjacency formed ok vPC keep-alive status : peer is alive Configuration consistency status: success vPC role : primary vPC Peer-link status --------------------------------------------------------------------id Port Status Active vlans ---------.-----------20 Po20 down* success success - The vPC status is “down” because we havenʼt configured the port-channel on the Catalyst 6500 yet. 10/14 for Pod6 10/26 for Pod7 10/38 for Pod8 N7K-C1-1-pod5(config-int)# int e10/2 N7K-C1-1-pod5(config-int)# channel-group 20 mode active Letʼs check the vPC status.Letʼs now add the port facing the Access Layer (Catalyst 6500) to the port-channel. N7K-C1-1-pod5(config-if)# show vpc brief Legend: (*) .Up in port-channel (members) I .Module-removed S .Switched R .Hot-standby (LACP only) s .-------------------------------------------------1 Po10 up 1-4 vPC status ---------------------------------------------------------------------id Port Status Consistency Reason Active vlans ---------. one of you can go on the Catalyst 6500 and configure the port-channel.Up (port-channel) ------------------------------------------------------------------------Group PortType Protocol Member Ports Channel -------------------------------------------------------------------------10 Po10(SU) Eth LACP Eth9/1(P) Eth9/2(D) 20 Po20(SD) Eth LACP Eth10/2(I) If your teammate has reached this point as well. N7K-C1-1-pod5(config-if)# sh port-channel summary Flags: D .----------.Down P . in fact the port is in “individual” state from a LACP prospective.local vPC is down.-------------------------.

-------------------------------------------------1 Po10 up 1-4 vPC status ---------------------------------------------------------------------id Port Status Consistency Reason Active vlans ---------.--. Cat6K-1(config-if-range)# show spanning-tree vlan 3 VLAN0003 Spanning tree enabled protocol rstp Root ID Priority 4099 Address 001b.--------.Nbr Type ---------------. Letʼs check the status of the vPC and the STP on the Nexus7000.local vPC is down.Individual S .Module-removed -------------------------------------------------------------------------Group PortType Protocol Member Ports Channel -------------------------------------------------------------------------20 Po20(U) Eth LACP Eth6/1(U) Eth6/2(U) The Catalyst 6500 has now a port-channel connected to two different upstream devices.up in port-channel I .-------.eca4.down U .0481 2 sec Max Age 20 sec Forward Delay 15 sec Interface Role Sts Cost Prio. forwarding via vPC peer-link vPC domain id : 1 Peer status : peer adjacency formed ok vPC keep-alive status : peer is alive Configuration consistency status: success vPC role : primary vPC Peer-link status --------------------------------------------------------------------id Port Status Active vlans ---------.---.4115 P2p Cat6K-1(config-if-range)# show port-channel summary Flags: D .Hot-standby (LACP only) R .---------------------------Po20 Root FWD 1 128.b1c2 Cost 1 Port 4115 (port-channel20) Hello Time 2 sec Max Age 20 sec Bridge ID Priority Address Hello Time Forward Delay 15 sec 32771 (priority 32768 sys-id-ext 3) 000d.-------------------------.-----------20 Po20 up success success 1-4 25 .----------.54c2.suspended H . N7K-C1-1-pod5(config-if)# sh vpc brief Legend: (*) .Cat6K-1(config-if-range)# channel-group 20 mode active Letʼs check the STP and the port-channel status.

In the unlikely case that both ports and line cards in the peer-link fail (being that two ports on two different line cards are the recommended minimum for the peer-link) the vPC software will look to the fault-tolerant link (the keep-alive link) to determine if the failure is a link level failure (perhaps a UDLD failure of some nature).b1c2 This bridge is the root Hello Time 2 sec Max Age 20 sec Bridge ID Priority Address Hello Time Role ---Desg Desg Desg Forward Delay 15 sec 4099 (priority 4096 sys-id-ext 3) 001b. or if in fact the remote peer has failed entirely.54c2.4105 128. We will bring down the peer-link interfaces on the vPC primary device and observe what happens on the vPC secondary and on the Access device.54c2. N7K-C1-1-pod5# conf t N7K-C1-1-pod5(config)# int e9/1-2 N7K-C1-1-pod5(config-if-range)# shutdown 9/9-10 for Pod6 9/17-18 for Pod7 9/25-26 for Pod8 26 . to avoid loops the vPC secondary switch will disable its vPC member ports and any Layer 3 interfaces attached to a vPC associated VLAN. With port-channel failover. vPC Failure Scenario One of the advantages of the vPC approach to loop management is that failure recovery on a link or of an entire switch relies on port-channel failover rather than on STP re-learning the entire network.b1c2 2 sec Max Age 20 sec Forward Delay 15 sec Cost --------1 1 2 Prio. In the case that the remote peer is still alive (peer-keepalive messages are still being received).Nbr -------128. In this step we will bring down the vPC peer-link. recovery is often sub-second. This alone is a key reason why vPC provides an efficient scaling mechanism relative to STP managed Layer 2 topologies.N7K-C1-1-pod5(config-if)# show spanning-tree vlan 3 VLAN0003 Spanning tree enabled protocol rstp Root ID Priority 4099 Address 001b.4115 128.266 Type ---------------------------(vPC peer-link) Network P2p (vPC) P2p P2p Interface ---------------Po10 Po20 Eth2/10 Sts --FWD FWD FWD The vPC topology is now up and running! 9.

suspended Hot-standby (LACP only) Module-removed -------------------------------------------------------------------------Group PortType Protocol Member Ports Channel -------------------------------------------------------------------------20 Po20(U) Eth LACP Eth6/1(U) Eth6/2(D) 30 Po30(D) Eth NONE -- While on the vPC secondary you should see the following: %VPC-2-VPC_SUSP_ALL_VPC: Peer-link going down.af42 Internet Address is 192.Up (port-channel) ------------------------------------------------------------------------Group PortType Protocol Member Ports Channel ------------------------------------------------------------------------10 Po10(SD) Eth LACP Eth9/1(D) Eth9/2(D) 20 Po20(SD) Eth LACP Eth10/2(D) We can now bring the peer-link interfaces on the vPC primary back up and check again the Catalyst 6500. address is 001b. the link back up: Cat6K-1(config-if-range)# show port-channel summary Flags: D .2/24 MTU 1500 bytes.202.On the Catalyst 6500 we can see how the port-channel port got suspended.down U .Down P .Module-removed S .Individual H . BW 1000000 Kbit.up in port-channel Individual S . DLY 10 usec.168.Switched R .Module-removed ------------------------------------------------------------------------Group PortType Protocol Member Ports 27 .Hot-standby (LACP only) s .suspended H . N7K-C1-1-pod5(config)# int e9/1-2 N7K-C1-1-pod5(config-if-range)# no shutdown 9/9-10 for Pod6 9/17-18 for Pod7 9/25-26 for Pod8 After few seconds you should see.Individual S .54c2.Routed U .up in port-channel I . line protocol is down Hardware is EtherSVI. suspending all vPCs on secondary N7K-C1-2-pod5(config-if)# show int vlan 2 Vlan2 is down.Suspended r . Cat6K-1(config-if-range)# show port-channel summary Flags: D I H R down U .Hot-standby (LACP only) R .Up in port-channel (members) I . <omitted output> N7K-C1-2-pod5(config-if)# show port-channel summary Flags: D .

1. These are the steps for this exercise: .<Student #>/32 N7K-C1-1-pod5(config-if)# feature ospf N7K-C1-1-pod5(config)# router ospf 1 N7K-C1-1-pod5(config-router)# log-adjacency-changes N7K-C1-1-pod5(config-router)# auto-cost reference-bandwidth 1000000 As you may have noticed the “network x. In this step we will configure OSPFv2 and we will see how the configuration is interface centric vs.x. This is a big different from IOS. as we will see with the next few commands.Instantiate an OSPF process .2 Cat6K-1(config-if-range)# no channel-group 20 mode active 10. so that it can be used in the next session: Cat6K-1(config)# int range f2/1 . Since we donʼt have a Core device in the topology we will modify the currents links and configure them from Layer2 to Layer3 together with removing some of the features we have configured in the previous steps.x. OSPF.Configure the Loopback interfaces .Turn the OSPFv2 service on . This step will consist of a very simple configuration of OSPF between the Nexus 7000 and the Catalyst 6500 just to give the students a first experience with the protocol and to set the stage for the “Stateful Process Restart” step which will follow this one. Note: 28 .Verify OSPF configuration by issuing few show command N7K-C1-1-pod5(config)# interface loopback0 N7K-C1-1-pod5(config-if)# ip address 10. as well as other IGP protocols. OSPF Configuration OSPF is fully implemented in NX-OS as part of the “Enterprise” License (however you can use the feature leveraging the grace-period mode for 120 days).x area y” configuration lines are not present.Channel ------------------------------------------------------------------------20 Po20(U) Eth LACP Eth6/1(U) Eth6/2(U) Also on the vPC secondary the SVIs are back up: N7K-C1-2-pod5(config-if)# show int vlan 2 Vlan2 is up. the network centric IOS based OSPF configuration.255. are interface centric. line protocol is up <omitted output> Before continuing letʼs remove the port-channel on the Catalyst 6500.

1. N7K-C1-1-pod5(config)# int e10/1 N7K-C1-1-pod5(config-if)# description OSPF link to the N7K N7K-C1-1-pod5(config-if)# ip address 192.1(5) feature ospf router ospf 1 log-adjacency-changes auto-cost reference-bandwidth 1000000 interface Ethernet10/1 ip ospf dead-interval 6 ip ospf hello-interval 2 ip ospf network point-to-point ip router ospf 1 area 0.168.Letʼs now configure the interfaces. N7K-C1-1-pod5# sh running-config ospf all version 4. The membership to an OSPF area is specified at the interface configuration level.0 Letʼs check now the complete OSPF configuration with its default values. Note: Now we can check the OSPF configuration we have been working on. This approach is more intuitive and manageable.0.0.1(5) feature ospf 29 .<Student #>/30 N7K-C1-1-pod5(config-if)# ip ospf hello-interval 2 N7K-C1-1-pod5(config-if)# ip ospf dead-interval 6 N7K-C1-1-pod5(config-if)# ip ospf network point-to-point N7K-C1-1-pod5(config-if)# ip router ospf 1 area 0 N7K-C1-1-pod5(config-if)# no shutdown N7K-C1-1-pod5(config-if)# 10/13 for Pod6 10/25 for Pod7 10/37 for Pod8 In the NX-OS the OSPF configuration is interface centric. N7K-C1-1-pod5(config-if)# sh running-config ? <CR> > aaa all am arp bgp <snip> l3vm license msdp netflow ospf ospfv3 pim pim6 <snip> Redirect it to a file Display aaa configuration Current operating configuration with defaults Display am information Display arp information Display bgp information Display l3vm information Display licensing configuration Display msdp information Show NetFlow configuration Display ospf information Display ospfv3 information Display pim information Display pim6 information N7K-C1-1-pod5(config-if)# sh running-config ospf version 4.

1.Verify that the OSPF process has been restarted with a new process ID 30 .168. NX-OS continuously checks the health of each software module making sure that if a process crashes or hangs the right action is taken to allow service continuity and availability. These are the steps for this exercise: . CDP. Stateful Process Restart NX-OS is a modern operating system.0. With this exercise we will see how the system recovers from an OSPF crash in a seamless way.Display the OSPF process ID .1.0 N7K-C1-1-pod5# sh ip ospf neighbors OSPF Process ID 1 VRF default Total number of neighbors: 1 Neighbor ID Pri State 10. All Layer2 protocols (STP. You will see how the connected Cat6K wonʼt even realize that the process crashed and restarted. NX-OS has been designed around the concept of zero service destruction.Kill the OSPF process .2 1 FULL/ N7K-C1-1-pod5# Up Time Address 00:08:58 192.2 Interface Eth10/1 11. LACP etc) and OSPF support the State-full Process Restart leveraging our PSS (Persistent Storage Service) architecture.snmp-server enable traps ospf rate-limit 10 7 snmp-server enable traps ospf 1 rate-limit 10 7 router ospf 1 graceful-restart graceful-restart grace-period 60 timers lsa-arrival 1000 distance 110 maximum-paths 8 auto-cost reference-bandwidth 1000000 ip ospf event-history size small ip ospf event-history cli size small ip ospf event-history redistribution size small ip ospf event-history spf size small ip ospf event-history lsa size small ip ospf event-history flooding size small ip ospf event-history ha size small ip ospf event-history event size small ip ospf event-history adjacency size small interface Ethernet10/2 ip ospf dead-interval 6 ip ospf hello-interval 2 ip ospf network point-to-point ip ospf priority 1 ip ospf retransmit-interval 5 ip ospf transmit-delay 1 ip router ospf 1 area 0.255.0.

. Just to show that the OSPF adjacency goes down as expected. plugin image has been deleted. N7K-C1-1-pod5# show process | inc ospf 1959 S NR NR NR NR 778f727b 1 0 0 0 0 ospf ospfv3 ospf ospfv3 ospf Notice the PID on the left (you will need it in the killing process) and the number of restarts (bold and blu). Both students can look at the same telnet session. ############################################################### Successfully loaded service restart debug-plugin!!! Commands Available: help kill <pid> exit Enter Commands: kill <ospf pid> killing … 2008 May 12 21:22:35 N7K-C1-1-pod5 %SYSMGR-2-SERVICE_CRASHED: Service "__inst_001__ospf" (PID 19700) hasn't caught signal 9 (no core).Check the Cat6K screen N7K-C1-1-pod5(config)# logging level ospf 7 N7K-C1-1-pod5(config)# logging monitor 7 N7K-C1-1-pod5(config)# terminal monitor This step should be performed only on one of the Nexus 7000.res p N7K-C1-1-pod5# load p load_isanimg: entry load_isanimg: uri_info:0x809ba90 load_isanimg: type:0x8 Loading plugin version 4. Now letʼs kill OSPF. 31 . N7K-C1-1-pod5(config-if)# no shutdown The interface is now up and the OSPF adjacency is back up. N7K-C1-1-pod5# N7K-C1-1-pod5# copy bootflash:proc.1(5) ############################################################### Warning: debug-plugin is for engineering internal use only! For security reason. when shutting down the link on the N7K N7K-C1-1-pod5(config)# int e10/1 N7K-C1-1-pod5(config-if)# shutdown 10/13 for Pod6 10/25 for Pod7 10/37 for Pod8 As you can see on the the link and the OSPF adjacency went down. Now bring the interface back up on the Nexus 7000.

As today NX-OS supports “Configuration Session” only for configuration related to Security ACLs and QoS. 12. looking at the other Nexus 7000 terminal. however the goal in the future is to support every feature within this programming mode. This new mode allows to “dry-run” the configuration against the system resources availability.Create a simple access-list and apply the access list to an interface . the neighbor didnʼt even realized that our OSPF process was killed and restarted.“Commit”” the configuration N7K-C1-1-pod5# configure session ? WORD Enter the name of the session Up to 32 active sessions within each VDC N7K-C1-1-pod5# configure session nxos Config Session started.Create a new configuration session . Configuration Session NX-OS offers a new way of configuring Security ACLs: the “Configuration Session” mode. These are the steps for this exercise: . For “dryrun” we mean a process that allows the user to check whether the hardware resources are available without actually perform on them any modification.“Verify” the configuration . Session ID is 1 N7K-C1-1-pod5(config-s)# ? Note: Note the “s” that indicates that the user is in configuration session. Abort the current configuration session Configure access control list parameters ARP access-list configuration commands Commit the current configuration session Exit configuration mode Error disable abort access-list arp commit end errdisable 32 . In this exercise the students will get familiar with the new configuration session process by configuring an ACL for a particular interface.exit N7K-C1-1-pod5# sh process | inc ospf 16066 S 778f727b 2 NR 0 NR 0 NR 0 NR 0 NR 0 NR 0 NR 0 - ospf ospfv3 ospf ospfv3 ospf ospfv3 ospf ospfv3 Notice how the OSPF process has now a new process ID and how.

NX-OS will treat them seamlessly just as a name N7K-C1-1-pod5(config-s)# ip access-list N7K-C1-1-pod5(config-s-acl)# permit tcp N7K-C1-1-pod5(config-s-acl)# permit tcp N7K-C1-1-pod5(config-s-acl)# permit tcp N7K-C1-1-pod5(config-s-acl)# exit nxos 111. Letʼs see our configuration within the config session.0/24 any Letʼs now attach the access-group to an interface.0/24 any 113.1. The slash notation for IP addresses. N7K-C1-1-pod5(config-s-if)# show configuration session config session nxos 0001 0002 0003 0004 0005 0006 ip access-list 1 permit tcp 111.3.1.1.3.2. You can have use either a number or string of characters or a mix of them when naming an ACL. N7K-C1-1-pod5(config-s)# int e10/2 N7K-C1-1-pod5(config-s-if)# ip access-group nxos in The access-list hasnʼt been programmed into the hardware yet.1.0/24 any permit tcp 113.2.exit interface ip logging mac object-group resequence save time-range verify vlan Exit from command interpreter Configure interfaces Configure IP features Modify message logging facilities MAC configuration commands Configure ACL object groups Resequence a list with sequence numbers Save the current configuration session to uri Define time range entries Verify the current configuration session Vlan commands N7K-C1-1-pod5(config-s)# ip access-list nxos ? <CR> Note: Note: Note: No “standard/extended/named/numbered” ACL… just ACL NX-OS introduces some ACL syntax improvements for better usability and manageability.3.2.0/24 any interface Ethernet10/2 ip access-group nxos in 33 .2.0/24 any permit tcp 112.0/24 any 112.3.

support for TCP flags. During the verification process the system checks the configuration against the hardware and software resources for their availability. N7K-C1-1-pod5# conf t N7K-C1-1-pod5(config)# interface e10/2 N7K-C1-1-pod5(config-if)# no ip access-group nxos in N7K-C1-1-pod5(config-if)# 13.1(5) interface Ethernet10/2 ip access-group nxos in The ACL shows up in the running config only after the “commit” has been performed. NetFlow Nexus7000 offers a very powerful implementation of NetFlow. letʼs remove the the ACL from the interface. etc. 34 . N7K-C1-1-pod5(config-s-if)# commit Commit Successful N7K-C1-1-pod5# show running-config int e10/2 version 4. Some of the most important aspects on Nexus7000 NetFlow are scalability. N7K-C1-1-pod5(config-s-if)# show running-config int e10/2 version 4. We are now ready to commit the configuration.1(5) interface Ethernet10/2 The configuration can fit in the hardware table.Number of active configuration sessions = 1 Letʼs now verify our configuration. support for NetFlow v9. effective hardware based sampling. If the commit process will succeed the session will be considered completed and will be terminated. Again. N7K-C1-1-pod5# show configuration session There are no active configuration sessions N7K-C1-1-pod5# Before continuing. till this point the ACL TCAM has not been touched yet. N7K-C1-1-pod5(config-s-if)# verify Verification Successful The ACL TCAM hasn’t been modified yet… but we now know that the hardware resources are enough to accommodate the new/modified ACL.

Letʼs start by configuring a “flow record”.In terms of NetFlow configuration.Attach the monitor to the interface . while the “collect” keyword defines the information that will be exported together with the flow. The “match” keyword defines on which fields the flow creation is based.Verify the NetFlow configuration N7K-C1-1-pod5# conf t N7K-C1-1-pod5(config)# feature netflow Note: Also NetFlow is a conditional service which must be enabled in order to configure the feature.Configure a flow export . A “flow record” translates in a hardware NetFlow profile and mask. NetFlow is a conditional service and it needs to be enabled for its CLI to be active and the feature to be configurable. N7K-C1-1-pod5(config)# flow record nxos-rec N7K-C1-1-pod5(config-flow-record)# ? collect description end exit match no pop push where Specify a non-key field Provide a description for this Flow Record Go to exec mode Exit from command interpreter Specify a key field Negate a command or set its defaults Pop mode from stack or restore from name Push current mode to stack or save it under name Shows the cli context you are in N7K-C1-1-pod5(config-flow-record)# match ? ip ipv4 ipv6 transport IP attributes IPv4 attributes IPv6 attributes Transport layer fields N7K-C1-1-pod5(config-flow-record)# match ipv4 destination address N7K-C1-1-pod5(config-flow-record)# match ipv4 source address N7K-C1-1-pod5(config-flow-record)# match ip protocol N7K-C1-1-pod5(config-flow-record)# collect ? counter Counters to collect flow Flow identifying fields routing Routing attributes timestamp Timestamp fields 35 .Configure a flow monitor . A “flow record” defines what information NetFlow will track. These are the steps for this exercise: . NX-OS follows the Cisco IOS Flexible NetFlow conventions.Configure a flow record . similar to the Cat6K concept of “flow mask”.

transport Transport layer fields N7K-C1-1-pod5(config-flow-record)# collect transport tcp flags The TCP flags can now be exported together with the other flow information.3. we can now put these two pieces together into an object called “flow monitor” and attach the “flow monitor” to an interface.3. They are very useful in the auditing and forensic. 36 . On NX-OS you can enable NetFlow on per interface basis.3 ? <CR> use-vrf Optional VRF label Note: The user can also set the VRF to be used when exporting the NetFlow statistics. the type of transport (ie: UDP only for now).3. The NetFlow exporter includes the destination address of the reporting server. N7K-C1-1-pod5(config-flow-exporter)# N7K-C1-1-pod5(config-flow-exporter)# N7K-C1-1-pod5(config-flow-exporter)# N7K-C1-1-pod5(config-flow-exporter)# destination 3.3. letʼs now configure the “flow exporter” that defines where and how to export this information. This will enable NetFlow on the interface. and the export format (ie: version 9).3 source loopback0 transport udp 9999 version 9 After configuring the “flow record” and the “flow exporter”. Note: N7K-C1-1-pod5(config-flow-record)# collect counter packets After we have configured the “flow record” that defines what information NetFlow will track and export. as well as when analyzing the client-server comunications. N7K-C1-1-pod5(config-flow-record)# flow exporter nxos-exp N7K-C1-1-pod5(config-flow-exporter)# ? description destination dscp end exit no pop push source transport version where Provide a description for this Flow Exporter Specify the destination address Optional DSCP Go to exec mode Exit from command interpreter Negate a command or set its defaults Pop mode from stack or restore from name Push current mode to stack or save it under name Source Interface for this destination Transport Destination Port Specify the export version Shows the cli context you are in N7K-C1-1-pod5(config-flow-exporter)# description to the NetFlow collector X N7K-C1-1-pod5(config-flow-exporter)# destination 3.

0(3) feature netflow flow exporter nxos-exp description to the NetFlow collector X destination 3. L4 Info .1.2): 56 data 64 bytes from 10.168.2 (10.967/45.2: icmp_seq=3 64 bytes from 10. (V)lan.1.1. (S)vi.883 ms N7K-C1-1-pod5# show hardware flow ip module 9 D . (T)unnel TCP Flags: Ack.202.1. Syn.<. 5 packets received.20. 0.062 ms time=220.1.00% packet loss round-trip min/avg/max = 0..Protocol:Source Port:Destination Port IF . Urgent 37 .366 ms time=1.> PING 10.1..10.20.3.3 transport udp 12002 source loopback0 version 9 flow record nxos-rec match ipv4 source address match ipv4 destination address match ip protocol collect counter packets collect transport tcp flags flow monitor nxos-mon record nxos-rec exporter nxos-exp interface Vlan 2 ip flow monitor nxos-mon input ip flow monitor nxos-mon output N7K-C1-1-pod5# N7K-C1-1-pod5# ping 192.1.045 ms time=0.2 ping statistics --5 packets transmitted. Push.1. Flush.2: icmp_seq=1 64 bytes from 10.2: icmp_seq=0 64 bytes from 10.2: icmp_seq=2 64 bytes from 10.967 ms .N7K-C1-1-pod5(config)# flow monitor nxos-mon N7K-C1-1-pod5(config-flow-monitor)# record nxos-rec N7K-C1-1-pod5(config-flow-monitor)# exporter nxos-exp N7K-C1-1-pod5(config-flow-monitor)# int vlan2 N7K-C1-1-pod5(config-if)# ip flow monitor nxos-mon ? input Apply Flow Monitor on input traffic output Apply Flow Monitor on output traffic N7K-C1-1-pod5(config-if)# ip flow monitor nxos-mon input N7K-C1-1-pod5(config-if)# ip flow monitor nxos-mon output N7K-C1-1-pod5(config-if)# end N7K-C1-1-pod5# sh running-config netflow version 4. (P)ortchannel.Interface: ()ethernet.55.1 for Student2 --.883 ms time=2.20.20.264/220.2 for Student1 .2: icmp_seq=4 bytes ttl=254 ttl=254 ttl=254 ttl=254 ttl=254 time=1.20.3.20. Reset.Direction.20.

.168. The following steps cannot be performed in the current lab. I S2 192.202.202.000. 38 .168. .002 224. . .D IF SrcAddr DstAddr L4 Info PktCnt TCP Flags -+-----+---------------+---------------+---------------+----------+----------I S2 192.168.202. .000. .001 001:00000:00000 0000000005 . .002 192. . . N7K-C1-1-pod3(config-if)# Congratulations!!! The lab is now complete! The next two steps belong to the old lab and they have been kept here just for reference. .002 017:00000:00000 0000000534 .

2009 Jan 8 07:44:17 N7K-1 %VDC_MGR-2-VDC_LIC_WARN: Service using grace period will be shutdown in 30 day(s) 2009 Jan 8 07:44:34 N7K-9 %VDC_MGR-2-VDC_ONLINE: vdc 2 has come online 39 . Each configured VDC presents itself as a unique device to connected users within the framework of that physical switch.Create a new VDC and allocate resources to it. .“switchto” the newly created VDC and perform the initial configuration script You need to be in the “default-VDC” N7K-1# show vdc vdc_id -----1 2 3 vdc_name -------N7K-1 pod5-S1 pod2-S1 state ----active active active mac ---------00:22:55:79:c4:41 00:22:55:79:c4:42 00:22:55:79:c4:43 You will now delete the Pod (that is VDC) you were working on. “2” for Student2 where “y” is your Pod number and ”x” is Deleting this vdc will remove its config.. These are the steps for this exercise: . N7K-1# conf t N7K-1(config)# no vdc pod< y >-S< x > “1” for Student1. and being managed by a separate administrator. having its own configuration.Delete the VDC you were working on. .Virtual Device Contexts NX-OS introduces support for the Virtual Device Contexts (VDCs). This lab has used the VDC concept to allow multiple PODs to work on a single switch. The VDC runs as a separate logical entity within the switch. which allow the Nexus7000 to be virtualized at the device level. one moment please . Continue deleting this vdc? Note: Deleting VDC.. [no] yes N7K-1(config)# 2009 Jan 8 07:43:34 N7K-1 %VDC_MGR-2-VDC_OFFLINE: vdc 2 is now offline Now create a new VDC and allocate the following interfaces N7K-1(config)# vdc pod< y >-S< x > “1” for Student1. maintaining its own unique set of running software processes. one moment please ... “2” for Student2 Note: where “y” is your Pod number and ”x” is Creating VDC.

The default VDC always has a high-availability option of reset assigned to it. This configured action will occur regardless of whether there are dual supervisors or a single supervisor present in the chassis. This value can be changed under configuration control. There are three actions that can be configured: restart.N7K-1(config-vdc)# ? allocate Assign interfaces to vdc Go to exec mode Exit from command interpreter Change HA policy for this VDC Resource configuration Negate a command or set its defaults Pop mode from stack or restore from name Push current mode to stack or save it under name Change the template for this vdc Shows the cli context you are in end exit ha-policy limit-resource no pop push template where N7K-1(config-vdc)# allocate interface ethernet <check the table above> Moving ports will cause all config associated to them in source vdc to be removed. The bringdown option will simply delete the VDC. bringdown. and reset. the administrator has a set of options that can be configured on a per-VDC basis defining what action will be taken regarding that VDC. Subsequent VDCs created will have a default value of bringdown assigned to them. If dual supervisors are present. The restart option will delete the VDC and then re-create it with the running configuration. N7K-1(config-vdc)# N7K-1(config-vdc)# m4route-mem m6route-mem monitor-session port-channel u4route-mem u6route-mem vlan vrf ha-policy single-sup restart dual-sup restart limit-resource ? Set ipv4 route memory limits Set ipv6 route memory limits Monitor local session Set port-channel limits Set ipv4 route memory limits Set ipv6 route memory limits Set VLAN limits Set vrf resource limits N7K-1(config-vdc)# limit-resource vrf minimum 16 maximum 20 N7K-1(config-vdc)# show vdc pod< y >-S< x > vdc id: 2 vdc name: pod5-S1 vdc state: active vdc mac address: 00:1b:54:c2:29:42 vdc ha policy: RESTART vdc dual-sup ha policy: RESTART vdc create time: Thu Aug 7 10:15:46 2008 vdc restart count: 0 detail 40 . The reset option will issue a reset for the active supervisor when there is only a single supervisor in the chassis. the reset option will force a supervisor switchover. Are you sure you want to move the ports? [yes] yes Should a control plane failure occur.

.0 Configure the default gateway? (yes/no) [y]: IPv4 address of the default gateway : 192. Use ctrl-c at anytime to skip the remaining dialogs.255.N7K-1(config-vdc)# show vdc pod< y >-S< x > membership vdc_id: 2 vdc_name: student1 Ethernet1/1 Ethernet1/5 Ethernet1/7 Ethernet1/10 Ethernet1/13 Ethernet1/16 N7K-1(config-vdc)# exit interfaces: Ethernet1/2 Ethernet1/5 Ethernet1/8 Ethernet1/11 Ethernet1/14 Ethernet1/3 Ethernet1/6 Ethernet1/9 Ethernet1/12 Ethernet1/15 Itʼs now time to “switchto” the newly created VDC.1 20 for Odd Pods – Student1 22 for Odd Pods – Student2 21 for Even Pods – Student1 23 for Even Pods – Student2 41 . Failure to register may affect response times for initial service calls.100. You will go through the initial script configuration. N7K-1# switchto vdc pod< y >-S< x > ---.168.System Admin Account Setup ---Do you want to enforce secure password standard (yes/no): no Enter the password for "admin": Test Confirm the password for "admin": Test ---.. Setup configures only enough connectivity for management of the system. which is similar to the one you would go through on a first time-booted Nexus7000.255.<. Please register Cisco Nexus7000 Family devices promptly with your supplier.> Mgmt0 IPv4 netmask : 255.168.100. Would you like to enter the basic configuration dialog (yes/no): yes Create another login account (yes/no) [n]: Configure read-only SNMP community string (yes/no) [n]: Configure read-write SNMP community string (yes/no) [n]: Enter the switch name : pod< y >-S< x > Continue with Out-of-band (mgmt0) management configuration? (yes/no) [y]: Mgmt0 IPv4 address : 192. DC3 devices must be registered to receive entitled support services. Press Enter at anytime to skip a dialog.Basic System Configuration Dialog VDC: 2 ---This setup utility will guide you through the basic configuration of the system.

65: icmp_seq=3 ttl=255 time=0. 5 packets received.221.107.168.0/0 192.596 --.100.221.107.255.504 64 bytes from 128.634/0.107.65: icmp_seq=0 ttl=255 time=0.0/0 192.65: icmp_seq=2 ttl=255 time=0.221.927 64 bytes from 128.221.221.255.20 255.65 ping statistics --5 packets transmitted.0.100.1 exit telnet server enable no ssh server enable no system default switchport system default switchport shutdown Would you like to edit the configuration? (yes/no) [n]: Use this configuration and save it? (yes/no) [y]: y N7K-1-pod5# N7K-1<x>nxos# sh running-config version 4.1 switchname pod5nxos <omitting interface config> interface mgmt0 ip address 192.452 64 bytes from 128.221.221.65: icmp_seq=1 ttl=255 time=0.221.Configure advanced IP options? (yes/no) [n]: Enable the telnet service? (yes/no) [y]: Enable the ssh service? (yes/no) [n]: Configure the ntp server? (yes/no) [n]: Configure default interface layer (L3/L2) [L3]: Configure default switchport interface state (shut/noshut) [shut]: Configure default switchport trunk mode (on/off/auto) [on]: The following configuration will be applied: switchname pod5nxos interface mgmt0 ip address 192.0 no shutdown vrf context management ip route 0.65: icmp_seq=4 ttl=255 time=0.927 ms ms ms ms ms ms 42 .107.168.100.20/26 N7K-1-pod5# ping 128.107.107.65 (128.0(3) username admin password 5 $1$XpvaHAKS$OhTkzciBdKkE4FOM0epik/ role vdc-admin telnet server enable ssh key rsa 1024 force no ssh server enable snmp-server user admin vdc-admin auth md5 0x77306315bd719b5d121cdeb6f0a9d697 priv 0x77306315bd719b5d121cdeb6f0a9d697 localizedkey vrf context management ip route 0.107.65): 56 data bytes 64 bytes from 128.128.692 64 bytes from 128.100.168.0.107.452/0.221.65 vrf management PING 128.0.107.00% packet loss round-trip min/avg/max = 0.0. 0.168.

When analyzing data traffic.2 192.0.0.0. Ethanalyzer can be used only from the default-VDC.2 224.0.90 2009-01-08 07:09:47.168.89 2009-01-08 07:09:46.202. To start access the default-VDC by opening the “Device Access” folder located in the “My Documents” folder and double click on the “N7K# default” ssh connection.1 192.2 224. NX-OS offers an integrated packet capture tool for packets directed to the control plane.2 192.202.1 192.203.168.203.0.202.89 2009-01-08 07:09:45.0.1 192.0. we wonʼt actually capture data traffic during this lab.0.0.1 192. This packet analyzer is built on top of Wireshark and it is called Ethanalyzer.90 2009-01-08 07:09:47.1 192.89 2009-01-08 07:09:46. but it can also be leveraged to look at data traffic in its “acl-log” mode.0.87 2009-01-08 07:09:45.2 224.2 224.2 224.2 224.84 2009-01-08 07:09:45.0.0.2 224.168.168. such traffic will reach the Supervisor after being rate limited in hardware.202.203.203.168. Wireshark® is the world's foremost network protocol analyzer and is the de facto (and often de jure) standard across many industries and educational institutions.2 HSRP HSRP HSRP HSRP HSRP HSRP HSRP HSRP HSRP HSRP Hello Hello Hello Hello Hello Hello Hello Hello Hello Hello (state (state (state (state (state (state (state (state (state (state Standby) Standby) Active) Active) Standby) Standby) Active) Active) Active) Active) 43 . N7K-1# ethanalyzer local interface ? inband Inband/Outband interface mgmt Management interface N7K-1# ethanalyzer local <CR> > >> brief capture-filter decode-internal display-filter limit-captured-frames limit-frame-size write | interface inband ? Redirect it to a file Redirect it to a file in append mode Display only protocol summary Filter on ethanalyzer capture Include internal system header decoding Display filter on frames captured Maximum number of frames to be captured (default is 100) Capture only a subset of a frame Filename to save capture to Pipe command output to filter The “brief” option will show one-liner info.89 2009-01-08 07:09:46.89 2009-01-08 07:09:46.168. and then we will set up an ACL just to show the procedure for capturing data-plane traffic.0.0.2 224.1 -> -> -> -> -> -> -> -> -> -> 224.0.0.2 224.2 192.168.203. The primary function of this protocol analyzer is to be able to capture and analyze control packets.Wireshark Wireshark used to be known as Ethereal®.168.0.0.168. During this step we will capture regular control traffic.0.0. N7K-1# ethanalyzer local interface inband brief capture-filter "udp" limitcaptured-frames 10 Capturing on eth0 10 packets captured 2009-01-08 07:09:45.168.202.90 192. where # is 1 for Student1 and 2 for Student 2.2 192.

N7K-1# To see the entire packet remove the “brief” keyword. . = IG bit: Group address (multicast/broadcast) .. 44 ... = IG bit: Individual address (unicast) . N7K-1# ethanalyzer local interface inband limit-captured-frames 30 write bootflash:capture Now the capture is on your Desktop..834050000 [Time delta from previous captured frame: 1227056768... ... launch Wireshark using the icon and load the file... = LG bit: Globally unique address (factory default) Type: IP (0x0800) <IP Header Omitted> Cisco Hot Standby Router Protocol Version: 0 Op Code: Hello (0) State: Standby (8) Hellotime: Non-Default (1) Holdtime: Non-Default (3) Priority: 20 Group: 1 Reserved: 0 Authentication Data: Default (cisco) Virtual IP Address: 192.168. ....0.. .. .. ...1 .... .....834050000 seconds] [Time delta from previous displayed frame: 1227056768. 62 bytes captured) Arrival Time: Nov 19...3 (192..168. 2008 01:06:08.. .... N7K-1# ethanalyzer local interface inband capture-filter "udp" limit-capturedframes 1 | no-more Capturing on eth0 1 packets captured Frame 1 (62 bytes on wire... Src: 00:22:55:79:be:42 (00:22:55:79:be:42).834050000 seconds] [Time since reference or first frame: 1227056768. Dst: 01:00:5e:00:00:02 (01:00:5e:0 0:00:02) Destination: 01:00:5e:00:00:02 (01:00:5e:00:00:02) Address: 01:00:5e:00:00:02 (01:00:5e:00:00:02) .. .. . .202......202.. so we can copy it over and look at it on our Windows machine......834050000 seconds] Frame Number: 1 Frame Length: 62 bytes Capture Length: 62 bytes [Frame is marked: False] [Protocols in frame: eth:ip:udp:hsrp] Ethernet II..... .. .. . ....0.. . = LG bit: Globally unique address (factory default) Source: 00:22:55:79:be:42 (00:22:55:79:be:42) Address: 00:22:55:79:be:42 (00:22:55:79:be:42) .......3) N7K-1# Let’s capture and store the file on the bootflash... ..0 . .

Ethanalyzer gives network administrators more visibility into applications behavior with few simple steps: 1. 6.1.1.16. Ethanalyzer can output to screen or dump to file on flash which can be copied to PC for GUI analysis Letʼs suppose to have an application using TCP port 5600 between the server 1. 4.16/32 eq 5600 log N7K-1(config)# int e1/1 N7K-1(config-if)# ip access-group etha in N7K-2-pod5(config-if)# end We can now capture selectively these packets and save the capture to the usb1 (so we could use our laptop with the nice wireshark graphical interface): N7K-1# ethanalyzer loc interf inband capture-filter "tcp port 5600" write bootflash:cap_acl_log 45 .1.16 eq 5600 log N7K-1(config-acl)# show ip access-lists etha IP access list etha statistics per-entry 10 permit tcp 1.1.24/32 1.a Ethereal) 7.24 host 1.1. so that network administrators can have an embedded and easy to use tool for on the fly capture.1.. Identify the application characteristics Create ad hoc ACL to match (and permit) the application flow between two servers Use the “log” keyword to punt copies of matching packets to supervisor CPU The original traffic gets forwarded with no impact The copies sent to CPU are subjected to hardware rate limiter (100 pps by default) These copies can be captured by our Ethanalyzer (Wireshark a.The following portion of the Wireshark step is optional.1. if you are running out of time jump to Step 13 “Virtual Device Context”!!! Ethanalyzer can capture data traffic as well.k.1. 5.1.24 and the client 1. Letʼs now create the ad hoc ACL and letʼs apply it to the interface.1. 3.1.1. 2.. We wonʼt actually capture traffic in this example and you do NOT need to run this part of the config: N7K-1(config)# ip access-list etha N7K-1(config-acl)# statistics per-entry N7K-1(config-acl)# permit tcp host 1.

Recommended Reading Cisco Nexus 7000 Series Switches: www.com/go/nxosnav Cisco NX-OS Home Page: www. and incorporate them into the content program year after year Go to the Internet stations located throughout the Convention Center to complete your session evaluations Thank you! 46 .cisco.cisco.com/go/nxos Complete Your Online Session Evaluation Cisco values your input. Give us your feedback! We read and carefully consider your scores and comments.html Cisco NX-OS Feature Navigator: www.com/en/US/products/ps9402/index.cisco.