Hi,
I'm sorry, but we had to reboot the switch to make progress this evening (in Europe). 😞
Anyway, routing was fine, I could ping all switch IP addresses from my notebook, and from the neighbor switch with the active VRRP address.
The VLAN I wanted to start VRRP on was shown as directly connected, route up (U) and installed in forwarding table (f). I did see ARP entries in this VLAN. I could ping IP addresses in this VLAN from the switch.
The VRRP is run via an EAPS ring. The switch is a transit node for the EAPS ring in question. The EAPS ring was complete. There are additonal EAPS domains on that switch.
The VRRP MAC was shown in the FDB on the port it had to be. I could ping the virtual and physical addresses of the neighboring VRRP peer, and that switch could ping the physical address of the problem stack in the problematic VLAN. The neighbor switches showed the correct MAC address on the port as well.
The VLAN showed two active ports, the two ring ports.
The reboot proved problematic, too. The switch lost its RADIUS configuration, and it blocked the secondary port on a complete EAPS ring it is transit node for. Disabling a different EAPS domain, transit node as well, sharing the same ports but no VLANs, with that ring incomplete, unblocked the secondary port in the complete EAPS ring.
The situation is stable, I will probably open a case (or two) tomorrow. I have saved a show tech-support from before the reboot.
If you have any ideas or speculations what could have caused the problem (any of those described above), feel free to post them.
Thanks again,
Erik