Q: 4
A company recently upgraded its campus switching infrastructure with Aruba 6300 CX switches. They
have implemented 802.1X authentication on edge ports where laptop and loT devices typically
connect An administrator has noticed that for PoE devices the pons are delivering the maximum
wattage instead of what the device actually needs Upon connecting the loT devices, the devices
request their specific required wattage through information exchange
Options
Discussion
Its D for this. On Aruba CX, device profiles are where you actually specify what power to allocate per port, including letting LLDP negotiate requested wattage. Without those profiles, the switch just hands out the max by default. Classifier policy (E) is more traffic related, not PoE allocation. I think D is correct but happy to hear if anyone's seen exceptions.
C isn't right here. D. Only device profiles on Aruba switches actually let you define port-specific PoE power, not classifier policy.
D imo, device profiles are what Aruba uses for PoE specifics. They let you set actual power needs per port, so the switch won't just hand out max wattage. E sounds more about data traffic classification than power settings tbh.
It’s E. Classifier policy could select the right power settings for each device type, not sure D handles every edge case here.
Looks like E. I figured a classifier policy could define PoE handling based on device type, so it might map devices to correct power settings. Not totally sure since Aruba has its quirks, but that's my take.
D . Device profiles actually let you set specific PoE behaviors per device type, including power. Without those, Aruba switches just default to maximum class-based power for everything. E seems more about traffic classification than PoE management. Pretty sure D is the move here but open if anyone has seen different behavior on live gear.
E
Be respectful. No spam.
