Ok, got it, that works unfortunately the data has rolled so if I’ll keep it up my sleeve to do this if it happens again…
Scott H Login, LLC > On Apr 22, 2018, at 7:57 PM, Khan Muddassir <[email protected]> wrote: > > Hi Scott, > the command looks to be "sho ip ospf statis", I wrongly typed the database. > https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/iproute_ospf/command/iro-cr-book/ospf-s1.html#wp3494003981 > > <https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/iproute_ospf/command/iro-cr-book/ospf-s1.html#wp3494003981> > > -muddassir > > On Sun, Apr 22, 2018 at 11:23 PM, Scott Harvanek <[email protected] > <mailto:[email protected]>> wrote: > Muddasir; > > Unfortunately I do not, the statistics command does not seem to exist; > > sh ip ospf database statistics > ^ > % Invalid input detected at '^' marker. > > sh ip ospf database ? > adv-router Advertising Router link states > asbr-summary ASBR summary link states > database-summary Summary of database > external External link states > internal Internal LSA information > multicast Multicast Topology > network Network link states > nssa-external NSSA External link states > opaque-area Opaque Area link states > opaque-as Opaque AS link states > opaque-link Opaque Link-Local link states > router Router link states > self-originate Self-originated link states > summary Network summary link states > topology Unicast Topology > > Scott H > > > >> On Apr 21, 2018, at 12:01 PM, Khan Muddassir <[email protected] >> <mailto:[email protected]>> wrote: >> >> Redistributing via ospf xxxxx >> >> do you have the output of the OSPF db from the 6500's? specifically "sho ip >> ospf data self-originate"? did the 6500's themselves update their db after >> track 5 went down? "sho ip ospf data statistics" should also help track if >> there was a change in lsdb which would ideally match the outage time. >> >> On Fri, Apr 20, 2018 at 10:52 PM, Scott Harvanek <[email protected] >> <mailto:[email protected]>> wrote: >> I’ve encountered an odd routing issue and I’m hoping it’s a simple >> configuration issue and not a Bug, looking for input on this please :) >> >> Equipment: Cisco 6500E series w/ SUP720 MSFC3/PFC3 >> Software: 15.1(2)SY10, RELEASE SOFTWARE (fc4) ADV IP Services >> >> Scenario; >> We have a pair of the above software/hardware combinations, providing HSRP >> to another device. A /29 is used as the link network/HSRP and there are >> subnets then routed to the far side in each 6509E. We are using IP SLA >> reachability tracking to activate/deactivate routes; >> >> Tracking configuration; >> track 5 ip sla 5 reachability >> ip sla 5 >> icmp-echo <MY DESTINATION> source-ip <MY SOURCE> >> threshold 2 >> timeout 1000 >> frequency 3 >> ip sla schedule 5 life forever start-time now >> >> ip route x.x.x.x 255.255.255.224 <MY DESTINATION> track 5 >> ip route x.x.x.x 255.255.255.248 <MY DESTINATION> track 5 >> >> This is all works fine however, the far side router briefly stopped >> responding or a reachability issue occurred; >> >> Apr 19 21:45:13.771: %TRACKING-5-STATE: 5 ip sla 5 reachability Up->Down >> Apr 19 21:45:18.771: %TRACKING-5-STATE: 5 ip sla 5 reachability Down->Up >> >> When this occurred, the routes were no longer being announced even after >> recover HOWEVER the router (6509E) thought they were; >> >> TUSLDC2.C6509E.1# sh ip route x.x.x.x >> Routing entry for x.x.x.x/27 >> Known via "static", distance 1, metric 0 >> Redistributing via ospf xxxxx >> Advertised by ospf xxxxx subnets >> Routing Descriptor Blocks: >> * <MY DESTINATION> >> Route metric is 0, traffic share count is 1 >> >> However, none of the other OSPF neighbors saw this route announcement, upon >> removing the static routes and re-applying them the announcement was then >> visible again… no other changes were made; >> >> no ip route x.x.x.x 255.255.255.224 <MY DESTINATION> track 5 >> no ip route x.x.x.x 255.255.255.248 <MY DESTINATION> track 5 >> ip route x.x.x.x 255.255.255.224 <MY DESTINATION> track 5 >> ip route x.x.x.x 255.255.255.248 <MY DESTINATION> track 5 >> >> What am I doing wrong or, is this a bug/known behavior? >> >> -Scott H >> >> >> >> _______________________________________________ >> cisco-nsp mailing list [email protected] >> <mailto:[email protected]> >> https://puck.nether.net/mailman/listinfo/cisco-nsp >> <https://puck.nether.net/mailman/listinfo/cisco-nsp> >> archive at http://puck.nether.net/pipermail/cisco-nsp/ >> <http://puck.nether.net/pipermail/cisco-nsp/> >> >> >> >> -- >> Thanks & Regards, >> Muddasir Khan > > > > > -- > Thanks & Regards, > Muddasir Khan _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
