HSRP problem...

syancy · ‎08-02-2004

I have been asked to look at a problem concerning HSRP. I believe the configuration is incorrect but have been told this config has been wporking at a another site. Below are the hsrp configs for both routers. Someone please give this a sanity check as I think the configs are incorrect.

ROUTER 1:

interface FastEthernet0/0

description FE-1

ip address 192.168.146.16 255.255.255.0

ip mask-reply

no ip proxy-arp

ip pim query-interval 1

ip pim sparse-dense-mode

ip ospf hello-interval 1

ip ospf dead-interval 3

ip ospf priority 255

ip igmp query-max-response-time 5

ip igmp query-interval 7

keepalive 1

speed 100

full-duplex

ntp broadcast

standby 1 ip 192.168.146.8

standby 1 timers 1 3

standby 1 priority 100

standby 1 preempt

standby 1 name one

standby 1 track FastEthernet0/1 10

standby 1 track Loopback101 10

standby 1 track Loopback102 5

standby 1 track Multilink5 10

!

interface Serial0/0:0

description PKTBTSCONc-15-1-276-1

no ip address

encapsulation ppp

keepalive 1

ppp multilink

multilink-group 5

!

interface FastEthernet0/1

description FE-2

ip address 192.168.147.16 255.255.255.0

ip mask-reply

no ip proxy-arp

ip pim query-interval 1

ip pim sparse-dense-mode

ip ospf hello-interval 1

ip ospf dead-interval 3

ip ospf priority 255

ip igmp query-max-response-time 5

ip igmp query-interval 7

keepalive 1

speed 100

full-duplex

ntp broadcast

standby 2 ip 192.168.147.8

standby 2 timers 1 3

standby 2 priority 100

standby 2 preempt

standby 2 name two

standby 2 track FastEthernet0/0 10

standby 2 track Loopback101 10

standby 2 track Loopback102 5

standby 2 track Multilink5 10

!

interface Serial0/1:0

description PKTBTSCONc-15-1-277-1

no ip address

encapsulation ppp

keepalive 1

ppp multilink

multilink-group 5

ROUTER 2:

interface FastEthernet0/0

description FE-1

ip address 192.168.146.17 255.255.255.0

ip mask-reply

no ip proxy-arp

ip pim query-interval 1

ip pim sparse-dense-mode

ip ospf hello-interval 1

ip ospf dead-interval 3

ip ospf priority 255

ip igmp query-max-response-time 5

ip igmp query-interval 7

keepalive 1

speed 100

full-duplex

ntp broadcast

standby 1 ip 192.168.146.8

standby 1 timers 1 3

standby 1 priority 100

standby 1 preempt

standby 1 name one

standby 1 track FastEthernet0/1 10

standby 1 track Loopback101 10

standby 1 track Loopback102 5

standby 1 track Multilink5 10

!

interface Serial0/0:0

description PKTBTSCONc-15-1-276-1

no ip address

encapsulation ppp

keepalive 1

ppp multilink

multilink-group 5

!

interface FastEthernet0/1

description FE-2

ip address 192.168.147.17 255.255.255.0

ip mask-reply

no ip proxy-arp

ip pim query-interval 1

ip pim sparse-dense-mode

ip ospf hello-interval 1

ip ospf dead-interval 3

ip ospf priority 255

ip igmp query-max-response-time 5

ip igmp query-interval 7

keepalive 1

speed 100

full-duplex

ntp broadcast

standby 2 ip 192.168.147.8

standby 2 timers 1 3

standby 2 priority 100

standby 2 preempt

standby 2 name two

standby 2 track FastEthernet0/0 10

standby 2 track Loopback101 10

standby 2 track Loopback102 5

standby 2 track Multilink5 10

!

interface Serial0/1:0

description PKTBTSCONc-15-1-277-1

no ip address

encapsulation ppp

keepalive 1

ppp multilink

multilink-group 5

smif101 · ‎08-02-2004

What is the problem that you are having? One thing I would do with this config is change the ospf timers back to the defaults. Get rid of the hello and dead intervals you have configured. Another thing is I would change the priority under your hsrp config to be 100 on your primary router and 110 on your secondary router. Also I would get rid of the timers config under hsrp too. Also I would get rid of the keepalive you have set under your ethernet statement too and change it back to default. Go with the basic config and everything should work fine. Why was there so many changes to all of the timers? Did TAC tell you to do that?

syancy · ‎08-02-2004

The problem I am having is that the interfaces keep going up and down. They seem to toggling bacck and forth from standby to Active. I also question the preempt statement. Shouldn't that be only on the primary or the interface with the highest priority?

erhoehne · ‎08-02-2004

I agree with the first reply. Both interfaces on both routers have the same hsrp priority. That is probably why they're getting confused on who should be primary and who should be backup.

a.awan · ‎08-02-2004

I agree that the priorities should be configured explicitly to ensure that the active router does take over but i disagree with the fact that this is causing the confusion as Cisco's implementation of HSRP has a workaround for same priorities (higher interface ip address becomes active).

Configure your switch ports connecting to the router for portfast and if that does not solve the issue use use-bia command and this should fix your issue.

smif101 · ‎08-02-2004

As stated in the other reply, the priority won't cause the flapping you have. But I do think the timers configs you have are messing it up. Is the load on the interfaces pretty high?

pmajumder · ‎08-02-2004

I agree that most likely the issue is with the timers, specially the standby hellotime & holdtime (1 and 3 seconds). See document below on avoiding HSRP instability.

http://www.cisco.com/en/US/customer/tech/tk648/tk362/technologies_configuration_example09186a0080093f93.shtml

Regards

Pradeep

deilert · ‎08-02-2004

I think that you are setting the keepalive setting way too low . Why don't you remove the keealive 1 from all the interfaces and let them have the default values , If the keepalive parameters do not match over your serial links this will cause them to flap.

syancy · ‎08-02-2004

Thanks for all you responses. I have disabled hsrp and I still have the problem of the interfaces flapping. I have noticed each time the interface flaps the next message is OSPF-4-CONFLICTING-LSAID...Found LSA with the same host bit.....Would this cause an interface to flap?

deilert · ‎08-02-2004

this would cause ospf to flap but not the line , Take a look at your keepalives make sure they match.

smif101 · ‎08-02-2004

Did you change the OSPF timers back to default and still get this error? The dead-interval should be 4x the hello interval and that might be another reason for your problems.