Task 7: Configure Chassis Alarms and Redundancy

Some M-series routers support Routing Engine (RE) and system control board redundancy options. You should be familiar with the configuration and operation of the various redundancy features available on the M20, M160, M40e, and T640 platforms, and you should be familiar with the ways in which various problems can be mapped to system alarm states. An example system alarm and redundancy scenario might consist of the following requirements:

• Configure the router to generate a yellow alarm when the fxp0 interface goes down.

• Set RE0 to be the primary, and configure RE failover in the event of routing daemon failure. You may assume that the configuration files have already been mirrored on the two REs for this task.

• Ensure that failure of router flash will not affect the operation of your initial configuration.

Configure alarms Alarms are configured at the [edit chassis alarms] configuration hierarchy. The following command is used to configure a yellow alarm upon detection of an fxp0 link down event:

[edit chassis alarm] lab@r2# set management-ethernet link-down yellow 

Configure redundancy System redundancy is configured at the [edit chassis redundancy] configuration hierarchy. The following commands are used to explicitly configure RE0 as the primary RE, which is the default, and to evoke a switchover to RE1 in the event of routing daemon (rpd) failure. The following commands were issued on a M20 router, because the M5 platform does not support RE redundancy:

[edit] lab@m20# set chassis redundancy routing-engine 0 master [edit] lab@m20# set system processes routing failover  other-routing-engine 

Perform a system snapshot To ensure that a failure of the router's flash will not cause the loss of your initial system configuration, you must perform a system snapshot to mirror the contents of the router's flash onto the router's hard drive:

lab@r1> request system snapshot umount: /altroot: not currently mounted Copying / to /altroot.. (this may take a few minutes) umount: /altconfig: not currently mounted Copying /config to /altconfig.. (this may take a few minutes) The following filesystems were archived: / /config 

Resulting alarms and redundancy configuration The configuration stanzas that resulted from the tasks in this example are shown next:

[edit] lab@sanjose# show system processes routing failover other-routing-engine; [edit] lab@sanjose# show chassis redundancy routing-engine 0 master; [edit] lab@sanjose# show chassis alarm management-ethernet {     link-down yellow;  }