SRST coming on too soon.

Unanswered Question
Mar 14th, 2008
User Badges:
  • Bronze, 100 points or more

CM4.2.3sr1 (pub/sub only) - We have 2 sites (Calif and NJ). According to our design, NJ should not go into SRST mode with our MPLS (primary link) and VPN redundancy (secondary line), the logs show the following:


Mar 14 09:27:47.477: %OSPF-5-ADJCHG: Process 1, Nbr 10.254.1.3 on GigabitEthernet0/1 from 2WAY to DOWN, Neighbor Down: Dead timer expired

Mar 14 09:27:47: %OSPF-5-ADJCHG: Process 1, Nbr 10.3.10.252 on Tunnel0 from FULL to DOWN, Neighbor Down: Dead timer expired<---------------Both WAN/VPN went down at 9:27.

Mar 14 09:28:30: %OSPF-5-ADJCHG: Process 1, Nbr 10.3.10.252 on Tunnel0 from LOADING to FULL, Loading Done<------After 43secs, VPN re-established with OSPF convergence ONLY on VPN.

Mar 14 09:37:11.214: %OSPF-5-ADJCHG: Process 1, Nbr 10.254.1.3 on GigabitEthernet0/1 from LOADING to FULL, Loading Done<---8min later, WAN came up so WAN should take precedence

Mar 14 09:42:07: %OSPF-5-ADJCHG: Process 1, Nbr 10.3.10.252 on Tunnel0 from FULL to DOWN, Neighbor Down: Dead timer expired<---5min later, VPN died

Mar 14 09:43:47: %OSPF-5-ADJCHG: Process 1, Nbr 10.3.10.252 on Tunnel0 from LOADING to FULL, Loading Done

Mar 14 11:43:47.575: %OSPF-5-ADJCHG: Process 1, Nbr 10.116.1.252 on Tunnel0 from LOADING to FULL, Loading Done<---40sec later, VPN came up

Mar 14 09:46:57.456: %OSPF-5-ADJCHG: Process 1, Nbr 10.254.1.3 on GigabitEthernet0/1 from FULL to DOWN, Neighbor Down: Dead timer expired<---3min later, WAN died so VPN takes precedence

Mar 14 09:48:17.728: %OSPF-5-ADJCHG: Process 1, Nbr 10.254.1.3 on GigabitEthernet0/1 from LOADING to FULL, Loading Done<---1min later, WAN came up.

Mar 14 11:50:10.232: %OSPF-5-ADJCHG: Process 1, Nbr 10.116.1.252 on Tunnel0 from FULL to DOWN, Neighbor Down: Dead timer expired

Mar 14 11:50:20.508: %OSPF-5-ADJCHG: Process 1, Nbr 10.116.1.252 on Tunnel0 from LOADING to FULL, Loading Done

Mar 14 09:50:20: %OSPF-5-ADJCHG: Process 1, Nbr 10.3.10.252 on Tunnel0 from LOADING to FULL, Loading Done.

Mar 14 09:51:50.986: %OSPF-5-ADJCHG: Process 1, Nbr 10.254.1.3 on GigabitEthernet0/1 from LOADING to FULL, Loading Done <----------2-3min later, both WAN/VPN came up


Per cisco documentation:

OSPF uses failure to receive hello packets from its neighbors for dead-interval time. After dead-interval if brings down the neighbor relationship and withdraws all the routes learnt from the neighbor. Currently, we are at Hello interval is 10 secs and the Dead interval is 40 secs.

Typically, it takes three times the keepalive period for a phone to discover that its connection to Cisco CallManager has failed. The default keepalive period is 30 seconds. If the phone has an active standby connection established with a Cisco SRST router, the fallback process takes 10 to 20 seconds after connection with Cisco CallManager is lost. The typical fallback to the SRST is can take approximately 2.5 minutes while the default time that Cisco IP phones wait before attempting to reestablish a connection to a remote Cisco CallManager is 120 seconds (2min)


Anyway to find out why SRST is coming on soon.


  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.

Actions

This Discussion