Configuring Overload State On A Single Sfm; Service Management Tasks; Changing The System Name - Alcatel-Lucent 7450 Configuration Manual

Service Management Tasks

Configuring Overload State on a Single SFM

A 7450 ESS or 7750 SR with a single SFM installed has a system multicast throughput that
is only a half of a system with dual SFMs installed. For example, in a mixed environment in
which IOM1s, IOM2s, and IOM3s are installed in the same system (chassis mode B or C),
system multicast throughput doubles when redundant SFMs are used instead of a single SFM.
If the required system multicast throughput is between 16G and 32G (which means both
SFMs are being actively used), when there is an SFM failure, multicast traffic needs to be
rerouted around the node.
Some scenarios include:
You can use an overload state in IGP to trigger the traffic reroute by setting the overload bit
in IS-IS or setting the metric to maximum in OSPF. Since PIM uses IGP to find out the
upstream router, a next-hop change in IGP will cause PIM to join the new path and prune the
old path, which effectively reroutes the multicast traffic downstream. When the problem is
resolved, the overload condition is cleared, which will cause the traffic to be routed back to
the router.
Service Management Tasks
This section discusses the following service management tasks:

Changing the System Name

The system command sets the name of the device and is used in the prompt string. Only one
system name can be configured. If multiple system names are configured, the last one
configured will overwrite the previous entry.
Use the following CLI syntax to change the system name:
84
• There is only one SFM installed in the system
• One SFM (active or standby) failed in a dual SFM configuration
• The system is in the ISSU process
• Changing the System Name
• Modifying Interface Parameters
• Deleting a Logical IP Interface
Router Configuration Guide