What is a best practice concerning voice traffic and dynamic segmentation on AOS-CX switches?
What is a best practice concerning voice traffic and dynamic segmentation on AOS-CX switches?
For delay-sensitive applications like voice traffic, the best practice on AOS-CX switches is to use local forwarding rather than tunneling. This is because local forwarding reduces the latency that can occur when forwarding traffic through a remote controller or device. Thus, switch authentication and local forwarding of the voice traffic is the correct approach.
CX not support port-based tunneling
D is correct: Tunnelling options related to dynamic segmentation User- Based Tunnel (UBT) : each user is assigned their own role Port- Based Tunnel(PBT) : each port (and all the devices connected to the same port) are assigned the same role (PBT is not currently supported in AOS- CX 10.4 but there are plans to add it in a future release) Switch- to- switch tunnelling: planned release in AOS- CX 10.5 None : Exempt certain traffic from tunnelling by performing local switching/forwarding (like voice, for example)
Page 757 & 760 Study Guide: Local switching is typically used when delay- sensitive traffic is involved between access- layer devices, like voice or video communications (VoIP phones, for example) or a third- party firewall already exists in the network and the company wants to continue using the policy function of that firewall. [Aruba Networks] mportant: Currently, voice traffic must use local switching [Aruba Networks]
Correct Answer: C ACSP Study Guide Page 783 - Locally switch traffic for delay-sensitive applications like voice or video
Sry my answer is wrong... could be C because AOS-CX not support Port-Based Tunneling... Should be D i think.
Student Guide p. 757 ---> Voip should always be switched locally.
D is correct. (important!) voice traffic must use local switching. page 793