Aruba Admin Edge Port

Admin-edge-port just puts the port into forwarding immediately without going through the blocking stage of STP. BPDU-protection will disable the port as soon as it receives a BPDU, so you probably don't want to use that. Hello all, Can someone explain to me the equivalent configuration of the following commands on Cisco switches for the HP ProCurve switches? Interface range f0/1 spanning-tree portfast end copy run start. Every time a port changes state, STP will examine it for loops and redundant paths. Some port state changes are normal - PCs or printers going to sleep or being turned off, for example. At each port change, STP will shut down the port, send out BPDU frames, check with the other switches, re-calculate a path, and then enable the port.

Admin Edge Port Aruba
Aruba Admin Edge Port St Lucie
Aruba Admin Edge Port Ludlow

The Aruba 3810 switch series is equipped with HPE Smart Rate multi-gigabit ports for high-speed IEEE 802.11ac, suitable for enterprises, SMBs, and branch office networks. Interact with product animations in this online 3D model using simple gestures to explore the product. There is a issue that when clients come on they do not have network access. Reading around, this seems to be that SSDs boot SO fast that the network doesnt have time to calculate any conflicts with STP and turn the port on. Reading around, Ive seen something called 'Edge Port' (HP calls it like this) can be enabled.

Several access devices, such as APs and IP Phones, support LLDP and that is very convenient for discovery and troubleshooting. However, these devices may include the locally configured PVID (the untagged VLAN) in their outgoing LLDP frames. This may result in some warning log messages in the switch.While this feature is supposed to be good (detect a mismatch of the untagged/native VLAN/PVID on VLAN trunks between network devices), it does not provide the desired result with some APs.

Admin Edge Port Aruba

This is because the default management IP address that an AP has, could be bound to its internal VLAN 1. And since the AP uplink port is just an untagged port member of this VLAN 1 (locally on the AP), the AP would announce this VLAN 1 as the PVID in its outgoing LLDP frames (example for legacy Unified Wireless APs)

The uplink port may also just report VLAN ID 0 (sometimes referred to as the ‘untagged’ VLAN ID) in the outgoing LLDP frames. (example for Aruba APs)

Since the switch port connecting to the AP will have the port assigned as an access port (untagged) in the AP management VLAN, such as VLAN11, the switch will now complain with a log message that there is a PVID mismatch on the port to the AP (with either the local AP VLAN 1 or VLAN 0)

Example on Comware

Example on ArubaOS-Switch

Solution

When you have a situation that requires a different PVID (untagged VLAN) between 2 devices, just make sure that neither of the 2 devices is including the local PVID LLDP TLV in the outgoing announcement.

Aruba AP

LLDP on the AP is great, but the AP is not supposed to announce a PVID. When the PVID TLV is not present in the incoming LLDP frame, the switch will not complain (log) anymore.

On the Aruba controller, the AP LLDP profile can be set to not send out the pvid. The syntax is a bit strange. One would expect a ‘no dot1-tlvs port-vlan’ command, but the controller expects to get a ‘dot1-tlvs vlan-name’, which disables the other command option, that is the ‘port-vlan’ option. If that is what it expects, just do it..

Example LLDP peer state on an ArubaOS-Switch (Provision) before the change

And after the change was made on the Aruba Mobility Controller, the Pvid will be empty:

ArubaOS-Switch

In case you have a peer device of an ArubaOS-Switch that complains in its log, either:

Fix the PVID error
Disable the outgoing PVID announcement of the local device if this is the desired configuration.

Example for port 11

Note that this will not disable the LOG messages for incoming LLDP frames with a PVID mismatch!

Comware