Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

TechLibrary
Navigation
Table of Contents
Guide That Contains This Content
[+] Expand All
[-] Collapse All

Creating a Single POP

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

Creating a single POP involves adding several types of objects, depending on whether the POP is for a centralized or distributed deployment. The sections in this topic describe how to add each type of object to a POP in Administration Portal. You must finish the steps in each section to create the objects that you need for a single POP and to save the POP successfully. This topic includes the following sections:

Adding Information About the POP

To create a a single POP and to add basic information to the POP:

  1. Click Resources > POPs.

    The POPs page appears.

  2. Click the plus icon(+) .

    The Add POP page appears.

  3. Complete the configuration settings according to the guidelines provided in Table 1.
  4. Click Next and proceed to "Adding a Device".

    The Add Device table appears.

Table 1: Fields on the Add POP page

Field

Description

Region

Select the name of the region for this POP.

Example: regional

Note: The administrator must not delete the region name.

POP Name

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

Example: north-east.

Street Address

Specify the street address. You can use an unlimited number of alphanumeric characters, including special characters.

Example: 1133 Innovation Way

City

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

Example: Sunnyvale

State/Province

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

Example: California

ZIP/Postal Code

Specify the zip code or postal code for the country. You can use an unlimited number of alphanumeric characters, including special characters.

Example: 94089

Country

Select the name of the country.

Example: USA

Adding a Device

You can add the following devices to a POP:

  • A router that acts as an SDN gateway and provides a Layer 3 routing service to customer sites for a centralized deployment.
  • A router that acts as a provider edge (PE) router and an IPsec concentrator for a distributed deployment.

To add a device:

  1. Click Resources > POPs > + .

    The Add POP page appears.

  2. Complete the configuration settings according to the guidelines provided in Table 1.
  3. Click Next.

    The Device section appears.

  4. Click the plus icon (+) in the Add Device section.

    The Add Device page appears.

  5. Complete the configuration according to the guidelines in Table 2.
  6. Click Save.
  7. Proceed as follows:

Table 2: Fields on the Add Device Page

Field

Description

Name

Specify the name of the device, such as a data center gateway, a PE router, or an IPsec concentrator. Some device examples are listed below.

  • An MX Series router used as an SDN gateway in a centralized deployment.
  • An MX Series router used as a provider edge (PE) router in a distributed deployment.
  • An SRX Services Gateway router or a vSRX instance used as a CPE device in a distributed deployment.

You can use letters, numbers, spaces, periods, dashes, underscores, commas, @, #, $, %, &, and *. Maximum length is 255 characters.

Example: MX-router-10

Family

Select the product family for the device.

Example: MX

Device Template

Select the name of the device template for the device:

  • Juniper-MX-MIS—Customized device template for an MX Series router that prevents the creation of black holes when an administrative user activates a service at a site. Select this option only if you have been advised to do so by Juniper Networks.
  • SDN-GW-MX—Default template for MX Series router. Select this option for MX routers in centralized and distributed deployments unless Juniper Networks advises use of the Juniper-MX-MIS device template.
  • SRX_Basic_SDWAN_HUB—Device template 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.
  • SRX_deployment_option_1—Device template for an SRX Services Gateway or a vSRX used as a CPE device in a distributed deployment.
  • NFX_deployment_option_1—Device template for an NFX device in distributed deployment. This template supports port-forwarding with Contrail Service Orchestration initiated connection.
  • SRX_Managed_Internet_CPE—Device template to manage an SRX Services Gateway devices for a managed internet service.
  • NFX_Managed_Internet_CPE—Device template to manage an NFX device for a managed internet service.
  • NFX_deployment_option_4—Device template for an NFX device in distributed deployment. This template supports outbound SSH, which is the device initiated connection, with port-forwarding capability.
  • vSRX-VNF-NFX—Device template for a vSRX VNF application on an NFX platform for a distributed deployment.

Type of Device

Select the type of device:

  • PNE—Device is managed by the EMS.

    Use this option for devices, such as data center gateway, in a centralized deployment, for an SRX Services Gateway or a vSRX used as a CPE device in a distributed deployment, and for PE routers in a distributed deployment that you want the EMS to manage.

  • PE/IPsec—Device is not managed by the EMS.

    Use this option for devices, such as provider edge (PE) router or IPsec concentrator, in a distributed deployment that you do not want the EMS to manage.

PNE package

If you specified that the device is a PNE for a centralized deployment, select the name of the package that contains metadata and configuration instructions for the PNE:

  • SRX—Use with SRX Series device template.
  • Juniper-MX—Use with the SDN-GW-MX device template.
  • Juniper-MX-MIS—Customized device template with MX Series configuration that prevents the creation of black holes when an administrative user activates a service at a site. Use with the Juniper-MX-MIS device template.

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

Do not use the SRX Series package for the MX router.

Management Type

Specify the management type for the PE device. The following options are available:

  • Managed—Select Managed if you use Contrail Service Orchestration to manage the device.
  • Unmanaged—Select Unmanaged if you use another application to manage the device.

Example: Unmanaged

Device IP

Specify the IPv4 address of the management interface for the device.

Example: 192.0.2.15

Internet Gateway (optional)

If you specified that the device is a PE router or an IPsec concentrator for a distributed deployment, then specify the IPv4 address of the Internet gateway. You can also specify a list of public IP addresses of the Internet Key Exchange (IKE) gateways on this device.

Example: 192.0.2.20

User Name

Specify the username that you configured when you set up the device. You use this username to log into the device. Providing login credentials gives Contrail Service Orchestration access to the device.

Password

Specify the password that you configured when you set up the device. You use this password to log into for the device. Providing login credentials gives Contrail Service Orchestration access to the device.

Adding a VIM

For a centralized deployment, you must specify information about Contrail Cloud Platform, which provides the VIM.

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

To add a VIM:

  1. Click Resources > POPs > + .

    The Add POP page appears.

  2. Complete the configuration settings according to the guidelines provided in Table 1.
  3. Click Next.

    The Device section appears.

  4. Click Next.

    The VIM page appears.

  5. In the Connection Information section, specify details for the Contrail Cloud Platform that provides the VIM for this POP.
  6. Complete the configuration according to the guidelines in Table 3.
  7. In the Network Information section, click the plus icon (+) to add each resource pool.
  8. In the Network Information section, specify details for the management network in Contrail.

    You can either specify details for a management network that you already created in Contrail or specify details for a new management network that Administration Portal notifies Contrail to automatically create.

  9. If this POP has a direct connection to the Internet, in the Internet Network section, click the plus icon (+) icon to add information about the Internet network in Contrail.
  10. Click Save.
  11. Proceed as follows:
    • If you use virtualized network functions (VNFs) that require an EMS other than the EMS microservice, click Next and proceed to "Adding an EMS".
    • If you do not need an additional EMS, click 5 (Summary) and proceed to Reviewing and Saving the POP Configuration Settings.

Table 3: Fields on the Add Cloud VIM Page

Field

Guidelines

Name

Specify the name of the virtualized infrastructure manager (VIM) for a centralized deployment. You can add multiple VIMs to a point of presence (POP). You can use letters, numbers, spaces, periods, dashes, underscores, commas, @, #, $, %, &, and *. Maximum length is 255 characters.

Example: vcpe-vim

Type

View the VIM type. The default VIM type is cloud.

Example: Cloud

Connection Information

IP address

Specify the IPv4 address of the Contrail Controller node in the Contrail Cloud Platform that provides the virtualized infrastructure manager (VIM). If you use a high availability (HA) configuration for the Contrail Cloud Platform, specify the virtual IP address of the Contrail Controller node.

Example: 10.102.28.36

Auth URL

Specify the authentication URL for the OpenStack Keystone.

Example: http://ip:5000/v3

User Name

Specify the OpenStack Keystone username that you configured.

Example: admin

Password

Specify the OpenStack Keystone password that you configured.

Example: contrail123

Domain

Specify the name of the OpenStack domain that you configured.

Example: default

Tenant

Specify the name of the OpenStack tenant that you configured.

Example: admin

Network Information

Resource Pools

Resource Pool Name

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

Example: north-east.

Compute Zone

Specify the availability zone in Contrail OpenStack in which the virtual machines 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

  

Does Management Network Exists?

Specify whether to use an existing virtual network in Contrail OpenStack or to create a new one.

  • yes—Import the named virtual network from Contrail OpenStack.
  • no—Create a virtual network in Contrail OpenStack with the specified name.

Management Network Name

Specify the name of the existing management network in Contrail or the new management network that you want to create in Contrail.

Example: mgmt-net

Management Network Information

 

Route Target

Specify one or more route targets for the existing management network in Contrail or the new management network that you want to create in Contrail.

Example: 64512:10000.

Subnet

Specify one or more prefixes that define the subnets for the Contrail Compute nodes. You can use an IPv4 address. Specify one or more IPv4 prefixes for the existing network in Contrail or the new network that you want to create in Contrail.

Example: 192.0.2.0/24.

Internet Network Information

 

Network Name

Specify the name of the Internet network name.

Example: int-net

Does Exist

Specify whether to use an existing virtual network in Contrail OpenStack or to create a new one.

  • True—Import the named virtual network from Contrail OpenStack.
  • False—Create a virtual network in Contrail OpenStack with the specified name.

Route Target

Select the route target for the internet network in Contrail.

Example: 64512:10000.

Subnet

Select the prefix that defines the subnet for the Contrail Compute nodes.

You can use an IPv4 address.

Example: 192.0.2.0/24.

Service Profile Information

 

Profile Name

Specify the name of the service profile in a VIM instance. Create one or more service profiles if you use a dedicated OpenStack Keystone for Contrail Service Orchestration in a centralized deployment. A service profile specifies the Contrail OpenStack tenant, domain, and login credentials. After Contrail Service Orchestration authenticates a tenant (customer), it uses the information in the service profile to provide access to Contrail OpenStack.

Example: vim-service-profile

Tenant Name

Specify the infra tenant for whom you want to assign the service profile.

Example:test-tenant

Domain Name

Specify the Infra domain name.

Example:Default

User Name

Specify the username of the tenant.

Example: admin

Password

Specify the password for the tenant user.

Example: password123

Default Service Profile

Specify the name of the default service profile if you use a dedicated OpenStack Keystone for Contrail Service Orchestration. If you do not specify a service profile when you configure the tenant, Contrail Service Orchestration uses the default profile to authenticate the tenant.

Example: default-service-profile

Adding an EMS

Configure an element management system (EMS) if you use virtualized network functions (VNFs) that require an EMS other than the EMS microservice.

To add an EMS:

  1. Click Resources > POPs > + .

    The Add POP page appears.

  2. Complete the configuration settings according to the guidelines provided in Table 1.
  3. Click Next.

    The Device section appears.

  4. Click Next.

    The VIM page appears.

  5. Click Next.

    The EMS page appears.

  6. Click the plus icon (+) to add the EMS.
  7. Complete the configuration according to the guidelines in Table 4.
  8. Click Save.
  9. Click Next to review the configuration settings for the POP.

Table 4: Fields on the Add EMS Page

Field

Guidelines

Name

Name of the EMS. This field is auto-populated with the name that you specified when you deployed the Junos Space Virtual Appliance.

Example: Junos Space

IP

Specify the IPv4 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: 192.0.2.3.

Vendor

Specify the vendor for the EMS.

Example: Juniper Networks

Version

Specify the version number of the EMS. The default version is 15.1.

Example: 15.1

Authentication URL

Specify the authentication URL for the EMS application.

User Name

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.

Example: juniper123

Reviewing and Saving the POP Configuration Settings

After you have configured a POP and its associated resources, you can review and save a copy of the configuration settings. Finally, you must save the POP that you configured.

  1. Click Resources > POPs > + .

    The Add POP page appears.

  2. Complete the configuration settings according to the guidelines provided in Table 1.
  3. Click Next.

    The Device section appears.

  4. Click Next.

    The VIM page appears.

  5. Click Next.

    The EMS page appears.

  6. Click Next.

    The Summary page appears.

  7. Click Summary > Edit to edit the configuration settings of the objects that you configured.
  8. Click Download POP Payload to save a JSON file of the configuration settings of the objects that you configured.
  9. Click OK to save the POP configuration. If you want to discard your changes, click Cancel instead.
 

Related Documentation

 

Modified: 2018-01-23

Download This Guide

 

Related Documentation

 

Modified: 2018-01-23

Previous Page Next Page