11-24-2012 11:50 PM - edited 03-04-2019 06:14 PM
11-27-2012 09:25 AM
Disclaimer
The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
Liability Disclaimer
In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
Posting
Besides PBR, there are other approaches you might use, "best" depends on what you're real requirements are.
For example, do you really need particular soruce VLANs to go via different paths, or are you looking for better or optimal performance?
You might just equally route from your L3 switch to both WAN routers. This would provide basic load balancing. If you need better treatment for some traffic, QoS policies on the WAN routers could provide that.
For optimal load balancing, OER/PfR on the WAN routers can dynamically load balance. Here too QoS can provide different treatment for different traffic.
If you really want to direct traffic using gateways, you could trunk to both WAN routers, run HSRP (or GLBP) between them.
11-25-2012 04:08 AM
Disclaimer
The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
Liability Disclaimer
In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
Posting
What subnets do you actually want to GLBP? Where's your subnets gateways? Core switch is pure L2 or is it L3?
11-25-2012 09:37 PM
Dear Joseph,
My switch is Core switch 4500 (L3), and all the vlans are created on Core switch. I need to balance my traffic,
As,
Vlan 10 and vlan 20 should go from WAN 1 link.
Vlan 30 should go from WAN 2 link.
And all the subnet gateways are configured on Core switch.
vlan 10 gateway 10.100.10.254
vlan 20 gateway 10.100.20.254
vlan 30 gateway 10.100.30.254
11-25-2012 10:14 PM
Hi,
I think with such requirement you can use Policy-based Routing (PBR) instead of GLBP. Create two access-lists one for subnets VLAN 10/20 second for VLAN 30. And route them with set ip nex-hop.
ip access-list extended 101
permit ip 10.100.10.0 0.0.0.255 any
permit ip 10.100.20.0 0.0.0.255 any
ip access-list extended 102
permit ip 10.100.30.0 0.0.0.255 any
route-map WAN1 permit 10
match ip address 101
set ip next-hop 10.100.10.3
route-map WAN2 permit 10
match ip address 102
set ip next-hop 10.100.10.4
int vlan 10
ip policy route-map WAN1
int vlan 20
ip policy route-map WAN1
int vlan 30
ip policy route-map WAN2
Hope it will help.
11-26-2012 09:27 PM
Hi Abzal,
I can do PBR,but I need redundancy for it,if one WAN link fails then what shall I do.
Thanks
11-27-2012 06:24 AM
Hi Majed,
Ok, then try this one,
ip access-list extended 101
permit ip 10.100.10.0 0.0.0.255 any
permit ip 10.100.20.0 0.0.0.255 any
ip access-list extended 102
permit ip 10.100.30.0 0.0.0.255 any
IP SLA configurations:
ip sla 1
icmp-echo 10.100.10.3
timeout 500
frequency 1
ip sla schedule 1 life forever start-time now
ip sla 2
icmp-echo 10.100.10.4
timeout 500
frequency 1
ip sla schedule 2 life forever start-time now
track 10 rtr 1 reachability
delay down 1 up 1
!
track 20 rtr 2 reachability
delay down 1 up 1
route-map WAN1 permit 10
match ip address 101
set ip next-hop verify-availability 10.100.10.3 track 10
route-map WAN2 permit 10
match ip address 102
set ip next-hop verify-availability 10.100.10.4 track 20
ip route 0.0.0.0 0.0.0.0 10.100.10.3 track 10
ip route 0.0.0.0 0.0.0.0 10.100.10.4 track 20
int vlan 10
ip policy route-map WAN1
int vlan 20
ip policy route-map WAN1
int vlan 30
ip policy route-map WAN2
Refer this link with great explanation
https://supportforums.cisco.com/docs/DOC-8313
Hope it will help.
11-27-2012 09:25 AM
Disclaimer
The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
Liability Disclaimer
In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
Posting
Besides PBR, there are other approaches you might use, "best" depends on what you're real requirements are.
For example, do you really need particular soruce VLANs to go via different paths, or are you looking for better or optimal performance?
You might just equally route from your L3 switch to both WAN routers. This would provide basic load balancing. If you need better treatment for some traffic, QoS policies on the WAN routers could provide that.
For optimal load balancing, OER/PfR on the WAN routers can dynamically load balance. Here too QoS can provide different treatment for different traffic.
If you really want to direct traffic using gateways, you could trunk to both WAN routers, run HSRP (or GLBP) between them.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide