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

Creating an RPF route,

Page 42 highlights

Figure 15 Changing an RPF route As shown in Figure 15, when no static multicast route is configured, Switch C's RPF neighbor on the path back to the source is Switch A, and the multicast data from the source travels through Switch A to Switch C. When a static multicast route is configured on Switch C with Switch B as its RPF neighbor on the path back to the source, the multicast data from the source travels along the path: Switch A to Switch B and then to Switch C. Creating an RPF route When a unicast route is blocked, multicast forwarding might be stopped due to lack of an RPF route. In this case, you can create an RPF route by configuring a static multicast route for a given multicast source, so that a multicast routing entry is created to guide multicast forwarding. Figure 16 Creating an RPF route Multicast Routing Table Static on Switch C Source/Mask Interface RPF neighbor/Mask 192.168.0.0/24 Vlan-int10 1.1.1.1/24 OSPF domain Switch D Receiver Multicast Routing Table Static on Switch D Source/Mask Interface RPF neighbor/Mask 192.168.0.0/24 Vlan-int20 2.2.2.2/24 Vlan-int20 2.2.2.1/24 Source 192.168.0.1/24 RIP domain Vlan-int10 Vlan-int10 1.1.1.1/24 1.1.1.2/24 Vlan-int20 2.2.2.2/24 Receiver Switch A Switch B Switch C Multicast packets Multicast static route As shown in Figure 16, the RIP domain and the OSPF domain are unicast isolated from each other. When no static multicast route is configured, the receiver hosts in the OSPF domain cannot receive the multicast packets from the multicast source in the RIP domain. If you configure a static multicast route on Switch C 35

  • 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

35
Figure 15
Changing an RPF route
As shown in
Figure 15
, when no static multicast route is configured, Switch C's RPF neighbor on the path
back to the source is Switch A, and the multicast data from the source travels through Switch A to Switch
C. When a static multicast route is configured on Switch C with Switch B as its RPF neighbor on the path
back to the source, the multicast data from the source travels along the path: Switch A to Switch B and
then to Switch C.
Creating an RPF route
When a unicast route is blocked, multicast forwarding might be stopped due to lack of an RPF route. In
this case, you can create an RPF route by configuring a static multicast route for a given multicast source,
so that a multicast routing entry is created to guide multicast forwarding.
Figure 16
Creating an RPF route
As shown in
Figure 16
, the RIP domain and the OSPF domain are unicast isolated from each other. When
no static multicast route is configured, the receiver hosts in the OSPF domain cannot receive the multicast
packets from the multicast source in the RIP domain. If you configure a static multicast route on Switch C
Vlan-int10
1.1.1.2/24
Vlan-int10
1.1.1.1/24
Vlan-int20
2.2.2.2/24
Vlan-int20
2.2.2.1/24
Source
192.168.0.1/24
Source/Mask
Multicast Routing Table Static on Switch C
192.168.0.0/24
Interface
Vlan-int10
RPF neighbor/Mask
1.1.1.1/24
Source/Mask
Multicast Routing Table Static on Switch D
192.168.0.0/24
Interface
Vlan-int20
RPF neighbor/Mask
2.2.2.2/24
OSPF domain
RIP domain
Switch A
Switch B
Switch C
Switch D
Receiver
Receiver
Multicast packets
Multicast static route