What is correct regarding the tunneling of user traffic between AOS-CX switches and Aruba Mobility Controllers (MCs)?
What is correct regarding the tunneling of user traffic between AOS-CX switches and Aruba Mobility Controllers (MCs)?
AOS-CX switches and Aruba Mobility Controllers use the same management protocol as Aruba APs, which is PAPI (UDP port 8211). The AOS-CX switches do not use IPSec for protection like the APs do for the PAPI connection between the AP and MC. Instead, optional MD5 HMAC protection can be implemented for PAPI communication between AOS-CX switches and MCs.
I think the answer is D because both AP and Switch use PAPI . Moreover in AOS-CX switch currently not support port based tunnel. AOS-CX switch only support User Based Tunnel (UBT)
the correct Answer is D
D is correct
D is the answer
should be D, the switch uses two protocols to connect to an MC: PAPI (control plane) and GRE (data plane). However, where APs use IPSec to protect the PAPI connection between the AP and MC, AOS-CX switches do not support this protection. Instead, you can optionally implement an MD5 HMAC function to protect PAPI between the AOS-CX switches and MCs
Answer is D, see page 784 Switches do not use IPsec or port-based tunneling
Answer is D, see page 784 Switches do not use IPsec or port-based tunneling
Answer is D
D is correct
Answer is D
Page 749 Study Guide: The switch uses two protocols to connect to an Aruba Mobility Controller (MC) The control plane uses PAPI (UDP port 8211) - the same protocol used by AP- to- MC communications. However, where APs use IPSec to protect the PAPI connection between the AP and MC, AOS- CX switches do not support this protection. Instead, you can optionally implement an MD5 HMAC function to protect PAPI between the AOS- CX switches and MCs. [Aruba Networks]