Nexus 5000/Nexus 2000 Lab Guide Overview This lab is designed to help attendees understand how to deploy Nexus 5000 and Nexus 2000 in the datacenter. It covers the configuration and management perspective for Nexus 5000 and Nexus 2000. Attendees will learn how to design and deploy Lab List This guide includes these activities: Lab 1: Basic configuration of N5k Lab 2: Deploy N5k/N2k using EtherChannel Lab 3: Deploy N5k/N2k using static pinning Lab 4: Configuration of FCoE Nexus 5000 and Nexus 2000 Overview The Cisco Nexus™ 5000 Series Switches comprise a family of line-rate, low-latency, lossless 10 Gigabit Ethernet, Cisco ® Data Center Ethernet, and Fibre Channel over Ethernet (FCoE) switches for data center applications. The switch family is highly serviceable, with redundant, hot-pluggable power supplies and fan modules. Its software is based on data center-class Cisco NX-OS Software for high reliability and ease of management.
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Nexus 5000/Nexus 2000 Lab Guide
Overview This lab is designed to help attendees understand how to deploy Nexus 5000 and Nexus 2000 in the datacenter. It covers the configuration and management perspective for Nexus 5000 and Nexus 2000. Attendees will learn how to design and deploy
Lab List This guide includes these activities:
Lab 1: Basic configuration of N5k
Lab 2: Deploy N5k/N2k using EtherChannel
Lab 3: Deploy N5k/N2k using static pinning
Lab 4: Configuration of FCoE
Nexus 5000 and Nexus 2000 Overview
The Cisco Nexus™ 5000 Series Switches comprise a family of line-rate, low-latency, lossless 10 Gigabit Ethernet, Cisco® Data Center Ethernet, and Fibre Channel over Ethernet (FCoE) switches for data center applications. The switch family is highly serviceable, with redundant, hot-pluggable power supplies and fan modules. Its software is based on data center-class Cisco NX-OS Software for high reliability and ease of management.
The Cisco Nexus 2148T provides 48 Gigabit Ethernet server ports and 4 10 Gigabit Ethernet uplink ports in a compact one rack-unit (1RU) form factor. The Cisco Nexus 2000 Series Fabric Extender integrates with the parent switch, allowing "zero-touch" provisioning as well automatic configuration and software upgrade when a rack is connected to the parent switch. This integration allows large numbers of servers to be supported with the same feature set of the parent Cisco Nexus 5000 Series switch, along with specific configuration parameters including security and quality of service (QoS). The FEX does not run Spanning Tree Protocol even when multiple links are connected to the parent switch, thus giving customers loop-free, active-active connectivity between the two.
Telnet to 128.107.65.194, sign on with a password of labops
Issue the show host command:
Nuova_TermServer>show host
[snip]
Host Port Flags Age Type Address(es)
tm1 2033 (perm, OK) 21 IP 1.1.1.1
tm2 2034 (perm, OK) 21 IP 1.1.1.1
tm3 2035 (perm, OK) 21 IP 1.1.1.1
tm4 2036 (perm, OK) 21 IP 1.1.1.1
tm5 2037 (perm, OK) 21 IP 1.1.1.1
tm6 2038 (perm, OK) 21 IP 1.1.1.1
tm7 2039 (perm, OK) 21 IP 1.1.1.1
tm9 2044 (perm, OK) 21 IP 1.1.1.1
tm8 2040 (perm, OK) 21 IP 1.1.1.1
tm6500 2042 (perm, OK) 21 IP 1.1.1.1
mds 2047 (perm, OK) 21 IP 1.1.1.1
Console in to the 5020 for your pod, for example, POD 1 would be TM1
Nuova_TermServer>tm1
Translating "tm1"
Trying tm1 (128.107.65.194, 2033)...
% Connection refused by remote host
Deleting login session
If you see the above error message you will need to get enable access to the terminal server and clear the line as shown below. The enable password is nuovanuova. If you do not see the error message above you can proceed to step 2
Nuova_TermServer>ena
Password:
Nuova_TermServer#clear line 33
[confirm] <- Hit enter
[OK]
Nuova_TermServer#tm1
Translating "tm1"
Trying tm1 (128.107.65.194, 2033)... Open Hit enter here
In this exercise you will configure basic connectivity to the switch, 802.1q trunking, LACP Port Channels, Fibre Channel Port Channels, and FCoE connectivity.
Note: The exercises in the lab were performed on POD 1. Please use the correct switches, VSANs, VLANs, IP addresses, and host associated with your assigned POD.
Lab Procedure
Continuing from the N5K/N2K lab, access the Nexus 5000 switch for your pod via the terminal server.
Step 1. In this step you will enable FCoE feature for the Nexus 5000 switch.
First turn on the FCoE feature. This will require a reboot of the switch to go into effect.
TM1# configure terminal
TM1(config)# feature fcoe
2008 Aug 13 22:56:01 switch %$ VDC-1 %$ %PFMA-2-FC_LICENSE_DESIRED: FCoE/FC feature will be enabled after the configuration is saved followed by a reboot
TM1(config)# copy running-config startup-config
[########################################] 100%
Packaging and storing to flash: \
TM1(config)# reload
Step 2. Creating a VSAN for the Fibre Channel Database
Once the switch comes back up, login into the switch and create the vsan needed for your POD. Please note that the convention used would be VSAN 20X, where X is your Pod #. Example would be for Pod1, would need to create VSAN 201, Pod 2 would be VSAN 202, etc.
TM1#configure terminal
TM1(config)# vsan database
TM1(config-vsan-db)# vsan 20X Again POD specific
TM1(config-vsan-db)# end
Step 3. Creating a SAN Port-Channel
TM1(config)# interface san-port-channel 10X Again POD specific
TM1(config-if)# interface fc2/3-4
TM1(config-if)# channel-group 10X force Again POD specific
fc2/3 fc2/4 added to san-port-channel 10X and disabled
please do the same operation on the switch at the other end of the channel, then do "no shutdown" at both ends to bring them up
Please note that the MDS9134 has already been initially configured to be in switching mode and the Port-Channels has been created on it as well. So the students nor instructor "DO NOT" need to do anything on the MDS switch.
TM1(config-if)# no shut
TM1(config)# interface san-port-channel 10X Again POD specific
Step 4. Configuring a VLAN to be FCoE capable. This also does the VLAN to VSAN mapping.
Note: The VLAN number will be following the convention of VLAN 20X, where X is your Pod #. Example would be VLAN 201 for Pod 1, VLAN 202 for Pod 2, etc.
TM1# configure terminal
TM1(config)# vlan 20X Again POD specific
TM1(config-vlan)# fcoe vsan 20X Again POD specific
TM1(config-vlan)# show vlan fcoe
VLAN VSAN Status
-------- -------- --------
201 201 Operational
Step 5. Create the virtual Fibre Channel interface, and move it to the VSAN assigned to your pod.
TM1(config-vlan)# interface vfc5 The "vfc" number is not relevant and can be any number the student chooses. But for consistency, please use #5 for all pods. All student pods should have interface "vfc5" when this is completed.
TM1(config-if)# bind interface Ethernet1/5
TM1(config-if)# no shut
Add Virtual Fibre Channel (vfc5) Interface to the VSAN database for your Pod.
TM1 (config-if)#vsan database
TM1 (config-vsan-db)#vsan 20X interface vfc5 Again POD specific
Step 6. Allow the FCoE VLAN to traverse interface ethernet 1/5 TM1(config-vsan-db)# interface ethernet 1/5
TM1(config-if)# switchport mode trunk
TM1(config-if)# switchport trunk allowed vlan 10X, 20X Again POD specific
TM1(config-if)# switchport trunk native vlan 10X Again POD specific
Step 7. Verify vfc interface is up Note: If the student does a "show interface vfc5", the vFC interface will be down awaiting the FCoE VLAN assignment, please be patient and the CNA port will come up.
vfc5 is down (STP not forwarding in FCoE Mapped VLAN)
Verify your CNA host is logged into the fabric and registered with the name server