Help Center User GuideGetting StartedFAQRelease Notes
 
X
User Guide
Getting Started
FAQ
Release Notes
Contents  

Adding a Cloud Hub Device

You can add an MX Series router, an SRX Series services gateway, or a vSRX instance as a cloud hub device in a hub-and-spoke topology or full mesh topology.

The device templates that are currently supported for cloud hub devices are:

  • MX as SD-WAN Hub

  • SRX as SD-WAN Hub

Note 

  • An MX Series router can be added as a cloud-hub device in brownfield deployment only.

  • An MX Series router can be used as an SD-WAN hub in single-hub and multihoming deployment.

  • When you use an MX Series router as SD-WAN hub, you must configure the NAT pools by using the stage-2 configuration template.

Before You Begin

Create all the resources required for the network point of presence (POP). See Creating a Single POP.

Procedure

To add a cloud hub device:

  1. Select Resources > Cloud Hub Devices.

    The Cloud Hub Devices page appears.

  2. Click the add icon (+).

    The Add Cloud Hub Device page appears.

  3. Complete the configuration according to the guidelines provided in Table 55.
  4. Click Ok. If you want to discard your changes, click Cancel instead.

    If you click Ok, the cloud hub device is created. The information about the new cloud hub device appears on the Cloud Hub Devices page.

Table 55: Fields on the Add Hub Device Page

Field

Description

Name

Enter the name of the cloud hub device.

You can use alphanumeric characters, including special character(-). The maximum length is 15 characters.

Example: MX-cloud-hub

Management Region

Displays the regional server with which the CPE device communicates. The management region name is populated based on the information from the device template.

Example: regional

POP

Select the POP where the hub device needs to be added.

Example: pop_blue

Capability

Select the capability of the cloud hub device. The following options are available:

  • Data—Transmits only data traffic. IPsec data tunnels are configured between spoke and data hub. IPsec OAM tunnels will not be configured between spoke and data hub.

  • OAM—Transmits only OAM traffic. IPsec OAM tunnels are configured between spoke and OAM hub(s). IPsec data tunnels are configured between spoke and data hub(s).

  • Data and OAM—Transmits both data traffic and OAM traffic. Both OAM and Data IPsec tunnels are configured between the spoke and the hub. This is the default capability for the hub device.

    Note: You must configure the first cloud hub device in the network with Data and OAM capability.

Proxy OAM Hub Device

For each hub device with data-only capability, select an OAM hub device to handle the OAM traffic. IPsec OAM tunnel is configured between the spoke and the proxy OAM hub.

Device Template

Select the device template that supports SD-WAN deployment.

Example: MX as SD-WAN Hub

Connectivity

Based on the deployment scenario, the following fields are displayed:

GRE Interfaces

Enter one or more interface names for the generic routing encapsulation (GRE) tunnel. Press Enter to provide multiple values. You configure this field when you select the MX Series router as a cloud hub device.

Example: gr-0/0/1

VT Interfaces

Enter one or more interface names for the virtual tunnel (VT). Press Enter to provide multiple values. You configure this field when you select the MX Series router as a cloud hub device.

Example: vt-0/0/1

MS Interfaces

Enter one or more interface names for the multiservices (MS) . Press Enter to provide multiple values. You configure this field when you select the MX Series router as a cloud hub device.

Example: ms-0/0/1

OAM Traffic Information

(Optional) Select this option if the management connectivity is initiated by Contrail Service Orchestration (CSO).

Management Connectivity

OAM Connectivity

Loopback IP Prefix

Enter an IPv4 address prefix for the loopback interface on the CPE device. The IP address prefix must be a /32 IP address prefix and must be unique across the entire management network.

Example: 192.168.1.1/32

OAM Interface

Select an interface on the cloud hub device to connect to the CSO. The interface is used only for OAM connectivity. The interface names are listed based on the configuration in device template for the cloud hub device.

Example: ge-0/0/1

OAM Interface IP Prefix

Enter an IPv4 address prefix for the OAM interface in the cloud hub device. The OAM IP Prefix must be unique across the entire management network.

  • For NFX250 devices,

    • If USE_SINGLE_SSH feature is enabled in the device template, then enter the IP address prefix as /32.

    • If USE_SINGLE_SSH feature is disabled in the device template, then enter the IP address prefix as /29 or above.

  • For NFX 150 devices, enter the IP address prefix based on the USE_SINGLE_SSH option and the number of VNFs being used.

    For SRX Series services gateways, specify the IP address prefix as /32.

OAM Interface VLAN ID

Enter an OAM VLAN ID for in-band management of the site. If you specify an OAM VLAN ID, then an in-band OAM traffic reaches the site through the selected OAM interface. The range is 0 through 65535.

OAM Gateway

Enter the IP address of the next-hop through which the CSO connectivity is established.

WAN_0

WAN_1

WAN_2

WAN_3

Select a WAN link to enable it. After selecting the link, specify the following information:

  • WAN Interface—Displays the interface name configured in the device template. You cannot modify this field.

    Example: ge-0/0/0

  • Link Type—Select the link type (MPLS or Internet) configured in the device template.

    Example: Internet

  • Address Assignment—Select the method for IP address assignment. The options available are:

    • DHCP—Select DHCP to assign IP address by using a DHCP server.

    • STATIC—Select STATIC to assign a static IP address.

      Example: STATIC

      • Static IP Prefix—Enter a private IPv4 address from the subnet.

        Example: 192.168.0.2/24

      • Gateway IP Address—Enter the gateway IP address of the default route.

        Example: 192.168.0.1

  • Traffic Type—Select the traffic type. The options available are:

    • DATA_ONLY—Select this option if you want to use the WAN link to transmit only data traffic.

    • OAM_AND_DATA—Select this option if you want to use the WAN link to transmit both data traffic and management traffic.

    Example: DATA_ONLY

  • Mapped OAM Hub Device Link—For each WAN interface that is enabled for a DATA-only hub device, you must select a WAN interface on the corresponding proxy OAM hub device for transmitting OAM traffic.

  • Data VLAN ID—(Optional) Enter the VLAN ID that is associated with the data link. A data VLAN identifier is an integer in the range 0–65,535.

    Example: 201

Devices

Serial Number

Enter the serial number of the hub device. The serial number is a unique string of alphanumeric characters and it is case-sensitive.

Example: XXXXXXXXXXXX

User Name

Enter the username that you configured when you set up the device. You use this username to log in to the device. Providing login credentials gives CSO access to the device.

Password

Enter the password that you configured when you set up the device. You use this password to log in to the device. Providing login credentials gives CSO access to the device.

After you add the cloud hub device, select the cloud hub device on the Resources > Cloud Hub Devices page and click Activate Device. The cloud hub device gets activated. During activation, the cloud hub device is discovered and the required details are stored in CSO.

Related Documentation

Help us to improve. Rate this article.
Feedback Received. Thank You!

Ask questions in TechWiki

Check documentation in TechLibrary

Rating by you:      
X

Additional Comments

800 characters remaining

May we contact you if necessary?

Name:
Email:

Need product assistance? Contact Juniper Support

Submit