Beruflich Dokumente
Kultur Dokumente
Nexus Platform:
The Nexus platform provides several advantages
that include the fact that it was built to be more
modular than the Catalyst platform.
This mean that processes such as OSPF, EIGRP,
hsrp, lacp can be started and stopped and
upgraded without affecting the kernel. It also
provides a path to perform inline software
service upgrades (ISSU) which allow upgrading a
switchs kernel without sacrificing downtime on
the network.
Virtual Port Channel vPC
feature lacp
feature vpc
Virtual Port Channel
vPC
Step -2:
Setup the management interfaces on each
Nexus 5K switch.
These will be the vPC keep alive link. We
can also use the cross over cable to connect
both the switches & it can be used as the
keep alive link as shown in the diagram.
The switches require L3 reachability
between them to have the keep alive
messages exchanged.
Virtual Port Channel
vPC
Step -3:
Next step is to setup a vPC Domain with the
management addresses of each management interface.
On Switch#1:
vpc domain 10
peer-keepalive destination 192.168.100.6 source
192.168.100.5 vrf management
On Switch#2:
vpc domain 10
peer-keepalive destination 192.168.100.5 source
192.168.100.6 vrf management
Virtual Port Channel
vPC
Step -4:
Next step is to configure the peer links that will carry
the data.
These peer links should at least have adequate
bandwidth & also offer redundancy.
we are using 2 * 10 Gbps SFP interfaces which offer
aggregated bandwidth of 20 Gbps.
We are using interface 1/1 & 1/2 on both the switches.
The port channel no used is 57.
Virtual Port Channel
vPC
On Switch#1
interface port-channel57
description ## vPc to Switch#2 ##
switchport mode trunk
spanning-tree port type network
interface Ethernet1/1
description ## To Switch#2 E1/1 ###
switchport mode trunk
channel-group 57 mode active
interface Ethernet1/2
description ## To Switch#2 E1/2 ###
switchport mode trunk
channel-group 57 mode active
Virtual Port Channel
vPC
On Switch#2
interface port-channel57
description ## vPc to Switch#1 ##
switchport mode trunk
spanning-tree port type network
interface Ethernet1/1
description ## To Switch#1 E1/1 ###
switchport mode trunk
channel-group 57 mode active
interface Ethernet1/2
description ## To Switch#1 E1/2 ###
switchport mode trunk
channel-group 57 mode active
Virtual Port Channel
vPC
The Port channel 57 needs to be defined as peer link using the below command.
interface port-channel57
vpc peer-link
Perform a show vpc brief to see the status of the port channel:
Switch#1# show vpc brief
Legend:
(*) local vPC is down, forwarding via vPC peer-link
vPC domain id : 10
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
vPC Peer-link status
id Port Status Active vlans
-
1 Po57 up 1
Virtual Port Channel
vPC
vPCPortSetup
Next step is to setup a port channel in Switch#3.
The Switch#3 we are using in this example is
3750 which uses 2 10Gbps ports.
The ports used are T1/0/1 & T1/0/2.
First thing is the configuration on Switch C. For
this configuration, we will be using a 3750 and
connecting two Ten Gigabit interfaces in a port
channel to switches A and B. Ports T1/0/1 and
T1/0/2 on the 3750 are connected to port
Ethernet 1/10 on both Switch#1 and Switch#2.
Virtual Port Channel
vPC
On Switch#3
interface Port-channel100
description ## To Switch#1 & Switch#2 ##
switchport trunk encapsulation dot1q
switchport mode trunk
interface TenGigabitEthernet1/0/1
description ## To Switch#1 Ethernet 1/10 ##
switchport trunk encapsulation dot1q
switchport mode trunk
channel-group 100 mode active
interface TenGigabitEthernet1/0/2
description ## To Switch#2 Ethernet 1/10 ##
switchport trunk encapsulation dot1q
switchport mode trunk
channel-group 100 mode active
Then on Switch#1 & Switch#2 configure a port channel in a vPC. The configuration is the same
on both switches & with this configuration, allowed only VLAN 1, 10 & 20 in the trunk port.
Virtual Port Channel
vPC
interface port-channel101
description ## To Switch#3 ##
switchport mode trunk
vpc 101
switchport trunk allowed vlan 1,10,20
spanning-tree port type edge trunk
spanning-tree bpduguard enable
interface Ethernet1/10
description ## To Switch#3 ##
switchport mode trunk
switchport trunk allowed vlan 1,10,20
channel-group 101 mode active
Once the connectivity is setup the port channel comes up & the status of the vPc
can be confirmed.
After this we have 20Gbps port channel connectivity to Switch#3.
Cisco OTV Overlay Transport Virtualization
4. What is the
specs/scalability/capacity of Cisco
OTV technology?
Cisco OTV is scalable up to 6 sites with
2 devices at each location.
Max 256 VLAN can be extended.
Distance Limitation Distance/Latency
is not a constraint for OTV.
Cisco OTV Overlay Transport
Virtualization
5. What are the
commands/configurations for
deploying Cisco OTV?
To enable OTV it requires few
commands on each of the Nexus
7000 series switches.
The below commands are required to
enable the OTV on Cisco Nexus 7000
series switches. The below example
is for extending the VLANs from 5
Cisco OTV Overlay Transport
Virtualization
! Configure the physical interface that OTV uses to reach the DCI transport
infrastructure
interface ethernet 2/1
ip address 192.0.2.1/24
ip igmp version 3
no shutdown
!Configure the VLAN that will be extended on the overlay network and the site-vlan
vlan 2,5-10
! Configure OTV including the VLANs that will be extended.
feature otv
otv site-vlan 2
otv site-identifier 256
interface Overlay1
otv control-group 239.1.1.1
otv data-group 232.1.1.0/28
otv join-interface ethernet 2/1
!Extend the configured VLAN
otv extend-vlan 5-10
no shutdown
Cisco OTV Overlay Transport
Virtualization
6. Any other benefits of Cisco
OTV
OTV is designed for the data center
interconnection & for the availability
of the services across data center.
It extends the same IP segment Data
center across multiple locations.