services-redundancy-group
Syntax
services-redundancy-group name { activeness-priority activeness-priority; activeness-probe { bfd-liveliness { destination-ip; interface; minimum-interval; multiplier; routing-instance 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;mandatory routing-instance routing-instance; } backup-signal-route { ip-address;mandatory routing-instance routing-instance; } deployment-type(cloud | hybrid | routing | switching); install-on-failure-route { ip-address; routing-instance routing-instance; } 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; } } 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;mandatory use-virtual-mac; } }
Hierarchy Level
[edit chassis high-availability]
Description
Configure a service redundacy group (SRG). An SRG includes and manages a collection of resources on both nodes of a Multinode High Availability and it fails over between the two devices. You can configure upto 20 SRGs in a Multinode Highavailability setup.
Options
name |
Services redundancy group identifier.
|
|
active-signal-route |
IP address used for route preference advertisement. You must specify the active signal route along with the route-exists policy in the policy-options statement. Signal route required for active role enforcement. When you configure the
|
|
activeness-priority |
Specify priority for the SRG1 in a node to take up the active role in a case where both nodes initialize at the same time. The node where SRG1 is in active state is considered as active node. If you prefer a certain node to take over as the active node on boot, you can do one of the followings:
|
|
activeness-probe |
Specify the probe destination IP address for activeness determination. |
|
backup-signal-route |
Specify the backup signal route to advertise a route with a medium priority. When the HA link is down or the current active node relinquishes active role after any failure, the active signal route is removed from the routing table. The backup overwrites the default routing preference toward the old active node with the medium priority.
|
|
deployment-type |
Deployment type of the Services Redundancy Group.
|
|
install-on-failure-route | Divert the traffic by changing the route in a Multinode High Availability setup during a software upgrade. In this case, traffic still traverses through the node and interface remains up. |
|
managed-services | Enable set of services for the specified SRG. |
monitor |
Specify to configure the BFD and IP monitoring options. |
|
peer-id |
Allows you to choose a specific peer when multiple HA peers are configured globally to the service redundancy group. |
|
preemption |
Allow preemption of activeness based on priority. When you configure the activeness priority (1-254) for the SRG1 and enable the preemptive behavior on both nodes, the preempt option ensures that the node with higher activeness priority always remains active after a failover. |
|
prefix-list | Define a named set of address prefixes. | Associate the IP prefix list to the SRG. A prefix list is a listing of IP prefixes that include the local address of IKE gateway. A prefix list is given a name and is configured within the [edit policy-options] configuration hierarchy. |
process-packet-on-backup |
Enable packet forward engine to forward packets on backup node for the corresponding service redundancy group. When you configure the process packet on back up option, the Packet Forwarding Engine forwards packets on backup node for the corresponding SRG. This configuration processes VPN packets on the backup node even when the node is not active. |
|
services |
Enable IPsec VPN service on a particular SRG. |
|
shutdown-on-failure |
Configure one or multiple Interfaces which are required to be shut down to isolate the node in case of internal failures or during software upgrades. During software upgrades, you can divert the traffic by closing down interfaces on the node. |
|
virtual-ip |
IP address used for activeness determination and enforcement on the switching side. Required for hybrid and default gateway deployments. |
The remaining statements are explained separately. See CLI Explorer.
Required Privilege Level
interface
Release Information
Statement introduced in Junos OS Release 20.4R1.
Multi SRG1s (SRG1+) support is added in Junos OS Release 22.4R1.
install-on-failure-route option is added in Junos OS Release 22.4R2.