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

RPT building, IPv6 multicast source registration, RPT building in an IPv6 PIM-SM domain

Page 151 highlights

RPT building Figure 49 RPT building in an IPv6 PIM-SM domain Source Server Host A Receiver RP DR Host B DR RPT Join message IPv6 multicast packets Receiver Host C As shown in Figure 49, the process of building an RPT is as follows: 1. When a receiver wants to join the IPv6 multicast group G, it uses an MLD message to inform the receiver-side DR. 2. After getting the receiver information, the DR sends a join message, which is forwarded hop by hop to the RP that provides services for the IPv6 multicast group. 3. The routers along the path from the DR to the RP form an RPT branch. Each router on this branch adds to its forwarding table a (*, G) entry, where the asterisk (*) means any IPv6 multicast source. The RPT is rooted at the RP and has the DR as its leaf. When the IPv6 multicast data addressed to the IPv6 multicast group G reaches the RP, the RP forwards the data to the DR along the established RPT, and finally to the receiver. When a receiver is no longer interested in the IPv6 multicast data addressed to the IPv6 multicast group G, the receiver-side DR sends a prune message, which goes hop by hop along the RPT to the RP. After receiving the prune message, the upstream node deletes the interface that connects to this downstream node from the outgoing interface list and checks whether it has receivers for that IPv6 multicast group. If not, the router continues to forward the prune message to its upstream router. IPv6 multicast source registration The IPv6 multicast source uses the registration process to inform an RP of its presence. 144

  • 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

144
RPT building
Figure 49
RPT building in an IPv6 PIM-SM domain
As shown in
Figure 49
, the process of building an RPT is as follows:
1.
When a receiver wants to join the IPv6 multicast group G, it uses an MLD message to inform the
receiver-side DR.
2.
After getting the receiver information, the DR sends a join message, which is forwarded hop by
hop to the RP that provides services for the IPv6 multicast group.
3.
The routers along the path from the DR to the RP form an RPT branch. Each router on this branch
adds to its forwarding table a (*, G) entry, where the asterisk (*) means any IPv6 multicast source.
The RPT is rooted at the RP and has the DR as its leaf.
When the IPv6 multicast data addressed to the IPv6 multicast group G reaches the RP, the RP forwards
the data to the DR along the established RPT, and finally to the receiver.
When a receiver is no longer interested in the IPv6 multicast data addressed to the IPv6 multicast group
G, the receiver-side DR sends a prune message, which goes hop by hop along the RPT to the RP. After
receiving the prune message, the upstream node deletes the interface that connects to this downstream
node from the outgoing interface list and checks whether it has receivers for that IPv6 multicast group. If
not, the router continues to forward the prune message to its upstream router.
IPv6 multicast source registration
The IPv6 multicast source uses the registration process to inform an RP of its presence.
Source
Server
Host A
Host B
Host C
Receiver
Receiver
IPv6 multicast packets
RPT
Join message
RP
DR
DR