Operation Manual – Multicast Protocol
H3C S3610&S5510 Series Ethernet Switches
Chapter 8 Multicast Routing and Forwarding
Configuration
8-9
Follow these steps to configure multicast load splitting:
To do...
Use the command...
Remarks
Enter system view
system-view
—
Configuring multicast load
splitting
multicast load-splitting
{
source
|
source-group
}
Required
Disabled by default
8.3.6 Configuring a Multicast Forwarding Range
Multicast packets do not travel without a boundary in a network. The multicast data
corresponding to each multicast group must be transmitted within a definite scope.
You can configure a forwarding boundary specific to a particular multicast group on all
interfaces that support multicast forwarding. A multicast forwarding boundary sets the
boundary condition for the multicast groups in the specified range. If the destination
address of a multicast packet matches the set boundary condition, the packet will not
be forwarded. Once a multicast boundary is configured on an interface, this interface
can no longer forward multicast packets (including packets sent from the local device)
or receive multicast packets.
Follow these steps to configure a multicast forwarding range:
To do...
Use the command...
Remarks
Enter system view
system-view
—
Enter interface view
interface interface-type
interface-number
—
Configure a multicast
forwarding boundary
multicast boundary
group-address
{
mask |
mask-length
}
Required
No forwarding boundary
by default
8.3.7 Configuring the Multicast Forwarding Table Size
Too many multicast routing entries can exhaust the router’s memory and thus result in
lower router performance. Therefore, the number of multicast routing entries should be
limited. You can set a limit on the number of entries in the multicast routing table based
on the actual networking situation and the performance requirements. In any case, the
number of route entries must not exceed the maximum number allowed by the system.
If the configured maximum number of downstream nodes (namely, the maximum
number of outgoing interfaces) for a routing entry in the multicast forwarding table is
smaller than the current number, the downstream nodes in excess of the configured
limit will not be deleted immediately; instead they must be deleted by the multicast
