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 single POP and to add basic information to the POP:
- Click Resources > POPs.
The POPs page appears.
- Click the plus icon (+) .
The Add POP page appears.
- Complete the configuration settings according to the guidelines provided in Table 1.
- Click Next and proceed to "Adding a Device".
The Add Device table appears.
Table 1: Fields on the Add POP page
Field | Description |
|---|---|
Region | Regions are used to group services for various business reasons such as location, proximity, service distribution and load.
Example: regional Note: The administrator must not delete the region name. |
POP Name | Enter the name of the POP. You can use an unlimited number of alphanumeric characters, including special characters. Example: north-east. |
Street Address | Enter the street address. You can use an unlimited number of alphanumeric characters, including special characters. Example: 1133 Innovation Way |
City | Enter the name of the city. You can use an unlimited number of alphanumeric characters, including special characters. Example: Sunnyvale |
State/Province | Enter the name of the state. You can use an unlimited number of alphanumeric characters, including special characters. Example: California |
ZIP/Postal Code | Enter 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:
- Click Resources > POPs > +.
The Add POP page appears.
- Complete the configuration settings according to the guidelines provided in Table 1.
- Click Next.
The Device section appears.
- Click the plus icon (+) in the Add Device section.
The Add Device page appears.
- Complete the configuration according to the guidelines in Table 2.
- Click Save.
- Proceed as follows:
For a centralized deployment, click Next and proceed to Adding a VIM.
For a distributed deployment, click 5 (Summary) and proceed to Reviewing and Saving the POP Configuration Settings.
Table 2: Fields on the Add Device Page
Field | Description |
|---|---|
Name | Enter the name of the device, such as a data center gateway, a PE router, or an IPsec concentrator. Some device examples are listed below.
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:
|
Type of Device | Select the type of device:
|
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:
Note: Select Juniper-MX for an MX Series router, unless Juniper Networks recommends the Juniper-MX-MIS package. 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:
Example: Unmanaged |
Device IP | Enter 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 | You must enter 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 | Enter 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:
- Click Resources > POPs > +.
The Add POP page appears.
- Complete the configuration settings according to the guidelines provided in Table 1.
- Click Next.
The Device section appears.
- Click Next.
The VIM page appears.
- In the Connection Information section, specify details for the Contrail Cloud Platform that provides the VIM for this POP.
- Complete the configuration according to the guidelines in Table 3.
- In the Network Information section, click the plus icon (+) to add each resource pool.
- 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.
- 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.
- Click Save.
- 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 | Enter 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 | Enter 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 | Enter the authentication URL for the OpenStack Keystone. Example: http://ip:5000/v3 |
User Name | Enter the OpenStack Keystone username that you configured. Example: admin |
Password | Enter the OpenStack Keystone password that you configured. Example: contrail123 |
Domain | Enter the name of the OpenStack domain that you configured. Example: default |
Tenant | Enter the name of the OpenStack tenant that you configured. Example: admin |
Network Information Resource Pools | |
Resource Pool Name | Enter a resource pool for each VIM. You can use an unlimited number of alphanumeric characters, including special characters. Example: north-east. |
Compute Zone | Enter 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? | Select whether to use an existing virtual network in Contrail OpenStack or to create a new one.
|
Management Network Name | Enter 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 | Enter the name of the Internet network. Example: int-net |
Does Exist | Specify whether to use an existing virtual network in Contrail OpenStack or to create a new one.
|
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 | Enter 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 | Enter the name of the infra tenant for whom you want to assign the service profile. Example: test-tenant |
Domain Name | Enter the Infra domain name. Example: Default |
User Name | Enter the username of the tenant. Example: admin |
Password | Enter the password for the tenant user. Example: password123 |
Default Service Profile | Select 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:
- Click Resources > POPs > +.
The Add POP page appears.
- Complete the configuration settings according to the guidelines provided in Table 1.
- Click Next.
The Device section appears.
- Click Next.
The VIM page appears.
- Click Next.
The EMS page appears.
- Click the plus icon (+) to add the EMS.
- Complete the configuration according to the guidelines in Table 4.
- Click Save.
- 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 | Enter 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 | Enter the vendor name for the EMS. Example: Juniper Networks |
Version | Enter the version number of the EMS. The default version is 15.1. Example: 15.1 |
Authentication URL | Enter the authentication URL for the EMS application. |
User Name | Enter 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 | Enter 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.
- Click Resources > POPs > +.
The Add POP page appears.
- Complete the configuration settings according to the guidelines provided in Table 1.
- Click Next.
The Device section appears.
- Click Next.
The VIM page appears.
- Click Next.
The EMS page appears.
- Click Next.
The Summary page appears.
- Click Summary > Edit to edit the configuration settings of the objects that you configured.
- Click Download POP Payload to save a JSON file of the configuration settings of the objects that you configured.
- Click OK to save the POP configuration. If you want to discard your changes, click Cancel instead.
