Showing posts with label vpc. Show all posts
Showing posts with label vpc. Show all posts

Friday, 8 August 2014

why vPC+ in fabric path

vPC and vPC+ at edge, understanding the differences


vPC is a technology that is around for a long time now and is a very intelligent (MLAG) solution for the nexus product line.
With Cisco FabricPath's introduction vPC+ was also introduced.
lets see how different vPC+ is and how vPC+ overcomes some problems that vPC has in a fabricpath environment.

Below is a diagram where standard vPC is configured in a fabricpath environment.


Server A with MAC (aaa.aaa.aaa) is connected to nexus 5k-1 and 5k-2 in a vPC.
so lets take it step wise:
  1. Server A sends traffic to Server B
  2. Server A can use either of the links in vPC depending on the hashing
  3. lets say Server A takes outgoing path via 5k-1 (using switch ID of 5k-1)
  4. 5k-1 sends traffic to 7k-4 via fabricpath
  5. 7k-4 sends traffic to 5k-3 and finally Server B receives the frame as classical ethernet
now the problem arises in the reverse path
5k-3 has to send traffic back to Server A , so MAC(aaa.aaa.aaa) is behind which Switch ID. 5k-1 or 5k-2 ??? so it send back to 5k-1 and we do not achieve multipathing

 This problem is resolved by using vPC+

Below is an example of vPC+ with Fabric path domain



So lets take it step wise:
  1. Server A sends traffic to Server B with source MAC(aaa.aaa.aaa)
  2. Server A uses either links in vPC+ depending on hashing
  3. say 5k-1 receives the frame , it encapsulates the frame in cisco Fabric path header with source switch-id 12(emulated switch ID)
  4. 5k-1 forwards the frame to 5k-3 via 7k-4 (basically the best fabric path SPT)
  5. 5k-3 forwards the frame as classical Ethernet to the host server B
So now in reverse path the frame from 5k-3 will be sent to emulated switch ID-12 which is physically either 5k-1 or 5k-2 , thus achieving true Multipathing


So now lets talk about the benefits of using vPC+ at edge


Functions that are enabled by vPC+ at the edge include:

• attach servers to edge switches with port-channel teaming
• attach additional Classic Ethernet switches in vPC mode
• attach Cisco Fabric Extenders in FEX Active/Active mode.

Thursday, 7 August 2014

vPC+ and EvPC

vPC+  configuration template on nexus 5k(N5K-C5596UP-SUP) with nexus 2k A.K.A FEX , and EvPC

The following post shows how to configure vPC+ and EvPC on nexus 5k and nexus 2k. Before we start just a few points to remember:

I have only covered the configuration for nexus 5k and fex for this post. my next post for fabricpath will have configurations for nexus 7k as well

The following list provides the reference terminology for vPC+ components:
  • vPC+: The functionality enabled on two independent upstream devices to make them appear as a single logical device to the downstream switches, allowing the establishment of PortChannel connections. All the MAC addresses learned from devices locally attached to downstream devices are advertised to the FabricPath domain as "connected" to the defined emulated switch.
  • vPC+ peer device: One of a pair of devices that are connected with the special port channel known as the vPC+ peer link.
  • vPC+ peer link: The link used to synchronize states between the vPC+ peer devices. Both ends must be on 10 Gigabit Ethernet interfaces.
  • vPC+ domain: This domain is formed by the two vPC+ peer link devices. It is also a configuration mode for configuring some of the vPC+ peer link parameters.
  • vPC+ peer-keepalive link: The peer-keepalive link, a Layer 3 link between the vPC+ peer devices, is used to ensure that both devices are up. The peer-keepalive link sends periodic keepalive messages between the vPC peers on an out-of-band path.
  • vPC+ member port: Interface that belongs to the vPC+



5K-1:
!
feature vpc
!
install feature-set fabricpath
feature-set fabricpath
!
feature fex
!
vlan 3
   mode fabricpath
vlan 4
   mode fabricpath
!
fex 100
  pinning max-links 1
  description "FEX0100"
fex 200
  pinning max-links 1
  description "FEX0200"
!
vpc domain 1
  role priority 1
  peer-keepalive destination 10.95.34.104 source 10.95.34.103
  fabricpath switch-id 512
!
interface Ethernet1/14
 channel-group 12  mode active
!
interface Ethernet1/15
  channel-group 12 mode active
!
interface port-channel 12
  switchport mode fabricpath
  speed 10000
  vpc peer-link
!
interface Ethernet1/17
  channel-group 100
!
interface Ethernet1/16
  channel-group 200
!
interface port-channel100
  switchport mode fex-fabric
  switchport trunk allowed vlan none
  fex associate 100
  vpc 100
!
interface port-channel200
  switchport mode fex-fabric
  switchport trunk allowed vlan none
  fex associate 200
  vpc 200
!

5K-2:
!
feature vpc
!
install feature-set fabricpath
feature-set fabricpath
!
feature fex
!
vlan 3
   mode fabricpath
vlan 4
   mode fabricpath
!
fex 100
  pinning max-links 1
  description "FEX0100"
fex 200
  pinning max-links 1
  description "FEX0200"
!
vpc domain 1
  role priority 1
  peer-keepalive destination 10.95.34.103 source 10.95.34.104
  fabricpath switch-id 512
!
interface Ethernet1/14
 channel-group 12  mode active
!
interface Ethernet1/15
  channel-group 12 mode active
!
interface port-channel 12
  switchport mode fabricpath
  speed 10000
  vpc peer-link
!
interface Ethernet1/17
  channel-group 200
!
interface Ethernet1/16
  channel-group 100
!
interface port-channel100
  switchport mode fex-fabric
  switchport trunk allowed vlan none
  fex associate 100
  vpc 100
!
interface port-channel200
  switchport mode fex-fabric
  switchport trunk allowed vlan none
  fex associate 200
  vpc 200
!

after this point your vPC+ peer link and member links should be up , as well as FEX(nexus 2k) should be online

OUTPUTS:

5K2# show fex
  FEX         FEX           FEX                       FEX               
Number    Description      State            Model            Serial     
------------------------------------------------------------------------
100        FEX0100               Online  N2K-C2232TM-E-10GE   SSI1xxxxx
200        FEX0200               Online  N2K-C2232TM-E-10GE   SSI1xxxxx

5K1# show fex
  FEX         FEX           FEX                       FEX               
Number    Description      State            Model            Serial     
------------------------------------------------------------------------
100        FEX0100                Online  N2K-C2232TM-E-10GE   SSI1xxxxxx
200        FEX0200                Online  N2K-C2232TM-E-10GE   SSI1xxxxxx

5K1# show vpc
Legend:
                (*) - local vPC is down, forwarding via vPC peer-link

vPC domain id                              : 1   
vPC+ switch id                             : 512
Peer status                                    : peer adjacency formed ok      
vPC keep-alive status                   : peer is alive                 
vPC fabricpath status                    : peer is reachable through fabricpath
Configuration consistency status    : success 
Per-vlan consistency status           : success                       
Type-2 consistency status             : success 
vPC role                                      : primary                       
Number of vPCs configured         : 67  
Peer Gateway                              : Disabled
Dual-active excluded VLANs       : -
Graceful Consistency Check         : Enabled
Auto-recovery status                    : Disabled

vPC Peer-link status
---------------------------------------------------------------------
id   Port   Status Active vlans    
--   ----   ------ --------------------------------------------------
1    Po12  up     3,4                                                     

vPC status
---------------------------------------------------------------------------
id     Port        Status Consistency Reason       Active vlans vPC+ Attrib
--     ----------  ------ ----------- ------       ------------ -----------
100    Po100       up     success     success      -            DF: Partial, 
                                                                                    FP MAC:      
                                                                                    512.0.0      
100    Po200       up     success     success      -            DF: Partial, 
                                                                                   FP MAC:      
                                                                                    512.0.0      


Now lets configure EvPC. a very simple configuration that can be done on the newly discovered FEX ports .

5K1:
!
interface E100/1/1,E200/1/1
  channel-group 300
!
interface port-channel 300
  switchport mode trunk
  switchport trunk allowed vlan 3,4
  spanning-tree port type edge trunk
!

5K2:
!
!
interface E100/1/1,E200/1/1
  channel-group 300
!
interface port-channel 300
  switchport mode trunk
  switchport trunk allowed vlan 3,4
  spanning-tree port type edge trunk
!

OUTPUT:

5K1# show vpc
Legend:
                (*) - local vPC is down, forwarding via vPC peer-link

vPC domain id                              : 1   
vPC+ switch id                             : 512
Peer status                                    : peer adjacency formed ok      
vPC keep-alive status                   : peer is alive                 
vPC fabricpath status                    : peer is reachable through fabricpath
Configuration consistency status    : success 
Per-vlan consistency status           : success                       
Type-2 consistency status             : success 
vPC role                                      : primary                       
Number of vPCs configured         : 67  
Peer Gateway                              : Disabled
Dual-active excluded VLANs       : -
Graceful Consistency Check         : Enabled
Auto-recovery status                    : Disabled

vPC Peer-link status
---------------------------------------------------------------------
id   Port   Status Active vlans    
--   ----   ------ --------------------------------------------------
1    Po12  up     3,4                                                     

vPC status
---------------------------------------------------------------------------
id     Port        Status Consistency Reason       Active vlans vPC+ Attrib
--     ----------  ------ ----------- ------       ------------ -----------
100    Po100       up     success     success      -                  DF: Partial, 
                                                                                         FP MAC:      
                                                                                         512.0.0      
100    Po200       up     success     success      -                  DF: Partial, 
                                                                                          FP MAC:      
                                                                                          512.0.0      
264143 Po300      up     success     success      3,4             DF: Partial, 
                                                                                           FP MAC:      
                                                                                           512.0.0      

>>>>>>>>>>>output snipped in above<<<<<<<<<<<<<<<<<<<<<



Thursday, 31 July 2014

vPC

Why vPC ?

vPC or virtual port channel allows links that are physically connected to two different Cisco Nexus  Series devices to appear as a single PortChannel to the third device.

In my opinion vPC technology  is a smart way for MLAG (multichassis link aggregation) designed for the nexus product line.

VSS on the other hand for cisco 6500 product line has its own limitations:

Control plane in VSS:
VSS can have maximum of two switches. The two switches are mamaged by one active switch and all configuration and state is synchronized  to the standby switch over the VSL link. All control plane processing is handled by the CPU on the active switch.

Control plane in vPC:
In vPC control plane is separate. Nexus switches are managed separately and have individual processing of control information. States are exchanged through the vpc peer-link.

some reasons why would I want to go with nexus ?

  • Throughput and performance problems with the 6500 product line
  • High port density and port speeds that can go till 100G
  • Next generation platform with enhanced features and protocols
  • vPC