Escolar Documentos
Profissional Documentos
Cultura Documentos
William Zambrano
8 years of professional IT experience.
Worked/consulted at various companies, as well as teaching.
CompTIAs, MCSE 2003, CCNA, CCNP, CCNA: Voice, Security, Datacenter,
and CCSI
Organizer at Cisco Networkers http://www.meetup.com/CiscoNetworkers/
Meetup Website http://nycnetworkers.com
Guest Speakers
Keith Barker & Anthony Sequeria
on CCIEv5
willzambrano@gmail.com
William.zambrano10577
vPCs cont
F cards (l2) for peer keepalive to sync
M cards for the l3 peer link for control plane
for the UDP ping between each switch and
need a M132XP-12 card to do this (VDC) 10
gig link
Best to use two modules for the PL for
redundancy
Want to have the PK in its own VRF
One vPC per VDC
vPC Cmds
#sh vpc brief
#sh vpc consistency-parameters global
#sh vpc consistency-parameters vpc 71 or
choose a specific the exact vPC #
Verification Cmds
#sh vpc
#sh vpc brief
#sh vpc consistency-parameters global
#sh port-channel capacity
#sh vpc statistics
#sh vpc role
#sh vpc peer-keepalive
Cavets of vPC
The Peer Link needs to be a 10gig link
A vPC is a per-VDC function and cannot be
spanned across multiple VDCs
You can only have two switches in a vPC
domain.
Cisco FabricPath
Ciscos proprietary version of TRILL based off
IS-IS.
Use ALL links in your network to provide full
bandwidth use and lower oversubscription.
Help eliminates suboptimal paths
Its layer 2 routing with some layer 3
functionality
Frames get forwarded along the shortest path
available.
FabricPath cont
From our CE devices coming into the FP
domain, FP will encap the CE l2 frame into a
FP l2 frame.
AKA as MAC and MAC routing because FP
looks at the source and dest frame headers to
decide the best way to route it via the SPF.
FabricPath Terms
Classical Ethernet (CE)
Leaf Switch: the border switch that connects to
a CE domain
Spine Switch: Core switch of the FP domain all
its ports are FabricPath ports (no CE)
FabricPath Core Ports: ports that connect to
another FP device (config-if)#switchport mode
fabricpath
CE Edge Ports: ports on a Leaf Switch connecting
to the classical Ethernet domain (configif)#switchport mode fabricpath
Configuring FabricPath
Enable the feature-set via #install feature-set
fabricpath and then #feature-set fabricpath
Configure the VLANs to go over the FP to change the
way they learn MACs (Conversational MAC Learning)
from CE to FP (config)#vlan 10 (config-vlan)#mode
fabricpath
Configure FP Core Ports via (config-if)#switchport
mode fabricpath
Optionally you can change a ports default mode to FP
via (config-if)#system default switchport fabricpath
Optionally, you can changeup the switch ID via (configvpc-domain)#fabricpath switch-id ?
Verification Cmds
#sh feature-set
#sh int brief
#sh spanning-tree summary
#sh fabricpath is-is database
#sh fabricpath is-is adj
OTV cont
We could use Dark Fiber, a P2P link, MPLS,
OTV uses GRE tunnels but it has some builtin features to stop STP, ARPs, broadcast
storms, etc. Keeps each DC as a island.
Generally you want to keep the control plane
traffic off OTV, but keep on it the data plane
traffic.
Things like having a VLAN in two sites but they
will be in 2 STP domains. Thus, we can have
VLAN overlays without a complications.
OTV cont
OTV does not support fragmentation, need to enable
jumbo frame on the Join int. mtu 9216
OTV can run over anything, OC, MPLS, P2P, etc as long
we are able to ping the two points.
You do not need to run multicast for OTV, but for better
use of bandwidth you can use multicast instead of
unicast (adj servers).
Layer 2 flooding isnt done over the OTV network, but
done by the OTV control plane.
Multihoming can be done as well with OTV (AED)
Generally deployed in its own VDC (OTV on stick) OTV
cant work with a VDC that has SVIs.
OTV Terms
Edge device: this device is responsible for all OTV
functionality, and sits at the core/aggregation
layer. Encaps l2 traffic into GRE, crosses the
network and pops out unencap as a l2 frame.
Authoritative Edge Device (AED): multiple edge
devices for redundancy/load balancing.
Internal int: the int on the edge device that face
the datacenter and carry at least one VLAN that
are extended through OTV. These are layer 2
devices.
Configuring OTV
Ensure we have l3 connectivity btwn the two sites
Enable the OTV feature (config)#feature otv
Create an Overlay VLAN (global) to be fwd over
the OTV tunnel and create a Site VLAN used to
sync the AEDs (local).
(config)#vlan 10
(config-vlan)#name OVERLAY_VLAN
(config)#vlan 20
(config-vlan)#name SITE_VLAN
Configuring OTV 2
Define the Site VLAN and Overlay VLAN. If you
have two AEDs at the DC you want this
number to be the same.
(config)#otv site-vlan 20
(config)#otv site-identifier 0.0.1
Define the overlay interface (local) and define
some OTV settings under it
(config)#int overlay 1
Configuring OTV 3
Define the Control Group, Data Group, and
Extended VLAN (what VLANs to bridge over)
(config-if-overlay)#otv control-group 239.1.1.1
(config-if-overlay)#otv data-group 232.1.1.0/28
(config-if-overlay)#otv extend-vlan 10
(config-if-overlay)#otv join-inter e1/1 note here
it will say to enable IGMPv3 on this int if you
haven't already
Verification Cmds
VDCs
Completely separate not like a VRF table
To reach must physically connect cables
All SW upgrades and mgmt of rsources must be
done from the defalt VDC
4 VDCs can be made check datasheets per
Nexus model
Ports get grouped to a VDC based on its ASIC
depending on what line card (N7K-M132XP-12)
Great for PoC, UAT/Dev env
VDCs cont
You can only do certain tasks like resource
allocation or deleting/creating VDCs from the
default VDC. Default VDC cannot be deleted
You can only map groups of ports into a VDC
based off the line cards ASIC.
Each VDC gets its own mgmt0 IP addr and
they do not overlap
VDCs cont
#sh run
Here we can see
VLAN limit
HW resource limit
Ports in this VDC
VDC Cmds
#Switchto
#Switchback
#copy run start vdc-all
#sh vdc
#sh run | begin vdc
#sh vdc membership
#sh vdc current-vdc
#sh vdc shared membership
#sh vdc resource detail
#sh vdc feature-set
Books
NX-OS and Cisco Nexus Switching: Next-Generation Data
Center Architectures 2nd Edition
Data Center Virtualization Fundamentals:
Understanding Techniques and Designs for Highly
Efficient Data Centers with Cisco Nexus, UCS, MDS, and
Beyond
Books #2
Cisco Unified Computing System (UCS) (Data
Center): A Complete Reference Guide to the
Cisco Data Center Virtualization Server
Architecture
Storage Networking Fundamentals: An
Introduction to Storage Devices, Subsystems,
Applications, Management, and File Systems
Network Warrior 2nd Edition Nexus Chapter
Cisco Titanium
https://learningnetwork.cisco.com/thread/49
328
Similar to what we are used to with GNS3, but
for the NX-OS instead of the IOS.
Officially not supported
Classroom
Cisco Official CCNA Datacenter Course
Introducing Cisco Data Center Networking
(DCICN)
Introducing Cisco Data Center Technologies
(DCICT)
Todd Lammles CCNA Datacenter Course
http://www.lammle.com/course/ccna-datacenter-bootcamp/
Get a Mentor!
Meetup groups
Co-workers avoid burning bridges, get on
LinkedIn
Network, network, network human physical
network
Get your name out there
Q&A
Visit us a our Meetup Page
http://www.meetup.com/Cisco-Networkers/
Visit our webpage at
http://www.nycnetworkers.com
http://www.youtube.com/cisconetworkers1
or visit our YouTube page for all uploaded videos
Or contact me directly at willzambrano@gmail.com or Skype name
william.zambrano10577