Question 280
At fictional Quayside Education, a network engineer supporting learning sites is reviewing IGMP and PIM multicast distribution during a planned network scaling change (HCIP-H12-821-MULTICAST-070). The observed network issue is: A source-specific multicast receiver attempts to use an any-source RP tree even though the deployment expects a specified source. Which observation most directly verifies that the corrective change succeeded?
Explanation
Correct Answer
The best verification observation is: Only the requested source-group stream is delivered without RP-based ambiguity. It demonstrates the corrective action: Configure compatible IGMPv3 source filters and source-specific PIM behavior. This fits the principle: SSM receivers identify the source and group and avoid general ASM RP discovery. Verify on the actual Huawei platform and network release.
Incorrect Answers
“The correct incoming interface and expected outgoing interface list are installed end to end” responds to another technical or business failure: An engineer diagnoses multicast stream loss by checking only source packets and ignores outgoing interface list and receiver state. That source case depends on: The best verification observation is: The correct incoming interface and expected outgoing interface list are installed end to end. The present issue is: A source-specific multicast receiver attempts to use an any-source RP tree even though the deployment expects a specified source. The more direct action is “Only the requested source-group stream is delivered without RP-based ambiguity” because the best verification observation is: Only the requested source-group stream is delivered without RP-based ambiguity.
“Receivers build valid PIM-SM join state toward the intended rendezvous point” responds to another technical or business failure: A PIM sparse-mode receiver joins a group but no rendezvous point is reachable in the intended PIM domain. That source case depends on: The best verification observation is: Receivers build valid PIM-SM join state toward the intended rendezvous point. The present issue is: A source-specific multicast receiver attempts to use an any-source RP tree even though the deployment expects a specified source. The more direct action is “Only the requested source-group stream is delivered without RP-based ambiguity” because the best verification observation is: Only the requested source-group stream is delivered without RP-based ambiguity.
“Packets arrive on the expected RPF interface and are forwarded downstream” responds to another technical or business failure: A multicast forwarding entry receives traffic from a source on the wrong interface and drops it. That source case depends on: The best verification observation is: Packets arrive on the expected RPF interface and are forwarded downstream. The present issue is: A source-specific multicast receiver attempts to use an any-source RP tree even though the deployment expects a specified source. The more direct action is “Only the requested source-group stream is delivered without RP-based ambiguity” because the best verification observation is: Only the requested source-group stream is delivered without RP-based ambiguity.