4-14After this feature is configured, Bootstrap messages cannot pass the border. However, the other PIMmessages can pass the domain border. The network can be effectively divided into domains that usedifferent BSRs.Filtering the Registration Packets from DR to RPWithin a PIM-SM domain, the source-side DR sends register messages to the RP, and these registermessages have different multicast source or group addresses. You can configure a filtering rule to filterregister messages so that the RP can serve specific multicast groups. If an (S, G) entry is denied by thefiltering rule, or the action for this entry is not defined in the filtering rule, the RP will send a register-stopmessage to the DR to stop the registration process for the multicast data..Follow these steps to filter the registration packets from RP to DR:To do... Use the command... RemarksEnter system view system-view —Enter PIM view pim —Configure to filter theregistration packets fromRP to DRregister-policy acl-numberRequiredBy default, the switch does not filterthe registration packets from DR.Only the registration packets matching the permit command of ACLs can be accepted. When an invalidACL is defined, RP will reject all the registration packets.Disabling RPT-to-SPT SwitchoverInitially, a PIM-SM-enabled multicast device forwards multicast packets through an RPT. By default, thelast-hop switch initiates an RPT-to-SPT switchover process. You can also disable RPT-to-SPTswitchover through the configuration.Follow these steps to disable RPT-to-SPT switchover:To do... Use the command... RemarksEnter system view system-view —Enter PIM view pim —Disable RPT-to-SPTswitchoverspt-switch-threshold infinity[ group-policy acl-number[ order order-value ] ]OptionalBy default, the device switchesto the SPT immediately after itreceives the first multicastpacket from the RPT.
