Passive multicast route insertion
The vrf parameter allows you to display IP PIM counters for the VRF instance specified by the vrf- name variable.
The following table displays the output from the show ip pim counter nsr command.
This field... | Displays... |
|
|
Mcache sync | The mcache NSR sync queue that carries the NSR sync message for mcache updates. |
|
|
pack | The number of NSR sync messages that are packed from the active module to the standby |
| module. |
|
|
unpack | The number of NSR sync messages that are received and unpacked by the standby module. |
|
|
ack | The number of NSR sync acknowledgements received by the active module. |
|
|
RPset sync | The RPset sync queue that carries the NSR sync message for RPset update. |
|
|
BSR status | The BSR status sync queue that carries the NSR sync message for BSR information update. |
|
|
Passive multicast route insertion
To prevent unwanted multicast traffic from being sent to the CPU, PIM routing and passive multicast route insertion (PMRI) can be used together to ensure that multicast streams are forwarded out only ports with interested receivers and unwanted traffic is dropped in hardware on Layer 3 switches.
PMRI enables a Layer 3 switch running PIM Sparse to create an entry for a multicast route (for example, (S,G)), with no directly attached clients or when connected to another PIM device (transit network).
When a multicast stream has no output interfaces (OIF), the Layer 3 switch can drop packets in hardware if the multicast traffic meets either of the following conditions:
In
•‐ The route has no OIF and
‐If directly connected source passed source
‐If non directly connected source passed source RPF check.
In
•‐ The route has no OIF and
‐passed source RPF check and
‐Device has no downstream PIM neighbor.
If the OIF is inserted after the
NOTE
Disabling
78 | FastIron Ethernet Switch IP Multicast Configuration Guide |
|