1/30/2020 · To return tagged VLANs to an Aruba switch, the HPE vendor specific attribute HPE-Egress-VLAN-ID or HPE-Egress-VLAN-Name is needed. If the VLAN names are not equal on every switch, the VLAN ID presents a good alternative. There are, however, a few steps we need to do before we can return the VLAN ID to the switch. Step by Step, 4/10/2018 · The HPE-Egress-VLAN-ID(64) and also the Tunnel-Private-Group ID which is typically used to return VLANs from the Radius Server. We have tested this with Clearpass version 6.6.9 and an Aruba-2930F running WC.16.04.0011 but this should also work with other firmware versions on the switch and CPPM as long as you are returning the attributes in the right format.
7/11/2016 · 2. For IETF Egress-VLANID (56), HP documentation says The value of Egress-VLANID is a bit string, the first 8 bits specify whether the VLAN is tagged or untagged and must be either 0x31 (tagged) or 0x32 (untagged). The next 12 bits are padding 0x000, and the final 12 bits are the VLAN ID as an integer value.
4/16/2020 · To return tagged VLANs to an Aruba switch, the HPE vendor specific attribute HPE-Egress-VLAN-ID or HPE-Egress-VLAN-Name is needed.If the VLAN… Continue Reading ? Posted in: Aruba , ArubaOS , ClearPass , RADIUS Filed under: Aruba , ArubaOS , ClearPass , HPE , RADIUS
