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

Troubleshooting IPv6 PIM, A multicast distribution tree cannot be correctly built, Symptom, Analysis

Page 181 highlights

RP address 1002::2 (local) Group/MaskLen: FF94::/16 RP address 1002::2 (local) Group/MaskLen: FFA4::/16 RP address 1002::2 (local) Group/MaskLen: FFB4::/16 RP address 1002::2 (local) Group/MaskLen: FFC4::/16 RP address 1002::2 (local) Group/MaskLen: FFD4::/16 RP address 1002::2 (local) Group/MaskLen: FFE4::/16 RP address 1002::2 (local) Group/MaskLen: FFF4::/16 RP address 1002::2 (local) Group/MaskLen: FF04::/16 RP address 1002::2 (local) Priority HoldTime Uptime Expires 192 180 00:02:03 00:02:56 Priority HoldTime Uptime Expires 192 180 00:02:03 00:02:56 Priority HoldTime Uptime Expires 192 180 00:02:03 00:02:56 Priority HoldTime Uptime Expires 192 180 00:02:03 00:02:56 Priority HoldTime Uptime Expires 192 180 00:02:03 00:02:56 Priority HoldTime Uptime Expires 192 180 00:02:03 00:02:56 Priority HoldTime Uptime Expires 192 180 00:02:03 00:02:56 Priority HoldTime Uptime Expires 192 180 00:02:03 00:02:56 Priority HoldTime Uptime Expires 192 180 00:02:03 00:02:56 # Display RP information on Switch F. [SwitchF] display pim rp-info BSR RP information: Scope: non-scoped Group/MaskLen: FF00::/8 RP address Priority HoldTime Uptime Expires 8001::1 (local) 192 180 00:10:28 00:02:31 Troubleshooting IPv6 PIM A multicast distribution tree cannot be correctly built Symptom An IPv6 multicast distribution tree cannot be correctly built because there are no IPv6 multicast forwarding entries established on the routers (including routers directly connected with multicast sources or receivers) in a IPv6 PIM network. Analysis • On an IPv6 PIM-DM enabled network, IPv6 multicast data is flooded from the router that directly connects to the IPv6 multicast source to the routers that directly connects to the receivers. When the IPv6 multicast data is flooded to a router, the router creates an (S, G) entry only if it has a route to 174

  • 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

174
RP address
Priority
HoldTime
Uptime
Expires
1002::2 (local)
192
180
00:02:03
00:02:56
Group/MaskLen: FF94::/16
RP address
Priority
HoldTime
Uptime
Expires
1002::2 (local)
192
180
00:02:03
00:02:56
Group/MaskLen: FFA4::/16
RP address
Priority
HoldTime
Uptime
Expires
1002::2 (local)
192
180
00:02:03
00:02:56
Group/MaskLen: FFB4::/16
RP address
Priority
HoldTime
Uptime
Expires
1002::2 (local)
192
180
00:02:03
00:02:56
Group/MaskLen: FFC4::/16
RP address
Priority
HoldTime
Uptime
Expires
1002::2 (local)
192
180
00:02:03
00:02:56
Group/MaskLen: FFD4::/16
RP address
Priority
HoldTime
Uptime
Expires
1002::2 (local)
192
180
00:02:03
00:02:56
Group/MaskLen: FFE4::/16
RP address
Priority
HoldTime
Uptime
Expires
1002::2 (local)
192
180
00:02:03
00:02:56
Group/MaskLen: FFF4::/16
RP address
Priority
HoldTime
Uptime
Expires
1002::2 (local)
192
180
00:02:03
00:02:56
Group/MaskLen: FF04::/16
RP address
Priority
HoldTime
Uptime
Expires
1002::2 (local)
192
180
00:02:03
00:02:56
# Display RP information on Switch F.
[SwitchF] display pim rp-info
BSR RP information:
Scope: non-scoped
Group/MaskLen: FF00::/8
RP address
Priority
HoldTime
Uptime
Expires
8001::1 (local)
192
180
00:10:28
00:02:31
Troubleshooting IPv6 PIM
A multicast distribution tree cannot be correctly built
Symptom
An IPv6 multicast distribution tree cannot be correctly built because there are no IPv6 multicast
forwarding entries established on the routers (including routers directly connected with multicast sources
or receivers) in a IPv6 PIM network.
Analysis
On an IPv6 PIM-DM enabled network, IPv6 multicast data is flooded from the router that directly
connects to the IPv6 multicast source to the routers that directly connects to the receivers. When the
IPv6 multicast data is flooded to a router, the router creates an (S, G) entry only if it has a route to