Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

problem with track command with SAA

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?

1 ACCEPTED SOLUTION

Accepted Solutions
Hall of Fame Super Blue

Re: problem with track command with SAA

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

4 REPLIES
Hall of Fame Super Blue

Re: problem with track command with SAA

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

New Member

Re: problem with track command with SAA

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?

Hall of Fame Super Blue

Re: problem with track command with SAA

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

New Member

Re: problem with track command with SAA

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.

157
Views
0
Helpful
4
Replies