Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Example: Configuring and Deploying a Multipoint-to-Multipoint VPLS Service

 

This example shows how to deploy and verify a multipoint-to-multipoint VPLS service starting with three MX Series routers. Figure 1 shows the service.

Figure 1: Simple Multipoint-to-Multipoint Service
Simple Multipoint-to-Multipoint
Service

This service provides connectivity for one VLAN, using 802.1Q interface endpoints. Customer site A connects to the network through an N-PE device named SJC . Customer site B connects to the network through an N-PE device named SFO . Customer site C connects to the network through an N-PE device named BLR. In this example, we allow Network Activate to select each UNI automatically.

Each UNI is to have its bandwidth limited to 25 Mbps.

You can create this service by performing the following tasks:

Preparing Devices for Discovery

Before you can add a device using device discovery, the following conditions must be met:

  • SSH v2 is enabled on the device. To enable SSH v2 on a device, issue the following CLI command:

    set system services ssh protocol-version v2
  • The NETCONF protocol over SSH is enabled on the device. To enable the NETCONF protocol over SSH on a device, issue the following CLI command:

    set system services netconf ssh
  • The device is configured with a static management IP address that is reachable from the Junos Space server. The IP address can be in-band or out-of-band.

  • A user with full administrative privileges is created on the device for the Junos Space administrator.

  • If you plan to use SNMP to probe devices as part of device discovery, ensure that SNMP is enabled on the device with appropriate read-only V1/V2C/V3 credentials.

Discovering Devices

Device discovery is a process that Junos Space uses to bring network devices under its control. This example brings two MX Series routers under Junos Space management.

  1. Log in to Junos Space using your credentials.
  2. In the Applications Chooser, select Platform > Devices > Discover Devices > Discover Targets.
  3. In the Discover Targets page, click +.

    The Add Device Target page appears.

  4. Select IP range.
  5. Enter the IP address information. This example uses a range of three addresses.

  6. Click Add, and then click Next.
  7. In the Devices > Discover Devices > Specify Probes page, select both Ping and SNMP as probes.
  8. Click Next.
  9. In the Devices > Discover Devices > Specify Credentials page, click + and enter the device login credentials.
  10. Click Finish.

    Device discovery begins. It displays a graph showing the status of the discovery operation. Initially, three devices are discovered. When the Junos Space software has accessed all three devices and brought them under its management, all three devices move from the Discovered column of the graph to the Managed column.

  11. To check the results of the device discovery operation, select the Devices workspace again, then select Device Management. The Manage Devices page shows the added devices.



See also

Preparing Devices for Prestaging

Before prestaging devices for multipoint-to-multipoint services, the following entities must be configured:

  • MPLS must run on each N-PE device.

  • MPBGP must run on each N-PE device that you want to participate in a multipoint-to-multipoint service.

To satisfy the preceding criteria, ensure that the following configuration exists on each N-PE device:

Note

The OSPF configuration is not required in prestaging.

The VPLS service needs to be enabled in a network device, to make the static pseudowire functionality active in the device. You can activate the static pseudowire functionality by configuring the network device through the CLI page. You need to enter the CLI configuration mode of a network element and run the command

set protocols vpls static-vpls no-tunnel-services

commit

If the device is not configured through CLI, a warning message appears in the application server log, that is the JBOSS Log:

<Device name> should be configured with static VPLS no tunnel service rule.

To discover the roles of the various network elements configured:

1. Select Network Activate > Prestage Devices > Manage Device Roles.

2. Select Discover Roles to view the relevant page.

3. Click Continue to view the Role Discovery Status page.

The Role Discovery Status page displays a graph which shows the number of unassigned devices that could be assigned the role of N-PE or PE.

To re-sync the role of the network elements configured:

1. Select Network Activate >Prestage Devices > Manage Device Roles.

2. To re-sync the role capability of a network element, right-click the network element’s name.

3. Click Re-sync Role Capability. The Re-sync Role Capability page appears where you can select the device’s name and click Re-sync.

The role is re-synced with the same device now.

To re-sync the routing state of the device:

  1. Select Network Activate >Prestage Devices > Manage Device Roles.
  2. To re-sync the routing state of the device, right-click the device’s name.
  3. Click Re-sync Routing State. The Re-sync Routing State page appears where you can select the device’s name and click Re-sync.

    The routing state of the device is re-synced.

    Starting with Release 17.1R4, you can use the new option Re-sync Routing State to re-sync the routing state of an old device.

Discovering and Assigning N-PE Roles

Before you can provision services, you must prestage the devices. prestaging includes assigning device roles and designating interfaces on those devices as UNIs. This example provides the steps to accept the recommendations of the Network Activate software for N-PE devices and UNIs.

  1. In the Application Chooser, select Network Activate:
  2. In the Network Activate task pane, select Prestage Devices > Manage Device Roles > Discover Roles.

    This action launches the role discovery process in which the Network Activate software examines the devices under Junos Space management looking for devices that match predefined rules that identify N-PE devices. The Role Discovery Status graph shows that, in this case, the Network Activate software has discovered three such devices.

  3. In the Assign Roles page, switch to multiple selection mode and select both N-PE devices.
  4. Open the Actions menu and select Assign NPE role.
  5. In the Assign NPE page, click Assign to confirm the assignment.
  6. To view the assignment status, in the Job Details page, click the job ID of the assignment job.

    The Job Management page shows the progress and status of the role assignment job.

  7. To verify the result, in the task pane, select Prestage Devices > Manage Device Roles.

    The Manage Device Roles page shows devices you can use for provisioning.

Choosing or Creating a Service Definition

A service definition provides a template upon which services are built. It specifies service attributes that are not specific to a service instance. In this example, the service definition provides all service attributes except the N-PE devices, the UNIs, and bandwidth.

The Network Activate software ships with standard service definitions. First, we check the standard service definitions to determine whether one already exists that can work.

  1. In the Network Activate task pane, select Service Design > Manage Service Definitions.

    The Manage Service Definitions page lists all service definitions in the system. In a new system, the page lists only predefined service definitions.

    This example requires a multipoint-to-multipoint service definition with UNIs that use 802.1Q interfaces and allow you to set a bandwidth of 25 Mbps. The standard service definitions have several examples for provisioning 802.1Q UNIs, but none that allow the setting of a 25 Mbps bandwidth limit. You need to create a new service definition.

  2. In the Network Activate task pane, select Service Design> Manage Service Definitions > Create VPLS Service Definition.

    The General page appears.

  3. Enter a name for the service definition.



  4. Click Next.
  5. In the Connectivity Settings page—because we intend to select a specific VLAN for each endpoint in the service—leave the Normalized VLAN setting as the default Normalize to VLAN none, and then click Next.
  6. In the UNI Settings page, in the Ethernet option field, select dot1q.
  7. In the Customer traffic type field, select Transport single VLAN.
  8. In the VLAN ID selection field, choose Select manually.
  9. In the VLAN range for manual input, specify the range.
  10. In the Outer Tag protocol ID, select 0x8100
  11. In the Physical IF encapsulation field, select flexible-ethernet-service.
  12. In the Logical IF encapsulation field, select vlan-vpls.
  13. In the Bandwidth Settings panel, select the Enable rate limiting check box.
  14. In the Default Bandwidth field, enter 10, for a default bandwidth of 10 Mbps.
  15. To the right of the value you just entered, select the Editable in service order check box.

    The Default Bandwidth (Mbps) field becomes active.

  16. Select the Enable in Service Order check box for the Default Bandwidth (Mbps) field.

    The Min Bandwidth (Kbps), Max Bandwidth (Mbps), and Increment (Kbps) fields become active.

  17. In the Bandwidth range fields, enter 10 and 64 respectively.
  18. In the Increment field, enter 64.

  19. To save and complete the service definition, click Finish.

    The Manage Service Definitions page includes the new service definition.

    You have created a customized Service Definition, but it has not yet been published. Before a service definition can be used in provisioning, it must be published.

  20. To publish the service definition, in the Manage Service Definitions page, select the vpls-dot1q-sd-1 service definition, and then in the Actions menu, select Publish Service Definition.

    The Publish Service Definition page appears.

  21. To confirm that you want to publish this service definition, click Publish.

    In the Manage Service Definitions page, the State column changes to Published.

The service definition is now ready for use in provisioning.

Creating a Customer

Before you can provision the service, customer details must be present in the Junos Space data base. To add a customer:

  1. In the Network Activate task pane, select Service Provisioning > Manage Customers > Create Customer.
  2. In the Name field, enter Best Customer.
  3. In the Account number field, enter 1234.
  4. Click Create.

The Manage Customers page shows the new customer.

Creating and Deploying a Multipoint-to-Multipoint Service Order

Now that you have prestaged your devices, created a suitable service definition, and added the customer information to the database, you are ready to create and deploy a service order.

  1. In the Network Activate task pane, select Service Provisioning > Manage Service Orders > Create VPLS Service Order.
  2. In the Manage Service Definitions page, select the service definition named vpls-dot1q-sd-1.

    This service definition is the customized service definition you created earlier.

  3. Click Next.
  4. In the General Settings box of the Enter Order page, in the Name field, enter vpls_so_1.
  5. In the Customer field, select the customer for which you are creating the service order..
  6. In the Endpoint Settings box of the Enter Order Information page, in the Bandwidth field, select 25.

  7. Clear the Autopick VLAN ID check box.

    The End Point Settings box expands to include the VLAN ID field.

  8. In the VLAN ID field, enter 600.
  9. Click Next.
  10. In the Select Endpoint PE Devices page, select BLR, SFO, and SJC.
  11. Click Create.
  12. In the Endpoint Settings page click Next to accept the system-selected endpoints.

    In the Deployment Options page, you can save the service order for later deployment, schedule the service order for later deployment, or deploy the service order now. Select Deploy now.

  13. Click OK to start the deployment.
  14. To monitor the progress and status of the deployment, in the Order Information page, click the job ID. The Job Management page shows the status of the job.
  15. When you see in the Job Management page that the deployment is successful, in the Network Activate task pane, select the Service Provisioning workspace again.
  16. In the task pane, select Manage Services.

    The Manage Services page shows the new service.

Performing a Functional Audit and a Configuration Audit

Now that your new service is deployed, we recommend that you validate its configuration and functional integrity. A functional audit runs operational commands on the device to verify that the service is up or down. A configuration audit verifies whether the configuration that was pushed to the device during deployment is actually on the device.

To perform a configuration audit and a functional audit of the service:

  1. In the Manage Services page, select the service instance you just deployed.
  2. Open the Actions menu and select Perform Functional Audit.
  3. In the Schedule Functional Audit page, you can choose to perform the audit now or schedule it for later. Select Audit now, and then click OK.
  4. In the Order Information page, click OK.
  5. Open the Actions menu and select Perform Configuration Audit.
  6. In the Schedule Configuration Audit page, you can choose to perform the audit now or schedule it for later. Select Audit now, and then click OK.
  7. In the Order Information page, click OK.
  8. To view the functional audit results,
    • In the Manage Services page, select the vpls_so_1 service instance.

    • Right-click or open the Actions menu to see the list of tasks available for this device, and select View Functional Audit Results.

    • In the Functional Audit Results page, select each device to view the results.

  9. To view the results of the configuration audit,
    • Right-click or open the Actions menu to see the list of tasks available for this device, and select View Configuration Audit Results.

    • In the Configuration Audit Results page, select each device in turn and review the results. This report indicates any part of the service configuration that is missing on the device, or inconsistent with the Junos Space database.

Following a successful audit, the service is deployed and ready to be used.

Release History Table
Release
Description
Starting with Release 17.1R4, you can use the new option Re-sync Routing State to re-sync the routing state of an old device.