3com 8807 User Guide
![3com](https://files.manualsbrain.com/attachments/960452ff43b9899cbcffced60c87abf956e7967a/common/fit/150/50/f6ac125d7af2cf40fec58935fa6d4bf71457a57efe50bee91208a434f325/brand_logo.jpeg)
PIM-SM Configuration
467
When configuring RP, if the range of the served multicast group is not specified,
the RP will serve all multicast groups. Otherwise, the range of the served multicast
group is the multicast group in the specified range. It is suggested to configure
Candidate RP on the backbone router.
the RP will serve all multicast groups. Otherwise, the range of the served multicast
group is the multicast group in the specified range. It is suggested to configure
Candidate RP on the backbone router.
c
CAUTION: Using the group-policy command on a candidate RP, you can
configure only the permit rule After the configuration ofthe permit rule, the RP
only serves for groups included in the permit rule.
configure only the permit rule After the configuration ofthe permit rule, the RP
only serves for groups included in the permit rule.
Configuring Static RP
To enhance network robustness, static RP serves as the backup of dynamic RP
c
CAUTION:
■
When the RP elected by BSR mechanism is effective, static RP does not work.
■
All routers in the PIM domain must be configured with this command
simultaneously, with the same RP address specified.
simultaneously, with the same RP address specified.
■
The system supports up to ten different static RP addresses. When more than
ten static RP addresses are configured, the system will give this prompt
information: "Cannot config static-rp, exceeded static-rp limit 10".
ten static RP addresses are configured, the system will give this prompt
information: "Cannot config static-rp, exceeded static-rp limit 10".
Configuring the PIM-SM
Domain Border
After the PIM-SM domain border is configured, bootstrap messages can not cross
the border in any direction. In this way, the PIM-SM domain can be split.
the border in any direction. In this way, the PIM-SM domain can be split.
Perform the following configuration in interface view.
By default, no domain border is set.
After this configuration is performed, a bootstrap message can not cross the
border but other PIM packets can. This configuration can effectively divide a
network into domains using different BSRs.
border but other PIM packets can. This configuration can effectively divide a
network into domains using different BSRs.
Table 458 Configure candidate-RPs
Operation
Command
Configure a candidate-RP
c-rp interface-type interface-number [ group-policy
acl-number | priority priority-value ]*
acl-number | priority priority-value ]*
Remove the candidate-RP configured
undo c-rp { interface-type interface-number | all }
Table 459 Configure static RP
Operation
Command
Remarks
Enter system view
system-view
-
Enter PIM view
pim
Required
Configure static RP
static-rp rp-address [ acl-number ]
Required
Table 460 Configure the PIM-SM domain border
Operation
Command
Set the PIM-SM domain border
pim bsr-boundary
Remove the PIM-SM domain border configured
undo pim bsr-boundary