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

Configuring multicast source registration, Configuring switchover to SPT

Page 84 highlights

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 PIM neighbor, semantic fragmentation is performed according to the MTU of the interface that sends the BSMs. Configuring multicast source registration In a PIM-SM domain, the source-side DR sends register messages to the RP, and these register messages have different multicast source or group addresses. You can configure a filtering rule to filter register messages so that the RP can provide services for specific multicast groups. If the filtering rule denies an (S, G) entry, or if the filtering rule does not define the action for this entry, the RP sends a register-stop message to the DR to stop the registration process for the 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. To configure multicast source registration: Step Command 1. Enter system view. system-view 2. Enter PIM view. pim 3. Configure a filtering rule for register messages. register-policy acl-number 4. Configure the device to calculate the checksum based on the entire register register-whole-checksum message. Remarks N/A N/A By default, no register filtering rule exists. By default, the device calculates the checksum based on the header of a register message. Configuring switchover to SPT CAUTION: If the device is an RP, disabling switchover to SPT might cause multicast traffic forwarding failures on the source-side DR. When disabling switchover to SPT, be sure you fully understand its impact on your network. To configure the switchover to SPT: Step Command Remarks 1. Enter system view. system-view N/A 2. Enter PIM view. pim N/A 3. Configure the criteria for triggering a switchover to SPT. spt-switch-threshold { immediacy | infinity } [ group-policy acl-number ] By default, both the receiver-side DR and RP immediately trigger the switchover from RPT to SPT after receiving the first multicast packet. 77

  • 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

77
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 PIM neighbor, semantic fragmentation is
performed according to the MTU of the interface that sends the BSMs.
Configuring multicast source registration
In a PIM-SM domain, the source-side DR sends register messages to the RP, and these register messages
have different multicast source or group addresses. You can configure a filtering rule to filter register
messages so that the RP can provide services for specific multicast groups. If the filtering rule denies an
(S, G) entry, or if the filtering rule does not define the action for this entry, the RP sends a register-stop
message to the DR to stop the registration process for the 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.
To configure multicast source registration:
Step
Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Enter PIM view.
pim
N/A
3.
Configure a filtering rule for
register messages.
register-policy
acl-number
By default, no register filtering rule
exists.
4.
Configure the device to
calculate the checksum based
on the entire register
message.
register-whole-checksum
By default, the device calculates
the checksum based on the header
of a register message.
Configuring switchover to SPT
CAUTION:
If the device is an RP, disabling switchover to SPT might cause multicast traffic forwarding failures on the
source-side DR. When disabling switchover to SPT, be sure you fully understand its impact on your
network.
To configure the switchover to SPT:
Step
Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Enter PIM view.
pim
N/A
3.
Configure the criteria for
triggering a switchover to SPT.
spt-switch-threshold
{
immediacy
|
infinity
} [
group-policy
acl-number
]
By default, both the receiver-side
DR and RP immediately trigger
the
switchover from RPT to SPT after
receiving the first multicast packet.