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

Configuration examples, Changing an RPF route, Network requirements

Page 47 highlights

Task Display multicast forwarding table information. Display information about the multicast routing table. Display information about the static multicast routing table. Display RPF route information about the multicast source. Clear forwarding entries from the multicast forwarding table. Clear routing entries from the multicast routing table. Command display multicast forwarding-table [ source-address [ mask { mask-length | mask } ] | group-address [ mask { mask-length | mask } ] | incoming-interface interface-type interface-number | outgoing-interface { exclude | include | match } interface-type interface-number | slot slot-number | statistics ] * display multicast routing-table [ source-address [ mask { mask-length | mask } ] | group-address [ mask { mask-length | mask } ] | incoming-interface interface-type interface-number | outgoing-interface { exclude | include | match } interface-type interface-number ] * display multicast routing-table static [ source-address { mask-length | mask } ] display multicast rpf-info source-address [ group-address ] reset multicast forwarding-table { { source-address [ mask { mask-length | mask } ] | group-address [ mask { mask-length | mask } ] | incoming-interface { interface-type interface-number } } * | all } reset multicast routing-table { { source-address [ mask { mask-length | mask } ] | group-address [ mask { mask-length | mask } ] | incoming-interface interface-type interface-number } * | all } NOTE: When a forwarding entry is removed, the associated routing entry is also removed. When a routing entry is removed, the associated forwarding entry is also removed. Configuration examples Changing an RPF route Network requirements As shown in Figure 18, PIM-DM runs in the network. All switches in the network support multicast. Switch A, Switch B, and Switch C run OSPF. Typically, the receiver host can receive the multicast data from the source through the path: Switch A to Switch B, which is the same as the unicast route. Perform the configuration so that the receiver host receives the multicast data from the source through the path: Switch A to Switch C to Switch B, which is different from the unicast route. 40

  • 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

40
Task
Command
Display multicast
forwarding table
information.
display multicast
forwarding-table
[
source-address
[
mask
{
mask-length
|
mask
} ] |
group-address
[
mask
{
mask-length
|
mask
} ] |
incoming-interface
interface-type interface-number
|
outgoing-interface
{
exclude
|
include
|
match
}
interface-type interface-number
|
slot
slot-number
|
statistics
] *
Display information about
the multicast routing table.
display multicast routing-table
[
source-address
[
mask
{
mask-length
|
mask
} ]
|
group-address
[
mask
{
mask-length
|
mask
} ] |
incoming-interface
interface-type interface-number
|
outgoing-interface
{
exclude
|
include
|
match
}
interface-type interface-number
] *
Display information about
the static multicast routing
table.
display multicast routing-table
static
[
source-address
{
mask-length
|
mask
} ]
Display RPF route
information about the
multicast source.
display multicast rpf-info
source-address
[
group-address
]
Clear forwarding entries
from the multicast
forwarding table.
reset multicast
forwarding-table
{ {
source-address
[
mask
{
mask-length
|
mask
} ] |
group-address
[
mask
{
mask-length
|
mask
} ] |
incoming-interface
{
interface-type interface-number
} } * |
all
}
Clear routing entries from
the multicast routing table.
reset multicast
routing-table
{ {
source-address
[
mask
{
mask-length
|
mask
} ] |
group-address
[
mask
{
mask-length
|
mask
} ] |
incoming-interface
interface-type interface-number
} * |
all
}
NOTE:
When a forwarding entry is removed, the associated routing entry is also removed. When a routing entry
is removed, the associated forwarding entry is also removed.
Configuration examples
Changing an RPF route
Network requirements
As shown in
Figure 18
, PIM-DM runs in the network. All switches in the network support multicast. Switch
A, Switch B, and Switch C run OSPF. Typically, the receiver host can receive the multicast data from the
source through the path: Switch A to Switch B, which is the same as the unicast route.
Perform the configuration so that the receiver host receives the multicast data from the source through the
path: Switch A to Switch C to Switch B, which is different from the unicast route.