09-29-2014 02:57 AM
Hi,
Got some issues with IPSLA/Track on ASR100v ver. 5.2.0. The IPSLA seems to work:
RP/0/0/CPU0:XRv2#show ipsla statistics Mon Sep 29 09:43:36.777 UTC Entry number: 1 Modification time: 09:37:01.893 UTC Mon Sep 29 2014 Start time : 09:37:01.913 UTC Mon Sep 29 2014 Number of operations attempted: 6 Number of operations skipped : 1 Current seconds left in Life : Forever Operational state of entry : Active Operational frequency(seconds): 60 Connection loss occurred : FALSE Timeout occurred : FALSE Latest RTT (milliseconds) : 1 Latest operation start time : 09:43:02.149 UTC Mon Sep 29 2014 Next operation start time : 09:44:02.149 UTC Mon Sep 29 2014 Latest operation return code : OK RTT Values: RTTAvg : 1 RTTMin: 1 RTTMax : 1 NumOfRTT: 1 RTTSum: 1 RTTSum2: 1
But TRACKing doesnt:
RP/0/0/CPU0:XRv2#show track track1 Mon Sep 29 09:44:34.733 UTC Track track1 Response Time Reporter 1 reachability ipsla operation not in progress RP/0/0/CPU0:XRv2#show track track1 bri Mon Sep 29 09:44:38.782 UTC Track Object Parameter Value -------------------------------------------------------------------------------------------------------- track1 IPSLA Operation 1 reachability Down RP/0/0/CPU0:XRv2#
And the debug info:
RP/0/0/CPU0:Sep 29 09:37:24.112 : object_tracking[318]: Entering (handle_ot_mgd_timer_expired) : RP/0/0/CPU0:Sep 29 09:37:24.112 : object_tracking[318]:(handle_ot_mgd_timer_expired) : RTR_SHM_POLL_INTERVAL expired RP/0/0/CPU0:Sep 29 09:37:24.112 : object_tracking[318]: RTR_SHM_POLL_INTERVAL timer triggered for track : track1 RP/0/0/CPU0:Sep 29 09:37:24.112 : object_tracking[318]: Entering(ot_rtr_read_shm_after_timer_expired) : RP/0/0/CPU0:Sep 29 09:37:24.112 : object_tracking[318]: (ot_rtr_read_shm_after_timer_expired) : track_name = track1 RP/0/0/CPU0:Sep 29 09:37:24.112 : object_tracking[318]: Entering (hash_db_get_track_item) : RP/0/0/CPU0:Sep 29 09:37:24.112 : object_tracking[318]: Entering (stop_ot_timer) : RP/0/0/CPU0:Sep 29 09:37:24.112 : object_tracking[318]: Entering (shm_read_ipsla_stats) : RP/0/0/CPU0:Sep 29 09:37:24.112 : object_tracking[318]: Entering (track_rtr_init) : RP/0/0/CPU0:Sep 29 09:37:24.112 : object_tracking[318]: Failed to initialize ipsla shared mem RP/0/0/CPU0:Sep 29 09:37:24.112 : object_tracking[318]: Corresponding ipsla operation with op id 1 is not running RP/0/0/CPU0:Sep 29 09:37:24.112 : object_tracking[318]: latestReturnCode = 0, latestResponseTime = 0 RP/0/0/CPU0:Sep 29 09:37:24.112 : object_tracking[318]: Entering (object_tracking_set_track_state_in_sysdb) : RP/0/0/CPU0:Sep 29 09:37:24.112 : object_tracking[318]: (object_tracking_set_track_state_in_sysdb) : track track1 state Unknown RP/0/0/CPU0:Sep 29 09:37:24.112 : object_tracking[318]: Entering (hash_db_get_track_item) : RP/0/0/CPU0:Sep 29 09:37:24.112 : object_tracking[318]: (object_tracking_set_track_state_in_sysdb) : track track1 sysdb state Unknown RP/0/0/CPU0:Sep 29 09:37:24.112 : object_tracking[318]: Entering (get_timer_ctx) : RP/0/0/CPU0:Sep 29 09:37:24.112 : object_tracking[318]: Entering (stop_ot_timer) : RP/0/0/CPU0:Sep 29 09:37:24.112 : object_tracking[318]: Entering (get_timer_ctx) : RP/0/0/CPU0:Sep 29 09:37:24.112 : object_tracking[318]: Entering (set_ot_shm_poll_wait_timer) : RP/0/0/CPU0:Sep 29 09:37:24.112 : syslog_dev[70]: object_tracking[318]: Unable to find window ipsla_ot
All states under for tracking under VRRP/ROUTE shows that tracked object is DOWN. This was the same as for 5.1.1
10-10-2014 06:39 AM
can you share your ipsla config please, I would like to see what you are tracking.
there is a known DDTS that tracks the requirement of route reachability verification that you may be hitting: CSCua95880
xander
10-17-2014 01:08 AM
Thank you xander,
here is the cfg you requested:
10-17-2014 04:58 AM
thanks for that config. I used it in my setup to verify ifs and hows.
I am running XR 512 on real hardware (I think you have an XRv there based on the name right?) and I was hoping to see the problem, but it worked straight up for me!
RP/0/RSP0/CPU0:A9K-BNG#show vrrp
Fri Oct 17 07:46:38.677 EDT
IPv4 Virtual Routers:
A indicates IP address owner
| P indicates configured to preempt
| |
Interface vrID Prio A P State Master addr VRouter addr
Gi0/0/0/0.10 10 95 P Master local 192.168.10.10
RP/0/RSP0/CPU0:A9K-BNG#RP/0/RSP0/CPU0:Oct 17 07:47:22.713 : object_tracking[356]: %SERVICES-OT-6-TRACK_INFO : track TRACK_ICMP state Track_Up
I can bring it down by removing the probe host:
RP/0/RSP0/CPU0:A9K-BNG#RP/0/RSP0/CPU0:Oct 17 07:46:08.650 : object_tracking[356]: %SERVICES-OT-6-TRACK_INFO : track TRACK_ICMP state Track_Down
That means to me that it is either one of the 3 things:
you are running into a bug in the XRv code that you have, or XRv has a deficiency in relation to running vrrp with ipsla probes or maybe the pinged/probed host configured is not reachable from inside the Xrv?
Any case, the config is good.
I would recommend playing with a different version maybe if possible and meanwhile I'll check if this can be run on Xrv in general.
Also run the VRRP on a signle node and see if that makes a difference whether the VRRP is messing up the probe, dunno but worth the try.
regards
xander
10-20-2014 01:19 AM
We have also XR 5.1.2 on ASR9001, the config works on that device but only for the first time after you assign tracking object to VRRP instance.
The ouput:
RP/0/RSP0/CPU0:ASR9001#sho vrrp det
Thu Oct 9 07:45:51.859 UTC
Bundle-Ether3.11 - IPv4 vrID 11
State is Master
9 state changes, last state change 6d22h
State change history:
Sep 29 15:32:45.980 UTC Init -> Backup Delay timer expired
Sep 29 15:32:49.570 UTC Backup -> Master Master down timer expired
Sep 29 16:16:18.939 UTC Master -> Init Interface Down update
Oct 2 09:04:59.379 UTC Init -> Backup Delay timer expired
Oct 2 09:05:02.971 UTC Backup -> Master Master down timer expired
Last resign sent: Sep 29 16:16:18.941 UTC
Last resign received: Never
Virtual IP address is X.X.X.X
Virtual MAC address is 0000.5E00.010b, state is active
Master router is local
Version is 2
Advertise time 1 secs
Master Down Timer 3.589 (3 x 1 + (151 x 1/256))
Minimum delay 1 sec, reload delay 5 sec
Current priority 105
Configured priority 105, may preempt
minimum delay 180 secs
Authentication enabled, string "11"
Tracked items: 1/1 up: 0 decrement
Object name State Decrement
TRACK_OBJECT Up 10
!
RP/0/RSP0/CPU0:ASR9001#show track TRACK_OBJECT
Thu Oct 9 07:46:44.946 UTC
Track TRACK_OBJECT
Response Time Reporter 253 reachability
2 changes, last change 07:45:40 UTC Thu Oct 09 2014
Latest operation return code: SockBindError
Latest RTT (millisecs) : 0
!
RP/0/RSP0/CPU0:ASR9001#sho ipsla statistics 253
Thu Oct 9 07:46:28.506 UTC
Entry number: 253
Modification time: 07:41:27.301 UTC Thu Oct 09 2014
Start time : 07:41:27.309 UTC Thu Oct 09 2014
Number of operations attempted: 250
Number of operations skipped : 52
Current seconds left in Life : Forever
Operational state of entry : Active
Operational frequency(seconds): 1
Connection loss occurred : FALSE
Timeout occurred : FALSE
Latest RTT (milliseconds) : Unknown
Latest operation start time : 07:46:28.310 UTC Thu Oct 09 2014
Next operation start time : 07:46:29.310 UTC Thu Oct 09 2014
Latest operation return code : SockBindError
RTT Values:
RTTAvg : 0 RTTMin: 0 RTTMax : 0
NumOfRTT: 0 RTTSum: 0 RTTSum2: 0
If you assign the tracking object for VRRP when the destination of ipsla is unreachable, it will be marked as down and wont change even if tracking will be recovered ;]
5.1.2 with no Service Packs, don't have access to downloads yet.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: