CSS WEBNS 7.4 critical reporters

Question

Hi,
I've two CSS configured to run VIP-Redundancy. To cover critical phy outage I configured a reporter type all-phy-up. This works fine, both VR (one in front of the CSS and one behind - as this is inline configuritation) are changing the status if one of the links fails. But, if let's say the link in front of the CSS recovers the VR behind of CSS swaps back (preemption is configured) but the VR in front needs some time due to the VRRP-Timers. That's fine so far. Therefore I configured a second critical service VRID-Peering (2 reporters in each circuit) and tried the same. I found out, that the fall back is not working neverthess preemption is still configured. In other words VR are changing if a link fails but do not swap back to the wanted position after the link recovers. I did not find any explanation why this is happening or what I'm doing wrong.
Any advices is appreciated.
TIA.
Kind Regards,
Joerg

Answer 1

Hi Gilles,
Thanks for your reply. Spanning-Tree is out of the game . The problem is that the VR remains on the original backup CSS and does not return to the active one. I waited for almost 5 minutes and it did not return.
The config looks like this:
circuit VLAN30 /VLAN3 (in VLAN3 is VRID 3)
description "to backbone eFCS"
ip address 10.242.8.41 255.255.255.240
ip virtual-router 30 priority 180 preempt
ip redundant-interface 30 10.242.8.43
ip redundant-vip 30 10.242.8.33
ip critical-reporter 30 eFCS
ip critical-reporter 30 eFCS-VRRP
reporter eFCS
type critical phy-all-up
reporter eFCS
type vrid-peering and the VRIP settings
The reporters are only configured on the active CSS (guess this should be okay).
Kind Regards,
Joerg