Exam HPE6-A73 topic 1 question 19 discussion

B&C is correct It is stated in the Study Guide, as mentioned above: "AOS-CX switches, however, do not support this feature. Instead, the remote mirroring must be to a device that supports it, like Wireshark."

Page 634 Study Guide: Both VSX peers have the same Control Plane information. This means that both members will be able to establish PIM neighborships, send PIM Join messages to the RP and Build a Shortest Path Tree (SPT). However, multicast traffic (data plane) is only routed from the VSX peer that acts as the PIM DR. The mechanism to have a pre- established Control Plane on both VSX peers permits the VSX cluster to achieve a fast fail over in case the PIM DR fails. [Aruba Networks]

A: In Aruba VSX (Virtual Switching Extension), the VSX peers do not run PIM (Protocol Independent Multicast) individually and maintain their own multicast group databases.

A: Multicast Traffic Flow: In a VSX environment with PIM-SM, multicast traffic is forwarded based on the multicast distribution tree established by PIM-SM. Each physical switch in the VSX pair independently participates in the PIM-SM operations, including joining the appropriate multicast distribution tree and forwarding multicast traffic accordingly. VSX and Multicast: When operating VSX and using PIM-SM routing, each physical switch within the VSX pair independently runs PIM-SM. This means that each switch has its own RP and maintains its own multicast routing tables.

Answer is A: Multicast traffic to these IGMP groups is pruned/forwarded based on the individual IGMP group database on each VSX node. ISLP does not synchronize IGMP groups between VSX peers. Source: https://www.arubanetworks.com/techdocs/AOS-CX/10.06/HTML/5200-7727/Content/Chp_prev_traf_loss/igm-sno-10.htm

i think the Answer is A. Each VSX switch has an identical IGMP group database: • Each VSX node individually learns any JOIN/LEAVE message received from a downstream VSX LAG. • The VSX IGMP process translates the received IGMP from the ISL into an IGMP join message from the VSX LAG. Multicast traffic to these IGMP groups is pruned/forwarded based on the individual IGMP group database on each VSX node. ISLP does not synchronize IGMP groups between VSX peers. The IGMP database construction is a data-plane based process. - Chapter 7, Preventing traffic loss, "ArubaOS-CX Virtual Switching Extension (VSX) Guide for 10.03"

Answer D Same routing table for fast failover and one is elected DR and share traffic and the other one is DR Proxy.

As the question stands A is correct.

In my opinion it is D... A also sounds quite good, but it is crucial that both VSX peers have and use the same multicast tables. "Both the DR and proxy DR maintain the same multicast tables and build the shortest path tree." Reference: https://www.arubanetworks.com/techdocs/AOS-CX/10.07/HTML/5200-7888/Content/Chp_Pre_tra_loss/ip-mul-rou-10.htm

"both VSX switches as a PIM Designate Router (DR). One node is the actual DR, the other node is the proxy DR." "Only the actual DR performs multicast routing and forward traffic destined to groups to its downstream VLANs in the data-path." https://www.arubanetworks.com/techdocs/AOS-CX/10.07/HTML/5200-7888/Content/Chp_Pre_tra_loss/ip-mul-rou-10.htm

it should be A

As the question stands A is correct. As Mrvn says, each VSX peer can be the DR for a VLAN, but not both at the same time.

In stufy book we can see that on peer stands as DR. meanst its A or D. I perefered A

C answer can be misleading though.. Each VSX peers runs PIM and builds its own group database.= correct Both VSX peers can forward multicast streams to receivers in a VLAN, = not same VLAN ! achieving load sharing = correct only if each VSX is configured as DR for different VLANs so answer A could be more correct as it is less open for misinterpretation

C is correct

The correct Answer is A

Yes: it should be A.