- play_arrow vSRX Virtual Firewall Deployment for KVM
- play_arrow Overview
- play_arrow Install vSRX Virtual Firewall in KVM
- Prepare Your Server for vSRX Virtual Firewall Installation
- Install vSRX Virtual Firewall with KVM
- Example: Install and Launch vSRX Virtual Firewall on Ubuntu
- Load an Initial Configuration on a vSRX Virtual Firewall with KVM
- Use Cloud-Init in an OpenStack Environment to Automate the Initialization of vSRX Virtual Firewall Instances
- play_arrow vSRX Virtual Firewall VM Management with KVM
- Configure vSRX Virtual Firewall Using the CLI
- Connect to the vSRX Virtual Firewall Management Console on KVM
- Add a Virtual Network to a vSRX Virtual Firewall VM with KVM
- Add a Virtio Virtual Interface to a vSRX Virtual Firewall VM with KVM
- SR-IOV and PCI
- Upgrade a Multi-core vSRX Virtual Firewall
- Monitor the vSRX Virtual Firewall VM in KVM
- Manage the vSRX Virtual Firewall Instance on KVM
- Recover the Root Password for vSRX Virtual Firewall in a KVM Environment
- play_arrow Configure vSRX Virtual Firewall Chassis Clusters on KVM
-
- play_arrow vSRX Virtual Firewall Deployment for Microsoft Hyper-V
- play_arrow Overview
- play_arrow Install vSRX Virtual Firewall in Microsoft Hyper-V
- play_arrow vSRX Virtual Firewall VM Management with Microsoft Hyper-V
- play_arrow Configure vSRX Virtual Firewall Chassis Clusters
-
- play_arrow vSRX Virtual Firewall Deployment for Contrail
- play_arrow Overview of vSRX Virtual Firewall Service Chains in Contrail
- play_arrow Install vSRX Virtual Firewall in Contrail
- play_arrow vSRX Virtual Firewall VM Management with Contrail
-
- play_arrow vSRX Virtual Firewall Deployment for Nutanix
- play_arrow Overview
- play_arrow Install vSRX Virtual Firewall in Nutanix
-
- play_arrow vSRX Virtual Firewall Deployment for AWS
- play_arrow Overview
- play_arrow Configure and Manage Virtual Firewall in AWS
- Configure an Amazon Virtual Private Cloud for vSRX Virtual Firewall
- Launch a vSRX Virtual Firewall Instance on an Amazon Virtual Private Cloud
- Enroll a vSRX Virtual Firewall on AWS with Juniper ATP Cloud
- Using Cloud-Init to Automate the Initialization of vSRX Virtual Firewall Instances in AWS
- AWS Elastic Load Balancing and Elastic Network Adapter
- Multi-Core Scaling Support on AWS with SWRSS and ENA
- Centralized Monitoring and Troubleshooting using AWS Features
- Deploying vSRX Virtual Firewall 3.0 for Securing Data using AWS KMS
- Configure vSRX Virtual Firewall Using the CLI
- Configure vSRX Virtual Firewall Using the J-Web Interface
- Upgrade Junos OS Software on a vSRX Virtual Firewall Instance
- Remove a vSRX Virtual Firewall Instance on AWS
- Geneve Flow Infrastructure on vSRX Virtual Firewall 3.0
- AWS Gateway Load Balancing with Geneve
- play_arrow Virtual Firewall in AWS Use Cases
-
- play_arrow vSRX Virtual Firewall Deployment for Microsoft Azure
- play_arrow Overview
- play_arrow Deploy vSRX Virtual Firewall from the Azure Portal
- play_arrow Deploy vSRX Virtual Firewall from the Azure CLI
- play_arrow Configure and Manage vSRX Virtual Firewall for Microsoft Azure
- play_arrow Configure Azure Features on vSRX Virtual Firewall and Use Cases
- Deployment of Microsoft Azure Hardware Security Module on vSRX Virtual Firewall 3.0
- Example: Configure an IPsec VPN Between Two vSRX Virtual Firewall Instances
- Example: Configure an IPsec VPN Between a vSRX Virtual Firewall and Virtual Network Gateway in Microsoft Azure
- Example: Configure Juniper ATP Cloud for vSRX Virtual Firewall
-
- play_arrow vSRX Virtual Firewall Deployment for Google Cloud Platform
- play_arrow Overview
- play_arrow Install vSRX Virtual Firewall in Google Cloud
-
- play_arrow vSRX Virtual Firewall Deployment for IBM Cloud
- play_arrow Overview
- play_arrow Installing and Configuring vSRX Virtual Firewall in IBM
- Performing vSRX Virtual Firewall Basics in IBM Cloud
- vSRX Virtual Firewall Readiness Checks in IBM Cloud
- Managing VLANs with a gateway appliance
- Working with the vSRX Virtual Firewall Default Configurations
- Migrating Legacy Configurations to the Current vSRX Virtual Firewall Architecture
- Allowing SSH and Ping to a Public Subnet
- Performing vSRX Virtual Firewall Advanced Tasks in IBM Cloud
- Upgrading the vSRX Virtual Firewall in IBM Cloud
- play_arrow Managing vSRX Virtual Firewall in IBM Cloud
- play_arrow Monitoring and Troubleshooting
-
- play_arrow vSRX Virtual Firewall Deployment for OCI
- play_arrow Overview
- play_arrow Installing vSRX Virtual Firewall in OCI
- play_arrow vSRX Virtual Firewall Licensing
-
Install vSRX Virtual Firewall with VMware vSphere Web Client
The following procedure describes how to install vSRX Virtual Firewall and connect vSRX Virtual Firewall interfaces to the virtual switches for the appropriate applications. Only the vSRX Virtual Firewall virtual switch has a connection to a physical adapter (the uplink) so that all application traffic flows through the vSRX Virtual Firewall VM to the external network.
To install vSRX Virtual Firewall with the VMware vSphere Web Client:
To upgrade an existing vSRX Virtual Firewall instance, see Migration, Upgrade, and Downgrade in the vSRX Virtual Firewall Release Notes.
Download the vSRX Virtual Firewall software package for VMware from the Juniper Networks website.
Note:Do not change the filename of the downloaded software image or the installation will fail.
Validate the vSRX Virtual Firewall .ova file if required. For more information, see Validate the vSRX .ova File for VMware.
Enter the vCenter server hostname or address in your browser (https://<ipaddress>:9443) to access the vSphere Web Client, and log in to the vCenter server with your credentials.
Select a host or other valid parent for a virtual machine and click Actions > All vCenter Actions > Deploy OVF Template.
Note:The Client Integration Plug-in must be installed before you can deploy OVF templates (see your VMware documentation).
Click Browse to locate the vSRX Virtual Firewall software package, and then click Next.
Click Next in the OVF Template Details window.
Click Accept in the End User License Agreement window, and then click Next.
Change the default vSRX Virtual Firewall VM name in the Name box and click Next. It is advisable to keep this name the same as the hostname you intend to give to the VM.
In the Datastore window, do not change the default settings for:
Datastore
Available Space
Table 1 lists the disk formats available to store the virtual disk. You can choose one of the three options listed.
Note:For detailed information on the disk formats, see Virtual Disk Provisioning.
Table 1: Disk Formats for Virtual Disk Storage Disk Format
Description
Thick Provision Lazy Zeroed
Allocates disk space to the virtual disk without erasing the previously stored data. The previous data is erased when the VM is used for the first time.
Thick Provision Eager Zeroed
Erases the previously stored data completely and then allocates the disk space to the virtual disk. Creation of disks in this format is time consuming.
Thin Provision
Allocates only as much datastore space as the disk needs for its initial operations. Use this format to save storage space.
Select a datastore to store the configuration file and virtual disk files in OVF template, and then click Next.
Select your management network from the list, and then click Next. The management network is assigned to the first network adapter, which is reserved for the management interface (fxp0).
Click Finish to complete the installation.
Open the Edit Settings page of the vSRX Virtual Firewall VM and select a virtual switch for each network adapter. Three network adapters are created by default. Network adapter 1 is for the management network (fxp0). To add a fourth adapter, select Network from New device list at the bottom of the page. To add more adapters, see Add vSRX Interfaces.
In Figure 1, network adapter 2 uses the management network for the uplink to the external network.
Figure 1: vSRX Virtual Firewall Edit Settings PageEnable promiscuous mode for the management virtual switch:
With vSRX Virtual Firewall platforms VMware uses the VMXNET 3 vNIC and requires promiscuous mode on the vSwitch for the management interface, fxp0.
This step is not required on vSRX Virtual Firewall 3.0 and there is no need for the ports to be connected to the control plane to have Promiscuous mode enabled.
Select the host where the vSRX Virtual Firewall VM is installed, and select Manage > Networking > Virtual switches.
In the list of virtual switches, select vSwitch0 to view the topology diagram for the management network connected to network adapter 1.
Click the Edit icon at the top of the list, select Security, and select Accept next to Promiscuous mode. Click OK.
Note:vSwitch1 corresponds to network adapter 2, vSwitch2 corresponds to network adapter 3, and so on.
Enable hardware-assisted virtualization to optimize performance of the vSRX Virtual Firewall Routing Engine that runs in a nested VM:
Power off the vSRX Virtual Firewall VM.
Right-click on the vSRX Virtual Firewall VM and select Edit Settings.
On the Virtual Hardware tab, expand CPU, select Expose hardware-assisted virtualization to guest OS, and click OK.
On the Manage tab, select Settings > VM Hardware and expand CPU to verify that the Hardware virtualization option is shown as Enabled.
The default vSRX Virtual Firewall VM login ID is root with no password. By default, vSRX Virtual Firewall is assigned a DHCP-based IP address if a DHCP server is available on the network.