high-availability (Chassis)
Syntax
high-availability {
grid-id id;
hardware-upgrade;
local-domain-id id <domain-size domain-size>;
local-id id <local-forwarding-ip loopback-address> <local-ip local-ip>;
peer-domain-id name {
domain-size domain-size;
peer-id name {
desc desc;
interface interface;
liveness-detection {
no-adaptation;
detection-time {
threshold milliseconds;
}
minimum-interval milliseconds;
minimum-receive-interval milliseconds;
multiplier multiplier;
transmit-interval {
minimum-interval milliseconds;
threshold milliseconds;
}
version (0 | 1 | automatic);
}
local-ip local-ip;
peer-ip peer-ip;
routing-instance routing-instance;
vpn-profile vpn-profile;
}
}
peer-id name {
desc desc;
interface interface;
liveness-detection {
no-adaptation;
detection-time {
threshold milliseconds;
}
minimum-interval milliseconds;
minimum-receive-interval milliseconds;
multiplier multiplier;
transmit-interval {
minimum-interval milliseconds;
threshold milliseconds;
}
version (0 | 1 | automatic);
}
peer-forwarding-ip loopback-address interface interface {
liveness-detection no-adaptation
<detection-time threshold milliseconds>
<minimum-interval milliseconds> <minimum-receive-interval milliseconds>
<multiplier multiplier> <transmit-interval <minimum-interval milliseconds> <threshold milliseconds>> <version (0 | 1 | automatic)>;
peer-ip peer-ip;
routing-instance routing-instance;
vpn-profile vpn-profile;
}
services-redundancy-group name {
activeness-priority activeness-priority;
activeness-probe {
bfd-liveliness {
destination-ip destination-ip;
interface interface;
minimum-interval milliseconds;
multiplier multiplier;
routing-instance routing-instance;
source-ip source-ip;
}
dest-ip {
ip-address;
routing-instance routing-instance;
src-ip src-ip;
}
minimum-interval minimum-interval;
multiplier multiplier;
}
active-signal-route {
ip-address;
routing-instance routing-instance;
}
backup-signal-route {
ip-address;
routing-instance routing-instance;
}
deployment-type (cloud | hybrid | routing | switching);
install-on-failure-route {
ip-address;
routing-instance routing-instance;
}
interface name {
virtual-mac-id virtual-mac-id;
}
managed-services name;
monitor {
bfd-liveliness name {
interface interface;
routing-instance routing-instance;
session-type (multihop | singlehop);
src-ip src-ip;
}
interface name;
ip name {
routing-instance routing-instance;
}
monitor-object name {
bfd-liveliness {
destination-ip name {
interface interface;
routing-instance routing-instance;
session-type (multihop | singlehop);
src-ip src-ip;
weight weight;
}
threshold threshold;
}
interface {
interface-name name {
weight weight;
}
threshold threshold;
}
ip {
destination-ip name {
routing-instance routing-instance;
weight weight;
}
threshold threshold;
}
object-threshold object-threshold;
}
srg-threshold srg-threshold;
}
peer-domain-id name {
peer-id name {
priority priority;
}
}
peer-id id;
preemption;
prefix-list name {
routing-instance routing-instance;
}
process-packet-on-backup;
shutdown-on-failure name;
virtual-ip name {
interface interface;
ip ip;
use-virtual-mac;
}
}
software-upgrade;
traceoptions {
file < filename> <files files> <match match> <size bytes> <(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 Multinode High Availability options on SRX Series Firewalls.
Options
| grid-id |
Grid identifier number.
|
| hardware-upgrade | Enable hardware upgrade state. |
| local-domain-id |
Local domain identifier for four-Node multinode high availability setup. |
| local-id | Define local node identifier. |
| peer-id |
Define peer node related information. |
| peer-domain-id |
Peer domain identifier for 4-Node multinode high availability setup. |
| services-redundancy-group | Define the services redundancy group details. |
| software-upgrade |
Enable software upgrade mode. |
| traceoptions | Define high availability traceoptions. CAUTION: Enabling tracing can adversely impact scale and performance and may increase security risk. We strongly recommend using the trace, tracing, or traceoptions commands only under the guidance of a JTAC support engineer. After collecting the debug information, immediately disable tracing to minimize risk and restore normal system performance. |
Required Privilege Level
interface
Release Information
Statement introduced in Junos OS Release 20.4R1.