What is chassis clustering?

What is chassis clustering?

Chassis clustering, also known as the Junos Services Redundancy Protocol (JSRP), provides network node redundancy by grouping a pair of the same kind of supported Juniper Networks secure routers or SRX Series Services Gateways into a cluster. The devices must be running Junos OS with enhanced services.

How do you cluster SRX?

We will configure SRX 240 cluster in active – passive mode.

1. Step 1: Enable Chassis Cluster (Configure Cluster ID and Node ID)
2. Step 2: Configure Control Link and Data Link.
3. Step 3: Configure Redundancy Groups.
4. Step 4: Configure Interfaces.

What are the maximum number of redundancy groups that would be used on a chassis cluster?

128 redundancy groups
You can create up to 128 redundancy groups. The maximum number of redundancy groups is equal to the number of redundant Ethernet interfaces that you configure. You can configure redundancy groups to suit your deployment. You configure a redundancy group to be primary on one node and backup on the other node.

What is the maximum number of SRX Series devices in a chassis cluster?

On SRX Series devices in a chassis cluster, when two logical systems are configured, the scaling limit crosses 13,000, which is very close to the standard scaling limit of 15,000, and a convergence time of 5 minutes results.

What is a redundancy group?

Redundancy groups (RG) in SRX chassis cluster provide high-availability. They fail over from one node to the other in case of failure. You can configure the cluster to monitor physical state of interfaces (interface monitoring) and/or check the reachability of IP addresses (IP monitoring).

How do I enable chassis cluster?

You create two vSRX instances to form a chassis cluster, and then you set the cluster ID and node ID on each instance to join the cluster. When a vSRX instance joins a cluster, it becomes a node of that cluster.

What is redundancy group in Juniper SRX?

Define a redundancy group. Except for redundancy group 0, a redundancy group is a logical interface consisting of two physical Ethernet interfaces, one on each chassis. When the active interface fails, the standby interface becomes active. The logical interface is called a redundant Ethernet interface ( reth ).

How do I get rid of virtual chassis configuration?

To delete an MX Series Virtual Chassis configuration, you must:

1. Delete all Virtual Chassis ports.
2. Remove the definitions and applications of the Virtual Chassis configuration groups.
3. Delete the preprovisioned member information configured at the [edit virtual-chassis] hierarchy level.
4. Delete any configured interfaces.

How to configure chassis clustering on SRX series devices?

After the reboot, the following interfaces are assigned and repurposed to form a cluster: For SRX300 and SRX320 devices, ge-0/0/0 becomes fxp0 and is used for individual management of the chassis cluster. SRX340 and SRX345 devices contain a dedicated port fxp0.

What is the purpose of a chassis cluster?

Chassis cluster includes the synchronization of configuration files and the dynamic runtime session states between the SRX Series devices, which are part of chassis cluster setup. The Junos OS provides high availability on SRX Series device by using chassis clustering.

Why is session persistence important in a chassis cluster?

For SRX Series devices, which act as stateful firewalls, it is important to preserve the state of the traffic between two devices. In a chassis cluster setup, in the event of failure, session persistence is required so that the established sessions are not dropped even if the failed device was forwarding traffic.

Can a swfab interface be used for srx650?

Switching supported ports must be used for swfab interfaces. For SRX650, the swfab member ports must belong to the same GPIM. Members spanning across multiple GPIMs are not supported. New pseudo interfaces – swfab0 and swfab1 are created for Layer 2 fabric functionality.