- play_arrow Overview
- play_arrow Setting Up a Chassis Cluster
- SRX Series Chassis Cluster Configuration Overview
- SRX Series Chassis Cluster Slot Numbering and Logical Interface Naming
- Preparing Your Equipment for Chassis Cluster Formation
- Connecting SRX Series Firewalls to Create a Chassis Cluster
- Example: Setting the Node ID and Cluster ID for Security Devices in a Chassis Cluster
- Chassis Cluster Management Interfaces
- Chassis Cluster Fabric Interfaces
- Chassis Cluster Control Plane Interfaces
- Chassis Cluster Redundancy Groups
- Chassis Cluster Redundant Ethernet Interfaces
- Configuring Chassis Clustering on SRX Series Devices
- Example: Enabling Eight-Queue Class of Service on Redundant Ethernet Interfaces on SRX Series Firewalls in a Chassis Cluster
- Conditional Route Advertisement over Redundant Ethernet Interfaces on SRX Series Firewalls in a Chassis Cluster
- play_arrow Configuring Redundancy and Failover in a Chassis Cluster
- Chassis Cluster Dual Control Links
- Chassis Cluster Dual Fabric Links
- Monitoring of Global-Level Objects in a Chassis Cluster
- Monitoring Chassis Cluster Interfaces
- Monitoring IP Addresses on a Chassis Cluster
- Configuring Cluster Failover Parameters
- Understanding Chassis Cluster Resiliency
- Chassis Cluster Redundancy Group Failover
- play_arrow Chassis Cluster Operations
- Aggregated Ethernet Interfaces in a Chassis Cluster
- NTP Time Synchronization on Chassis Cluster
- Active/Passive Chassis Cluster Deployments
- Example: Configuring an SRX Series Services Gateway as a Full Mesh Chassis Cluster
- Example: Configuring an Active/Active Layer 3 Cluster Deployment
- Multicast Routing and Asymmetric Routing on Chassis Cluster
- Ethernet Switching on Chassis Cluster
- Media Access Control Security (MACsec) on Chassis Cluster
- Understanding SCTP Behavior in Chassis Cluster
- Example: Encrypting Messages Between Two Nodes in a Chassis Cluster
- play_arrow Upgrading or Disabling a Chassis Cluster
- play_arrow Configuration Statements and Operational Commands
- play_arrow Chassis Cluster Support on SRX100, SRX210, SRX220, SRX240, SRX550M, SRX650, SRX1400, SRX3400, and SRX3600 Devices
Troubleshooting a Control Link Failure in an SRX Chassis Cluster
Problem
Description
The control link fails to come up in an SRX chassis cluster.
Environment
SRX chassis cluster
Symptoms
The chassis cluster is down due to a control
link failure. The status of the control link is displayed as down
in the output of the show chassis cluster
interfaces
command. Here are sample outputs for an SRX branch
device and a high-end SRX device.
{primary:node0} root@J-SRX-branch> show chassis cluster interfaces Control link 0 name: fxp1 Control link status: Down
{primary:node0} root@J-SRX-highend> show chassis cluster interfaces Control link 0 name: em0 Control link 1 name: em1 Control link status: Down
Diagnosis
Are the control link ports connected through a switch?
Yes: Remove the switch and connect the control link ports directly. Reboot the secondary node and check whether the control link is up.
If the link is up, then there might be an issue in the chassis cluster setup on the Layer 2 switch network. See SRX Series Gateway Cluster Deployment in Layer 2 Network.
If the link is down, proceed to Step 2.
No: Proceed to Step 2.
Are the link LEDs for the control link ports on both the nodes lit green?
Yes: Proceed to Step 4.
No: The control link cable might be faulty. Proceed to Step 3.
Change the cable connecting the control link ports and check the link LED. Is the LED lit green?
Yes: This indicates that the original cable was faulty. Reboot both the nodes simultaneously to come out of the bad state. If the control link does not come up after the reboot, proceed to Step 4.
No: Open a case with your technical support representative to resolve the issue. Proceed to Data Collection for Customer Support.
Is this device an SRX5400, SRX5600, or SRX5800?
Yes: Reconfigure the control link on a different Services Processing Card (SPC), connect the cable to the new port, and reboot both the nodes.
Check whether the control link status is up:
If the link is up, the issue is resolved.
There might be a hardware issue with the SPC. Open a case with your technical support representative to resolve the hardware issue. Proceed to Data Collection for Customer Support.
If the link is still down, the transceivers might be faulty. Proceed to Step 5.
No: Verify that the correct ports are connected (see the following table):
Port Type
Port
Management (fxp0)
An Ethernet port on the Routing Engine
HA Control (fxp1 or em0/em1)
Port 0 (fiber only) on SPC—em0
Port 1 (fiber only) on SPC—em1
Fabric (fab0 and fab1)
Any available ge or xe interface (fiber only)
If the ports are connected correctly, and the link is still down, proceed to Step 5.
If the control link port is an SFP or XFP port, change the transceivers on both the nodes. Ensure that you use transceivers provided by Juniper Networks and that the transceivers are of the same type (such as LX or SX). Is the control link up now?
Yes: The issue is resolved.
The transceiver might be faulty. Open a case with your technical support representative to resolve the issue with the transceivers. Proceed to Data Collection for Customer Support.
No: Continue to troubleshoot this issue with your technical support representative. Proceed to Data Collection for Customer Support.