Reset Search
 

 

Article

Probe not causing VRRP fail over within the cofigured hellp timers

« Go Back

Information

 
TitleProbe not causing VRRP fail over within the cofigured hellp timers
Symptoms
  • Configured VRRP
  • Configured Probe
  • Pull two links removing the path of the probe
  • VRRP fail over takes longer than the configured VRRP advertisement interval
Environment
  • S-Series Firmware 8.62.01.0034
  • Summit 460 - G2 Firmware 22.3.1.4
Cause

In EOS
configure terminal
!
 interface vlan.0.2
  ip address 10.128.81.48 255.255.0.0 primary
  vrrp create 1 v3-IPv4
  vrrp address 1 10.128.83.1 
  vrrp critical-ip 1 10.21.10.2 40 remote probe-name CNI1 
  vrrp critical-ip 1 10.21.11.1 40 remote probe-name CNI1 
  vrrp advertise-interval 1 centiseconds 20
  vrrp enable 1
  no shutdown
  exit
 interface vlan.0.10
  ip address 10.21.10.4 255.255.255.0 primary
  no shutdown
  exit
 interface vlan.0.11
  ip address 10.21.11.4 255.255.255.0 primary
  no shutdown
  exit
!
 probe CNI1 icmp
  description "CNI1 Route Failure Detection"
  faildetect count 2 interval 2
  passdetect count 2 interval 4
  receive 2
  inservice
  exit
 
top7002(su-config)->probe asdf1 icmp
top7002(su-config-probe)->faildetect ?
  count                        Consecutive failed attempts to mark probe down
  interval                     Delay between probes to a service that is up
top7002(su-config-probe)->faildetect count 2 interval ?
  <2-300 seconds>              Delay between probes to a service that is up
top7002(su-config-probe)->faildetect count 2 interval


In EXOS
create vrrp vlan FDCN vrid 1
configure vrrp vlan FDCN vrid 1 advertisement-interval 20 centiseconds
configure vrrp vlan FDCN vrid 1 priority 120
configure vrrp vlan FDCN vrid 1 add 10.128.83.1
enable vrrp vlan FDCN vrid 1
configure vrrp vlan FDCN vrid 1 add track-ping  10.21.10.3 frequency 2 miss 2 success 2
configure vrrp vlan FDCN vrid 1 add track-ping  10.21.11.4 frequency 2 miss 2 success 2
 
X460G2 SW1 # configure vrrp vlan fdcn vrid 1 add track-
  track-iproute   track the status of an IP route
  track-ping      track the availability of an IP address via ping
  track-vlan      track the status of a VLAN
X460G2 SW461A.1 # configure vrrp vlan fdcn vrid 1 add track-ping 1.1.1.1 frequency ?
  <seconds>       value for the frequency. Range 1-600

So in both EOS and EXOS if the failover is due to VRRP not passing between Master and Backup the failover may be timed in centiseconds.  If the failover event is due to lost contact with the critical address via the probe, the time is in seconds based on the allowed frequency of the probes.
 
Resolution
This is Functioning as Designed currently
Additional notes

Feedback

 

Was this article helpful?


   

Feedback

Please tell us how we can make this article more useful.

Characters Remaining: 255