Usage Scenario
A BSR message carries information about all candidate-rendezvous points (C-RPs) on a network. If there are a large number of C-RPs, the length of a BSR message may exceed the maximum transmission unit (MTU) of an outbound interface. As a result, the BSR message cannot be processed, RP election fails, and multicast services cannot be transmitted normally. To resolve these problems, run the bsm semantic fragmentation command to enable BSR message fragmentation, so that the devices on the network can learn consistent RP information and MDTs can be successfully established.
BSR message fragmentation is recommended because it can solve the problem faced by IP fragmentation that all fragments become unavailable due to loss of fragment information.
- If IP fragmentation is enabled, the protocol layer transmits the entire BSR message up to the IP layer regardless of the length of the BSR message. The BSR message is then fragmented at the IP layer. After BSR message fragments are transmitted to the destination, the destination cannot parse the entire BSR message if one fragment is lost. As a result, the destination cannot learn RP information and MDTs cannot be established, which causes a multicast data forwarding failure.
- If BSR message fragmentation is enabled, the protocol layer directly fragments a long BSR message. After BSR message fragments are transmitted to the destination, only the information carried in a lost fragment is lost. As a result, only MDTs corresponding to the information carried in the lost fragments cannot be established, but MDTs corresponding to the information carried in other BSR message fragments that reach the destination can still be established.
Precautions
To use the BSR message fragmentation function, you need to enable this function on all devices. If BSR message fragmentation is not enabled on some devices, RP information on these devices is inconsistent with that on other devices and MDTs cannot be established on these devices.