LACP Configurations - Maipu and Cisco Switches

Hi All, I was doing a inter-operability testing for Maipu ME switches and Cisco 2960 and ME switches for LACP features (on mode and LACP mode).  It is working absolutely fine, In case any body is having any issues in configuration, They can refer this testing process and do it. 

I want to share testing report with you. It will help you in any future deployments.  This post is for LACP mode. In next post, I will share ON mode.

Maipu and Cisco LACP testing

Objective -  To test Maipu and Cisco LACP interoperability.

Cisco configuration -

port-channel load-balance src-dst-mac

interface Port-channel1

 switchport trunk native vlan 2

 switchport mode trunk

 load-interval 30

!

interface FastEthernet0/1

 switchport access vlan 10

 switchport mode access

!

interface FastEthernet0/2

 switchport access vlan 10

 switchport mode access

!

interface FastEthernet0/3

 switchport access vlan 10

 switchport mode access

!

interface FastEthernet0/23

 switchport trunk native vlan 2

 switchport mode trunk

 load-interval 30

 channel-group 1 mode passive

!

interface FastEthernet0/24

 switchport trunk native vlan 2

 switchport mode trunk

 load-interval 30

 channel-group 1 mode passive

!

Maipu Configuration –

link-aggregation 1 mode lacp

link-aggregation 1 load-balance src-dst-mac

vlan 1

 exit

port 0/0/14

 duplex full

 speed 100

 link-aggregation 1 active

 exit

port 0/0/15

 duplex full

 speed 100

 link-aggregation 1 active

 exit

link-aggregation 1

 port-type nni

 port mode trunk

 port trunk allowed vlan all

 port trunk pvid vlan 2

 exit

Show Outputs

Cisco outputs

Port Channel status-

Port Channel interface - 

Interface fa0/23

Fa0/24

Show version

Maipu outputs –

Link aggregation output -

Port 0/0/14 -

Port 0/0/15 -

Test Conclusion - Maipu and Cisco LACP is properly working fine and bandwidth is load-balancing on both links. 

Hope this information will help you. 

Thanks for reading.. 

For feedback. Plz comment with Name and Mail ID..  

Maipu - Failover Configuration Using Static Route

Hi , I want to share one testing report with all of you. This is majorly focused on Fail over configuration with static routing.. Below are objectives for testings...

Objective - 

• R1 Client Router both interface should be UP every time.
• PC should ping 20.1.1.1 Loopback interface continuously.
•  Auto Failover should happen.
• One time one port should forward traffic to ISP router.
• As the primary F0 links fails, The F1 should get active to forward traffic to ISP router.
• After restoration of F0 links, The F0 should forward the traffic to ISP router.

Topology:

Configurations–

(Client)R1-

interface fastethernet0

 ip address 10.20.20.2 255.255.255.0

 media-type fiber

 rate 100

 duplex full

 load-interval 30

 exit

interface fastethernet1

 ip address 10.20.30.2 255.255.255.0

 media-type fiber

 rate 100

 duplex full

 load-interval 30

  exit

interface vlan1

 ip address 10.1.1.1 255.255.255.0

 exit

ip route 0.0.0.0 0.0.0.0 fastethernet0

ip route 0.0.0.0 0.0.0.0 fastethernet1 10

(ISP)R2 –

interface loopback0

 ip address 20.1.1.1 255.255.255.0

 exit

interface fastethernet0

 ip address 10.20.20.1 255.255.255.0

 media-type fiber
 keepalive gateway 10.20.20.2 4

 rate 100

 duplex full

 load-interval 30

 exit

interface fastethernet1

 ip address 10.20.30.1 255.255.255.0

 media-type fiber
 keepalive gateway 10.20.30.2 4

 rate 100

 duplex full

 load-interval 30

 exit

ip route 10.1.1.0 255.255.255.0 10.20.20.2

ip route 10.1.1.0 255.255.255.0 10.20.30.2 10

Testing Scenarios – 

10.1.1.2  ping to Gateway to observe delay….

10.1.1.2  (PC) ping to 20.1.1.1 (Loopback interface in ISP Router)

Currently in this screen shot, both interface as UP. Primary link F0 is forwarding traffic to ISP router.

After Primary link is down –

You can see F0 is down and F1 is up, F1 is forwarding traffic to ISP router.

Below is ping snap shot from 10.1.1.2 (PC)  to 20.1.1.1 ( ISP loopback interface)

10.1.1.2 (PC) pinging to Gateway IP

After restoration of link

As the link is restored, F0 interface is active interface to forward traffic to ISP router.

The F1 forwarding is shifted to F0 interface.  PC (10.1.1.2) pinging to ISP router loopback (20.1.1.1)

PC pinging to Gateway 10.1.1.1

Above testing successfully demonstrates above objectives are successfully. 

Hope this information will help you. 

Thanks for reading.. 

For feedback. Plz comment with Name and Mail ID..