The temperature of one or more components (Field Replaceable Units or FRUs) exceeded the indicated temperature, which is the upper of two thresholds. The fans (and impellers, if applicable) were in the indicated state. If the temperature does not go below the threshold within four minutes after the chassis process (chassisd) detects this condition, the chassisd process shuts … [Read more...]
How to distinguish Tx and Rx lockup status on em0 interface
The em0 interface is supposed to be 'UP' all the time because it provides the communication channel between the Routing Engine (RE) and Packet Forwarding Engines (PFEs); however, in a certain condition the link status will be changed to 'DOWN'. When EM0 is marked as 'DOWN' it can cause the following issues. Chassis Cluster failover Chassis Cluster failover of Data … [Read more...]
How to automatically trigger failover of redundancy-group 0 and redundancy-group 1 at the same time on a chassis cluster
This article discusses how failover of redundancy-group 0 (RG0) and redundancy-group 1 (RG1) be automatically triggered at the same time on a chassis cluster. Some protocols, such as the Unified Threat Management (UTM) feature, are currently only supported in an active/passive cluster scenario whereby both RG0 and RG1 need to be primary on the same node. How can Ithe user … [Read more...]
Creating rescue of the current configuration on the Chassis Cluster before proceeding with ISSU
This article is the third article of a series of articles for performing an ISSU (In-Service Software Upgrade). Load the Junos Software package on the device Verify the Health of the Cluster (Important step) Create backup of the current configuration and set the rescue config Start the In-Service Software Upgrade Process to follow, in the event of the ISSU … [Read more...]