Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


vSRX Virtual Firewall Cluster Staging and Provisioning in Hyper-V

Staging and provisioning a vSRX Virtual Firewall cluster on a Hyper-V host computer includes the following tasks:


Starting in Junos OS Release 15.1X49-D100 and Junos OS Release 17.4R1, support for chassis clustering to provide network node redundancy is only available on Windows Hyper-V Server 2016.

Deploying the VMs and Additional Network Adapters in Hyper-V

The vSRX Virtual Firewall cluster uses three interfaces exclusively for clustering (the first two are predefined):

  • Out-of-band management interface (fxp0).

  • Cluster control link (em0).

  • Cluster fabric links (fab0 and fab1). For example, you can specify ge-0/0/0 as fab0 on node0 and ge-7/0/0 as fab1 on node1.

A cluster requires three interfaces (two for the cluster and one for management) and additional interfaces to forward data. This section outlines how to create the control link and fabric link connections, and to map all data interfaces to network adapters.


For an overview on the procedure to add virtual switches and map the virtual switch to a network adapter, see Add vSRX Interfaces

Creating the Data Interfaces Using Hyper-V

To map all data interfaces to the desired network adapters:

  1. If necessary, open the Hyper-V Manager by selecting Start > Administrative Tools > Hyper-V Manager.
  2. From the Hyper-V Manager, select Action > Virtual Switch Manager. The Virtual Switch Manager appears.
  3. Under the Virtual Switches section, select New virtual network switch. The Create Virtual Switch pane appears (see Figure 1).
  4. Select Internal as the type of virtual switch. Internal allows communication between virtual machines on the same Hyper-V server, and between the virtual machines and the management host operating system.
  5. Select Create Virtual Switch. The Virtual Switch Properties page appears (see Figure 2).
  6. Specify a name for the data interface virtual switch. Leave the other virtual switch properties at their default settings.
  7. Click OK and then click Yes to apply networking changes and to close the Virtual Switch Manager window.
  8. Right-click the vSRX Virtual Firewall VM and select Settings from the context menu. From the Settings dialog for the vSRX Virtual Firewall VM, the Hardware section, click Network Adapter to access the Network Adapter pane. The Network Adapter pane appears (see Figure 3). Assign network adapter 3 as the data interface (fab 0 or fab 1) virtual switch.
  9. From the Virtual switch drop-down assign data interface to the virtual switch.
  10. From the Network Adapter pane, select Advanced Features. Select the Enable MAC address spoofing check box to enable the MAC address spoofing function for the network adapter. MAC address spoofing is a requirement for the data interfaces included in the redundancy groups.
  11. Click OK and then click Yes to apply network adapter changes. The data interface will be connected through the data virtual switch.

Prestaging the Configuration from the Console

The following procedure explains the configuration commands required to set up the vSRX Virtual Firewall chassis cluster. The procedure powers up both nodes, adds the configuration to the cluster, and allows SSH remote access.

  1. Log in as the root user. There is no password.
  2. Start the CLI.
  3. Enter configuration mode.
  4. Copy the following commands and paste them into the CLI:
  5. Set the root authentication password by entering a cleartext password, an encrypted password, or an SSH public key string (DSA or RSA).
  6. To enable SSH remote access:
  7. To enable IPv6:

    This step is optional and requires a system reboot.

  8. Commit the configuration to activate it on the device.
  9. When you have finished configuring the device, exit configuration mode.

Connecting and Installing the Staging Configuration

After the vSRX Virtual Firewall cluster initial setup, set the cluster ID and the node ID, as described in Configure a vSRX Chassis Cluster in Junos OS.

After reboot, the two nodes are reachable on interface fxp0 with SSH. If the configuration is operational, the show chassis cluster status command displays output similar to that shown in the following sample output.

vSRX Virtual Firewall> show chassis cluster status

A cluster is healthy when the primary and secondary nodes are present and both have a priority greater than 0.

Release History Table
Starting in Junos OS Release 15.1X49-D100 and Junos OS Release 17.4R1, support for chassis clustering to provide network node redundancy is only available on Windows Hyper-V Server 2016.