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

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

Page 103 highlights

• • • Solution 1. 2. 3. 4. 5. 6. source, or if PIM-SM is not enabled on the RPF interface toward the multicast source, the router cannot create an (S, G) entries. When a multicast router receives a multicast packet, it looks up the existing 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 unicast route and is independent of PIM. The RPF interface must be enabled with PIM, and the RPF neighbor must be a PIM neighbor. If PIM is not enabled on the RPF interface or the RPF neighbor, the multicast distribution tree cannot be built correctly, causing abnormal multicast forwarding. Because a hello message does not carry PIM mode information, a PIM router cannot identify what PIM mode its PIM neighbor is running. If the RPF interface on a router and the connected interface of the router's RPF neighbor operate in different PIM modes, the multicast distribution tree cannot be built correctly, causing abnormal multicast forwarding. The same PIM mode must run on the entire network. Otherwise, the multicast distribution tree cannot be built correctly, causing abnormal multicast forwarding. Use display ip routing-table to verify that a unicast route to the multicast source or the RP is available. Use display pim interface to verify PIM information on each interface, especially on the RPF interface. If PIM is not enabled on the interfaces, use pim dm or pim sm to enable PIM-DM or PIM-SM for the interfaces. Use display pim neighbor to verify that the RPF neighbor is a PIM neighbor. Verify that PIM and IGMP are enabled on the interfaces that directly connect to the multicast sources or the receivers. Use display pim interface verbose to verify that the same 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 PIM mode is enabled on all routers. For PIM-SM, verify that the BSR and C-RPs are correctly configured. Multicast data is abnormally terminated on an intermediate router Symptom An intermediate router can receive multicast data successfully, but the data cannot reach the last-hop router. An interface on the intermediate router receives multicast data but does not create an (S, G) entry in the PIM routing table. Analysis • If a multicast forwarding boundary has been configured through the multicast boundary command, and the multicast packets are kept from crossing the boundary, PIM cannot create routing entries for the packets. • If an ACL is defined by the source-policy command, and the multicast packets cannot match the ACL rule, PIM cannot create the routing entries for the packets. 96

  • 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

96
source, or if PIM-SM is not enabled on the RPF interface toward the multicast source, the router
cannot create an (S, G) entries.
When a multicast router receives a multicast packet, it looks up the existing 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 unicast
route and is independent of PIM. The RPF interface must be enabled with PIM, and the RPF neighbor
must be a PIM neighbor. If PIM is not enabled on the RPF interface or the RPF neighbor, the multicast
distribution tree cannot be built correctly, causing abnormal multicast forwarding.
Because a hello message does not carry PIM mode information, a PIM router cannot identify what
PIM mode its PIM neighbor is running. If the RPF interface on a router and the connected interface
of the router's RPF neighbor operate in different PIM modes, the multicast distribution tree cannot be
built correctly, causing abnormal multicast forwarding.
The same PIM mode must run on the entire network. Otherwise, the multicast distribution tree cannot
be built correctly, causing abnormal multicast forwarding.
Solution
1.
Use
display ip routing-table
to verify that a unicast route to the multicast source or the RP is
available.
2.
Use
display pim interface
to verify PIM information on each interface, especially on the RPF
interface. If PIM is not enabled on the interfaces, use
pim dm
or
pim sm
to enable PIM-DM or
PIM-SM for the interfaces.
3.
Use
display pim neighbor
to verify that the RPF neighbor is a PIM neighbor.
4.
Verify that PIM and IGMP are enabled on the interfaces that directly connect to the multicast
sources or the receivers.
5.
Use
display pim interface verbose
to verify that the same 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 PIM mode is enabled on all routers. For
PIM-SM, verify that the BSR and C-RPs are correctly configured.
Multicast data is abnormally terminated on an intermediate
router
Symptom
An intermediate router can receive multicast data successfully, but the data cannot reach the last-hop
router. An interface on the intermediate router receives multicast data but does not create an (S, G) entry
in the PIM routing table.
Analysis
If a multicast forwarding boundary has been configured through the
multicast boundary
command,
and the multicast packets are kept from crossing the boundary, PIM cannot create routing entries for
the packets.
If an ACL is defined by the
source-policy
command, and the multicast packets cannot match the
ACL rule, PIM cannot create the routing entries for the packets.