cluster (Chassis)
Syntax
cluster {
configuration-synchronize (Chassis Cluster) {
no-secondary-bootup-auto;
}
control-interface {
node name {
disable;
}
}
control-link-recovery;
control-ports fpc {
port;
}
health-monitoring;
heartbeat-interval milliseconds;
heartbeat-threshold heartbeat-threshold;
network-management {
cluster-master;
}
redundancy-group (Chassis Cluster) name {
gratuitous-arp-count gratuitous-arp-count;
hold-down-interval seconds;
interface-monitor name {
weight weight;
}
ip-monitoring {
family {
inet {
address name {
interface logical-interface-name {
secondary-ip-address;
}
weight weight;
}
}
}
global-threshold global-threshold;
global-weight global-weight;
retry-count retry-count;
retry-interval (Chassis Cluster) retry-interval;
}
node (Chassis Cluster Redundancy Group) (0 | 1) {
priority priority;
}
preempt (Chassis Cluster) {
delay seconds;
limit limit;
period seconds;
}
}
redundancy-mode(active-active | active-backup);
redundant-interface name {
mapping-interface mapping-interface;
}
reth-count (Chassis Cluster) reth-count;
traceoptions (Chassis Cluster) {
file <filename> <files files> <match match> <size size> <(world-readable | no-world-readable)>;
flag name;
level (alert | all | critical | debug | emergency | error | info | notice | warning);
no-remote-trace;
}
}
Hierarchy Level
[edit chassis]
Description
Configure a chassis
cluster. Perform the configuration under the [edit chassis cluster] configuration stanza to define chassis cluster configuration, operations,
and monitoring. This configuration must specify configuration synchronization,
control link recovery, heartbeat interval and threshold, network management,
redundancy group, and traceoptions.
Options
| configuration-synchronize |
Disable automatic chassis cluster synchronization. See configuration-synchronize (Chassis Cluster). |
| control-interface |
Disable and Enable chassis cluster control-link interface on SRX1500, SRX4100, SRX4200, and SRX4600 devices. If you want to reboot any of the nodes, then you must disable the control interfaces on both nodes using the CLI configuration to ensure control link remains disabled after reboot. When control link is down, configuration change on local node will not be synchronized to the remote node. From configuration mode, run the From the operational mode, run the |
| control-link-recovery |
Enable automatic control link recovery option. |
| control-ports |
Enable specific chassis cluster control ports.
|
| health-monitoring |
Enable to monitor the health status of the SRX Series devices operating in chassis cluster mode. The health status between the two nodes is monitored and shared over control links and fabric links. Failover between the nodes occurs based on the heart beat status and health status of the control links and fabric links. By default, the option is disabled. |
| heartbeat-interval |
Interval between successive heartbeats (milliseconds)
|
| heartbeat-threshold |
Number of consecutive missed heartbeats to indicate device failure
|
| network-management |
Define parameters for network management. See network-management. |
| redundancy-group name |
Define a redundancy group. See redundancy-group (Chassis Cluster). |
| redundancy-mode |
Redundancy mode for the cluster (Reboot all nodes simultaneously after change)
|
| reth-count |
Number of redundant ethernet interfaces
|
| traceoptions |
Define chassis cluster redundancy process tracing operations. See traceoptions (Chassis Cluster). |
The remaining statements are explained separately. See CLI Explorer.
Required Privilege Level
interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration.
Release Information
Statement introduced in Junos OS Release 9.0.
The health-monitoring option is introduced in Junos OS Release
18.4R1.
The control-interface option is introduced in Junos OS Release
20.4R1 for SRX1500 devices.
The Redundancy mode option is introduced in Junos OS Release
24.4R1.