Multi-Chassis Link Aggregation (MLAG)

SOURCE:
Image.png
SW1
hostname SW1
vlan 30
vlan 4094
  trunk group mlagpeer
interface Port-Channel3
  switchport mode trunk
  mlag 3
interface Port-Channel4
  switchport mode trunk
  mlag 4
interface Port-Channel10
  switchport mode trunk
  switchport trunk group mlagpeer
interface Ethernet1
  channel-group 10 mode active
interface Ethernet2
  channel-group 10 mode active
interface Ethernet3
  channel-group 3 mode active
interface Ethernet4
  channel-group 4 mode active
interface Vlan4094
  no autostate
  ip address 12.0.0.1/30
mlag configuration
  domain-id mlag1
  local-interface Vlan4094
  peer-address 12.0.0.2
  peer-link Port-Channel10
end
wr

SW2
hostname SW2
vlan 30
vlan 4094
  trunk group mlagpeer
interface Port-Channel3
  switchport mode trunk
  mlag 3
interface Port-Channel4
  switchport mode trunk
  mlag 4
interface Port-Channel10
  switchport mode trunk
  switchport trunk group mlagpeer
interface Ethernet1
  channel-group 10 mode active
interface Ethernet2
  channel-group 10 mode active
interface Ethernet3
  channel-group 3 mode active
interface Ethernet4
  channel-group 4 mode active
interface Vlan4094
  no autostate
  ip address 12.0.0.2/30
mlag configuration
  domain-id mlag1
  local-interface Vlan4094
  peer-address 12.0.0.1
  peer-link Port-Channel10
end
wr

SW3
hostname SW3
no spanning-tree vlan 4094
vlan 30
interface Port-Channel3
  switchport mode trunk
interface Ethernet1
  switchport access vlan 30
interface Ethernet3
  channel-group 3 mode active
interface Ethernet4
  channel-group 3 mode active
end
wr

SW4
hostname SW4
no spanning-tree vlan 4094
vlan 30
interface Port-Channel4
  switchport mode trunk
interface Ethernet1
  switchport access vlan 30
interface Ethernet3
  channel-group 4 mode active
interface Ethernet4
  channel-group 4 mode active
end
wr

VERIFICATION
SW1#sh mlag
MLAG Configuration:
domain-id           :               mlag1
local-interface     :            Vlan4094
peer-address        :            12.0.0.2
peer-link           :      Port-Channel10
peer-config         :          consistent
MLAG Status:
state               :              Active
negotiation status  :           Connected
peer-link status    :                  Up
local-int status    :                  Up
system-id           :   52:00:00:cb:38:c2
MLAG Ports:
Disabled            :                   0
Configured          :                   0
Inactive            :                   0
Active-partial      :                   0
Active-full         :                   2

SW1# sh mlag interfaces detail
                                        local/remote
 mlag         state   local   remote    oper    config    last change   changes
—— ————- ——- ——– ——- ———- ————– ——-
    3   active-full     Po3      Po3   up/up   ena/ena    0:13:09 ago         4
    4   active-full     Po4      Po4   up/up   ena/ena    0:13:09 ago         4

SW1#sh lacp sys-id detailed
System Identifier used by LACP:
System priority: 32768
Switch MAC Address: 50:00:00:d7:ee:0b
  802.11.43 representation: 8000,50-00-00-d7-ee-0b
MLAG System-identifier: 52:00:00:cb:38:c2
  802.11.43 representation: 8000,52-00-00-cb-38-c2

SW2#sh mlag
MLAG Configuration:
domain-id           :               mlag1
local-interface     :            Vlan4094
peer-address        :            12.0.0.1
peer-link           :      Port-Channel10
peer-config         :          consistent
MLAG Status:
state               :              Active
negotiation status  :           Connected
peer-link status    :                  Up
local-int status    :                  Up
system-id           :   52:00:00:cb:38:c2
MLAG Ports:
Disabled            :                   0
Configured          :                   0
Inactive            :                   0
Active-partial      :                   0
Active-full         :                   2

SW2#sh mlag interfaces detail
                                        local/remote
 mlag         state   local   remote    oper    config    last change   changes
—— ————- ——- ——– ——- ———- ————– ——-
    3   active-full     Po3      Po3   up/up   ena/ena    0:14:28 ago         4
    4   active-full     Po4      Po4   up/up   ena/ena    0:14:28 ago         4

SW2#sh lacp sys-id detailed
System Identifier used by LACP:
System priority: 32768
Switch MAC Address: 50:00:00:cb:38:c2
  802.11.43 representation: 8000,50-00-00-cb-38-c2
MLAG System-identifier: 52:00:00:cb:38:c2
  802.11.43 representation: 8000,52-00-00-cb-38-c2

SW2#sh etherchannel detailed
Port Channel Port-Channel3 (Fallback State: Unconfigured):
  Active Ports:
       Port                Time became active       Protocol    Mode
    ——————- ———————— ————– ——
       Ethernet3           16:59:15                 LACP        Active
       PeerEthernet3       16:59:16                 LACP        Active
Port Channel Port-Channel4 (Fallback State: Unconfigured):
  Active Ports:
       Port                Time became active       Protocol    Mode
    ——————- ———————— ————– ——
       Ethernet4           16:59:15                 LACP        Active
       PeerEthernet4       16:59:16                 LACP        Active
Port Channel Port-Channel10 (Fallback State: Unconfigured):
  Active Ports:
       Port            Time became active       Protocol    Mode
    ————— ———————— ————– ——
       Ethernet1       16:59:06                 LACP        Active
       Ethernet2       16:59:06                 LACP        Active
Advertisements

Stackwise, VSS, VPC, MLAG

SOURCE:
https://supportforums.cisco.com/discussion/12367366/vss-vs-stackwise-vs-vpc

Stackwise:
This is the Proprietary cabling mechanism and is limited to distance. The advantage of Stackwise over VSS is that you can add/stack around 9 devices at one go.Were as you cant do the same with VSS.

Another advantage is that if stacking device does not require any configuration only that the device needs to be supported.
Cisco StackWise technology unites up to nine individual switches into a single logical unit, using special stack-interconnect cables and stacking software. The individual switches can be any combination of Cisco Catalyst 3750 and Cisco Catalyst 3750-E Series Switches.

VSS (Virtual Switching System):
SOURCE:
http://www.cisco.com/c/en/us/products/collateral/switches/catalyst-6500-virtual-switching-system-1440/prod_qas0900aecd806ed74b.html

VSS can be done with 4500 or 6500 series . It supports only two chasis and it uses 10GE interfaces and can be geographically separated.

VPC (Virtual PortChannel):
SOURCE:
http://www.cisco.com/c/en/us/products/collateral/switches/nexus-5000-series-switches/configuration_guide_c07-543563.html

It is Nexus specific technology and you cant configure this with other catalyst switches.
This is the new technology were in you can connect one switch (Access)to two uplink switches(distribution switch) and form an ether channel between them. Thats the good advantage of VPC which none of them have.

MLAG (Multichassis Link Aggregation):
SOURCE:
http://ethancbanks.com/2014/03/27/the-ethernet-switching-landscape-part-04-multichassis-link-aggregation-mlag/

Both Arista’s MLAG and Cisco’s vPC are similar to configure and operate, with similar concerns. In general, I found the Arista MLAG setup a bit easier, because many of the details are handled for the network operator when compared to the more granular fussiness of the vPC configuration.

MLAG is the ability of two and sometimes more switches to act like a single switch when forming link bundles. This allows a host to uplink to two switches for physical diversity, while still only having a single bundle interface to manage.

Also, two switches could connect to two other switches using MLAG, with all links forwarding.

For access layer when I have only 3750 stackable switches I cant do VSS or VPC on that hence would be using stacking and connecting them together to have single access.

6500/4500 I would use the VSS here at the distribution layer to avoid much impact.
VPC is best but you need to have Nexus device if you want to use this feature.

Arista vEOS under VirtualBox in GNS3 1.2.1

Download Arista vEOS vmdk and Aboot-veos from https://www.arista.com/en/support/software-download

In my example are Aboot-veos-2.1.0.iso and vEOS-lab-4.14.2F.vmdk

Set boot order to cd first
1
2
Set CD/DVD Drive as IDE Primary Slave
3
4
5
6
vEOS1:
login: admin
Last login: Tue Dec 16 12:48:19 on ttyS0
>en
#conf t
(config)#hostname vEOS1
(config)#int e1
(config-if-Et1)#no switchport
(config-if-Et1)#ip address 10.0.0.1/24
(config-if-Et1)#end
#wr
Copy completed successfully.
vEOS2:
login: admin
Last login: Tue Dec 16 12:48:19 on ttyS0
>en
#conf t
(config)#hostname vEOS2
(config)#int e1
(config-if-Et1)#no switchport
(config-if-Et1)#ip address 10.0.0.2/24
(config-if-Et1)#end
#wr
Copy completed successfully.
vEOS2#ping 10.0.0.1
PING 10.0.0.1 (10.0.0.1) 72(100) bytes of data.
80 bytes from 10.0.0.1: icmp_req=1 ttl=64 time=94.3 ms