Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

Working RTR in a 6506e Switch

I have 2 ISPs.  If one fails I want the routes to go out a different set of ASA's then the primary.  I have tried to figure out how to use the RTR command without the IP SLA because it does not exists in my IOS on the switch, so I can put the track command at the end of my route statements in the switch, but have seen a solution for this.

Does anybody have a solution to this issue?

Thank you for your help

1 ACCEPTED SOLUTION

Accepted Solutions
Hall of Fame Super Blue

Re: Working RTR in a 6506e Switch

peter.williams@waiglobal.com

Jon,

If the primary route comes back up will it fail back to the primary route from the backup route automatically?

ex -

rtr 1

type echo protocol ipIcmpEcho 195.53.168.121

timeout 200

frequency 10

rtr schedule 1 life forever start-time now

track 123 rtr 1 reachability

ip route x.x.x.x 195.53.168.121 track 123 - this would be the primary route

ip route x.x.x.x 195.53.168.150 - this would be the backup route

Is the example above correct?

Thank you for your help

Peter

You should make the backup route a floating static so it is only put in the routing table if the primary route is removed eg.

ip route x.x.x.x 195.53.168.150 250

what will happen -

1) if the primary link is up the primary route will be in the routing table

2) if IP SLA ping fails then the primary route is removed and now the secondary route is instaled in the routing table

3) if the IP SLA ping then starts to work again the primary route is reinstalled into the routing table and the backup route is removed

Jon

8 REPLIES
Hall of Fame Super Blue

Re: Working RTR in a 6506e Switch

What IOS are you running on your switch ?

If you are running hybrid mode please include IOS and CatOS.

Jon

New Member

Re: Working RTR in a 6506e Switch

IOS (tm) s3223_rp Software (s3223_rp-ADVIPSERVICESK9_WAN-M), Version 12.2(18)SXF, RELEASE SOFTWARE (fc1)

Thank you

Hall of Fame Super Blue

Re: Working RTR in a 6506e Switch

Peter

Are you saying there are missing options or that you simply want to see a config example ie. -

Jon

New Member

Re: Working RTR in a 6506e Switch

Jon,

I am missing the IP SLA option but I have the RTR option.  I would like to see an example that would work for me using the RTR command, so I track the routes in my switch.  I think I do not have the IP SLA option becasue of the age of the IOS, I would hate to change the IOS just for that command.

Thank you for your help

Hall of Fame Super Blue

Re: Working RTR in a 6506e Switch

Peter

rtr 1

type echo protocol ipIcmpEcho 195.53.168.121

timeout 200

frequency 10

rtr schedule 1 life forever start-time now

track 123 rtr 1 reachability

ip route x.x.x.x track 123

Jon

New Member

Re: Working RTR in a 6506e Switch

Jon,

If the primary route comes back up will it fail back to the primary route from the backup route automatically?

ex -

rtr 1

type echo protocol ipIcmpEcho 195.53.168.121

timeout 200

frequency 10

rtr schedule 1 life forever start-time now

track 123 rtr 1 reachability

ip route x.x.x.x 195.53.168.121 track 123 - this would be the primary route

ip route x.x.x.x 195.53.168.150 - this would be the backup route

Is the example above correct?

Thank you for your help

Hall of Fame Super Blue

Re: Working RTR in a 6506e Switch

peter.williams@waiglobal.com

Jon,

If the primary route comes back up will it fail back to the primary route from the backup route automatically?

ex -

rtr 1

type echo protocol ipIcmpEcho 195.53.168.121

timeout 200

frequency 10

rtr schedule 1 life forever start-time now

track 123 rtr 1 reachability

ip route x.x.x.x 195.53.168.121 track 123 - this would be the primary route

ip route x.x.x.x 195.53.168.150 - this would be the backup route

Is the example above correct?

Thank you for your help

Peter

You should make the backup route a floating static so it is only put in the routing table if the primary route is removed eg.

ip route x.x.x.x 195.53.168.150 250

what will happen -

1) if the primary link is up the primary route will be in the routing table

2) if IP SLA ping fails then the primary route is removed and now the secondary route is instaled in the routing table

3) if the IP SLA ping then starts to work again the primary route is reinstalled into the routing table and the backup route is removed

Jon

New Member

Re: Working RTR in a 6506e Switch

Thank you for your help!!

440
Views
0
Helpful
8
Replies