11-21-2012 05:18 AM
Hi everyone,
I've decided to configure interface tracking for HSRP, to decrease priority value of the router in case of int failure. Pretty much straight forward.
Here is my config for HSRP:
router hsrp
Interface bvi52
address family ipv4
hsrp 3 version 1
priority 90
address 10.20.163.33
track GigabitEthernet0/0/0/10 20
The problem is that hsrp thinks that g0/0/0/10 is down, but it's actually not.
p.s. g0/0/0/10 is L2 interface.
RP/0/RSP1/CPU0:ASR9k-2#sh hsrp bvi52 detail
Wed Nov 21 15:08:03.587 EET
BVI52 - Group 3
Local state is Active, priority 70
Hellotime 3 sec holdtime 10 sec
Next hello sent in 0.148
Minimum delay 1 sec, reload delay 5 sec
Hot standby IP address is 10.20.163.33 configured
Active router is local
Standby router is 10.20.163.34 expires in 00:00:07
Standby virtual mac address is 0000.0c07.ac03
4 state changes, last state change 09:08:44
State change history:
Nov 12 09:08:12.407 EET Init -> Listen Delay timer expired
Nov 12 09:08:22.409 EET Listen -> Speak Standby timer expired
Nov 12 09:08:32.411 EET Speak -> Standby Standby timer expired
Nov 21 05:59:19.590 EET Standby -> Active Lower priority active received
Last coup sent: Nov 21 05:59:19.590 EET
Last coup received: Never
Last resign sent: Never
Last resign received: Never
Tracking states for 1 object, 0 up:
Down GigabitEthernet0/0/0/10 Priority decrement: 20
Show int g0/0/0/10 tells completely different story:
RP/0/RSP1/CPU0:ASR9k-2#sh int g0/0/0/10
Wed Nov 21 15:10:49.021 EET
GigabitEthernet0/0/0/10 is up, line protocol is up
Interface state transitions: 3
Hardware is GigabitEthernet, address is 6c9c.ed0d.9d9e (bia 6c9c.ed0d.9d9e)
Description: RNC5_NPGEP11/0
Layer 2 Transport Mode
MTU 1514 bytes, BW 1000000 Kbit (Max: 1000000 Kbit)
reliability 254/255, txload 0/255, rxload 0/255
Encapsulation ARPA,
Full-duplex, 1000Mb/s, LXFDX, link type is autonegotiation
output flow control is off, input flow control is off
loopback not set,
ARP type ARPA, ARP timeout 04:00:00
Last input 00:02:03, output 00:00:00
Last clearing of "show interface" counters never
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 1 packets/sec
84 packets input, 5058 bytes, 0 total input drops
0 drops for unrecognized upper-level protocol
Received 83 broadcast packets, 1 multicast packets
0 runts, 0 giants, 0 throttles, 0 parity
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
636821 packets output, 39363916 bytes, 0 total output drops
Output 59421 broadcast packets, 577338 multicast packets
0 output errors, 0 underruns, 0 applique, 0 resets
0 output buffer failures, 0 output buffers swapped out
3 carrier transitions
Where could be the problem?
Thank You in advance!
Solved! Go to Solution.
11-21-2012 05:47 AM
Unfortunately IOS-XR tracks the state of the IPv4 interface, so interfaces without IP address will be considered down. So this is the expected behavior, tracking doesn't work for L2transport interfaces.
11-21-2012 05:47 AM
Unfortunately IOS-XR tracks the state of the IPv4 interface, so interfaces without IP address will be considered down. So this is the expected behavior, tracking doesn't work for L2transport interfaces.
11-22-2012 12:48 AM
Thank You very much for Your reply!
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