Question 610
At an enterprise telemetry network with multicast subscribers, a Junos specialist investigates this scenario: The operations team sees (S,G) entries and assumes they mean every source may send to a joined group. The team should test joins and forwarding separately. What protocol behavior accounts for this failure?
Explanation
Correct Answer
For an enterprise telemetry network with multicast subscribers, the governing mechanism is: (S,G) multicast state identifies one particular source S and destination group G. It explains the reported symptom: The operations team sees (S,G) entries and assumes they mean every source may send to a joined group. The intended response is: Inspect the source and group state to diagnose the correct sender-specific distribution tree. Verification: show multicast route or PIM state contains the planned source-group combination.
Incorrect Answers
IPv4 multicast traffic uses group addresses from 224.0.0.0 through 239.255.255.255 rather than ordinary unicast host destinations. This alternative mechanism does not match the current fault.
Multicast group and routing policies can limit which group ranges and sources cross specified boundaries. Fixing that different mechanism would not address the current root cause: (S,G) multicast state identifies one particular source S and destination group G.
Shared-tree (*,G) state expresses interest in traffic to group G from potentially multiple sources. Its verification is distinct from the reported condition: The operations team sees (S,G) entries and assumes they mean every source may send to a joined group. The team should test joins and forwarding separately.