Wireless Access

Contributor I

VLAN Operational State

Aruba best practices state that VLANs should be configured to be up by using the "operstate up" command to change the protocol status to up.  Does anyone know the reasoning behind this?  I haven't been able to find any further documentation on this.

Re: VLAN Operational State


You use that command when you don't that VLAN tied to a port , usually people do this for guest VLAN hosted on the controller itself and is not tied to a trunk or access port on the controller

Thank you

Victor Fabian
Lead Mobility Architect @WEI
Trusted Contributor I

Re: VLAN Operational State

as for the reason, not 100% sure, might be to prevent odd effects with a network being down when there are no users in it.

Guru Elite

Re: VLAN Operational State

Normally when no there are no devices in a VLAN, the VLAN shuts down. This can happen on the controllers when you don't have an IP interface for that VLAN on the controller itself. Operstate up can help prevent the VLAN from shutting down.

| Tim Cappalli | Aruba Security | @timcappalli | timcappalli.me |

NOTE: Answers and views expressed by me on this forum are my own and not necessarily the position of Aruba or Hewlett Packard Enterprise.
Contributor I

Re: VLAN Operational State

Thanks cappalli, I know this keeps the VLANs that are not tied to an interface from shutting down.  What I was curious about was why this was an "Aruba Best Practice" since the VLAN immediately goes to an up state when a device joins.  Is this performance related, security related, etc.  Doesn't seem like anyone is sure of the reasoning behind this, and I can't find any Aruba documentation that explains this.

Search Airheads
Showing results for 
Search instead for 
Did you mean: