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

Attention: The Community will be in read-only mode on 12/14/2017 from 12:00 am pacific to 11:30 am.

During this time you will only be able to see content. Other interactions such as posting, replying to questions, or marking content as helpful will be disabled for few hours.

We apologize for the inconvenience while we perform important updates to the Community.

New Member

HSRP and tracking ip route

I'm trying to use the track command to determine if a route is present or not via eigrp. If the route is not present then I would like HSRP to fail over to the standby router.

I'm tracking a route to a loopback across a WAN interface. The tracking works because I can shut down the WAN interface issue a show track and see that it is down. However HRSP does not fail over. I have standby 1 track 10 command in the interface, but nothing happens.

Thanks

1 ACCEPTED SOLUTION

Accepted Solutions
Cisco Employee

Re: HSRP and tracking ip route

Hello Christopher,

You seem to have a difficult-to-notice configuration typo in both the R1 and R2 configurations.

Note that both on R1 and R2 Fa0/1, you have some standby commands written as "standby 1" while others use just "standby" without the group number. However, if you do not specify the group number, it is assumed to be group 0. What you have created here is basically a mix of configurations for two different standby groups on a single interface.

The solution should be a simple one - make sure that all your standby commands refer to an explicit group number, for example, 1.

Best regards,

Peter

3 REPLIES
New Member

Re: HSRP and tracking ip route

Here are the config's.

New Member

Re: HSRP and tracking ip route

Disregard got it to work. It was an HSRP configuration.

Cisco Employee

Re: HSRP and tracking ip route

Hello Christopher,

You seem to have a difficult-to-notice configuration typo in both the R1 and R2 configurations.

Note that both on R1 and R2 Fa0/1, you have some standby commands written as "standby 1" while others use just "standby" without the group number. However, if you do not specify the group number, it is assumed to be group 0. What you have created here is basically a mix of configurations for two different standby groups on a single interface.

The solution should be a simple one - make sure that all your standby commands refer to an explicit group number, for example, 1.

Best regards,

Peter

392
Views
0
Helpful
3
Replies
CreatePlease to create content