[c-nsp] FW: ios xr - asr9k - object tracking route reachability

[Aaron]

i'm trying to track the existence of a route in the vrf "oneone" routing
table.... why is the "show track" showing that it is looking for it in the
vrf "default" ?

RP/0/RSP0/CPU0:9k#sh run track mylist1

Tue Apr 16 12:33:21.328 CDT

track mylist1

type list boolean and

  object track-a-route

!

delay up 10

!

RP/0/RSP0/CPU0:9k#sh run track track-a-route

Tue Apr 16 12:33:27.775 CDT

track track-a-route

type route reachability

  vrf oneone

  route ipv4 10.101.14.20/30

!

delay up 10

!

RP/0/RSP0/CPU0:9k#sh track

Tue Apr 16 12:33:33.285 CDT

Track mylist1

        List boolean and is DOWN

        1 change, last change 11:56:10 CDT Tue Apr 16 2013

                object track-a-route DOWN

Track track-a-route

        Ip route 10.101.14.20 255.255.255.252 reachability ip vrf default

        Reachability is DOWN

        2 changes, last change 12:33:01 CDT Tue Apr 16 2013

RP/0/RSP0/CPU0:9k#

 

RP/0/RSP0/CPU0:9k#sh route vrf oneone

Tue Apr 16 12:31:55.194 CDT

Codes: C - connected, S - static, R - RIP, 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, E - EGP

       i - ISIS, L1 - IS-IS level-1, L2 - IS-IS level-2

       ia - IS-IS inter area, su - IS-IS summary null, * - candidate default

       U - per-user static route, o - ODR, L - local, G  - DAGR

       A - access/subscriber, (!) - FRR Backup path

Gateway of last resort is not set

C    10.101.14.20/30 is directly connected, 01:19:40,
GigabitEthernet0/0/0/10

L    10.101.14.21/32 is directly connected, 01:19:40,
GigabitEthernet0/0/0/10

RP/0/RSP0/CPU0:9k#

 

 

From: Aaron [mailto:aaron1 at gvtc.com] 
Sent: Tuesday, April 16, 2013 11:46 AM
To: cisco-nsp at puck.nether.net
Subject: ios xr - asr9k - object tracking route reachability

 

why do I get a failure on the config BUT it still allows me to exit the
config  as if it was commited, and sh run proves it's there.  I thought a
failure upon commit caused configuration to NOT be committed.

 

 

RP/0/RSP0/CPU0:9k#sh run track track-default-route

Tue Apr 16 11:41:18.821 CDT

% No such configuration item(s)

 

RP/0/RSP0/CPU0:9k#

RP/0/RSP0/CPU0:9k#conf

Tue Apr 16 11:41:28.966 CDT

RP/0/RSP0/CPU0:9k(config)#track track-default-route

RP/0/RSP0/CPU0:9k(config-track)# type route reachability

RP/0/RSP0/CPU0:9k(config-track-route)#  vrf oneone

RP/0/RSP0/CPU0:9k(config-track-route)#  route ipv4 0.0.0.0/0

RP/0/RSP0/CPU0:9k(config-track-route)#exit

RP/0/RSP0/CPU0:9k(config-track)#delay up 10

RP/0/RSP0/CPU0:9k(config-track)#commit

Tue Apr 16 11:41:32.446 CDT

 

% Failed to commit one or more configuration items. Please issue 'show     

configuration failed' from this session to view the errors

 

RP/0/RSP0/CPU0:9k(config-track)#

 

RP/0/RSP0/CPU0:9k#sh run track track-default-route

Tue Apr 16 11:41:42.273 CDT

track track-default-route

type route reachability

vrf oneone

  route ipv4 0.0.0.0/0

!

delay up 10

!

 

 

Aaron