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

Multicast forwarding across unicast subnets, Configuration task list

Page 43 highlights

and Switch D, specifying Switch B as the RPF neighbor of Switch C and Switch C as the RPF neighbor of Switch D, the receiver hosts can receive the multicast data from the multicast source. NOTE: A static multicast route is effective only on the multicast router on which it is configured, and will not be advertised throughout the network or redistributed to other routers. Multicast forwarding across unicast subnets Routers forward the multicast data from a multicast source hop by hop along the forwarding tree, but some routers might not support multicast protocols in a network. When the multicast data is forwarded to a router that does not support IP multicast, the forwarding path is blocked. In this case, you can enable multicast forwarding across two unicast subnets by establishing a tunnel between the routers at the edges of the two unicast subnets. Figure 17 Multicast data transmission through a tunnel As shown in Figure 17, with a tunnel established between the multicast routers Switch A and Switch B, Switch A encapsulates the multicast data in unicast IP packets, and forwards them to Switch B across the tunnel through unicast routers. Then, Switch B strips off the unicast IP header and continues to forward the multicast data to the receiver. To use this tunnel only for multicast traffic, configure the tunnel as the outgoing interface only for multicast routes. Configuration task list Tasks at a glance (Required.) Enabling IP multicast routing (Optional.) Configuring multicast routing and forwarding • (Optional.) Configuring static multicast routes • (Optional.) Configuring the RPF route selection rule • (Optional.) Configuring multicast load splitting • (Optional.) Configuring static multicast MAC address entries 36

  • 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

36
and Switch D, specifying Switch B as the RPF neighbor of Switch C and Switch C as the RPF neighbor of
Switch D, the receiver hosts can receive the multicast data from the multicast source.
NOTE:
A static multicast route is effective only on the multicast router on which it is configured, and will not be
advertised throughout the network or redistributed to other routers.
Multicast forwarding across unicast subnets
Routers forward the multicast data from a multicast source hop by hop along the forwarding tree, but
some routers might not support multicast protocols in a network. When the multicast data is forwarded
to a router that does not support IP multicast, the forwarding path is blocked. In this case, you can enable
multicast forwarding across two unicast subnets by establishing a tunnel between the routers at the edges
of the two unicast subnets.
Figure 17
Multicast data transmission through a tunnel
As shown in
Figure 17
, with a tunnel established between the multicast routers Switch A and Switch B,
Switch A encapsulates the multicast data in unicast IP packets, and forwards them to Switch B across the
tunnel through unicast routers. Then, Switch B strips off the unicast IP header and continues to forward the
multicast data to the receiver.
To use this tunnel only for multicast traffic, configure the tunnel as the outgoing interface only for multicast
routes.
Configuration task list
Tasks at a glance
(Required.)
Enabling IP multicast routing
(Optional.)
Configuring multicast routing and forwarding
(Optional.)
Configuring static multicast routes
(Optional.)
Configuring the RPF route selection rule
(Optional.)
Configuring multicast load splitting
(Optional.)
Configuring static multicast MAC address entries