DCICT

Introducing Cisco
Data Center
Technologies
Version 1.0 revision C

Lab Guide
DCICT

Lab Guide

Overview
This guide presents the instructions and other information concerning the lab activities for this course.

Outline
This guide includes these activities:
 Lab 0: Accessing the NterOne Lab Devices (Nexus 7000 Lab Rack)
 Activity 1: Cisco Power Calculator (Instructor Demonstration Only)
 Lab 2: Cisco Nexus 7000 Platform Discovery
 Lab 3: Running CLI Commands
 Lab 4: Configuring vPC
 Lab 5: Configuring FabricPath
 Lab 6: Configuring OTV
 Lab 7: Accessing the NterOne Lab Devices (Nexus 5000 Lab Rack)
 Lab 8: Initial Cisco Nexus 5000 Switch Configuration
 Lab 9: Initial Cisco MDS Switch Configuration
 Lab 10: Configuring the Cisco Nexus 2000 Series Fabric Extender
 Lab 11: Configuring FCoE
 Lab 12: Accessing the NterOne Lab Devices (UCS Lab Rack)
 Lab 13: Exploring the Cisco UCS Manager GUI
 Lab 14: Creating a Service Profile from a Template and Performing VMware ESXi 5.1 SAN Boot
 Activity 15: Initial Cisco UCS Configuration (Instructor Demonstration Only)
Lab 0: Accessing the NterOne Lab Devices
(Nexus 7000 Lab Rack)
The purpose of this lab exercise is to make you familiar with the NterOne lab environment and how to
successfully connect to the various devices that you will use during this class.

Task 1: Understanding your NterOne Lab Environment

Before you can begin configuring you lab devices you must understand how the NterOne lab environment is
constructed and how it is accessed.

Your Student Server

Before you can gain access to the NterOne lab devices you must first successfully log in to a Student Server.
 Once you have successfully logged in to a Student Server you will be able to use the applications
installed on the Student Server to access the lab devices for your class.
 Student Server names and account credentials will be given to you by your instructor.
 Two students may log in to the same Student Server using different accounts; in this case each
student will have a unique Desktop which is not shared with the other student.

The Student Servers are often referred to by a two-digit number (the Student Server Number) which is part of
the DNS and IP address of the Student Server.
 The first digit in the Student Server number corresponds to the NterOne Class Room Number to
which the Student Server belongs.
 The second digit in the Student Server number is the number of the specific Student Server within
that Room.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 3
©2016 NterOne Corporation
Pods and Pod Pairs
The NterOne lab hardware used during this class is divided into Pods and Pod Pairs:
 A Pod is a set of lab devices (hardware and software) that is configured by one or two students.
 A Pod Pair is a set of two Pods that may be required to work together to perform certain lab exercise
tasks.
 The Lab Guide will refer to the Pods within a Pod Pair as Pod P and Pod Q.
 Pod P always refers to the Pod to which you are assigned.
 Pod Q always refers to the opposite Pod within your Pod Pair, also referred to as the Peer Pod.

 A class may use more than one Pod Pair depending on the class size.
 All Student Servers can access all of the Pods used by the class. There are no restrictions binding a
Student Server to a specific Pod or Pod Pair.
 You will be assigned to a Pod for a given lab exercise, possibly with another student depending on
the class size.
 During the lab exercises you will be asked to configure the devices in your Pod. Do not configure
any devices outside your assigned Pod unless specifically instructed to do so.

Letter Variables
The Lab Guide for your class uses letter variables (similar to algebra) to represent letters or digits within a
command or command output. Usually, whenever you see one of the capital letters in the following table you
should replace that letter with the correct value; the Lab Guide should also point out when a letter variable is
being used. For example, if you are currently assigned to Pod 8, and if you are instructed to ping the IP
address of 10.20.30.4P, you would ping the IP address of 10.20.30.48. The following tables list all of the
letter variables that are commonly used in the Lab Guide.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 4
©2016 NterOne Corporation
 Letter Variable Description
R The Nexus 7000 Rack your class is using (1 or 2)
JK Your Pod Pair Number, w hich is a combination of your Pod Number and Peer Pod numbers
P Your Pod Number (this is assigned to you by your instructor)
Q Your Peer Pod Number (the number of the other Pod in your Pod Pair)
X The last letter of the name of your Pod Nexus 5548UP sw itch
Y The last letter of the name of your Peer Pod Nexus 5548UP sw itch

Your Assigned Your VDC Your Pod Value of Value of Value of Value of Value of
Pod Num ber Nam e N5K Nam e “P” “Q” “JK” “X” “Y”
1 vdc1 N5K-A 1 2 12 A B
2 vdc2 N5K-B 2 1 12 B A
3 vdc3 N5K-A 3 4 34 A B
4 vdc4 N5K-B 4 3 34 B A
5 vdc5 N5K-A 5 6 56 A B
6 vdc6 N5K-B 6 5 56 B A
7 vdc7 N5K-A 7 8 78 A B
8 vdc8 N5K-B 8 7 78 B A

Your Assigned Value of Value of Value of Value of Value of Value of Value of Value of
Pod Num ber “A” “B” “C” “D” “a” “b” “c” “d”
1 1 2 3 4 1 2 17 18
2 5 6 7 8 2 1 18 17
3 9 10 11 12 3 4 19 20
4 13 14 15 16 4 3 20 19
5 17 18 19 20 5 6 21 22
6 21 22 23 24 6 5 22 21
7 25 26 27 28 7 8 23 24
8 29 30 31 32 8 7 24 23

You should determine the value of each of these letter variables before you start each lab exercise. If you do
not use the correct values you may not be able to complete the lab exercise and you may also cause another
student’s lab devices to malfunction.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 5
©2016 NterOne Corporation
Remote Desktop Connection
The application that you must use to log in to your Student Server is Remote Desktop Connection (RDC).
 This is the only application that can be used to log in to your Student Server.
 The shortcut to RDC is typically found on Windows-based systems by clicking Start  All
Programs  Accessories  Remote Desktop Connection. Another way to find RDC is to use the
“Search programs and files” function in the Windows Start menu.

or

 Students using Apple-based computers can download the Microsoft Remote Desktop app from
https://itunes.apple.com/us/app/id715768417?mt=12 .
 Students using Linux-based computers can download rdesktop from http://www.rdesktop.org/ .

Task 2: Connect to your Assigned Student Server using Remote

Desktop Connection (RDC)
Follow the steps in this Task in order to log in to a Student Server.
Step 1 Your instructor will give you the information you need to log in to a Stu dent Server. The
following table is provided for you to record these values.

Student Server Nam e / IP Address User Nam e Passw ord

Step 2 Log in to your personal/work computer.

Step 3 Verify that your computer is able to access the Internet. A simple test to verify this would be to
use a browser to access www.nterone.com .
Step 4 Verify that your computer has a Remote Desktop Connection (RDC) client installed. Use the
information on the previous page if you are having difficulty finding RDC on your computer.
Step 5 Start the Remote Desktop Connection application. The following window should appear.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 6
©2016 NterOne Corporation
 Note The follow ing steps use the Microsoft version of RDC; if you are using an Apple- or Linux-based
computer the screens that you w ill see w ill be different.

Step 6 In the Computer field enter the DNS name or IP address of the Student Server that has been
assigned to you.
Step 7 Click the Connect button.The Windows Security window should appear.

Note If this step fails after several seconds, please contact your class instructor for assistance.

Note If you are able to access the Internet but are unable to access any of the NterOne Student
Servers you w ill need to determine if there is a firew all somew here preventing your computer
from accessing the NterOne Student Servers. This is a common problem for students w ho are
using a computer at their place of employment, in w hich case you may need to contact your
company’s IT department f or assistance.

Step 8 Click on the “Use another account” section of the window.

Step 9 Enter the User name and Password needed to connect to the Student Server.

Step 10 Click the OK button. A window should appear which will look similar to the window below

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 7
©2016 NterOne Corporation
 Step 11 Click the check box next to “Don’t ask me again for connections to this computer” and then
click “Yes”.
Step 12 After a few seconds the login process should finish and the desktop of your Student Server
should appear which will look similar to the window below.

Step 13 Information about how your Student Server is configured will be displayed in the upper right -
hand corner of the Desktop.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 8
©2016 NterOne Corporation
 Step 14 The most commonly used applications such as PuTTY will have shortcut to them on the
Desktop. Other applications may also be found using the Start menu.
Step 15 Some files that you will be using during the class will be located in the S: drive, also referred to
as the students file share. There is a shortcut to this location on the Desktop. There is also a
shortcut on the Desktop to the Local Class Files, which may also be used during the class.

Step 16 The process to connect to your Student Server is complete.

Task 3: Use PuTTY on the Student Server to Connect to the Lab

Equipment
This procedure details the steps you will use to connect to a network device using the PuTTY application.
This procedure assumes that you have successfully accessed your Student Server.
Step 17 Determine the following information about device to which you will be connecting:
 Device name or IP address
 Connection type (typically SSH or Telnet)
 Username
 Password
Step 18 From the desktop of your Student Server start the PuTTY application. A shortcut to PuTTY
should be on the desktop of the Student Server.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 9
©2016 NterOne Corporation
 Step 19 The PuTTY Configuration window will appear.

Step 20 Enter the IP address or the name of the device to which you will be connecting in the “Host
Name (or IP address)” field.
Step 21 Click the radio button next to the correct Connection type.
Step 22 Click the Open button.

Note If you see the PuTTY Fatal Error w indow appear (show n below ) this means that PuTTY w as not
able to contact the device that you entered in the previous steps. Verify the IP address and/or
device name and try again. You may also need to verify that the target device is able to accept
connections. If you continue to have difficulty connecting to the device contact your instructor.

Step 23 If the connection attempt is successful you may see a window similar to the examples below. If
one of these windows appears, click Yes to continue.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 10
©2016 NterOne Corporation
 Step 24 If the connection attempt is successful you will see a window similar to the example below

Step 25 Enter the login information that the device is requesting, If the credentials are valid you should
see a command line prompt similar to the example show below.

Step 26 The process to use PuTTY to connect to a network device is complete.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 11
©2016 NterOne Corporation
Activity 1: Using the Cisco Power Calculator
(Instructor Demonstration Only)
During this task, your instructor will demonstrate how to use the Cisco Power Calculator.

Activity Procedure
Complete these steps:
Step 1 On your computer open a browser and navigate to the Cisco website at http://www.cisco.com
and log in using your Cisco.com account credentials.
Step 2 Go to http://tools.cisco.com/cpc/ to access the Cisco Power Calculator:
Step 3 Click Launch Cisco Power Calculator to launch the calculator.

Step 4 Click “I Agree” to accept or confirm acceptance of the online privacy policy.
Step 5 If necessary, click on the “Select Product” tab so that it is in the foreground.
Step 6 In the Product Family drop-down menu, choose Cisco Nexus 7000.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 12
©2016 NterOne Corporation
 Step 7 Click the Next button.
Step 8 In the Configure Product tab, choose the following options:
Chassis: N7K-C7009
Supervisor Engine: N7K-SUP1
Redundant Supervisor Engine: YES
Fantray: N7K-C7009-FAN
How many Fabric modules? 5
Input Voltage: 200-240 volts
Slot 1: N7K-SUP1
Slot 2: N7K-SUP1
Slot 3: N7K-M148GT-11L
Slot 4: N7K-M148GT-11L
Slot 5: N7K-M132XP-12L
Slot 6: N7K-F248XP-25
Slot 7: N7K-F248XP-25
Slot 8: N7K-M108X2-12L
Slot 9: N7K-M108X2-12L

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 13
©2016 NterOne Corporation
 Step 9 Click the Next button.
Step 10 The Power Calculation tab appears showing power supply recommendations.

Step 11 View the supported redundancy options further down on the same page.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 14
©2016 NterOne Corporation
 Step 12 View the information in the Total Output columns, which is based on the chosen power
redundancy mode.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 15
©2016 NterOne Corporation
 Step 13 View how much power each item requires.

Step 14 Click the link to download the summary either to a Microsoft Excel or Adobe PDF file.

Activity Verification
You have completed this task when you attain this result:
 You have used the Cisco Power Calculator to calculate power supply options for the Cisco Nexus
7000 9-Slot Switch chassis and selected modules.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 16
©2016 NterOne Corporation
Lab 2: Cisco Nexus 7000 Platform Discovery
Complete this lab activity to practice what you learned in the related module.

Activity Objective
In this activity, you will log into the admin VDC and discover the Cisco Nexus 7000 Switch platform
hardware and software components. You will connect to your remote lab to complete your task. After
completing this activity, you will be able to meet these objectives:
 Validate key Cisco Nexus 7000 hardware and software parameters
 Configure I/O module interfaces in your VDC
 Assign IP addresses to interfaces and validate Layer 3 connectivity
 Create a configuration checkpoint and perform a rollback operation

Command List
The table describes the commands that are used in this activity.

Com m and Description

checkpoint {[cp-name] [description descr] | This command creates a checkpoint of the running
file filename } configuration to either a user checkpoint name or a file.
configure This command enters global configuration mode.
dir bootflash: This command displays the bootflash contents.
This command specifies an Ethernet interface to configure,
interface Ethernet slot/port
and enters interface configuration mode.
ip address ipv4 address/length This command configures the IP address for this interface.
rollback running-config checkpoint cp- This command creates a rollback to the specified checkpoint
name name or file.

show cp state This command displays status information about the

supervisor module control processor.
This command displays information about the hardw are
show environment
environment status.
show interface brief This command displays a table of interface states.
show inventory This command displays all hardw are inventory information.
show ip interface brief This command displays IP-related interface information.

show module This command displays module information for all I/O
modules and supervisor modules in the chassis.

show redundancy status This command displays detailed information about

redundancy.
show running-config interface This command displays the interface running configuration.
This command displays information about the softw are
show version
version.
This command configures the interface as a Layer 2
sw itchport interface and deletes any configuration that is specific to
Layer 3 on this interface.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 17
©2016 NterOne Corporation
Task 0: Lab Preparation
In this task, you will perform the steps necessary to get ready for performing the subsequent tasks in this lab
exercise.

Activity Procedure
Complete these steps:
Step 1 Make sure that you know the value of your Pod Number. Your Pod Number is assigned to you
by your instructor and is used to identify the lab devices that you will use during this lab
exercise. Refer to the following table when a task step in this lab exercise uses a letter variable.

Your
Your Your Your
Assigned Value of Value of Value of Value of Value of
Pod VDC Peer Pod Pod N5K “P” “Q” “JK” “X” “Y”
Pod
Nam e VDC Nam e Nam e
Num ber
1 vdc1 vdc2 N5K-A 1 2 12 A B
2 vdc2 vdc1 N5K-B 2 1 12 B A
3 vdc3 vdc4 N5K-A 3 4 34 A B
4 vdc4 vdc3 N5K-B 4 3 34 B A
5 vdc5 vdc6 N5K-A 5 6 56 A B
6 vdc6 vdc5 N5K-B 6 5 56 B A
7 vdc7 vdc8 N5K-A 7 8 78 A B
8 vdc8 vdc7 N5K-B 8 7 78 B A

Your
Assigned Value of Value of Value of Value of Value of Value of Value of Value of
“A” “B” “C” “D” “a” “b” “c” “d”
Pod Num ber
1 1 2 3 4 1 2 17 18
2 5 6 7 8 2 1 18 17
3 9 10 11 12 3 4 19 20
4 13 14 15 16 4 3 20 19
5 17 18 19 20 5 6 21 22
6 21 22 23 24 6 5 22 21
7 25 26 27 28 7 8 23 24
8 29 30 31 32 8 7 24 23

Step 2 Make sure that you know the value of your Rack Number. Your Rack Number is assigned to
you by your instructor and is used to identify the Nexus 7000 rack of devices that you will use
during this lab exercise.
Step 3 Your assigned Pod is one of two Pods within a Pod Pair. The details of each Pod Pair, including
diagrams and tables of related values, are contained in one of several NterOne Resource Guide
documents. Open the NterOne Resource Guide that corresponds to your assigned Pod Number.
Step 4 Locate the various tables that provide additional information about your assigned Pod, which
include details such as IP addresses and device login credentials.
Step 5 Verify that you are currently logged in to your Student Server.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 18
©2016 NterOne Corporation
 Step 6 From your Student Server desktop use the PuTTY application to open SSH sessions to each of
the devices in the following table (there may be preconfigured shortcuts to these devices on the
Student Server desktop).

Note * You w ill need to get the passw ords for the Nexus sw itches from your instructor.

Note Make sure to use the IP address that corresponds to your assigned Rack Number .

Device Nam e Device Description IP Address Username Passw ord

vdcP Your Pod Nexus 7004 VDC Rack 1 – 10.0.0.8P admin *

(Pod VDC) Rack 2 – 10.0.0.18P
Rack 1 – 10.0.0.80
N7K The Nexus 7004 admin VDC student Nterone179
Rack 2 – 10.0.0.180

Activity Verification
You have completed this activity when you have achieved these goals:
 You have made a successful connection to your Student Server.
 You have successfully used PuTTY to connect to the devices in the table above.

Task 1: Platform Validation

In this task, you will validate key Cisco Nexus 7000 hardware and software parameters.

Activity Procedure
Complete these steps:
Step 7 Switch to the PuTTY session to the admin VDC (N7K).
Step 8 Determine the system software version that is currently running on the Cisco Nexus 7004
Switch by entering the show version command.

N7K# show version

Cisco Nexus Operating System (NX-OS) Software
TAC support: http://www.cisco.com/tac
Documents: http://www.cisco.com/en/US/products/ps9372/tsd_products_support_serie
s_home.html
Copyright (c) 2002-2015, Cisco Systems, Inc. All rights reserved.
The copyrights to certain works contained in this software are
owned by other third parties and used and distributed under
license. Certain components of this software are licensed under
the GNU General Public License (GPL) version 2.0 or the GNU
Lesser General Public License (LGPL) Version 2.1. A copy of each
such license is available at
http://www.opensource.org/licenses/gpl-2.0.php and
http://www.opensource.org/licenses/lgpl -2.1.php

Software
BIOS: version 2.12.0
kickstart: version 7.2(1)D1(1)
system: version 7.2(1)D1(1)
BIOS compile time: 05/29/2013
kickstart image file is: bootflash:///n7000 -s2-kickstart.7.2.1.D1.1.bin
kickstart compile time: 10/8/2015 15:00:00 [10/24/2015 05:44:18]
system image file is: bootflash:///n7000 -s2-dk9.7.2.1.D1.1.bin
system compile time: 10/8/2015 15:00:00 [10/24/2015 07:38:15]

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 19
©2016 NterOne Corporation
 Hardware
cisco Nexus7000 C7004 (4 Slot) Chassis ("Supervisor Module -2")
Intel(R) Xeon(R) CPU with 32744992 kB of memory.
Processor Board ID JAF1803BARF

Device name: N7K

bootflash: 2007040 kB
slot0: 0 kB (expansion flash)

Kernel uptime is 0 day(s), 19 hour(s), 56 minute(s), 9 second(s)

Last reset at 671220 usecs after Fri Jul 4 20:2 3:19 2014

Reason: Reset Requested by CLI command reload

System version: 7.2(1)D1(1)
Service:

plugin
Core Plugin, Ethernet Plugin

Active Package(s)

Q1) Which version of Cisco NX-OS Software is currently running on the active and standby processors?

Q2) How much memory is present on the CPU motherboard?

Q3) How much bootflash memory is present?

Step 9 View the contents of the bootflash directory.

N7K# dir bootflash:

4096 Jun 07 23:12:39 2014 .patch/
0 Feb 08 17:17:01 2013 admin.rc.cli
4096 Jul 04 20:22:06 2014 configs/
4096 Sep 21 22:05:57 2014 licenses/
4096 May 22 11:38:21 2014 lost+found/
218199431 Mar 28 04:16:50 2014 n7000-s2-dk9.6.1.2.bin
425228450 Aug 29 15:50:34 2013 n7000-s2-dk9.6.2.12.bin
479589200 Jun 07 14:27:28 2014 n7000-s2-dk9.7.2.1.D1.1.bin
67492633 Aug 29 15:47:22 2013 n7000-s2-epld.6.2.12.img
36344320 Mar 28 04:16:16 2014 n7000-s2-kickstart.6.1.2.bin
36633088 Aug 29 15:46:45 2013 n7000-s2-kickstart.6.2.12.bin
37989376 Jun 07 14:28:48 2014 n7000-s2-kickstart.7.2.1.D1.1.bin
2451 Jul 04 23:02:13 2014 poap_replay01.cfg
2451 Jul 04 23:02:19 2014 poap_replay02.cfg
4096 Jun 07 23:13:50 2014 scripts/
4096 Jul 04 23:14:18 2014 vdc_2/
4096 Jul 04 23:14:51 2014 vdc_3/
4096 Jul 01 16:53:28 2014 vdc_4/
4096 Jul 01 16:58:47 2014 vdc_5/
4096 Jun 15 16:32:27 2014 vdc_6/
4096 Jun 23 15:10:14 2014 vdc_7/
4096 Jun 08 14:49:55 2014 vdc_8/
4096 Jun 22 18:36:32 2014 vdc_9/
4096 Jun 07 23:12:42 2014 virtual -instance-stby-sync/

Usage for bootflash://sup-local

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 20
©2016 NterOne Corporation
 1429946368 bytes used
386539520 bytes free
1816485888 bytes total

Q4) What is the file size of each kickstart and system image?

Step 10 Determine the Cisco Nexus 7004 hardware components.

N7K# show inventory

NAME: "Chassis", DESCR: "Nexus7000 C7004 (4 Slot) Chassis "
PID: N7K-C7004 , VID: V01 , SN: JAF1651AMRJ

NAME: "Slot 1", DESCR: "Supervisor module-2"

PID: N7K-SUP2E , VID: V01 , SN: JAF1652ANGS

NAME: "Slot 3", DESCR: "10/100/1000 Mbps Ethernet XL Module"

PID: N7K-M148GT-11L , VID: V02 , SN: JAF1651AGHR

NAME: "Slot 4", DESCR: "1/10 Gbps Ethern et Module"

PID: N7K-F248XP-25E , VID: V01 , SN: JAF1707AGGQ

NAME: "Slot 33", DESCR: "Nexus7000 C7004 (4 Slot) Chassis Power Supply"
PID: N7K-AC-3KW , VID: V01 , SN: DTM164800GF

NAME: "Slot 34", DESCR: "Nexus7000 C7004 (4 Slot) Chassis Power Supply"
PID: N7K-AC-3KW , VID: V01 , SN: DTM164901SV

NAME: "Slot 37", DESCR: "Nexus7000 C7004 (4 Slot) Chassis Fan Module"
PID: N7K-C7004-FAN , VID: V01 , SN: JAF1649BFHK

Q5) Does this switch offer N + 1 switching redundancy?

Q6) How many I/O modules are installed in this chassis?

Q7) How many power supplies are installed in this chassis?

Q8) How many system fans are installed in this chassis?

Q9) Is there system fan redundancy in this chassis?

Q10) How many empty I/O module slots are there in this chassis?

Step 11 Display system environment information.

N7K# show environment

Power Supply:
Voltage: 50 Volts
Power Actual Total
Supply Model Output Capacity Status
(Watts ) (Watts )
------- ------------------- ----------- ----------- --------------

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 21
©2016 NterOne Corporation
 1 N7K-AC-3KW 826 W 3000 W Ok
2 N7K-AC-3KW 0 W 0 W Shutdown
3 ------------ 0 W 0 W Absent
4 ------------ 0 W 0 W Absent

Actual Power
Module Model Draw Allocated Status
(Watts ) (Watts )
------- ------------------- ----------- ----------- --------------
1 N7K-SUP2E 129 W 265 W Powered -Up
2 supervisor N/A 0 W Absent
3 N7K-M148GT-11L 274 W 400 W Powered -Up
4 N7K-F248XP-25E 300 W 450 W Powered -Up
fan1 N7K-C7004-FAN 134 W 450 W Powered -Up

N/A - Per module power not available

Power Usage Summary:

--------------------
Power Supply redundancy mode (configured) PS -Redundant
Power Supply redundancy mode (operational) Non -Redundant

Total Power Capacity (based on configured mode) 3000 W

Total Power of all Inputs (cumulative) 3000 W
Total Power Output (actual draw) 826 W
Total Power Allocated (budget) 1830 W
Total Power Available for additional modules 1170 W

Clock:
----------------------------------------------------------
Clock Model Hw Status
----------------------------------------------------------
A Clock Module -- NotSupported/None
B Clock Module -- NotSupported/None

Fan:
------------------------------------------------------
Fan Model Hw Status
------------------------------------------------------
Fan1(sys_fan1) N7K-C7004-FAN 1.0 Ok
Fan_in_PS1 -- -- Ok
Fan_in_PS2 -- -- Shutdown
Fan_in_PS3 -- -- Absent
Fan_in_PS4 -- -- Absent
Fan Zone Speed: Zone 1: 0x8f

Temperature:
--------------------------------------------------------------------
Module Sensor MajorThresh MinorThres CurTemp Status
(Celsius) (Celsius) (Celsius)
--------------------------------------------------------------------
1 Inlet (s1) 60 42 32 Ok
1 PMFPGA (s2) 80 60 39 Ok
1 Crossbar(s3) 105 95 52 Ok
1 L2L3Dev1(s4) 105 95 38 Ok
1 Arbiter (s5) 105 95 45 Ok
1 CPU1CORE1(s6) 85 70 38 Ok
<… output omitted …>

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 22
©2016 NterOne Corporation
 Q11) Which power supply redundancy mode is currently specified?

Q12) Which module or modules draw the least amount of power?

Step 12 Display individual module hardware summary information.

N7K# show module

Mod Ports Module-Type Model Status

--- ----- ----------------------------------- ------------------ ----------
1 0 Supervisor module-2 N7K-SUP2E active *
3 48 10/100/1000 Mbps Ethernet XL Module N7K -M148GT-11L ok
4 48 1/10 Gbps Ethernet Module N7K -F248XP-25E ok

Mod Sw Hw
--- -------------- ------
1 6.1(2) 1.0
3 6.1(2) 1.2
4 6.1(2) 1.0

Mod MAC-Address(es) Serial -Num

--- -------------------------------------- ----------
1 84-78-ac-58-09-d4 to 84-78-ac-58-09-e6 JAF1652ANGS
3 00-06-f6-1b-86-14 to 00-06-f6-1b-86-47 JAF1651AGHR
4 84-78-ac-0f-66-50 to 84-78-ac-0f-66-83 JAF1707AGGQ

Mod Online Diag Status

--- ------------------
1 Pass
3 Pass
4 Pass

* this terminal session

Activity Verification
You have completed this task when you attain these results:
 You have successfully identified key software and hardware parameters.

Task 4: Interface Configuration

During this exercise, you will complete the interface configuration of all I/O modules and activate the
interfaces in your Pod VDC.

Activity Procedure
Complete these steps:
Step 13 Switch to the PuTTY session to your Pod VDC.
Step 14 View the status of all of the interfaces in the Pod VDC by entering the show interface brief
command.

vdcP# show interface brief

--------------------------------------------------------------------------------
Port VRF Status IP Address Speed MTU

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 23
©2016 NterOne Corporation
 --------------------------------------------------------------------------------
mgmt0 -- up 10.0.0.xxx 100 1500

--------------------------------------------------------------------------------
Ethernet VLAN Type Mode Status Reason Speed Port
Interface Ch #
--------------------------------------------------------------------------------
Eth3/A -- eth routed down Administratively down auto(D) --
Eth3/B -- eth routed down Administratively down auto(D) --
Eth3/C -- eth routed down Administratively down auto(D) --
Eth3/D -- eth routed down Administratively down auto(D) --
Eth4/A 1 eth access down Administratively down auto(D) --
Eth4/B 1 eth access down Administratively down auto(D) --
Eth4/C 1 eth access down Administratively down auto(D) --
Eth4/D 1 eth access down Administratively down auto(D) --

-------------------------------------------------------------------------------
Interface Secondary VLAN(Type) Status Reason
-------------------------------------------------------------------------------
Vlan1 -- down Administratively down
VlanP0 -- down VLAN is down
VlanJK -- down VLAN is down
VlanQ0 -- down VLAN is down

Q13) Are the I/O module interfaces currently set to perform as Layer 2 or Layer 3 interfaces?

Step 15 Determine the SFP+ transceiver types that are installed in module 4.

vdcP# show interface transceiver

Ethernet3/1
transceiver is not applicable

Ethernet3/2
transceiver is not applicable

Ethernet3/3
transceiver is not applicable

Ethernet3/4
transceiver is not applicable

Ethernet4/A
transceiver is present
type is SFP-H10GB-CU5M
name is CISCO-MOLEX
part number is 74752-9521
revision is 09
serial number is MOC1638050A
nominal bitrate is 10300 MBit/sec
Link length supported for copper is 5 m
cisco id is --
cisco extended id number is 4

Ethernet4/B
transceiver is present
type is SFP-H10GB-CU5M
name is CISCO-MOLEX
part number is 74752-9521
revision is 09
serial number is MOC1638051W
nominal bitrate is 10300 MBit/sec

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 24
©2016 NterOne Corporation
 Link length supported for copper is 5 m
cisco id is --
cisco extended id number is 4

Ethernet4/C
transceiver is present
type is SFP-H10GB-CU5M
name is CISCO-MOLEX
part number is 74752-9521
revision is 09
serial number is MOC1638050A
nominal bitrate is 10300 MBit/sec
Link length supported for copper is 5 m
cisco id is --
cisco extended id number is 4

Ethernet4/D
transceiver is present
type is SFP-H10GB-CU5M
name is CISCO-MOLEX
part number is 74752-9521
revision is 09
serial number is MOC1638050A
nominal bitrate is 10300 MBit/sec
Link length supported for copper is 5 m
cisco id is --
cisco extended id number is 4

Q14) Which type of SFP+ transceivers are installed in module 4?

Q15) What is the maximum distance between devices that this transceiver will support?

Step 16 Examine the detailed interface status of the first Ethernet interface in your VDC.

vdcP# show interface ethernet 4/A

Ethernet4/A is down (Administratively down)
admin state is down, Dedicated Interface
Hardware: 1000/10000 Ethernet, address: 8478.ac57.9649 (bia acf2.c564.9a04)
MTU 1500 bytes, BW 10000000 Kbit, DLY 10 usec
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, medium is broadca st
auto-duplex, auto-speed, media type is 10G
Beacon is turned off
Auto-Negotiation is turned on
Input flow-control is off, output flow-control is off
Auto-mdix is turned off
Rate mode is dedicated
Switchport monitor is off
EtherType is 0x8100
EEE (efficient-ethernet) : n/a
Last link flapped never
Last clearing of "show interface" counters never
0 interface resets
30 seconds input rate 0 bits/sec, 0 packets/sec
30 seconds output rate 0 bits/sec, 0 packets/sec
Load-Interval #2: 5 minute (300 seconds)
input rate 0 bps, 0 pps; output rate 0 bps, 0 pps
RX
120 unicast packets 13635 multicast packets 0 broadcast packets

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 25
©2016 NterOne Corporation
 13671 input packets 1221910 bytes
0 jumbo packets 0 storm suppression packets
0 runts 0 giants 0 CRC 0 no buffer
0 input error 0 short frame 0 overrun 0 underrun 0 ignored
0 watchdog 0 bad etype drop 0 bad proto drop 0 if down drop
0 input with dribble 0 input discard
0 Rx pause
TX
120 unicast packets 417 multicast packets 0 broadcast packets
453 output packets 140839 bytes
0 jumbo packets
0 output error 0 collision 0 deferred 0 late collision
0 lost carrier 0 no carrier 0 babble 0 output discard
0 Tx pause

Step 17 Examine the interface capabilities of the first interface in your VDC.

vdcP# show interface ethernet 4/A capabilities

Ethernet4/A
Model: N7K-F248XP-25
Type (SFP capable): 10Gbase-(unknown)
Speed: 1000,10000
Duplex: full
Trunk encap. type: 802.1Q
FabricPath capable: yes
Channel: yes
Broadcast suppression: percentage(0 -100)
Flowcontrol: rx-(off/on/desired),tx-(off/on/desired)
Rate mode: dedicated
Port mode: Routed,Switched
QOS scheduling: rx-(8q4t),tx-(3p5q1t)
CoS rewrite: yes
ToS rewrite: yes
SPAN: yes
UDLD: yes
MDIX: no
TDR capable: no
Link Debounce: yes
Link Debounce Time: yes
FEX Fabric: yes
dot1Q-tunnel mode: yes
Pvlan Trunk capable: yes
Port Group Members: A-D
EEE (efficient-eth): no
PFC capable: yes

Step 18 Operationally enable two interfaces within your Pod VDC, Ethernet 3/C and 3/D.

vdcP# configure
Enter configuration commands, one per line. End with CNTL/Z.
vdcP(config)# interface ethernet 3/C-D
vdcP(config-if-range)# no shutdown
vdcP(config-if-range)# end

Step 19 Verify that the interfaces you just enabled are in an “up” state. You may have to wait until your
Peer Pod completes the previous step before the interfaces will appear as “up”.

vdcP# show interface brief | include Eth3

Eth3/1 -- eth routed down Administratively down auto(D) --
Eth3/2 -- eth routed down Administratively down auto(D) --
Eth3/3 -- eth routed up none 1000(D) --

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 26
©2016 NterOne Corporation
 Eth3/4 -- eth routed up none 1000(D) --

Activity Verification
You have completed this task when you attain these results:
 You have used show commands to verify the Ethernet interface status.
 You have determined the operational speed of the Ethernet interfaces.
 You have enabled the Ethernet interfaces.

Task 6: Checkpoints and Rollback

This exercise will familiarize you with creating and utilizing a configuration checkpoint and rollback. This
exercise allows you to name and retrieve the saved running configuration from a particular po int in time.
Creating a checkpoint is a convenient feature that allows you to revert to an older running configuration. An
older running configuration may be required because of configuration error or instability of the existing
configuration.

Activity Procedure
Complete these steps:
Step 20 View the current configuration of interface Ethernet 3/D. At this point the interface should be
enabled.

vdcP# show running-config interface ethernet 3/D

!Command: show running-config interface Ethernet3/D

!Time: Sat Jul 5 16:32:39 2014

version 7.2(1)D1(1)

interface Ethernet3/D
description [from vdcP Eth 3/D (3/D) to vdcQ Eth 3/?]
no shutdown

Step 21 Create and name the checkpoint CHARLIE for the current configuration.

vdcP# checkpoint ?
*** No matching command found in curren t mode, matching in (exec) mode ***
<CR>
WORD Checkpoint name (Max Size 80)
description Checkpoint description for the given checkpoint
file Create configuration rollback checkpoint to file
vdcP# checkpoint CHARLIE
Done

Step 22 Verify the newly created checkpoint.

vdcP# show checkpoint summary

1) CHARLIE:
Created by admin
Created at Sat, 16:32:05 05 Jul 2014
Size is 5,430 bytes
User Checkpoint Summary
--------------------------------------------------------------------------------
Description: None

Step 23 Modify the running configuration by shutting down interface Ethernet 3/D.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 27
©2016 NterOne Corporation
 vdcP# configure
Enter configuration commands, one per line. End with CNTL/Z.
vdcP(config)# interface ethernet 3/D
vdcP(config-if)# shutdown
vdcP(config-if)# end

Step 24 Verify the new configuration of the interface.

vdcP# show running-config interface ethernet 3/D

!Command: show running-config interface Ethernet3/D

!Time: Sat Jul 5 16:32:39 2014

version 7.2(1)D1(1)

interface Ethernet3/D
description [from vdcP Eth 3/D (3/D) to vdcQ Eth 3/?]

Step 25 Perform the rollback operation.

vdcP# rollback running-config checkpoint CHARLIE

Note: Applying config parallelly may fail Rollback verification
Collecting Running-Config
#Generating Rollback Patch
Executing Rollback Patch
Generating Running-config for verification
Generating Patch for verification
Verification is Sucessful.

Rollback completed successfully.

Step 26 Verify the rollback.

vdcP# show running-config interface ethernet 3/D

!Command: show running-config interface Ethernet3/D

!Time: Sat Jul 5 16:32:39 2014

version 7.2(1)D1(1)

interface Ethernet3/D
description [from vdcP Eth 3/D (3/D) to vdcQ Eth 3/?]
no shutdown

Step 27 To remove a checkpoint, use the no form of the command.

vdcP# no checkpoint CHARLIE

Done

Step 28 Verify that the checkpoint has been removed.

vdcP# show checkpoint summary

vdcP#

Activity Verification
You have completed this task when you attain these results:
 You have created a configuration checkpoint. You have made some changes to the configuration,
and you have successfully rolled back to the previous checkpoint.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 28
©2016 NterOne Corporation
Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 29
©2016 NterOne Corporation
Lab 3: Running CLI Commands
Complete this lab activity to practice what you learned in the related module

Activity Objective
In this activity, you will connect to your Pod Switches to run various show commands. After completing this
activity, you will be able to meet these objectives:
 Configure Layer 2 and Layer 3 interfaces
 Use show commands to verify VLANs and VLAN membership, which interfaces are operational,
and verify the MAC address table
 Verify which Cisco NX-OS Software version is running on the switch, the running and startup
configurations, and determine if there are any connectivity issues in the network

Task 0: Lab Preparation

In this task, you will perform the steps necessary to get ready for performing the subsequent tasks in this lab
exercise.

Activity Procedure
Complete these steps:
Step 1 Make sure that you know the value of your Pod Number. Your Pod Number is assigned to you
by your instructor and is used to identify the lab devices that you will use during this lab
exercise. Refer to the following table when a task step in this lab exercise uses a letter variable.

Your
Your Your Your
Assigned Value of Value of Value of Value of Value of
Pod VDC Peer Pod Pod N5K “P” “Q” “JK” “X” “Y”
Pod
Nam e VDC Nam e Nam e
Num ber
1 vdc1 vdc2 N5K-A 1 2 12 A B
2 vdc2 vdc1 N5K-B 2 1 12 B A
3 vdc3 vdc4 N5K-A 3 4 34 A B
4 vdc4 vdc3 N5K-B 4 3 34 B A
5 vdc5 vdc6 N5K-A 5 6 56 A B
6 vdc6 vdc5 N5K-B 6 5 56 B A
7 vdc7 vdc8 N5K-A 7 8 78 A B
8 vdc8 vdc7 N5K-B 8 7 78 B A

Your
Assigned Value of Value of Value of Value of Value of Value of Value of Value of
“A” “B” “C” “D” “a” “b” “c” “d”
Pod Num ber
1 1 2 3 4 1 2 17 18
2 5 6 7 8 2 1 18 17
3 9 10 11 12 3 4 19 20
4 13 14 15 16 4 3 20 19
5 17 18 19 20 5 6 21 22
6 21 22 23 24 6 5 22 21

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 30
©2016 NterOne Corporation
 Your
Assigned Value of Value of Value of Value of Value of Value of Value of Value of
“A” “B” “C” “D” “a” “b” “c” “d”
Pod Num ber
7 25 26 27 28 7 8 23 24
8 29 30 31 32 8 7 24 23

Step 2 Make sure that you know the value of your Rack Number. Your Rack Number is assigned to
you by your instructor and is used to identify the Nexus 7000 rack of devices that you will use
during this lab exercise.
Step 3 Your assigned Pod is one of two Pods within a Pod Pair. The details of each Pod Pair, including
diagrams and tables of related values, are contained in one of several NterOne Resource Guide
documents. Open the NterOne Resource Guide that corresponds to your assigned Pod Number.
Step 4 Locate the various tables that provide additional information about your assigned Pod, which
include details such as IP addresses and device login credentials.
Step 5 Locate the diagram that corresponds to this lab exercise. This diagram may help you visualize
the intended goal of this lab exercise.

Task 0.1: Log In to your Student Server and Connect to Lab Devices
During this task you will log in to your assigned Student Server and use PuTTY to start SSH sessions to each
of the devices that you will use during this lab exercise.

Activity Procedure
Complete these steps:
Step 6 Verify that you are currently logged in to your Student Server.
Step 7 From your Student Server desktop use the PuTTY application to open SSH sessions to each of
the devices in the following table (there may be preconfigured shortcuts to these devices on the
Student Server desktop).

Note * You w ill need to get the passw ords for the Nexus sw itches from your instructor.

Note Make sure to use the IP address that corresponds to your assigned Rack Number.

Device Nam e Device Description IP Address Username Passw ord

vdcP Your Pod Nexus 7004 VDC Rack 1 – 10.0.0.8P admin *

(Pod VDC) Rack 2 – 10.0.0.18P
Your Peer Pod Nexus 7004 VDC Rack 1 – 10.0.0.8Q
vdcQ admin *
(Peer Pod VDC) Rack 2 – 10.0.0.18Q

N5K-A Nexus 5548UP Sw itch managed by Rack 1 – 10.0.0.78 podP *

odd-numbered Pods Rack 2 – 10.0.0.178
Nexus 5548UP Sw itch managed by Rack 1 – 10.0.0.79
N5K-B podP *
even-numbered Pods Rack 2 – 10.0.0.179

Note It is suggested that you arrange the PuTTY w indow s in a rectangle in a similar arrangement as
the sw itches in the lab diagram in the Resource Guide.

Task 0.2: Reset the Configuration of your Pod VDC

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 31
©2016 NterOne Corporation
 In order to ensure that the steps in this lab exercise function properly the running configuration of your Pod
VDC must be reset to the baseline configuration. During this task you will reset the configuration of your
Pod VDC to the baseline state.

Activity Procedure
Complete these steps:
Step 8 Switch to the PuTTY session to your Pod VDC (vdcP).
Step 9 You will be using the NX-OS checkpoint function to reset the configuration of the VDC to a
baseline state, which removes the configuration created in a previous lab exercise. Execute the
following command to roll back the configuration:
rollback running-config file bootflash:baseline best-effort

vdcP# rollback running-config file bootflash:baseline best-effort

Collecting Running-Config
#Generating Rollback Patch
Executing Rollback Patch

Rollback completed successfully.

Step 10 Execute the show running-config command. You should see that all of the physical interfaces
now only have a description and there are no commands present from the previous lab exercise.
Step 11 Execute the show running-config ip command. The baseline configuration contains three
VLAN interfaces; each VLAN interface should have an IP address assigned to it.

Note If any of the VLAN interfaces do NOT have an IP address, repeat the rollback command in
Step 9. In some cases the rollback does not reset all of the configuration.

vdcP# show running-config ip

!Command: show running-config ip

!Time: Tue Jun 10 14:34:05 2014

version 7.2(1)D1(1)
vrf context management
ip route 0.0.0.0/0 10.0.0.1

interface VlanP0
ip address 172.16.P0.7P/24

interface VlanJK
ip address 172.16.JK.7P/24

interface VlanQ0
ip address 172.16.Q0.7P/24

interface mgmt0
ip address 10.0.0.xxx/24

vdcP#

Task 0.3: Reset the Configuration of your Pod N5K

In order to ensure that the steps in this lab exercise function properly the running configuration of your Po d
N5K must be reset to the baseline configuration. During this task you will reset the configuration of your Pod
N5K to the baseline state for the portions of the overall switch configuration that are managed by your Pod.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 32
©2016 NterOne Corporation
Activity Procedure
Complete these steps:
Step 12 Switch to the PuTTY session to your Pod N5K (N5K-X).
Step 13 Reset the running configuration of your Pod to the baseline state by entering the
run-script baseline command (where “P” is your Pod Number).

N5K-A# run-script resetpodP

`configure
`default interface Ethernet1/P-Q
<… output omitted …>
`end

Step 14 Execute the show running-config interface Ethernet 1/P-Q command (where “P” is your Pod
Number and “Q” is your Peer Pod Number). You should see that these interfaces now only have
a description and there are no commands present from the previous lab exercise.

N5K-X# show running-config interface ethernet 1/P-Q

!Command: show running-config interface Ethernet1/P-Q

!Time: Mon Jul 4 11:57:15 2016

version 7.3(0)N1(1)

interface Ethernet1/P
description [from N5K-X Eth 1/P (1/a) to vdcP Eth 4/?]

interface Ethernet1/Q
description [from N5K-X Eth 1/Q (1/b) to vdcQ Eth 4/?]

Activity Verification
You have completed this activity when you have achieved these goals:
 You have made a successful connection to your Student Server.
 You have successfully used PuTTY to connect to the Nexus switches in the lab rack.
 You have reset the running configuration of your Pod VDC to a baseline state.
 You have reset the running configuration of your Pod’s interfaces in your Pod N5K to a baseline
state.

Task 1: Configure Layer 2 and Layer 3 Interfaces

In this task, you will configure layer 2 and layer 3 interfaces between the switches in the Pod Pair.

Activity Procedure
Complete these steps:
Step 15 In your Pod VDC configure interface Ethernet 4/D as a Layer 3 interface.

vdcP# configure
Enter configuration commands, one per line. End with CNTL/Z.
vdcP(config)# interface Ethernet 3/D
vdcP(config-if)# ip address 192.168.JK.P/24
vdcP(config-if)# no shutdown

STOP! Wait until your Peer Pod has com pleted all steps up to this point before proceeding.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 33
©2016 NterOne Corporation
 Step 16 Confirm IP connectivity between your Pod VDC and your Peer Pod VDC.

vdcP(config-if)# ping 192.168.JK.Q

PING 192.168.JK.Q (192.168.JK.Q): 56 data bytes
36 bytes from 192.168.JK.Q: Destination Host Unreachable
Request 0 timed out
64 bytes from 192.168.JK.Q: icmp_seq=1 ttl=254 time=1.119 ms
64 bytes from 192.168.JK.Q: icmp_seq=2 ttl=254 time=0.648 ms
64 bytes from 192.168.JK.Q: icmp_seq=3 ttl=254 time=0.767 ms
64 bytes from 192.168.JK.Q: icmp_seq=4 ttl=254 time=0.802 ms

--- 192.168.JK.Q ping statistics ---

5 packets transmitted, 4 packets received, 20.00% packet loss
round-trip min/avg/max = 0.648/0.833/1.119 ms

Step 17 In your Pod VDC create a port-channel interface containing Ethernet 3/C.

vdcP(config-if)# feature lacp

vdcP(config)# interface ethernet 3/C
vdcP(config-if)# switchport
vdcP(config-if)# switchport mode trunk
vdcP(config-if)# spanning-tree port type network
vdcP(config-if)# channel-group JK mode active
vdcP(config-if)# no shutdown

Step 18 Verify the status of the port channel.

vdcP(config-if)# show port-channel summary

Flags: D - Down P - Up in port-channel (members)
I - Individual H - Hot-standby (LACP only)
s - Suspended r - Module-removed
S - Switched R - Routed
U - Up (port-channel)
M - Not in use. Min-links not met
--------------------------------------------------------------------------------
Group Port- Type Protocol Member Ports
Channel
--------------------------------------------------------------------------------
JK PoJK(SU) Eth LACP Eth3/C(P)

STOP! Wait until your peer pod has com pleted all steps up to this point before proceeding.

Step 19 Create an 802.1Q trunk between your Pod VDC and your Pod N5K.

vdcP(config)# interface ethernet 3/A

vdcP(config-if)# switchport
vdcP(config-if)# switchport mode trunk
vdcP(config-if)# spanning-tree port type network
vdcP(config-if)# no shutdown

N5K-X# configure
Enter configuration commands, one per line. End with CNTL/Z.
N5K-X(config)# interface ethernet 1/c
N5K-X(config-if)# switchport
N5K-X(config-if)# switchport mode trunk
N5K-X(config-if)# spanning-tree port type network
N5K-X(config-if)# no shutdown

Step 20 Create the following VLANs and SVIs on your Pod VDC (the correct VLANs and SVIs for
your Pod N5K are already configured as part of the lab baseline).

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 34
©2016 NterOne Corporation
 vdcP(config-if)# feature interface-vlan
vdcP(config)# vlan P0,Q0
vdcP(config-vlan)# interface vlan P0
vdcP(config-if)# ip address 172.16.P0.7P/24
vdcP(config-if)# no shutdown
vdcP(config-if)# interface vlan Q0
vdcP(config-if)# ip address 172.16.Q0.7P/24
vdcP(config-if)# no shutdown
vdcP(config-if)# end

STOP! Wait until your peer pod has com pleted all steps up to this point before proceeding.

Step 21 Use the show cdp neighbors command to verify that each of the interfaces on your Pod VDC
are connected to the correct devices and are enabled.

vdcP# 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, D - Remotely-Managed-Device,
s - Supports-STP-Dispute

Device-ID Local Intrfce Hldtme Capability Platform Port ID

N1-B2-SW1.ad.lab mgmt0 160 S I WS-C3560-48TS Fas0/??
N5K-X(SSI16420TRQ)
Eth3/A 175 R S I s N5K -C5548UP Eth1/?
vdcQ(JAF1651AMRJ) Eth3/C 157 R S I s N7K -C7004 Eth3/?
vdcQ(JAF1651AMRJ) Eth3/D 154 R S s N7K -C7004 Eth3/?

Total entries displayed: 4

Step 22 Use the show interface status command to view a summary of the status of each of the
interfaces on your Pod VDC.

vdcP# show interface status

--------------------------------------------------------------------------------
Port Name Status Vlan Duplex Speed Type
--------------------------------------------------------------------------------
mgmt0 -- connected routed full a-100 --
Eth3/A [from vdcP Eth connected trunk full a-1000 10/100/1000
Eth3/B [from vdcP Eth disabled routed auto auto 10/100/1000
Eth3/C [from vdcP Eth connected trunk full a-1000 10/100/1000
Eth3/D [from vdcP Eth connected routed full a-1000 10/100/1000
Eth4/A [from vdcP Eth disabled 1 auto auto SFP -H10GB-C
Eth4/B [from vdcP Eth disabled 1 auto auto SFP -H10GB-C
Eth4/C [from vdcP Eth disabled 1 auto auto SFP -H10GB-C
Eth4/D [from vdcP Eth dis abled 1 auto auto SFP -H10GB-C
PoJK -- connected trunk full a-1000 --
Vlan1 -- down routed auto auto --
VlanP0 -- connected routed auto auto --
VlanJK -- connected routed auto auto --
VlanQ0 -- connected routed auto auto --

Step 23 From your Pod VDC, verify that you can ping the VLAN P0 SVI interfaces on the N5K
switches (172.16.P0.5P and 172.16.P0.5Q).

vdcP# ping 172.16.P0.5P

PING 172.16.P0.5P (172.16.P0.5P): 56 data bytes
36 bytes from 172.16.10.7P: Destination Host Unreachable
Request 0 timed out

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 35
©2016 NterOne Corporation
 64 bytes from 172.16.P0.5P: icmp_seq=1 ttl=254 time=1.909 ms
64 bytes from 172.16.P0.5P: icmp_seq=2 ttl=254 time=2.107 ms
64 bytes from 172.16.P0.5P: icmp_seq=3 ttl=254 time=2.519 ms
64 bytes from 172.16.P0.5P: icmp_seq=4 ttl=254 time=2.373 ms

--- 172.16.P0.5P ping statistics ---

5 packets transmitted, 4 packets received, 20.00% packet loss
round-trip min/avg/max = 1.909/2.226/2.519 ms

vdcP# ping 172.16.P0.5Q

PING 172.16.P0.5Q (172.16.P0.5Q): 56 data bytes
36 bytes from 172.16.10.7P: Destination Host Unreachable
Request 0 timed out
64 bytes from 172.16.P0.5Q: icmp_seq=1 ttl=254 time=1.708 ms
64 bytes from 172.16.P0.5Q: icmp_seq=2 ttl=254 time=2.132 ms
64 bytes from 172.16.P0.5Q: icmp_seq=3 ttl=254 time=2.512 ms
64 bytes from 172.16.P0.5Q: icmp_seq=4 ttl=254 time=2.321 ms

--- 172.16.P0.5Q ping statistics ---

5 packets transmitted, 4 packets re ceived, 20.00% packet loss
round-trip min/avg/max = 1.708/2.168/2.512 ms

Activity Verification
You have completed this task when you attain these results:
 You have successfully created a layer 3 connection between your Pod VDC and your Peer Pod VDC
 You have successfully created a layer 2 trunk between your Pod VDC and your Pod N5K.
 You have successfully created VLANs and SVI interfaces associated with those VLANs .

Task 2: Verify VLAN and VLAN Membership

In this task, you will use CLI commands to verify the VLAN database and membership.

Activity Procedure
Complete these steps:
Step 24 On both your Pod VDC identify what types of VLANs are currently configured by entering the
show vlan summary command.

vdcP# show vlan summary

Number of existing VLANs : 4

Number of existing user VLANs : 4
Number of existing extended VLANs : 0

Step 25 Use the show vlan brief command to find out which interfaces are members of each VLAN.

vdcP# show vlan brief

VLAN Name Status Ports

---- -------------------------------- --------- -------------------------------
1 default active PoJK, Eth3/A, Eth3/C, Eth4/A
Eth4/B, Eth4/C, Eth4/D
P0 VLAN00P0 active PoJK, Eth3/A, Eth3/C
JK VLAN00JK active PoJK, Eth3/A, Eth3/C
Q0 VLAN00Q0 active PoJK, Eth3/A, Eth3/C

Q16) Are there any interfaces that are members of multiple VLANs?

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 36
©2016 NterOne Corporation
 Q17) What is the reason for this?

Activity Verification
You have completed this task when you attain these results:
 You have successfully identified which VLANs have been configured and which interfaces are
members of which VLAN.
 You have correctly identified why some interfaces are members of multiple VLANs.

Task 3: Verify Interface States

In this task, you will use CLI commands to verify the interface states.

Activity Procedure
Complete these steps:
Step 26 The show interface brief command is used to provide a summary state of all interfaces on the
switch. Run the show interface brief command on your Pod VDC.

vdcP# show interface brief

--------------------------------------------------------------------------------
Port VRF Status IP Address Speed MTU
--------------------------------------------------------------------------------
mgmt0 -- up 10.0.0.??? 100 1500

--------------------------------------------------------------------------------
Ethernet VLAN Type Mode Status Reason Speed Port
Interface Ch #
--------------------------------------------------------------------------------
Eth3/A 1 eth trunk up none 1000(D) --
Eth3/B -- eth routed down Administratively down auto(D) --
Eth3/C 1 eth trunk up none 1000(D) JK
Eth3/D -- eth routed up none 1000(D) --
Eth4/A 1 eth access down Administratively down auto(D) --
Eth4/B 1 eth access down Administratively down auto(D) --
Eth4/C 1 eth access down Administratively down auto(D) --
Eth4/D 1 eth access down Administratively down auto(D) --

--------------------------------------------------------------------------------
Port-channel VLAN Type Mode Status Reason Speed Protocol
Interface
--------------------------------------------------------------------------------
PoJK 1 eth trunk up none a -1000(D) lacp

-------------------------------------------------------------------------------
Interface Secondary VLAN(Type) Status Reason
-------------------------------------------------------------------------------
Vlan1 -- down Administratively down
VlanP0 -- up --
VlanJK -- up --
VlanQ0 -- up --

Q18) What is the default mode for interfaces on your Pod VDC?

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 37
©2016 NterOne Corporation
 Q19) When were these default modes set?

Step 27 Some of the interfaces on the switches are set as trunk interfaces. On your Pod VDC check
whether any of these interfaces have any VLAN errors disabled on the trunk using the
command show interface trunk.

vdcP# show interface trunk

--------------------------------------------------------------------------------
Port Native Status Port
Vlan Channel
--------------------------------------------------------------------------------
Eth3/A 1 trunking --
Eth3/C 1 trnk-bndl PoJK
PoJK 1 trunking --

------------------------------------------------------- -------------------------
Port Vlans Allowed on Trunk
--------------------------------------------------------------------------------
Eth3/A 1-4094
Eth3/C 1-4094
PoJK 1-4094

------------------------------------------------ --------------------------------
Port Vlans Err-disabled on Trunk
--------------------------------------------------------------------------------
Eth3/A none
Eth3/C none
PoJK none

--------------------------------------------------------------------------------
Port STP Forwarding
--------------------------------------------------------------------------------
Eth3/A none
Eth3/C none
PoJK none

------------------------------------------------- -------------------------------
Port Vlans in spanning tree forwarding state and not pruned
--------------------------------------------------------------------------------
Eth3/A none
Eth3/C none
PoJK none

--------------------------------------------------------------------------------
Port Vlans Forwarding on FabricPath
--------------------------------------------------------------------------------
Eth3/A none
Eth3/C none
PoJK none

Q20) Were there any VLANs disabled on your Pod VDC?

Activity Verification
You have completed this task when you attain these results:
 You have successfully verified the state of the interfaces.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 38
©2016 NterOne Corporation
  You have successfully verified there are no error-disabled VLANs on the trunk interfaces.

Task 4: Verify the MAC Address Table

In this task, you will use CLI commands to verify the MAC address table.

Activity Procedure
Complete these steps:
Step 28 As MAC addresses are discovered, they are put into a MAC address table. Use the following
command to identify which MAC addresses are currently in the table on your Pod VDC: show
mac address-table.

Note Your output may not match the lab guide output exactly.

vdcP# show mac address-table

Note: MAC table entries displayed are getting read from software.
Use the 'hardware-age' keyword to get information related to 'Age'

Legend:
* - primary entry, G - Gateway MAC, (R) - Routed MAC, O - Overlay MAC
age - seconds since last seen,+ - primary entry using vPC Peer-Link, E -
EVPN entry
(T) - True, (F) - False , ~~~ - use 'hardware-age' keyword to retrieve age
info
VLAN/BD MAC Address Type age Secure NTFY Ports/SWID.SSID.LID
---------+-----------------+--------+---------+------+----+------------------
G - 8478.ac57.9642 static - F F sup-eth1(R)
G P0 8478.ac57.9642 static - F F sup-eth1(R)
G JK 8478.ac57.9642 static - F F sup-eth1(R)
G Q0 8478.ac57.9642 static - F F sup-eth1(R)
* P0 002a.6a0f.7181 dynamic ~~~ F F PoJK
* P0 0050.56b0.ee43 dynamic ~~~ F F Eth3/A
* P0 547f.eef7.6bfc dynamic ~~~ F F Eth3/A
* JK 0050.56b0.af55 dynamic ~~~ F F Eth3/A
* JK 0050.56b0.c396 dynamic ~~~ F F PoJK
* Q0 0050.56b0.095c dynamic ~~~ F F PoJK

Step 29 Using the show mac address-table aging-time command, find out the aging time for entries in
the MAC address table.

vdcP# show mac address-table aging-time

Vlan Aging Time
---- ----------
1 1800
P0 1800
JK 1800
Q0 1800

Q21) What is the aging time value?

Q22) We have no Cisco FabricPath configured. Using the show mac address-table learning-mode
command, what is the learning mode for MAC addresses on the Pod VDC?

vdcP# show mac address-table learning-mode

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 39
©2016 NterOne Corporation
 Vlan Learning Mode
---- ----------
1 Non-Conversational-Learning
P0 Non-Conversational-Learning
JK Non-Conversational-Learning
Q0 Non-Conversational-Learning

Activity Verification
You have completed this task when you attain these results:
 You have successfully verified the MAC address table.
 You have successfully identified the learning mode for MAC addresses.
 You have successfully identified how MAC addresses have been discovered.

Task 5: Verify the Cisco NX-OS Software

In this task, you will use CLI commands to verify the Cisco NX-OS version.

Activity Procedure
Complete these steps:
Step 30 The show version command shows you which version of software you are running currently on
the switch. Use the show version command to answer the following questions (the following
output is an example of the output you will see on the switches):

Note Your output may not match the lab guide output exactly.

vdcP# show version

Cisco Nexus Operating System (NX-OS) Software
TAC support: http://www.cisco.com/tac
Documents:
http://www.cisco.com/en/US/products/ps9372/tsd_products_support_series_home.html
Copyright (c) 2002-2015, Cisco Systems, Inc. All rights reserved.
The copyrights to certain works contained in this software are
owned by other third parties and used and distributed under
license. Certain components of this software are licensed under
the GNU General Public License (GPL) version 2.0 or the GNU
Lesser General Public License (LGPL) Version 2.1. A copy of each
such license is available at
http://www.opensource.org/licenses/gpl-2.0.php and
http://www.opensource.org/licenses/lgpl -2.1.php

Software
BIOS: version 2.12.0
kickstart: version 7.2(1)D1(1)
system: version 7.2(1)D1(1)
BIOS compile time: 05/29/2013
kickstart image file is: bootflash:// /n7000-s2-kickstart.7.2.1.D1.1.bin
kickstart compile time: 10/8/2015 15:00:00 [10/24/2015 05:44:18]
system image file is: bootflash:///n7000 -s2-dk9.7.2.1.D1.1.bin
system compile time: 10/8/2015 15:00:00 [10/24/2015 07:38:15]

Hardware
cisco Nexus7000 C7004 (4 Slot) Chassis ("Supervisor Module -2")
Intel(R) Xeon(R) CPU with 32744992 kB of memory.
Processor Board ID JAF1652ANGS

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 40
©2016 NterOne Corporation
 Device name: vdc1
bootflash: 2007040 kB
slot0: 0 kB (expansion flash)

Kernel uptime is 17 day(s), 14 hour(s), 15 minute(s), 14 second(s)

Last reset at 66877 usecs after Fri Sep 3 09:08:14 2010

Reason: Reset Requested by CLI command reload

System version: 7.2(1)D1(1)
Service:

plugin
Core Plugin, Ethernet Plugin

Active Package(s)

Q23) Which version of the kickstart image is running on each of the four switches?

Q24) Which version of the system image is running on each of the four switches?

Q25) Are you running the same version of kickstart and system image on the switches?

Q26) Are you running the same version of software on both of your Pod Switches?

Q27) How long has the switch been operating?

Q28) What is the reason for the last switch reset?

Activity Verification
You have completed this task when you attain this result:
 You have successfully verified the Cisco NX-OS software image that is being used.

Task 6: Verify the Running and Startup Configuration

In this task, you will use CLI commands to verify the running and startup configuration.

Activity Procedure
Complete these steps:
Step 31 The show running-config command is used to show the running configuration. Use the
command to see what your current configuration looks like.
Q29) Use the show startup-config command to see the configurations. Are the running and startup
configurations the same?

Q30) If they were different, which command would you use to save the running configuration to the
startup configuration?

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 41
©2016 NterOne Corporation
 Step 32 The show running-config interface mgmt0 all command shows you additional configuration
for the mgmt0 interface.

vdcP# show running-config interface mgmt0 all

!Command: show running-config interface mgmt0 all

!Time: Mon Sep 20 23:25:45 2010

version 7.2(1)D1(1)

interface mgmt0
no description
speed auto
duplex auto
no shutdown
cdp enable
spanning-tree port-priority 128
spanning-tree cost auto
spanning-tree link-type auto
no spanning-tree bpduguard
no spanning-tree bpdufilter
vrf member management
ip address 10.0.0.???/24

Q31) When you add the all parameter to the show running–config <feature> command, what additional
configuration is actually being displayed?

Step 33 To be able to configure the interface-vlan feature, you would have had to enable the feature.
Use the show feature command on your Pod VDC to find out what other additional features are
available for you to configure.

vdcP# show feature

Feature Name Instance State
-------------------- -------- --------
bfd 1 disabled
bfd_app 1 disabled
bgp 1 disabled
cts 1 disabled
dhcp 1 disabled
dot1x 1 disabled
eigrp 1 disabled
eigrp 2 disabled
eigrp 3 disabled
eigrp 4 disabled
eth_port_sec 1 disabled
glbp 1 disabled
hsrp_engine 1 disabled
interface-vlan 1 enabled
isis 1 disabled
<…output omitted…>

Step 34 Use the same command on your Pod N5K. Are you running the same features?

N5K-X# show feature

Feature Name Instance State
-------------------- -------- --------
Flexlink 1 disabled
amt 1 disabled

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 42
©2016 NterOne Corporation
 bgp 1 disabled
cts 1 disabled
dhcp 1 disabled
dot1x 1 disabled
eigrp 1 disabled
eigrp 2 disabled
eigrp 3 disabled
eigrp 4 disabled
eth_port_sec 1 disabled
fcoe 1 disabled
fcoe-npv 1 disabled
fex 1 disabled
glbp 1 disabled
hsrp_engine 1 disabled
http-server 1 disabled
interface-vlan 1 enabled
<…output omitted…>

Activity Verification
You have completed this task when you attain these results:
 You have successfully verified the configuration that is being used in running and startup
configuration.
 You have successfully verified which features are currently enabled on both Pod Switches.

Task 7: Use the tech-support Command

In this task, you will use CLI commands to view the tech-support command output.

Activity Procedure
Complete these steps:
Step 35 The show tech-support command provides you with valuable information about the switch, and
the output is often provided to Cisco TAC so that they have a complete picture of the switch that
is having problems.
Step 36 Run the show tech-support command on your Pod N5K.
Step 37 Run the show tech-support command on your Pod VDC.
Step 38 As you can see, there is a large amount of data to view. If you are looking for specific
information, you can pull out the tech support details for a specific feature.
Step 39 For example, run the show tech-support vpc on your Pod VDC. There is still a large amount of
data, but it is now focused on a specific feature you may be having issues with.
Step 40 It is often necessary to send this output to Cisco TAC, or you may wish to analyze the
information offline. To be able to do this analysis, you can send the output to a file, which can
then be copied to a TFTP server.
Step 41 Run the show tech-support > volatile:tech command. In this command, you are sending the
output of the command to a file called tech, which is being stored in volatile memory.

Activity Verification
You have completed this task when you attain this result:
 You have successfully run and viewed the output from the show tech-support command.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 43
©2016 NterOne Corporation
Lab 4: Configuring vPC
Complete this lab activity to practice what you learned in the related module.

Activity Objective
In this activity, you will configure a vPC between the Pod Pair VDCs. After completing this activity, you will
be able to meet these objectives:
 Configure the vPC domain ID
 Configure the vPC keepalive link between the Nexus 7000 VDCs
 Configure the vPC peer link between the Nexus 7000 VDCs
 Configure and optimize the vPC

Command List
The table describes the commands that are used in this activity.
Com m and Description
channel-group nr This command adds an interface to a port channel.
This command adds an interface to a port channel that is
channel-group nr mode active
dynamically negotiated through LACP.
feature lacp This command enables the use of LACP
feature vpc This command enables the vPC feature.
peer-keepalive destination vpc-peer-ip- This command enables the vPC peer keepalive link to the
address vPC peer IP address.

ping ip-address vrf vrf This command verifies IP connectivity to an IP address in a

VRF using ICMP echo messages.
This command displays summarized status information for
show interface intf brief
an interface.

show lacp neighbor This command displays a list of LACP neighbors and their
operational parameters.
show license usage This command displays the usage of licensed features.

show port-channel summary This command displays a summarized view of port-channel

operation.
This command displays the current configuration for an
show running-config intf
interface.
show spanning-tree This command displays information that is related to STP.
show vpc This command displays the vPC operational parameters.
show vpc brief This command displays a brief overview of vPC status.
show vpc consistency-parameters global This command displays global vPC consistency status.

show vpc peer-keepalive This command displays status information for the vPC peer
keepalive link.
vpc nr This command adds a port-channel interface to a vPC.
vpc domain nr This command creates a vPC domain.

vpc peer-link This command defines a port-channel interface as the vPC

peer link.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 44
©2016 NterOne Corporation
Task 0: Lab Preparation
In this task, you will perform the steps necessary to get ready for performing the subsequent tasks in this lab
exercise.

Activity Procedure
Complete these steps:
Step 1 Make sure that you know the value of your Pod Number. Your Pod Number is assigned to you
by your instructor and is used to identify the lab devices that you will use during this lab
exercise. Refer to the following table when a task step in this lab exercise uses a letter variable.

Your
Your Your Your
Assigned Value of Value of Value of Value of Value of
Pod VDC Peer Pod Pod N5K “P” “Q” “JK” “X” “Y”
Pod
Nam e VDC Nam e Nam e
Num ber
1 vdc1 vdc2 N5K-A 1 2 12 A B
2 vdc2 vdc1 N5K-B 2 1 12 B A
3 vdc3 vdc4 N5K-A 3 4 34 A B
4 vdc4 vdc3 N5K-B 4 3 34 B A
5 vdc5 vdc6 N5K-A 5 6 56 A B
6 vdc6 vdc5 N5K-B 6 5 56 B A
7 vdc7 vdc8 N5K-A 7 8 78 A B
8 vdc8 vdc7 N5K-B 8 7 78 B A

Your
Assigned Value of Value of Value of Value of Value of Value of Value of Value of
“A” “B” “C” “D” “a” “b” “c” “d”
Pod Num ber
1 1 2 3 4 1 2 17 18
2 5 6 7 8 2 1 18 17
3 9 10 11 12 3 4 19 20
4 13 14 15 16 4 3 20 19
5 17 18 19 20 5 6 21 22
6 21 22 23 24 6 5 22 21
7 25 26 27 28 7 8 23 24
8 29 30 31 32 8 7 24 23

Step 2 Make sure that you know the value of your Rack Number. Your Rack Number is assigned to
you by your instructor and is used to identify the Nexus 7000 rack of devices that you will use
during this lab exercise.
Step 3 Your assigned Pod is one of two Pods within a Pod Pair. The details of each Pod Pair, including
diagrams and tables of related values, are contained in one of several NterOne Resource Guide
documents. Open the NterOne Resource Guide that corresponds to your assigned Pod Number.
Step 4 Locate the various tables that provide additional information about your assigned Pod, which
include details such as IP addresses and device login credentials.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 45
©2016 NterOne Corporation
 Step 5 Locate the diagram that corresponds to this lab exercise. This diagram may help you visualize
the intended goal of this lab exercise.

Task 0.1: Log In to your Student Server and Connect to Lab Devices
During this task you will log in to your assigned Student Server and use PuTTY to start SSH sessions to each
of the devices that you will use during this lab exercise.

Activity Procedure
Complete these steps:
Step 6 Verify that you are currently logged in to your Student Server.
Step 7 From your Student Server desktop use the PuTTY application to open SSH sessions to each of
the devices in the following table (there may be preconfigured shortcuts to these devices on the
Student Server desktop).

Note * You w ill need to get the passw ords for the Nexus sw itches from your instructor.

Note Make sure to use the IP address that corresponds to your assigned Rack Number .

Device Nam e Device Description IP Address Username Passw ord

vdcP Your Pod Nexus 7004 VDC Rack 1 – 10.0.0.8P admin *

(Pod VDC) Rack 2 – 10.0.0.18P
Your Peer Pod Nexus 7004 VDC Rack 1 – 10.0.0.8Q
vdcQ admin *
(Peer Pod VDC) Rack 2 – 10.0.0.18Q

N5K-A Nexus 5548UP Sw itch managed by Rack 1 – 10.0.0.78 podP *

odd-numbered Pods Rack 2 – 10.0.0.178
Nexus 5548UP Sw itch managed by Rack 1 – 10.0.0.79
N5K-B podP *
even-numbered Pods Rack 2 – 10.0.0.179

Note It is suggested that you arrange the PuTTY w indow s in a rectangle in a similar arrangement as
the sw itches in the lab diagram in the Resource Guide.

Task 0.2: Reset the Configuration of your Pod VDC

In order to ensure that the steps in this lab exercise function properly the running configuration of your Pod
VDC must be reset to the baseline configuration. During this task you will reset the configuration of your
Pod VDC to the baseline state.

Activity Procedure
Complete these steps:
Step 8 Switch to the PuTTY session to your Pod VDC (vdcP).
Step 9 You will be using the NX-OS checkpoint function to reset the configuration of the VDC to a
baseline state, which removes the configuration created in a previous lab exercise. Execute the
following command to roll back the configuration:
rollback running-config file bootflash:baseline best-effort

vdcP# rollback running-config file bootflash:baseline best-effort

Collecting Running-Config
#Generating Rollback Patch
Executing Rollback Patch

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 46
©2016 NterOne Corporation
 Rollback completed successfully.

Step 10 Execute the show running-config command. You should see that all of the physical interfaces
now only have a description and there are no commands present from the previous lab exercise.
Step 11 Execute the show running-config ip command. The baseline configuration contains three
VLAN interfaces; each VLAN interface should have an IP address assigned to it.

Note If any of the VLAN interfaces do NOT have an IP address, repeat the rollback command in
Step 9. In some cases the rollback does not reset all of the configuration.

vdcP# show running-config ip

!Command: show running-config ip

!Time: Tue Jun 10 14:34:05 2014

version 7.2(1)D1(1)
vrf context management
ip route 0.0.0.0/0 10.0.0.1

interface VlanP0
ip address 172.16.P0.7P/24

interface VlanJK
ip address 172.16.JK.7P/24

interface VlanQ0
ip address 172.16.Q0.7P/24

interface mgmt0
ip address 10.0.0.xxx/24

vdcP#

Task 0.3: Reset the Configuration of your Pod N5K

In order to ensure that the steps in this lab exercise function properly the running configuration of your Pod
N5K must be reset to the baseline configuration. During this task you will reset the configuration of your Pod
N5K to the baseline state for the portions of the overall switch configuration that are managed by your Pod.

Activity Procedure
Complete these steps:
Step 12 Switch to the PuTTY session to your Pod N5K (N5K-X).
Step 13 Reset the running configuration of your Pod to the baseline state by entering the
run-script baseline command (where “P” is your Pod Number).

N5K-A# run-script resetpodP

`configure
`default interface Ethernet1/P-Q
<… output omitted …>
`end

Step 14 Execute the show running-config interface Ethernet 1/P-Q command (where “P” is your Pod
Number and “Q” is your Peer Pod Number). You should see that these interfaces now only have
a description and there are no commands present from the previous lab exercise.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 47
©2016 NterOne Corporation
 N5K-X# show running-config interface ethernet 1/P-Q

!Command: show running-config interface Ethernet1/P-Q

!Time: Mon Jul 4 11:57:15 2016

version 7.3(0)N1(1)

interface Ethernet1/P
description [from N5K-X Eth 1/P (1/a) to vdcP Eth 4/?]

interface Ethernet1/Q
description [from N5K-X Eth 1/Q (1/b) to vdcQ Eth 4/?]

Activity Verification
You have completed this activity when you have achieved these goals:
 You have made a successful connection to your Student Server.
 You have successfully used PuTTY to connect to the Nexus switches in the lab rack.
 You have reset the running configuration of your Pod VDC to a baseline state.
 You have reset the running configuration of your Pod’s interfaces in your Pod N5K to a baseline
state.

Task 1: Configure the vPC Domain

In this task, you will create and configure the vPC domain.

Activity Procedure
Complete these steps:
Step 15 On your Pod VDC, enable the vPC feature.

vdcP# configure
Enter configuration commands, one per line. End with CNTL/Z.
vdcP(config)# feature vpc

Step 16 Configure your vPC domain identifier as JK (where “JK” is your Pod Pair Number).

vdcP(config)# vpc domain JK

vdcP(config-vpc-domain)# show vpc
Legend:
(*) - local vPC is down, forwarding via vPC peer -link

vPC domain id : JK
Peer status : peer link not configured
vPC keep-alive status : Disabled
Configuration consistency status : failed
Per-vlan consistency status : failed
Configuration inconsistency reason: vPC peer -link does not exist
Type-2 consistency status : failed
Type-2 inconsistency reason : vPC peer -link does not exist
vPC role : none established
Number of vPCs configured : 0
Peer Gateway : Disabled
Dual-active excluded VLANs : -
Graceful Consistency Check : Disabled (due to peer configuration)
Auto-recovery status : Disabled

Activity Verification

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 48
©2016 NterOne Corporation
 You have completed this task when you attain these results:
 You have used the show commands on your Pod VDC to verify that the vPC domain ID is
configured correctly.

Task 2: Configure the vPC Keepalive Link

In this task, you will configure the vPC keepalive link between the Pod Pair VDCs.

Activity Procedure
Complete these steps:
Step 17 On your Pod VDC configure interface Ethernet 3/D as a Layer 3 port. This will be the peer
keepalive-link between the two VDC’s in your pod pair.

vdcP(config-vpc-domain)# interface Ethernet 3/D

vdcP(config-if)# ip address 192.168.JK.P/24
vdcP(config-if)# no shutdown

STOP! Wait until your Peer Pod has com pleted all steps up to this point before proceeding.

Step 18 Confirm IP connectivity between your Pod VDC and your Peer Pod VDC. You may have to
wait for them to catch up to the same step.

vdcP(config-if)# ping 192.168.JK.Q

PING 192.168.JK.Q (192.168.JK.Q): 56 data bytes
36 bytes from 192.168.JK.Q: Destination Host Unreachable
Request 0 timed out
64 bytes from 192.168.JK.Q: icmp_seq=1 ttl=254 time=1.119 ms
64 bytes from 192.168.JK.Q: icmp_seq=2 ttl=254 time=0.648 ms
64 bytes from 192.168.JK.Q: icmp_seq=3 ttl=254 time=0.767 ms
64 bytes from 192.168.JK.Q: icmp_seq=4 ttl=254 time=0.802 ms

--- 192.168.JK.Q ping statistics ---

5 packets transmitted, 4 packets received, 20.00% packet loss
round-trip min/avg/max = 0.648/0.833/1.119 ms

Step 19 Create a VRF context for the peer keepalive link and allocate the interface to it. You will need
to reconfigure the IP address after the interface has been allocated to this VRF.

vdcP(config-if)# vrf context vpc

vdcP(config-vrf)# interface Ethernet 4/D
vdcP(config-if)# vrf member vpc
% Deleted all L3 config on interface Ethernet4/D
vdcP(config-if)# ip address 192.168.JK.P/24

Step 20 Verify that your Pod VDC can reach your Peer Pod’s VLAN JK IP address.

STOP! Wait until your Peer Pod has com pleted all steps up to this po int before proceeding.

vdcP(config-if)# ping 192.168.JK.Q vrf vpc

PING 192.168.JK.Q (192.168.JK.Q): 56 data bytes
36 bytes from 192.168.JK.Q: Destination Host Unreachable
Request 0 timed out
64 bytes from 192.168.JK.Q: icmp_seq=1 ttl=254 time=0.763 ms
64 bytes from 192.168.JK.Q: icmp_seq=2 ttl=254 time=0.732 ms
64 bytes from 192.168.JK.Q: icmp_seq=3 ttl=254 time=0.704 ms
64 bytes from 192.168.JK.Q: icmp_seq=4 ttl=254 time=0.79 ms

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 49
©2016 NterOne Corporation
 --- 192.168.JK.Q ping statistics ---
5 packets transmitted, 4 packets receiv ed, 20.00% packet loss
round-trip min/avg/max = 0.704/0.747/0.79 ms

Step 21 Configure the vPC keepalive link destination as your peer’s VDC IP address.

vdcP(config) vpc domain JK

vdcP(config-vpc-domain)# peer-keepalive destination 192.168.JK.Q source
192.168.JK.P vrf vpc

STOP! Wait until your Peer Pod has com pleted all steps up to this point before proceeding.

Step 22 Confirm the status of the vPC peer configuration.

vdcP(config-vpc-domain)# show vpc

Legend:
(*) - local vPC is down, forwarding via vPC peer-link

vPC domain id : JK
Peer status : peer link not configured
vPC keep-alive status : peer is alive
Configuration consistency status : failed
Configuration inconsistency reason: vPC peer-link does not exist
Per-vlan consistency status : failed
Type-2 consistency status : failed
Type-2 inconsistency reason : vPC peer -link does not exist
vPC role : none established
Number of vPCs configured : 0
Peer Gateway : Disabled
Dual-active excluded VLANs : -
Graceful Consistency Check : Enabled
Auto-recovery status : Enabled (timeout = 240 seconds)

Step 23 Check the vPC keepalive link. Do not continue to the next task before you verify that the vPC
peer keepalive status is alive.

vdcP(config-vpc-domain)# show vpc peer-keepalive

vPC keep-alive status : peer is alive

--Peer is alive for : (284) seconds, (374) msec
--Send status : Success
--Last send at : 2014.06.05 13:50:39 395 ms
--Sent on interface : Eth3/D
--Receive status : Success
--Last receive at : 2014.06.05 13:50:38 585 ms
--Received on interface : Eth3/D
--Last update from peer : (0) seconds, (935) msec

vPC Keep-alive parameters

--Destination : 192.168.JK.Q
--Keepalive interval : 1000 msec
--Keepalive timeout : 5 seconds
--Keepalive hold timeout : 3 seconds
--Keepalive vrf : vpc
--Keepalive udp port : 3200
--Keepalive tos : 192

Activity Verification

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 50
©2016 NterOne Corporation
 You have completed this task when you attain these results:
 You have used the show commands to verify that the vPC keepalive link is up.

Task 3: Configure the vPC Peer Link

In this task, you will configure the vPC peer link between the Pod Pair VDCs.

Activity Procedure
Complete these steps:
Step 24 On your Pod VDC create a port-channel interface containing Ethernet 4/C.

vdcP(config-vpc-domain)# feature lacp

vdcP(config)# interface ethernet 4/C
vdcP(config-if)# switchport mode trunk
vdcP(config-if)# switchport trunk allowed vlan P0,Q0
vdcP(config-if)# spanning-tree port type network
vdcP(config-if)# channel-group JK mode active
vdcP(config-if)# no shutdown

Step 25 Verify the port channel status.

vdcP(config-if)# show port-channel summary

Flags: D - Down P - Up in port-channel (members)
I - Individual H - Hot-standby (LACP only)
s - Suspended r - Module-removed
S - Switched R - Routed
U - Up (port-channel)
M - Not in use. Min-links not met
--------------------------------------------------------------------------------
Group Port- Type Protocol Member Ports
Channel
--------------------------------------------------------------------------------
JK PoJK(SU) Eth LACP Eth4/C( P)

STOP! Wait until your peer pod has com pleted all steps up to this point before proceeding.

Step 26 Make this port channel your vPC peer link.

vdcP(config-if)# interface port-channel JK

vdcP(config-if)# vpc peer-link
Please note that spanning tree port type is changed to "network" port type on vPC
peer-link.
This will enable spanning tree Bridge Assurance on vPC peer-link provided the STP
Bridge Assurance
(which is enabled by default) is not disabled.

STOP! Wait until your peer pod has com pleted all steps up to this point before proceeding.

Step 27 Check the global vPC consistency parameters.

vdcP(config-if)# show vpc consistency-parameters global

Legend:
Type 1 : vPC will be suspended in case of mismatch

Name Type Local Value Peer Value

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 51
©2016 NterOne Corporation
 ------------- ---- ---------------------- -----------------------
STP Mode 1 Rapid -PVST Rapid-PVST
STP Disabled 1 None None
STP MST Region Name 1 "" ""
STP MST Region Revision 1 0 0
STP MST Region Instance to 1
VLAN Mapping
STP Loopguard 1 Disabled Disabled
STP Bridge Assurance 1 Enabled Enabled
STP Port Type, Edge 1 Normal, Disabled, Normal, Disabled,
BPDUFilter, Edge BPDUGuard Disabled Disabled
STP MST Simulate PVST 1 Enabled Enabled
Interface-vlan admin up 2 P0,Q0 P0,Q0
Interface-vlan routing 2 P0,Q0 P0,Q0
capability
Allowed VLANs - P0,Q0 P0,Q0
Local error VLANs - - -

Step 28 Check the vPC status.

vdcP(config-if)# show vpc

Legend:
(*) - local vPC is down, forwarding via v PC peer-link

vPC domain id : JK
Peer status : peer adjacency formed ok
vPC keep-alive status : peer is alive
Configuration consistency status : success
Per-vlan consistency status : success
Type-2 consistency status : success
vPC role : primary
Number of vPCs configured : 0
Peer Gateway : Disabled
Dual-active excluded VLANs : -
Graceful Consistency Check : Enabled
Auto-recovery status : Enabled (timeout = 240 seconds)

vPC Peer-link status

---------------------------------------------------------------------
id Port Status Active vlans
-- ---- ------ --------------------------------------------------
1 PoJK up P0,Q0

Activity Verification
You have completed this task when you attain these results:
 You have used the show commands to verify that the vPC peer link is up and the VPC status is OK.

Task 4: vPC Configuration and Optimization

In this task, you will configure the vPC between the Pod VDCs and the Pod N5Ks.

Activity Procedure
Complete these steps:
Step 29 On your Pod N5K create a port channel and add both uplink ports that go to your Pod VDC and
your Peer Pod VDC.

N5K-X(config)# no interface port-channel P

N5K-X(config)# interface ethernet 1/a-b

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 52
©2016 NterOne Corporation
 N5K-X(config-if-range)# switchport mode trunk
N5K-X(config-if-range)# spanning-tree port type network
N5K-X(config-if-range)# channel-group P mode active
N5K-X(config-if-range)# no shutdown

Step 30 Check the state of the port channel. You should see that the port channel has been created but is
in the down state.

N5K-X(config-if-range)# show port-channel summary

Flags: D - Down P - Up in port-channel (members)
I - Individual H - Hot-standby (LACP only)
s - Suspended r - Module-removed
S - Switched R - Routed
U - Up (port-channel)
M - Not in use. Min-links not met
--------------------------------------------------------------------------------
Group Port- Type Protocol Member Ports
Channel
--------------------------------------------------------------------------------
P PoP(SD) Eth LACP Eth1/a(D) Eth1/b (D)
Q PoQ(SD) Eth NONE --
JK PoJK(SD) Eth NONE --

Step 31 Create two port channels in your Pod VDC, one going to each N5K switch (where “P” is your
Pod number and “Q” is your Peer Pod number).

vdcP(config)# interface ethernet 4/A

vdcP(config-if)# switchport mode trunk
vdcP(config-if)# spanning-tree port type network
vdcP(config-if)# channel-group P mode active
vdcP(config-if)# no shutdown
vdcP(config-if)# interface ethernet 4/B
vdcP(config-if)# switchport
vdcP(config-if)# switchport mode trunk
vdcP(config-if)# spanning-tree port type network
vdcP(config-if)# channel-group Q mode active
vdcP(config-if)# no shutdown

Step 32 Configure vPC IDs on the port channel interfaces. Keep the vPC ID number the same as the
port channel number. Although it can be any value, the values must match on the vPC peer (the
Peer Pod VDC). For simplicity, it is recommended to keep the values simple to make
troubleshooting easier.

vdcP(config-if)# interface port-channel P

vdcP(config-if)# vpc P
vdcP(config-if)# interface port-channel Q
vdcP(config-if)# vpc Q

STOP! Wait until your peer pod has com pleted all steps up to this point before proceeding.

Step 33 Check the vPC status and consistency parameters for your vPC.

vdcP(config-if)# show vpc

Legend:
(*) - local vPC is down, forwarding via vPC peer -link

vPC domain id : JK
Peer status : peer adjacency formed ok
vPC keep-alive status : peer is alive

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 53
©2016 NterOne Corporation
 Configuration consistency status : success
Per-vlan consistency status : success
Type-2 consistency status : success
vPC role : primary
Number of vPCs configured : 2
Peer Gateway : Disabled
Dual-active excluded VLANs : -
Graceful Consistency Check : Enabled
Auto-recovery status : Enabled (timeout = 240 seconds)

vPC Peer-link status

---------------------------------------------------------------------
id Port Status Active vlans
-- ---- ------ --------------------------------------------------
1 PoJK up P0,Q0

vPC status
----------------------------------------------------------------------
id Port Status Consistency Reason Active vlans
-- ---- ------ ----------- ------ ------------
P PoP up success success P0,Q0
Q PoQ up success success P0,Q0

Step 34 Check the port channel status on your Pod N5K.

N5K-X(config-if-range)# show port-channel summary

Flags: D - Down P - Up in port-channel (members)
I - Individual H - Hot-standby (LACP only)
s - Suspended r - Module-removed
S - Switched R - Routed
U - Up (port-channel)
M - Not in use. Min-links not met
--------------------------------------------------------------------------------
Group Port- Type Protocol Member Ports
Channel
--------------------------------------------------------------------------------
P PoP(SU) Eth LACP Eth1/a(P) Eth1/b(P)
Q PoQ(SD) Eth NONE --
JK PoJK(SD) Eth NONE --

Step 35 Configure the peer switch feature on your Pod VDC. Ensure that your Peer Pod VDC has also
completed this configuration.

vdcP(config)# vpc domain JK

vdcP(config-vpc-domain)# peer-switch

Step 36 Ensure that the interfaces are operational and confirm connectivity between the Pod N5K and
your Pod VDC.

N5K-X(config-if)# ping 172.16.P0.7P source 172.16.P0.5P

PING 172.16.P0.5P (172.16.P0.7P) from 172.16.P0.5P: 56 data bytes
64 bytes from 172.16.P0.7P: icmp_seq=0 ttl= 254 time=1.316 ms
64 bytes from 172.16.P0.7P: icmp_seq=1 ttl=254 time=0.865 ms
64 bytes from 172.16.P0.7P: icmp_seq=2 ttl=254 time=1.007 ms
64 bytes from 172.16.P0.7P: icmp_seq=3 ttl=254 time=7.161 ms
64 bytes from 172.16.P0.7P: icmp_seq=4 ttl=254 time=9.5 86 ms

--- 172.16.P0.7P ping statistics ---

5 packets transmitted, 5 packets received, 0.00% packet loss
round-trip min/avg/max = 0.865/3.986/9.586 ms

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 54
©2016 NterOne Corporation
 Step 37 Disable the link to your Pod VDC (Ethernet 1/a) and test connectivity again.

N5K-X(config)# interface ethernet 1/a

N5K-X(config-if)# shutdown

N5K-X(config-if)# ping 172.16.P0.7P source 172.16.P0.5P

PING 172.16.P0.5P (172.16.P0.7P) from 172.16.P0.5P: 56 data bytes
64 bytes from 172.16.P0.7P: icmp_seq=0 ttl=254 time=1.316 ms
64 bytes from 172.16.P0.7P: icmp_seq=1 ttl=254 time=0.865 ms
64 bytes from 172.16.P0.7P: icmp_seq=2 ttl=254 time=1.007 ms
64 bytes from 172.16.P0.7P: icmp_seq=3 ttl=254 time=7.161 ms
64 bytes from 172.16.P0.7P: icmp_seq=4 ttl=254 time=9.586 ms

--- 172.16.P0.7P ping statistics ---

5 packets transmitted, 5 packets received, 0.00% packet loss
round-trip min/avg/max = 0.865/3.986/9.586 ms

Step 38 Re-enable the uplink to your Pod VDC and disable the uplink to your Peer Pod VDC.

N5K-X(config-if)# interface ethernet 1/a

N5K-X(config-if)# no shutdown

Step 39 Confirm connectivity again to your Pod VDC.

N5K-X(config-if)# ping 172.16.P0.7P source 172.16.P0.5P

PING 172.16.P0.5P (172.16.P0.7P) from 172.16.P0.5P: 56 data bytes
64 bytes from 172.16.P0.7P: icmp_seq=0 ttl=254 time=1.316 ms
64 bytes from 172.16.P0.7P: icmp_seq=1 ttl=254 time=0.865 ms
64 bytes from 172.16.P0.7P: icmp_seq=2 ttl=254 time=1.007 ms
64 bytes from 172.16.P0.7P: icmp_seq=3 ttl=254 time=7.161 ms
64 bytes from 172.16.P0.7P: icmp_seq=4 ttl=254 time=9.586 ms

--- 172.16.P.2 ping statistics ---

5 packets transmitted, 5 packets received, 0.00% packet loss
round-trip min/avg/max = 0.865/3.986/9.586 ms

Activity Verification
You have completed this task when you attain these results:
 You have used the show commands to verify that the vPC appears in the port channel database and
that traffic is passing over the different physical interfaces.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 55
©2016 NterOne Corporation
Lab 5: Configuring FabricPath
Complete this lab activity to practice what you learned in the related module.

Activity Objective
In this activity, you will configure and verify Cisco FabricPath on the Cisco Nexus 7000 Series switches.
After completing this activity, you will be able to meet these objectives:
 Analyze spanning-tree load balancing
 Implement Cisco FabricPath
 Verify Cisco FabricPath
 Analyze Cisco FabricPath load balancing

Command List
The following table describes the Cisco NX-OS commands that are used in this activity.
Com m and Description
install feature-set fabricpath Installs the FabricPath feature set on a Cisco Nexus 7000
Series sw itch
feature-set fabricpath Enables the FabricPath feature set
fabricpath sw itch-id Sets the FabricPath sw itch identifier (Note: The same
command configured the virtual sw itch ID for vPC+ in the
vPC domain configuration mode.)
sw itchport mode fabricpath Configures the FabricPath mode on an interface (This
command is available in interface configuration mode.)
mode fabricpath Changes a VLAN to a Cisco FabricPath VLAN
show mac address-table vlan <vlan> Displays the MAC address table for a VLAN
show spanning-tree vlan <vlan> Displays the spanning-tree topology for a VLAN
fabricpath load-balance unicast Configures the load-balancing method for unicast traffic
show fabricpath sw itch-id Displays the FabricPath sw itch ID table
show fabricpath isis route Displays the FabricPath Intermediate System-to-
Intermediate System (IS-IS paths
show fabricpath route Displays the FabricPath routing table

Task 0: Lab Preparation

In this task, you will perform the steps necessary to get ready for performing the subsequent tasks in this lab
exercise.

Activity Procedure
Complete these steps:
Step 1 Make sure that you know the value of your Pod Number. Your Pod Number is assigned to you
by your instructor and is used to identify the lab devices that you will use during this lab
exercise. Refer to the following table when a task step in this lab exercise uses a letter variable.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 56
©2016 NterOne Corporation
 Your
Your Your Your
Assigned Value of Value of Value of Value of Value of
Pod VDC Peer Pod Pod N5K “P” “Q” “JK” “X” “Y”
Pod
Nam e VDC Nam e Nam e
Num ber
1 vdc1 vdc2 N5K-A 1 2 12 A B
2 vdc2 vdc1 N5K-B 2 1 12 B A
3 vdc3 vdc4 N5K-A 3 4 34 A B
4 vdc4 vdc3 N5K-B 4 3 34 B A
5 vdc5 vdc6 N5K-A 5 6 56 A B
6 vdc6 vdc5 N5K-B 6 5 56 B A
7 vdc7 vdc8 N5K-A 7 8 78 A B
8 vdc8 vdc7 N5K-B 8 7 78 B A

Your
Assigned Value of Value of Value of Value of Value of Value of Value of Value of
“A” “B” “C” “D” “a” “b” “c” “d”
Pod Num ber
1 1 2 3 4 1 2 17 18
2 5 6 7 8 2 1 18 17
3 9 10 11 12 3 4 19 20
4 13 14 15 16 4 3 20 19
5 17 18 19 20 5 6 21 22
6 21 22 23 24 6 5 22 21
7 25 26 27 28 7 8 23 24
8 29 30 31 32 8 7 24 23

Step 2 Make sure that you know the value of your Rack Number. Your Rack Number is assigned to
you by your instructor and is used to identify the Nexus 7000 rack of devices that you will use
during this lab exercise.
Step 3 Your assigned Pod is one of two Pods within a Pod Pair. The details of each Pod Pair, including
diagrams and tables of related values, are contained in one of several NterOne Resource Guide
documents. Open the NterOne Resource Guide that corresponds to your assigned Pod Number.
Step 4 Locate the various tables that provide additional information about your assigned Pod, which
include details such as IP addresses and device login credentials.
Step 5 Locate the diagram that corresponds to this lab exercise. This diagram may help you visualize
the intended goal of this lab exercise.

Task 0.1: Log In to your Student Server and Connect to Lab Devices
During this task you will log in to your assigned Student Server and use PuTTY to start SSH sessions to each
of the devices that you will use during this lab exercise.

Activity Procedure
Complete these steps:
Step 6 Verify that you are currently logged in to your Student Server.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 57
©2016 NterOne Corporation
 Step 7 From your Student Server desktop use the PuTTY application to open SSH sessions to each of
the devices in the following table (there may be preconfigured shortcuts to these devices on the
Student Server desktop).

Note * You w ill need to get the passw ords for the Nexus sw itches from your instructor.

Note Make sure to use the IP address that corresponds to your assigned Rack Number .

Device Nam e Device Description IP Address Username Passw ord

vdcP Your Pod Nexus 7004 VDC Rack 1 – 10.0.0.8P admin *

(Pod VDC) Rack 2 – 10.0.0.18P
Your Peer Pod Nexus 7004 VDC Rack 1 – 10.0.0.8Q
vdcQ admin *
(Peer Pod VDC) Rack 2 – 10.0.0.18Q

N5K-A Nexus 5548UP Sw itch managed by Rack 1 – 10.0.0.78 podP *

odd-numbered Pods Rack 2 – 10.0.0.178
Nexus 5548UP Sw itch managed by Rack 1 – 10.0.0.79
N5K-B podP *
even-numbered Pods Rack 2 – 10.0.0.179

N7K The Nexus 7004 admin VDC Rack 1 – 10.0.0.80 student Nterone179
Rack 2 – 10.0.0.180

Note It is suggested that you arrange the PuTTY w indow s in a rectangle in a similar arrangement as
the sw itches in the lab diagram in the Resource Guide.

Task 0.2: Reset the Configuration of your Pod VDC

In order to ensure that the steps in this lab exercise function properly the running configuration of your Pod
VDC must be reset to the baseline configuration. During this task you will reset the configuration of your
Pod VDC to the baseline state.

Activity Procedure
Complete these steps:
Step 8 Switch to the PuTTY session to your Pod VDC (vdcP).
Step 9 You will be using the NX-OS checkpoint function to reset the configuration of the VDC to a
baseline state, which removes the configuration created in a previous lab exercise. Execute the
following command to roll back the configuration:
rollback running-config file bootflash:baseline best-effort

vdcP# rollback running-config file bootflash:baseline best-effort

Collecting Running-Config
#Generating Rollback Patch
Executing Rollback Patch

Rollback completed successfully.

Step 10 Execute the show running-config command. You should see that all of the physical interfaces
now only have a description and there are no commands present from the previous lab exercise.
Step 11 Execute the show running-config ip command. The baseline configuration contains three
VLAN interfaces; each VLAN interface should have an IP address assigned to it.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 58
©2016 NterOne Corporation
 Note If any of the VLAN interfaces do NOT have an IP address, repeat the rollback command in
Step 9. In some cases the rollback does not reset all of the configuration.

vdcP# show running-config ip

!Command: show running-config ip

!Time: Tue Jun 10 14:34:05 2014

version 7.2(1)D1(1)
vrf context management
ip route 0.0.0.0/0 10.0.0.1

interface VlanP0
ip address 172.16.P0.7P/24

interface VlanJK
ip address 172.16.JK.7P/24

interface VlanQ0
ip address 172.16.Q0.7P/24

interface mgmt0
ip address 10.0.0.xxx/24

vdcP#

Task 0.3: Reset the Configuration of your Pod N5K

In order to ensure that the steps in this lab exercise function properly the running configuration of your Pod
N5K must be reset to the baseline configuration. During this task you will reset the configuration of your Pod
N5K to the baseline state for the portions of the overall switch configuration that are managed by your Pod.

Activity Procedure
Complete these steps:
Step 12 Switch to the PuTTY session to your Pod N5K (N5K-X).
Step 13 Reset the running configuration of your Pod to the baseline state by entering the
run-script baseline command (where “P” is your Pod Number).

N5K-A# run-script resetpodP

`configure
`default interface Ethernet1/P-Q
<… output omitted …>
`end

Step 14 Execute the show running-config interface Ethernet 1/P-Q command (where “P” is your Pod
Number and “Q” is your Peer Pod Number). You should see that these interfaces now only have
a description and there are no commands present from the previous lab exercise.

N5K-X# show running-config interface ethernet 1/P-Q

!Command: show running-config interface Ethernet1/P-Q

!Time: Mon Jul 4 11:57:15 2016

version 7.3(0)N1(1)

interface Ethernet1/P
description [from N5K-X Eth 1/P (1/a) to vdcP Eth 4/?]

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 59
©2016 NterOne Corporation
 interface Ethernet1/Q
description [from N5K-X Eth 1/Q (1/b) to vdcQ Eth 4/?]

Activity Verification
You have completed this activity when you have achieved these goals:
 You have made a successful connection to your Student Server.
 You have successfully used PuTTY to connect to the Nexus switches in the lab rack.
 You have reset the running configuration of your Pod VDC to a baseline state.
 You have reset the running configuration of your Pod’s interfaces in your Pod N5K to a baseline
state.

Task 1: Configure Device Interfaces

In this task, you will configure the interfaces that will be used during this lab exercise.

Activity Procedure
Complete these steps:
Step 15 On your Pod VDC, enable the interfaces toward your Pod N5K and your Peer Pod VDC, and
configure them as trunks.

vdcP# configure
Enter configuration commands, one per line. End with CNTL/Z.
vdcP(config-if)# interface ethernet 4/A, ethernet 4/C -D
vdcP(config-if-range)# switchport mode trunk
vdcP(config-if-range)# spanning-tree port type network
vdcP(config-if-range)# no shutdown
vdcP(config-if-range)# end

Step 16 On your Pod N5K, configure interface Ethernet 1/a as a trunk port.

N5K-X# configure
Enter configuration commands, one per line. End with CNTL/Z.
N5K-X(config)# interface ethernet 1/a
N5K-X(config-if)# switchport mode trunk
N5K-X(config-if)# spanning-tree port type network
N5K-X(config-if)# no shutdown
N5K-X(config-if)# end

Step 17 Ping the SVI interfaces on each of the switches in your Pod Pair to verify that you have
correctly configured VLAN JK and the trunking between the two switches:
 vdcP – 172.16.JK.7P
 vdcQ – 172.16.JK.7Q
 N5K-X – 172.16.JK.5P
 N5K-Y – 172.16.JK.5Q

vdcP# ping 172.16.JK.5P

PING 172.16.JK.5P (172.16.JK.5P): 56 data bytes
64 bytes from 172.16.JK.5P: icmp_seq=0 ttl=254 time=1.245 ms
64 bytes from 172.16.JK.5P: icmp_seq=1 ttl=254 time=0.694 ms
64 bytes from 172.16.JK.5P: icmp_seq=2 ttl=254 time=0.776 ms
64 bytes from 172.16.JK.5P: icmp_seq=3 ttl=254 time=7.507 ms
64 bytes from 172.16.JK.5P: icmp_seq=4 ttl=254 time=9.524 ms

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 60
©2016 NterOne Corporation
 --- 172.16.JK.5P ping statistics ---
5 packets transmitted, 5 packets received, 0.00% packet loss
round-trip min/avg/max = 0.694/C.949/9.524 ms

vdcP# ping 172.16.JK.5Q

PING 172.16.JK.5Q (172.16.JK.5Q): 56 data bytes
64 bytes from 172.16.JK.5Q: icmp_seq =0 ttl=254 time=2.701 ms
64 bytes from 172.16.JK.5Q: icmp_seq=1 ttl=254 time=0.975 ms
64 bytes from 172.16.JK.5Q: icmp_seq=2 ttl=254 time=1.748 ms
64 bytes from 172.16.JK.5Q: icmp_seq=3 ttl=254 time=7.341 ms
64 bytes from 172.16.JK.5Q: icmp_seq=4 ttl=254 t ime=6.968 ms

--- 172.16.JK.5Q ping statistics ---

5 packets transmitted, 5 packets received, 0.00% packet loss
round-trip min/avg/max = 0.975/3.946/7.341 ms

vdcP# ping 172.16.JK.7P

PING 172.16.JK.7P (172.16.JK.7P): 56 data bytes
64 bytes from 172.16.JK.7P: icmp_seq=0 ttl=255 time=0.72 ms
64 bytes from 172.16.JK.7P: icmp_seq=1 ttl=255 time=0.444 ms
64 bytes from 172.16.JK.7P: icmp_seq=2 ttl=255 time=0.57 ms
64 bytes from 172.16.JK.7P: icmp_seq=3 ttl=255 time=0.726 ms
64 bytes from 172.16.JK.7P: icmp_seq=4 ttl=255 time=0.399 ms

--- 172.16.JK.7P ping statistics ---

5 packets transmitted, 5 packets received, 0.00% packet loss
round-trip min/avg/max = 0.399/0.571/0.726 ms

vdcP# ping 172.16.JK.7Q

PING 172.16.JK.7Q (172.16.JK.7Q): 56 data bytes
64 bytes from 172.16.JK.7Q: icmp_seq=0 ttl=254 time=1.025 ms
64 bytes from 172.16.JK.7Q: icmp_seq=1 ttl=254 time=0.679 ms
64 bytes from 172.16.JK.7Q: icmp_seq=2 ttl=254 time=0.735 ms
64 bytes from 172.16.JK.7Q: icmp_seq=3 ttl=254 time=0.668 ms
64 bytes from 172.16.JK.7Q: icmp_seq=4 ttl=254 time=0.7 ms

--- 172.16.JK.7Q ping statistics ---

5 packets transmitted, 5 packets received, 0.00% packet loss
round-trip min/avg/max = 0.668/0.761/1.025 ms

Step 18 Examine the spanning-tree topology of VLAN JK on the VDCs in your Pod Pair and identity
the links that are in a blocking state. Note that at this point we are not concerned about which
switch is the root bridge.

vdcP# show spanning-tree vlan JK

VLAN00JK
Spanning tree enabled protocol rstp
Root ID Priority 32780
Address 002a.6a0f.7181
Cost 6
Port 515 (Ethernet4/C)
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec

Bridge ID Priority 32780 (priority 32768 sys -id-ext JK)

Address 8478.ac57.9642
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec

Interface Role Sts Cost Prio.Nbr Type

---------------- ---- --- --------- -------- --------------------------------
Eth4/A Desg FWD 2 128.513 Network P2p

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 61
©2016 NterOne Corporation
 Eth4/C Root FWD 4 128.515 Network P2p
Eth4/D Altn BLK 4 128.516 Network P2p

vdcP# show spanning-tree blockedports

Name Blocked Interfaces List

-------------------- ------------------------------------
VLAN0001 Eth4/D
VLAN00JK Eth4/D

Number of blocked ports (segments) in the system : 2

vdcQ# show spanning-tree vlan JK

VLAN00JK
Spanning tree enabled protocol rstp
Root ID Priority 32780
Address 002a.6a0f.7181
Cost 2
Port 517 (Ethernet4/5)
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec

Bridge ID Priority 32780 (priority 32768 sys -id-ext JK)

Address 8478.ac57.9643
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec

Interface Role Sts Cost Prio.Nbr Type

---------------- ---- --- --------- -------- --------------------------------
Eth4/A Root FWD 2 128.517 Network P2p
Eth4/C Desg FWD 4 128.519 Network P2p
Eth4/D Desg FWD 4 128.520 Network P2p

vdcQ# show spanning-tree blockedports

Activity Verification
You have completed this task when you attain these results:
 You have verified that the spanning-tree topology does not allow several active links between two
switches or Layer 2 loops in the topology.

Task 2: Implement Cisco FabricPath

In this task, you will implement Cisco FabricPath technology on your Pod VDC.

Activity Procedure
Complete these steps:
Step 19 On your Pod VDC, examine the license usage.

vdcP# show license usage

Feature Lic Ins
Status Expiry Date Comments
Count
--------------------------------------------------------------------------------
MPLS_PKG Yes - Unused 18 Sep 2013 -
STORAGE-ENT No - Unused -
VDC_LICENSES Yes 4 Unused 18 Sep 2013 -
ENTERPRISE_PKG No - Unused -
FCOE-N7K-F132XP No 0 Unused -
FCOE-N7K-F248XP No 0 Unused -
ENHANCED_LAYER2_PKG Yes - Unused 18 Sep 2013 -

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 62
©2016 NterOne Corporation
 SCALABLE_SERVICES_PKG No - Unused -
TRANSPORT_SERVICES_PKG Yes - Unused 18 Sep 2013 -
LAN_ADVANCED_SERVICES_PKG Yes - Unused 18 Sep 2013 -
LAN_ENTERPRISE_SERVICES_PKG Yes - Unused 18 Sep 2013 -
--------------------------------------------------------------------------------

Step 20 Enable the Cisco FabricPath feature set.

vdcP# configure
Enter configuration commands, one per line. End with CNTL/Z.
vdcP(config)# feature-set fabricpath

Step 21 Examine the Cisco FabricPath switch ID of your Pod VDC.

vdcP(config)# show fabricpath switch-id

FABRICPATH SWITCH-ID TABLE
Legend: '*' - this system
=========================================================================
SWITCH-ID SYSTEM-ID FLAGS STATE STATIC EMULATED
----------+----------------+------------+-----------+--------------------
*2172 8478.ac57.9642 Primary Confirmed No No
Total Switch-ids: 1

Note The sw itch ID w ill be different than in the example.

Step 22 Configure the switch ID of your Pod VDC to be 7P (where “P” is your Pod Number).

vdcP(config)# fabricpath switch-id 7P

Step 23 Verify the configured Cisco FabricPath switch ID.

vdcP(config)# show fabricpath switch-id

FABRICPATH SWITCH-ID TABLE
Legend: '*' - this system
=========================================================================
SWITCH-ID SYSTEM-ID FLAGS STATE STATIC EMULATED
----------+----------------+------------+-----------+--------------------
*7P 8478.ac57.9642 Primary Confirmed Yes No
Total Switch-ids: 1

Step 24 Configure the interfaces to your Peer Pod VDC as FabricPath interfaces.

vdcP(config)# interface ethernet 4/C-D

vdcP(config-if-range)# switchport mode fabricpath

Step 25 Reexamine the Cisco FabricPath switch IDs.

vdcP(config-if-range)# show fabricpath switch-id

FABRICPATH SWITCH-ID TABLE
Legend: '*' - this system
=========================================================================
SWITCH-ID SYSTEM-ID FLAGS STATE STATIC EMULATED
----------+----------------+------------+-----------+--------------------
*7P 8478.ac57.9642 Primary Confirmed Yes No
7Q 8478.ac57.9643 Primary Confirmed Yes No
Total Switch-ids: 2

STOP! Wait until your Peer Pod has com pleted all steps up to this point before proceeding.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 63
©2016 NterOne Corporation
 Step 26 Use the show fabricpath isis adjacency command to verify that Cisco FabricPath IS-IS
adjacencies have been formed between the VDCs.

vdcP(config-if-range)# show fabricpath isis adjacency

Fabricpath IS-IS domain: default Fabricpath IS-IS adjacency database:
System ID SNPA Level State Hold Time Interface
vdcQ N/A 1 UP 00:00:31 Ethernet4/C
vdcQ N/A 1 UP 00:00:30 Ethernet4/D

Step 27 From your Pod N5K, ping 172.16.JK.5Q, the IP address of your Peer Pod N5K (where “Q” is
your Peer Pod number), in order to confirm IP connectivity between the two pods. Determine if
the ping was successful and why.

N5K-X# ping 172.16.JK.5Q

PING 172.16.JK.5Q (172.16.JK.5Q): 56 data bytes
Request 0 timed out
Request 1 timed out
Request 2 timed out
Request 3 timed out
Request 4 timed out
--- 172.16.JK.5Q ping statistics ---
5 packets transmitted, 0 packets received, 100.00% packet loss

Step 28 Examine the Cisco FabricPath routing table on your Pod VDC.

vdcP(config-if-range)# show fabricpath route

FabricPath Unicast Route Table
'a/b/c' denotes ftag/switch-id/subswitch-id
'[x/y]' denotes [admin distance/metric]
ftag 0 is local ftag
subswitch-id 0 is default subswitch-id

FabricPath Unicast Route Table for Topology -Default

0/7P/0, number of next-hops: 0

via ---- , [60/0], 0 day/s 00:07:47, local

Note The Cisco FabricPath routing table does not list any remote sw itches until at least one Cisco
FabricPath VLAN has been configured.

Step 29 Convert VLAN JK to a Cisco FabricPath VLAN on your Pod VDC.

vdcP(config-if-range)# vlan JK
vdcP(config-vlan)# mode fabricpath
vdcP(config-vlan)# exit

Note In NX-OS changes to a VLAN’s configuration are not implemented until you leave VLAN
configuration mode; this can be done by using the “exit” command.

Step 30 Configure your Pod VDC to be the root bridge for VLAN JK. This step is necessary so that
traffic flows through the FabricPath properly.

vdcP(config)# spanning-tree vlan JK root primary

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 64
©2016 NterOne Corporation
 Step 31 Examine the state of spanning tree of VLAN JK by using the show spanning-tree vlan JK
command. You should see that your Pod VDC is now only connected to your Pod N5K switch
and that there is no longer any spanning tree configured between your VDCs.

vdcP(config)# show spanning-tree vlan JK

VLAN00JK
Spanning tree enabled protocol rstp
Root ID Priority 24588
Address c84c.75fa.6000
This bridge is the root
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec

Bridge ID Priority 24588 (priority 24576 sys -id-ext JK)

Address c84c.75fa.6000
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec

Interface Role Sts Cost Prio.Nbr Type

---------------- ---- --- --------- -------- --------------------------------
Eth4/A Desg FWD 2 128.513 Network P2p

STOP! Wait until your Peer Pod has com pleted all steps up to this point before proceeding.

Step 32 Reexamine the Cisco FabricPath routing table.

vdcP(config)# show fabricpath route

FabricPath Unicast Route Table
'a/b/c' denotes ftag/switch-id/subswitch-id
'[x/y]' denotes [admin distance/metric]
ftag 0 is local ftag
subswitch-id 0 is default subswitch-id

FabricPath Unicast Route Table for Topology -Default

0/7P/0, number of next-hops: 0

via ---- , [60/0], 0 day/s 00:15:27, local
1/7Q/0, number of next-hops: 2
via Eth4/C, [115/400], 0 day/s 00:00:39, isis_fabricpath -default
via Eth4/D, [115/400], 0 day/s 00:00:39, isis_fabricpath -default

Step 33 From your Pod N5K, ping 172.16.JK.7P, the IP address of your Pod VDC.

N5K-X# ping 172.16.JK.7P

PING 172.16.JK.7P (172.16.JK.7P): 56 data bytes
64 bytes from 172.16.JK.7P: icmp_seq=0 ttl=254 time=2.111 ms
64 bytes from 172.16.JK.7P: icmp_seq=1 ttl=254 time=0.789 ms
64 bytes from 172.16.JK.7P: icmp_seq=2 ttl=254 time=0.746 ms
64 bytes from 172.16.JK.7P: icmp_seq=3 ttl=254 time=0.737 ms
64 bytes from 172.16.JK.7P: icmp_seq=4 ttl=254 time=0.735 ms
--- 172.16.JK.7P ping statistics ---
5 packets transmitted, 5 packets received, 0.00% packet loss
round-trip min/avg/max = 0.735/1.024/1.111 ms

Step 34 From your Pod N5K, ping 172.16.JK.5Q, the IP address of your Peer Pod N5K.

N5K-X# ping 172.16.JK.5Q

PING 172.16.JK.5Q (172.16.JK.5Q): 56 data bytes
64 bytes from 172.16.JK.5Q: icmp_seq=0 ttl=254 time=2.111 ms
64 bytes from 172.16.JK.5Q: icmp_seq=1 ttl=254 time=0.789 ms

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 65
©2016 NterOne Corporation
 64 bytes from 172.16.JK.5Q: icmp_seq=2 ttl=254 time=0.746 ms
64 bytes from 172.16.JK.5Q: icmp_seq=3 ttl=254 time=0.737 ms
64 bytes from 172.16.JK.5Q: icmp_seq=4 ttl=254 time=0.735 ms
--- 172.16.JK.5Q ping statistics ---
5 packets transmitted, 5 packets received, 0.00% packet loss
round-trip min/avg/max = 0.735/1.024/1.111 ms

Step 35 Examine the MAC address table for VLAN JK on your Pod N5K. You should see entries for
the SVI interface of your Pod VDC and your Peer Pod N5K.

Note Keep in mind how FabricPath uses conversational MAC learning w hile you are looking at these
results.

N5K-X(config)# show mac address-table vlan JK

Legend:
* - primary entry, G - Gateway MAC, (R) - Routed MAC, O - Overlay MAC
age - seconds since last seen,+ - primary entry using vPC Peer-Link
VLAN MAC Address Type age Secure NTFY Ports/SWID.SSID.LID
---------+-----------------+--------+---------+------+----+------------------
* JK 002a.6a0f.7181 dynamic 110 F F Eth1/a
* JK 547f.eef7.6bfc static 0 F F Router
* JK 8478.ac57.9642 dynamic 120 F F Eth1/a
* JK 8478.ac57.9643 dynamic 120 F F Eth1/a

Step 36 Examine the MAC address table for VLAN JK on your Pod VDC.

vdcP(config)# show mac address-table vlan JK

Legend:
* - primary entry, G - Gateway MAC, (R) - Routed MAC, O - Overlay MAC
age - seconds since last seen,+ - primary entry using vPC Peer-Link,
(T) - True, (F) - False
VLAN MAC Address Type age Secure NTFY Ports/SWID.SSID.LID
---------+-----------------+--------+---------+------+----+------------------
G JK 8478.ac57.9642 static - F F sup-eth1(R)
JK 002a.6a0f.7181 dynamic 150 F F 72.0.52
* JK 547f.eef7.6bfc dynamic 150 F F Eth4/A
JK 8478.ac57.9643 dynamic 150 F F 72.0.4306

Note Do not proceed to the next task until you succeed in pinging the Peer Pod N5K VLAN JK IP
address. Troubleshoot together w ith your peer as necessary.

Activity Verification
You have completed this task when you attain these results:
 You have implemented Cisco FabricPath on your Pod VDC.
 You have established a Cisco FabricPath cloud with your Peer Pod VDC.
 You have verified IP connectivity between your Pod N5K and your Peer Pod N5K in the VLAN
across the Cisco FabricPath cloud.

Task 3: Analyze Cisco FabricPath Load Balancing

In this task, you will examine the traffic load balancing in a Cisco FabricPath environment.

Activity Procedure
Complete these steps:

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 66
©2016 NterOne Corporation
 Step 37 On your Pod VDC, configure the VLAN JK interface with the secondary IP address of
172.16.JK.9P (where “P” is your Pod Number).

vdcP(config)# interface vlan JK

vdcP(config-if)# ip address 172.16.JK.9P/24 secondary
Disabling IP Redirects on VlanJK :secondary address configured.

Step 38 Configure Cisco FabricPath load balancing to use only Layer 3 for hash calculation.

vdcP(config-if)# fabricpath load-balance unicast layer3

Step 39 Examine the current FabricPath routing table.

vdcP(config)# show fabricpath route

FabricPath Unicast Route Table
'a/b/c' denotes ftag/switch-id/subswitch-id
'[x/y]' denotes [admin distance/metric]
ftag 0 is local ftag
subswitch-id 0 is default subswitch-id

FabricPath Unicast Route Table for Topology -Default

0/7P/0, number of next-hops: 0

via ---- , [60/0], 0 day/s 00:12:45, local
1/7Q/0, number of next-hops: 2
via Eth4/C, [115/400], 0 day/s 00:12:07, isis_fabricpath -default
via Eth4/D, [115/400], 0 day/s 00:12:07, isis_fabricpath -default

Step 40 Determine which links Cisco FabricPath will use to forward traffic toward your Peer Pod VDC.
Examine the flows between the following IP addresses:
 172.16.JK.7P to 172.16.JK.7Q
 172.16.JK.7P to 172.16.JK.9Q
 172.16.JK.9P to 172.16.JK.9Q
 172.16.JK.9P to 172.16.JK.7Q

Note Make sure to replace “P” w ith your Pod Number and “Q” w ith your Peer Pod Number in each
command. You may w ant to use Notepad to type out these long commands and then copy and
paste them into PuTTY.

vdcP(config)# show fabricpath load-balance unicast forwarding-path ftag 1 switchid

7Q flow-type L3 src-ip 172.16.JK.7P dst-ip 172.16.JK.7Q vlan JK module 4
This flow selects interface Eth4/C
vdcP(config)# show fabricpath load-balance unicast forwarding-path ftag 1 switchid
7Q flow-type L3 src-ip 172.16.JK.7P dst-ip 172.16.JK.9Q vlan JK module 4
This flow selects interface Eth4/D
vdcP(config)# show fabricpath load-balance unicast forwarding-path ftag 1 switchid
7Q flow-type L3 src-ip 172.16.JK.9P dst-ip 172.16.JK.9Q vlan JK module 4
This flow selects interface Eth4/C
vdcP(config)# show fabricpath load-balance unicast forwarding-path ftag 1 switchid
7Q flow-type L3 src-ip 172.16.JK.9P dst-ip 172.16.JK.7Q vlan JK module 4
This flow selects interface Eth4/D

Step 41 To check high availability of the Cisco FabricPath cloud, disable interface Ethernet 4/C.

vdcP(config)# interface ethernet 4/C

vdcP(config-if)# shutdown

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 67
©2016 NterOne Corporation
 Step 42 Reexamine the Cisco FabricPath routing table.

vdcP(config-if)# show fabricpath route

FabricPath Unicast Route Table
'a/b/c' denotes ftag/switch-id/subswitch-id
'[x/y]' denotes [admin distance/metric]
ftag 0 is local ftag
subswitch-id 0 is default subswitch-id

FabricPath Unicast Route Table for Topology -Default

0/7P/0, number of next-hops: 0

via ---- , [60/0], 0 day/s 00:38:00, local
1/7Q/0, number of next-hops: 1
via Eth4/D, [115/400], 0 day/s 00:37:55, isis_fabricpath -default

Step 43 On your Pod N5K, ping 172.16.JK.5Q, the IP address of your Peer Pod N5K, in order to
confirm high availability between the two pods.

N5K-X# ping 172.16.JK.5Q

PING 172.16.JK.5Q (172.16.JK.5Q): 56 data bytes
64 bytes from 172.16.JK.5Q: icmp_seq=0 ttl=254 time=2.111 ms
64 bytes from 172.16.JK.5Q: icmp_seq=1 ttl=254 time=0.789 ms
64 bytes from 172.16.JK.5Q: icmp_seq=2 ttl=254 time=0.746 ms
64 bytes from 172.16.JK.5Q: icmp_seq=3 ttl=254 time=0.737 ms
64 bytes from 172.16.JK.5Q: icmp_seq=4 ttl=254 time=0.735 ms
--- 172.16.JK.5Q ping statistics ---
5 packets transmitted, 5 packets received, 0.00% packet loss
round-trip min/avg/max = 0.735/1.024/B.111 ms

Activity Verification
You have completed this task when you attain these results:
 You have examined the Cisco FabricPath load balancing.
 You have examined the high availability of the Cisco FabricPath links.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 68
©2016 NterOne Corporation
Lab 6: Configuring OTV
Complete this lab activity to practice what you learned in the related module.

Activity Objective
In this activity, you will configure OTV between your Pod Pair VDCs. After completing this activity, you
will be able to meet these objectives:
 Configure a Cisco Nexus 7000 Series switch to support OTV
 Verify the OTV operation

Command List
The following table describes the Cisco NX-OS commands that are used in this activity.

Com m and Description

feature interface-vlan Enables the interface-vlan feature, w hich allow s SVIs to be
created
show license usage Displays the license usage in a VDC
feature otv Enables the Overlay Transport Virtualization (OTV) feature
otv site-vlan <vlan> Defines the OTV site VLAN
ip igmp version <version> Configures the Internet Group Management Protocol (IGMP)
version
interface overlay <nr> Creates an OTV overlay
otv join-interface <intf> Defines the OTV join interface for an overlay
otv control-group <multicast-group> Defines the OTV control multicast group for an overlay
otv data-group <multicastgroup-range> Defines the range of multicast groups to be used for
multicast forw arding on an overlay
otv extend-vlan <vlanrange> Defines the range of VLANs that are extended across an
overlay
show otv overlay <nr> Displays basic parameters and status information for an
OTV overlay
show otv adjacency Displays the list of OTV adjacencies on a VDC
show otv route Displays the OTV MAC routing table
show otv arp-nd-cache Displays the content of the OTV Address Resolution
Protocol (ARP) and neighbor discovery (ND) cache
show spanning-tree vlan <vlan> Displays the spanning-tree state for a VLAN

Task 0: Lab Preparation

In this task, you will perform the steps necessary to get ready for performing the subsequent tasks in this lab
exercise.

Activity Procedure
Complete these steps:
Step 1 Make sure that you know the value of your Pod Number. Your Pod Number is assigned to you
by your instructor and is used to identify the lab devices that you will use during this lab
exercise. Refer to the following table when a task step in this lab exercise uses a letter variable.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 69
©2016 NterOne Corporation
 Your
Your Your Your
Assigned Value of Value of Value of Value of Value of
Pod VDC Peer Pod Pod N5K “P” “Q” “JK” “X” “Y”
Pod
Nam e VDC Nam e Nam e
Num ber
1 vdc1 vdc2 N5K-A 1 2 12 A B
2 vdc2 vdc1 N5K-B 2 1 12 B A
3 vdc3 vdc4 N5K-A 3 4 34 A B
4 vdc4 vdc3 N5K-B 4 3 34 B A
5 vdc5 vdc6 N5K-A 5 6 56 A B
6 vdc6 vdc5 N5K-B 6 5 56 B A
7 vdc7 vdc8 N5K-A 7 8 78 A B
8 vdc8 vdc7 N5K-B 8 7 78 B A

Your
Assigned Value of Value of Value of Value of Value of Value of Value of Value of
“A” “B” “C” “D” “a” “b” “c” “d”
Pod Num ber
1 1 2 3 4 1 2 17 18
2 5 6 7 8 2 1 18 17
3 9 10 11 12 3 4 19 20
4 13 14 15 16 4 3 20 19
5 17 18 19 20 5 6 21 22
6 21 22 23 24 6 5 22 21
7 25 26 27 28 7 8 23 24
8 29 30 31 32 8 7 24 23

Step 2 Make sure that you know the value of your Rack Number. Your Rack Number is assigned to
you by your instructor and is used to identify the Nexus 7000 rack of devices that you will use
during this lab exercise.
Step 3 Your assigned Pod is one of two Pods within a Pod Pair. The details of each Pod Pair, including
diagrams and tables of related values, are contained in one of several NterOne Resource Guide
documents. Open the NterOne Resource Guide that corresponds to your assigned Pod Number.
Step 4 Locate the various tables that provide additional information about your assigned Pod, which
include details such as IP addresses and device login credentials.
Step 5 Locate the diagram that corresponds to this lab exercise. This diagram may help you visualize
the intended goal of this lab exercise.

Task 0.1: Log In to your Student Server and Connect to Lab Devices
During this task you will log in to your assigned Student Server and use PuTTY to start SSH sessions to each
of the devices that you will use during this lab exercise.

Activity Procedure
Complete these steps:
Step 6 Verify that you are currently logged in to your Student Server.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 70
©2016 NterOne Corporation
 Step 7 From your Student Server desktop use the PuTTY application to open SSH sessions to each of
the devices in the following table (there may be preconfigured shortcuts to these devices on the
Student Server desktop).

Note * You w ill need to get the passw ords for the Nexus sw itches from your instructor.

Note Make sure to use the IP address that corresponds to your assigned Rack Number .

Device Nam e Device Description IP Address Username Passw ord

vdcP Your Pod Nexus 7004 VDC Rack 1 – 10.0.0.8P admin *

(Pod VDC) Rack 2 – 10.0.0.18P
Your Peer Pod Nexus 7004 VDC Rack 1 – 10.0.0.8Q
vdcQ admin *
(Peer Pod VDC) Rack 2 – 10.0.0.18Q

N5K-A Nexus 5548UP Sw itch managed by Rack 1 – 10.0.0.78 podP *

odd-numbered Pods Rack 2 – 10.0.0.178
Nexus 5548UP Sw itch managed by Rack 1 – 10.0.0.79
N5K-B podP *
even-numbered Pods Rack 2 – 10.0.0.179

Note It is suggested that you arrange the PuTTY w indow s in a rectangle in a similar arrangement as
the sw itches in the lab diagram in the Resource Guide.

Task 0.2: Reset the Configuration of your Pod VDC

In order to ensure that the steps in this lab exercise function properly the running configuration of your Pod
VDC must be reset to the baseline configuration. During this task you will reset the configuration of your
Pod VDC to the baseline state.

Activity Procedure
Complete these steps:
Step 8 Switch to the PuTTY session to your Pod VDC (vdcP).
Step 9 You will be using the NX-OS checkpoint function to reset the configuration of the VDC to a
baseline state, which removes the configuration created in a previous lab exercise. Execute the
following command to roll back the configuration:
rollback running-config file bootflash:baseline best-effort

vdcP# rollback running-config file bootflash:baseline best-effort

Collecting Running-Config
#Generating Rollback Patch
Executing Rollback Patch

Rollback completed successfully.

Step 10 Execute the show running-config command. You should see that all of the physical interfaces
now only have a description and there are no commands present from the previous lab exercise.
Step 11 Execute the show running-config ip command. The baseline configuration contains three
VLAN interfaces; each VLAN interface should have an IP address assigned to it.

Note If any of the VLAN interfaces do NOT have an IP address, repeat the rollback command in
Step 9. In some cases the rollback does not reset all of the configuration.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 71
©2016 NterOne Corporation
 vdcP# show running-config ip

!Command: show running-config ip

!Time: Tue Jun 10 14:34:05 2014

version 7.2(1)D1(1)
vrf context management
ip route 0.0.0.0/0 10.0.0.1

interface VlanP0
ip address 172.16.P0.7P/24

interface VlanJK
ip address 172.16.JK.7P/24

interface VlanQ0
ip address 172.16.Q0.7P/24

interface mgmt0
ip address 10.0.0.xxx/24

vdcP#

Task 0.3: Reset the Configuration of your Pod N5K

In order to ensure that the steps in this lab exercise function properly the running configuration of your Pod
N5K must be reset to the baseline configuration. During this task you will reset the configuration of your Pod
N5K to the baseline state for the portions of the overall switch configuration that are managed by your Pod.

Activity Procedure
Complete these steps:
Step 12 Switch to the PuTTY session to your Pod N5K (N5K-X).
Step 13 Reset the running configuration of your Pod to the baseline state by entering the
run-script baseline command (where “P” is your Pod Number).

N5K-A# run-script resetpodP

`configure
`default interface Ethernet1/P-Q
<… output omitted …>
`end

Step 14 Execute the show running-config interface Ethernet 1/P-Q command (where “P” is your Pod
Number and “Q” is your Peer Pod Number). You should see that these interfaces now only have
a description and there are no commands present from the previous lab exercise.

N5K-X# show running-config interface ethernet 1/P-Q

!Command: show running-config interface Ethernet1/P-Q

!Time: Mon Jul 4 11:57:15 2016

version 7.3(0)N1(1)

interface Ethernet1/P
description [from N5K-X Eth 1/P (1/a) to vdcP Eth 4/?]

interface Ethernet1/Q
description [from N5K-X Eth 1/Q (1/b) to vdcQ Eth 4/?]

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 72
©2016 NterOne Corporation
Activity Verification
You have completed this activity when you have achieved these goals:
 You have made a successful connection to your Student Server.
 You have successfully used PuTTY to connect to the Nexus switches in the lab rack.
 You have reset the running configuration of your Pod VDC to a baseline state.
 You have reset the running configuration of your Pod’s interfaces in your Pod N5K to a baseline
state.

Task 1: Configuring Basic OTV

In this task, you will configure basic Cisco OTV features and verify the configuration between the two sites.

Activity Procedure
Complete these steps:
Step 15 On your Pod N5K, configure the interface to your Pod VDC (Ethernet 1/c) as a Layer 2 trunk.

N5K-X# configure
Enter configuration commands, one per line. End with CNTL/Z.
N5K-X(config)# interface ethernet 1/c
N5K-X(config-if)# speed 1000
N5K-X(config-if)# switchmode mode trunk
N5K-X(config-if)# spanning-tree port type network
N5K-X(config-if)# no shutdown
N5K-X(config-if)# end

Step 16 On your Pod VDC make sure that the interface-vlan feature has been disabled.

vdcP# configure
Enter configuration commands, one per line. End with CNTL/Z.
vdcP(config)# no feature interface-vlan

Note With the current release of the NX-OS, OTV and SVI cannot coexist w ithin the same VDC. You
must disable the interface VLAN feature in order for OTV to function properly.

Step 17 Enable the Cisco OTV feature.

vdcP(config)# feature otv

Step 18 Verify the status of the TRANSPORT_SERVICES_PKG license.

vdcP(config)# show license usage

Feature Ins Lic Status Expiry Date Comments
Count
------------------------------------------------------------------------------
MPLS_PKG Yes - Unused 09 May 2013 -
STORAGE-ENT No - Unused -
VDC_LICENSES No 0 Unused Grace 87D 22H
ENTERPRISE_PKG No - Unused -
FCOE-N7K-F132XP No 0 Unused -
FCOE-N7K-F248XP No 0 Unused -
ENHANCED_LAYER2_PKG Yes - Unused 09 May 2013 -
SCALABLE_SERVICES_PKG No - Unused -
TRANSPORT_SERVICES_PKG Yes - In use 09 May 2013 -
LAN_ADVANCED_SERVICES_PKG Yes - Unused 09 May 2013 -
LAN_ENTERPRISE_SERVICES_PKG Yes - Unused 09 May 2013 -

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 73
©2016 NterOne Corporation
 ------------------------------------------------ ------------------------------

Step 19 Configure the interface to your Pod N5K (Ethernet 3/A) as a trunk.

vdcP(config)# interface ethernet 3/A

vdcP(config-if)# switchport
vdcP(config-if)# switchport mode trunk
vdcP(config-if)# spanning-tree port type network
vdcP(config-if)# no shutdown

Step 20 Configure the second interface that is connected to your Peer Pod VDC (Ethernet 3/D) as a
Layer 3 interface with address 192.168.JK.7P/24 (where “JK” is your Pod Pair Number and “P”
is your Pod Number).

vdcP(config)# interface ethernet 3/D

vdcP(config-if)# no switchport
vdcP(config-if)# ip address 192.168.JK.7P/24
vdcP(config-if)# no shutdown

Step 21 Enable IGMP version 3 on the interface.

vdcP(config-if)# ip igmp version 3

Step 22 Configure the OTV site identifier. Use the value 0xP (where “P” is your Pod Number).

vdcP(config-if)# otv site-identifier 0xP

% Site Identifier mismatch will prevent overlays from forwarding traffic.

Note You w ill alw ays get a w arning message, even w hen the syntax is correct.

Step 23 Create the OTV Site VLAN, VLAN JK.

vdcP(config-if)# vlan JK
vdcP(config-vlan)# otv site-vlan JK

Step 24 Configure your Pod VDC to be the root bridge for VLAN JK. This step is necessary so that
traffic flows through the OTV overlay properly.

vdcP(config-site-vlan)# spanning-tree vlan JK root primary

Step 25 Create a logical Cisco OTV overlay interface.

vdcP(config)# interface overlay1

Step 26 Configure a multicast group address that is used by the Cisco OTV control plane for this OTV
overlay network.

vdcP(config-if-overlay)# otv control-group 239.1.JK.1

Step 27 Configure a range of local IPv4 multicast group prefixes used for multicast data traffic.

vdcP(config-if-overlay)# otv data-group 232.1.JK.0/28

Step 28 Join the Cisco OTV overlay interface with Ethernet 3/D.

vdcP(config-if-overlay)# otv join-interface ethernet 3/D

OTV needs join interfaces to be configured for IGMP version 3

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 74
©2016 NterOne Corporation
 Note You w ill alw ays get a w arning message, even w hen the syntax is correct.

Step 29 Assign the VLAN range to the Cisco OTV overlay interface.

vdcP(config-if-overlay)# otv extend-vlan JK

vdcP(config-if-overlay)# no shutdown
vdcP(config-if-overlay)# end

STOP! Wait until your peer pod has com pleted all steps up to this point before proceeding.

Step 30 Verify the adjacencies on the overlay network.

vdcP# show otv adjacency

Overlay Adjacency database

Overlay-Interface Overlay1 :
Hostname System -ID Dest Addr Up Time State
vdcQ 8478.ac57.9643 192.168.JK.7Q 00:00:06 UP

Step 31 Verify information about the overlay interface.

vdcP# show otv overlay 1

OTV Overlay Information

Site Identifier 0000.0000.000P

Overlay interface Overlay1

VPN name : Overlay1

VPN state : UP
Extended vlans : JK (Total:1)
Control group : 239.1.JK.1
Data group range(s) : 232.1.JK.0/28
Join interface(s) : Eth3/D (192.168.JK.7P)
Site vlan : JK (up)
AED-Capable : Yes
Capability : Multicast-Reachable

Step 32 Test connectivity from your Pod N5K to your Peer Pod N5K by pinging interface VLAN JK on
your Peer Pod N5K.

Note You may lose one or tw o packets the first time you attempt the ping.

N5K-X# ping 172.16.JK.5Q

PING 172.16.JK.5Q (172.16.JK.5Q): 56 data bytes
64 bytes from 172.16.JK.5Q: icmp_seq=0 ttl=254 time=1.306 ms
64 bytes from 172.16.JK.5Q: icmp_seq=1 ttl=254 time=0.736 ms
64 bytes from 172.16.JK.5Q: icmp_seq=2 ttl=254 time=0.705 ms
64 bytes from 172.16.JK.5Q: icmp_seq=3 ttl=254 time=0.721 ms
64 bytes from 172.16.JK.5Q: icmp_seq=4 ttl=254 time=0.723 ms

--- 172.16.JK.5Q ping statistics ---

5 packets transmitted, 5 packets received, 0.00% packet loss
round-trip min/avg/max = 0.705/0.838/1.306 ms

Step 33 Verify the VLANs that are associated with an overlay interface.

vdcP# show otv vlan

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 75
©2016 NterOne Corporation
 OTV Extended VLANs and Edge Device State Information (* - AED)

Legend:
(NA) - Non AED, (VD) - Vlan Disabled, (OD) - Overlay Down
(DH) - Delete Holddown, (HW) - HW: State Down

VLAN Auth. Edge Device Vlan State Overlay

---- ----------------------------------- ---------- -------
JK* vdcP active Overlay1

Step 34 Check information about the Cisco OTV routes on your Pod VDC.

vdcP# show otv route

OTV Unicast MAC Routing Table For Overlay1

VLAN MAC-Address Metric Uptime Owner Next-hop(s)

---- -------------- ------ -------- --------- -----------
JK 002a.6a0f.7159 42 00:02:55 overlay vdcQ
JK 547f.eef7.6bfc 1 00:01:19 site Ethernet3/ A

Step 35 Check the MAC address table on your VDC.

vdcP# show mac address-table

Legend:
* - primary entry, G - Gateway MAC, (R) - Routed MAC, O - Overlay MAC
age - seconds since last seen,+ - primary entry using vPC Peer-Link,
(T) - True, (F) - False
VLAN MAC Address Type age Secure NTFY Ports/SWID.SSID.LID
---------+-----------------+--------+---------+------+----+------------------
G - 8478.ac57.9642 static - F F sup-eth1(R)
O JK 002a.6a0f.7159 dynamic 0 F F Overlay1
* JK 547f.eef7.6bfc dynamic 60 F F Eth3/ A

Activity Verification
You have completed this task when you attain these results.
 You have used the show commands to verify that the basic Cisco OTV configuration is in place and
that a connection exists between the two sites.

Task 2: Configuring Advanced OTV

In this task, you will configure advanced Cisco OTV features and verify the configuration between the two
sites.

Activity Procedure
Complete these steps.
Step 36 Configure a key chain named “otv-keys”.

vdcP(config)# key chain otv-keys

vdcP(config-keychain)# key 0
vdcP(config-keychain-key)# key-string 0 Nterone179

Step 37 Configure authentication for edge devices.

vdcP(config-keychain-key)# interface overlay 1

vdcP(config-if-overlay)# otv isis authentication-check

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 76
©2016 NterOne Corporation
 vdcP(config-if-overlay)# otv isis authentication-type md5
vdcP(config-if-overlay)# otv isis authentication key-chain otv-keys

Step 38 Configure Cisco OTV PDU authentication. Use the VPN name Overlay1.

vdcP(config-if-overlay)# otv-isis default

vdcP(config-router)# vpn overlay1
vdcP(config-router-vrf)# authentication-check
vdcP(config-router-vrf)# authentication-type md5
vdcP(config-router-vrf)# authentication key-chain otv-keys

Step 39 Change the IS-IS network entity title for the routing process to 10.0000.0000.000P.00 (where
“P” is your Pod number).

vdcP(config-router-vrf)# net 10.0000.0000.000P.00

STOP! Wait until your peer pod has com pleted all steps up to this point before proceeding.

Step 40 Check the Cisco OTV VPN configuration.

vdcP(config-router)# show otv isis hostname vpn all

OTV-IS-IS Process: default dynamic hostname table VPN: Overlay1
Level System ID Dynamic hostname
1 0000.0000.000P* vdcP
1 0000.0000.000Q vdcQ

Step 41 Complete these steps if you are working on the LOWER numbered VDC only. Configure the
adjacency server function on your Pod VDC.

vdcP(config-router-vrf)# interface overlay 1

vdcP(config-if-overlay)# no otv control-group 239.1.JK.1
vdcP(config-if-overlay)# no otv data-group 232.1.JK.0/28
vdcP(config-if-overlay)# otv adjacency-server unicast-only
vdcP(config-if-overlay)# end

Step 42 Complete this step if you are working on the HIGHER numbered VDC only. Configure the
Peer Pod VDC IP address as the adjacency server.

vdcP(config-router)# interface overlay 1

vdcP( config-if-overlay)# no otv control-group 239.1.JK.1
vdcP( config-if-overlay)# no otv data-group 232.1.JK.0/28
vdcP( config-if-overlay)# otv use-adjacency-server 192.168.JK.7Q unicast-only
vdcP(config-if-overlay)# end

Step 43 Verify information about overlay interfaces.

On the LOWER numbered VDC:

vdcP# show otv overlay 1

OTV Overlay Information

Site Identifier 0000.0000.000X

Overlay interface Overlay1

VPN name : Overlay1

VPN state : UP
Extended vlans : JK (Total:1)
Join interface(s) : Eth3/D (192.168.JK.7P )
Site vlan : JK (up)

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 77
©2016 NterOne Corporation
 AED-Capable : Yes
Capability : Unicast-Only
Is Adjacency Server : Yes
Adjacency Server(s) : [None] / [None]

On the HIGHER number VDC:

vdcP# show otv overlay 1

OTV Overlay Information

Site Identifier 0000.0000.000Y

Overlay interface Overlay1

VPN name : Overlay1

VPN state : UP
Extended vlans : JK (Total:1)
Join interface(s) : Eth3/D (192.168.JK.7Y)
Site vlan : JK (up)
AED-Capable : Yes
Capability : Unicast-Only
Is Adjacency Server : No
Adjacency Server(s) : 192.168.JK.7X / [None]

Step 44 Test Test connectivity from your Pod N5K to your Peer Pod N5K by pinging interface VLAN
JK on your Peer Pod N5K.

N5K-X# ping 172.16.JK.5Q

PING 172.16.JK.5Q (172.16.JK.5Q): 56 data bytes
64 bytes from 172.16.JK.5Q: icmp_seq=0 ttl=254 time=1.003 ms
64 bytes from 172.16.JK.5Q: icmp_seq=1 ttl=254 time=0.925 ms
64 bytes from 172.16.JK.5Q: icmp_seq=2 ttl=254 time=0.851 ms
64 bytes from 172.16.JK.5Q: icmp_seq=3 ttl=254 time=0.851 ms
64 bytes from 172.16.JK.5Q: icmp_seq=4 ttl=254 time=6.575 ms

--- 172.16.JK.5Q ping statistics ---

5 packets transmitted, 5 packets received, 0.00% packet loss
round-trip min/avg/max = 0.851/2.041/6.575 ms

Activity Verification
You have completed this task when you attain these results.
 You have used the show commands to verify that the advanced Cisco OTV features are configured
correctly.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 78
©2016 NterOne Corporation
Lab 7: Accessing the NterOne Lab Devices
(Nexus 5000 Lab Rack)
The purpose of this lab exercise is to help you familiarize yourself with the NterOne lab environment and
how to successfully connect to the various devices that you will use during this class.

Task 1: Understanding your NterOne Lab Environment

Before you can begin configuring you lab devices you must understand how the NterOne lab environment is
constructed and how it is accessed.

Your Student Server

Before you can gain access to the NterOne lab devices you must first successfully log in to a Student Server.
 Once you have successfully logged in to a Student Server you will be able to use the applications
installed on the Student Server to access the lab devices for your class.
 Student Server names and account credentials will be given to you by your instructor.
 Two students may log in to the same Student Server using different accounts; in this case each
student will have a unique Desktop which is not shared with the other student.

The Student Servers are often referred to by a two-digit number (the Student Server Number) which is part of
the DNS and IP address of the Student Server.
 The first digit in the Student Server number corresponds to the NterOne Class Room Number to
which the Student Server belongs.
 The second digit in the Student Server number is the number of the specific Student Server within
that Room.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 79
©2016 NterOne Corporation
Pods and Pod Pairs
The NterOne lab hardware used during this class is divided into Pods and Pod Pairs:
 A Pod is a set of lab devices (hardware and software) that is configured by one or two students.
 A Pod Pair is a set of two Pods that may be required to work together to perform certain lab exercise
tasks.
 The Lab Guide will refer to the Pods within a Pod Pair as Pod P and Pod Q.
 Pod P always refers to the Pod to which you are assigned.
 Pod Q always refers to the opposite Pod within your Pod Pair, also referred to as the Peer Pod.

 A class may use more than one Pod Pair depending on the class size.
 All Student Servers can access all of the Pods used by the class. There are no restrictions binding a
Student Server to a specific Pod or Pod Pair.
 You will be assigned to a Pod for a given lab exercise, possibly with another student depending on
the class size.
 During the lab exercises you will be asked to configure the devices in your Pod. Do not configure
any devices outside your assigned Pod unless specifically instructed to do so.

Letter Variables
The Lab Guide for your class uses letter variables (similar to algebra) to represent letters or digits within a
command or command output. Usually, whenever you see one of the capital letters in the following table you
should replace that letter with the correct value; the Lab Guide should also point out when a letter variable is
being used. For example, if you are currently assigned to Pod 13, and if you are instructed to ping the IP
address of 10.20.30.P, you would ping the IP address of 10.20.30.13. The following table lists all of the letter
variables that are commonly used in the Lab Guide.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 80
©2016 NterOne Corporation
 Letter Variable Description
PP Your Pod Number (this is assigned to you by your instructor)
QQ Your Peer Pod Number (the number of the other Pod in your Pod Pair)
R The first digit of your Student Server Number (your Class Room number)
S The last digit of your Student Server Number
Z Your Pod Pair Number

The values of R and S are based on your Student Server Number as detailed in the previous table. The
following table indicates what the value of PP, QQ, and Z will be based on your Pod Number.

Value of “PP” Value of “QQ” Value of “Z”

Your Assigned Pod Num ber
(Your Pod Num ber) (Your Peer Pod Num ber) (Your Pod Pair Num ber)
11 11 12 1
12 12 11 1
13 13 14 2
14 14 13 2
15 15 16 3
16 16 15 3
17 17 18 4
18 18 17 4
19 19 20 5
20 20 19 5
21 21 22 6
22 22 21 6
23 23 24 7
24 24 23 7
25 25 26 8
26 26 25 8
27 27 28 9
28 28 27 9

You should determine the value of each of these letter variables before you start each lab exercise. If you do
not use the correct values you may not be able to complete the lab exercise and you may also cause another
student’s lab devices to malfunction.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 81
©2016 NterOne Corporation
Remote Desktop Connection
The application that you must use to log in to your Student Server is Remote Desktop Connection (RDC).
 This is the only application that can be used to log in to your Student Server.
 The shortcut to RDC is typically found on Windows-based systems by clicking Start  All
Programs  Accessories  Remote Desktop Connection. Another way to find RDC is to use the
“Search programs and files” function in the Windows Start menu.

or

 Students using Apple-based computers can download the Microsoft Remote Desktop app from
https://itunes.apple.com/us/app/id715768417?mt=12 .
 Students using Linux-based computers can download rdesktop from http://www.rdesktop.org/ .

Task 2: Connect to your Assigned Student Server using Remote

Desktop Connection (RDC)
Follow the steps in this Task in order to log in to a Student Server.
Step 1 Your instructor will give you the information you need to log in to a Stu dent Server. The
following table is provided for you to record these values.

Student Server Nam e / IP Address User Nam e Passw ord

Step 2 Log in to your personal/work computer.

Step 3 Verify that your computer is able to access the Internet. A simple test to verify this would be to
use a browser to access www.nterone.com .
Step 4 Verify that your computer has a Remote Desktop Connection (RDC) client installed. Use the
information on the previous page if you are having difficulty finding RDC on your computer.
Step 5 Start the Remote Desktop Connection application. The following window should appear.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 82
©2016 NterOne Corporation
 Note The follow ing steps use the Microsoft version of RDC; if you are using an Apple- or Linux-based
computer the screens that you w ill see w ill be different.

Step 6 In the Computer field enter the DNS name or IP address of the Student Server that has been
assigned to you.
Step 7 Click the Connect button.The Windows Security window should appear.

Note If this step fails after several seconds, please contact your class instructor for assistance.

Note If you are able to access the Internet but are unable to access any of the NterOne Student
Servers you w ill need to determine if there is a firew all somew here preventing your computer
from accessing the NterOne Student Servers. This is a common problem for students w ho are
using a computer at their place of employment, in w hich case you may need to contact your
company’s IT department f or assistance.

Step 8 Click on the “Use another account” section of the window.

Step 9 Enter the User name and Password needed to connect to the Student Server.

Step 10 Click the OK button. A window should appear which will look similar to the window below

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 83
©2016 NterOne Corporation
 Step 11 Click the check box next to “Don’t ask me again for connections to this computer” and then
click “Yes”.
Step 12 After a few seconds the login process should finish and the desktop of your Student Server
should appear which will look similar to the window below.

Step 13 Information about how your Student Server is configured will be displayed in the upper right-
hand corner of the Desktop.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 84
©2016 NterOne Corporation
 Step 14 The most commonly used applications such as PuTTY will have shortcut to them on the
Desktop. Other applications may also be found using the Start menu.
Step 15 Some files that you will be using during the class will be located in the S: drive, also referred to
as the students file share. There is a shortcut to this location on the Desktop. There is also a
shortcut on the Desktop to the Local Class Files , which may also be used during the class.

Step 16 The process to connect to your Student Server is complete.

Task 3: Use PuTTY on the Student Server to Connect to the Lab

Equipment
This procedure details the steps you will use to connect to a network device using the PuTTY application.
The device to which you will connect is the Cisco Nexus 5548UP switch in your Pod (also known as your
Pod Switch). This procedure assumes that you have successfully accessed your Student Server.
Step 17 Determine the following information about the device to which you will be connecting, which
is your Pod Switch:
 IP address of the management interface
 Username
 Password

Note Device-specific information such as IP addresses, usernames, and passw ords are located in the
NterOne Resource Guide for this class.

Step 18 From the desktop of your Student Server start the PuTTY application. A shortcut to PuTTY
should be on the desktop of the Student Server.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 85
©2016 NterOne Corporation
 Step 19 The PuTTY Configuration window will appear.

Step 20 Enter the IP address of the device to which you will be connecting in the “Host Name (or IP
address)” field.
Step 21 Click the radio button next to the correct Connection type. Typically you may leave this set to
SSH (the default); SSH is the default management connection method for Cisco devices.
Step 22 Click the Open button.

Note If you see the PuTTY Fatal Error w indow appear (show n below ) this means that PuTTY w as not
able to contact the device that you entered in the previous steps. Verify the IP address and/or
device name and try again. You may also need to verify that the target device is able to accept
connections. If you continue to have difficulty connecting to the device contact your instructor.

Step 23 If the connection attempt is successful you may see a window similar to the examples below. If
one of these windows appears, click Yes to continue.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 86
©2016 NterOne Corporation
 Step 24 If the connection attempt is successful you will see a window similar to the example below

Step 25 Enter the login information that the device is requesting, If the credentials are valid you should
see a command line prompt similar to the example show below.

Step 26 The process to use PuTTY to connect to a network device is complete.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 87
©2016 NterOne Corporation
Lab 7: Initial Cisco Nexus 5000 Series Switch
Configuration
Complete this lab activity to practice what you learned in the related module.

Activity Objective
Upon completing this guided lab, you will be able to:
 Verify the boot up process and logs of the Cisco Nexus 5000 Series Switch
 Identify the installed hardware on the Cisco Nexus 5000 Series Switch
 Perform an initial configuration

Task 1: System Reset and Familiarization

During this task, you will become familiar with usage of the Basic System Configuration Dialog and the CLI
features of the Cisco NX-OS Software.

Activity Procedure
Complete these steps:
Step 1 Verify that you are currently logged in to your Student Server.
Step 2 From your Student Server desktop, start a session to the console port of your Pod’s Nexus
switch by using the PuTTY shortcut to N5K-PP (Console) (replace “PP” with your assigned 2-
digit Pod Number).

Step 3 If you do not see login prompt press <Enter> once or twice; this will cause the login prompt to
be displayed.
Step 4 Log in to the switch with the following credentials:
 Username: admin
 Password: Nterone179
Step 5 Erase the startup configuration file by entering the write erase command. When prompted if
you wish to proceed, type “y” and press Enter.

N5K-PP# write erase

Warning: This command will erase the startup-configuration.
Do you wish to proceed anyway? (y/n) [n] y

Step 6 Reload the switch by entering the reload command. When prompted if you wish to proceed,
type “y” and press Enter.

N5K-PP# reload
WARNING: This command will reboot the system
Do you want to continue? (y/n) [n] y
[222535.269896] Shutdown Ports..
[222535.305315] writing reset reason 9,

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 88
©2016 NterOne Corporation
 2016 May 24 11:34:41 N5K-17 %$ VDC-1 %$ %PFMA-2-PFM_SYSTEM_RESET: Manual system
restart from Command Line Interface
<… output omitted …>

Note The sw itch w ill take approximately 5 minutes to reload.

Note At this point the sw itch is in a “new ” state, meaning that this is the state of the sw itch w hen you
receive it from your vendor.

Step 7 Due to the fact you erased the startup configuration file the switch will have no usable
configuration and attempt to use Power On Auto Provisioning (POAP) in order to find a usable
configuration. When you are prompted by the switch to Abort Auto Provisioning and
continue with normal setup type “y” and press Enter.

<… output omitted …>

2016 May 24 11:46:18 switch %$ VDC-1 %$ %POAP-2-POAP_INFO: - Abort Power On Auto
Provisioning and continue with normal setup ?(yes/no)[n]: y

Note It may be several seconds before the next question appears.

Step 8 The switch will then ask if you want to enforce secure user account passwords. Type “y” and
press Enter. This will force all user accounts to use passwords that include upper-case, lower-
case, and numeric characters.

---- System Admin Account Setup ----

Do you want to enforce secure password standard (yes/no) [y]: y

Step 9 The next task is to configure the admin account password. When you are prompted to enter the
password for the admin account use the password Nterone179. Enter Nterone179 again when
asked to confirm the admin account password.

Note Use the exact passw ord and capitalization as show n. Please do not use any other passw ords in
the lab unless instructed to do so.

Enter the password for "admin": Nterone179

Confirm the password for "admin": Nterone179

Note All Cisco Nexus sw itches have a user account named “admin” w hich is the built-in superuser
account. You must configure this account, and you cannot disable or delete this account.

Note Cisco Nexus 5000 Series Sw itches implement username and passw ord authentication by
default. Unlike Cisco IOS Softw are devices, an enable passw ord alone is not sufficient, even in
the default configuration.

Step 10 The Basic System Configuration Dialog will now appear. To continue, enter yes when
prompted.

---- Basic System Configuration Dialog ----

This setup utility will guide you through the basic configuration of
the system. Setup configures only enough connectivity for management
of the system.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 89
©2016 NterOne Corporation
 Please register Cisco Nexus 5000 Family devices promptly with your
supplier. Failure to register may affect response times for initial
service calls. Nexus devices must be registered to receive entitled
support services.

Press Enter at anytime to skip a dialog. Use ctrl -c at anytime

to skip the remaining dialogs.

Would you like to enter the basic configuration dialog (yes/no) [y]: yes

Step 11 The Basic System Configuration Dialog is a menu system that will prompt for common
configuration parameters, primarily used to configure the management interface IPv4 address
for your Pod Switch. Complete the Basic System Configuration Dialog script by answering the
questions using the following information.

Create another login account (yes/no) [n]: n

Configure read-only SNMP community string (yes/no) [n]: n

Configure read-write SNMP community string (yes/no) [n]: n

Enter the switch name : N5K-PP (replace “PP” with your assigned Pod Number)

Continue with Out-of-band (mgmt0) management configuration? (yes/no) [y]: y

Note In the next question use the follow ing table to determine the Mgm t0 IPv4 Address assigned to
your Pod’s Nexus sw itch.

Pod Mgm t0 IPv4 Pod Mgm t0 IPv4 Pod Mgm t0 IPv4

Num ber Address Num ber Address Num ber Address
11 10.1.5.4 17 10.1.5.28 23 10.1.5.52
12 10.1.5.8 18 10.1.5.32 24 10.1.5.56
13 10.1.5.12 19 10.1.5.36 25 10.1.5.60
14 10.1.5.16 20 10.1.5.40 26 10.1.5.64
15 10.1.5.20 21 10.1.5.44 27 10.1.5.68
16 10.1.5.24 22 10.1.5.48 28 10.1.5.72

Mgmt0 IPv4 address : <Mgmt0 IPv4 Address>

Mgmt0 IPv4 netmask : 255.255.255.0

Configure the default gateway? (yes/no) [y]: y

IPv4 address of the default gateway : 10.1.5.1

Enable the telnet service? (yes/no) [n]: n

Enable the ssh service? (yes/no) [y]: y

Type of ssh key you would like to generate (dsa/rsa) : rsa

Number of key bits <768-2048> : 1024

Configure the ntp server? (yes/no) [n]: n

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 90
©2016 NterOne Corporation
 Enter basic FC configurations (yes/no) [n]: n

Step 12 After you have answered the questions in the Basic System Configuration Dialog the
configuration commands that will be applied to the switch will be displayed:
 If you do not want to make any changes to the initial configuration, enter “n”.
 If you want to make changes to the initial configuration (perhaps you entered the incorrect
information for a question), enter “y”. You will then be prompted to answer all of the questions in
the Basic System Configuration Dialog again.

The following configuration will be applied:

switchname N5K-PP
interface mgmt0
ip address <Mgmt0 IPv4 Address> 255.255.255.0
no shutdown
exit
vrf context management
ip route 0.0.0.0/0 10.1.5.1
exit
no telnet server enable
ssh key rsa 1024 force
ssh server enable

Would you like to edit the configuration? (yes/no) [n]: n

Step 13 You will be asked to confirm that you wish to use the configuration you created. Enter “y” to
apply the configuration to the switch and save the configuration to the startup configuration file.

Use this configuration and save it? (yes/no) [y]: y

[########################################] 100%
Copy complete, now saving to disk (please wait)...

Step 14 Log in to your Pod Switch with the following credentials:

 Username: admin
 Password: Nterone179

User Access Verification

N5K-17 login: admin
Password: Nterone179
Cisco Nexus Operating System (NX-OS) Software
TAC support: http://www.cisco.com/tac
Copyright (c) 2002-2015, Cisco Systems, Inc. All rights reserved.
The copyrights to certain works contained in this software are
owned by other third parties and used and distributed under
license. Certain components of this software are licensed under
the GNU General Public License (GPL) version 2.0 or the GNU
Lesser General Public License (LGPL) Version 2.1. A copy of each
such license is available at
http://www.opensource.org/licenses/gpl-2.0.php and
http://www.opensource.org/licenses/lgpl -2.1.php
N5K-17#

Step 15 Verify reachability from the management interface to the default gateway by entering the
ping 10.1.5.1 vrf management command.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 91
©2016 NterOne Corporation
 Note Any time that you are executing a command on a Nexus sw itch that uses layer 3 you must
specify the VRF in w hich you w ant that command to be executed.

N5K-PP# ping 10.1.5.1 vrf management

PING 10.1.5.1 (10.1.5.1): 56 data bytes
64 bytes from 10.1.5.1: icmp_seq=0 ttl=254 time=8.765 ms
64 bytes from 10.1.5.1: icmp_seq=1 ttl=254 time=1.448 ms
64 bytes from 10.1.5.1: icmp_seq=2 ttl=254 time=0.864 ms
64 bytes from 10.1.5.1: icmp_seq=3 ttl=254 time=0.842 ms
64 bytes from 10.1.5.1: icmp_seq=4 ttl=254 time=0.851 ms

--- 10.1.5.1 ping statistics ---

5 packets transmitted, 5 packets received, 0.00% packet loss
round-trip min/avg/max = 0.842/2.554/8.765 ms

Step 16 The initial switch configuration was done from the console. The console allows only one user to
access the switch at one time. Additional users can now connect via Telnet or SSH to the
switch, allowing all learners simultaneous switch access. From this point forward, multiple
administrators may be connected to the same switch. Configuration changes that are made in
one session will affect all other sessions to the same switch. Proceed with caution.
Step 17 From your Student Server desktop, use PuTTY to start an SSH session to your Pod Switch
using the following information:
 IP Address: <Mgmt0 IPv4 Address>
 Username: admin
 Password: Nterone179
Step 18 From your Student Server desktop, use PuTTY to start an SSH session to your Pod Switch.
There should be a shortcut on the Student Server desktop labeled “N5K-PP (SSH)” (replace
“PP” with your assigned 2-digit Pod Number). If there is not a PuTTY shortcut to your Pod
Switch use PuTTY to start an SSH session to the management IP address you configured in the
previous steps.

Step 19 A PuTTY Security Alert will appear due to the fact that this is the first time you are
connecting to the switch using SSH. Make a mental note of the rsa2 key fingerprint’s final few
characters.

Step 20 Click the Yes button.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 92
©2016 NterOne Corporation
 Step 21 Log in to the switch using the following information:
 Username: admin
 Password: Nterone179

login as: admin

Nexus 5000 Switch
Using keyboard-interactive authentication.
Password: Nterone179
Cisco Nexus Operating System (NX-OS) Software
TAC support: http://www.cisco.com/tac
Copyright (c) 2002-2015, Cisco Systems, Inc. All rights reserved.
The copyrights to certain works contained in this software are
owned by other third parties and used and distributed under
license. Certain components of this software are licensed under
the GNU General Public License (GPL) version 2.0 or the GNU
Lesser General Public License (LGPL) Version 2.1. A copy of each
such license is available at
http://www.opensource.org/licenses/gpl-2.0.php and
http://www.opensource.org/licenses/lgpl -2.1.php

Step 22 View the RSA key of the switch. The fingerprint listed should match the fingerprint presented
by PuTTY in the PuTTY Security Alert window. This fingerprint mechanism can be used to
verify that you are connected to the correct device.

N5K-PP# show ssh key rsa

**************************************
rsa Keys generated:Tue May 24 11:38:41 2016

ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAAAgQC/xWDuNOg5A8WCLBDfX4/UkLttKCyeOvVlbGG5SYGH
6CIGpJNdewOHazF9xyEMn8m7o/41alG9q/ToeLv5zeekP3Dn4tFKec+p3lQE6Yzfcwjvo2yszXVctxpz
JqpU8xUc7vx0zIngTDjAvLsEAAZxWn9zvYIZRgtqadikJeqQ/w==

bitcount:1024
fingerprint:
c0:db:a3:ec:a3:36:cd:49:01:07:53:b6:ab:83:07:7c
*********************************** ***

Step 23 Enter configuration mode of the switch by entering the configure command.

N5K-PP# configure
Enter configuration commands, one per line. End with CNTL/Z.
N5K-PP(config)#

Note In Cisco NX-OS Softw are, the ‘t’ (for terminal) is not required w hen entering configuration mode
(Cisco IOS uses “configure terminal”). How ever, you can type it if you like.

Step 24 Exit configuration mode by entering the end command.

N5K-PP(config)# end

Step 25 Save the running configuration to the startup configuration by entering the wr command.

N5K-PP# wr
^
% Incomplete command at '^' marker. N5K -PP#

Step 26 Save the running configuration to the startup configuration by entering the copy running-
config startup-config command, which is supported on Cisco NX-OS Software.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 93
©2016 NterOne Corporation
 N5K-PP# copy running-config startup-config
[########################################] 100%

Step 27 The <TAB> key can be used to complete the command line, in order to simplify the typing of
lengthy commands. Explore the usage of the TAB key, for example as in the following
command:

N5K-PP# copy run<TAB>

N5K-PP# copy running-config star<TAB>
N5K-PP# copy running-config startup-config
[########################################] 100%

Step 28 Many administrators prefer the ‘wr’ version of this command, which is used in Cisco IOS.
Create a CLI alias so that the ‘wr’ command can be used to save the switch configurations for
the remainder of the labs. Use the new alias to save your Pod Switch configuration.

Note An alias name cannot contain a space.

N5K-PP# configure
Enter configuration commands, one per line. En d with CNTL/Z.
N5K-PP(config)# cli alias name wr copy running-config startup-config
N5K-PP(config)# wr
[########################################] 100%

Note In the Cisco NX-OS Softw are, ‘show ’ commands and saving the configuration can be performed
from any CLI context, w ithout exiting.

Step 29 View the command aliases present on the switch by entering the alias command.

N5K-PP(config)# alias
CLI alias commands
==================
alias :show cli alias
wr :copy running-config startup-config

Step 30 Press the <TAB> key. This will list all of the commands that are available in global
configuration mode.

N5K-PP(config)#
aaa fabric mac -list role
acllog fabric-mode monitor route-map
apply fabricpath mvr-config slot
as-format feature no snmp-server
banner feature-set ntp spanning-tree
batch-mac fips onep ssh
boot hardware otv -isis switchname
callhome hostname param -list system
cdp hw-module password table -map
cfs install poap terminal
class-map interface policy-map track
cli ip pop username
clock ipv4 port -channel vdc
control-plane ipv6 port-monitor virtual-service
crypto key port -profile vlan
default l2 poweroff vni
diagnostic license push vpc
ecp line qos vrf
end lldp radius-server where

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 94
©2016 NterOne Corporation
 errdisable logging rate -limit wrr-queue
event m2rib resequence xml
exit mac rmon

Step 31 Determine the CLI context that you are currently in and your user credentials by entering the
where command. The where command is useful to determine what portion of the configuration
you are currently modifying.

N5K-PP(config)# where
conf admin@N5K-PP

Step 32 Determine the users that are currently logged into the switch and how they connected by
entering the show users command.

N5K-PP(config)# show users

NAME LINE TIME IDLE PID COMMENT
admin ttyS0 May 24 13:44 00:03 8699
admin pts/0 May 24 13:49 . 9243 (192.168.30.20) session=ssh
*

Note The ttyS0 is the console connection; pts/0 indicates remote connections such as Telnet or SSH.

Step 33 Use help (the question mark) to explore the available ‘grep’ options that are available within
the Cisco NX-OS Software. These options are available on any command.

N5K-PP(config)# show interface brief | ?

cut Print selected parts of lines.
diff Show difference between current and previous invocation (creates
temp files: remove them with 'diff-clean' command and dont use it
on commands with big outputs, like 'show tech'!)
egrep Egrep - print lines matching a pattern
grep Grep - print lines matching a pattern
head Display first lines
human Output in human format
last Display last lines
<… output omitted …>

Step 34 Exit configuration mode by entering the end command.

N5K-PP(config)# end

Step 35 Initiate an SSH session from your Pod Switch to your Peer Pod’s Nexus switch. Use the
following table to determine your Peer Pod’s Nexus Switch Mgmt0 IPv4 Address.

Your Peer Pod’s Your Peer Pod’s Your Peer Pod’s

YOUR Pod YOUR Pod YOUR Pod
Nexus Sw itch Nexus Sw itch Nexus Sw itch
Num ber Num ber Num ber
Mgm t0 IPv4 Address Mgm t0 IPv4 Address Mgm t0 IPv4 Address
11 10.1.5.8 (N5K-12) 17 10.1.5.32 (N5K-18) 23 10.1.5.56 (N5K-24)
12 10.1.5.4 (N5K-11) 18 10.1.5.28 (N5K-17) 24 10.1.5.52 (N5K-23)
13 10.1.5.16 (N5K-14) 19 10.1.5.40 (N5K-20) 25 10.1.5.64 (N5K-26)
14 10.1.5.12 (N5K-13) 20 10.1.5.36 (N5K-19) 26 10.1.5.60 (N5K-25)
15 10.1.5.24 (N5K-16) 21 10.1.5.48 (N5K-22) 27 10.1.5.72 (N5K-28)
16 10.1.5.20 (N5K-15) 22 10.1.5.44 (N5K-21) 28 10.1.5.68 (N5K-27)

N5K-PP# ssh <Peer Pod’s Nexus Switch Mgmt0 IPv4 Address> vrf management

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 95
©2016 NterOne Corporation
 The authenticity of host '10.1.5.?? (10.1.5.??)' can't be established.
RSA key fingerprint is c0:db:a3:ec:a3:36:cd:49:01:07:53:b6:ab:83:07:7c.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '10.1.5.??' (RSA) to the list of known hosts.
Nexus 5000 Switch
Password:
Cisco Nexus Operating System (NX-OS) Software
TAC support: http://www.cisco.com/tac
Copyright (c) 2002-2015, Cisco Systems, Inc. All rights reserved.
The copyrights to certain works contained in this software are
owned by other third parties and used and distributed under
license. Certain components of this software are licensed under
the GNU General Public License (GPL) version 2.0 or the GNU
Lesser General Public License (LGPL) Version 2.1. A copy of each
such license is available at
http://www.opensource.org/licenses/gpl-2.0.php and
http://www.opensource.org/licenses/lgpl -2.1.php
N5K-QQ#

Note The letters “QQ” refer to your Peer Pod Number.

Note If you receive the follow ing message WARNING: REMOTE HOST IDENTIFICATION HAS
CHANGED the Cisco Nexus host file already has a ssh key stored for this hostname. In a
production environment this w ould be a serious security issue; in this lab environment how ever
use the clear ssh hosts command to delete the hostfile to continue w ith the task.

Step 36 While connected to the peer pod switch, verify the user account and credential that you used to
log into the peer pod switch by entering the show user-account command.

N5K-QQ# show user-account

user:admin
this user account has no expiry date
roles:network-admin

Step 37 End the SSH session to the pod peer switch and return to your Pod Switch by entering the exit
command.

N5K-QQ# exit
Connection to 10.1.5.?? closed.
N5K-PP#

Activity Verification
You have completed this task when you attain these results:
 You have logged into the switch console.
 You have established connectivity from the switch to the lab management network.
 You have accessed the Pod Windows servers via RDP.
 You have used SSH to connect from the Windows server to the management IP of your Pod Switch
and the pod peer switch.
 You have used SSH to connect from your Pod Switch to the management IP of your Peer Pod’s
Nexus switch.
 All the required switch interfaces for the lab are operational.
 You have become familiar with the Cisco NX-OS Software CLI.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 96
©2016 NterOne Corporation
Task 2: Identify the Installed Hardware of the Cisco Nexus 5000 Series
Switch
During this task, you will verify the installed hardware, interfaces, and the operating environment of the
Cisco Nexus 5000 Series Switch.

Activity Procedure
Complete these steps:
Step 38 Verify the hardware and software versions of your Pod Switch by entering the show version
command.

Note The show command outputs in this task are specific to the hardw are in use. Differences in
hardw are w ill result in variations in the display. The follow ing example outputs are gathered from
a Nexus 5672UP w ithout Layer 3 daughter card.

N5K-PP# show version

Cisco Nexus Operating System (NX-OS) Software
TAC support: http://www.cisco.com/tac
Documents: http://www.cisco.com/en/US/products/ps9372/tsd_products_support_serie
s_home.html
Copyright (c) 2002-2015, Cisco Systems, Inc. All rights reserved.
The copyrights to certain works contained herein are owned by
other third parties and are used and distributed under license.
Some parts of this software are covered under the GNU Public
License. A copy of the license is available at
http://www.gnu.org/licenses/gpl.html.

Software
BIOS: version 2.1.2
loader: version N/A
kickstart: version 7.0(6)N1(1)
system: version 7.0(6)N1(1)
Power Sequencer Firmware:
Module 1: version v4.0
Module 2: version v4.0
Fabric Power Sequencer Firmware: Module 1: version v4.0
Microcontroller Firmware: version v0.0.0.15
QSFP Microcontroller Firmware:
Module 2: v2.0.0.0
SFP Microcontroller Firmware:
Module 1: v1.3.0.0
BIOS compile time: 07/16/2014
kickstart image file is: bootflash:///n6000 -uk9-kickstart.7.0.6.N1.1.bin
kickstart compile time: 4/7/2015 4:00:00 [04/07/2015 17:05:44]
system image file is: bootflash:///n6000 -uk9.7.0.6.N1.1.bin
system compile time: 4/7/2015 4:00:00 [04/07/2015 17:07:37]

Hardware
cisco Nexus 5672UP Chassis ("Nexus 5672UP Supervisor")
Intel(R) Xeon(R) CPU @ 1.80 with 8243352 kB of memory.
Processor Board ID FOC19421SQV

Device name: N5K-27

bootflash: 7692288 kB

Kernel uptime is 3 day(s), 1 hour(s), 15 minute(s), 15 second(s)

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 97
©2016 NterOne Corporation
 Last reset at 343346 usecs after Sat May 21 12:52:18 2016

Reason: Reset Requested by CLI command reload

System version: 7.0(6)N1(1)
Service:

plugin
Core Plugin, Ethernet Plugin

Step 39 Verify the operating environment of your Pod Switch by entering the show environment
command.

N5K-PP# show environment

Fan:
------------------------------------------------------
Fan Model Hw Status
------------------------------------------------------
Chassis-1 N6K-C6001-FAN-F -- ok
Chassis-2 N6K-C6001-FAN-F -- ok
Chassis-3 N6K-C6001-FAN-F -- ok
PS-1 NXA-PAC-1100W -- ok
PS-2 NXA-PAC-1100W -- failure

Temperature
-----------------------------------------------------------------
Module Sensor MajorThresh MinorThres CurTemp Status
(Celsius) (Celsius) (Celsius)
-----------------------------------------------------------------
1 Outlet 65 55 29 ok
1 Bigsur-0 125 110 46 ok
1 Bigsur-1 125 110 62 ok
1 Bigsur-2 125 110 0 ok
1 Bigsur-3 125 110 0 ok
1 Bigsur-4 125 110 0 ok
1 Bigsur-5 125 110 0 ok
1 Bigsur-6 125 110 0 ok
1 Pacifica 125 110 0 ok

Power Supply:
Voltage: 12 Volts
-----------------------------------------------------------
PS Model Input Power Current Status
Type (Watts) (Amps)
-----------------------------------------------------------
1 NXA-PAC-1100W AC 1080.00 90.00 ok
2 -- -- -- -- fail/shutdown

Mod Model Power Current Power Current Status

Requested Requested Allocated Allocated
(Watts) (Amps) (Watts) (Amps)
--- ---------------------- ------- ---------- --------- ---------- ----------
1 N5K-C5672UP-SUP 450.00 37.50 450 .00 37.50 powered-up
2 N5K-C5672UP-M6Q 200.04 16.67 200.04 16.67 powered -up

Power Usage Summary:

--------------------
Power Supply redundancy mode: Redundant
Power Supply redundancy operational mode: Non-redundant

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 98
©2016 NterOne Corporation
 Total Power Capacity 1080.00 W

Power reserved for Supervisor(s) 450.00 W

Power currently used by Modules 200.04 W

-------------
Total Power Available 429.96 W
-------------

Step 40 Determine the boot variables currently in use by your Pod Switch by entering the show boot
command. These parameters control the Cisco NX-OS Software version that will be used when
the switch reloads.

N5K-PP# show boot

Current Boot Variables:

kickstart variable = bootflash:/n6000 -uk9-kickstart.7.0.6.N1.1.bin

system variable = bootflash:/n6000-uk9.7.0.6.N1.1.bin
Boot POAP Disabled

Boot Variables on next reload:

kickstart variable = bootflash:/n6000 -uk9-kickstart.7.0.6.N1.1.bin

system variable = bootflash:/n6000-uk9.7.0.6.N1.1.bin
Boot POAP Disabled

Step 41 View the types of modules that are installed in the switch chassis by entering the show module
command.

N5K-PP# show module

Mod Ports Module-Type Model Status
--- ----- ----------------------------------- ---------------------- ------------
1 48 Nexus 5672UP Supervisor N5K -C5672UP-SUP active *
2 6 Nexus 6xQSFP Ethernet Module N5K -C5672UP-M6Q ok

Mod Sw Hw World-Wide-Name(s) (WWN)

--- -------------- ------ ----------------------------------------------------
1 7.0(6)N1(1) 1.0 --
2 7.0(6)N1(1) 1.0 --

Mod MAC-Address(es) Serial -Num

--- -------------------------------------- ----------
1 8c60.4fc0.dda8 to 8c60.4fc0.ddd7 FO C19421SQV
2 8c60.4fc0.ddd8 to 8c60.4fc0.ddef FOC19421SQV

Step 42 View the state of the interfaces of your Pod Switch by entering the
show interface brief command.

N5K-PP# show interface brief

------------------------------------------------------------- -------------------
Ethernet VLAN Type Mode Status Reason Speed Port
Interface Ch #
------------------------------------------------------------------------ --------
Eth1/1 1 eth access down Administratively down 10G(D) --
Eth1/2 1 eth access down Administratively down 10G(D) --
Eth1/3 1 eth access down Administratively down 10G(D) --
Eth1/4 1 eth access down SFP not inserted 10G(D) --
Eth1/5 1 eth access down Administratively down 10G(D) --

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 99
©2016 NterOne Corporation
 Eth1/6 1 eth access down Administratively down 10G(D) --
Eth1/7 1 eth access down SFP not inserted 10G(D) --
Eth1/8 1 eth access down SFP not inserted 10G(D) --
Eth1/9 1 eth access down Administratively down 10G(D) --
Eth1/10 1 eth access down Administratively down 10G(D) --
Eth1/11 1 eth access down SFP not inserted 10G(D) --
Eth1/12 1 eth access down SFP not inserted 10G(D) --
Eth1/13 1 eth access down SFP not inserted 10G(D) --
Eth1/14 1 eth access down SFP not inserted 10G(D) --
Eth1/15 1 eth access down SFP not inserted 10G(D) --
Eth1/16 1 eth access down SFP not inserted 10G(D) --
Eth1/17 1 eth access down SFP not inserted 10G(D) --
Eth1/18 1 eth access down SFP not inserted 10G(D) --
Eth1/19 1 eth access down SFP not inserted 10G(D) --
Eth1/20 1 eth access down SFP not inserted 10G(D) --
Eth1/21 1 eth access down SFP not inserted 10G(D) --
Eth1/22 1 eth access down SFP not inserted 10G(D) --
Eth1/23 1 eth access down SFP not inserted 10G(D) --
Eth1/24 1 eth access down SFP not inserted 10G(D) --
Eth1/25 1 eth access down SFP not inserted 10G(D) --
Eth1/26 1 eth access down SFP not inserted 10G(D) --
Eth1/27 1 eth access down SFP not inserted 10G(D) --
Eth1/28 1 eth access down SFP not inserted 10G(D) --
Eth1/29 1 eth access down SFP not inserted 10G(D) --
Eth1/30 1 eth access down SFP not inserted 10G(D) --
Eth1/31 1 eth access down SFP not inserted 10G(D) --
Eth1/32 1 eth access down SFP not inserted 10G(D) --
Eth1/33 1 eth access down Administratively down 10G(D) --
Eth1/34 1 eth access down Administratively down 10G(D) --
Eth1/35 1 eth access down SFP not inserted 10G(D) --
Eth1/36 1 eth access down SFP not inserted 10G(D) --
Eth1/37 1 eth access down SFP not inserted 10G(D) --
Eth1/38 1 eth access down SFP not inserted 10G(D) --
Eth1/39 1 eth access down SFP not inserted 10G(D) --
Eth1/40 1 eth access down SFP not inserted 10G(D) --
Eth1/41 1 eth access down SFP not inserted 10G(D) --
Eth1/42 1 eth access down SFP not inserted 10G(D) --
Eth1/43 1 eth access down SFP not inserted 10G(D) --
Eth1/44 1 eth access down SFP not inserted 10G(D) --
Eth1/45 1 eth access down SFP not inserted 10G(D) --
Eth1/46 1 eth access down SFP not inserted 10G(D) --
Eth1/47 1 eth access down SFP not inserted 10G(D) --
Eth1/48 1 eth access down SFP not inserted 10G(D) --
Eth2/1 1 eth access down SFP not inserted 40G(D) --
Eth2/2 1 eth access down SFP not inserted 40G(D) --
Eth2/3 1 eth access down SFP not inserted 40G(D) --
Eth2/4 1 eth access down SFP not inserted 40G(D) --
Eth2/5 1 eth access down SFP not inserted 40G(D) --
Eth2/6 1 eth access down SFP not inserted 40G(D) --

--------------------------------------------------------------------------------
Port VRF Status IP Address Speed MTU
--------------------------------------------------------------------------------
mgmt0 -- up 10.1.5.68 1000 1500

Step 43 View the default configuration settings for an interface of the switch by entering the
show running-config interface ethernet 1/1 all command.

Note The all command line parameter specifies to display the hidden default settings.

N5K-PP# show running-config interface ethernet 1/1 all

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 100
©2016 NterOne Corporation
 !Command: show running-config interface Ethernet1/1 all
!Time: Tue May 24 14:16:29 2016

version 7.0(6)N1(1)

interface Ethernet1/1
description [to FEX 127 Uplink 1]
shutdown
priority-flow-control mode auto
lldp transmit
lldp receive
no switchport block unicast
no switchport block multicast
hardware multicast hw-hash
no hardware vethernet mac filtering per -vlan
packet latency threshold 536870904
cdp enable
switchport
switchport mode access
no switchport monitor
no switchport dot1q ethertype
no switchport priority extend
spanning-tree port-priority 128
spanning-tree cost auto
spanning-tree link-type auto
spanning-tree port type normal
no spanning-tree bpduguard
no spanning-tree bpdufilter
speed 10000
duplex auto
flowcontrol receive off
flowcontrol send off
negotiate auto
no link debounce
no beacon
mtu 1500
delay 1
snmp trap link-status
logging event port link-status default
logging event port trunk-status default
bandwidth 10000000
no bandwidth inherit
mdix auto
storm-control broadcast level 100.00
storm-control multicast level 100.00
storm-control unicast level 100.00
no shutdown lan
load-interval counter 1 30
load-interval counter 2 300
no load-interval counter 3
medium broadcast

Step 44 Determine the installed SFP+ transceiver type for interface Ethernet 1.1 by entering the
show interface ethernet 1/1 transceiver command.

N5K-PP# show interface ethernet 1/1 transceiver

Ethernet1/1
transceiver is present
type is SFP-H10GB-CU5M
name is CISCO-MOLEX
part number is 74752-9521

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 101
©2016 NterOne Corporation
 revision is 09
serial number is MOC1941A6F0
nominal bitrate is 10300 MBit/sec
Link length supported for copper is 5 m
cisco id is --
cisco extended id number is 4

Step 45 Is the same type of SFP+ transceiver installed in all interfaces of the switch? Determining this
could take some time and require issuing commands repetitively. By using regular expression
piping of command output, repetitive command line tasks can be simplified.

N5K-PP# show interface transceiver | include name prev 3

Ethernet1/1
transceiver is present
type is SFP-H10GB-CU5M
name is CISCO-MOLEX
--
Ethernet1/2
transceiver is present
type is SFP-H10GB-CU5M
name is CISCO-MOLEX
--
Ethernet1/3
transceiver is present
type is SFP-H10GB-CU5M
name is CISCO-MOLEX
--
Ethernet1/5
transceiver is present
type is SFP-H10GB-CU1M
name is CISCO-OEM
--
Ethernet1/6
transceiver is present
type is SFP-H10GB-CU1M
name is OEM
--
Ethernet1/9
transceiver is present
type is SFP-H10GB-CU3M
name is CISCO-MOLEX
--
Ethernet1/10
transceiver is present
type is SFP-H10GB-CU3M
name is CISCO-TYCO
--
Ethernet1/33
transceiver is present
type is 1Gbase-CISCO-AVAGO
name is CISCO-AVAGO
--
Ethernet1/34
transceiver is present
type is 1Gbase-CISCO-AVAGO
name is CISCO-AVAGO

Note The show interface <interface> capabilities command may also be used to determine interface
transceiver information, in addition to other interface capabilities.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 102
©2016 NterOne Corporation
 Step 46 View the IP addresses configured on the switch by entering the show ip interface brief vrf all
command.

N5K-PP# show ip interface brief vrf all

IP Interface Status for VRF "default"(1)
Interface IP Address Interface Status

IP Interface Status for VRF "management"(2)

Interface IP Address Interface Status
mgmt0 10.1.5.?? protocol -up/link-up/admin-up

Step 47 Verify that there is a default route present in the management VRF by entering the show ip
route vrf management command.

N5K-PP# show ip route vrf management

IP Route Table for VRF "management"
'*' denotes best ucast next-hop
'**' denotes best mcast next-hop
'[x/y]' denotes [preference/metric]
'%<string>' in via output denotes VRF <string>

0.0.0.0/0, ubest/mbest: 1/0

*via 10.1.5.1, [1/0], 3d01h, static
10.1.5.0/24, ubest/mbest: 1/0, attached
*via 10.1.5.??, mgmt0, [0/0], 3d01h, direct
10.1.5.??/32, ubest/mbest: 1/0, attached
*via 10.1.5.??, mgmt0, [0/0], 3d01h, local

Activity Verification
You have completed this task when you attain these results:
 You have verified the installed hardware and interface types of your Pod Switch.
 You have verified the boot variables of your Pod Switch.
 You have configured interface descriptions for all in use interfaces of your Pod Switch.
 You have determined the interface capabilities and installed transceivers of your Pod Switch.
 You have verified basic interface operation on your Pod Switch.
 You have verified the contents of the management VRF routing table.

Task 3: Initial Switch Configuration

During this task, you will perform an initial configuration of the Cisco Nexus 5000 Series Switch and
configure basic operational parameters.

Activity Procedure
Complete these steps:
Step 48 View the Cisco devices connected to your Pod Switch by entering the show cdp neighbors
command. You should see two entries for the connections to your Peer Pod’s Switch and one
entry for the connection between the mgmt0 interface and an external switch.

N5K-PP# 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, D - Remotely-Managed-Device,
s - Supports-STP-Dispute

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 103
©2016 NterOne Corporation
 Device-ID Local Intrfce Hldtme Capability Platform Port ID
N1-B2-SW1.ad.lab mgmt0 132 S I WS-C3560-48TS Fas0/13
N5K-QQ(SSI1751086N)
Eth1/5 161 R S I s N5K -C5548UP Eth1/5
N5K-QQ(SSI1751086N)
Eth1/6 161 R S I s N5K -C5548UP Eth1/6

Step 49 Ethernet interfaces 1/11 and 1/12 are not connected to other devices. Ensure that they are
administratively disabled.

N5K-PP# configure
N5K-PP(config)# interface ethernet 1/11-12
N5K-PP(config-if-range)# shutdown

Step 50 Assign descriptions to all the Ethernet interfaces that are used in this class.

N5K-PP(config-if)# int e1/1-2

N5K-PP(config-if-range)# description Connection to Pod FEX
N5K-PP(config-if-range)# int e1/3
N5K-PP(config-if)# description Connection to Peer Pod FEX
N5K-PP(config-if)# int e1/5-6
N5K-PP(config-if-range)# description Connection to Peer Pod Switch
N5K-PP(config-if-range)# int e1/9
N5K-PP(config-if)# description Connection to Pod Server
N5K-PP(config-if)# int e1/10
N5K-PP(config-if)# description Connection to Peer Pod Server

Step 51 Verify that the descriptions are applied to the correct interfaces by entering the show interface
description | include Connection command.

N5K-PP(config-if)# show interface description | include Connection

Eth1/1 eth 10G Connection to Pod FEX
Eth1/2 eth 10G Connection to Pod FEX
Eth1/3 eth 10G Connection to Peer Pod FEX
Eth1/5 eth 10G Connection to Peer Pod Switch
Eth1/6 eth 10G Connection to Peer Pod Switch
Eth1/9 eth 10G Connection to Pod Server
Eth1/10 eth 10G Connection to Peer Pod Server

Step 52 Disable the console port session timeout and then exit configuration mo de.

N5K-PP(config-if)# line console

N5K-PP(config-console)# exec-timeout 0
N5K-PP(config-console)# end
N5K-PP#

Step 53 Save the switch configuration using the configured alias.

N5K-PP# wr
[########################################] 100%
Copy complete, now saving to disk (please wait)...
N5K-PP#

Activity Verification
You have completed this task when you attain these results:
 You have verified all interfaces required for the lab are operational.
 You have configured descriptions on all the required interfaces.
 You have shut down any unused interfaces.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 104
©2016 NterOne Corporation
  You have configured a default route in the management VRF.
 You have saved the switch configuration to disk using the CLI alias wr.

Task 4: Checkpoints and Rollback

This exercise will familiarize you with creating and utilizing a configuration checkpoint and rollback. This
exercise allows you to name and retrieve the saved running configuration from a particular point in time.
Creating a checkpoint is a convenient feature that allows you to revert to an older running configuration. An
older running configuration may be required because of configuration error or instability of the existing
configuration.

Activity Procedure
Complete these steps:
Step 54 View the running configuration by entering the show running-config command.
Step 55 Create a checkpoint for the current configuration named “lab1” by entering the checkpoint
lab1 command.

N5K-PP# checkpoint lab1

Done

Step 56 Verify the newly created checkpoint by entering the show checkpoint summary command.

N5K-PP# show checkpoint summary

User Checkpoint Summary
--------------------------------------------------------------------------------
1) lab1:
Created by admin
Created at Tue, 16:11:58 24 May 2016
Size is 8,496 bytes
Description: None

Step 57 Modify the running configuration by changing the hostname of the device to N5K-modified.

N5K-PP# configure
N5K-PP(config)# switchname N5K-modified
N5K-modified(config)# end

Step 58 Verify that the name of the switch has changed in running configuration by entering the show
running-config | include switchname command.

N5K-modified# show running-config | include switchname

switchname N5K-modified

Step 59 Perform a rollback to the “lab1” checkpoint by entering the rollback running-config
checkpoint lab1 command.

N5K-modified(config)# rollback running-config checkpoint lab1

Collecting Running-Config
Generating Rollback patch for switch profile
Rollback Patch is Empty
Note: Applying config parallelly may fail Rollback verification
Collecting Running-Config
#Generating Rollback Patch
Executing Rollback Patch
Generating Running-config for verification
Generating Patch for verification

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 105
©2016 NterOne Corporation
 Rollback completed successfully.

N5K-PP#

Step 60 Verify that the name of the switch has changed back to the correct value by entering the show
running-config | include switchname command.

N5K-PP# show running-config | include switchname

switchname N5K-PP

Activity Verification
You have completed this task when you attain these results:
 You have verified all interfaces required for the lab are operational.
 You have configured descriptions on all the required interfaces.
 You have shut down some unused interfaces.
 You have saved the switch configuration to disk using the CLI alias wr.
 You have created a configuration checkpoint.
 You have made some changes to the configuration, and you have successfully rolled back to the
previous checkpoint

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 106
©2016 NterOne Corporation
Lab 9: Initial Cisco MDS Switch Configuration
Complete this lab activity to practice what you learned in the related module.

Activity Objectives
In this activity, you will perform the tasks necessary to configure a Cisco MDS 9000 Series switch. After
completing this activity, you will be able to meet the following objectives:
 Perform the initial setup of a new Cisco MDS switch
 Create VSANs
 Configure NTP
 Configure fabric interfaces
 Configure device aliases

Task 1: System Reset and Familiarization

In this task, you will observe how to erase the configuration and use the Basic System Configuration Dialog
to perform the initial configuration of a Cisco MDS switch.

Activity Procedure
Complete these steps:
Step 1 Verify that you are currently logged in to your Student Server.
Step 2 From your Student Server desktop, start a session to the console port of your Pod MDS switch
by using the PuTTY shortcut to MDS-PP (Console) (replace “PP” with your assigned 2-digit
Pod Number).

Step 3 If you do not see login prompt press <Enter> once or twice; this will cause the login prompt to
be displayed.
Step 4 Log in to the switch with the following credentials:
 Username: admin
 Password: Nterone179

MDS-PP login: admin

Password: Nterone179
Cisco Nexus Operating System (NX-OS) Software
TAC support: http://www.cisco.com/tac
Copyright (c) 2002-2013, Cisco Systems, Inc. All rights reserved.
The copyrights to certain works contained in this software are
owned by other third parties and used and distributed under
license. Certain components of this software are licensed under
the GNU General Public License (GPL) version 2.0 or the GNU
Lesser General Public License (LGPL) Version 2.1. A copy of each
such license is available at
http://www.opensource.org/licenses/g pl-2.0.php and
http://www.opensource.org/licenses/lgpl -2.1.php
MDS-PP#

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 107
©2016 NterOne Corporation
 Step 5 Erase the startup configuration file by entering the write erase command. When prompted if
you wish to proceed, type “y” and press Enter.

MDS-PP# write erase

Warning: This command will erase the startup-configuration.
Do you wish to proceed anyway? (y/n) [n] y

Step 6 Reload the switch by entering the reload command. When prompted if you wish to proceed,
type “y” and press Enter.

MDS-PP# reload
This command will reboot the system. (y/n)? [n] y
2014 Dec 24 18:13:38 MDS-PP %$ %PLATFORM-2-PFM_SYSTEM_RESET: Manual system restart
from Command Line Interface
<… output omitted …>

Note The sw itch w ill take approximately 5 minutes to reload.

Note At this point the sw itch is in a “new ” state, meaning that this is the state of the sw itch w hen you
receive it from your vendor.

Step 7 After the switch finishes reloading, the first question it will ask is if you want to enforce secure
user account passwords. Type “y” and press Enter. This will force all user accounts to use
passwords that include upper-case, lower-case, and numeric characters.

Note You w ill probably see additional log messages appear after this question appears, w hich is
normal.

---- System Admin Account Setup ----

Do you want to enforce secure password standard (yes/no) [y]: y

Step 8 The next task is to configure the admin account password. When you are prompted to enter the
password for the admin account use the password Nterone179. Enter Nterone179 again when
asked to confirm the admin account password.

Note Use the exact passw ord and capitalization as show n. Please do not use any other passw ords in
the lab unless instructed to do so.

Enter the password for "admin": Nterone179

Confirm the password for "admin": Nterone179

Note All Cisco MDS sw itches have a user account named “admin” w hich is the built-in superuser
account. You must configure this account, and you cannot disable or delete this account.

Step 9 The Basic System Configuration Dialog will now appear. To continue, enter yes when
prompted.

---- Basic System Configuration Dialog ----

This setup utility will guide you through the basic configuration of
the system. Setup configures only enough connectivity for management
of the system.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 108
©2016 NterOne Corporation
 Please register Cisco MDS 9000 Family devices promptly with your
supplier. Failure to register may affect response times for initial
service calls. MDS devices must be registered to receive entitled
support services.

Press Enter at anytime to skip a dialog. Use ctrl -c at anytime

to skip the remaining dialogs.

Would you like to enter the basic configuration dialog (yes/no): yes

Step 10 Complete the Basic System Configuration Dialog script by answering the questions using the
following information.

Create another login account (yes/no) [n]: n

Configure read-only SNMP community string (yes/no) [n]: n

Configure read-write SNMP community string (yes/no) [n]: n

Enter the switch name : MDS-PP

Continue with Out-of-band (mgmt0) management configuration? (yes/no) [y]: y

Note In the next question use the follow ing table to determine the Mgm t0 IPv4 Address assigned to
your Pod’s MDS sw itch.

Pod Mgm t0 IPv4 Pod Mgm t0 IPv4 Pod Mgm t0 IPv4

Num ber Address Num ber Address Num ber Address
11 10.1.5.6 17 10.1.5.30 23 10.1.5.54
12 10.1.5.10 18 10.1.5.34 24 10.1.5.58
13 10.1.5.14 19 10.1.5.38 25 10.1.5.62
14 10.1.5.18 20 10.1.5.42 26 10.1.5.66
15 10.1.5.22 21 10.1.5.46 27 10.1.5.70
16 10.1.5.26 22 10.1.5.50 28 10.1.5.74

Mgmt0 IPv4 address : <Mgmt0 IPv4 Address>

Mgmt0 IPv4 netmask : 255.255.255.0

Configure the default gateway? (yes/no) [y]: y

IPv4 address of the default gateway : 10.1.5.1

Configure advanced IP options? (yes/no) [n]: n

Enable the ssh service? (yes/no) [y]: y

Type of ssh key you would like to generate (dsa/rsa) [rsa]: rsa

Number of rsa key bits <1024-2048> [1024]: 1024

Enable the telnet service? (yes/no) [n]: y

Configure congestion/no_credit drop for fc interfaces? (yes/no) [q/quit] to

quit [y]: y

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 109
©2016 NterOne Corporation
 Enter the type of drop to configure congestion/no_credit drop? (con/no) [c]: c
Enter number of milliseconds for congestion/no_credit drop[100 - 1000] or
[d/default] for default: d
Enter mode for congestion/no_credit drop[E/F]: E

Enable the http-server? (yes/no) [y]: y

Configure clock? (yes/no) [n]: n

Configure timezone? (yes/no) [n]: n

Configure summertime? (yes/no) [n]: n

Configure the ntp server? (yes/no) [n]: n

Configure default switchport interface state (shut/noshut) [shut]: shut

Configure default switchport trunk mode (on/off/auto) [on]: on

Configure default switchport port mode F (yes/no) [n]: n

Configure default zone policy (permit/deny) [deny]: deny

Enable full zoneset distribution? (yes/no) [n]: n

Configure default zone mode (basic/enhanced) [basic]: basic

Step 11 After you have answered the questions in the Basic System Configuration Dialog the
configuration commands that will be applied to the switch will be displayed:
 If you do not want to make any changes to the initial configuration, enter “n”.
 If you want to make changes to the initial configuration (perhaps you entered the incorrect
information for a question), enter “y”. You will then be prompted to answer all of the questions in
the Basic System Configuration Dialog again.

The following configuration will be applied:

password strength-check
switchname MDS-PP
interface mgmt0
ip address <Mgmt0 IPv4 Address> 255.255.255.0
no shutdown
ip default-gateway 10.1.5.1
ssh key rsa 1024 force
feature ssh
no feature telnet
system timeout congestion-drop default mode E
feature http-server
system default switchport shutdown
system default switchport trunk mode on
no system default zone default-zone permit
no system default zone distribute full
no system default zone mode enhanced

Would you like to edit the configuration? (yes/no) [n]: n

Step 12 You will be asked to confirm that you wish to use the configuration you created. Enter “y” to
apply the configuration to the switch and save the configuration to the startup configuration file.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 110
©2016 NterOne Corporation
 Use this configuration and save it? (yes/no) [y]: y

[########################################] 100%
Copy complete, now saving to disk (please wait)...

Step 13 Log in to your Pod MDS with the following credentials:

 Username: admin
 Password: Nterone179

MDS-PP login: admin

Password: Nterone179
Cisco Nexus Operating System (NX-OS) Software
TAC support: http://www.cisco.com/tac
Copyright (c) 2002-2014, Cisco Systems, Inc. All rights reserved.
The copyrights to certain works contained in this software are
owned by other third parties and used and distributed under
license. Certain components of this software are licensed under
the GNU General Public License (GPL) version 2.0 or the GNU
Lesser General Public License (LGPL) Version 2.1. A copy of each
such license is available at
http://www.opensource.org/licenses/gpl-2.0.php and
http://www.opensource.org/licenses/lgpl -2.1.php
MDS-PP#

Step 14 Verify reachability to the default gateway by entering the ping 10.1.5.1 command.

Note You w ill need to press <CTRL>+<C> to stop the ping; this is standard on Cisco MDS series
sw itches. Also, Cisco MDS series sw itches do not use VRFs.

MDS-PP# ping 10.1.5.1

PING 10.1.5.1 (10.1.5.1): 56 data bytes
64 bytes from 10.1.5.1: icmp_seq=0 ttl=254 time=1.033 ms
64 bytes from 10.1.5.1: icmp_seq=1 ttl=254 time=0.811 ms
64 bytes from 10.1.5.1: icmp_seq=2 ttl=254 time=0.797 ms
64 bytes from 10.1.5.1: icmp_seq=3 ttl=254 time=0.893 ms
64 bytes from 10.1.5.1: icmp_seq=4 ttl=254 time=0.782 ms
^C
--- 10.1.5.1 ping statistics ---
5 packets transmitted, 5 packets received, 0.00% packet loss
round-trip min/avg/max = 0.782/0.863/1.033 ms

Step 15 Close your PuTTY session to the Pod MDS console.

Activity Verification
You have completed this task when you attain these results:
 The configuration of the switch is erased
 The Basic System Configuration Dialog was used to perform the initial configuration of the switch
 Connectivity to the management network has been verified

Task 2: Identify the Installed Hardware of the Cisco MDS Switch

During this task, you will verify the installed hardware, interfaces, and the operating environment of the
Cisco MDS switch.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 111
©2016 NterOne Corporation
Activity Procedure
Complete these steps:
Step 16 From your Student Server desktop use the PuTTY application to open an SSH session to your
assigned Pod MDS Switch. Use the following username and password:
 Username: admin
 Password: Nterone179
The following table contains the management address of the MDS switch assigned to your Pod.

Note There may be preconfigured shortcuts to these devices on the Student Server desktop.

Pod MDS Pod MDS Pod MDS

Your Assigned Pod Pod
Managem ent Managem ent Managem ent
Pod Num ber Num ber Num ber
Address Address Address
11 10.1.5.6 17 10.1.5.30 23 10.1.5.54
12 10.1.5.10 18 10.1.5.34 24 10.1.5.58
13 10.1.5.14 19 10.1.5.38 25 10.1.5.62
14 10.1.5.18 20 10.1.5.42 26 10.1.5.66
15 10.1.5.22 21 10.1.5.46 27 10.1.5.70
16 10.1.5.26 22 10.1.5.50 28 10.1.5.74

Step 17 Verify the hardware and software versions of your Pod MDS by entering the show version
command.

MDS-PP# show version

Cisco Nexus Operating System (NX-OS) Software
TAC support: http://www.cisco.com/tac
Documents: http://www.cisco.com/en/US/products/ps9372/t sd_products_support_serie
s_home.html
Copyright (c) 2002-2013, Cisco Systems, Inc. All rights reserved.
The copyrights to certain works contained herein are owned by
other third parties and are used and distributed under license.
Some parts of this software are covered under the GNU Public
License. A copy of the license is available at
http://www.gnu.org/licenses/gpl.html.

Software
BIOS: version 1.0.17
loader: version N/A
kickstart: version 5.2(8c)
system: version 5.2(8c)
BIOS compile time: 05/28/09
kickstart image file is: bootflash:/m9100 -s2ek9-kickstart-mz.5.2.8c.bin
kickstart compile time: 12/25/2020 12:00:00 [10/23/2013 07:34:26]
system image file is: bootflash:/m9100 -s2ek9-mz.5.2.8c.bin
system compile time: 9/16/2013 12:00:00 [10/23/2013 07:57:09]

Hardware
cisco MDS 9124 (1 Slot) Chassis ("1/2/4 Gbps FC/Supervisor -2")
Motorola, e500 with 516128 kB of memory.
Processor Board ID JAF1333BPRP

Device name: MDS-PP

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 112
©2016 NterOne Corporation
 bootflash: 254464 kB
Kernel uptime is 0 day(s), 0 hour(s), 45 minute(s), 4 second(s)

Last reset at 843757 usecs after Fri Jun 17 08:15:41 2016

Reason: Reset Requested by CLI command reload

System version: 5.2(8c)
Service:

Step 18 Verify the operating environment of your Pod MDS by entering the show environment
command.

Note Some of the Pod MDS sw itches in the NterOne lab have only one pow er supply installed.

MDS-PP# show environment

Clock:
----------------------------------------------------------
Clock Model Hw Status
----------------------------------------------------------
A Clock Module -- NotSupported/None

Fan:
------------------------------------------------------
Fan Model Hw Status
------------------------------------------------------
ChassisFan1 FAN Module 1 -- Ok
ChassisFan2 FAN Module 2 -- Ok
ChassisFan3 FAN Module 3 -- Ok
Fan_in_PS1 -- -- Failure
Fan_in_PS2 -- -- Ok
Fan Air Filter : NotSupported

Temperature:
--------------------------------------------------------------------
Module Sensor MajorThresh MinorThres CurTemp Status
(Celsius) (Celsius) (Celsius)
--------------------------------------------------------------------
1 Outlet 75 60 37 Ok
1 Outlet 75 60 38 Ok
1 Intake 65 50 35 Ok

Power Supply:
Voltage: 42 Volts
--------------------------------------------- --------
PS Model Power Power Status
(Watts) (Amp)
-----------------------------------------------------
1 ------------ 0.00 0.00 Fail/Shut
2 DS-C24-300AC 299.88 7.14 Ok

Mod Model Power Power Power Power Status

Requested Requested Allocated Allocated
(Watts) (Amp) (Watts) (Amp)
--- ------------------- ------- ---------- --------- ---------- ----------
1 DS-C9124-K9-SUP 209.16 4.98 209.16 4.98 Powered -Up

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 113
©2016 NterOne Corporation
 Power Usage Summary:
--------------------
Power Supply redundancy mode: Redundant
Power Supply redundancy operational mode: Redundant

Total Power Capacity 299.88 W

Power reserved for Supervisor(s) 209.16 W

Power reserved for Fan Module(s) 42.00 W
-------------
Total Power Available 48.72 W
-------------

Step 19 Determine the boot variables currently in use by your Pod MDS by entering the show boot
command. These parameters control the Cisco NX-OS Software version that will be used when
the switch reloads.

MDS-PP# show boot

Current Boot Variables:

kickstart variable = bootflash:/m9100 -s2ek9-kickstart-mz.5.2.8c.bin

system variable = bootflash:/m9100-s2ek9-mz.5.2.8c.bin
No module boot variable set

Boot Variables on next reload:

kickstart variable = bootflash:/m9100 -s2ek9-kickstart-mz.5.2.8c.bin

system variable = bootflash:/m9100-s2ek9-mz.5.2.8c.bin
No module boot variable set

Step 20 View the types of modules that are installed in the switch chassis by entering the show module
command.

MDS-PP# show module

Mod Ports Module-Type Model Status
--- ----- ----------------------------------- ------------------ ----------
1 24 1/2/4 Gbps FC/Supervisor -2 DS-C9124-K9-SUP active *

Mod Sw Hw World-Wide-Name(s) (WWN)

--- -------------- ------ ----------------------------------------------- ---
1 5.2(8c) 5.1 20:01:00:0d:ec:da:78:c0 to 20:18:00:0d:ec:da:78:c0

Mod MAC-Address(es) Serial -Num

--- -------------------------------------- ----------
1 00-0d-ec-be-b2-d4 to 00-0d-ec-be-b2-d8 JAF1333BPRP

* this terminal session

Step 21 View the state of the interfaces of your Pod MDS by entering the show interface brief
command.

MDS-PP# show interface brief

-------------------------------------------------------------------------------
Interface Vsan Admin Admin Status SFP Oper Oper Port
Mode Trunk Mode Speed Channel
Mode (Gbps)
--------------------------------------------------------------- ----------------
fc1/1 1 auto on down swl -- --

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 114
©2016 NterOne Corporation
 fc1/2 1 auto on down swl -- --
fc1/3 1 auto on down swl -- --
fc1/4 1 auto on sfpAbsent -- -- --
fc1/5 1 auto on sfpAbsent -- -- --
fc1/6 1 auto on sfpAbsent -- -- --
fc1/7 1 auto on sfpAbsent -- -- --
fc1/8 1 auto on sfpAbsent -- -- --
fc1/9 1 auto on sfpAbsent -- -- --
fc1/10 1 auto on sfpAbsent -- -- --
fc1/11 1 auto on sfpAbsent -- -- --
fc1/12 1 auto on sfpAbsent -- -- --
fc1/13 1 auto on sfpAbsent -- -- --
fc1/14 1 auto on sfpAbsent -- -- --
fc1/15 1 auto on sfpAbsent -- -- --
fc1/16 1 auto on sfpAbsent -- -- --
fc1/17 1 auto on sfpAbsent -- -- --
fc1/18 1 auto on sfpAbsent -- -- --
fc1/19 1 auto on sfpAbsent -- -- --
fc1/20 1 auto on sfpAbsent -- -- --
fc1/21 1 auto on sfpAbsent -- -- --
fc1/22 1 auto on sfpAbsent -- -- --
fc1/23 1 auto on sfpAbsent -- -- --
fc1/24 1 auto on sfpAbsent -- -- --

-------------------------------------------------------------------------------
Interface Status Speed
(Gbps)
----------------------------------------------------------------- --------------
sup-fc0 up 1

-------------------------------------------------------------------------------
Interface Status IP Address Speed MTU
-------------------------------------------------------------------------------
mgmt0 up 10.1.5.??/24 100 Mbps 1500

Step 22 Determine the installed SFP+ transceiver type for interface fc 1.1 by entering the
show interface fc 1/1 transceiver command.

MDS-PP# show interface fc 1/1 transceiver

fc1/1 sfp is present
Name is CISCO-AVAGO
Manufacturer's part number is SFBR-5799APZ
Revision is
Serial number is A4A1220HYRC
Cisco part number is 10-2195-01
Cisco pid is DS-SFP-FC4G-SW
FC Transmitter type is short wave laser w/o OFC (SN)
FC Transmitter supports intermediate distance link length
Transmission medium is multimode laser with 62.5 um aperture (M6)
Supported speeds are - Min speed: 1000 Mb/s, Max speed: 4000 Mb/s
Nominal bit rate is 4300 Mb/s
Link length supported for 50/125mm fiber is 150 m
Link length supported for 62.5/125mm fiber is 70 m
Cisco extended id is unknown (0x0)

No tx fault, no rx loss, in sync state, diagnostic monitoring type is 0x68

SFP Diagnostics Information:
Temperature : 30.52 C
Voltage : 3.32 V
Current : 0.00 mA --
Optical Tx Power : N/A dBm --
Optical Rx Power : -3.78 dBm

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 115
©2016 NterOne Corporation
 Tx Fault count : 0
Note: ++ high-alarm; + high-warning; -- low-alarm; -low-warning

Step 23 Is the same type of SFP+ transceiver installed in all interfaces of the switch? Determining this
could take some time and require issuing commands repetitively. By using regular expression
piping of command output, repetitive command line tasks can be simplified.

MDS-PP# show interface transceiver | include Name prev 1

fc1/1 sfp is present
Name is CISCO-AVAGO
--
Note: ++ high-alarm; + high-warning; -- low-alarm; -low-warning

fc1/2 sfp is present

Name is CISCO-AVAGO
--
Note: ++ high-alarm; + high-warning; -- low-alarm; -low-warning

fc1/3 sfp is present

Name is CISCO-FINISAR
MDS-PP# show interface transceiver | include Name prev 1
fc1/1 sfp is present
Name is CISCO-AVAGO
--
fc1/2 sfp is present
Name is CISCO-AVAGO
--
fc1/3 sfp is present
Name is CISCO-FINISAR

Activity Verification
You have completed this task when you attain these results:
 You have verified the installed hardware and interface types of your Pod MDS.
 You have verified the boot variables of your Pod MDS.
 You have determined the interface capabilities and installed transceivers of your Pod MDS.

Task 3: Enable NX-OS Software Features

During this task, you will enable the NX-OS features that will be used by MDS-PP.

Activity Procedure
Complete these steps:
Step 24 Enter configuration mode of the Pod MDS switch.

MDS-PP# configure
Enter configuration commands, one per line. End with CNTL/Z.
MDS-PP(config)#

Step 25 Enable the NPIV feature by entering the feature npiv command.

MDS-PP(config)# feature npiv

Step 26 Verify that the features have been enabled on MDS-PP by entering the show running-config |
inc feature command.

MDS-PP(config)# show running-config | inc feature

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 116
©2016 NterOne Corporation
 feature npiv
feature telnet
rule 5 permit show feature environment
rule 4 permit show feature hardware
rule 3 permit show feature module
rule 2 permit show feature snmp
rule 1 permit show feature system

Activity Verification
You have completed this task when you attain these results:
 The NX-OS features used by the MDS switch have been enabled.

Task 4: Configure NTP

During this task, you will configure NTP on your Pod MDS so that it will synchronize it’s clock with a time
source within the NterOne data center.

Activity Procedure
Complete these steps:
Step 27 Configure the correct local timezone by entering the clock timezone command.

MDS-PP(config)# clock timezone EST -5 0

Step 28 Configure the correct daylight savings time settings by entering the
clock summer-time command.

MDS-PP(config)# clock summer-time EDT 2 sunday march 02:00 1 sunday november 02:00
60

Step 29 Configure the switch to use an external NTP time source by entering the
ntp server 10.0.99.234 command.

MDS-PP(config)# ntp server 10.0.99.234

Step 30 Verify that the switch is synchronizing with the NTP server by entering the show ntp peer-
status command. You should see the remote IP address of 10.0.99.234 with an asterisk next to
it, indicating that the local switch’s clock is synchronized to the NTP server.

Note It may take a few minutes for the sw itch to complete the NTP synchronization process.

MDS-PP(config)# show ntp peer-status

Total peers : 1
* - selected for sync, + - peer mode(active),
- - peer mode(passive), = - polled in client mode
remote local st poll reach delay
------------------------------------------------------------------------
*10.0.99.234 0.0.0.0 3 32 17 0.00037

Step 31 Verify that the clock is displaying the correct time by entering the show clock command.

MDS-PP(config)# show clock

09:36:01.439 EDT Wed Oct 14 2015

Activity Verification

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 117
©2016 NterOne Corporation
 You have completed this task when you attain these results:
 NTP has been configured on MDS-PP to synchronize the clock with an external time server.

Task 5: Configure the VSAN Database

During this task, you will configure the VSAN database on the Pod MDS. You will create the VSAN used by
Fabric A and configure interfaces to be members of the VSAN.
The NterOne Nexus 5000 labs follow the standard model of implementing two separate SAN fabrics:
 Odd-numbered N5K pods will use Fabric A (which uses VSAN 11)
 Even-numbered N5K pods will use Fabric B (which uses VSAN 12)

Activity Procedure
Complete these steps:
Step 32 Enter VSAN database configuration mode by entering the vsan database command.

MDS-PP(config)# vsan database

Step 33 Create VSAN 1X by entering the vsan 1X command. Refer to the table below to determine the
value of “X” for your assigned pod.

Your Pod Num ber Value of “X” SAN Fabric FC VSAN Num ber
11,13,15,17,19,21,23,25,27 1 A 11
12,14,16,18,20,22,24,26,28 2 B 12

Note Replace “X” w ith the value in this table in the rest of this lab exercise.

MDS-PP(config-vsan-db)# vsan 1X

Step 34 Change the VSAN membership of interfaces fc1/1 through fc1/3 by entering the
vsan 1X interface fc1/1-3 command.

MDS-PP(config-vsan-db)# vsan 1X interface fc1/1-3

Step 35 Verify that interfaces fc1/1 through fc1/3 were added to VSAN 1X by entering the show vsan
membership command.

MDS-PP(config-vsan-db)# show vsan membership

vsan 1 interfaces:
fc1/4 fc1/5 fc1/6 fc1/7
fc1/8 fc1/9 fc1/10 fc1/11
fc1/12 fc1/13 fc1/14 fc1/15
fc1/16 fc1/17 fc1/18 fc1/19
fc1/20 fc1/21 fc1/22 fc1/23
fc1/24

vsan 1X interfaces:
fc1/1 fc1/2 fc1/3

vsan 4079(evfp_isolated_vsan) interfaces:

vsan 4094(isolated_vsan) interfaces:

Step 36 Exit VSAN database configuration mode by entering the exit command.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 118
©2016 NterOne Corporation
 Note You do not have to commit changes to the VSAN database; changes to the VSAN database are
applied immediately.

MDS-PP(config-vsan-db)# exit

Step 37 Verify that VSAN 1X was created by entering the show vsan command. The operational state
of VSAN 1X will be down until at least one interface configured to use VSAN 1X is brought
up.

MDS-PP(config)# show vsan

vsan 1 information
name:VSAN0001 state:active
interoperability mode:default
loadbalancing:src-id/dst-id/oxid
operational state:down

vsan 11 information
name:VSAN0011 state:active
interoperability mode:default
loadbalancing:src-id/dst-id/oxid
operational state:down

vsan 4079:evfp_isolated_vsan

vsan 4094:isolated_vsan

Step 38 To simplify Fibre Channel zoning, configure a default policy of permit for VSAN 1X by
entering the zone default-zone permit vsan 1X command.

MDS-PP(config)# zone default-zone permit vsan 1X

Activity Verification
You have completed this task when you attain these results:
 The correct VSAN for your Pod MDS has been created.
 The correct interfaces have been added to the VSAN.
 Zoning has been configured to permit all devices to communicate with each other.

Task 6: Configure Fibre Channel Domain IDs

A requirement of the switches in a fibre channel SAN is each switch must have a unique domain ID for each
configured VSAN. During this task, you will configure the fibre channel domain IDs for VSAN 1 and VSAN
1X on your Pod MDS. In order to ensure all switches have a unique domain ID you will set the domain IDs
on your Pod MDS to match your Pod Number.

Activity Procedure
Complete these steps:
Step 39 Change the fibre channel domain ID for VSAN 1 and VSAN 1X to PP (replace “PP” with your
assigned Pod Number and replace “X” with the correct value).

MDS-PP(config)# fcdomain domain PP static vsan 1

MDS-PP(config)# fcdomain domain PP static vsan 1X

Step 40 In order to force your Pod MDS to use the new domain IDs the fcdomain process for each
VSAN must be restarted. Restart the fcdomain process for VSAN 1 and VSAN 1X.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 119
©2016 NterOne Corporation
 MDS-PP(config)# fcdomain restart vsan 1
MDS-PP(config)# fcdomain restart vsan 1X

Step 41 Verify that the domain IDs for the VSANs have been configured properly by entering the show
fcdomain domain-list command. At this point you should only see one entry per VSAN which
corresponds to your Pod MDS.

MDS-PP(config)# show fcdomain domain-list

VSAN 1
Number of domains: 1
Domain ID WWN
--------- -----------------------
0x??(PP) 20:01:00:0d:ec:da:78:c1 [Local] [Principal]

VSAN 1X
Number of domains: 1
Domain ID WWN
--------- -----------------------
0x??(PP) 20:0b:00:0d:ec:da:78:c1 [Local] [Principal]

Activity Verification
You have completed this task when you attain these results:
 The fibre channel domain ID for each VSAN on the Pod MDS has been configured to match the
Pod Number.

Task 7: Configure Fibre Channel Interfaces

During this task, you will configure the fibre channel interfaces in your Pod MDS that are connected to the
other devices within your Pod.

Note You w ill not see the interfaces that you configure in this task in a fully functional state until you
configure the devices that are connected to the MDS sw itches. The configuration of the other
devices w ill be performed in other lab exercises.

Activity Procedure
Complete these steps:
Step 42 Configure the interfaces to your Pod Switch by entering the following commands (replace “PP”
with your assigned 2-digit Pod Number):

MDS-PP(config)# interface fc 1/1-2

MDS-PP(config-if)# switchport description to N5K-PP
MDS-PP(config-if)# no shutdown

Step 43 Configure the interface to the core MDS switch by entering the following commands:

MDS-PP(config-if)# interface fc 1/3

MDS-PP(config-if)# switchport description to core MDS switch
MDS-PP(config-if)# no shutdown

Step 44 Determine the state of the three interfaces you just configured by entering the
show interface fc1/1-3 brief command. At this point you should see interface fc1/3 in a
trunking state; this is the connection to the core MDS switch for your Fabric. Interfaces fc1/1-2
will be in the notConnected state since the Pod Switch has yet to be configured.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 120
©2016 NterOne Corporation
 MDS-PP(config-if)# show interface fc1/1-3 brief

--------------------------------------------------------------------- ----------
Interface Vsan Admin Admin Status SFP Oper Oper Port
Mode Trunk Mode Speed Channel
Mode (Gbps)
-------------------------------------------------------------------------------
fc1/1 1X auto on notConnected swl -- --
fc1/2 1X auto on notConnected swl -- --
fc1/3 1X auto on trunking swl TE 4 --

Step 45 Examine the state of interface fc1/3 by entering the show interface fc1/3 command. You
should see the interface is in TE (trunked expansion) mode and that VSANs 1 and 1X are in an
up state on the trunk.

Note Auto-detection of the interface speed is enabled by default; the devices on each end of a
connection w ill determine the maximum speed that is possible w ith the hardw are present. The
negotiation of the speed is per the fibre channel standard; any device that you connect to the
MDS sw itch should support auto-detection of speed as w ell.

MDS-PP# show interface fc1/3

fc1/3 is trunking
Port description is to core MDS switch
Hardware is Fibre Channel, SFP is short wave laser w/o OFC (SN)
Port WWN is 20:03:00:0d:ec:da:78:c0
Peer port WWN is 20:01:00:0d:ec:5f:72:40
Admin port mode is auto, trunk mode is on
snmp link state traps are enabled
Port mode is TE
Port vsan is 1X
Speed is 4 Gbps
Rate mode is dedicated
Transmit B2B Credit is 16
Receive B2B Credit is 16
B2B State Change Number is 14
Receive data field Size is 2112
Beacon is turned off
Trunk vsans (admin allowed and active) (1,1X)
Trunk vsans (up) (1,1X)
Trunk vsans (isolated) ()
Trunk vsans (initializing) ()
5 minutes input rate 568 bits/sec, 71 bytes/sec, 0 frames/sec
5 minutes output rate 296 bits/sec, 37 bytes/sec, 0 frames/sec
20413 frames input, 2161964 bytes
0 discards, 0 errors
0 CRC, 0 unknown class
0 too long, 0 too short
20141 frames output, 1306848 bytes
0 discards, 0 errors
1 input OLS, 2 LRR, 0 NOS, 0 loop inits
1 output OLS, 1 LRR, 0 NOS, 1 loop inits
16 receive B2B credit remaining
16 transmit B2B credit remaining
14 low priority transmit B2B credit remaining
Interface last changed at Fri Jun 17 13:42:37 2016

Step 46 Examine the configuration of interface fc1/3 by entering the

show running-config interface fc1/3 command. You should not see any configuration
commands that configure the interface as a trunk.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 121
©2016 NterOne Corporation
 Note The default settings of the fibre channel interfaces on an MDS sw itch are to auto-detect the
mode of the interface (in this case fc1/3 is in TE mode) and w hether it should form a trunk w ith
the device to w hich it is connected.

MDS-PP# show running-config interface fc1/3

!Command: show running-config interface fc1/3

!Time: Fri Jun 17 20:42:05 2016

version 5.2(8c)

interface fc1/3
switchport description to core MDS switch
port-license acquire
no shutdown

Step 47 Re-examine the fibre channel domain IDs that are known by the Pod MDS by entering the
show fcdomain domain-list command. At this point you should now see several other MDS
switches listed now that the connection to the core MDS switch is complete. The core MDS
switch for each Fabric is configured with domain ID 1 and is the Principal switch for the Fabric.
Your Pod MDS will have the Local flag at the end of the corresponding domain ID.

MDS-PP(config-if)# show fcdomain domain-list

VSAN 1
Number of domains: 12
Domain ID WWN
--------- -----------------------
0x01(1) 20:01:00:0d:ec:5f:72:41 [Principal]
0xa4(164) 20:01:00:0d:ec:4c:8b:41
0x??(PP) 20:01:00:0d:ec:da:78:c1 [Local]
0x1e(30) 20:01:00:0d:ec:aa:e6:c1
0x4f(79) 20:01:00:0d:ec:67:c6:01
0x91(145) 20:01:00:0d:ec:da:1f:01
0x32(50) 20:01:00:0d:ec:90:23:41
0x15(21) 20:01:00:0d:ec:63:68:c1
0x17(23) 20:01:00:0d:ec:cf:4a:81
0x7f(127) 20:01:00:0d:ec:ab:10:41
0xea(234) 20:01:00:2a:6a:06:4c:41
0xc3(195) 20:01:8c:60:4f:b7:df:81

VSAN 1X
Number of domains: 12
Domain ID WWN
--------- -----------------------
0x01(1) 20:0b:00:0d:ec:5f:72:41 [Principal]
0xe2(226) 20:0b:00:0d:ec:4c:8b:41
0x??(PP) 20:0b:00:0d:ec:da:78:c1 [Local]
0xdf(223) 20:0b:00:0d:ec:aa:e6:c1
0xde(222) 20:0b:00:0d:ec:67:c6:01
0xdd(221) 20:0b:00:0d:ec:da:1f:01
0xdc(220) 20:0b:00:0d:ec:90:23:41
0x15(21) 20:0b:00:0d:ec:63:68:c1
0x17(23) 20:0b:00:0d:ec:cf:4a:81
0xdb(219) 20:0b:00:0d:ec:ab:10:41
0xda(218) 20:0b:00:2a:6a:06:4c:41
0xd9(217) 20:0b:8c:60:4f:b7:df:81

Activity Verification

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 122
©2016 NterOne Corporation
 You have completed this task when you attain these results:
 The three interfaces connected to other devices have been configured.
 Interface fc1/3 is trunking VSAN 1 and VSAN 1X to the core MDS switch.

Task 8: Configure Device Aliases on MDS-PP

During this task, you will configure device aliases on your Pod MDS. These devices aliases will make it
easier to easily identify SAN ports and devices in the Fabric when commands are executed on the MDS
switch.

Activity Procedure
Complete these steps:
Step 48 Examine the contents of the fibre channel name server (FCNS) database by entering the
show fcns database command. At this point you should see one entry under VSAN 1X. The
entry should identify the vendor as NetApp.

MDS-PP(config-if)# show fcns database

VSAN 1X:
--------------------------------------------------------------------------
FCID TYPE PWWN (VENDOR) FC4 -TYPE:FEATURE
--------------------------------------------------------------------------
0x010000 N 50:0a:09:8?:86:78:22:ca (NetApp) scsi-fcp

Step 49 Examine additional details of the NetApp entry that are available by entering the
show fcns database fcid <FCID> detail vsan 1X command (replace <FCID> with the FCID
that you see in the output of show fcns database from the previous step). The output of this
command is similar to the output of the show cdp neighbors detail command in that the output
contains a number of details about the connected device. This information was learned when the
NetApp storage controller logged in to the fabric and is stored in the FCNS database at that
point. In a given SAN fabric the contents of the FCNS database on each SAN switch should be
identical.

MDS-PP# show fcns database fcid 0x010000 detail vsan 1X

------------------------
VSAN:1P FCID:0x010000
------------------------
port-wwn (vendor) :50:0a:09:8?:86:78:22:ca (NetApp)
node-wwn :50:0a:09:80:86:78:22:ca
class :3
node-ip-addr :0.0.0.0
ipa :ff ff ff ff ff ff ff ff
fc4-types:fc4_features :scsi-fcp
symbolic-port-name :
symbolic-node-name :
port-type :N
port-ip-addr :0.0.0.0
fabric-port-wwn :20:15:00:0d:ec:5f:72:40
hard-addr :0x000000
permanent-port-wwn (vendor) :00:00:00:00:00:00:00:00
connected interface :fc1/21
switch name (IP address) :N5K-MDS-? (10.1.5.25?)

Step 50 In the output of many MDS “show” commands there will be a long list of WWPNs. It is
difficult to determine the device that uses a given WWPN as a WWPN is displayed as a string
of hexadecimal characters. Labels can be created for each WWPN by creating entries in the

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 123
©2016 NterOne Corporation
 device-alias database. To begin the process of creating a device-alias, enter device-alias
database configuration mode by entering the device-alias database command.

MDS-PP(config)# device-alias database

Step 51 Create device aliases for each of the devices in the following table.

Alias Nam e PWWN

SAN_STORAGE_VSAN_11 50:0a:09:82:86:78:22:ca
SAN_STORAGE_VSAN_12 50:0a:09:81:86:78:22:ca

MDS-PP(config-device-alias-db)# device-alias name SAN_STORAGE_VSAN_11 pwwn

50:0a:09:82:86:78:22:ca
MDS-PP(config-device-alias-db)# device-alias name SAN_STORAGE_VSAN_12 pwwn
50:0a:09:81:86:78:22:ca

Step 52 Verify that the device aliases have been added to the database by entering the
show device-alias database command.

MDS-PP(config-device-alias-db)# show device-alias database

There are no entries in the database

Note Doh! The device aliases w ill not be placed into the database until you commit the changes.

Step 53 Commit the changes to the device-alias database by entering the

device-alias commit command.

MDS-PP(config-device-alias-db)# device-alias commit

Step 54 Verify that the device aliases have been added to the database by entering the
show device-alias database command.

MDS-PP(config)# show device-alias database

device-alias name SAN_STORAGE_VSAN_11 pwwn 50:0a:09:82:86:78:22:ca
device-alias name SAN_STORAGE_VSAN_12 pwwn 50:0a:09:81:86:78:22:ca

Total number of entries = 2

Step 55 Examine the contents of the fibre channel name server (FCNS) database again by entering the
show fcns database command. At this point the device alias for the NetApp storage controller
should be present in the row after the database entry.

Note Nearly any command that displays WWPNs w ill also display the corresponding device aliases (if
present). It is good practice to create device aliases f or each device connecting to the SAN to
simplify management and troubleshooting.

MDS-PP(config-if)# show fcns database

VSAN 1X:
--------------------------------------------------------------------------
FCID TYPE PWWN (VENDOR) FC4-TYPE:FEATURE
--------------------------------------------------------------------------
0x010000 N 50:0a:09:8?:86:78:22:ca (NetApp) scsi-fcp
[SAN_STORAGE_VSAN_1X]

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 124
©2016 NterOne Corporation
Activity Verification
You have completed this task when you attain these results:
 Device aliases have been configured for the SAN storage controllers connected to the fabric.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 125
©2016 NterOne Corporation
Lab 10: Configuring the Cisco Nexus 2000 Series
Fabric Extender
Complete this lab activity to practice what you learned in the related module.

Activity Objectives
In this activity, you will connect a Cisco Nexus 2000 Series Fabric Extender to Pod Switch. After completing
this activity, you will be able to meet these objectives:
 Establish the connection between the Cisco Nexus 2000 Series Fabric Extender and the parent Cisco
Nexus 5000 Series Switch
 Configure the Cisco Nexus 2000 Fabric Extender to support static pinning
 Configure the Cisco Nexus 2000 Fabric Extender for dynamic pinning
 Configure the Cisco Nexus 2000 Fabric Extender host interfaces

Visual Objective
Please refer to the NterOne Resource Guide for this class in order to view the lab diagrams for this lab
exercise.

Command List
The table describes the commands that are used in this activity.
Com m and Description
feature fex Enables Fabric Extender (FEX) features
show interface fex-fabric Displays all Fabric Extender fabric interfaces
show cdp neighbors Displays neighbor of devices discovered by CDP
fex <fex-id> Assigns a Fabric Extender a virtual slot number
description Assigns a description to the FEX
show fex <fex-id> Display information about a specific Fabric Extender

sw itchport mode fex-fabric Sets the interface type to be an uplink port for a Fabric
Extender.
fex associate <fex-id> Associates a Fabric Extender to a fabric interface
show fex <fex-id> transceiver detail Display the information about the FEX uplink connections
show module fex <fex-id> Displays information of the FEX virtual module
show interface capabilities Displays detailed information about one or more interfaces
show interface sw itchport Displays detailed information about one or more sw itchports
show interface brief Displays a summary of the interfaces
show mac address-table [vlan vlan-id] Displays the MAC address table for the specified VLAN
show interface transceiver Displays detailed information about installed SFPs

pinning max-links <1-8> Configures the FEX server interface to uplink interface
distribution
channel-group <number> Creates a port-channel interface
show interface port-channel 1PP brief Displays the port-channel interface information

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 126
©2016 NterOne Corporation
Task 0: Lab Preparation
In this task, you will perform the steps necessary to get ready for performing the subsequent tasks in this lab
exercise.

Activity Procedure
Complete these steps:
Step 1 Make sure that you know the value of your Pod Number. Your Pod Number is assigned to you
by your instructor and is used to identify the lab devices that you will use during this lab
exercise. Refer to the following table when a task step in this lab exercise uses a letter variable.

Value of “PP” Value of “QQ” Value of “Z”

Your Assigned Pod Num ber
(Your Pod Num ber) (Your Peer Pod Num ber) (Your Pod Pair Num ber)
11 11 12 1
12 12 11 1
13 13 14 2
14 14 13 2
15 15 16 3
16 16 15 3
17 17 18 4
18 18 17 4
19 19 20 5
20 20 19 5
21 21 22 6
22 22 21 6
23 23 24 7
24 24 23 7
25 25 26 8
26 26 25 8
27 27 28 9
28 28 27 9

Step 2 Your assigned Pod is one of two Pods within a Pod Pair. The details of each Pod Pair, including
diagrams and tables of related values, are contained in one of several NterOne Resource Guide
documents. Open the NterOne Resource Guide that corresponds to your assigned Pod Number.
Step 3 Locate the various tables that provide additional information about your assigned Pod, which
include details such as IP addresses and device login credentials.
Step 4 Locate the diagram that corresponds to this lab exercise. This diagram may help you visualize
the intended goal of this lab exercise.

Task 0.1: Log In to your Student Server and Reset the Configuration of
your Pod Switch
In order to ensure that the steps in this lab exercise function properly the running configuration of your Pod
Switch (a Cisco Nexus 5000 series switch) must be reset to the baseline configuration. During this Task you

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 127
©2016 NterOne Corporation
 will log in to your assigned Student Server and reset the configuration of your Pod Switch to the baseline
state.

Activity Procedure
Complete these steps:
Step 5 Verify that you are currently logged in to your Student Server.
Step 6 From your Student Server desktop use the PuTTY application to open an SSH session to your
assigned Pod Switch. Use the following username and password:
 Username: admin
 Password: Nterone179
The following table contains the management addresses of each switch assigned to your Pod.

Note There may be preconfigured shortcuts to these devices on the Student Server desktop.

Pod Sw itch Peer Pod Sw itch

Your Assigned Pod Sw itch Peer Pod Sw itch
Nam e Nam e
Pod Num ber Managem ent Address Managem ent Address
(N5K-PP) (N5K-QQ)
11 N5K-11 10.1.5.4 N5K-12 10.1.5.8
12 N5K-12 10.1.5.8 N5K-11 10.1.5.4
13 N5K-13 10.1.5.12 N5K-14 10.1.5.16
14 N5K-14 10.1.5.16 N5K-13 10.1.5.12
15 N5K-15 10.1.5.20 N5K-16 10.1.5.24
16 N5K-16 10.1.5.24 N5K-15 10.1.5.20
17 N5K-17 10.1.5.28 N5K-18 10.1.5.32
18 N5K-18 10.1.5.32 N5K-17 10.1.5.28
19 N5K-19 10.1.5.36 N5K-20 10.1.5.40
20 N5K-20 10.1.5.40 N5K-19 10.1.5.36
21 N5K-21 10.1.5.44 N5K-22 10.1.5.48
22 N5K-22 10.1.5.48 N5K-21 10.1.5.44
23 N5K-23 10.1.5.52 N5K-24 10.1.5.56
24 N5K-24 10.1.5.56 N5K-23 10.1.5.52
25 N5K-25 10.1.5.60 N5K-26 10.1.5.64
26 N5K-26 10.1.5.64 N5K-25 10.1.5.60
27 N5K-27 10.1.5.68 N5K-28 10.1.5.72
28 N5K-28 10.1.5.72 N5K-27 10.1.5.68

N5K-PP login: admin

Password: Nterone179

Cisco Nexus Operating System (NX-OS) Software

TAC support: http://www.cisco.com/tac
Copyright (c) 2002-2016, Cisco Systems, Inc. All rights reserved.
The copyrights to certain works contained in this software are
owned by other third parties and used and distributed under
license. Certain components of this software are licensed under

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 128
©2016 NterOne Corporation
 the GNU General Public License (GPL) version 2.0 or the GNU
Lesser General Public License (LGPL) Version 2.1. A copy of each
such license is available at
http://www.opensource.org/licenses/gpl-2.0.php and
http://www.opensource.org/licenses/lgpl-2.1.php
N5K-PP#

Step 7 Reset the running configuration to the baseline state by entering the run-script baseline
command.

N5K-PP# run-script baseline

`terminal dont-ask
`write erase
Warning: This command will erase the startup -configuration.
`copy bootflash:/configs/mgmt.txt scheduled -config
Copy complete, now saving to disk (please wait)...
`reload
[ 1047.127077] Shutdown Ports..
<… output omitted …>

Note At this point the Pod Sw itch w ill reload, and your PuTTY session w ill be terminated. It w ill take
betw een 5 and 10 minutes for the Pod Sw itch to reload; you w ill not be able to log back in to the
Pod Sw itch until the reload is complete.

Step 8 Use the PuTTY application to open a new SSH session to your assigned Pod Switch. The
credentials you should use are the same as what you used previously in this Task.

Task 1: Connect the Cisco Nexus 2000 Series Fabric Extender to the
Parent Switch
During this Task, you will configure and verify the Cisco Nexus 2000 Series Fabric Extender interfaces from
your Pod Switch.

Activity Procedure
Complete these steps:
Step 9 Enter configuration mode and enable interfaces Ethernet 1/1-3.

N5K-PP# configure
Enter configuration commands, one per line. End with CNTL/Z.
N5K-PP(config)# interface ethernet 1/1-3
N5K-PP(config-if-range)# no shutdown

Step 10 Configure your Pod Switch to support fabric extenders.

N5K-PP(config)# feature fex

Step 11 Determine if the system discovers any Cisco Nexus 2000 Series Fabric Extenders.

N5K-PP(config)# show interface fex-fabric

Fabric Fabric Fex FEX Fex
Fex Port Port State Uplink Model Serial
---------------------------------------------------------------
--- Eth1/1 Discovered 1 N2K-C2232PP-10GE SSI18070DWX
--- Eth1/2 Discovered 2 N2K-C2232PP-10GE SSI18070DWX
--- Eth1/3 Discovered 3 N2K-C2232PP-10GE SSI17410AZT

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 129
©2016 NterOne Corporation
 Note The FEX (leftmost) column is empty in the output above. This column represents the virtual slot
numbers that are occupied by the FEX in the system.

Q32) How many different FEXs did the system recognize?

Step 12 Refer to your topology diagram. There is a Cisco Nexus 2000 Series Fabric Extender connected
to your Pod Switch via interfaces Ethernet 1/1 and Ethernet 1/2. There is a different Cisco
Nexus 2000 Series Fabric Extender connected to your Pod Switch via interface Ethernet 1/3.
Step 13 Determine the CDP neighbors that are present.

N5K-PP(config)# 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, D - Remotely-Managed-Device,
s - Supports-STP-Dispute

Device-ID Local Intrfce Hldtme Capability Platform Port ID

B4-SW1.ad.lab mgmt0 144 S I WS -C2960G-48T Gig0/31

Q33) Why does the FEX not appear in the CDP display?

Q34) How does the parent switch discover it?

Step 14 Enter FEX configuration mode for FEX number 1PP (where “P” is your Pod Number), which
defines a FEX instance, and assign the FEX a description.

N5K-PP(config)# fex 1PP

N5K-PP(config-fex)# description "Lab FEX 1PP"

Step 15 Configure your Pod Switch interfaces (Ethernet 1/1-2) that connect your Pod FEX to operate as
fabric interfaces.

N5K-PP(config-fex)# interface ethernet 1/1-2

N5K-PP(config-if-range)# switchport mode fex-fabric
N5K-PP(config-if-range)# fex associate 1PP
N5K-PP(config-if-range)# end

Step 16 Verify the status of the fabric extender. The FEX connected to fabric interfaces Ethernet 1/1
and 1/2 should now be displayed as active. The FEX number that was associated to it in the
previous step should be listed in the left column.

N5K-PP# show interface fex-fabric

Fabric Fabric Fex FEX Fex
Fex Port Port State Uplink Model Serial
---------------------------------------------------------------
1PP Eth1/1 Active 1 N2K-C2232PP-10GE SSI18070DWX
1PP Eth1/2 Active 2 N2K-C2232PP-10GE SSI18070DWX
--- Eth1/3 Discovered 3 N2K-C2232PP-10GE SSI17410AZT

Step 17 Verify that the interfaces connected to the FEX are operating as fabric interfaces.

N5K-PP# show interface ethernet 1/1-2 brief

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 130
©2016 NterOne Corporation
 ------------------------------------------------------------------- -------------
Ethernet VLAN Type Mode Status Reason Speed Port
Interface Ch #
--------------------------------------------------------------------------------
Eth1/1 1 eth fabric up none 10G(D) --
Eth1/2 1 eth fabric up none 10G(D) --

Step 18 Repeat the show fex 1PP command during this time to determine what is occurring. If the FEX
state does not become Online after 5 or more minutes, please contact your instructor.
Step 19 The FEX is online and operational when the following messages appear. Be patient as it may
take a few minutes before they appear.

2016 Jul 6 19:08:30 N5K-PP %$ VDC-1 %$ %SATCTRL-FEX1PP-2-SATCTRL: FEX-1PP Module

1: Cold boot
2016 Jul 6 19:08:42 N5K-PP %$ VDC-1 %$ %PFMA-2-FEX_STATUS: Fex 1PP is online
2016 Jul 6 19:08:42 N5K-PP %$ VDC-1 %$ %NOHMS-2-NOHMS_ENV_FEX_ONLINE: FEX-1PP On-
line
2016 Jul 6 19:08:42 N5K-PP %$ VDC-1 %$ %PFMA-2-FEX_STATUS: Fex 1PP is online

Step 20 Verify the connections between the parent switch and the FEX.

N5K-PP# show fex 1PP transceiver detail

Fabric Port: Ethernet1/1

Fex Uplink: 1
sfp is present
name is CISCO-MOLEX
type is SFP-H10GB-CU5M
part number is 74752-9521
revision is 09
serial number is MOC163804WX
nominal bitrate is 10300 MBits/sec
cisco id is --
cisco extended id number is 4

DOM is not supported

Fabric Port: Ethernet1/2

Fex Uplink: 2
sfp is present
name is CISCO-MOLEX
type is SFP-H10GB-CU5M
part number is 74752-9521
revision is 09
serial number is MOC163804TQ
nominal bitrate is 10300 MBits/sec
cisco id is --
cisco extended id number is 4

DOM is not supported

<… output omitted …>

Step 21 Now that a FEX has been installed virtually in the switch chassis, an additional module will be
present in the virtual switch chassis.

N5K-PP# show module fex

FEX Mod Ports Card Type Model Status

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 131
©2016 NterOne Corporation
 --- --- ----- ---------------------------------- ------------------ -----------
1PP 1 32 Fabric Extender 32x10GE + 8x10G Module N2K -C2232PP-10GE present

FEX Mod Sw Hw World-Wide-Name(s) (WWN)

--- --- -------------- ------ -----------------------------------------------
1PP 1 7.3(0)N1(1) 5.0 --

FEX Mod MAC-Address(es) Serial -Num

--- --- -------------------------------------- ----------
1PP 1 580a.2036.b740 to 580a.2036.b75f SSI18070DWX

Step 22 Verify that all ports on the new FEX (module) are recognized.

N5K-PP# show interface ethernet 1PP/1/1-32 brief

--------------------------------------------------------------------------------
Ethernet VLAN Type Mode Status Reason Speed Port
Interface Ch #
--------------------------------------------------------------------------------
Eth1PP/1/1 1 eth access down SFP validation failed 10G(D) --
Eth1PP/1/2 1 eth access down SFP not inserted 10G(D) --
Eth1PP/1/3 1 eth access down SFP not inserted 10G(D) --
Eth1PP/1/4 1 eth access down SFP not inserted 10G(D) --
Eth1PP/1/5 1 eth access down SFP not inserted 10G(D) --
-- output omitted --

Step 23 Configure the FEX interface connecting to your Pod Server.

N5K-PP# configure
Enter configuration commands, one per line. End with CNTL/Z.
N5K-PP(config)# interface ethernet 1PP/1/1
N5K-PP(config-if)# description "Pod Server P NIC 1"
N5K-PP(config-if)# speed 1000
N5K-PP(config-if)# no shutdown
N5K-PP(config-if)# end

Step 24 Determine the switchport parameters of the FEX host interface that is up.

N5K-PP# show interface ethernet 1PP/1/1 switchport

Name: Ethernet1PP/1/1
Switchport: Enabled
Switchport Monitor: Not enabled
Operational Mode: access
Access Mode VLAN: 1 (default)
Trunking Native Mode VLAN: 1 (default)
Trunking VLANs Allowed: 1-4094
Voice VLAN: none
Extended Trust State : not trusted [COS = 0]
Administrative private-vlan primary host-association: none
Administrative private-vlan secondary host-association: none
Administrative private-vlan primary mapping: none
Administrative private-vlan secondary mapping: none
Administrative private-vlan trunk native VLAN: none
Administrative private-vlan trunk encapsulation: dot1q
Administrative private-vlan trunk normal VLANs: none
Administrative private-vlan trunk private VLANs: none
Operational private-vlan: none
Unknown unicast blocked: disabled
Unknown multicast blocked: disabled

Step 25 Determine the capabilities of the FEX interface

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 132
©2016 NterOne Corporation
 N5K-PP# show interface Ethernet1PP/1/1 capabilities
Ethernet1PP/1/2
Model: N2K-C2232PP-10GE
Type (SFP capable): 1000base-T
Speed: 1000,10000
Duplex: full
Trunk encap. type: 802.1Q
Channel: yes
Broadcast suppression: no
Flowcontrol: rx-(off/on),tx-(off/on)
Rate mode: none
QOS scheduling: rx-(6q1t),tx-(1p6q0t)
CoS rewrite: no
ToS rewrite: no
SPAN: yes
UDLD: no
MDIX: no
Link Debounce: yes
Link Debounce Time: yes
dot1Q-tunnel mode: yes
Pvlan Trunk capable: yes
TDR capable: no
FabricPath capable: no
Port mode: Switched
FEX Fabric: no

Step 26 Determine if there have been any MAC addresses that are learned on FEX host (server)
interfaces. There should be an entry for the NIC in the Pod Server.

N5K-PP# show mac address-table vlan 1

Legend:
* - primary entry, G - Gateway MAC, (R) - Routed MAC, O - Overlay MAC
age - seconds since last seen,+ - primary entry using vPC Peer-Link
VLAN MAC Address Type ag e Secure NTFY Ports/SWID.SSID.LID
---------+-----------------+--------+---------+------+----+------------------
* 1 4403.a762.2f4a dynamic 120 F F Eth1PP/1/1

Q35) Is the FEX configuration stored in the running config of the parent s witch?

Activity Verification
You have completed this task when you attain these results:
 You have enabled your Cisco Nexus 5000 Series Switch to support a Cisco Nexus 2000 Series
Fabric Extender.
 You have configured a server interface on the Cisco Nexus 2000 Series Fabric Extender.

Task 2: Configure the Cisco Nexus 2000 Series Fabric Extender to

Support Static Pinning
During this exercise, you will configure and verify your Pod FEX uplink interface pinning to your Pod
Switch.

Activity Procedure
Complete these steps:
Step 27 Verify the current pinning of your Pod FEX.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 133
©2016 NterOne Corporation
 N5K-PP# show fex 1PP
FEX: 1PP Description: FEX 1PP, Rack 1 state: Online
FEX version: 5.1(3)N2(1) [Switch version: 5.1(3)N2(1)]
Extender Serial: SSI16490DVW
Extender Model: N2K-C2232PP-10GE, Part No: 73-12533-05
Pinning-mode: static Max-links: 1
Fabric port for control traffic: Eth1/1
FCoE Admin: false
FCoE Oper: true
FCoE FEX AA Configured: false
Fabric interface state:
Eth1/1 - Interface Up. State: Active
Eth1/2 - Interface Up. State: Active

Step 28 Based on the output of the show fex command above:

Q36) What is the current pinning mode?

Q37) What is the current Max-links setting?

Q38) How many fabric interfaces (uplinks) are physically present?

Q39) How many server ports will use one uplink?

Q40) What will happen if one of the uplinks fails?

Step 29 Change the FEX pinning to utilize available physical uplinks.

N5K-PP# configure
Enter configuration commands, one per line. End with CNTL/Z.
N5K-PP(config)# fex 1PP
N5K-PP(config-fex)# pinning max-links 2
Change in Max-links will cause traffic disruption.

Step 30 Verify the new pinning of your Pod FEX.

N5K-PP(config-fex)# show fex 1PP

FEX: 1PP Description: FEX 1PP, Rack 1 state: Online
FEX version: 5.1(3)N2(1) [Switch version: 5.1(3)N2(1)]
Extender Serial: SSI16490DVW
Extender Model: N2K-C2232PP-10GE, Part No: 73-12533-05
Pinning-mode: static Max-links: 2
Fabric port for control traffic: Eth1/1
FCoE Admin: false
FCoE Oper: true
FCoE FEX AA Configured: false
Fabric interface state:
Eth1/1 - Interface Up. State: Active
Eth1/2 - Interface Up. State: Active

Step 31 Verify the current state of the FEX to Pod Server interface.

N5K-PP(config-fex)# show interface ethernet 1PP/1/1 brief

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 134
©2016 NterOne Corporation
 --------------------------------------------------------------------------------
Ethernet VLAN Type Mode Status Reason Speed Port
Interface Ch #
--------------------------------------------------------------------------------
Eth1PP/1/1 1 eth access up none 1000(D) --

Step 32 Simulate an uplink failure by shutting down fabric interface Ethernet 1/1.

N5K-PP(config-fex)# interface ethernet 1/1

N5K-PP(config-if)# shutdown

Step 33 Verify the current state of the FEX to Pod Server interface.

N5K-PP(config-if)# show interface ethernet 1PP/1/1 brief

--------------------------------------------------------------------------------
Ethernet VLAN Type Mode Status Reason Speed Port
Interface Ch #
--------------------------------------------------------------------------------
Eth1PP/1/1 1 eth access down fabricIfDown 1000(D) --

Step 34 Enable fabric interface Ethernet 1/1.

N5K-PP(config-if)# interface ethernet 1/1

N5K-PP(config-if)# no shutdown

Step 35 Change the FEX pinning back to the default setting.

N5K-PP(config-if)# fex 1PP

N5K-PP(config-fex)# pinning max-links 1
Change in Max-links will cause traffic disruption.
N5K-PP(config-fex)# end

Activity Verification
You have completed this task when you attain these results:
 You have changed the pinning mode of the FEX to utilize all available physical uplinks.
 You have simulated an uplink failure on your Pod FEX and verified the impact on the server
interfaces.

Task 3: Configure the Cisco Nexus 2000 Series Fabric Extender to

Support Dynamic Pinning
During this exercise, you will configure and verify your Pod FEX uplink interface pinning to your Pod
Switch.

Activity Procedure
Complete these steps:
Step 36 Verify that the FEX of your Pod Switch is recognized.

N5K-PP# show interface fex-fabric

Fabric Fabric Fex FEX
Fex Port Port State Uplink Model Serial
---------------------------------------------------------------
1PP Eth1/1 Active 1 N2K -C2232PP-10GE SSI16490DVW

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 135
©2016 NterOne Corporation
 1PP Eth1/2 Active 2 N2K -C2232PP-10GE SSI16490DVW
--- Eth1/3 Discovered 3 N2K-C2232PP-10GE SSI16490AGP

Step 37 Verify the configuration of the fabric interfaces.

N5K-PP# show running-config interface ethernet 1/1-2

!Command: show running-config interface Ethernet1/1-2

!Time: Wed May 15 09:16:43 2013

version 5.1(3)N2(1)

interface Ethernet1/1
description [to FEX 1PP Uplink 1]
switchport mode fex-fabric
fex associate 1PP

interface Ethernet1/2
description [to FEX 1PP Uplink 2]
switchport mode fex-fabric
fex associate 1PP

Step 38 Verify that the FEX is operational and the pinning state.

N5K-PP# show fex 1PP

FEX: 1PP Description: FEX 1PP, Rack 1 state: Online
FEX version: 5.1(3)N2(1) [Switch version: 5.1(3)N2(1)]
Extender Serial: SSI16490DVW
Extender Model: N2K-C2232PP-10GE, Part No: 73-12533-05
Pinning-mode: static Max-links: 1
Fabric port for control traffic: Eth1/2
FCoE Admin: false
FCoE Oper: true
FCoE FEX AA Configured: false
Fabric interface state:
Eth1/1 - Interface Up. State: Active
Eth1/2 - Interface Up. State: Active

Note With the pinning max-links parameter set to 1, all server interface traffic utilizes only one uplink
port. There are tw o available uplinks in the lab topology. In this s cenario, uplink 2 w ould never
be used. The best practice is to use all available uplinks. By configuring a port channel across all
uplink interfaces, the system w ill see only one uplink port, the port channel.

Step 39 Enable the LACP protocol.

N5K-PP# configure
Enter configuration commands, one per line. End with CNTL/Z.
N5K-PP(config)# feature lacp

Step 40 Configure all the fabric interfaces into a port channel. Use a port channel number of 1PP
(matching the FEX number) where P is your Pod Number.

N5K-PP(config)# interface ethernet 1/1-2

N5K-PP(config-if-range)# channel-group 1PP
N5K-PP(config-if-range)# end

Note The FEX w ill briefly go offline and return online as the port channel forms. This may take several
seconds.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 136
©2016 NterOne Corporation
 Step 41 Verify that the port channel is operational and the mode is fabric.

N5K-PP# show interface port-channel 1PP brief

--------------------------------------------------------------------------------
Port-channel VLAN Type Mode Status Reason Speed Protocol
Interface
--------------------------------------------------------------------------------
Po1PP 1 eth fabric up none a-10G(D) none

Step 42 Verify that the FEX recognizes the port channel as a fabric port.

N5K-PP# show fex 1PP

FEX: 1PP Description: FEX 1PP, Rack 1 state: Online
FEX version: 7.3(0)N1(1) [Switch version: 7.3(0)N1(1)]
Extender Serial: SSI18070DWX
Extender Model: N2K-C2232PP-10GE, Part No: 73-12533-06
Pinning-mode: static Max-links: 1
Fabric port for control traffic: Eth1 /2
FCoE Admin: false
FCoE Oper: true
FCoE FEX AA Configured: false
Fabric interface state:
Po1PP - Interface Up. State: Active
Eth1/1 - Interface Up. State: Active
Eth1/2 - Interface Up. State: Active

Note The max-links parameter is set to 1 causing all server traffic to utilize only one uplink port. With
dynamic pinning, the FEX sees the port channel as the only available uplink. The port channel
has multiple physical connections and utilizes the port channel load distribution algorithm w hen
sending traffic betw een the FEX and the parent sw itch.

Step 43 Verify the current state of the FEX to Pod Server interface.

N5K-PP# show interface ethernet 1PP/1/1 brief

--------------------------------------------------------------------------------
Ethernet VLAN Type Mode Status Reason Speed Port
Interface Ch #
--------------------------------------------------------------------------------
Eth1PP/1/1 1 eth access up none 1000(D) --

Step 44 Simulate an uplink failure by shutting down fabric interface Ethernet 1/1.

N5K-PP# configure
Enter configuration commands, one per line. End with CNTL/Z.
N5K-PP(config)# interface ethernet 1/1
N5K-PP(config-if)# shutdown

Step 45 Verify the current state of the FEX to Pod Server interface.

N5K-PP(config-if)# show interface ethernet 1PP/1/1 brief

--------------------------------------------------------------------------------
Ethernet VLAN Type Mode Status Reason Speed Port
Interface Ch #
--------------------------------------------------------------------------------
Eth1PP/1/1 1 eth access up none 1000(D) --

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 137
©2016 NterOne Corporation
 Note When dynamic pinning w ith port channels used for the fabric uplinks, the FEX server interfaces
remain operational even if there is a physical failure of a fabric interface.

Step 46 Re-enable fabric interface Ethernet 1/1.

N5K-PP(config-if)# interface ethernet 1/1

N5K-PP(config-if)# no shutdown
N5K-PP(config-if)# end

Activity Verification
You have completed this task when you attain these results:
 You have configured a port channel across the fabric interfaces connecting your Pod Switch to your
Pod FEX to utilize all available physical uplinks.
 You have verified that when dynamic pinning is configured, a FEX uplink failure does not result in
FEX server interfaces failing.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 138
©2016 NterOne Corporation
Lab 11: Configuring FCoE
Complete this lab activity to practice what you learned in the related lesson.

Activity Objective
In this activity, you will configure your Pod Switch to support FCoE. After completing this activity, you will
be able to meet these objectives:
 Become familiar with, configure, and verify the operation of FCoE using the CLI of the Cisco
Nexus 5000 Series switches

Command List
The table below lists the commands that are used in this activity.
Com m and Description
show license usage Displays licensing information
feature fcoe Enables FCoE features
show vlan brief Displays the configured VLANs
vlan n Creates a VLAN
name vlan-name Assigns a name to a VLAN
no shutdow n Enables a VLAN
fcoe [vsan <>] Defines a VLAN as an FCoE VLAN
interface ethernet 1/3 Enters interface configuration mode
sw itchport mode trunk Defines an Ethernet port as a trunk
sw itchport trunk allow ed vlan Defines the VLANs allow ed on the trunk

spanning-tree port type edge trunk Defines an edge port that is configured as a trunk as a
PortFast port
interface vfc n Creates a virtual Fibre Channel (VFC) interface
sw itchport description Assigns a description to a sw itchport
bind interface ethernet module/port Associates a VFC to a physical interface
vsan database Enters the VSAN database
vsan id name Creates a VSAN
vsan id interface vfc n Binds a VFC to a VSAN
system qos Enters the system QoS context
service-policy type qos input fcoe-default-
Assigns the type QoS input policy to an MQC object
in- policy
service-policy type queuing input fcoe- Assigns the type queuing input policy to an MQC object
default-in- policy
service-policy type queuing output fcoe-
Assigns the type queuing output policy to an MQC object
default-out- policy
service-policy type netw ork-qos fcoe- Assigns the type netw ork-qos policy to an MQC object
default- nq-policy
show module n [port type] Displays the ports of a module
slot 1 Selects a slot in the module
port n-n type [ethernet | fc Selects the operation of interfaces in a Unified Port module
show interface [brief] Displays abbreviated interface information
show interface <> fcoe Displays the FCoE interface parameters

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 139
©2016 NterOne Corporation
 Com m and Description
show flogi database Displays the FLOGI database
show fcns database Displays the FCNS database
fcping fcid <> vsan n Generates an FC Ping

Task 0: Lab Preparation

In this task, you will perform the steps necessary to get ready for performing the subsequent tasks in this lab
exercise.

Activity Procedure
Complete these steps:
Step 1 Make sure that you know the value of your Pod Number. Your Pod Number is assigned to you
by your instructor and is used to identify the lab devices that you will use during this lab
exercise. Refer to the following table when a task step in this lab exercise uses a letter variable.

Value of “PP” Value of “QQ” Value of “Z”

Your Assigned Pod Num ber
(Your Pod Num ber) (Your Peer Pod Num ber) (Your Pod Pair Num ber)
11 11 12 1
12 12 11 1
13 13 14 2
14 14 13 2
15 15 16 3
16 16 15 3
17 17 18 4
18 18 17 4
19 19 20 5
20 20 19 5
21 21 22 6
22 22 21 6
23 23 24 7
24 24 23 7
25 25 26 8
26 26 25 8
27 27 28 9
28 28 27 9

Step 2 Your assigned Pod is one of two Pods within a Pod Pair. The details of each Pod Pair, including
diagrams and tables of related values, are contained in one of several NterOne Resource Guide
documents. Open the NterOne Resource Guide that corresponds to your assigned Pod Number.
Step 3 Locate the various tables that provide additional information about your assigned Pod, which
include details such as IP addresses and device login credentials.
Step 4 Locate the diagram that corresponds to this lab exercise. This diagram may help you visualize
the intended goal of this lab exercise.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 140
©2016 NterOne Corporation
Task 0.1: Log In to your Student Server and Reset the Configuration of
your Pod Switch
In order to ensure that the steps in this lab exercise function properly the running configuration of your Pod
Switch (a Cisco Nexus 5000 series switch) must be reset to the baseline configuration. During this Task you
will log in to your assigned Student Server and reset the configuration of your Pod Switch to th e baseline
state.

Activity Procedure
Complete these steps:
Step 5 Verify that you are currently logged in to your Student Server.
Step 6 From your Student Server desktop use the PuTTY application to open an SSH session to your
assigned Pod Switch. Use the following username and password:
 Username: admin
 Password: Nterone179
The following table contains the management addresses of each switch assigned to your Pod.

Note There may be preconfigured shortcuts to these devices on the Student Server desktop.

Pod Sw itch Peer Pod Sw itch

Your Assigned Pod Sw itch Peer Pod Sw itch
Nam e Nam e
Pod Num ber Managem ent Address Managem ent Address
(N5K-PP) (N5K-QQ)
11 N5K-11 10.1.5.4 N5K-12 10.1.5.8
12 N5K-12 10.1.5.8 N5K-11 10.1.5.4
13 N5K-13 10.1.5.12 N5K-14 10.1.5.16
14 N5K-14 10.1.5.16 N5K-13 10.1.5.12
15 N5K-15 10.1.5.20 N5K-16 10.1.5.24
16 N5K-16 10.1.5.24 N5K-15 10.1.5.20
17 N5K-17 10.1.5.28 N5K-18 10.1.5.32
18 N5K-18 10.1.5.32 N5K-17 10.1.5.28
19 N5K-19 10.1.5.36 N5K-20 10.1.5.40
20 N5K-20 10.1.5.40 N5K-19 10.1.5.36
21 N5K-21 10.1.5.44 N5K-22 10.1.5.48
22 N5K-22 10.1.5.48 N5K-21 10.1.5.44
23 N5K-23 10.1.5.52 N5K-24 10.1.5.56
24 N5K-24 10.1.5.56 N5K-23 10.1.5.52
25 N5K-25 10.1.5.60 N5K-26 10.1.5.64
26 N5K-26 10.1.5.64 N5K-25 10.1.5.60
27 N5K-27 10.1.5.68 N5K-28 10.1.5.72
28 N5K-28 10.1.5.72 N5K-27 10.1.5.68

N5K-PP login: admin

Password: Nterone179

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 141
©2016 NterOne Corporation
 Cisco Nexus Operating System (NX-OS) Software
TAC support: http://www.cisco.com/tac
Copyright (c) 2002-2016, Cisco Systems, Inc. All rights reserved.
The copyrights to certain works contained in this software are
owned by other third parties and used and distributed under
license. Certain components of this software are licensed under
the GNU General Public License (GPL) version 2.0 or the GNU
Lesser General Public License (LGPL) Version 2.1. A copy of each
such license is available at
http://www.opensource.org/licenses/gpl-2.0.php and
http://www.opensource.org/licenses/lgpl -2.1.php
N5K-PP#

Step 7 Reset the running configuration to the baseline state by entering the run-script baseline
command.

N5K-PP# run-script baseline

`terminal dont-ask
`write erase
Warning: This command will erase the startup -configuration.
`copy bootflash:/configs/mgmt.txt scheduled -config
Copy complete, now saving to disk (please wait)...
`reload
[ 1047.127077] Shutdown Ports..
<… output omitted …>

Note At this point the Pod Sw itch w ill reload, and your PuTTY session w ill be terminated. It w ill take
betw een 5 and 10 minutes for the Pod Sw itch to reload; you w ill not be able to log back in to the
Pod Sw itch until the reload is complete.

Step 8 Use the PuTTY application to open a new SSH session to your assigned Pod Switch. The
credentials you should use are the same as what you used previously in this Task.

Task 0.2: Reset the Configuration of your Pod MDS Switch

In order to ensure that the steps in this lab exercise function properly the running configuration of your Pod
MDS Switch (a Cisco MDS 9100 series switch) must be reset to the baseline configuration. During this Task
you will log in to your assigned Student Server and reset the configuration of your Pod Switch to the baseline
state.

Activity Procedure
Complete these steps:
Step 9 From your Student Server desktop, start a session to the console port of your Pod MDS Switch
by using the PuTTY shortcut to MDS-PP (Console) (replace “PP” with your assigned 2-digit
Pod Number).

Step 10 If you do not see login prompt press <Enter> once or twice; this will cause the login prompt to
be displayed.
Step 11 Log in to your Pod MDS with the following credentials:

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 142
©2016 NterOne Corporation
  Username: admin
 Password: Nterone179

MDS-PP login: admin

Password: Nterone179
Cisco Nexus Operating System (NX-OS) Software
TAC support: http://www.cisco.com/tac
Copyright (c) 2002-2013, Cisco Systems, Inc. All rights reserved.
The copyrights to certain works contained in this software are
owned by other third parties and used and distributed under
license. Certain components of this software are licensed under
the GNU General Public License (GPL) version 2.0 or the GNU
Lesser General Public License (LGPL) Version 2.1. A copy of each
such license is available at
http://www.opensource.org/licenses/gpl-2.0.php and
http://www.opensource.org/licenses/lgpl -2.1.php
MDS-PP#

Step 12 Erase the startup configuration file by entering the write erase command. When prompted if
you wish to proceed, type “y” and press Enter.

MDS-PP# write erase

Warning: This command will erase the startup -configuration.
Do you wish to proceed anyway? (y/n) [n] y

Step 13 Reload the Pod MDS by entering the reload command. When prompted if you wish to proceed,
type “y” and press Enter.

MDS-PP# reload
This command will reboot the system. (y/n)? [n] y
2014 Dec 24 18:13:38 MDS-PP %$ %PLATFORM-2-PFM_SYSTEM_RESET: Manual system restart
from Command Line Interface
<… output omitted …>

Note The sw itch w ill take approximately 5 minutes to reload.

Step 14 After the Pod MDS finishes reloading, the first question it will ask is if you want to enforce
secure user account passwords. Type “y” and press Enter. This will force all user accounts to
use passwords that include upper-case, lower-case, and numeric characters.

Note You w ill probably see additional log messages appear after this question appears, w hich is
normal.

---- System Admin Account Setup ----

Do you want to enforce secure password standard (yes/no) [y]: y

Step 15 The next task is to configure the admin account password. When you are prompted to enter the
password for the admin account use the password Nterone179. Enter Nterone179 again when
asked to confirm the admin account password.

Enter the password for "admin": Nterone179

Confirm the password for "admin": Nterone179

Step 16 The Basic System Configuration Dialog will now appear. Exit the Basic System
Configuration Dialog by entering no when prompted.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 143
©2016 NterOne Corporation
 ---- Basic System Configuration Dialog ----

This setup utility will guide you through the basic configuration of
the system. Setup configures only enough connectivity for management
of the system.

Please register Cisco MDS 9000 Family devices promptly with your
supplier. Failure to register may affect response tim es for initial
service calls. MDS devices must be registered to receive entitled
support services.

Press Enter at anytime to skip a dialog. Use ctrl -c at anytime

to skip the remaining dialogs.

Would you like to enter the basic configuration dialog (yes/ no): no

Step 17 Log in to your Pod MDS with the following credentials:

 Username: admin
 Password: Nterone179

User Access Verification

10.1.5.xx login: admin
Password: Nterone179
Cisco Nexus Operating System (NX-OS) Software
TAC support: http://www.cisco.com/tac
Copyright (c) 2002-2013, Cisco Systems, Inc. All rights reserved.
The copyrights to certain works contained in this software are
owned by other third parties and used and distributed under
license. Certain components of this software are licensed under
the GNU General Public License (GPL) version 2.0 or the GNU
Lesser General Public License (LGPL) Version 2.1. A copy of each
such license is available at
http://www.opensource.org/licenses/gpl-2.0.php and
http://www.opensource.org/licenses/lgpl -2.1.php
switch#

Step 18 Reset the running configuration to the baseline state by entering the run-script baseline
command.

switch# run-script baseline

`terminal dont-ask
`copy bootflash:/configs/mgmt.txt running -config
Event in-use by active port monitor policy
This will prevent CFS from distributing the configuration to other switches.
Operation is not permitted as the fabric distribution is currently disabled.
Copy complete, now saving to disk (please wait)...
`copy running-config startup-config
[########################################] 100%
Copy complete, now saving to disk (please wait)...
MDS-PP#

Note The Pod MDS reset process w as successful if the command prompt changed from “sw itch” to
“MDS-PP”.

Step 19 Close the PuTTY session to the console port of your Pod MDS switch.
Step 20 From your Student Server desktop use the PuTTY application to open an SSH session to your
assigned Pod MDS Switch. Use the following username and password:
 Username: admin

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 144
©2016 NterOne Corporation
  Password: Nterone179
The following table contains the management address of the MDS switch assigned to your Pod.

Note There may be preconfigured shortcuts to these devices on the Student Server desktop.

Pod MDS Pod MDS Pod MDS

Your Assigned Pod Pod
Managem ent Managem ent Managem ent
Pod Num ber Num ber Num ber
Address Address Address
11 10.1.5.6 17 10.1.5.30 23 10.1.5.54
12 10.1.5.10 18 10.1.5.34 24 10.1.5.58
13 10.1.5.14 19 10.1.5.38 25 10.1.5.62
14 10.1.5.18 20 10.1.5.42 26 10.1.5.66
15 10.1.5.22 21 10.1.5.46 27 10.1.5.70
16 10.1.5.26 22 10.1.5.50 28 10.1.5.74

Task 0.3: Open a Remote Desktop Session to your Pod Server

During this Task you will use the Remote Desktop Connection application to open a session to your assigned
Pod Server, which is a Cisco UCS C-series server running Microsoft Windows Server 2008.

Activity Procedure
Complete these steps:
Step 21 From your Student Server desktop use the Remote Desktop Connection application to open a
session to your Pod Server. Use the following username and password:
 Username: student
 Password: Nterone179

Note There may be a preconfigured shortcut to this device on the Student Server desktop.

Pod Server Pod Server Pod Server

Your Assigned Pod Pod
Managem ent Managem ent Managem ent
Pod Num ber Num ber Num ber
Address Address Address
11 10.1.5.5 17 10.1.5.29 23 10.1.5.53
12 10.1.5.9 18 10.1.5.33 24 10.1.5.57
13 10.1.5.13 19 10.1.5.37 25 10.1.5.61
14 10.1.5.17 20 10.1.5.41 26 10.1.5.65
15 10.1.5.21 21 10.1.5.45 27 10.1.5.69
16 10.1.5.25 22 10.1.5.49 28 10.1.5.73

Task 1: Install the License and Enable the Fibre Channel Ports
During this task, you will activate and verify the required licensing required for FCoE and enable the Fibre
Channel ports of the switch.

Activity Procedure

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 145
©2016 NterOne Corporation
 Complete these steps:
Step 22 View the licenses that are available and in use on your Pod Switch.

N5K-PP# show license usage

Feature LicIns
Status Expiry Date Comments
Count
--------------------------------------------------------------------------------
FCOE_NPV_PKG No - Unused -
FM_SERVER_PKG No - Unused -
ENTERPRISE_PKG Yes - Unused Never -
FC_FEATURES_PKG Yes - Unused Never -
VMFEX_FEATURE_PKG No - Unused -
ENHANCED_LAYER2_PKG Yes - Unused Never -
LAN_BASE_SERVICES_PKG Yes - In use Never -
LAN_ENTERPRISE_SERVICES_PKG Yes - Unused Never -
--------------------------------------------------------------------------------

Note FCoE requires the FC_FEATURES_PKG w hich contains the Storage Protocol Services license.

Step 23 View the current configuration of QoS by entering the show running-config ipqos command.
You should not see any QoS commands in the output; starting in NX-OS version 7.0 the default
QoS commands are hidden.

N5K-PP# show running-config ipqos

!Command: show running-config ipqos

!Time: Sat Jun 18 13:28:05 2016

version 7.3(0)N1(1)

Step 24 Enter configuration mode and enable the FCoE feature, which activates the Storage Protocol
Services feature set of the Cisco NX-OS Software.

N5K-PP# configure
Enter configuration commands, one per line. End with CNTL/Z.
N5K-PP(config)# feature fcoe
FC license checked out successfully
fc_plugin extracted successfully
FC plugin loaded successfully
FCoE manager enabled successfully
FC enabled on all modules successfully
Enabled FCoE QoS policies successfully

Step 25 Re-examine the configuration of QoS by entering the show running-config ipqos command.
At this point you should see the QoS statements automatically added by the switch when you
enabled the FCoE feature.

Note A know n problem w ith the Nexus 5000 series sw itch is that it may not automatically add the QoS
statements below w hen the FCoE feature is enabled.

If you do not see the QoS com m ands below you m ust add them m anually, otherwise
FCoE w ill not function properly later in this lab exercise .

N5K-PP(config)# show running-config ipqos

!Command: show running-config ipqos

!Time: Sat Jun 18 13:28:05 2016

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 146
©2016 NterOne Corporation
 version 7.3(0)N1(1)
system qos
service-policy type qos input fcoe-default-in-policy
service-policy type queuing input fcoe-default-in-policy
service-policy type queuing output fcoe-default-out-policy
service-policy type network-qos fcoe-default-nq-policy

Step 26 View the licenses that are available and in use. You should now see that the
FC_FEATURES_PKG license is in use.

N5K-PP(config)# show license usage

Feature Ins Lic Status Expiry Date Comments
Count
--------------------------------------------------------------------------------
FCOE_NPV_PKG No - Unused -
FM_SERVER_PKG No - Unused -
ENTERPRISE_PKG Yes - Unused Never -
FC_FEATURES_PKG Yes - In use Never -
VMFEX_FEATURE_PKG No - Unused -
ENHANCED_LAYER2_PKG Yes - Unused Never -
LAN_BASE_SERVICES_PKG Yes - In use Never -
LAN_ENTERPRISE_SERVICES_PKG Yes - Unused Never -
--------------------------------------------------------------------------------

Step 27 Cisco Nexus 5000 series switches that contain the letters “UP” in the part numb er contain
Unified Ports, which are ports that can be configured as Ethernet or Fibre Channel interfaces.
Determine how the Unified Ports are currently configured by entering the
show module 1 port type command. At this point all of the interfaces should be Ethernet
interfaces.

Pod Num ber Sw itch Model Num ber of Unified Ports

11 through 22 N5K-C5548UP 32
23 through 28 N5K-C5672UP 48

N5K-PP(config)# show module 1 port type

Slot/Port Operational Type Admin Type
--------- ---------------------- ------------
1/1 Ethernet Ethernet
1/2 Ethernet Ethernet
1/3 Ethernet Ethernet
<… output omitted …>
1/30 Ethernet Ethernet
1/31 Ethernet Ethernet
1/32 Ethernet Ethernet

Step 28 In order to connect your Pod Switch to your Pod MDS you will need to reconfigure the
necessary unified ports in the Pod Switch as Fibre Channel ports. You will reconfigure a range
of unified ports based on the model of switch in your Pod. Use the following table to determine
the first and last port numbers to reconfigure.

First Unified Last Unified

Pod Num ber Sw itch Model
Port Num ber Port Num ber
11 through 22 N5K-C5548UP 21 32
23 through 28 N5K-C5672UP 33 48

N5K-PP(config)# slot 1

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 147
©2016 NterOne Corporation
 N5K-PP(config-slot)# port <First Port>-<Last Port> type fc
Port type is changed. Please copy configuration and reload the switch
N5K-PP(config-slot)# end

Step 29 The module that contains the unified ports that are being reconfigured must be rebooted to
implement the new configuration. Before you reload the switch you must save the
configuration, otherwise you will have to start over after the switch reloads. Copy the running
configuration to the startup configuration.

N5K-PP# copy running-config startup-config

[########################################] 100%
Copy complete, now saving to disk (please wait)...

Step 30 Reload your Pod Switch in order to complete the process of changing the range of unified ports
to fibre channel mode.

N5K-PP# reload
WARNING: This command will reboot the system
Do you want to continue? (y/n) [n] y

Note It w ill take approximately five minutes for the sw itch to reboot.

Step 31 After the reload is complete, log back in to the Pod Switch and verify how the unified ports are
now being utilized.

N5K-PP# show module 1 port type

Slot/Port Operational Type Admin Type
--------- ---------------------- ------------
1/1 Ethernet Ethernet
1/2 Ethernet Ethernet
1/3 Ethernet Ethernet
<… output omitted …>
1/21 Fc Fc
1/22 Fc Fc
1/23 Fc Fc
1/24 Fc Fc
1/25 Fc Fc
1/26 Fc Fc
1/27 Fc Fc
1/28 Fc Fc
1/29 Fc Fc
1/30 Fc Fc
1/31 Fc Fc
1/32 Fc Fc

Activity Verification
You have completed this task when you attain these results:
 You have activated and verified the required licensing to configure FCoE.
 You have configured the required unified ports to operate in FC mode.

Task 2: Configure VLANs and VSANs

During this task, you will configure the necessary VLANs and VSANs for FCoE connectivity on your Pod
Switch.

Activity Procedure

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 148
©2016 NterOne Corporation
 Complete these steps:
Step 32 Enter configuration mode and create and name VLAN 300. This VLAN will be used by the Pod
Servers to carry regular Ethernet traffic.

N5K-PP# configure
Enter configuration commands, one per line. End with CNTL/Z.
N5K-PP(config)# vlan 300
N5K-PP(config-vlan)# name LAN_Traffic

Step 33 Create and name VLAN 101X. This VLAN will be used by the Pod Servers to carry FCoE
traffic. Refer to the table below to determine the value of “X” for your assigned pod.

Pod Num ber Value of “X” FCoE VLAN Num ber FC VSAN Num ber
11, 13, 15, 17, 19, 21, 23, 25, 27 1 1011 11
12, 14, 16, 18, 20, 22, 24, 26, 28 2 1012 12

Note Replace “X” w ith the value in this table in the rest of this lab exercise.

N5K-PP(config-vlan)# vlan 101X

N5K-PP(config-vlan)# name FCoE_Traffic

Step 34 Create and name VSAN 1X. This VSAN will be used to carry SAN traffic from the Pod Servers
to the SAN fabric.

N5K-PP(config-vlan)# vsan database

N5K-PP(config-vsan-db)# vsan 1X name SAN_Traffic
N5K-PP(config-vsan-db)# exit

Step 35 The VLAN that is carrying the FCoE traffic must be mapped to the VSAN that will be used to
carry the SAN traffic to the fabric. Map VLAN 101X to VSAN 1X.

N5K-PP(config)# vlan 101X

N5K-PP(config-vlan)# fcoe vsan 1X
N5K-PP(config-vlan)# end

Step 36 Confirm the VLAN-to-VSAN mapping by entering the show vlan fcoe command.

N5K-PP# show vlan fcoe

Original VLAN ID Translated VSAN ID Association State

---------------- ------------------ -----------------

101X 1X Operational

Activity Verification
You have completed this task when you attain these results:
 You have created the VLANs and VSANs necessary to carry traffic from the Pod Servers to the
LAN as well as the SAN
 You have mapped the FCoE VLAN to the VSAN used by the SAN fabric.

Task 3: Configure Fibre Channel Domain IDs

A requirement of the switches in a fibre channel SAN is each switch must have a unique domain ID for each
configured VSAN. During this task, you will configure the fibre channel domain IDs for VSAN 1 and VSAN

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 149
©2016 NterOne Corporation
 1X on your Pod Switch. In order to ensure all switches have a unique domain ID you will set the domain IDs
on your Pod Switch to include your Pod Number.

Activity Procedure
Complete these steps:
Step 37 Change the fibre channel domain ID for VSAN 1 and VSAN 1X to 1PP (replace “PP” with
your assigned Pod Number and replace “X” with the correct value).

N5K-PP(config)# fcdomain domain 1PP static vsan 1

N5K-PP(config)# fcdomain domain 1PP static vsan 1X

Step 38 In order to force your Pod Switch to use the new domain IDs the fcdomain process for each
VSAN must be restarted. Restart the fcdomain process for VSAN 1 and VSAN 1X.

N5K-PP(config)# fcdomain restart vsan 1

N5K-PP(config)# fcdomain restart vsan 1X
N5K-PP(config)# end

Step 39 Verify that the domain IDs for the VSANs have been configured properly by entering the
show fcdomain domain-list command. At this point you should only see one entry per VSAN
which corresponds to your Pod Switch.

N5K-PP# show fcdomain domain-list

VSAN 1
Number of domains: 1
Domain ID WWN
--------- -----------------------
0x??(1PP) 20:01:00:0d:ec:da:78:c1 [Local] [Principal]

VSAN 1X
Number of domains: 1
Domain ID WWN
--------- -----------------------
0x??(1PP) 20:0b:00:0d:ec:da:78:c1 [Local] [Principal]

Activity Verification
You have completed this task when you attain these results:
 The fibre channel domain ID for each VSAN on the Pod Switch has been configured to a unique
value.

Task 4: Enable Fibre Channel Connectivity to the Pod MDS

During this task, you will enable Fibre Channel connectivity between your Pod Switch and your Pod MDS.

Activity Procedure
Complete these steps:
Step 40 Before enabling the connection between your Pod Switch and your Pod MDS, disable the
distribution of device aliases on your Pod Switch. This will allow you to co nfigure device
aliases in a subsequent task.

N5K-PP# configure
Enter configuration commands, one per line. End with CNTL/Z.
N5K-PP(config)# no device-alias distribute

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 150
©2016 NterOne Corporation
 Step 41 Verify that the distribution of device aliases has been disabled by entering the show device-
alias status command.

N5K-21(config)# show device-alias status

Fabric Distribution: Disabled
Database:- Device Aliases 0 Mode: Basic
Checksum: 0xf6bd6b3389b87233d462029172c8612

Step 42 Use the following table to determine the Fibre Channel port nu mbers on your Pod Switch that
are connected to the SAN. In the rest of this lab exercise replace the letters “PN” with this
value.

Pod Num ber Fibre Channel

Port Num ber (PN)
11 through 22 21
23 through 28 33

Note Each Pod Sw itch has tw o ports connected to the Pod MDS; this lab exercise w ill use only one of
these connections.

Step 43 Examine the state of the Fibre Channel interface by entering the show interface fc 1/PN
command. The interface should be in the administratively down state.

N5K-PP(config)# show interface fc 1/PN

fc1/21 is down (Administratively down)
Hardware is Fibre Channel, SFP is short wave laser w/o OFC (SN)
Port WWN is 20:15:00:2a:6a:09:fa:40
Admin port mode is auto, trunk mode is on
snmp link state traps are enabled
Port vsan is 1
Receive data field Size is 2112
Beacon is turned off
1 minute input rate 0 bits/sec, 0 bytes/sec, 0 frames/sec
1 minute output rate 0 bits/sec, 0 bytes/sec, 0 frames/sec
0 frames input, 0 bytes
0 discards, 0 errors
0 CRC, 0 unknown class
0 too long, 0 too short
0 frames output, 0 bytes
0 discards, 0 errors
0 input OLS, 0 LRR, 0 NOS, 0 loop inits
0 output OLS, 0 LRR, 0 NOS, 0 loop inits
last clearing of "show interface" counters never

Step 44 Enable the Fibre Channel interface to your Pod MDS.

N5K-PP(config)# interface fc 1/PN

N5K-PP(config-if)# no shutdown
N5K-PP(config-if)# end

Step 45 Re-examine the state of the connection to your Pod MDS by entering the show interface fc
1/PN command. You should see the interface is in TE (trunked expansion) mode and that
VSANs 1 and 1X are in an up state on the trunk.

Note It may take several seconds for the Trunk VSANs to enter the “up” state.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 151
©2016 NterOne Corporation
 Note Auto-detection of the interface speed is enabled by default; the devices on each end of a
connection w ill determine the maximum speed that is possible w ith the hardw are present. The
negotiation of the speed is per the fibre channel standard; any device that you connect to the
sw itch should support auto-detection of speed as w ell.

N5K-PP# show interface fc 1/PN

fc1/PN is trunking
Hardware is Fibre Channel, SFP is short wave laser w/o OFC (SN)
Port WWN is 20:15:00:2a:6a:09:fa:40
Peer port WWN is 20:01:00:0d:ec:da:78:c0
Admin port mode is auto, trunk mode is on
snmp link state traps are enabled
Port mode is TE
Port vsan is 1
Speed is 4 Gbps
Transmit B2B Credit is 16
Receive B2B Credit is 16
Receive data field Size is 2112
Beacon is turned off
Trunk vsans (admin allowed and active) (1,1X)
Trunk vsans (up) (1,1X)
Trunk vsans (isolated) ()
Trunk vsans (initializing) ()
1 minute input rate 16888 bits/sec, 2111 bytes/sec, 21 frames/sec
1 minute output rate 22816 bits/sec, 2852 bytes/sec, 21 frames/sec
3575 frames input, 338556 bytes
0 discards, 0 errors
0 CRC, 0 unknown class
0 too long, 0 too short
3583 frames output, 408936 bytes
0 discards, 0 errors
0 input OLS, 2 LRR, 0 NOS, 0 loop inits
3 output OLS, 2 LRR, 0 NOS, 0 loop inits
last clearing of "show interface" counters never
16 receive B2B credit remaining
16 transmit B2B credit remaining
0 low priority transmit B2B credit remaining
Interface last changed at Sat Jun 18 14:55:55 2016

STOP! Do NOT continue this lab exercise if the Trunk VSANs do not enter the “up” state w ithin a
m inute of enabling the interface; the rest of the lab exercise w ill fail if the trunk to your
Pod MDS is not functioning. Troubleshoot the configuration before proceeding to the next
step.

Step 46 Examine the configuration of interface fc 1/PN by entering the

show running-config interface fc 1/PN command. You should not see any configuration
commands that configure the interface as a trunk.

Note The default settings of the fibre channel interfaces on a Nexus sw itch are to auto-detect the
mode of the interface (in this case fc1/PN is in TE mode) and w hether it should form a trunk w ith
the device to w hich it is connected.

N5K-PP# show running-config interface fc 1/PN

!Command: show running-config interface fc1/PN

!Time: Sat Jun 18 15:02:15 2016

version 7.3(0)N1(1)

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 152
©2016 NterOne Corporation
 interface fc1/PN
no shutdown

Step 47 Re-examine the fibre channel domain IDs that are known by the Pod Switch by entering the
show fcdomain domain-list command. At this point you should now see several other switches
listed now that the connection to the Pod MDS switch is complete. The core MDS switch for
each Fabric is configured with domain ID 1 and is the Principal switch for the Fabric. Your Pod
Switch will have the Local flag at the end of the corresponding domain ID.

N5K-PP# show fcdomain domain-list

VSAN 1
Number of domains: 11
Domain ID WWN
--------- -----------------------
0x01(1) 20:01:00:0d:ec:5f:72:41 [Principal]
0x0b(11) 20:01:00:0d:ec:da:78:c1
0x0d(13) 20:01:00:0d:ec:aa:e6:c1
0x0f(15) 20:01:00:0d:ec:67:c6:01
0x11(17) 20:01:00:0d:ec:da:1f:01
0x13(19) 20:01:00:0d:ec:90:23:41
0x15(21) 20:01:00:0d:ec:63:68:c1
0x17(23) 20:01:00:0d:ec:cf:4a:81
0x19(25) 20:01:00:0d:ec:ab:10:41
0x1b(27) 20:01:00:0d:ec:4c:8b:41
0x??(1PP) 20:01:00:2a:6a:09:fa:41 [Local]

VSAN 1X
Number of domains: 11
Domain ID WWN
--------- -----------------------
0x01(1) 20:0b:00:0d:ec:5f:72:41 [Principal ]
0x0b(11) 20:0b:00:0d:ec:da:78:c1
0x0d(13) 20:0b:00:0d:ec:aa:e6:c1
0x0f(15) 20:0b:00:0d:ec:67:c6:01
0x11(17) 20:0b:00:0d:ec:da:1f:01
0x13(19) 20:0b:00:0d:ec:90:23:41
0x15(21) 20:0b:00:0d:ec:63:68:c1
0x17(23) 20:0b:00:0d:ec:cf:4a:81
0x19(25) 20:0b:00:0d:ec:ab:10:41
0x1b(27) 20:0b:00:0d:ec:4c:8b:41
0x??(1PP) 20:0b:00:2a:6a:09:fa:41 [Local]

Step 48 Verify the role of the Pod Switch within the Fibre Channel domain by entering the
show fcdomain vsan 1X command.

N5K-PP# show fcdomain vsan 1X

The local switch is a Subordinated Switch.

Local switch run time information:

State: Stable
Local switch WWN: 20:0b:00:2a:6a:09:fa:41
Running fabric name: 20:0b:00:0d:ec:5f:72:41
Running priority: 128
Current domain ID: 0x??(1PP)

Local switch configuration information:

State: Enabled
FCID persistence: Enabled
Auto-reconfiguration: Disabled

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 153
©2016 NterOne Corporation
 Contiguous-allocation: Disabled
Configured fabric name: 20:01:00:05:30:00:28:df
Optimize Mode: Disabled
Configured priority: 128
Configured domain ID: 0x??(1PP) (static)

Principal switch run time information:

Running priority: 1

Interface Role RCF-reject

------------------ ------------- ------------
fc1/?? Upstream Disabled
------------------ ------------- ------------

Activity Verification
You have completed this task when you attain these results:
 Interface fc1/PN is trunking VSAN 1 and VSAN 1X to the Pod MDS switch.

Task 5: Configure Device Aliases

During this task, you will configure device aliases on your Pod Switch. These devices aliases will make it
easier to easily identify SAN ports and devices in the Fabric when commands are executed on the switch.

Activity Procedure
Complete these steps:
Step 49 Examine the contents of the fibre channel name server (FCNS) database by entering the
show fcns database command. At this point you should see an entry under VSAN 1X. The
entry should identify the vendor as NetApp.

N5K-PP# show fcns database

VSAN 1X:
--------------------------------------------------------------------------
FCID TYPE PWWN (VENDOR) FC4 -TYPE:FEATURE
--------------------------------------------------------------------------
0x010000 N 50:0a:09:8?:86:78:22:ca (NetApp) scsi-fcp

Step 50 Examine additional details of the NetApp entry that are available by entering the
show fcns database fcid <FCID> detail vsan 1X command (replace <FCID> with the FCID
that you see in the output of show fcns database from the previous step). The output of this
command is similar to the output of the show cdp neighbors detail command in that the output
contains a number of details about the connected device. This information was learned when the
NetApp storage controller logged in to the fabric and is stored in the FCNS database at that
point. In a given SAN fabric the contents of the FCNS database on each SAN switch should be
identical.

N5K-PP# show fcns database fcid 0x010000 detail vsan 1X

------------------------
VSAN:1P FCID:0x010000
------------------------
port-wwn (vendor) :50:0a:09:8?:86:78:22:ca (NetApp)
node-wwn :50:0a:09:80:86:78:22:ca
class :3
node-ip-addr :0.0.0.0
ipa :ff ff ff ff ff ff ff ff
fc4-types:fc4_features :scsi-fcp
symbolic-port-name :

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 154
©2016 NterOne Corporation
 symbolic-node-name :
port-type :N
port-ip-addr :0.0.0.0
fabric-port-wwn :20:15:00:0d:ec:5f:72:40
hard-addr :0x000000
permanent-port-wwn (vendor) :00:00:00:00:00:00:00:00
connected interface :fc1/21
switch name (IP address) :N5K-MDS-? (10.1.5.25?)

Step 51 In the output of many “show” commands there will be a long list of WWPNs. It is difficult to
determine the device that uses a given WWPN as a WWPN is displayed as a string of
hexadecimal characters. Labels can be created for each WWPN by creating entries in the
device-alias database. To begin the process of creating a device-alias, enter device-alias
database configuration mode by entering the device-alias database command.

N5K-PP(config)# device-alias database

Step 52 Create device aliases for each of the devices in the following table (replace “PP” with your
assigned 2-digit Pod Number and replace “QQ” with your 2-digit Peer Pod Number).

Alias Nam e PWWN

SAN_STORAGE_VSAN_11 50:0a:09:82:86:78:22:ca
SAN_STORAGE_VSAN_12 50:0a:09:81:86:78:22:ca
POD-SERVER-PP_fc0_to_N5K-PP_E1-9 20:00:00:25:b5:55:0a:PP
POD-SERVER-QQ_fc1_to_N5K-PP_E1-10 20:00:00:25:b5:55:0b:QQ

N5K-PP(config-device-alias-db)# device-alias name SAN_STORAGE_VSAN_11 pwwn

50:0a:09:82:86:78:22:ca
N5K-PP(config-device-alias-db)# device-alias name SAN_STORAGE_VSAN_12 pwwn
50:0a:09:81:86:78:22:ca
N5K-PP(config-device-alias-db)# device-alias name POD-SERVER-PP_fc0_to_N5K-PP_E1-9
pwwn 20:00:00:25:b5:55:0a:PP
N5K-PP(config-device-alias-db)# device-alias name POD-SERVER-QQ_fc1_to_N5K-PP_E1-10
pwwn 20:00:00:25:b5:55:0b:QQ

Step 53 Verify that the device aliases have been added to the database by entering the
show device-alias database command.

N5K-PP(config-device-alias-db)# show device-alias database

There are no entries in the database

Note Doh! The device aliases w ill not be placed into the database until you commit the changes.

Step 54 Commit the changes to the device-alias database by entering the

device-alias commit command.

N5K-PP(config-device-alias-db)# device-alias commit

Step 55 Verify that the device aliases have been added to the database by entering the
show device-alias database command.

N5K-PP(config)# show device-alias database

device-alias name SAN_STORAGE_VSAN_11 pwwn 50:0a:09:82:86:78:22:ca
device-alias name SAN_STORAGE_VSAN_12 pwwn 50:0a:09:81:86:78:22:ca
device-alias name POD-SERVER-PP_fc0_to_N5K-PP_E1-9 pwwn 20:00:00:25:b5:55:0a:PP
device-alias name POD-SERVER-QQ_fc1_to_N5K-PP_E1-10 pwwn 20:00:00:25:b5:55:0b:QQ

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 155
©2016 NterOne Corporation
 Total number of entries = 4

Step 56 Examine the contents of the fibre channel name server (FCNS) database again by entering the
show fcns database command. At this point the device alias for the NetApp storage controller
should be present in the row after the database entry.

Note Nearly any command that displays WWPNs w ill also display the corresponding device aliases (if
present). It is good practice to create device aliases for each device connecting to the SAN to
simplify management and troubleshooting.

N5K-PP(config-if)# show fcns database

VSAN 1X:
--------------------------------------------------------------------------
FCID TYPE PWWN (VENDOR) FC4 -TYPE:FEATURE
--------------------------------------------------------------------------
0x010000 N 50:0a:09:8?:86:78: 22:ca (NetApp) scsi-fcp
[SAN_STORAGE_VSAN_1X]

Activity Verification
You have completed this task when you attain these results:
 Device aliases have been configured for the SAN storage controllers connected to the fabric.

Task 6: Configure FCoE Interfaces

During this task, you will configure FCoE on the interfaces connecting the Pod Servers to your Pod Switch.

Activity Procedure
Complete these steps:
Step 57 Configure the interfaces connected to the Pod Servers (Ethernet 1/9-10) as 802.1Q trunks. The
two interfaces need to permit VLAN 300 for LAN traffic and permit VLAN 101X for FCoE
traffic.

Note FCoE w ill not function properly on an interface that does not trunk VLAN for LAN traffic and a
VLAN for FCoE traffic.

N5K-PP(config-if)# interface ethernet 1/9-10

N5K-PP(config-if-range)# switchport mode trunk
N5K-PP(config-if-range)# switchport trunk allowed vlan 300,101X
N5K-PP(config-if-range)# switchport trunk native vlan 300
N5K-PP(config-if-range)# spanning-tree port type edge trunk
Warning: Edge port type (portfast) should only be enabled on ports connected to a
single
host. Connecting hubs, concentrators, switches, bridges, etc... to this
interface when edge port type (portfast) is enabled, can cause temporary bridging
loops.
Use with CAUTION
N5K-PP(config-if-range)# no shutdown

Step 58 Verify that interfaces Ethernet 1/9-10 are up and trunking VLANs 300 and 101X by entering
the show interface trunk command.

N5K-PP(config-if)# show interface trunk

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 156
©2016 NterOne Corporation
 ---------------------------------------- ----------------------------------------
Port Native Status Port
Vlan Channel
--------------------------------------------------------------------------------
Eth1/9 300 trunking --
Eth1/10 300 trunking --

--------------------------------------------------------------------------------
Port Vlans Allowed on Trunk
--------------------------------------------------------------------------------
Eth1/9 300,101X
Eth1/10 300,101X

<… output omitted …>

Step 59 Create virtual Fibre Channel (vFC) interfaces for the FCoE traffic on the interfaces connected
to the Pod Servers (Ethernet 1/9-10). Bind the vFC interfaces to the correct Ethernet interfaces.

N5K-PP(config-if-range)# interface vfc 9

N5K-PP(config-if)# switchport description FCoE to Pod Server PP fc0
N5K-PP(config-if)# switchport trunk allowed vsan 1X
Warning: This command will remove all VSANs currently being trunked and trunk only
the specified VSANs.
Do you want to continue? (y/n) [n] y
N5K-PP(config-if)# bind interface ethernet 1/9
N5K-PP(config-if)# no shutdown
N5K-PP(config-if)# interface vfc 10
N5K-PP(config-if)# switchport description FCoE to Pod Server QQ fc1
N5K-PP(config-if)# switchport trunk allowed vsan 1X
Warning: This command will remove all VSANs currently being trunked and trunk only
the specified VSANs.
Do you want to continue? (y/n) [n] y
N5K-PP(config-if)# bind interface ethernet 1/10
N5K-PP(config-if)# no shutdown

Step 60 Examine the state of the vFC interfaces by entering the show interface vfc 9-10 command.

N5K-PP# show interface vfc 9-10

vfc9 is trunking
Bound interface is Ethernet1/9
Port description is FCoE to Pod Server PP fc0
Hardware is Ethernet
Port WWN is 20:08:00:2a:6a:09:fa:7f
Admin port mode is F, trunk mode is on
snmp link state traps are enabled
Port mode is TF
Port vsan is 1
Trunk vsans (admin allowed and active) (1X)
Trunk vsans (up) ()
Trunk vsans (isolated) ()
Trunk vsans (initializing) (1X)
1 minute input rate 0 bits/sec, 0 bytes/sec, 0 frames/sec
1 minute output rate 0 bits/sec, 0 bytes/sec, 0 frames/sec
0 frames input, 0 bytes
0 discards, 0 errors
0 frames output, 0 bytes
0 discards, 0 errors
last clearing of "show interface" counters Sun Jun 19 17:48:44 2016

Interface last changed at Sun Jun 19 17:48:46 2016

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 157
©2016 NterOne Corporation
 vfc10 is trunking
Bound interface is Ethernet1/10
Port description is FCoE to Pod Server QQ fc1
Hardware is Ethernet
Port WWN is 20:09:00:2a:6a:09:fa:7f
Admin port mode is F, trunk mode is on
snmp link state traps are enabled
Port mode is TF
Port vsan is 1
Trunk vsans (admin allowed and active) (1X)
Trunk vsans (up) ()
Trunk vsans (isolated) ()
Trunk vsans (initializing) (1X)
1 minute input rate 0 bits/sec, 0 bytes/sec, 0 frames/sec
1 minute output rate 0 bits/sec, 0 bytes/sec, 0 frames/sec
0 frames input, 0 bytes
0 discards, 0 errors
0 frames output, 0 bytes
0 discards, 0 errors
last clearing of "show interface" counters Sun Jun 19 17:48:44 2016

Interface last changed at Sun Jun 19 17:48:46 2016

Note The Trunk VSANs are in the initializing state and w ill not enter the up state because the VSAN
that the vFC interfaces should use has not been configured.

Step 61 Determine the VSAN to which the vFC interfaces have been assigned by entering the
show vsan membership command. At this point all of the fibre channel and vFC interfaces are
in VSAN 1.

N5K-PP(config-if)# show vsan membership

vsan 1 interfaces:
fc1/21 fc1/22 fc1/23 fc1/24
fc1/25 fc1/26 fc1/27 fc1/28
fc1/29 fc1/30 fc1/31 fc1/32
vfc9 vfc10

vsan 1X interfaces:

vsan 4079(evfp_isolated_vsan) interfaces:

vsan 4094(isolated_vsan) interfaces:

Step 62 Change the VSAN assignment for the vFC interfaces by entering the commands below.

N5K-PP(config-if)# vsan database

N5K-PP(config-vsan-db)# vsan 1X interface vfc 9
N5K-PP(config-vsan-db)# vsan 1X interface vfc 10
N5K-PP(config-vsan-db)# exit

Step 63 Re-enter the show vsan membership command. You should now see that interfaces vfc 9 and
10 are now a member of VSAN 1X.

N5K-PP(config)# show vsan membership

vsan 1 interfaces:
fc1/21 fc1/22 fc1/23 fc1/24
fc1/25 fc1/26 fc1/27 fc1/28

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 158
©2016 NterOne Corporation
 fc1/29 fc1/30 fc1/31 fc1/32

vsan 1X interfaces:
vfc9 vfc10

vsan 4079(evfp_isolated_vsan) interfaces:

vsan 4094(isolated_vsan) interfaces:

Step 64 Re-Examine the state of the vFC interfaces by entering the show interface vfc 9-10 command.
You should now see the interface is in TF (trunked fabric) mode and that VSAN 1X is in an up
state on the trunk.

Note It may take several seconds for the Trunk VSANs to enter the “up” state.

N5K-PP# show interface vfc 9-10

vfc9 is trunking
Bound interface is Ethernet1/9
Port description is FCoE to Pod Server PP fc0
Hardware is Ethernet
Port WWN is 20:08:00:2a:6a:09:fa:7f
Admin port mode is F, trunk mode is on
snmp link state traps are enabled
Port mode is TF
Port vsan is 1X
Trunk vsans (admin allowed and active) (1X)
Trunk vsans (up) (1X)
Trunk vsans (isolated) ()
Trunk vsans (initializing) ()
1 minute input rate 0 bits/sec, 0 bytes/sec, 0 frames/sec
1 minute output rate 0 bits/sec, 0 bytes/sec, 0 frames/sec
88 frames input, 9484 bytes
0 discards, 0 errors
128 frames output, 23860 bytes
0 discards, 0 errors
last clearing of "show interface" counters Sat Jun 18 15:42: 26 2016

Interface last changed at Sat Jun 18 15:42:28 2016

vfc10 is trunking
Bound interface is Ethernet1/10
Port description is FCoE to Pod Server QQ fc1
Hardware is Ethernet
Port WWN is 20:09:00:2a:6a:09:fa:7f
Admin port mode is F, trunk mode is on
snmp link state traps are enabled
Port mode is TF
Port vsan is 1X
Trunk vsans (admin allowed and active) (1X)
Trunk vsans (up) (1X)
Trunk vsans (isolated) ()
Trunk vsans (initializing) ()
1 minute input rate 0 bits/sec, 0 bytes/sec, 0 frames/sec
1 minute output rate 0 bits/sec, 0 bytes/sec, 0 frames/sec
10834 frames input, 1084100 bytes
0 discards, 0 errors
21641 frames output, 10420980 bytes
0 discards, 0 errors
last clearing of "show interface" counters Sat Jun 18 15:42:27 2016

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 159
©2016 NterOne Corporation
 Interface last changed at Sat Jun 18 15:42:28 2016

Step 65 View the addresses that are associated to the Pod Server interfaces by entering the
show interface ethernet 1/9-10 fcoe command.

N5K-PP# show interface ethernet 1/9-10 fcoe

Ethernet1/9 is FCoE UP
vfc9 is Up
FCID is 0x6f0000
PWWN is 20:00:00:25:b5:55:0a:PP
MAC addr is 7c:ad:74:27:c4:6e
Ethernet1/10 is FCoE UP
vfc10 is Up
FCID is 0x6f0020
PWWN is 20:00:00:25:b5:55:0b:QQ
MAC addr is 7c:ad:74:27:4f:33

Step 66 Verify that the Pod Servers have successfully logged in to the SAN fabric by entering the
show flogi database command. There should be two entries; one for the fc0 interface of your
Pod Server, and one for the fc1 interface of your Peer Pod Server.

N5K-PP(config-if)# show flogi database

--------------------------------------------------------------------------------
INTERFACE VSAN FCID PORT NAME NODE NAME
--------------------------------------------------------------------------------
vfc9 1X 0x6f0000 20:00:00:25:b5:55:0a:PP 20:00:00:25:b5:55:0f:PP
[POD-SERVER-PP_fc0_to_N5K-PP_E1-9]
vfc10 1X 0x6f0020 20:00:00:25:b5:55:0b:QQ 20:00:00:25:b5:55:0f:QQ
[POD-SERVER-QQ_fc1_to_N5K-PP_E1-10]

Total number of flogi = 2.

Step 67 Now that the Pod Switch is connected to the SAN, and the Pod Servers are logged in to the
fabric, the Pod Servers should be able to access the storage configured specifically for them.
The NetApp storage on the SAN fabrics is configured with a 1 GB LUN that is mapped to the
WWPNs of your Pod Server. If everything is configured properly on your Pod Switch the 1 GB
LUN should be visible on your Pod Server. Return to the Remote Desktop Connection session
to your Pod Server.
Step 68 From your Pod Server start the Disk Management application. There should be a shortcut on
the Pod Server desktop.

Note If the shortcut is not present on the Pod Server desktop, start the Disk Managem ent application
by clicking the start button and then entering “diskm gmt.msc” in the “Search programs and
files” field directly above the Start button.

Step 69 The Disk Management window will appear and look similar to the image below.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 160
©2016 NterOne Corporation
 Note You should NOT see the 1 GB LUN at this point; there is still one more task before your Pod
Server can see it’s 1 GB LUN.

Step 70 Return to the PuTTY session to your Pod Switch.

Step 71 To implement simple (but insecure) Fibre Channel zoning, configure a default policy of permit
for VSAN 1X.

N5K-PP(config)# zone default-zone permit vsan 1X

Note This zoning policy is not a recommended practice and is being used for lab purposes only.

Step 72 Return to the Remote Desktop Connection session to your Pod Server.
Step 73 Re-examine the contents of the Disk Management application. You should now see at least one
1 GB disk.

Note You w ill see tw o 1 GB disks only if you and your Peer Pod have completed all of the tasks up to
this point. The Pod Server w ill see tw o disks because it is seeing the same disk across both
fabrics.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 161
©2016 NterOne Corporation
Activity Verification
You have completed this task when you attain these results:
 You have configured and verified the operation of the Ethernet and vFC interfaces on your Pod
Switch.
 You have verified that the Pod Server has access to the Fibre Channel storage.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 162
©2016 NterOne Corporation
Lab 12: Accessing the NterOne Lab Devices
(Cisco UCS Lab Rack)
The purpose of this lab exercise is to make you familiar with the NterOne lab environment and how to
successfully connect to the various devices that you will use during this class.

Task 1: Understanding your NterOne Lab Environment

Before you can begin configuring you lab devices you must understand how the NterOne lab environment is
constructed and how it is accessed.

Your Student Server

Before you can gain access to the NterOne lab devices you must first successfully log in to a Student Server.
 Once you have successfully logged in to a Student Server you will be able to use the applications
installed on the Student Server to access the lab devices for your class.
 Student Server names and account credentials will be given to you by your instructor.
 Two students may log in to the same Student Server using different accounts; in this case each
student will have a unique Desktop which is not shared with the other student.

The Student Servers are often referred to by a two-digit number (the Student Server Number) which is part of
the DNS and IP address of the Student Server.
 The first digit in the Student Server number corresponds to the NterOne Class Room Number to
which the Student Server belongs.
 The second digit in the Student Server number is the number of the specific Student Server within
that Room.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 163
©2016 NterOne Corporation
Lab Devices and Pods
During this class you will be using a UCS Lab Rack. A UCS Lab Rack contains the following equipment:
 Two (2) Cisco UCS Fabric Interconnects running UCS Manager version 2.1
 One (1) Cisco UCS 5108 Blade Server Chassis
 Two (2) Cisco UCS Fabric Extenders (I/O Modules)
 Eight (8) Cisco UCS Blade Servers
 Two (2) Cisco Layer 2 switches
You will have access to all of these devices; however you will be assigned a single Pod within the UCS Lab
Rack:
 A Pod is a portion of the UCS Lab Rack that is configured by one or two students.
 A Pod Number is used to uniquely identify each Pod. The Pod Number (“X”) is a value between 1
and 8, and it also indicates the slot number of the B-Series blade server assigned to that Pod.

 You will be assigned to a Pod for a given lab exercise, possibly with another student depending on
the class size.
 During the lab exercises you will be asked to configure the devices in your Pod. Do not configure
any devices outside your assigned Pod unless specifically instructed to do so.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 164
©2016 NterOne Corporation
Letter Variables
The Lab Guide for your class uses letter variables (similar to algebra) to represent digits within a command
or command output. Usually, whenever you see one of the capital letters in the following table you should
replace that letter with the correct value; the Lab Guide should also point out when a letter variable is being
used.
For example, if you are currently assigned to Pod 2, and if you are instructed to create a policy within UCS
Manager called “PodX-Policy”, the name of your policy would be “Pod2-Policy”. The following table lists
all of the letter variables that are commonly used in the Lab Guide.

Letter Variable Description

R The first digit of your Student Server Number (your Class Room number)
S The last digit of your Student Server Number
Your Pod Number, and
X
the slot number w ithin the UCS B-Series chassis w here your blade server is located
Z The number of the UCS Domain in your UCS Lab Rack

You should determine the value of each of these letter variables before you start each lab exercise. If you do
not use the correct values you may not be able to complete the lab exercise and you may also cause another
student’s lab devices to malfunction.

Remote Desktop Connection

The application that you must use to log in to your Student Server is Remote Desktop Connection (RDC).
 This is the only application that can be used to log in to your Student Server.
 The shortcut to RDC is typically found on Windows-based systems by clicking Start  All
Programs  Accessories  Remote Desktop Connection. Another way to find RDC is to use the
“Search programs and files” function in the Windows Start menu.

or

 Students using Apple-based computers can download the Microsoft Remote Desktop app from
https://itunes.apple.com/us/app/id715768417?mt=12 .
 Students using Linux-based computers can download rdesktop from http://www.rdesktop.org/ .

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 165
©2016 NterOne Corporation
Task 2: Connect to your Assigned Student Server using Remote
Desktop Connection (RDC)
Follow the steps in this Task in order to log in to a Student Server.
Step 1 Your instructor will give you the information you need to log in to a Student Server. The
following table is provided for you to record these values.

Student Server Nam e / IP Address User Nam e Passw ord

Step 2 Log in to your personal/work computer.

Step 3 Verify that your computer is able to access the Internet. A simple test to verify this would be to
use a browser to access www.nterone.com .
Step 4 Verify that your computer has a Remote Desktop Connection (RDC) client installed. Use the
information on the previous page if you are having difficulty finding RDC on your computer.
Step 5 Start the Remote Desktop Connection application. The following window should appear.

Note The follow ing steps use the Microsoft version of RDC; if you are using an Apple- or Linux-based
computer the screens that you w ill see w ill be different.

Step 6 In the Computer field enter the DNS name or IP address of the Student Server that has been
assigned to you.
Step 7 Click the Connect button.The Windows Security window should appear.

Note If this step fails after several seconds, please contact your class instructor for assistance.

Note If you are able to access the Internet but are unable to access any of the NterOne Student
Servers you w ill need to determine if there is a firew all somew here preventing your computer
from accessing the NterOne Student Servers. This is a common problem for students w ho are
using a computer at their place of employment, in w hich case you may need to contact your
company’s IT department f or assistance.

Step 8 Click on the “Use another account” section of the window.

Step 9 Enter the User name and Password needed to connect to the Student Server.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 166
©2016 NterOne Corporation
 Step 10 Click the OK button. A window should appear which will look similar to the window below

Step 11 Click the check box next to “Don’t ask me again for connections to this computer” and then
click “Yes”.
Step 12 After a few seconds the login process should finish and the desktop of your Student Server
should appear which will look similar to the window below.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 167
©2016 NterOne Corporation
 Step 13 Information about how your Student Server is configured will be displayed in the upper right -
hand corner of the Desktop.

Step 14 The most commonly used applications such as PuTTY will have shortcut to them on the
Desktop. Other applications may also be found using the Start menu.
Step 15 Some files that you will be using during the class will be located in the S: drive, also referred to
as the students file share. There is a shortcut to this location on the Desktop. There is also a
shortcut on the Desktop to the Local Class Files, which may also be used during the class.

Step 16 The process to connect to your Student Server is complete.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 168
©2016 NterOne Corporation
Task 3: Log In to the UCS Manager for the UCS Domain
This procedure details the steps you will use to start the UCS Manager application and log in to the UCS
domain. This procedure assumes that you have successfully accessed your Student Server.
Step 17 From the desktop of your Student Server open a browser and navigate to the URL of the UCS
Manager of the UCS Domain that you will be using during this class. The following table
contains the URLs for each possible UCS Domain.

UCS Dom ain UCS Manager URL

UCS1 https://10.1.7.16
UCS2 https://10.1.7.32
UCS3 https://10.1.7.48
UCS4 https://10.1.7.64

Step 18 Click the Launch UCS Manager button.

Step 19 You will see the Java 6 splash screen for a second or two. The UCS Manager is a Java-based
application and must be downloaded from the UCS domain.
Step 20 Due to the fact that UCS Manager is a Java-based application you may see one or both of the
security warning windows shown below. If you see one of these windows click the check box
next to Always trust content from this publisher and then click Yes or Run.

Step 21 The UCS Manager – Login to UCS window will appear.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 169
©2016 NterOne Corporation
 Step 22 Login to the UCS Manager with the credentials below:
 Username: admin
 Password: Nterone179
Step 23 You should now see the Cisco Unified Computing System Manager window. If you have
used this UCS Manager before you will be returned to the last point in the interface that you
used, otherwise you will see the image below.

Step 24 The process to log in to the UCS Manager for your UCS Domain is complete.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 170
©2016 NterOne Corporation
Lab 13: Exploring the Cisco UCS Manager GUI
Complete this lab activity to practice what you learned in the related module.

Activity Objective
In this activity, you will explore the UCS Manager GUI interface. This lab focuses on the functionality of the
Cisco UCS Manager GUI, and not on the execution of tasks. Take your time and click as many tabs and
options as needed to become familiar with the Cisco UCS Manager GUI layout. After completing this
activity, you will be able to meet these objectives:
 Navigate the Equipment tab and explore important options
 Navigate the Servers tab and explore important options
 Navigate the LAN tab and explore important options
 Navigate the SAN tab and explore important options
 Navigate the VM tab and explore important options
 Navigate the Admin tab and explore important options

Note The steps in this lab exercise assume that you are familiar w ith the information contained in
Lab 0 – Accessing the NterOne Lab Devices.

Task 1: Connect to and Navigate Cisco UCS Manager

In this task, you will connect to and navigate the Cisco UCS Manager GUI.

Activity Procedure
Complete the following steps:
Step 1 From your Student Server, start the Cisco UCS Manager application for your UCS domain.
Step 2 Take note of a few important aspects of the overall Cisco UCS Manager GUI layout.

 The left quarter vertical panel is called the navigation panel.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 171
©2016 NterOne Corporation
  The right three quarter vertical panel is called the content panel. The content in this panel will
change depending on which tab in the navigation panel is selected. To verify, click the different tabs
in the navigation panel and note how the content changes.
 The user controls the size of the navigation and content panels. Move the mouse over the vertical
border of the two panels. When you see a left and right arrow, left-click and move the mouse to the
left or right to expand or contract the size of the two panels.
 Above the content panel is a ribbon thread showing your current location in the Cisco UCS Manager
GUI.
Step 3 Above the navigation panel is the Fault Summary section. The Fault Summary section is visible
at all times, regardless of where you are on the navigation or content panel. Clicking a
particular fault takes you to the Faults, Events, and Audit Log.

Step 4 Above the content panel, click the Options button. The UCS Manager – Properties window
will appear.

Step 5 Review the four different properties that you can configure. In particular, the Confirmation
Messages panel allow you to disable the windows that can pop up while you are configuring
Cisco UCS Manager. Close the UCS Manager – Properties window after you are finished
exploring.

Activity Verification
 You have completed this task when you attain this result:
 You have explored the overall layout of the Cisco UCS Manager GUI.

Task 2: Explore the Equipment Tab

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 172
©2016 NterOne Corporation
 In this task, you will explore the information available from the Equipment tab in the navigation panel, and
correlate this information with the entire Cisco UCS system.

Activity Procedure
Complete the following steps:
Step 6 Click the Equipment tab in the navigation panel and then click to highlight Equipment in the
navigation panel.

Step 7 The Filter drop-down menu near the top of the navigation panel (below the tabs) allows you to
reduce the amount of content in the navigation panel, enhancing readability. The Filter drop -
down menu will be visible regardless of which tab is selected. Experiment with the Filter drop -
down menu.

Step 8 The plus sign (+) and minus sign (–) icons below the Filter menu allow you to quickly expand
or collapse the entire navigation panel. Experiment with the plus sign (+) and minus sign (–)
icons.

Step 9 The figure shows the tabs in the content panel when Equipment is highlighted in the navigation
panel. In addition to the subcategories under Equipment on the Equipment tab, there are
Equipment configuration options in the content panel. The Main Topology View tab provides a
high-level visual of the Cisco UCS system.
Step 10 The Fabric Interconnects and Servers tabs in the content panel provide high-level
information that can also be viewed by expanding the appropriate items in the navigation panel.
Explore the Fabric Interconnects and Servers tabs in the content panel.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 173
©2016 NterOne Corporation
 Step 11 Click Firmware Management in the content panel.

 The Installed Firmware tab provides details on the firmware versions (Running, Startup, and
Backup versions) of every Cisco UCS component.
Step 12 Explore the other tabs under Firmware Management within the content panel.
Step 13 Expand Chassis within the Equipment tab in the navigation panel by clicking the plus sign (+)
to the left of Chassis. Expand Chassis 1 and Servers. Click to highlight Chassis 1.

 Note that the content panel of Chassis 1 includes tabs to look at the Servers, IO Modules, Fans, and
PSUs. This interface is an abbreviated method to review the different components within a chassis,
in addition to drilling down the chassis via the navigation panel.
 From the General tab within the content panel, there are many actions that you can take, including
Acknowledge or Decommission a Chassis.
Step 14 Right-click Chassis 1 in the navigation panel. Note that you can also execute many of these
same actions on a chassis.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 174
©2016 NterOne Corporation
 Step 15 Expand the Status Details within the Status portion of the content panel, by clicking the
chevron, to clarify the Overall Status of the Chassis.

Step 16 Explore the tabs and information available to you in the content panel.
Step 17 Click Server 1 in the navigation panel under Equipment > Chassis > Chassis 1 > Servers.

 The overall layout of the content panel provides a number of tabs that allow you to view a physical
display of a server, and the Properties and Actions of the server.
 There are different Actions that you can take on Server 1.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 175
©2016 NterOne Corporation
  The Overall Status of the Server is Unassociated. This status will change after the user configures
service profiles in a later lab.
 Note that if you right-click Server 1 within the navigation panel, you can also take many of the same
actions that are available in the content panel.
Step 18 Explore the tabs and information available to you in the content panel.
Step 19 Expand Fabric Interconnect A and B on the navigation panel under Equipment > Fabric
Interconnects by clicking the plus sign (+). Click to highlight Fabric Interconnects in the
navigation panel.

 Similarly to the Chassis, when Fabric Interconnect is highlighted in the navigation panel, you can
view specifics about each Fabric Interconnect, such as Fixed Module details, IO Modules, Fans, or
Power. Conversely, you could also expand the Fixed Module, Fans, or Power under a specific
Fabric Interconnect within the navigation panel.
Step 20 If you right-click Fabric Interconnect in the navigation panel, note that no action options are
available. Explore the tabs and information available to you in the content panel.
Step 21 Click to highlight Fabric Interconnect A within the navigation panel.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 176
©2016 NterOne Corporation
  In the content panel you have access to the different configuration managers—Internal Fabric, LAN
Uplinks, SAN Uplinks, and so on.
 If you right-click Fabric Interconnect A within the navigation panel, you can enable some of the
configuration managers and execute many of the same actions available on the content panel.
 Note the Physical Display of the Fabric Interconnect within the content panel. This display provides
a quick way to visually determine which interfaces are up, down, or not connected.
Step 22 Explore the tabs and information available to you in the content panel.

Activity Verification
You have completed this task when you attain these results:
 You have explored the Equipment tab of the navigation panel to view the hardware-specific details
of the entire Cisco UCS system.
 You know where to navigate to determine the hardware details of the servers within the Cisco UCS
system.
 You know where to navigate to determine the hardware details of the fabric interconnects within the
Cisco UCS system.
 You know that right-clicking a hardware component in the navigation panel sometimes offers the
same actions available to you on the content panel.

Task 3: Explore the Servers Tab

In this task, you will explore the information available from the Servers tab in the navigation panel, and
correlate this information with the entire Cisco UCS system.

Activity Procedure
Complete the following steps:
Step 23 In the Cisco UCS Manager GUI, click the Servers tab in the navigation panel and then click to
highlight Servers.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 177
©2016 NterOne Corporation
  While the Equipment tab from the previous task covered the hardware-specific components of the
Cisco UCS system, the Servers tab only covers the virtual portions of the Cisco UCS system,
including the service profiles (which define the entire configuration of a server and override the
identity values that are on the physical server at the time of association), the policies (which are
attached to a service profile and provide granular control over different administrative tasks), the
pools (which define the universally unique identifier [UUID] to be used), and the server pools
(which provide control over what type of hardware is desired for a specific service profile).
 Service profiles are a significant capability of the Cisco UCS system. Service profiles allow the
abstraction of the configuration of a server to be totally controlled by the user. Service profiles
provide mobility for maintenance or high availability.
 In a later lab, you will configure service profiles. For now, note that there are no service profiles
preconfigured in Cisco UCS.
 Service profile templates are optional and allow for ease of configuration when you need several
service profiles with the same basic parameters, such as the number of vNICs and vHBAs, and with
identity information that is drawn from the same pools.
 Note that by right-clicking Service Profiles in the navigation panel, you can create service profiles.
 Another way to create service profiles is to click the plus sign (+) (at the far right of the content
panel) when the All tab is selected.
Step 24 Expand Service Profiles > root. Click to highlight Service Profiles.

 Organization is a hierarchical construct (with root as the default top level) that allows administrators
to partition resources logically, to scale management more effectively, and to support multitenancy.
Any suborganizations that are created will have a corresponding set of pools, policies, and templates
within their management scope. You will configure organizations in a later lab.
 You can create a new suborganization by right-clicking Sub-Organizations (on any tab where you
see Sub-Organizations).

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 178
©2016 NterOne Corporation
  Note the different tabs that are available in the content panel. Initially, the tabs will be empty until
server profiles are configured and associated.
Step 25 Click the Filter drop-down menu and choose Policies. Expand Policies by clicking the plus
sign (+) to the left of the word. Click to highlight Policies.

 Use the Filter drop-down menu to limit the display to Policies. This action will improve the
readability of the navigation panel.
 The options under Policies on the navigation panel are similar to the tabs available within the
content panel. To create new policies, right-click any of the options under Policies. Optionally, you
can click the plus sign (+) (at the right of the content panel) when Policies is selected.
Step 26 Click the Filter drop-down and choose Pools. Expand Pools by clicking the plus sign (+) to the
left of the word. Click to highlight Pools.

 Use the Filter drop-down menu below the tabs in the navigation panel to limit the display to Pools.
This action will improve the readability of the navigation panel.
 Similarly to policies, the content panel mimics the pool options in the navigation panel. You can
either right-click a pool type in the navigation panel, or click the plus sign (+) on the right of the
content panel, when the tab is selected, to create a new pool.

Activity Verification
You have completed this task when you attain these results:
 You have explored the Servers tab of the navigation panel to view the virtual server details of the
entire Cisco UCS system.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 179
©2016 NterOne Corporation
  You know where to navigate to determine the configuration details of the servers within the Cisco
UCS system.
 You know that right-clicking a component in the navigation panel sometimes offers the same
actions available to you on the content panel.

Task 4: Explore the LAN Tab

In this task, you will explore the information available from the LAN tab in the navigation panel, and
correlate this information with the entire Cisco UCS system.

Activity Procedure
Complete the following steps:
Step 27 Click the LAN tab in the navigation panel and click to highlight LAN. Expand LAN by
clicking the plus sign (+) to the left of LAN.

 The LAN tab is used to configure a mix of the hardware and virtual aspects that are specific to LAN
networking in the Cisco UCS system. For example, LAN Cloud concerns the uplinks from the Cisco
UCS system (the fabric interconnects in particular) to the rest of the network. LAN Cloud is also
where the VLANs for the entire Cisco UCS system are configured.
 The internal LAN controls the connections that are internal to the UCS system, from the fabric
interconnects to the I/O modules on the chassis.
 Similarly to the Servers tab, policies and pools specific to LAN can be configured.
 Note that you can launch the LAN Uplinks Manager from the bottom of the content panel (under
Port Channels and Uplinks). Remember from Task 2 that you can also launch the LAN Uplinks
Manager from Equipment > Fabric Interconnects > Fabric Interconnect A (or B).
Step 28 Filter the navigation panel on the LAN Cloud, and click the plus sign (+) below the filter to
expand the entire LAN Cloud.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 180
©2016 NterOne Corporation
  Again, note the uplink connection details under Fabric A or Fabric B. Connections can include
individual interfaces or port channels.
 Although you can configure VLANs per fabric, the typical scenario is to configure VLANs globally
via VLANs at the bottom of the LAN Cloud in the navigation panel.
Step 29 Filter the navigation panel on the Internal LAN, and click the plus sign (+) below the filter to
expand the entire Internal LAN. Click to highlight Internal LAN in the navigation panel, and
click the tab Server Links in the content panel.

 The internal LAN is specific and limited to the downlinks from the Cisco UCS Fabric Interconnects
to the I/O modules on the Cisco UCS chassis.
 You can view the links and port channels that are in use, and configure (add or remove) other links,
by using the Ports window within the content panel.
Step 30 Filter the navigation panel on Policies, and click the plus sign (+) below the filter to expand the
Policies. Click to highlight Policies in the navigation panel.

 Note that the policy configurations available are specific to LAN networking.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 181
©2016 NterOne Corporation
  Note the overlap in the options available under Policies in the navigation panel and the tabs in the
content panel.
Step 31 Filter the navigation panel on Pools, and click the plus sign (+) below the filter to expand the
Pools. Click to highlight Pools in the navigation panel.

 LAN pools are limited to MAC pools. Note that you can create new MAC pools by either right-
clicking MAC pools within the navigation panel, or by clicking the plus sign (+) (at the right side of
the content panel) when the MAC Pools tab is selected.
 Each server in a Cisco UCS domain must have a management IP address that is assigned to its Cisco
Integrated Management Controller (Cisco IMC) or to the service profile associated with the server.
Cisco UCS Manager uses this IP address for external access that terminates in the Cisco IMC
through the KVM console, Serial over LAN, or an IPMI tool.
 Before Cisco UCS 2.0, the IP pool that was used to manage these addresses was configured via the
Admin tab in the navigation panel. After UCS 2.0, the IP pool configuration has been moved to
Pools under the LAN tab of the navigation panel.

Activity Verification
You have completed this task when you attain these results:
 You have explored the LAN tab of the navigation panel to view the details specific to the LAN
connectivity of the entire Cisco UCS system.
 You know where to navigate to determine the configuration details of the LAN uplinks, downlinks,
policies, and pools within the Cisco UCS system.
 You know that right-clicking a component in the navigation panel sometimes offers the same
actions available to you on the content panel.

Task 5: Explore the SAN Tab

In this task, you will explore the information available from the SAN tab in the nav igation panel, and
correlate this information with the entire Cisco UCS system.

Activity Procedure
Complete the following steps:
Step 32 Click the SAN tab in the navigation panel, and then click to highlight SAN. Expand SAN by
clicking the plus sign (+) to the left of SAN.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 182
©2016 NterOne Corporation
  Similarly to the LAN tab, the SAN tab is used to configure a mix of the hardware and virtual aspects
specific to SAN networking of the Cisco UCS system. For example, SAN Cloud concerns the Fibre
Channel uplinks from the Cisco UCS system (the fabric interconnects, in particular) to the rest of
the network. SAN Cloud is also where the VSANs for the entire UCS system are configured.
 Unlike the LAN tab, there is no Internal SAN option because there are no Fibre Channel
connections between the Cisco UCS fabric interconnects and the Cisco UCS chassis.
Step 33 Filter the navigation panel on the SAN Cloud, and click the plus sign (+) below the filter to
expand the entire SAN Cloud.

 The uplink connection details for Fabric A or B are detailed here. Connections can include
individual interfaces or port channels. Fibre Channel connections have not yet been configured, so
no links are shown here.
 Although you can configure VSANs per fabric, the typical scenario is to configure VSANs globally
(via VSANs at the bottom of the SAN Cloud in the navigation panel).
Step 34 Filter the navigation panel on Policies, and click the plus sign (+) below the filter to expand the
policies. Click to highlight Policies in the navigation panel.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 183
©2016 NterOne Corporation
  Note that the policy configurations available are specific to SAN networking.
 Note also the amount of overlap in the options available under Policies in the navigation panel, and
the tabs in the content panel.
Step 35 Filter the navigation panel on Pools, and click the plus sign (+) below the filter to expand the
pools. Click to highlight Pools in the navigation panel.

 SAN pools consist of IQN, WWNN, WWPN, and WWxN pools. WWxN pools are new in Cisco
UCS 2.1 code. A WWxN pool is a WWN pool that contains both WW node names and WW port
names.
 Note that you can create new pools by either right-clicking a pool within the navigation panel, or by
clicking the plus sign (+) (at the right side of the content panel) when a particular pools tab is
selected.

Activity Verification
You have completed this task when you attain these results:
 You have explored the SAN tab of the navigation panel to view the details specific to the SAN
connectivity of the entire Cisco UCS system.
 You know where to navigate to determine the configuration details of the SAN uplinks, policies,
and pools within the Cisco UCS system.
 You know that right-clicking a component in the navigation panel sometimes offers the same
actions available to you on the content panel.

Task 6: Explore the VM Tab

In this task, you will briefly explore the information available from the VM tab in the navigation panel, and
correlate this information with the entire Cisco UCS system.

Activity Procedure

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 184
©2016 NterOne Corporation
 Complete the following step:
Step 36 Click the VM tab in the navigation panel, and click the plus sign (+) below the filter to expand
the entire navigation panel. Click to highlight All.

 The VM tab is used to configure a feature that is called VM-FEX. However, there are configuration
requirements that extend beyond the VM tab. For example, you must create a dynamic vNIC
connection policy (under the LAN tab), and create a service profile for VM-FEX (under the Servers
tab).
 Port profiles contain the properties and settings to configure virtual interfaces in Cisco UCS for
VM-FEX, which interface with different hypervisors.
 The Cisco UCS cluster is a grouping of hypervisors that can be distributed across multiple hosts. In
a Hyper-V system, the cluster is analogous to the distributed virtual switch (DVS) in a VMware
ESX system. The cluster defines the scope of the port profile and is the boundary of the migration
domain. When multiple hypervisor hosts are associated to a cluster, you can migrate a VM from one
host to another within the cluster.

Activity Verification
You have completed this task when you attain these results:
 You have explored the VM tab of the navigation panel to view the details specific to the use of
hypervisors within the Cisco UCS system.
 You know where to navigate to determine the configuration details of the VMs within the Cisco
UCS system.
 You know that right-clicking a component in the navigation panel sometimes offers the same
actions available to you on the content panel.

Task 7: Explore the Admin Tab

In this task, you will explore the information available from the Admin tab in the navigation panel, and
correlate this information with the entire Cisco UCS system.

Activity Procedure
Complete the following steps:
Step 37 Click the Admin tab in the navigation panel and click to highlight All. Expand All by clicking
the plus sign (+) to the left of All.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 185
©2016 NterOne Corporation
  Administration of the Cisco UCS system includes logging (Fault, Events, and Audit), authentication
(RADIUS, LDAP, and TACACS), external communication (DNS, Call Home, UCS Central),
firmware (Capability Catalog), and License Management.
 When All is highlighted in the Admin tab of the navigation panel, the content panel provides the
options necessary to back up and import configurations.
 The large number of options in the Admin tab makes the Filter drop-down menu very useful.
Step 38 Click the Filter drop-down menu and choose Faults, Events, and Audit Log.

 Recall that in Task 1, the Fault Summary section (above the navigation panel) was introduced. The
Fault Summary section will be visible at all times, regardless of where you are on the navigation or
content panel. When you click a particular fault, you will be taken to the Faults, Events, and Audit
Log under the Admin tab.
 You have maximum granularity in terms of what to display, based on Category and Severity, by
checking the radio boxes. Uncheck a few radio boxes and observe the results.
 When you choose a specific fault in the content panel, the fault detail appears in the Details panel of
the content panel.
Step 39 Click the Audit Logs link in the navigation panel.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 186
©2016 NterOne Corporation
  The Audit Log records every configuration change that is made to the Cisco UCS Manager
database. This log can be a useful tool for determining which user created, modified, or deleted a
particular object.
Step 40 Click the Filter drop-down menu and choose User Management. Expand the navigation panel
by clicking the plus sign (+) to the left of User Management.

 Authentication for controlling access to the Cisco UCS system is configured on this panel. Similarly
to Cisco NX-OS Software, role-based access control (RBAC) is available (via Roles under User
Services) for controlling what a user can see and modify.
 Locales assign or restrict user privileges and roles by organization, if you do not want all users to
have access to all organizations.
 User Services > Locally Authenticated Users is where you add, modify, and delete locally
authenticated Cisco UCS Manager users. Although the admin user cannot be deleted, it is a best
practice to disable admin user and assign administrative privileges to individual users.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 187
©2016 NterOne Corporation
 Step 41 Click the Filter drop-down and choose Communication Management. Expand the navigation
panel by clicking the plus sign (+) to the left of the filter. Explore the options available to
configure.

Activity Verification
You have completed this task when you attain these results:
 You have explored the Admin tab of the navigation panel to view the details specific to the
administration of the Cisco UCS system.
 You know where to navigate to determine the configuration details for the administration of the
Cisco UCS system.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 188
©2016 NterOne Corporation
Lab 14: Creating a Service Profile from a
Template and Performing VMware ESXi 5.1 SAN
Boot
Complete this lab activity to demonstrate what you learned in the related module.

Activity Objective
In this activity, you will generate a service profile for your pod and boot VMware ESXi 5.1 from Fibre
Channel SAN. After completing this activity, you will be able to meet these objectives:
 Explain how to access the KVM console in Cisco UCS Manager
 Explain how to properly shut down a VMware ESXi server
 Explain how to disassociate a service profile from a blade server
 Explain how to spawn a service profile from a service profile template
 Explain how to monitor service profile association with the FSM tab
 Explain how to boot the server

Note The steps in this lab exercise assume that you are familiar w ith the information contained in
Lab 0 – Accessing the NterOne Lab Devices.

Visual Objective
Please refer to the NterOne Resource Guide for this class in order to view the lab diagrams for this lab
exercise.

Task 1: Launch the KVM of Your Service Profile

In this task, you will connect to the KVM Console of your Pod’s Service Profile.

Activity Procedure
Complete these steps:

Note The examples show n in all tasks of this lab are based on Pod 1. Be sure to use the values that
are associated w ith your assigned Pod.

Step 1 From your Student Server, start the Cisco UCS Manager application for your UCS domain.
Step 2 In the UCS Manager navigation pane, click the Servers tab.
Step 3 Expand Servers >Service Profiles > root > Sub-Organizations> (Your Organization).
Step 4 Right-click PodX-Service-Profile-BFS (replace “X” with your assigned Pod Number) and then
select KVM Console from the context menu.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 189
©2016 NterOne Corporation
 Note Before you see the KVM Console you may need to address some security prompts generated by
the Java applet.

Step 5 When the KVM Console window appears look at the bottom left-hand side of the window. You
may see a status message similar to the following image. This indicates that the KVM Console
software has not completely finished loading.

Step 6 You will not be able to use the KVM Console until you see a status message similar to the
following image.

Step 7 When the KVM Console is finished loading you will be presented with the service console of
the VMware ESXi host running on your blade server.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 190
©2016 NterOne Corporation
 Step 8 Click in the KVM Console window and press the F12 key until you receive a login prompt.

Step 9 Authenticate with the username root and the password Nterone179.
Step 10 When the Shut Down/Restart window appears, press the F2 key to shut down VMware ESXi.

Step 11 The server will not prompt you to confirm your choice; it will immediately begin shutting
down.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 191
©2016 NterOne Corporation
 Step 12 You will know that the ESXi host has finished shutting down when you see a green background
with the words No Signal in yellow. This is what you will see in the KVM Console when the
associated blade server is turned off.

Step 13 Close the KVM Console window.

Activity Verification
You have completed this task when you attain this result:
 You have used the KVM console of your service profile and to down the VMware ESXi server
running on the blade server.

Task 2: Disassociate the Existing Service Profile

In this task, you will disassociate the existing service profile from your Pod’s blade server. You will need the
blade server in a disassociated state in order to complete this lab exercise.

Activity Procedure
Complete the following steps:
Step 14 In the UCS Manager navigation pane, click the Servers tab.
Step 15 Expand Servers > Service Profile Templates > root > Sub-Organizations > (Your Organization).
Step 16 Right-click the existing service profile and then select Disassociate Service Profile from the
context menu.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 192
©2016 NterOne Corporation
 Step 17 You will be asked if you want to continue with the disassociation process.

Step 18 Click Yes, and then click OK to close the confirmation dialog box when it appears.
Step 19 Although the Status of the service profile will indicate Unassociated, there are still processes
operating on the blade.

Step 20 Now that the service profile has been disassociated from the server you can delete it. Right-
click the service profile and then select Delete from the context menu

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 193
©2016 NterOne Corporation
 Step 21 You will be asked if you want to continue with the deletion process.

Step 22 Click Yes, and then click OK to close the confirmation dialog box when it appears.
Step 23 You can observe the disassociation process by navigating to the server under Equipment >
Chassis > Chassis 1 > Server X (replace “X” with your assigned Pod Number). Click the FSM
tab and observe the process of disassociation.

Note You can alw ays observe actions being performed on a server using this method.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 194
©2016 NterOne Corporation
Activity Verification
You have completed this task when you attain this result:
 You observe that all disassociation tasks are complete and the blue Progress Status bar reaches
100%.

Task 3: Generate a Service Profile from a Template

In this task, you will generate a service profile from a template and observe the association process.

Activity Procedure
Complete these steps:
Step 24 In the UCS Manager navigation pane, click the Servers tab.
Step 25 Expand Servers > Service Profile Templates > root > Sub-Organizations > (Your Organization).
Step 26 Right-click the service profile template that is present in your organization (PodX-SP-
Template-BFS) and then select Create Service Profiles from Template from the context
menu.

Step 27 The Create Service Profiles From Template wizard will appear. This wizard allows you to
create multiple service profiles derived from a template at once. You will be creating a single
service profile with a temporary name which you will change in the next Task. Enter the values
in the following table.

Field Value
Nam ing Prefix podX-new -service-policy (replace “X” w ith your Pod Number)
Nam e Suffix Starting Num ber 0
Num ber of Instances 1

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 195
©2016 NterOne Corporation
 Step 28 Click OK to complete the wizard, and then click OK to close the confirmation dialog box when
it appears.
Step 29 In the Servers tab, expand Servers > Service Profiles > root > Sub-Organizations > (Your
Organization) and click podX-new-service-profile0. You should see that the Overall Status of
the service profile is in the Config state, meaning that the UCS Manager is currently associating
the service profile to your blade server.

Step 30 In the content panel click the FSM tab. You can see the progress of the association process at
this location.

Note It w ill typically take from three to five minutes to complete the service profile association process.

Step 31 When the Progress Status reaches 100% that indicates that the association process is complete.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 196
©2016 NterOne Corporation
 Step 32 In the content panel click the General tab then click to open the Status Details and Assigned
Server or Server Pool sections. You should see that the service profile has been associated to a
server in your PodX-Pool-Server Server Pool. The specific server that was used is listed next
to Associated Server.

Activity Verification
You have completed this task when you attain this result:
 You generated a service profile from an updating template and observed the association process.

Task 4: Rename a Service Profile

In this task, you will rename an existing service profile. When you rename a service profile, the following
occurs:
1. Event logs and audit logs that reference the previous name of the service profile are retained under that
name.
2. A new audit record is created to log the rename operation.
3. All records of faults against the service profile under its previous name are transferred to the new service
profile name.

Note You cannot rename a service profile that has pending changes.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 197
©2016 NterOne Corporation
Activity Procedure
Complete these steps:
Step 33 In the UCS Manager navigation pane, click the Servers tab.
Step 34 Expand Servers > Service Profiles > root > Sub-Organizations > (Your Organization).
Step 35 Right-click podX-new-service-profile0 and then select Rename Service Profile from the
context menu.

Step 36 Click Yes to continue when prompted.

Step 37 In the Rename Service Profile dialog box, enter the values in the following table.

Note This name can be betw een 2 and 32 alphanumeric characters. You cannot use spaces or any
special characters other than - (hyphen), _ (underscore), : (colon), and . (period), and this name
must be unique across all service profiles and service profile templates w ithin the same
organization.

Field Value
New Nam e PodX-Service-Profile-BFS (replace “X” w ith your assigned Pod Number)

Step 38 Click OK to complete the process, and then click OK to close the confirmation dialog box
when it appears.
Step 39 Due to the service profile being renamed you are no longer looking at the properties of the
PodX-new-service-profile. In the navigation panel click PodX-Service-Profile-BFS to return
to the properties of the service profile.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 198
©2016 NterOne Corporation
Activity Verification
You have completed this task when you attain this result:
 You successfully renamed a service profile and observed the renaming process.

Task 5: Verify the Status of the VMware ESXi Server

In this task, you will verify that the VMware ESXi server that was running while using the old service profile
is now running using the new service profile.

Activity Procedure
Complete these steps:
Step 40 In the UCS Manager navigation pane, click the Servers tab.
Step 41 Expand Servers > Service Profiles > root > Sub-Organizations > (Your Organization).
Step 42 Right-click PodX-Service-Profile-BFS (replace “X” with your assigned Pod Number) and then
select KVM Console from the context menu.

Step 43 At this point the VMware ESXi server should be finished booting. If not, wait until the boot
process is complete.
Step 44 After VMware ESXi finishes loading, you should see the server console.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 199
©2016 NterOne Corporation
 Step 45 From your Student Server, launch the VMware vSphere Client application.

Step 46 Enter the IP address for your ESXi server (10.1.R0.1X3, where “R” is your Room Number and
“X” is your Pod Number) and authenticate with the username root and password Nterone179.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 200
©2016 NterOne Corporation
 Step 47 Click the Login button. Click the Ignore button when you receive the Security Warning. In a
few seconds you will see the vSphere Client window.

Step 48 You have successfully completed the lab once you have logged into your ESXi host using the
vSphere client.

Activity Verification
You have completed this task when you attain these results:
 You have successfully logged in to your ESXi host using the VMware vSphere Client.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 201
©2016 NterOne Corporation
Activity 15: Initial Cisco UCS Configuration
(Instructor Demonstration)
Complete this lab activity to practice what you learned in the related module.

Activity Objective
In this activity, you will perform the initial configuration of a Cisco Unified Computing System (Cisco UCS)
clustered environment that is centered around two Cisco UCS 6100 or 6200 Series Fabric Interconnects.
After completing this activity, you will be able to meet these objectives:
 Configure the Cisco UCS Fabric Interconnects with the Setup Wizard
 Configure Fabric Interconnect Server Links
 Configure Fabric Interconnect Uplinks
 Configure an IP address pool for Cisco UCS server management
 Configure the system clock to use Network Time Protocol (NTP)

Note This lab exercise covers the initial configuration of a UCS domain that contains a pair of 6100
series or 6200 series fabric interconnects. Most of the steps that follow are applicable for both
types of fabric interconnects. A few of the steps w ill have different instructions for each type of
fabric interconnects; in these cases there w ill be separate instructions for each type.

Visual Objective
Please refer to the NterOne Resource Guide for this class in order to view the lab diagrams for this lab
exercise.

Command List
The table describes the commands that are used in this activity. The commands are listed in alphabetical
order so that you can easily locate the information that you need. Refer to this list if you need configuration
command assistance during the lab activity.

Com m and Description

connect local-mgmt Connect to the local-management CLI
erase configuration Erase system configuration
show cluster state Show cluster mode state

Task 1: Configure the Cisco UCS Fabric Interconnects with the Setup
Wizard
In this task, you will complete the initial setup configuration of a Cisco UCS Fabric Interconnect and
establish a cluster relationship between two Cisco UCS Fabric Interconnects.

Activity Procedure
Complete the following steps:
Step 1 Log in to the Student Server that is reserved for use by the instructor. This is the Student Server
that will contain the shortcuts to the console ports of the fabric interconnects.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 202
©2016 NterOne Corporation
 Step 2 From the administrator’s Student Server, use PuTTY to open a connection to the console port
of Fabric Interconnect A.

Note Do NOT use SSH to connect to the fabric interconnects; you must use the console ports
because the IP addresses on the fabric interconnects w ill be erased during this process.

Note The examples show n in all tasks of this lab are based on the UCS domain named “UCS2”. Be
sure to use the values that are associated w ith your assigned UCS domain.

Step 3 Log in to Fabric Interconnect A with the username admin and the password Nterone179.

Cisco UCS 6200 Series Fabric Interconnect

UCS2-A login: admin
Password: Nterone179
Cisco Nexus Operating System (NX-OS) Software
TAC support: http://www.cisco.com/tac
Copyright (c) 2009, Cisco Systems, Inc. All rights reserved.
The copyrights to certain works contained in this software are
owned by other third parties and used and distribut ed under
license. Certain components of this software are licensed under
the GNU General Public License (GPL) version 2.0 or the GNU
Lesser General Public License (LGPL) Version 2.1. A copy of each
such license is available at
http://www.opensource.org/licenses/gpl-2.0.php and
http://www.opensource.org/licenses/lgpl -2.1.php

UCS2-A#

Step 4 Connect to the local-mgmt shell.

UCS2-A# connect local-mgmt

Cisco Nexus Operating System (NX-OS) Software
TAC support: http://www.cisco.com/tac
Copyright (c) 2009, Cisco Systems, Inc. All rights reserved.
The copyrights to certain works contained in this software are
owned by other third parties and used and distributed under
license. Certain components of this software are licensed under
the GNU General Public License (GPL) version 2.0 or the GNU
Lesser General Public License (LGPL) Version 2.1. A copy of each
such license is available at
http://www.opensource.org/licenses/gpl-2.0.php and
http://www.opensource.org/licenses/lgpl -2.1.php

UCS2-A(local-mgmt)#

Step 5 Erase the configuration.

UCS2-A(local-mgmt)# erase configuration

All UCS configurations will be erased and system will reboot. Are you sure?
(yes/no):yes
Removing all the configuration. Please wait....

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 203
©2016 NterOne Corporation
 /bin/rm: cannot remove directory `/bootflash/sysdebug//tftpd_logs': Devic e or
resource busy
Configurations are cleaned up. Rebooting....
Shutdown Ports..
writing reset reason 9,

INIT: Sending processes the TERM signal

<… output omitted …>

Step 6 Fabric Interconnect A will immediately erase the configuration and reboot.

Note If the second fabric interconnect is not also erased, the first fabric interconnect w ill attempt to
rejoin the cluster w hen the fabric interconnect boots.

Step 7 From the administrator’s Student Server, use PuTTY to open a connection to the console port
of Fabric Interconnect B.

Step 8 Log in to Fabric Interconnect B with the username admin and the password Nterone179.

Cisco UCS 6200 Series Fabric Interconnect

UCS2-B login: admin
Password: Nterone179
Cisco Nexus Operating System (NX-OS) Software
TAC support: http://www.cisco.com/tac
Copyright (c) 2009, Cisco Systems, Inc. All rights reserved.
The copyrights to certain works contained in this software are
owned by other third parties and used and distributed under
license. Certain components of this software ar e licensed under
the GNU General Public License (GPL) version 2.0 or the GNU
Lesser General Public License (LGPL) Version 2.1. A copy of each
such license is available at
http://www.opensource.org/licenses/gpl-2.0.php and
http://www.opensource.org/licenses/lgpl-2.1.php

UCS2-B#

Step 9 Connect to the local-mgmt shell.

UCS2-B# connect local-mgmt

Cisco Nexus Operating System (NX-OS) Software
TAC support: http://www.cisco.com/tac
Copyright (c) 2009, Cisco Systems, Inc. All rights reserved.
The copyrights to certain works contained in this software are
owned by other third parties and used and distributed under
license. Certain components of this software are licensed under
the GNU General Public License (GPL) version 2.0 or the GNU
Lesser General Public License (LGPL) Version 2.1. A copy of each
such license is available at
http://www.opensource.org/licenses/gpl-2.0.php and
http://www.opensource.org/licenses/lgpl -2.1.php

UCS2-B(local-mgmt)#

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 204
©2016 NterOne Corporation
 Step 10 Erase the configuration.

UCS2-B(local-mgmt)# erase configuration

All UCS configurations will be erased and system will reboot. Are you sure?
(yes/no):yes
Removing all the configuration. Please wait....
/bin/rm: cannot remove directory `/bootflash/sysdebug//tftpd_logs': Device or
resource busy
Configurations are cleaned up. Rebo oting....
Shutdown Ports..
writing reset reason 9,

INIT: Sending processes the TERM signal

<… output omitted …>

Step 11 Return to the PuTTY session to Fabric Interconnect A. After observing the reboot and power-on
self-test (POST) processes, choose the console method of initial configuration.

System is coming up ... Please wait ...

2014 Aug 2 09:52:53 %$ VDC-1 %$ %VDC_MGR-2-VDC_ONLINE: vdc 1 has come online
nohup: appending output to `nohup.out'

---- Basic System Configuration Dialog ----

This setup utility will guide you through the basic configuration of
the system. Only minimal configuration including IP connectivity to
the Fabric interconnect and its clustering mode is performed through these steps.

Type Ctrl-C at any time to abort configuration and reboot system.

To back track or make modifications to already entered values,
complete input till end of section and answer no when prompted
to apply configuration.

Enter the configuration method. (console/gui) ? console

Step 12 Specify that you will be setting up the system manually (as opposed to restoring the system up
from a backup) and set the admin password to Nterone179 (do not enforce the strong password
check).

Note The default answ er for each question (w hen applicable) is in brackets and w ill be used w hen you
enter a carriage return w ithout any input.

Enter the setup mode; setup newly or restore from backup. (setup/restore) ? setup

You have chosen to setup a new Fabric interconnect. Continue? (y/n): y

Enforce strong password? (y/n) [y]: y

Enter the password for "admin": Nterone179

Confirm the password for "admin": Nterone179

Step 13 Enter “y” to indicate that you will be configuring a cluster.

Is this Fabric interconnect part of a cluster(select 'no' for standalone) ?

(yes/no) [n]: y

Step 14 Enter “A” to indicate that this will be Fabric Interconnect A within the UCS cluster.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 205
©2016 NterOne Corporation
 Enter the switch fabric (A/B) []: A

Step 15 Enter the name of the UCS cluster.

Enter the system name: UCS2

Note The system name applies to both nodes. The fabric designator (A or B) is appended to form the
hostname.

Step 16 Set the management IP configuration options. Each fabric interconnect has a unique IP address
as well as a shared cluster address. Enter the values in the following table based on the UCS
domain that you are using.

UCS Physical Sw itch Mgm t0 Physical Sw itch Mgm t0 IPv4 Address of the Cluster IPv4
Dom ain IPv4 Address IPv4 Netm ask Default Gatew ay Address
UCS1 10.1.7.17 255.255.255.0 10.1.7.1 10.1.7.16
UCS2 10.1.7.33 255.255.255.0 10.1.7.1 10.1.7.32
UCS3 10.1.7.49 255.255.255.0 10.1.7.1 10.1.7.48
UCS4 10.1.7.65 255.255.255.0 10.1.7.1 10.1.7.64

Physical Switch Mgmt0 IPv4 address : 10.1.7.33

Physical Switch Mgmt0 IPv4 netmask : 255.255.255.0

IPv4 address of the default gateway : 10.1.7.1

Cluster IPv4 address : 10.1.7.32

Configure the DNS Server IPv4 address? (yes/no) [n]: n

Configure the default domain name? (yes/no) [n]: n

Join centralized management environment (UCS Central)? (yes/no) [n]: n

Step 17 Confirm and apply the configuration information. If you made any errors, enter “no” and start
the configuration over.

Following configurations will be applied:

Switch Fabric=A
System Name=UCS
Enforced Strong Password=yes
Physical Switch Mgmt0 IP Address=10.1.7.33
Physical Switch Mgmt0 IP Netmask=255.255.255.0
Default Gateway=10.1.7.1

Cluster Enabled=yes
Cluster IP Address=10.1.7.32
NOTE: Cluster IP will be configured only after both Fabric Interconnects are
initialized

Apply and save the configuration (select 'no' if you want to re-enter)? (yes/no):
yes
Applying configuration. Please wait.

Configuration file - Ok

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 206
©2016 NterOne Corporation
 Step 18 It will take several seconds for the initial configuration to be applied to Fabric Interconnect A.
When the login prompt appears log in to Fabric Interconnect A and view the cluster status using
the show cluster state command.

Cisco UCS 6200 Series Fabric Interconnect

UCS2-A login: admin
Password: Nterone179
Cisco Nexus Operating System (NX-OS) Software
TAC support: http://www.cisco.com/tac
Copyright (c) 2009, Cisco Systems, Inc. All rights reserved.
The copyrights to certain works contained in this software are
owned by other third parties and used and distributed under
license. Certain components of this software are licensed under
the GNU General Public License (GPL) version 2.0 or the GNU
Lesser General Public License (LGPL) Version 2.1. A copy of each
such license is available at
http://www.opensource.org/licenses/gpl-2.0.php and
http://www.opensource.org/licenses/lgpl -2.1.php

UCS2-A# show cluster state

Cluster Id: 0xc5d2bd8e1a2a11e4-0x8f41002a6a87f204

A: UP, ELECTION IN PROGRESS (Management services: UP)

B: UNRESPONSIVE, INAPPLICABLE, (Management services: UNRESPONSIVE)

HA NOT READY
Peer Fabric Interconnect is down
No device connected to this Fabric Interconnect

Note Fabric Interconnect B is unresponsive; this is normal due to the fact that it has not been
configured yet.

Step 19 Return to the PuTTY session to Fabric Interconnect B to complete the initial configuration.
After it completes the boot process (which was occurring while you were configuring Fabric
Interconnect A) it should detect the presence of the cluster. Enter “y” to indicate that you want
to add this fabric interconnect to the cluster.

---- Basic System Configuration Dialog ----

This setup utility will guide you through the basic configuration of
the system. Only minimal configuration including IP connectivity to
the Fabric interconnect and its clustering mode is performed through these steps.

Type Ctrl-C at any time to abort configuration and reboot system.

To back track or make modifications to already entered values,
complete input till end of section and answer no when prompted
to apply configuration.

Enter the configuration method. (console/gui) ? console

Installer has detected the presence of a peer Fabric interconnect. This Fabric
interconnect will be added to the cluster. Continue (y/n) ? y

Step 20 Enter the admin password that you configured on Fabric Interconnect A.

Enter the admin password of the peer Fabric interconnect: Nterone179

Step 21 Next, configure the management IP address for Fabric Interconnect B. Enter the value in the
following table based on the UCS domain that you are using.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 207
©2016 NterOne Corporation
 UCS Dom ain Physical Sw itch Mgm t0 IPv4 Address
UCS1 10.1.7.18
UCS2 10.1.7.34
UCS3 10.1.7.50
UCS4 10.1.7.66

Connecting to peer Fabric interconnect... done

Retrieving config from peer Fabric interconnect... done

Peer Fabric interconnect Mgmt0 IP Address: 10.1.7.33

Peer Fabric interconnect Mgmt0 IP Netmask: 255.255.255.0
Cluster IP address : 10.1.7.32

Physical Switch Mgmt0 IPv4 address : 10.1.7.34

Step 22 Confirm and apply the configuration information. If you made any errors, enter “no” and start
the configuration over.

Apply and save the configuration (select 'no' if you want to re -enter)? (yes/no):
yes
Applying configuration. Please wait.

Note The fabric designator B is automatically assigned.

Step 23 Log in to Fabric Interconnect B and view the cluster status using the show cluster state
command.

Cisco UCS 6200 Series Fabric Interconnect

UCS2-B login: admin
Password: Nterone179
Cisco Nexus Operating System (NX-OS) Software
TAC support: http://www.cisco.com/tac
Copyright (c) 2009, Cisco Systems, Inc. All rights reserved.
The copyrights to certain works contained in this software are
owned by other third parties and used and distributed under
license. Certain components of this software ar e licensed under
the GNU General Public License (GPL) version 2.0 or the GNU
Lesser General Public License (LGPL) Version 2.1. A copy of each
such license is available at
http://www.opensource.org/licenses/gpl-2.0.php and
http://www.opensource.org/licenses/lgpl-2.1.php

UCS2-B# show cluster state

Cluster Id: 0xc5d2bd8e1a2a11e4-0x8f41002a6a87f204

B: UP, SUBORDINATE
A: UP, PRIMARY

HA NOT READY
No device connected to this Fabric Interconnect

Note Fabric Interconnects A and B are now in a primary and subordinate cluster state. How ever, high
availability is not available. High availability is not used until UCS servers are connected to the
fabric interconnects.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 208
©2016 NterOne Corporation
 Step 24 Use a browser to log in to the Cisco UCS Manager GUI using the cluster IP address. Click
Launch UCS Manager to start the Cisco UCS Manager application, and log in.

Note If a security panel opens, choose Accept or Proceed. If a File Dow nload panel opens for the
Cisco UCS Manager.jnlp file, click Save and replace the previous file on the desktop. Af ter the
dow nload is complete, click Open and Cisco UCS Manager launches.

Activity Verification
You have completed this task when you attain this result:
 You have performed the initial configuration of both of the Cisco UCS Fabric Interconnects. When
you complete this activity, your network topology should be similar to the following.

Note At this time, no servers are show n under the chassis.

Task 2: Configure the Fabric Interconnect Server Links

In this task, you will continue the initial configuration of the fabric interconnects and establish the server
links to the Cisco UCS 5108 Blade Server Chassis.

Activity Procedure
Complete the following steps:
Step 25 Note that both fabric interconnects are visible in the Equipment tab, but no chassis is yet
available, because all Ethernet ports are disabled by default.
Step 26 Before the chassis is manageable and the cluster becomes fully operational, each fabric
interconnect must have at least one active link to the chassis. There are several methods to
configure the links to the chassis, also known as server ports. Choose either fabric interconnect
in the navigation panel and then click Internal Fabric Manager in the Actions section.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 209
©2016 NterOne Corporation
 Step 27 The Internal Fabric Manager window will appear. Expand Unconfigured Ethernet Ports >
Fabric Interconnect > Fabric Interconnects A > Fixed Module. Choose Port 1 through Port 4
(use the Ctrl or Shift keys to select multiple ports). Click Make Server Port. Click Yes in the
confirmation window.

Step 28 Using the same Internal Fabric Manager window, repeat the same process to configure Port
1 through Port 4 on Fabric Interconnect B.
Step 29 Click OK to close the Internal Fabric Manager. Review the contents of the Equipment tab.
Note that a chassis is now visible after you expand the Equipment > Chassis branch.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 210
©2016 NterOne Corporation
 Step 30 Click the Equipment object at the top of the hierarchy and then click the Policies tab in the
content panel. Under the Global Policies tab, change the Chassis/FEX Discovery Policy to “4
Link” from the drop-down menu. Click OK to commit the changes.

Step 31 Click Chassis 1 in the Equipment panel, and then click Acknowledge Chassis in the Actions
section. This action makes sure that the uplinks between the fabric interconnects and the chassis
are properly enabled. Click Yes to confirm the action, and then click OK to dismiss the
confirmation panel.

Step 32 Return to the PuTTY session to Fabric Interconnect A and check the cluster status again. It may
take up to 60 seconds before the CLI reports that the cluster is fully operational.

UCS2-A# show cluster extended-state

Cluster Id: 0xc5d2bd8e1a2a11e4-0x8f41002a6a87f204

Start time: Sat Aug 2 10:03:11 2014

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 211
©2016 NterOne Corporation
 Last election time: Sat Aug 2 10:06:22 2014

A: UP, PRIMARY
B: UP, SUBORDINATE

A: memb state UP, lead state PRIMARY, mgmt services state: UP

B: memb state UP, lead state SUBORDINATE, mgmt services state: UP
heartbeat state PRIMARY_OK

INTERNAL NETWORK INTERFACES:

eth1, UP
eth2, UP

HA READY
Detailed state of the device selected for HA storage:
Chassis 1, serial: FOX1743GC85, state: active

Note High availability is now available.

Step 33 In addition to the CLI check in the last step, you can confirm high availability from the GUI.
Click either fabric interconnect from the Equipment tab in the navigation panel, and then click
the General tab in the content panel. Expand the High Availability Details section under
Properties in order to see the details of the state of high availability on the fabric interconnect.

Activity Verification
You have completed this task when you attain this result:
 You have successfully configured the links between both fabric interconnects and the Cisco UCS
5108 chassis.

Task 3: Configure the Fabric Interconnect Uplinks

In this task, you will continue the initial configuration of the fabric interconnects and estab lish the uplinks to
the Cisco Nexus 5500s.

Activity Procedure
Complete the following steps:
Step 34 Return to the Cisco UCS Manager GUI. To configure the Ethernet uplink ports, choose Fabric
Interconnect A, and then click LAN Uplinks Manager in the Actions section.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 212
©2016 NterOne Corporation
 Step 35 Expand Unconfigured Ethernet Ports > Fabric Interconnects > Fabric Interconnect A >
Fixed Module. Choose Port 11 through Port 14 on Fabric Interconnect A, and then click
Make Uplink (you may need to scroll down in order to see the button). Click Yes to confirm
the ports, and then click OK to dismiss the confirmation panel.

Step 36 Repeat this process for Port 11 through Port 14 on Fabric Interconnect B.
Step 37 When you have completed the previous steps the Port Channels and Uplinks panel of the
LAN Uplinks Manager should look similar to the following image.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 213
©2016 NterOne Corporation
 Step 38 Click OK to close the LAN Uplinks Manager.
Step 39 Navigate to Equipment > Chassis > Chassis 1 and then click the Hybrid Display tab in the
content panel to view your network topology. When you complete this activity, your network
topology should be similar to the following image.

Activity Verification
You have completed this task when you attain these results:
 You have performed the uplink configuration of both of the Cisco UCS Fabric Interconnects.

Task 4: Configure IP Addresses for UCS Server Management

In this task, you will configure the IP address pool “ext-mgmt” to provide addresses to the Cisco UCS
servers so that they can be managed by the UCS Manager.

Activity Procedure
Complete the following steps:
Step 40 In the UCS Manager navigation pane, click the LAN tab.
Step 41 Expand LAN > Pools > root > IP Pools > IP Pool ext-mgmt.
Step 42 Right-click IP Pool ext-mgmt and then select Create Block of IP Address from the context
menu.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 214
©2016 NterOne Corporation
 Step 43 The Create a Block of IP Addresses wizard will appear. Enter the values in the following table
based on the UCS Domain that you are using.

Pod Num ber From Size Subnet Mask Default Gatew ay

UCS1 10.1.7.24 8 255.255.255.0 10.1.7.1
UCS2 10.1.7.40 8 255.255.255.0 10.1.7.1
UCS3 10.1.7.56 8 255.255.255.0 10.1.7.1
UCS4 10.1.7.72 8 255.255.255.0 10.1.7.1

Step 44 Click OK to complete the wizard, and then click OK to close the confirmation dialog box when
it appears.
Step 45 In the content panel click the IP Addresses tab to confirm that the IP addresses have been
assigned to the blade servers.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 215
©2016 NterOne Corporation
Activity Verification
You have completed this task when you attain these results:
 You have configured an IP address pool for server management.

Task 5: Configure Time Synchronization

In this task, you will configure the UCS Manager to use Network Time Protocol (NTP) to synchronize the
system clock with an external time server.

Activity Procedure
Complete the following steps:
Step 46 In the UCS Manager navigation pane, click the Admin tab.
Step 47 Expand All > Time Zone Management.
Step 48 In the content pane click Add NTP Server.

Step 49 The Add NTP Server window will appear. Enter the IP address of 10.0.99.100.

Step 50 Click OK to complete the wizard, and then click OK to close the confirmation dialog box when
it appears.
Step 51 In the Time Zone drop-down list, select the time zone named America/New York (Eastern
Time).

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 216
©2016 NterOne Corporation
 Step 52 Click Save Changes, and then click OK to close the confirmation dialog box when it appears.
Step 53 The system clock can be seen in the bottom right-hand corner of the UCS Manager window.
The time displayed should match the correct time; it may take several seconds for the UCS
Manager to synchronize the clock.

Activity Verification
You have completed this task when you attain these results:
 You have configured the UCS Manager to use Network Time Protocol (NTP) to synchronize the
system clock with an external time source.

Introducing Cisco Data Center Technologies (DCICT) Lab Guide v1.0 rev C Page 217
©2016 NterOne Corporation