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

Relationship between IPv6 admin-scoped zones and the IPv6 global-scoped zone

Page 154 highlights

admin-scoped zones are designated can have intersections, but the IPv6 multicast groups in an IPv6 admin-scoped zone are valid only within its local zone, and theses IPv6 multicast groups are regarded as private group addresses. The IPv6 global-scoped zone can be regarded as a special IPv6 admin-scoped zone, and it maintains a BSR to provide services for the IPv6 multicast groups with the scope field value as 14. Relationship between IPv6 admin-scoped zones and the IPv6 global-scoped zone The IPv6 global-scoped zone and each IPv6 admin-scoped zone have their own C-RPs and BSRs. These devices are effective only on their respective zones, and the BSR election and the RP election are implemented independently. Each IPv6 admin-scoped zone has its own boundary. The IPv6 multicast information within a zone cannot cross this boundary in either direction. You can have a better understanding of the IPv6 global-scoped zone and IPv6 admin-scoped zones based on geographical locations and the scope field values. • In view of geographical locations: An IPv6 admin-scoped zone is a logical zone for particular IPv6 multicast groups with the same scope filed value. The IPv6 multicast packets for such IPv6 multicast groups are confined within the local IPv6 admin-scoped zone and cannot cross the boundary of the zone. Figure 51 Relationship in view of geographical locations As shown in Figure 51, for the IPv6 multicast groups with the same scope field value, the IPv6 admin-scoped zones must be geographically separated and isolated. The IPv6 global-scoped zone includes all routers in the IPv6 PIM-SM domain. IPv6 multicast packets that do not belong to any IPv6 admin-scoped zones are forwarded in the entire IPv6 PIM-SM domain. • In view of the scope field values: In terms of the scope field values, the scope field in an IPv6 multicast group address shows which zone the IPv6 multicast group belongs to. 147

  • 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

147
admin-scoped zones are designated can have intersections, but the IPv6 multicast groups in an IPv6
admin-scoped zone are valid only within its local zone, and theses IPv6 multicast groups are regarded
as private group addresses.
The IPv6 global-scoped zone can be regarded as a special IPv6 admin-scoped zone, and it maintains a
BSR to provide services for the IPv6 multicast groups with the scope field value as 14.
Relationship between IPv6 admin-scoped zones and the IPv6 global-scoped zone
The IPv6 global-scoped zone and each IPv6 admin-scoped zone have their own C-RPs and BSRs. These
devices are effective only on their respective zones, and the BSR election and the RP election are
implemented independently. Each IPv6 admin-scoped zone has its own boundary. The IPv6 multicast
information within a zone cannot cross this boundary in either direction. You can have a better
understanding of the IPv6 global-scoped zone and IPv6 admin-scoped zones based on geographical
locations and the scope field values.
In view of geographical locations:
An IPv6 admin-scoped zone is a logical zone for particular IPv6 multicast groups with the same
scope filed value. The IPv6 multicast packets for such IPv6 multicast groups are confined within the
local IPv6 admin-scoped zone and cannot cross the boundary of the zone.
Figure 51
Relationship in view of geographical locations
As shown in
Figure 51
, for the IPv6 multicast groups with the same scope field value, the IPv6
admin-scoped zones must be geographically separated and isolated. The IPv6 global-scoped
zone includes all routers in the IPv6 PIM-SM domain. IPv6 multicast packets that do not belong to
any IPv6 admin-scoped zones are forwarded in the entire IPv6 PIM-SM domain.
In view of the scope field values:
In terms of the scope field values, the scope field in an IPv6 multicast group address shows which
zone the IPv6 multicast group belongs to.