Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation
Guide That Contains This Content
[+] Expand All
[-] Collapse All

    Enabling Chassis Cluster Formation

    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. With the exception of unique node settings and management IP addresses, nodes in a cluster share the same configuration.

    You can deploy up to 255 chassis clusters in a Layer 2 domain. Clusters and nodes are identified in the following ways:

    • The cluster ID (a number from 1 to 255) identifies the cluster.
    • The node ID (a number from 0 to 1) identifies the cluster node.

    Generally, on SRX Series devices, the cluster ID and node ID are written into EEPROM. On the vSRX instance, vSRX stores and reads the IDs from boot/loader.conf and uses the IDs to initialize the chassis cluster during startup.

    Prerequisites

    Ensure that your vSRX instances comply with the following prerequisites before you enable chassis clustering:

    • You have committed a basic configuration to both vSRX instances that form the chassis cluster. See Configuring vSRX Using the CLI.
    • Use show version in Junos OS to ensure that both vSRX instances have the same software version.
    • Use show system license in Junos OS to ensure that both vSRX instances have the same licenses installed.

    You must set the same chassis cluster ID on each vSRX node and reboot the vSRX VM to enable chassis cluster formation.

    1. In operational command mode, set the chassis cluster ID and node number on vSRX node 0.
      user@vsrx0>set chassis cluster cluster-id number node 0 reboot
    2. In operational command mode, set the chassis cluster ID and node number on vSRX node 1.
      user@vsrx1>set chassis cluster cluster-id number node 1 reboot

    Note: The vSRX interface naming and mapping to vNICs changes when you enable chassis clustering. See Interface Naming and Mapping for a summary of interface names and mappings for a pair of vSRX VMs in a cluster (node 0 and node 1).

    Modified: 2017-09-26