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

Solution, IPv6 multicast data is abnormally terminated on an intermediate router, Symptom, Analysis

Page 182 highlights

• • • • Solution 1. 2. 3. 4. 5. 6. the IPv6 multicast source. If the router does not have a route to the IPv6 multicast source, or if IPv6 PIM-DM is not enabled on the RPF interface toward the IPv6 multicast source, the router cannot create an (S, G) entry. On an IPv6 PIM-SM enabled network, when a router wants to join the SPT, the router creates an (S, G) entry only if it has a route to the IPv6 multicast source. If the router does not have a route to the IPv6 multicast source, or if IPv6 PIM-SM is not enabled on the RPF interface toward the IPv6 multicast source, the router cannot create an (S, G) entry. When a multicast router receives an IPv6 multicast packet, it looks up the existing IPv6 unicast routing table for the optimal route to the packet source. The outgoing interface of this route act as the RPF interface and the next hop acts the RPF neighbor. The RPF interface completely relies on the existing IPv6 unicast route and is independent of IPv6 PIM. The RPF interface must be enabled with IPv6 PIM, and the RPF neighbor must be an IPv6 PIM neighbor. If IPv6 PIM is not enabled on the RPF interface or the RPF neighbor, the multicast distribution tree cannot be correctly built, causing abnormal multicast forwarding. Because a hello message does not carry IPv6 PIM mode information, an IPv6 PIM router cannot identify what IPv6 PIM mode its IPv6 PIM neighbor is running in. If the RPF interface on a router and the connected interface of the router's RPF neighbor operate in different IPv6 PIM modes, the multicast distribution tree cannot be correctly built, causing abnormal multicast forwarding. The same IPv6 PIM mode must run on the entire network. Otherwise, the multicast distribution tree cannot be correctly built, causing abnormal multicast forwarding. Use display ipv6 routing-table to verify that an IPv6 unicast route to the IPv6 multicast source or the RP is available. Use display ipv6 pim interface to verify IPv6 PIM information on each interface, especially on the RPF interface. If IPv6 PIM is not enabled on the interfaces, use ipv6 pim dm or ipv6 pim sm to enable IPv6 PIM-DM or IPv6 PIM-SM for the interfaces. Use display ipv6 pim neighbor to verify that the RPF neighbor is an IPv6 PIM neighbor. Verify that IPv6 PIM and MLD are enabled on the interfaces that directly connect to the IPv6 multicast sources or the receivers. Use display ipv6 pim interface verbose to verify that the same IPv6 PIM mode is enabled on the RPF interface on a router and the connected interface of the router's RPF neighbor. Use display current-configuration to verify that the same IPv6 PIM mode is enabled on all routers on the network. For IPv6 PIM-SM, verify that the BSR and C-RPs are correctly configured. IPv6 multicast data is abnormally terminated on an intermediate router Symptom An intermediate router can receive IPv6 multicast data successfully, but the data cannot reach the last-hop router. An interface on the intermediate router receives IPv6 multicast data but does not create an (S, G) entry in the IPv6 PIM routing table. Analysis • If an IPv6 multicast forwarding boundary has been configured through the ipv6 multicast boundary command, and the IPv6 multicast packets are kept from crossing the boundary, IPv6 PIM cannot create routing entries for the packets. 175

  • 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

175
the IPv6 multicast source. If the router does not have a route to the IPv6 multicast source, or if IPv6
PIM-DM is not enabled on the RPF interface toward the IPv6 multicast source, the router cannot
create an (S, G) entry.
On an IPv6 PIM-SM enabled network, when a router wants to join the SPT, the router creates an (S,
G) entry only if it has a route to the IPv6 multicast source. If the router does not have a route to the
IPv6 multicast source, or if IPv6 PIM-SM is not enabled on the RPF interface toward the IPv6
multicast source, the router cannot create an (S, G) entry.
When a multicast router receives an IPv6 multicast packet, it looks up the existing IPv6 unicast
routing table for the optimal route to the packet source. The outgoing interface of this route act as
the RPF interface and the next hop acts the RPF neighbor. The RPF interface completely relies on the
existing IPv6 unicast route and is independent of IPv6 PIM. The RPF interface must be enabled with
IPv6 PIM, and the RPF neighbor must be an IPv6 PIM neighbor. If IPv6 PIM is not enabled on the RPF
interface or the RPF neighbor, the multicast distribution tree cannot be correctly built, causing
abnormal multicast forwarding.
Because a hello message does not carry IPv6 PIM mode information, an IPv6 PIM router cannot
identify what IPv6 PIM mode its IPv6 PIM neighbor is running in. If the RPF interface on a router and
the connected interface of the router's RPF neighbor operate in different IPv6 PIM modes, the
multicast distribution tree cannot be correctly built, causing abnormal multicast forwarding.
The same IPv6 PIM mode must run on the entire network. Otherwise, the multicast distribution tree
cannot be correctly built, causing abnormal multicast forwarding.
Solution
1.
Use
display ipv6 routing-table
to verify that an IPv6 unicast route to the IPv6 multicast source or the
RP is available.
2.
Use
display ipv6 pim interface
to verify IPv6 PIM information on each interface, especially on the
RPF interface. If IPv6 PIM is not enabled on the interfaces, use
ipv6 pim dm
or
ipv6 pim sm
to
enable IPv6 PIM-DM or IPv6 PIM-SM for the interfaces.
3.
Use
display ipv6 pim neighbor
to verify that the RPF neighbor is an IPv6 PIM neighbor.
4.
Verify that IPv6 PIM and MLD are enabled on the interfaces that directly connect to the IPv6
multicast sources or the receivers.
5.
Use
display ipv6 pim interface verbose
to verify that the same IPv6 PIM mode is enabled on the RPF
interface on a router and the connected interface of the router's RPF neighbor.
6.
Use
display current-configuration
to verify that the same IPv6 PIM mode is enabled on all routers
on the network. For IPv6 PIM-SM, verify that the BSR and C-RPs are correctly configured.
IPv6 multicast data is abnormally terminated on an
intermediate router
Symptom
An intermediate router can receive IPv6 multicast data successfully, but the data cannot reach the
last-hop router. An interface on the intermediate router receives IPv6 multicast data but does not create
an (S, G) entry in the IPv6 PIM routing table.
Analysis
If an IPv6 multicast forwarding boundary has been configured through the
ipv6 multicast boundary
command, and the IPv6 multicast packets are kept from crossing the boundary, IPv6 PIM cannot
create routing entries for the packets.