Description

How to verify if the configuration of node0 and node1 is the same in a Chassis Cluster setup.

Symptoms

Verify if the configuration files on two nodes of a Chassis Cluster are the same or not. The challenge involved is that the configuration file is too huge to be cross-checked manually.

Solution

NOTE:  The solution in this article will work only when the other node in the cluster is not lost/ and the FAB link is up too (steps 1 and 2 below).

Follow these steps in order:

  1. Check the status of the cluster using command:

    >show chassis cluster status

    The target node should not show as lost. If it does then check if the CTRL Link is up or not  and if the Other device is powered on or not. For additional help on fixing this, refer to KB20641 - Troubleshooting steps when the Chassis Cluster does not come up [juniper.net] .

  2. Then check if the fabric link is up or not, command for that would be:

    >show interfaces terse fab*
    or
    >show interfaces terse | match fab

    The fabric links should show Admin up and Link up. If not, then check the cables/Lights on ports and reseat them.  For additional help on fixing this, refer to KB20641 - Troubleshooting steps when the Chassis Cluster does not come up [juniper.net] .

  3. After the above steps have been verified, run this config mode command:

    #show | compare node1:/config/juniper.conf.gz

    The /config/juniper.conf.gz is the current config file in the node1 as well as node0.
    So the show command is actually fetching the data in the node1 /config/juniper.conf.gz and comparing it with the data in the node0 /config/juniper.conf.gz

Modification History

2020-07-14: Article reviewed for accuracy. Minor non-technical edits.