topic RE: Mlag default route in ExtremeSwitching (Other)

Mlag default route

Edward — Tue, 29 Apr 2014 08:14:00 GMT

Hi,

I have an question with mlag which my access switch default route should point to which Core Switch? Please refer to below scenario.

]http://i.imgur.com/gNIDTYA.jpg

Core Switch 1
=========================================
Create vlan test10 tag 10
Configure test10 ipaddress 192.168.10.1/24
configure test10 add port 23, 24 tagged
Create vlan test20 tag 20
Configure test20 ipaddress 192.168.20.1/24
configure test20 add port 23, 24 tagged
configure default ipaddress 192.168.1.1/24
enable ipforwarding

Create vlan isc tag 3000
configure isc ipaddress 1.1.1.1/24
configure isc add port 24 tagged

Create mlag peer "peerToCS2"
config mlag peer "peertoCS2" ipaddress 1.1.1.2
enable mlag port 23 peer "peerToCS2" id 1

Core Switch 2
=========================================
Create vlan test10 tag 10
Configure test10 ipaddress 192.168.10.1/24
configure test10 add port 23, 24 tagged
Create vlan test20 tag 20
Configure test20 ipaddress 192.168.20.1/24
configure test20 add port 23, 24 tagged
configure default ipaddress 192.168.1.2/24
enable ipforwarding

Create vlan isc tag 3000
configure isc ipaddress 1.1.1.2/24
configure isc add port 24 tagged

Create mlag peer "peerToCS1"
config mlag peer "peertoCS1" ipaddress 1.1.1.1
enable mlag port 23 peer "peerToCS1" id 1

Access Switch
==========================================
Create vlan test10 tag 10
configure test10 add port 21 tagged
Create vlan test20 tag 20
configure test20 add port 21 tagged
enable sharing 23 grouping 23-24

configure default ipaddress 192.168.1.4/24
configure iproute add default 192.168.1.x ????

Thanks and Regards,
Edward

RE: Mlag default route

Sumit_Tokle — Tue, 29 Apr 2014 14:18:00 GMT

I believe you can configure the VRRP on core 1 and core 2 switch and configure VIP as default gateway on ACCESS switch.

RE: Mlag default route

Edward — Tue, 29 Apr 2014 14:18:00 GMT

Thanks for your reply, btw VRRP is the only way in this case?

RE: Mlag default route

Sumit_Tokle — Tue, 29 Apr 2014 14:18:00 GMT

VRRP is the best and easiest solution. However, I believe you may configure flow-redirect and change the next hop address. but, I have not seen anyone who uses flow-redirect to achieve.

RE: Mlag default route

Paul_Russo — Tue, 29 Apr 2014 14:18:00 GMT

VRRP would be the best solution to allow for the traffic to really span to both core switches.

RE: Mlag default route

Paul_Russo — Tue, 29 Apr 2014 18:30:00 GMT

Hello Edward Sumit is right what you need to do is set up VRRP and specifically active/active setting which is explained on page 1118 of the 15.4 ExtremeXOS concepts guide.

This will allow both MLAG switches to act as the default gateway.

Let us know if you have questions after reading it.

P

RE: Mlag default route

Edward — Tue, 29 Apr 2014 18:30:00 GMT

Thanks, I will look into vrrp set up.

RE: Mlag default route

Sumit_Tokle — Tue, 29 Apr 2014 19:37:00 GMT

https://community.extremenetworks.com/extreme/topics/active_active_vrrp_with_mlag

We have already discussed acitve-active VRRP with MLAG in above post. still, if you have any doubt then let us know.

RE: Mlag default route

santhosh_kumar — Sat, 11 Oct 2014 10:23:00 GMT

Hi,
I have a query reagrding Mlag in L3 Switch which is acting as a Gateway for all Vlans. we are using BD X8 as core switch in which we have enabled Mlag as below. is it necessary that i have to make VRRP configuration as i can see my gateway switches are working fine with this configuration. kindly suggest me in this regard.

Core Switch 1
=========================================
Create vlan test10 tag 10
Configure test10 ipaddress 192.168.10.1/24
configure test10 add port 23, 24 tagged
Create vlan test20 tag 20
Configure test20 ipaddress 192.168.20.1/24
configure test20 add port 23, 24 tagged
configure default ipaddress 192.168.1.1/24
enable ipforwarding

Create vlan isc tag 3000
configure isc ipaddress 1.1.1.1/24
configure isc add port 24 tagged

Create mlag peer "peerToCS2"
config mlag peer "peertoCS2" ipaddress 1.1.1.2
enable mlag port 23 peer "peerToCS2" id 1

Core Switch 2
=========================================
Create vlan test10 tag 10
Configure test10 ipaddress 192.168.10.1/24
configure test10 add port 23, 24 tagged
Create vlan test20 tag 20
Configure test20 ipaddress 192.168.20.1/24
configure test20 add port 23, 24 tagged
configure default ipaddress 192.168.1.2/24
enable ipforwarding

Create vlan isc tag 3000
configure isc ipaddress 1.1.1.2/24
configure isc add port 24 tagged

Create mlag peer "peerToCS1"
config mlag peer "peertoCS1" ipaddress 1.1.1.1
enable mlag port 23 peer "peerToCS1" id 1

RE: Mlag default route

Paul_Russo — Sat, 11 Oct 2014 17:16:00 GMT

Hello Santhosh im order for MLAG to give you the best solution you really should have VRRP in active/active mode otherwise all of the traffic will go to one switch to be routed. Hope that helps

RE: Mlag default route

dflouret — Wed, 15 Oct 2014 18:11:00 GMT

Santosh,

Here's a picture of what happens if you route traffic through only one member of the MLAG pair (either because it is the default gateway or because VRRP is configured as Active / Standby).

ALL traffic sent to the MLAG switch that is NOT acting as the active Default Gateway must traverse the ISC link.

RE: Mlag default route

Ebrar — Mon, 16 Feb 2015 16:32:00 GMT

Hi,

In our case there is a router in place of the server. We use active-active VRRP and we have a MLAG configuration. But we should also use BGP between router and SWs. We have two BGP neighbor between Router-to-SW1 and Router-to-SW2. Because extreme guys told us we can not use VRRP IP as BGP peer. So because of the router BGP best route selection process, traffic goes through only one SW. I want to use both the SWs as active. I want to throw traffic from all the links between router and SWs.

So what should i do?

Can you help me?

Thanks,
Ebrar