H3C Technologies H3C S7500E Series Switches - Manual (Page 179)

6-42
If there are no special networking requirements, we recommend that you use the default
settings.
Configuring Join/Prune Message Sizes
A larger join/prune message size will result in loss of a larger amount of information when a
message is lost; with a reduced join/message size, the loss of a single message will bring
relatively minor impact.
By controlling the maximum number of (S, G) entries in a join/prune message, you can
effectively reduce the number of (S, G) entries sent per unit of time.
Follow these steps to configure join/prune message sizes:
To do... Use the command... Remarks
Enter system view system-view —
Enter public instance PIM view
or VPN instance PIM view
pim [ vpn-instance
vpn-instance-name ]
—
Configure the maximum size of
a join/prune message
jp-pkt-size packet-size
Optional
8,100 bytes by default
Configure the maximum number
of (S, G) entries in a join/prune
message
jp-queue-size queue-size
Optional
1,020 by default
Displaying and Maintaining PIM
To do... Use the command... Remarks
View the BSR information in the
PIM-SM domain and locally
configured C-RP information in
effect
display pim [ all-instance | vpn-instance
vpn-instance-name ] bsr-info
Available in
any view
View the information of unicast
routes used by PIM
display pim [ all-instance | vpn-instance
vpn-instance-name ] claimed-route
[ source-address ]
Available in
any view