[Contents] [Prev] [Next] [Index] [Report an Error]

Verifying Routing Engine Redundancy Status

A separate log file is provided for redundancy logging at /var/log/mastership. To view the log, use the file show /var/log/mastership command. Table 8 lists the mastership log event codes and descriptions.

Table 8: Routing Engine Mastership Log

Event Code

Description

E_NULL = 0

The event is a null event.

E_CFG_M

The Routing Engine is configured as master.

E_CFG_B

The Routing Engine is configured as backup.

E_CFG_D

The Routing Engine is configured as disabled.

E_MAXTRY

The maximum number of tries to acquire or release mastership was exceeded.

E_REQ_C

A claim mastership request was sent.

E_ACK_C

A claim mastership acknowledgement was received.

E_NAK_C

A claim mastership request was not acknowledged.

E_REQ_Y

Confirmation of mastership is requested.

E_ACK_Y

Mastership is acknowledged.

E_NAK_Y

Mastership is not acknowledged.

E_REQ_G

A release mastership request was sent by a Routing Engine.

E_ACK_G

The Routing Engine acknowledged release of mastership.

E_CMD_A

The command request chassis routing-engine master acquire was issued from the backup Routing Engine.

E_CMD_F

The command request chassis routing-engine master acquire force was issued from the backup Routing Engine.

E_CMD_R

The command request chassis routing-engine master release was issued from the master Routing Engine.

E_CMD_S

The command request chassis routing-engine master switch was issued from a Routing Engine.

E_NO_ORE

No other Routing Engine is detected.

E_TMOUT

A request timed out.

E_NO_IPC

Routing Engine connection was lost.

E_ORE_M

Other Routing Engine state was changed to master.

E_ORE_B

Other Routing Engine state was changed to backup.

E_ORE_D

Other Routing Engine state was changed to disabled.


[Contents] [Prev] [Next] [Index] [Report an Error]