problem with track command with SAA

Answered Question
Sep 3rd, 2009
User Badges:

Hi


I am getting the following error exactly after 1 minute on my router when I am giving the command sh track 1 whose output is


RGGNHILINET002#sh track 1

Track 1

Response Time Reporter 4 reachability

Reachability is Down

389340 changes, last change 00:00:00

Latest operation return code: Timeout

Tracked by:

HSRP Vlan1 40


Because of this my HSRP IP is getting changes simultaneously. Can somebody help me over it?

Correct Answer by Jon Marshall about 7 years 8 months ago

Can you post config of 3845.


Can you post "sh ip route" of 3845.


Is there any chance that your pings or whatever you are using for reachability are getting lost or are getting dropped due to not enough bandwidth.


Also have you tried increasing the timeout on the IP SLA ping ?


Finally, are you sure the device you are pinging is not so busy it is not responding in the timeout or indeed it is just dropping out and then coming back ?


Jon

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
Jon Marshall Thu, 09/03/2009 - 03:28
User Badges:
  • Super Blue, 32500 points or more
  • Hall of Fame,

    Founding Member

  • Cisco Designated VIP,

    2017 LAN, WAN

Not really enough information here.


What type of device are you doing this on.

When it reports a timeout have you tried a ping from the device to see if the destination is actually down.

Does it keep bouncing ie. it reports down, then reports up ?


Could we see the config and a quick topology so we can help you out ?


Jon

pranuvpandit Thu, 09/03/2009 - 03:59
User Badges:

This is 3845 router. The device is not actually down..I have checked it and yeah it does keep bouncing. Please let me know...what sh commands output you need?

Correct Answer
Jon Marshall Thu, 09/03/2009 - 04:06
User Badges:
  • Super Blue, 32500 points or more
  • Hall of Fame,

    Founding Member

  • Cisco Designated VIP,

    2017 LAN, WAN

Can you post config of 3845.


Can you post "sh ip route" of 3845.


Is there any chance that your pings or whatever you are using for reachability are getting lost or are getting dropped due to not enough bandwidth.


Also have you tried increasing the timeout on the IP SLA ping ?


Finally, are you sure the device you are pinging is not so busy it is not responding in the timeout or indeed it is just dropping out and then coming back ?


Jon

pranuvpandit Sun, 09/06/2009 - 00:41
User Badges:

Thanks Jon ..it is working now.. I have increased the timeout for IP SLA. After monitoring for 30 minutes I observed that regulary after 1 or 2 minutes the RTT was reaching upto 240 ms. But in our configuration it was configured as 10 ms. Increased it to upto 300 ms. Now it is working fine.

Actions

This Discussion