Configuring Message Filtering - Cisco Nexus 7000 Series Configuration Manual

Configuring Message Filtering

Step 4
Step 5
Configuring Message Filtering
Note
Prefix matches in the rp-candidate-policy must be exact relative to what the c-rp is advertising. Subset matches
are not possible.
You can configure filtering of the PIM and PIM6 messages described in the table below.
Table 18: PIM and PIM6 Message Filtering
Message Type
Global to the Device
Log Neighbor changes
PIM register policy
BSR candidate RP policy
BSR policy
Cisco Nexus 7000 Series NX-OS Multicast Routing Configuration Guide
108
Command or Action
show route-map
Example:
switch(config-route-map)# show route-map
copy running-config startup-config
Example:
switch(config-route-map)# copy
running-config startup-config
Purpose
(Optional) Displays configured route maps.
(Optional) Saves configuration changes.
Description
Enables syslog messages that list the neighbor state
changes to be generated. The default is disabled.
Enables PIM register messages to be filtered based
4
on a route-map policy where you can specify group
or group and source addresses with the match ip[v6]
multicast command. This policy applies to routers
that act as an RP. The default is disabled, which means
that the software does not filter PIM register messages.
Enables BSR candidate RP messages to be filtered by
the router based on a route-map policy1 where you
can specify the RP and group addresses and whether
the type is Bidir or ASM with the match ip[v6]
multicast command. This command can be used on
routers that are eligible for BSR election. The default
is no filtering of BSR messages.
Enables BSR messages to be filtered by the BSR client
routers based on a route-map policy1 where you can
specify BSR source addresses with the match ip[v6]
multicast command. This command can be used on
client routers that listen to BSR messages. The default
is no filtering of BSR messages.
Configuring PIM and PIM6