Question 560
At an enterprise telemetry network with multicast subscribers, a Junos specialist investigates this scenario: An upstream multicast router receives no distribution request even though a downstream receiver requires the stream. The team should test joins and forwarding separately. Which response best restores the intended behavior?
Explanation
Correct Answer
For an enterprise telemetry network with multicast subscribers, the direct corrective action is: Enable compatible sparse-mode PIM and verify receiver-driven upstream join signaling. This addresses the mechanism: PIM sparse mode builds multicast forwarding paths in response to explicit joins rather than flooding everywhere. Confirm by checking: show pim join reports an expected entry and packets follow the joined multicast branch. During rollout, verify unicast routing to the source or RP before expecting successful reverse-path checks.
Incorrect Answers
PIM-SM can transition selected traffic from an RP-rooted shared tree to a source-rooted shortest-path tree. The appropriate correction for the reported case is: Enable compatible sparse-mode PIM and verify receiver-driven upstream join signaling.
PIM Join and Prune signaling maintains or removes forwarding-tree state as downstream interest changes. Fixing that different mechanism would not address the current root cause: PIM sparse mode builds multicast forwarding paths in response to explicit joins rather than flooding everywhere.
Any-source multicast allows receivers to request a group independent of a specific source, typically using a shared-tree mechanism. Its verification is distinct from the reported condition: An upstream multicast router receives no distribution request even though a downstream receiver requires the stream. The team should test joins and forwarding separately.