HP 6125XLG R2306-HP 6125XLG Blade Switch IP Multicast Configuration Guide - Page 162

Disabling the BSM semantic fragmentation function, Configuring IPv6 multicast source registration

Page 162 highlights

Step 3. Configuring an IPv6 PIM domain border. Command ipv6 pim bsr-boundary Remarks By default, no IPv6 PIM domain border is configured. Disabling the BSM semantic fragmentation function Generally, a BSR periodically advertises the RP-set information in BSMs within the IPv6 PIM-SM domain. It encapsulates a BSM in an IPv6 datagram and might fragment the datagram if the message exceeds the MTU. In this case, loss of a single IP fragment leads to unavailability of the entire message. Semantic fragmentation of BSMs can solve this issue. When a BSM exceeds the MTU, it is split to multiple BSM fragments (BSMFs). • If the RP-set information for an IPv6 multicast group range is carried in one BSMF, a non-BSR router directly updates the RP-set information for the group range after receiving the BSMF. • If the RP-set information for an IPv6 multicast group range is carried in multiple BSMFs, a non-BSR router updates the RP-set information for the group range after receiving all these BSMFs. Because the RP-set information contained in each segment is different, loss of some IP fragments does not result in dropping of the entire BSM. The BSM semantic fragmentation function is enabled by default. A device that does not support this function might regard a fragment as a BSM and thus learns only part of the RP-set information. Therefore, if such devices exist in the IPv6 PIM-SM domain, you must disable the BSM semantic fragmentation function on the C-BSRs. To disable the BSM semantic fragmentation function: Step 1. Enter system view. 2. Enter IPv6 PIM view. 3. Disable the BSM semantic fragmentation function. Command system-view ipv6 pim undo bsm-fragment enable Remarks N/A N/A By default, BSM semantic fragmentation is enabled. NOTE: Generally, a BSR performs BSM semantic fragmentation according to the MTU of its BSR interface. However, for BSMs originated due to learning of a new IPv6 PIM neighbor, semantic fragmentation is performed according to the MTU of the interface that sends the BSMs. Configuring IPv6 multicast source registration In an IPv6 PIM-SM domain, the source-side DR sends register messages to the RP, and these register messages have different IPv6 multicast source or IPv6 multicast group addresses. You can configure a filtering rule to filter register messages so that the RP can provide services for specific IPv6 multicast groups. If the filtering rule denies an (S, G) entry, or if the filtering rule does not define an action for this entry, the RP sends a register-stop message to the DR to stop the registration process for the IPv6 multicast data. In view of information integrity of a register message in the transmission process, you can configure the device to calculate the checksum based on the entire register message. However, to reduce the workload of encapsulating data in register messages and for the sake of interoperability, do not use this checksum calculation method. 155

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211

155
Step
Command
Remarks
3.
Configuring an IPv6 PIM
domain border.
ipv6 pim bsr-boundary
By default, no IPv6 PIM domain
border is configured.
Disabling the BSM semantic fragmentation function
Generally, a BSR periodically advertises the RP-set information in BSMs within the IPv6 PIM-SM domain.
It encapsulates a BSM in an IPv6 datagram and might fragment the datagram if the message exceeds the
MTU. In this case, loss of a single IP fragment leads to unavailability of the entire message.
Semantic fragmentation of BSMs can solve this issue. When a BSM exceeds the MTU, it is split to multiple
BSM fragments (BSMFs).
If the RP-set information for an IPv6 multicast group range is carried in one BSMF, a non-BSR router
directly updates the RP-set information for the group range after receiving the BSMF.
If the RP-set information for an IPv6 multicast group range is carried in multiple BSMFs, a non-BSR
router updates the RP-set information for the group range after receiving all these BSMFs. Because
the RP-set information contained in each segment is different, loss of some IP fragments does not
result in dropping of the entire BSM.
The BSM semantic fragmentation function is enabled by default. A device that does not support this
function might regard a fragment as a BSM and thus learns only part of the RP-set information. Therefore,
if such devices exist in the IPv6 PIM-SM domain, you must disable the BSM semantic fragmentation
function on the C-BSRs.
To disable the BSM semantic fragmentation function:
Step
Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Enter IPv6 PIM view.
ipv6 pim
N/A
3.
Disable the BSM semantic
fragmentation function.
undo bsm-fragment
enable
By default, BSM semantic
fragmentation is enabled.
NOTE:
Generally, a BSR performs BSM semantic fragmentation according to the MTU of its BSR interface.
However, for BSMs originated due to learning of a new IPv6 PIM neighbor, semantic fragmentation is
performed according to the MTU of the interface that sends the BSMs.
Configuring IPv6 multicast source registration
In an IPv6 PIM-SM domain, the source-side DR sends register messages to the RP, and these register
messages have different IPv6 multicast source or IPv6 multicast group addresses. You can configure a
filtering rule to filter register messages so that the RP can provide services for specific IPv6 multicast
groups. If the filtering rule denies an (S, G) entry, or if the filtering rule does not define an action for this
entry, the RP sends a register-stop message to the DR to stop the registration process for the IPv6 multicast
data.
In view of information integrity of a register message in the transmission process, you can configure the
device to calculate the checksum based on the entire register message. However, to reduce the workload
of encapsulating data in register messages and for the sake of interoperability, do not use this checksum
calculation method.