VRRP on 3500

[Jaguar]

Hi,
I'm having a little difficulty here. I have 2 units of ProCurve 3500 with a ProCurve 2626. The 2626 (VLAN100 tagged port 1 & 2) are connected to the 3500 (VLAN100 tagged port 1 on both units). My PC connects to 2626 at port 3 untagged VLAN 100, and its default gateway points to the virtual-ip-address of 10.10.8.1 (pls see attach config).
I ping 10.10.8.1 when both units are working. No issue. When I power down the Owner, the Backup took over but instead of using the virtual-ip-address, it used its own physical IP address (which is 10.10.8.3). Any idea what have I missed out?

[Matt Hobbs]

To me your config looks right. The post below also sounds like the same issue you're seeing:

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=1029371

K.11.33 is out now, although there are no VRRP listed fixes in there, I'd recommend you try it just in case as sometimes unlisted bugs are fixed. (If you're not already running it).

If you're still having the same problem, contact HP support and let us know how you go. Have 'show tech all' reports from the switch ready and any of the show vrrp commands too should help.

[Mohieddin Kharnoub]

HI Jaguar

Can you show us the output of:

show vrrp vlan 100 vrid 1 config

Thanks !

[tomastomas]

Hello,
this is known inconvenience of VRRP standard. If owner is down, you can never ping that ip address, but backup switch will definately work as a default gateway. So only thing is, that since physical interface with IP 10.10.8.1 is down, no interface will respond, but redundancy works just fine !

This is caused by standard, sorry :)

[Matt Hobbs]

Thanks tomastomas, you learn something new everyday..

Jaguar:

http://www3.ietf.org/proceedings/98aug/98aug-111.htm

The question of whether or not a VRRP backup (which has become master) should
respond to ping. It was noted this is confusing for customers if they cannot ping the router even though it is forwarding traffic. Much discussion ensued. The benefits of not responding are it makes a down owner noticeable by network management. The default behavior should be not to respond (although specific implementations may implement a switch).

Don't forget to assign points.

[Domenico Viggiani]

Hi,
I'm experiencing this kind of problem too. I configured two ProCurve 8212zl switches with VRRP (with more than one vlan) and I've got the same problem. If I ping the virtual ip address (eg. 10.63.1.254) it works only if the owner remanis UP. If I power it down I don't get any response by ping of virtual ip address.
The "sh vrrp vlan 4 statistics" commmand on the back up VR shows this:

VRRP Virtual Router Statistics Information

Vlan ID : 4
Virtual Router ID : 4
State : Master
Up Time : 62 mins
Virtual MAC Address : 00005e-000104
Master's IP Address : 10.63.1.253
Associated IP Addr Count : 1 Near Failovers : 4
Advertise Pkts Rx : 3671 Become Master : 1
Zero Priority Rx : 0 Zero Priority Tx : 0
Bad Length Pkts : 0 Bad Type Pkts : 0
Mismatched Interval Pkts : 0 Mismatched Addr List Pkts : 0
Mismatched IP TTL Pkts : 0 Mismatched Auth Type Pkts : 0

Is it the same problem?
Thanks