Technical Documentation

Configuring Register Message Filtering on a PIM RP or DR

You configure RP/DR register message filtering to control the number and location of multicast sources that an RP knows. You can apply register message filters on a DR to control outgoing register messages, or apply them on an RP to control incoming register messages. When anycast RP is configured, all RPs in the anycast RP set need to be configured with the same register message filtering policy.

To filter incoming register messages at the RP, include the rp-register-policy statement for the RP:

rp {rp-register-policy [ rp-register-policies ];local {address address;}}

To filter outgoing register messages at the DR, configure the dr-register-policy statement for the DR:

rp {dr-register-policy [ policy-names ];static {address address;}}

You can include these statements at the following hierarchy levels:

  • [edit protocols pim]
  • [edit routing-instances routing-instance-name protocols pim]
  • [edit logical-systems logical-system-name protocols pim]
  • [edit logical-systems logical-system-name routing-instances routing-instance-name protocols pim]

If you delete a group and source address from a filter policy on an RP router, the RP will register the group and source only when the DR sends a null register message.

You can configure more than one policy for each statement. If a referenced policy does not exist, the configuration commit checkout will fail. For examples of both types of register filters, see Example: Configuring Register Message Filters on PIM RPs and DRs.

For more information on RP/DR register message filtering, see Filtering RP/DR Register Messages.

Related Topics


Published: 2010-07-19

Help
|
My Account
|
Log Out