Buy or Renew
Buy or Renew
Cisco + Splunk: It’s a new day for your data. Learn more.
 
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Start a conversation
3491
Views
0
Helpful
5
Replies

All IPv6 routes missing timestamps (IOS)

Go to solution
fsebera
Level 4
Level 4

‎01-11-2012 09:17 AM - edited ‎03-01-2019 05:31 PM

sh ipv6 route

:

shows all the v6 routes in the routing table, some from local interfaces, some from neighbors and still other routes redistributed

several hops away and none of the routes have timestamps.

:

Any ideas?

Tks

Frank

:

:

WAN4#sh ipv6 route

IPv6 Routing Table - 20 entries

Codes: C - Connected, L - Local, S - Static, R - RIP, B - BGP     

U - Per-user Static route      

I1 - ISIS L1, I2 - ISIS L2, IA - ISIS interarea, IS - ISIS summary     

O - OSPF intra, OI - OSPF inter, OE1 - OSPF ext 1, OE2 - OSPF ext 2    

ON1 - OSPF NSSA ext 1, ON2 - OSPF NSSA ext 2

B  ::/0 [20/0]    

     via FE80::222:90FF:FEB0:BE10, FastEthernet0/0.40

B  172:17:10::/126 [20/0]

     via FE80::222:90FF:FEB0:BE10, FastEthernet0/0.40

B  172:17:16::/126 [20/0]

     via FE80::222:90FF:FEB0:BE10, FastEthernet0/0.40

B  172:17:20::/126 [20/0]

     via FE80::222:90FF:FEB0:BE10, FastEthernet0/0.40

B  172:17:26::/126 [20/0]

     via FE80::222:90FF:FEB0:BE10, FastEthernet0/0.40

B  172:17:30::/126 [20/0]

     via FE80::222:90FF:FEB0:BE10, FastEthernet0/0.40

C  172:17:40::/126 [0/0]

     via ::, FastEthernet0/0.40

L  172:17:40::1/128 [0/0]

     via ::, FastEthernet0/0.40

B  172:18:250::/126 [20/0]

     via FE80::222:90FF:FEB0:BE10, FastEthernet0/0.40

B  2002:AC10:A03::1/128 [20/0]

     via FE80::222:90FF:FEB0:BE10, FastEthernet0/0.40

S  2608:300:4F:FE40::/58 [1/0]

     via ::, Null0

C  2608:300:4F:FE40::/64 [0/0]

     via ::, FastEthernet0/0.401

L  2608:300:4F:FE40::1/128 [0/0]

     via ::, FastEthernet0/0.401

LC  2608:300:4F:FE7F::F/128 [0/0]

     via ::, Loopback0

B  2608:300:4F:FEC0::/58 [20/0]

     via FE80::222:90FF:FEB0:BE10, FastEthernet0/0.40

B  2608:300:4F:FF40::/58 [20/0]

     via FE80::222:90FF:FEB0:BE10, FastEthernet0/0.40

B  2608:300:4F:FF80::/60 [20/0]

     via FE80::222:90FF:FEB0:BE10, FastEthernet0/0.40

B  2608:300:4F:FFC0::/58 [20/0]

     via FE80::222:90FF:FEB0:BE10, FastEthernet0/0.40

L  FE80::/10 [0/0]     via ::, Null0

L  FF00::/8 [0/0]     via ::, Null0

Labels:
0 Helpful
1 Accepted Solution

Accepted Solutions

Go to solution
stmillet
Cisco Employee
Cisco Employee
In response to fsebera

‎01-19-2012 01:25 AM

Frank,

Thanks to some internal feedback on this issue, I was made aware of the 'show ipv6 route updated' command. This does show a type of timestamp.

e.g.

C   2001:DB8:1:255::/127 [0/0]

     via Ethernet0/0, directly connected

      Last updated 04:24:44 13 January 2012     <== Here

L   2001:DB8:1:255::/128 [0/0]

     via Ethernet0/0, receive

      Last updated 04:24:45 13 January 2012

B   2001:DB8:2::/48 [20/0]

     via FE80::A8BB:CCFF:FE01:FF01, Ethernet0/0

      Last updated 04:26:30 13 January 2012

So if you are using the timestamp for debugging purposes or to identify route table chrun in IPv6 then the info is there, you just need to adapt any scripts or operational processes you are using for the new output.

I hope this helps,

Cheers

View solution in original post

0 Helpful
5 Replies 5

Go to solution
stmillet
Cisco Employee
Cisco Employee

‎01-17-2012 05:59 AM

Frank,

This is a known issue and is being tracked with the following Bug ID, CSCsh49409

You should be able to track this through Bug Toolkit http://www.cisco.com/go/bugs

Hope this helps

Stephan

0 Helpful

Go to solution
fsebera
Level 4
Level 4
In response to stmillet

‎01-18-2012 07:57 AM

Hey Stephan, Ahh the bug - thought I had missed this detail --all along for several years now. :) Thanks for clearing this up. I will research on the bug Id Thanks again Frank

0 Helpful

Go to solution
stmillet
Cisco Employee
Cisco Employee
In response to fsebera

‎01-19-2012 01:25 AM

Frank,

Thanks to some internal feedback on this issue, I was made aware of the 'show ipv6 route updated' command. This does show a type of timestamp.

e.g.

C   2001:DB8:1:255::/127 [0/0]

     via Ethernet0/0, directly connected

      Last updated 04:24:44 13 January 2012     <== Here

L   2001:DB8:1:255::/128 [0/0]

     via Ethernet0/0, receive

      Last updated 04:24:45 13 January 2012

B   2001:DB8:2::/48 [20/0]

     via FE80::A8BB:CCFF:FE01:FF01, Ethernet0/0

      Last updated 04:26:30 13 January 2012

So if you are using the timestamp for debugging purposes or to identify route table chrun in IPv6 then the info is there, you just need to adapt any scripts or operational processes you are using for the new output.

I hope this helps,

Cheers

0 Helpful

Go to solution
fsebera
Level 4
Level 4
In response to stmillet

‎01-20-2012 11:24 AM

Hey Stephan,

Thanks for the info about the sh ipv6 route updated command.

As it turns out, I always use the timestamps to look for routing loops ( sh ip ro bgp | i 00: ), it's very quick and this is how I noticed v6 didn't provide the much needed timestamps.

I updated to the latest IOS for the 1700 series routers (no change) The optional "updated" command is not available in this latest version. (Yea I know these routers are older but they still work well). IOS c1700-advipservicesk9-mz.124-25d.bin

I'm good on the 2800 series (even under the MPLS parameters)!

IOS c2800nm-advipservicesk9-mz.151-4.M3.bin

Regards

Frank

PE1#sh ipv6 route vrf HQI updated

IPv6 Routing Table - HQI - 16 entries

Codes: C - Connected, L - Local, S - Static, U - Per-user Static route

       B - BGP, HA - Home Agent, MR - Mobile Router, R - RIP

       I1 - ISIS L1, I2 - ISIS L2, IA - ISIS interarea, IS - ISIS summary

       D - EIGRP, EX - EIGRP external, ND - Neighbor Discovery, l - LISP

       O - OSPF Intra, OI - OSPF Inter, OE1 - OSPF ext 1, OE2 - OSPF ext 2

       ON1 - OSPF NSSA ext 1, ON2 - OSPF NSSA ext 2

B  ::/0 [20/0]

     via FE80::211:92FF:FEEC:A294, FastEthernet0/0.10

       Last updated 19:16:15 20 January 2012

C  172:17:10::/126 [0/0]

     via FastEthernet0/0.10, directly connected

       Last updated 18:50:06 20 January 2012

L  172:17:10::2/128 [0/0]

     via FastEthernet0/0.10, receive

       Last updated 18:50:07 20 January 2012

B  172:17:16::/126 [200/0]

     via 10.0.0.2%default, indirectly connected

       Last updated 19:00:52 20 January 2012

B  172:17:20::/126 [200/0]

     via 10.0.0.2%default, indirectly connected

       Last updated 19:00:52 20 January 2012

B  172:17:26::/126 [200/0]

----snip---

0 Helpful

Go to solution
fsebera
Level 4
Level 4
In response to stmillet

‎01-20-2012 12:42 PM

Hey,

Sometimes I am slow, sometimes I am even slower and still most other times I don’t even get it.

BUT, luckily I did get this one!

If you were to compare the v6 table to the v4 table you would start to see some really useful detail.

IPv4 route timestamps show how long the route has been stable basd on some random time ¿ in the past.

---Whereas---

IPv6 shows the actual date the route was updated, it shows stability from a specific date/time in history.

(I think) this is a really good feature.

PE1#sh ipv6 route vrf HQI updated

IPv6 Routing Table - HQI - 16 entries

B  ::/0 [20/0]

     via FE80::211:92FF:FEEC:A294, FastEthernet0/0.10

       Last updated 13:59:14 20 January 2012

----snip---

PE1#sh ip route vrf HQI

          Routing Table: HQI Gateway of last resort is 172.17.10.1 to network 0.0.0.0

B*    0.0.0.0/0 [20/0] via 172.17.10.1, 01:24:02

       172.16.0.0/16 is variably subnetted, 16 subnets, 3 masks

B        172.16.1.0/24 [20/2] via 172.17.10.1, 01:24:02

B        172.16.2.0/24 [200/2] via 10.0.0.2, 00:24:44

B        172.16.3.0/24 [200/0] via 10.0.0.3, 00:11:35

----snip----

0 Helpful
Customers Also Viewed These Support Documents