The implementation plan for AOS-Switches calls for them to implement port-based tunneled node. The Aruba Mobility Controllers that will support the AOS-
Switches run software 8.1. The controllers will also support APs, are managed by Mobility Master, and use clustering.
Which issue with this plan needs to be addressed?
The correct issue to address is that the switches must use role-based tunneled node to work with clustering controllers. In environments where controllers are using clustering, only role-based tunneled-node is supported, not port-based tunneled-node. Therefore, the plan to implement port-based tunneled node is not valid with the current setup involving clustering controllers.
The answer is D
Only role-based tunneled-node, not port-based tunneled-node, is supported in cluster environments. The Answer is D.
Starting from ArubaOS 8.2.0.0, the per-port tunnel node and per-user tunnel node support is added on Mobility Controller Virtual Appliance. Note: Mode should be configured as role-based for dynamic segmentation – can be changed to port-based for per port tunneling
User-Based Tunneling – Controller Cluster (Large Scale - Wired and Wireless Deployment)If there is a large scale wired and wireless deployment, a controller cluster can be used solely for tunneled user traffic. This will enable wired clients and devices to tunnel back to dedicated controller clusters freeing the wireless controllers to handle pure wireless traff
Yes but the current ArubaOS is 8.1 so it is not supported.