06-03-2021 01:31 PM
Hi everyone
I have a situation in a lab where I'm running a couple ASAs (ASAv version 9.14(1)). On one of them I'm trying to configure a static route using tracking, when I do that it doesn't show in the routing table.
asa# sh run route
route point2point 172.30.0.0 255.255.0.0 10.10.4.1 1 track 4
route outside 0.0.0.0 0.0.0.0 8.8.10.1 1
asa#
asa# sh route
Codes: L - local, C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2, V - VPN
i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS inter area, * - candidate default, U - per-user static route
o - ODR, P - periodic downloaded static route, + - replicated route
SI - Static InterVRF
Gateway of last resort is 8.8.10.1 to network 0.0.0.0
S* 0.0.0.0 0.0.0.0 [1/0] via 8.8.10.1, outside
C 8.8.10.0 255.255.255.0 is directly connected, outside
L 8.8.10.2 255.255.255.255 is directly connected, outside
C 10.10.4.0 255.255.255.252 is directly connected, point2point
L 10.10.4.2 255.255.255.255 is directly connected, point2point
When I remove the tracking is when the route shows up in the routing table.
asa(config)# sh run route
route outside 0.0.0.0 0.0.0.0 8.8.10.1 1
route point2point 172.30.0.0 255.255.0.0 10.10.4.1 1
asa# sh route
Codes: L - local, C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2, V - VPN
i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS inter area, * - candidate default, U - per-user static route
o - ODR, P - periodic downloaded static route, + - replicated route
SI - Static InterVRF
Gateway of last resort is 8.8.10.1 to network 0.0.0.0
S* 0.0.0.0 0.0.0.0 [1/0] via 8.8.10.1, outside
C 8.8.10.0 255.255.255.0 is directly connected, outside
L 8.8.10.2 255.255.255.255 is directly connected, outside
C 10.10.4.0 255.255.255.252 is directly connected, point2point
L 10.10.4.2 255.255.255.255 is directly connected, point2point
S 172.30.0.0 255.255.0.0 [1/0] via 10.10.4.1, point2point
The sla is working.
asa# sh sla monitor operational-state
Entry number: 4
Modification time: 13:40:33.096 UTC Thu Jun 3 2021
Number of Octets Used by this Entry: 2056
Number of operations attempted: 2201
Number of operations skipped: 0
Current seconds left in Life: Forever
Operational state of entry: Active
Last time this entry was reset: Never
Connection loss occurred: FALSE
Timeout occurred: FALSE
Over thresholds occurred: FALSE
Latest RTT (milliseconds): 4
Latest operation start time: 19:47:13.209 UTC Thu Jun 3 2021
Latest operation return code: OK
RTT Values:
RTTAvg: 4 RTTMin: 1 RTTMax: 10
NumOfRTT: 3 RTTSum: 12 RTTSum2: 102
Basically, I need to do route tracking to test a few things but can't figure out why the route doesn't show in routing table.
Any idea why?
Thanks.
Solved! Go to Solution.
06-03-2021 01:39 PM
Hi,
Have you configured track? Because track doesn't mean SLA, so SLA 4 isn't automatically track 4 you would need to configure command like:
track [object-id] ip sla [operation] state
06-03-2021 01:39 PM
Hi,
Have you configured track? Because track doesn't mean SLA, so SLA 4 isn't automatically track 4 you would need to configure command like:
track [object-id] ip sla [operation] state
06-03-2021 02:09 PM
Thanks, I was missing this command track 4 rtr 4 reachability.
Your comment pointed me in the right direction though.
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