Wireless Access

I have a mobility master using an access port, which is therefore vlan 1 from the perspective of the MM. It doesn't seem to be possible to configure VRRP on vlan 1. The GUI complains about using vlan1 (only vlan there is) the CLI does not. But it doesn't work. The MM can ping itself on the VRRP address, but nothing else can.

I've found documentation, albeit from an earlier version of AOS8, that shows vlan1 being used.https://www.arubanetworks.com/techdocs/ArubaOS_81_Web_Help/Content/ArubaFrameStyles/VRRP/Redundancy_Parameters.htm

I've used
vrrp 88
ip address <ip>

authentication <password>
vlan 1
no shutdown

Should this work?

VMM

Hi Matthew Seymour,

using VMM I setup MM-redundancy with VLAN id 1 and I verified failover while rebooting the primary MM as well.

see the below configuration screenshots and CLI outputs.

Yep, I've done exactly that... Just doesn't work.

here are the settings I'm using for the vrrp.

On submit I get a warning the vlan is invalid. The config will apply, and I can see it in the CLI - all looks fine, but it doesn't work. The VRRP address exists in the box (so to speak) the MM can ping itself on that address, but it doesn't get attached to the vlan and make it onto the wire.

This must be something to do with the network setup for the MM, that I've done wrong... but I don't know what. 

can you check VLAN tag id in mgmt interfaces?

And which AOS version are you using?

Hi Mathew,

It seems like a warning. Try deploying the changes and then check if VRRP is up or not?

Yeah, this thread is because it doesn't work. 

The VRRP IP is pingable from the MM itself, but it doesn't make it out onto the wire.

FOUND IT!!!!!!

It looks like the warning is incorrect. That's what threw me.

The problem is our VM infrastructure has promiscuous mode denied. Hadn't twigged this because I don't get to setup anything on VMware.

Thanks all

I'm getting the same warning invalid vlan with  hardware mobility masters not using vlan 1 either. I have one vlan created for the controller IP of each MM and the controller IP is in /24 different IP's. I still get this warning the vlan is trunked though a port channel I'm using ports 0 and 1. 

That doesn't seem related to the Op's VM issue.  I would open a separate thread with your specific details.