VRRP

[Brad_199]

Testing 2 x 5406's in a lab with a few VLAN's.  VRID's configured for each VLAN.

VLAN 1 Virtual IP = 192.168.1.254

Primary core switch VLAN 1 IP = 192.168.1.254

Backup core switch VLAN 1 IP = 192.168.1.253

DHCP server's scope for VLAN 1 assigns client devices gateway to 192.168.1.254

I've noticed that if a laptop or client workstation is plugged into the backup core switch; it can still reach off site networks despite it's gateway IP being the primary core switch (192.168.1.254)

I wasn't expecting that behaviour as the backup core switch is effectively sitting idle (I thought?)

VRRP config commands on each switch verified that the owner for VLAN 1 is the primary switch.

Is this normal behaviour?

[Vince-Whirlwind]

That's exactly why you want VRRP.

The master "owns" the .254 address and does all the routing. The backup is functioning as a layer2 switch.

It wouldn't be any good if devices patched into the "backup" couldn't reach their default GW, would it?

[Brad_199]

Thanks Vince.

I overlooked the fact its L3 redundancy and was thinking of it like an active/standby setup