Please do through my pasted config and notice that i did administratively shut down the interface and it knows it down as well based on the output:
R01(config-if)#
*Jul 5 19:10:08.812: %TRACK-6-STATE: 1 interface Et0/1 line-protocol Up -> Down
R01(config-if)#
*Jul 5 19:10:08.817: %BGP-5-NBR_RESET: Neighbor 172.16.3.1 reset (Interface flap)
*Jul 5 19:10:08.817: %BGP-5-ADJCHANGE: neighbor 172.16.3.1 Down Interface flap
*Jul 5 19:10:08.817: %BGP_SESSION-5-ADJCHANGE: neighbor 172.16.3.1 IPv4 Unicast topology base removed from session Interface flap
R01(config-if)#
*Jul 5 19:10:10.815: %LINK-5-CHANGED: Interface Ethernet0/1, changed state to administratively down
*Jul 5 19:10:11.819: %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet0/1, changed state to down
So yes it knows it is down as the tracking object initiated.
HSRP object tracking
Moderator: mike
-
- Posts: 5067
- Joined: Wed Mar 15, 2017 4:44 pm
- Location: London
- Contact:
Re: HSRP object tracking
here you are:)
Missed preempt commands on R1 and R2 under e0/0
R1 config with IP SLA
track 2 ip sla 1 reachability
###########IP SLA sending ICMP to R3 172.16.3.1#############
ip sla 1
icmp-echo 172.16.3.1 source-interface Ethernet0/1
threshold 1000
timeout 1500
frequency 10
ip sla schedule 1 start-time now recurring
interface Ethernet0/0
ip address 10.100.100.2 255.255.255.0
standby 1 ip 10.100.100.1
standby 1 priority 105
standby 1 preempt
standby 1 authentication md5 key-string cisco123
standby 1 track 2 decrement 10
if you shutdown R3 e0/0
the IP SLA and track change Active HSRP to R2
and trace is following:
Before R3 e0/0 shutdown:
PC01#trace 10.77.77.10
Type escape sequence to abort.
Tracing the route to 10.77.77.10
VRF info: (vrf in name/id, vrf out name/id)
1 10.0.0.1 0 msec 1 msec 0 msec
2 10.100.100.2 1 msec 1 msec 0 msec #########R1
3 172.16.3.1 1 msec 0 msec 1 msec
4 99.0.3.1 1 msec 1 msec 0 msec
5 77.77.77.2 1 msec 1 msec 1 msec
6 10.77.77.10 1 msec * 2 msec
After R3 e0/0 shut
PC01#trace 10.77.77.10
Type escape sequence to abort.
Tracing the route to 10.77.77.10
VRF info: (vrf in name/id, vrf out name/id)
1 10.0.0.1 1 msec 0 msec 0 msec
2 10.100.100.3 1 msec 1 msec 0 msec############ (R2)
3 172.16.5.5 1 msec 1 msec 1 msec
4 99.0.5.1 1 msec 1 msec 1 msec
5 77.77.77.2 1 msec 1 msec 1 msec
6 10.77.77.10 1 msec * 2 msec
UD
Missed preempt commands on R1 and R2 under e0/0
R1 config with IP SLA
track 2 ip sla 1 reachability
###########IP SLA sending ICMP to R3 172.16.3.1#############
ip sla 1
icmp-echo 172.16.3.1 source-interface Ethernet0/1
threshold 1000
timeout 1500
frequency 10
ip sla schedule 1 start-time now recurring
interface Ethernet0/0
ip address 10.100.100.2 255.255.255.0
standby 1 ip 10.100.100.1
standby 1 priority 105
standby 1 preempt
standby 1 authentication md5 key-string cisco123
standby 1 track 2 decrement 10
if you shutdown R3 e0/0
the IP SLA and track change Active HSRP to R2
and trace is following:
Before R3 e0/0 shutdown:
PC01#trace 10.77.77.10
Type escape sequence to abort.
Tracing the route to 10.77.77.10
VRF info: (vrf in name/id, vrf out name/id)
1 10.0.0.1 0 msec 1 msec 0 msec
2 10.100.100.2 1 msec 1 msec 0 msec #########R1
3 172.16.3.1 1 msec 0 msec 1 msec
4 99.0.3.1 1 msec 1 msec 0 msec
5 77.77.77.2 1 msec 1 msec 1 msec
6 10.77.77.10 1 msec * 2 msec
After R3 e0/0 shut
PC01#trace 10.77.77.10
Type escape sequence to abort.
Tracing the route to 10.77.77.10
VRF info: (vrf in name/id, vrf out name/id)
1 10.0.0.1 1 msec 0 msec 0 msec
2 10.100.100.3 1 msec 1 msec 0 msec############ (R2)
3 172.16.5.5 1 msec 1 msec 1 msec
4 99.0.5.1 1 msec 1 msec 1 msec
5 77.77.77.2 1 msec 1 msec 1 msec
6 10.77.77.10 1 msec * 2 msec
UD
-
- Posts: 5067
- Joined: Wed Mar 15, 2017 4:44 pm
- Location: London
- Contact:
Re: HSRP object tracking
YOU HAVE missed preempt commands on R1 and R2stevenjwilliams83 wrote: ↑Wed Jul 05, 2017 8:21 pmPlease do through my pasted config and notice that i did administratively shut down the interface and it knows it down as well based on the output:
R01(config-if)#
*Jul 5 19:10:08.812: %TRACK-6-STATE: 1 interface Et0/1 line-protocol Up -> Down
R01(config-if)#
*Jul 5 19:10:08.817: %BGP-5-NBR_RESET: Neighbor 172.16.3.1 reset (Interface flap)
*Jul 5 19:10:08.817: %BGP-5-ADJCHANGE: neighbor 172.16.3.1 Down Interface flap
*Jul 5 19:10:08.817: %BGP_SESSION-5-ADJCHANGE: neighbor 172.16.3.1 IPv4 Unicast topology base removed from session Interface flap
R01(config-if)#
*Jul 5 19:10:10.815: %LINK-5-CHANGED: Interface Ethernet0/1, changed state to administratively down
*Jul 5 19:10:11.819: %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet0/1, changed state to down
So yes it knows it is down as the tracking object initiated.
standby 1 preempt
-
- Posts: 77
- Joined: Mon Mar 20, 2017 1:53 pm
Re: HSRP object tracking
Ugh. Thank you. Stare at something long enough and you miss stuff.