- 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 VMware
- play_arrow Overview
- play_arrow Install vSRX Virtual Firewall in VMware
- play_arrow vSRX Virtual Firewall VM Management with VMware
- play_arrow Configure vSRX Virtual Firewall Chassis Clusters in VMware
-
- 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 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
-
Requirements for vSRX Virtual Firewall on Contrail
Software Requirements
Table 1 lists the system software requirement specifications when deploying vSRX Virtual Firewall on Juniper Networks Contrail. The table outlines the Junos OS release in which a particular software specification for deploying vSRX Virtual Firewall on KVM was introduced. You will need to download a specific Junos OS release to take advantage of certain features.
Component | Specification | Junos OS Release Introduced |
---|---|---|
Hypervisor support | Linux KVM | Junos OS Release 15.1X49-D20 and Junos OS Release 17.3R1 |
Memory | 4 GB | Junos OS Release 15.1X49-D20 and Junos OS Release 17.3R1 |
8 GB | Junos OS Release 15.1X49-D70 and Junos OS Release 17.3R1 | |
Disk space | 20 GB IDE drive | Junos OS Release 15.1X49-D20 and Junos OS Release 17.3R1 |
vCPUs | 2 vCPUs Note: The Contrail compute node must bare metal since vSRX Virtual Firewall as a VNF does not support nested virtualization. | Junos OS Release 15.1X49-D20 and Junos OS Release 17.3R1 |
5 vCPUs Note: The Contrail compute node must bare metal since vSRX Virtual Firewall as a VNF does not support nested virtualization. | Junos OS Release 15.1X49-D70 and Junos OS Release 17.3R1 | |
vNICs | Up to 16 vNICs
| Junos OS Release 15.1X49-D20 and Junos OS Release 17.3R1 |
Table 2 lists the software specifications on the vSRX Virtual Firewall.
Flavor Name | vCPU | Junos OS Release Introduced |
---|---|---|
Hypervisor support | Linux KVM | Junos OS Release 18.2R1 or later release |
Memory | 4 GB | Junos OS Release 18.2R1 or later release |
8 GB | Junos OS Release 18.2R1 or later release | |
Disk space | 20 GB IDE drive | Junos OS Release 18.2R1 or later release |
vCPUs | 2 vCPUs | Junos OS Release 18.2R1 or later release |
5 vCPUs | Junos OS Release 18.2R1 or later release | |
vNICs | Up to 16 vNICs
| Junos OS Release 18.2R1 or later release |
Contrail Recommendations for vSRX Virtual Firewall
Table 3 lists the recommended software versions to run vSRX Virtual Firewall on Contrail.
Software | Version | Supported Release |
---|---|---|
Contrail | 2.20 | Junos OS Release 15.1X49-D20 and Junos OS Release 17.3R1 or later release |
3.1 | Junos OS Release 15.1X49-D60 and Junos OS Release 17.3R1 or later release | |
3.5 | Junos OS Release 18.4R1 | |
OpenStack | Juno or Icehouse | Junos OS Release 15.1X49-D20 and Junos OS Release 17.3R1 or later release |
Juno or Kilo | Junos OS Release 15.1X49-D60 and Junos OS Release 17.3R1 or later release | |
Host OS | Ubuntu 14.04.2 | Junos OS Release 15.1X49-D20 and Junos OS Release 17.3R1 or later release |
Linux Kernel | 3.16 | Junos OS Release 15.1X49-D20 and Junos OS Release 17.3R1 or later release |
We recommend that you enable hardware-based virtualization on the host machine. You can verify CPU compatibility here: http://www.linux-kvm.org/page/Processor_support. See Contrail - Server Requirements to review any additional requirements for Contrail.
Table 4 lists the contrail recommendations for vSRX Virtual Firewall.
Software | Version | Supported Release |
---|---|---|
Contrail | 3.1 | Junos OS Release 18.2R1 or later release |
3.2 | Junos OS Release 18.2R1 or later release | |
5.X | Junos OS Release 19.3R1 or later release | |
OpenStack | Centos 7 or 8 | Junos OS Release 18.2R1 or later release |
Host OS | Ubuntu 14.04.2 | Junos OS Release 18.2R1 or later release |
Linux Kernel | Queens or later | Junos OS Release 18.2R1 or later release |
Hardware Recommendations
Table 5 lists the hardware specifications for the host machine that runs the vSRX Virtual Firewall VM.
Component | Specification |
---|---|
Host memory size | 4 GB (minimum) . |
Host processor type | Intel x86_64 multicore CPU Note: DPDK requires Intel Virtualization VT-x/VT-d support in the CPU. See About Intel Virtualization Technology. |
Virtual network adapter | VMXNet3 device or VMWare Virtual NIC Note: Virtual Machine Communication Interface (VMCI) communication channel is internal to the ESXi hypervisor and the vSRX Virtual Firewall VM. |
Best Practices for Improving vSRX Virtual Firewall Performance
Review the following practices to improve vSRX Virtual Firewall performance.
NUMA Nodes
The x86 server architecture consists of multiple sockets and multiple cores within a socket. Each socket also has memory that is used to store packets during I/O transfers from the NIC to the host. To efficiently read packets from memory, guest applications and associated peripherals (such as the NIC) should reside within a single socket. A penalty is associated with spanning CPU sockets for memory accesses, which might result in nondeterministic performance. For vSRX Virtual Firewall, we recommend that all vCPUs for the vSRX Virtual Firewall VM are in the same physical non-uniform memory access (NUMA) node for optimal performance.
The packet forwarding engine (PFE) on the vSRX Virtual Firewall might become
unresponsive if the NUMA nodes topology properties in OpenStack includes
the line hw:numa_nodes=2
to spread the instance’s
vCPUs across multiple host NUMA nodes. We recommend that you remove
the hw:numa_nodes=2
line from OpenStack to ensure that
the PFE functions properly.
PCI NIC-to-VM Mapping
If the node on which vSRX Virtual Firewall is running is different from the node
to which the Intel PCI NIC is connected, then packets will have to
traverse an additional hop in the QPI link, and this will reduce overall
throughput. On a Linux host OS, install the hwloc
package
and use the lstopo
command to view information about relative
physical NIC locations. On some servers where this information is
not available, refer to the hardware documentation for the slot-to-NUMA
node topology.
Mapping Virtual Interfaces to a vSRX Virtual Firewall VM
To determine which virtual interfaces on your Linux host OS map to a vSRX Virtual Firewall VM:
Use the
virsh list
command on your Linux host OS to list the running VMs.content_copy zoom_out_maphostOS# virsh list
content_copy zoom_out_mapId Name State ---------------------------------------------------- 25 instance-00000060 running 31 instance-0000005b running 34 instance-000000bd running 35 instance-000000bc running
Use the
virsh domiflist vsrx-name
command to list the virtual interfaces on that vSRX Virtual Firewall VM.content_copy zoom_out_maphostOS# virsh domiflist 31
content_copy zoom_out_mapInterface Type Source Model MAC ------------------------------------------------------- tapd3d9639c-d5 ethernet - virtio 02:d3:d9:63:9c:d5 tapc3c3751a-37 ethernet - virtio 02:c3:c3:75:1a:37 tap8af29333-1b ethernet - virtio 02:8a:f2:93:33:1b tapf0387bee-9b ethernet - virtio 02:f0:38:7b:ee:9b tap04e4b59a-91 ethernet - virtio 02:04:e4:b5:9a:91
Note:The first virtual interface maps to the fxp0 interface in Junos OS.
Interface Mapping for vSRX Virtual Firewall on Contrail
Each network adapter defined for a vSRX Virtual Firewall is mapped to a specific interface, depending on whether the vSRX Virtual Firewall instance is a standalone VM or one of a cluster pair for high availability. The interface names and mappings in vSRX Virtual Firewall are shown in Table 6 and Table 7.
Note the following:
In standalone mode:
fxp0 is the out-of-band management interface.
ge-0/0/0 is the first traffic (revenue) interface.
In cluster mode:
fxp0 is the out-of-band management interface.
em0 is the cluster control link for both nodes.
Any of the traffic interfaces can be specified as the fabric links, such as ge-0/0/0 for fab0 on node 0 and ge-7/0/0 for fab1 on node 1.
Table 6 shows the interface names and mappings for a standalone vSRX Virtual Firewall VM.
Network Adapter | Interface Name in Junos OS for vSRX Virtual Firewall |
---|---|
1 | fxp0 |
2 | ge-0/0/0 |
3 | ge-0/0/1 |
4 | ge-0/0/2 |
5 | ge-0/0/3 |
6 | ge-0/0/4 |
7 | ge-0/0/5 |
8 | ge-0/0/6 |
Table 7 shows the interface names and mappings for a pair of vSRX Virtual Firewall VMs in a cluster (node 0 and node 1).
Network Adapter | Interface Name in Junos OS for vSRX Virtual Firewall |
---|---|
1 | fxp0 (node 0 and 1) |
2 | em0 (node 0 and 1) |
3 | ge-0/0/0 (node 0)ge-7/0/0 (node 1) |
4 | ge-0/0/1 (node 0)ge-7/0/1 (node 1) |
5 | ge-0/0/2 (node 0)ge-7/0/2 (node 1) |
6 | ge-0/0/3 (node 0)ge-7/0/3 (node 1) |
7 | ge-0/0/4 (node 0)ge-7/0/4 (node 1) |
8 | ge-0/0/5 (node 0)ge-7/0/5 (node 1) |
vSRX Virtual Firewall Default Settings on Contrail
vSRX Virtual Firewall requires the following basic configuration settings:
Interfaces must be assigned IP addresses.
Interfaces must be bound to zones.
Policies must be configured between zones to permit or deny traffic.
Table 8 lists the factory default settings for the vSRX Virtual Firewall security policies.
Source Zone | Destination Zone | Policy Action |
---|---|---|
trust | untrust | permit |
trust | trust | permit |
untrust | trust | deny |