Importing Data for Multiple POPs

You, as an SP administrator, can use the Import POPs page to import a POP and its associated resources, such as a provider edge device for the POP, a virtualized infrastructure manager (VIM), a container for management network for the VIM, and an element management system (EMS).

Customizing a POP Data File

Procedure

To customize a POP data file:

  1. Select Resources > POPs.
  2. Click Import POPs > Import.

    The Import POPs page appears.

  3. Click the Download Sample JSON link to open and save the sample JSON data file.

    The sample file opens at the bottom of the page.

  4. Save the file to your computer with an appropriate name.

    Example: sample-pop-data.json

    Note You need to retain the file format as .json to successfully upload the POP details to the Administration Portal.

  5. Customize the sample JSON file using the guidelines in Table 34.
  6. Save the customized file.

Table 34: Fields on the POPs Page

 

Field

Description

POP Information

dc_name

Specify the name of the region for this POP.

Example: regional

Note: Administrator should not delete the region name.

name

Specify the name of the POP. You can use an unlimited number of alphanumeric characters, including special characters.

Example: pne-pop10

street

Specify the street address.

Example: 1133 Innovation Way

city

Specify the name of the city.

Example: Sunnyvale.

state

Specify the name of the state.

Example: CA

zip_code

Specify the zip code or postal code for the state.

Example: 94089.

country

Specify the name of the country.

Example: USA

VIM Information

Note: You must add a VIM for a centralized deployment. Do not add a VIM for a distributed deployment.

name

Specify the name of the VIM instance. You can use an unlimited number of alphanumeric characters, including special characters.

Example: vim10

vim_type

Specify the VIM instance type. The default VIM type is cloud.

Example: cloud

address

Specify the IP address of the primary Contrail Configure and Control node for the Contrail Cloud Reference Architecture (CCRA) for this POP.

Example: 10.102.28.148

auth_url

Specify the authentication URL for the OpenStack Keystone.

Example: http://10.102.28.148:5000/v3

default_domain

Specify the name of the OpenStack domain that you configured.

Example: Default.

password

Specify the OpenStack Keystone password that you configured.

Example: contrail123

default_tenant

Specify the name of the OpenStack tenant that you configured.

Example: admin

username

Specify the OpenStack Keystone username that you configured.

Example: admin

Resource Pool

name

Specify a resource pool for each VIM. You can use an unlimited number of alphanumeric characters, including special characters.

Example: ResoucePool123

compute_zone

Specify the availability zone in Contrail OpenStack in which the VMs for network services reside. The default availability zone is nova.

You can run the nova availability-zone-list command on the Contrail OpenStack to find the list of available zones.

Example: nova

Management Network

vld_name

Specify the name of the virtual link descriptor for the management network. The default name is mgmt.

Example: mgmt

vl_name

Specify the name of the management network in Contrail.

Example: mgmt-net

onboard

Specify the onboard value for the management network.

  • true—Import named virtual network object from VIM.

  • false—Create a virtual network in VIM with the specified name.

route_target

Select the route target for the management network in Contrail.

Example: 8887:887

subnet

Specify one or more prefixes that define the subnets for the Contrail Compute nodes. You can use an IPv4 address.

Example: 10.102.82.0/23

EMS Information

name

Specify the name of the EMS application.

Example: Junos Space

ip

Specify the IP address of the Junos Space Web user interface (UI). For a redundant Contrail Service Orchestration, configure the IP address of the Web UI for the primary Junos Space Virtual Appliance.

Example: 10.102.86.12

username

Specify the username of the device administrator that you configured. This user should be assigned the admin role in all the tenants. The default username is super.

Example: super

password

Specify the administrator password that you configured. The default password is juniper123.

You can choose a password that is at least eight characters long and contains characters from at least three of the following four character classes: uppercase letters, lowercase letters, numbers (0 through 9), and special characters.

Example: juniper123

vendor

Specify the vendor for the EMS.

Example: Juniper Networks

version

Specify the version number of the EMS.

Example: 15.1

Device Information

name

Specify the name of the device, such as a physical network element (PNE) for a centralized deployment. You can use any number of alphanumeric characters, including special characters.

Example: PNE-MX10

device_ip

Specify the management IP address of the device.

Example: 192.0.2.15.

pne_package

Specify the name of the package providing metadata and configuration templates needed to program a PNE device for service chain attachments in the case of a vCSO solution. If you configure a PNE for the POP in a centralized deployment, select a software image from the menu:

  • MX as Hybrid WAN IPSec HUB—Default for MX Series router. Select this option for most installations.

  • MX as Gateway for vCPE—Customized device profile with MX configuration that prevents the creation of black holes when an administrative user activates a service at a site.

You must specify the PNE package only for a data center gateway device.

Do not use the SRX Series package for the PE router or the SDN gateway.

assigned_device_profile

Select the name of the configuration image for the SDN gateway or the PE router.

  • MX as Hybrid WAN IPSec HUB—Default for MX Series router. Select this option for most centralized deployments and for all distributed deployments.

  • MX as Gateway for vCPE—Customized device profile with MX Series configuration that prevents the creation of black holes when an administrative user activates a service at a site.

  • SRX as SDWAN Hub—Device profile for an SRX Services Gateway used as a CPE device that offers basic SD-WAN functionality in a distributed deployment. Select this option only if you have been advised to do so by Juniper Networks.

username

Specify the username of the device administrator for logging into the device.

Example: root

password

Specify the password for logging into the device.

Example: pwd123

Uploading a POP Data File

You can use the Administration Portal to import POP data to support tenant services.

Procedure

To upload a POP data file:

  1. Select Resources > POPs.
  2. Click Import POPs > Import.

    The Import POPs page appears.

  3. Click Browse and navigate to the directory containing the POP data file.
  4. Select the file and click Open.
  5. Click Import. If you want to discard the import process, click Cancel instead.

    A success message is displayed indicating that the job was uploaded successfully.