IBM Cloud Docs
vSRX deployment

vSRX deployment

Deploy the VMware Cloud Foundation for Classic - Automated instance before the vSRX edge gateway appliance order is placed.

Ordering Juniper gateway devices

The following procedure assumes that you are deploying the IaaS KVM-based Juniper® vSRX high availability (HA) cluster. If you want to build your own gateway by using VMware ESXi™, then order the No-OS gateway option instead. For more information, see Ordering a Bring Your Own Gateway Appliance.

Open the IBM Cloud infrastructure customer portal, then select Infrastructure > Network > Gateway Appliances > Create Gateway.

  • Gateway vendor - Juniper

  • Gateway Appliance

    • Hostname - Provide the hostname for node 1 in the gateway cluster. For example, gateway01. Select a hostname consistent with the existing VCF for Classic - Automated naming convention since the vSRX nodes are manually added to the VCF for Classic - Automated AD/DNS server for hostname resolution.
    • Domain - Enter the applicable domain name for the gateway cluster. For example, myvcsdomain.local, where myvcsdomain.local is the domain that is assigned to the previously deployed VCF for Classic - Automated instance.
    • Select High availability.
      • HA hostname - Provide the hostname for node 2 in the gateway cluster. For example, gateway02. Select a hostname consistent with the existing VCF for Classic - Automated naming convention since the vSRX nodes are manually added to the VCF for Classic - Automated AD/DNS server for hostname resolution.
      • HA Domain - Verify that this value is the same domain name that is provided for node1. For example, myvcsdomain.local

  • Location

    • Select geography, for example, NA South
    • Select dataCenter, for example, Dallas 10

  • POD

    • Select POD where the existing VCF for Classic - Automated instance is deployed to. For example, dal10.pod01
    • Ensure that you order the vSRX in the same POD as your VCF for Classic - Automated instance. VLANs don't span PODs so you must deploy to the correct POD.
    • Determining SoftLayer_Network_Pod

    The setting SoftLayer_Network_Pod refers to a portion of a data center that share a Backend Customer Router (BCR) and usually a front-end counterpart that is known as a Frontend Customer Router (FCR). A Pod primarily denotes a logical location within the network and the physical aspects that support the networks, in contrast to representing a specific physical location.

    A pod is identified by a name, which is unique. A Pod name follows the format dddnn.podii, where ddd is a data center code, nn is the data center number, and pod is a literal string. The value ii is a two-digit number, zero-padded to the left, which corresponds to a Backend Customer Router (BCR) of the data center. For example,

    `dal09.pod01` is Dallas 9, Pod 1 (that is, bcr01)
`ams01.pod01` is Amsterdam 1, Pod 1 (that is, bcr01)

  • Select Dual Processor hardware option - Intel Xeon 5120, 28 core

  • RAM - 192 GB

  • Add-ons

    • Accept default values.

  • Storage Disks

    • Type - RAID 1
    • Number of disks - 2
    • Disk Media - SATA (preselected)
    • Disk Size - 4 TB.

  • Network interface

    • Uplink Port Speeds - 10 Gbps Public and Private Network Uplinks.
    • Ensure that you enable both public and private NICs (four ports total).
    • Add-ons - accept default values. Optionally select an IPv6 address.

Review the order and click Create. Provisioning takes three to four hours.

Post deployment

If you deployed the IaaS KVM-based Juniper vSRX HA Cluster, you can continue with configuration of the vSRX cluster as described in IBM Cloud performing vSRX basics.

If you opted to deploy the No-OS gateway offering, then follow the guidance in Installing an operating system on the gateway to prepare the hosts for your appliance.