A new video multicast application is deployed in the network. The application team wants to use the 239.0.0.1 multicast group to stream the video to users. They want to know if this choice will impact the existing multicast design. What impact will their choice have on the existing multicast design?
A. Because 239.0.0.1 is a private multicast range, a flood of PIM packets that have to be processed by the CPU and hosts will be sent by the routers in the network.
B. Because 239.0.0.1 is a private multicast range, the rendezvous point has to send out constant group updates that will have to be processed by the CPU and hosts.
C. The multicast application sends too many packets into the network and the network infrastructure drops packets.
D. The 239.0.0.1 group address maps to a system MAC address, and all multicast traffic will have to be sent to the CPU and flooded out all ports.
Answer: D
A customer is using a service provider to provide a WAN backbone for a 30-site network. In establishing the network, the customer must work within these constraints: The customer has a self-managed MPLS backbone. The VPLS WAN backbone of the service provider does not support PIM snooping. Multicast VPN must be used for multicast support inside some VRFs. What can the customer do so that multicast traffic is NOT flooded to all sites?
A. Configure static GRE tunnels and run the MPLS and multicast VPN inside these GRE tunnels.
B. Use Label Switched Multicast for the multicast transport.
C. Use PIM-SSM as the multicast routing protocol with IETF Rosen Draft multicast VPN.
D. Configure a static mapping between multicast addresses and MAC addresses.
E. Use GET VPN to encrypt the multicast packets inside the WAN.
Answer: A
No comments:
Post a Comment
Note: only a member of this blog may post a comment.