Changing an rpf route, Network requirements – H3C Technologies H3C SecPath F1000-E User Manual
Page 594
569
Task
Command
Remarks
Clear forwarding entries
from the multicast
forwarding table.
reset multicast 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
Clear routing entries from
the multicast routing table.
reset multicast 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
CAUTION:
•
The reset command clears the information in the multicast routing table or the multicast forwarding
table, and thus might cause failure of multicast transmission.
•
When a routing entry is deleted from the multicast routing table, the corresponding forwarding entry will
also be deleted from the multicast forwarding table.
•
When a forwarding entry is deleted from the multicast forwarding table, the corresponding routing
entry will also be deleted from the multicast routing table.
Multicast routing and forwarding configuration
examples at the CLI
Changing an RPF route
Network requirements
PIM-DM runs in the network. All routers in the network support multicast. SecPath A, SecPath B and
SecPath C run OSPF.
Typically, Receiver can receive the multicast data from Source through the path SecPath A – SecPath B,
which is the same as the unicast route.
Perform the following configuration so that Receiver can receive the multicast data from Source through
the path SecPath A – SecPath C – SecPath B, which is different from the unicast route.