Documente Academic
Documente Profesional
Documente Cultură
1 of 4
http://kb.juniper.net/InfoCenter/index?page=content&id=KB15504&actp=...
Back to Answers
Printer Friendly
PR Search
Create a Support Case
Knowledge Center Feedback
SUMMARY:
This article describes the basic setup of a Chassis Cluster (High Availability), also known as JSRP, on a SRX240 device.
PROBLEM OR GOAL:
Configure SRX240 devices as a Chassis Cluster.
The following topology will be used for the configuration:
Topology notes:
Both reths (reth 0.0 and reth 1.0) belong to Redundancy Group 1, the data plane.
Redundancy Group 0 is the control plane.
ge-0/0/2 was selected for the fabric (data) link in this example. For the fabric link, a GE port is recommended.
For the Deployment Guide for SRX Series Services Gateways in Chassis Cluster Configuration, refer to TN260.
For other SRX devices, refer to the following articles:
SRX100
SRX210
SRX220
SRX550
SRX650
SRX1400
SRX3000 series
SRX5000 series
KB15669
KB15505
KB21312
KB25889
KB15503
TN10
TN10
TN10
CAUSE:
SOLUTION:
This section contains the following:
Prerequisites
Configuration
Technical_Documentation
Verification
Troubleshooting
10/26/2015 3:05 PM
2 of 4
http://kb.juniper.net/InfoCenter/index?page=content&id=KB15504&actp=...
Prerequisites
Before proceeding with configuring the device for a Chassis Cluster, complete these prerequisites:
a. In the SRX configuration, remove any existing configuration associated with the interfaces that will be
transformed into fxp0 (out-of-band management) and fxp1 (control link) when the chassis cluster feature is
enabled.
For the SRX240B, these interfaces are ge-0/0/0 and ge-0/0/1. The ge-0/0/0 interface will be mapped to fxp0
(out-of-band management) and the ge-0/0/1 interface will be mapped to fxp1 (control). The interfaces that are
mapped to fxp0 and fxp1 are device specific. For more information on this, refer to KB15356 - How are interfaces
assigned on J-Series and SRX platforms when the chassis cluster is enabled?
For help on removing the existing configuration on these interfaces, refer to KB27713 - How to remove references
to the interfaces that will be used as fxp0 and fxp1.
Important note: If you do not perform this prerequisite, then your chassis cluster may not come up; it may go into a
Hold/Lost state on both nodes.
c. Confirm that the SOFTWARE on both standalone devices is the same Junos OS version.
Verify using this command on both devices:
root> show version
Model: srx240b
JUNOS Software Release [11.4R7.5]
d. Confirm that the LICENSE keys are the same on both devices.
There is not a separate license for chassis cluster. However, both firewalls must have the identical features and
license keys enabled or installed. Note that the license keys are not required to configure your chassis cluster, but
they are required once your chassis cluster is in production and you need to use those features on either device.
Verify the license keys by using this command on both devices:
root> show system license
e. If running Junos 10.4 or earlier, Ethernet switching is not supported. For more information, refer to Disabling
Switching on SRX100, SRX210, SRX220, and SRX240 Devices Before Enabling Chassis Clustering .
Configuration
The following are the basic steps required for configuring a Chassis Cluster on SRX240 devices.
Physically connect the two devices together to form the control and fabric (data) links.
Control link:
On the SRX240 device, connect ge-0/0/1 on device A to ge-0/0/1 on device B. The ge-0/0/1 interface on device B will
change to ge-5/0/1 after clustering is enabled in Step 2.
Note: It is strongly recommended that the interfaces used for the control link are connected directly with a cable (instead of
a switch). If a switch must be used, then refer to KB25017.
Fabric (Data) link:
On the SRX240 device, connect ge-0/0/2 on device A to ge-0/0/2 on device B. The ge-0/0/2 interface on device B will
change to ge-5/0/2 after clustering is enabled in Step 2.
Note: For the Fabric (Data) link, it is recommended to use a GE port. If ge-0/0/2 is not available, you can choose another
open port on your devices. The Fabric (Data) link can be any available open port either onboard or gPIM other than
ge-0/0/0 and ge-0/0/1.
It is helpful to know that after step 2, the following will interface assignments will occur:
ge-0/0/0 will become fxp0 and used as for individual management of each of the devices
ge-0/0/1 will become fxp1 and used as the control link between the two devices (This is also documented in
KB15356.)
The other interfaces are also renamed on the secondary device. For example, on a SRX 240 device, the ge-0/0/0
interface is renamed to ge-5/0/0 on the secondary node 1. Refer to the complete mapping for each SRX Series
device: Node Interfaces on Active SRX Series Chassis Clusters.
10/26/2015 3:05 PM
3 of 4
http://kb.juniper.net/InfoCenter/index?page=content&id=KB15504&actp=...
Enable cluster mode and reboot the devices. Note that this is done in operational mode and not with a configure
mode command.
> set chassis cluster cluster-id <0-15> node <0-1> reboot
For example:
On device A:
On device B:
Cluster id will be the same on both devices, but the node id should be different as one device is node0 the other
device is node1.
This command will need to be done on both devices.
The range for the cluster-id is 0-15. Setting it to 0 is the equivalent of disabling cluster mode. User has only 1-15 (15
cluster IDs) ids for working cluster, so user can calculate virtual MAC only for these 15 cluster ids. For more
information, refer to [KB13689] How is the virtual MAC address derived for reth interfaces on J-Series and SRX?
After the reboot, note how the ge-0/0/0 and ge-0/0/1 interfaces are re-purposed to fxp0 and fxp1 respectively.
NOTE: The following steps 3 - 8 can all be performed on the primary device (Device A), and they will be automatically
copied over to the secondary device (Device B) when a commit is done.
Configure the device specific configurations such as host names and management IP addresses. This is
specific to each device and is the only part of the configuration that is unique to its specific node. This is done by entering
the following commands (all on the primary node):
On device A:
{primary:node0}
# set groups node0 system host-name <name-node0>
# set groups node0 interfaces fxp0 unit 0 family inet
-Device A's management IP address on fxp0 interface
# set groups node1 system host-name <name-node1>
# set groups node1 interfaces fxp0 unit 0 family inet
-Device B's management IP address on fxp0 interface
The 'set apply-groups' command is run so that the individual configs for each node, set by the above commands, are
applied only to that node. This command is required.
Configure the FAB links (data plane links for RTO sync, etc). For this example we will use physical ports ge-0/0/2
from each node.
On device A:
{primary:node0}
-fab0 is node0 (Device A) interface for the data link
# set interfaces fab0 fabric-options member-interfaces ge-0/0/2
-fab1 is node1 (Device B) interface for the data link
# set interfaces fab1 fabric-options member-interfaces ge-5/0/2
Note: There are no configuration commands for the Control link connection. Only the SRX5600 and SRX5800 platforms
require configuration commands for the Control link (SPC port).
Configure the Redundancy Group 0 for the Routing Engine failover properties. Also configure Redundancy
Group 1 (all the interfaces will be in one Redundancy Group in this example) to define the failover properties for
the Reth interfaces.
Note: If you want to use multiple Redundancy Groups for the interfaces, refer to the Security Configuration Guide.
{primary:node0}
# set chassis cluster
# set chassis cluster
# set chassis cluster
# set chassis cluster
redundancy-group
redundancy-group
redundancy-group
redundancy-group
0
0
1
1
node
node
node
node
0
1
0
1
priority
priority
priority
priority
100
1
100
1
Configure the interface monitoring. Monitoring the health of the interfaces is one way to trigger Redundancy group
failover.
Note: Interface monitoring is not recommended for redundancy-group 0.
On device A:
{primary:node0}
# set chassis cluster
# set chassis cluster
# set chassis cluster
# set chassis cluster
redundancy-group
redundancy-group
redundancy-group
redundancy-group
1
1
1
1
interface-monitor
interface-monitor
interface-monitor
interface-monitor
ge-0/0/3
ge-0/0/4
ge-5/0/3
ge-5/0/4
weight
weight
weight
weight
255
255
255
255
Configure the Redundant Ethernet interfaces (Reth interface) and assign the Redundant interface to a zone.
Make sure that you setup your max number of redundant interfaces as follows:
On device A:
{primary:node0}
# set chassis cluster reth-count <max-number>
-for first interface in the group (on Device A)
# set interfaces <node0-interface-name> gigether-options redundant-parent reth0
-for second interface in the group (on Device B)
# set interfaces <node1-interface-name> gigether-options redundant-parent reth0
-set up redundancy group for interfaces
# set interfaces reth0 redundant-ether-options redundancy-group <group-number>
10/26/2015 3:05 PM
4 of 4
http://kb.juniper.net/InfoCenter/index?page=content&id=KB15504&actp=...
Commit and changes will be copied over to the Secondary Node, Device B.
On device A:
{primary:node0}
# commit
This will prepare the basic clustering setting for both the devices.
TIP: If you want to manage this cluster via NSM or any other Management devices, refer to KB20795.
Technical Documentation
Chassis Cluster for Security Devices
Junos 12.1X45-D10
HTML
Junos 11.4
PDF--See Chapter 48, Chassis Cluster (page 1319)
HTML
Verification
You can check the cluster status with the following commands.
show
show
show
show
show
show
chassis
chassis
chassis
chassis
chassis
chassis
cluster
cluster
cluster
cluster
cluster
cluster
status
interfaces
statistics
control-plane statistics
data-plane statistics
status redundancy-group 1
Refer to the Junos Security Configuration Guide for what these commands mean:
HTML - Verifying the Chassis Cluster Configuration
Troubleshooting
Resolution Guide - SRX Chassis Cluster
PURPOSE:
Implementation
RELATED LINKS:
Deployment Guide for SRX Series Services Gateways in Chassis Cluster Configuration
Site Map / RSS Feeds / Careers / Accessibility / Feedback / Privacy & Policy / Legal Notices
10/26/2015 3:05 PM