Aruba APs expect the switch port to supply 802.3at/af/BT PoE, receive their own IP address on the untagged management VLAN, and deliver user traffic in tagged client / guest VLANs.

The only option that

1) makes the port a trunk with native (untagged) VLAN 100,

2) explicitly permits VLANs 100, 200 and 300 on the trunk, and

3) enables PoE for the port(s)

is option C.

Because cables are not labeled and the installer is un-trained, LLDP-based device-profile automation in the template binds the configuration automatically to any port into which an AP-515/575 is plugged, guaranteeing correct operation without manual port selection.

A – Configures the port as access VLAN 100; no trunk, so WLAN client and guest VLANs never reach the AP.

B – Trunk native 100 but omits VLAN 300 from the allowed list; guest SSID will fail.

D – Keeps native VLAN 1 and allows only VLAN 100; AP never receives management on 100 and lacks client/guest VLANs; PoE not explicitly enabled.

1. ArubaOS-CX 10.10 Management and Configuration Guide for Aruba CX 6300 Switches

“Device Profile for Aruba-AP”

pp. 851-853.

2. Aruba Campus Access Design Fundamentals (HPE Part #: 5200-7777)

Section 7.2 “Trunk requirements for APs”

p. 132-133.

3. HPE Aruba Networking CX 6300 Installation and Getting Started Guide

“PoE power classes and port configuration”

pp. 48-50.

4. Hewlett Packard Enterprise

Best Practices for Deploying Aruba 500-Series and 570-Series APs

Rev. 5.0

p. 9.