# Juniper vSRX Specifications ## Licensing[​](#licensing "Direct link to Licensing") Bring Your Own License (BYOL) products require a valid license. You are responsible for purchasing and managing your own licenses from Juniper Networks. To purchase a software license, contact your Juniper sales representative or partners. * [Juniper Networks](https://www.juniper.net/us/en/how-to-buy/form.html) * [Find Juniper Networks Partners](https://www.juniper.net/us/en/partners.html) * [Juniper vSRX BYOL License SKU Information](https://www.juniper.net/documentation/us/en/software/license/licensing/topics/topic-map/vsrx-licensing.html#id-vsrx-license-model-numbers-for-aws-and-microsoft-azure-cloud__d11e33) ## Support[​](#support "Direct link to Support") vSRX support is available for BYOL licenses. Contact your Juniper sales representative or partner to purchase a license and support contract. * [Juniper Community](https://community.juniper.net/home) * [Juniper Technical Support](https://support.juniper.net/support/requesting-support/) ## Juniper vSRX[​](#juniper-vsrx "Direct link to Juniper vSRX") * For more information about Juniper vSRX Series, see the [vSRX Virtual Firewall Product](https://www.juniper.net/us/en/products/security/srx-series/vsrx-virtual-firewall.html) page. * [Juniper Networks vSRX Virtual Firewall Data Sheet](https://www.juniper.net/content/dam/www/assets/datasheets/us/en/security/vsrx-virtual-firewall-datasheet.pdf) * [vSRX Documentation](https://www.juniper.net/documentation/product/us/en/vsrx/) | | 2 Cores | 5 Cores | 9 Cores | | ----------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- | ------- | ------- | | Memory | 4 GB | 8 GB | 16 GB | | Software Package | Standard | | | | Virtual Data Interfaces Supported (Default/Max) | 8 / 8 | | | | System Reserved Interfaces | Fxp0 (Management)
Ge-0/0/0 (WAN/SSH) | | | | Available License Type | BYOL | | | | Access Methods | SSH
Web Console | | | | Image Version | See [Available Image Versions](https://docs.equinix.com/network-edge/vendors-devices/ne-certified-vnfs.md#juniper) | | | | Restricted CLI Commands | None for Self-Configured vSRX devices. See [restricted commands](#restricted-commands) below for Equinix-Managed device restrictions. | | | | Deployment Options | Single
Redundant
Cluster | | | ## Juniper vSRX SD-WAN[​](#juniper-vsrx-sd-wan "Direct link to Juniper vSRX SD-WAN") | | 2 Cores | 5 Cores | 9 Cores | | ----------------------------------------------- | ------------------------------------------------------------------------------------------------------------------ | ------- | ------- | | Memory | 4 GB | 8 GB | 16 GB | | Software Package | Standard | | | | Virtual Data Interfaces Supported (Default/Max) | 8 / 8 | | | | Reserved Interfaces | Fxp 0 (Management)
Ge-0/0/0 (WAN/SSH) | | | | Available License Type | BYOL | | | | Access Methods | SSH
Web Console | | | | Image Version | See [Available Image Versions](https://docs.equinix.com/network-edge/vendors-devices/ne-certified-vnfs.md#juniper) | | | | Deployment Options | Single
Redundant
Cluster | | | For information about Juniper limitations, see [Juniper vSRX Limitations.](https://docs.equinix.com/en-us/Content/Interconnection/NE/deploy-guide/Juniper/NE-Juniper-SRXFortinet-restrictcomms.htm) For information about creating a Juniper vSRX cluster, see [Creating a Juniper vSRX Cluster](https://docs.equinix.com/en-us/Content/Interconnection/NE/deploy-guide/Juniper/NE-create-juniper-cluster.htm). ### Creating a Juniper vSRX SD-WAN Device[​](#creating-a-juniper-vsrx-sd-wan-device "Direct link to Creating a Juniper vSRX SD-WAN Device") A Juniper vSRX SD-WAN edge device can be ordered and created on Network Edge. You can create a cluster, redundant devices, or a single edge device. Juniper SD-WANs require you to bring your own license. This topic demonstrates how to create a single Juniper device. Before creating your Juniper SD-WAN in Network Edge, do the following in Juniper’s Contrail Service orchestrator: 1. Upload the license file to generate a bootstrap configuration of the device. 2. Provide the user name and public key for accessing the device. 3. Apply an ACL that supports UDP destination ports 500 & 4500, and TCP port destination 7894. This ACL is necessary to make sure the vSRX SD-WAN is accessible by the orchestrator. 4. Finalize the device. It can take several minutes for the device to be active and visible on the orchestrator. Do not make any changes during this time. 5. Sign into the device and start an SFTP service. This allows the orchestrator to push the template file to the vSRX instance. 6. Select the template SRX as SD-WAN CPE then clone it to create your own configuration. > **Tip** > > SD-WAN devices can be launched using Network Edge APIs. For more information, see [Network Edge API – Launch SD-WAN Device](https://docs.equinix.com/en-us/Content/KnowledgeCenter/NE/GettingStarted/Launch-SDWAN-Device.htm). ## Juniper vSRX Limitations[​](#juniper-vsrx-limitations "Direct link to Juniper vSRX Limitations") This topic provides a list of commands that are restricted on Juniper vSRX, and information about certificates and version upgrade limitations. ### Restricted Commands[​](#restricted-commands "Direct link to Restricted Commands") The following commands are restricted on Equinix-Managed Juniper vSRX devices: * Any command starting from `request`. Exceptions: `request system reboot`. * Start shell. * Show interfaces fxp0. * Any command starting from `ssh`. * Any command starting from `telnet`. * Any command starting from `restart`. * Any command starting from `file`. * Show system license keys. * Any system level commands or commands that include the word `system`. * Any config on interface `ge-0/0/0`. * Any config on interface `fxp0`. * Any config on interface `loopback 0 unit 10`. * Any config or command that has `routing-instance external`. * Any command that has `security-zone external`. * Any command that has `security policies from-zone external`. * Any command that has `routing-options static`. ### Version Upgrade Limitations[​](#version-upgrade-limitations "Direct link to Version Upgrade Limitations") * Always save a copy of certificates before performing vSRX upgrades. * Once the vSRX upgrade is complete, certificates are required to be copied and loaded back into vSRX configuration as they were before the upgrade. ### Enabling Certificates[​](#enabling-certificates "Direct link to Enabling Certificates") For information on enabling certificates on Juniper, see .