83
Task Command
Remarks
specified multicast source.
[
group-address
] [
|
{
begin
|
exclude
|
include
}
regular-expression
]
Clear forwarding entries
from the multicast
forwarding table.
reset multicast
[
all-instance | vpn-instance
vpn-instance-name
]
forwarding-table
{ {
source-address
[
mask
{
mask
|
mask-length
} ] |
group-address
[
mask
{
mask
|
mask-length
} ] |
incoming-interface
{
interface-type
interface-number
|
register
} } * |
all
}
Available in user view.
When a multicast
forwarding entry is
removed, the
associated multicast
routing entry is also
removed.
Clear routing entries from
the multicast routing table.
reset multicast
[
all-instance | vpn-instance
vpn-instance-name
]
routing-table
{ {
source-address
[
mask
{
mask
|
mask-length
} ] |
group-address
[
mask
{
mask
|
mask-length
} ] |
incoming-interface
{
interface-type
interface-number
|
register
} } * |
all
}
Available in user view.
When a multicast
routing entry is
removed, the
associated multicast
forwarding entry is
removed.
For more information about designated forwarder (DF), see "
Multicast routing and forwarding configuration
examples
This section describes details about multicast routing and forwarding configuration examples.
RPF route change configuration example
Network requirements
As shown in
:
•
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 can receive the multicast data from the source through the path: Switch A
to Switch B, which is the same as the unicast route.
Configure the switches so that the receiver can receive the multicast data from the source through
the path: Switch A to Switch C to Switch B. This path is different from the unicast route.
