J Series Chassis Cluster Configuration Overview
This section provides an overview of the basic steps to create a J Series chassis cluster.
For the basic steps to set up an SRX Series chassis cluster, see SRX Series Chassis Cluster Configuration Overview.
Before You Begin |
---|
For background information, read: |
![]() | Note: For J Series chassis clusters, the two nodes in a cluster must be identical models, but can have any combination of PIMs installed. |
To create a J Series chassis cluster:
- Physically connect a pair of the same kind of supported
J Series devices together:
- To create the fabric link between two nodes in a cluster,
connect any pair of Gigabit Ethernet interfaces, either the built-in
interfaces or interfaces on the PIMs. The only requirement is that
both interfaces be Gigabit Ethernet interfaces. Connecting J Series Devices in a Cluster (J6350 Devices) shows nodes
connected using the built-in ge-0/0/1 interface for the fabric
link.
When using dual fabric link functionality, connect the two pairs of Gigabit Ethernet interfaces that you will use on each device. For more information, see Understanding Chassis Cluster Dual Fabric Links.
- Connect the ge-0/0/3 interfaces together to create the control link.
- To create the fabric link between two nodes in a cluster,
connect any pair of Gigabit Ethernet interfaces, either the built-in
interfaces or interfaces on the PIMs. The only requirement is that
both interfaces be Gigabit Ethernet interfaces. Connecting J Series Devices in a Cluster (J6350 Devices) shows nodes
connected using the built-in ge-0/0/1 interface for the fabric
link.
- On the first device to be initialized in the cluster—this
is the node that will form the cluster—connect to the console
port.
For connection instructions, see the J Series Services Routers Hardware Guide.
- Use CLI operational mode commands to enable clustering:
- Identify the cluster by giving it a cluster ID.
- Identify the node by giving it its own node ID and then reboot the system.
See Example: Setting the Chassis Cluster Node ID and Cluster ID (CLI).
- On the other device, connect to the console port and use
CLI operational mode commands to enable clustering:
- Identify the cluster that the device is joining by setting the same cluster ID you set on the first node.
- Identify the node by giving it its own node ID and then reboot the system.
- Configure the management interfaces on the cluster.
See Example: Configuring the Chassis Cluster Management Interface (CLI).
- To configure the cluster with the CLI, see:
- Example: Configuring the Number of Redundant Ethernet Interfaces in a Chassis Cluster (CLI)
- Example: Configuring the Chassis Cluster Fabric (CLI)
- Example: Configuring Chassis Cluster Redundancy Groups (CLI)
- Example: Configuring Chassis Cluster Redundant Ethernet Interfaces (CLI)
- Example: Configuring Chassis Cluster Interface Monitoring (CLI)
- To initiate manual failover, see Initiating a Chassis Cluster Manual Redundancy Group Failover.
- To configure conditional route advertisement over redundant Ethernet interfaces, see Understanding Conditional Route Advertising in a Chassis Cluster.
- To verify the configuration, see Verifying a Chassis Cluster Configuration.
Related Topics
- JUNOS Software Feature Support Reference for SRX Series and J Series Devices
- Understanding What Happens When Chassis Cluster Is Enabled
- Connecting J Series Hardware to Create a Chassis Cluster
- Example: Setting the Chassis Cluster Node ID and Cluster ID (CLI)
- Example: Configuring the Chassis Cluster Management Interface (CLI)
- Example: Configuring the Number of Redundant Ethernet Interfaces in a Chassis Cluster (CLI)
- Verifying a Chassis Cluster Configuration