Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Providing Broadband Network Gateway Service Support with Cross Provisioning Platform

 

The following are the three kinds of broadband network gateway (BNG) services offered to residential subscribers:

  • IPTV

  • Broadband Remote Access Server (B-RAS)

  • Wholesale

With Cross Provisioning Platform (CPP), you can provision, maintain, and troubleshoot BNG services. For example, you can add or remove BNG devices to or from the existing Layer 3 VPN services. You can add or remove underlying interfaces for any given BNG device. You can also troubleshoot subscriber issues by using the Report Management functionality through Juniper Networks devices.

Note

BNG service support is provided only for Juniper Networks devices. CPP multistaged service support is provided to all MX Series products of Juniper Networks and to third-party devices. A test service can be implemented only by using device configlets. The device configlets of third-party devices are not supported. Hence, you cannot create a test service for third-party devices through CPP.

Provisioning a BNG service involves multiple steps. For example, the following steps are involved in provisioning a B-RAS service in third-party devices:

  • Create a prefix-list.

  • Create a community.

  • Create an export policy.

  • Create an import policy.

  • Create a virtual private routed network (VPRN) B-RAS service site.

Sending a validation or pretesting command may also be included in these steps to provision the service. If any one of the steps fails, you may manually intervene to correct the issue and resume from the failed step. This eliminates the need to repeat the previously completed successful steps. The GUI script controls the provisioning flow internally and shows the status of each step.

You can troubleshoot connectivity and networking issues for subscribers availing different BNG services. To troubleshoot, you can perform any one of the following tasks:

  • You can issue remote procedure call (RPC) commands against the BNG devices to obtain information about active subscribers and to obtain a history of service utilization for a given BNG device that includes the number of current active subscribers and the peak subscriber count.

  • You can execute operational scripts for all MX Series devices on a daily basis and generate graphs of the RPC commands.

  • Subscribers can launch test commands from their devices at home to determine whether a physical connection exists from their homes to a BNG device. To enable subscribers to launch test commands, you need to create a test virtual routing and forwarding (VRF) on MX Series devices.

The CPP framework requires that information about the device and interface at every step to create a service order. The CPP multistage framework supports multiple devices at a time.

The BNG service type supports all three kinds of BNG services. In a multistaged workflow, all steps involved should include the creation of a new service order and the service endpoint common attribute.

This topic has the following sections:

Create Workflow for Broadband Network Gateway Services

The procedure to create a BNG service order is the same for Juniper Networks devices and third-party devices.

The create workflow for BNG services is as follows:

  1. While creating a BNG service order, the GUI collects the data and sends CreateRequest with the Multistaged tag. The initial service order type must be ADD.Note

    You need to create a service definition with the BNG type and a service order based on this BNG service definition. The number of service orders you need to create is equal to the number of tasks you need to perform to troubleshoot the services.

    The CPP returns the job information, polls the status of the job, and invokes the configuration script.

  2. The configuration script verifies the value of the Multistaged tag.
    • If you have specified the Multistaged tag as SINGLETON, the configuration script executes the specified single task.

      If the single task is successful, the job status is updated. The service order status is changed to Completed, and the service status is changed to Deployed.

      If the single task fails, the service order status is changed to Failed_Deployment. To fix the issue manually, you can modify or re-create the service order from the previously successful service order.

      Note

      The single-task BNG service must have an endpoint.

    • If you have specified the Multistaged tag value as INIT, the configuration script executes all the specified tasks.

      If the first task is successful, the job status is updated. The service order status is changed to Completed and the service status is changed to Deploying.

      The configuration script again verifies the value of the Multistaged tag, and executes each task until the Multistaged tag value is LAST.

      After the last task is successful, the job status is updated. The service order status is changed to Completed and the service status is changed to Deployed.

After you complete all the steps, the service modification options are enabled.

Note

If you close any page by mistake while performing a step, you can always go to the Service Orders landing page and perform the remaining steps by using the Recreate Service Order option. The Recreate Service Order option is available only in the previous successful service order. If the service is in the Deploying state, you cannot perform the following actions on the Services page:

  • Modify

  • Configuration Audit

  • View Service Configuration

To poll a job, go to the following URL:

’/serviceui/resteasy/cpp-service-order/order-job-status/’+jobId

To delete a service order, go to the following URL:

'/serviceui/resteasy/cpp-service-order/’+serviceRequestId

To find the service element ID, go to the following URL:

’/serviceui/resteasy/cpp-service/seId

The troubleshooting procedure, which involves the execution of operational scripts and CLI configlets, is applicable only to Juniper Networks devices. The configuration audit function is enabled only when the BNG service state is Deployed. The option to decommission is enabled only when the service state is Deploying or Deployed.

Modify Workflow for Broadband Network Gateway Services

The modify workflow for BNG services is as follows:

  1. While modifying a BNG service order, the GUI collects the data and sends CreateRequest with the Multistaged tag.

    The following tags are mandatory for modifying a BNG service:

    • Service order type—The service order type must be MODIFY.

    • Workflow type—The workflow type must be MODIFY.

    • Record OP type—The record operation type must be MODIFY.

    • Service Element ID—To identify the service element ID, you can call the findServiceEndpointId API.

    The CPP returns job information, polls the status of the job, and invokes the configuration script.

  2. The configuration script verifies the value of the Multistaged tag.
    • If you have specified the Multistaged tag as SINGLETON, the configuration script executes the specified single task.

      If modifying the single task is successful, the job status is updated. The service order status is changed to Completed and the service status is changed to Deployed.

      If modifying the single task fails, the service order status is changed to Failed_Deployment. To fix the issue manually you can modify or re-create the service order from the previously successful service order.

      Note

      The single-task BNG service must have an endpoint.

    • If you have specified the Multistaged tag value as INIT, the configuration script executes all specified tasks.

      If modifying the first task is successful, the job status is updated. The service order status is changed to Completed and the service status is changed to Deploying.

      The configuration script again verifies the value of the Multistaged tag and modifies each task until the Multistaged tag value is LAST.

      After the last task is successful, the job status is updated. The service order status is changed to Completed and the service status is changed to Deployed.

After you complete all the steps, the service order status is changed to Completed.

Viewing Broadband Network Gateway Services Details

A BNG service is created only with common artifacts and no VPRN service is associated with a BNG service. Hence, the service details are not displayed in CPP. In this case, instead of service details, the following tabs are displayed, if available:

  • General–Displays the service name, device name, artifact, and vendor type

  • Configuration–Displays configuration details

  • Artifact–Displays common artifact information from the Simple Object Access Protocol (SOAP) response

  • Igmp–Displays information about group addresses and interfaces

  • Interface–Displays dynamic profile-related information.

  • MVPN–Displays neighbor ID and provider tunnel ID.

  • AAA Info–Displays AAA-related information

  • QoS Info–Displays QoS-related information

The Juniper Subscriber Service Details tab displays details of Dynamic Host Configuration Protocols server (DHCP) address pool, and RADIUS servers. In the case of IPTV, pool information and RADIUS are not displayed. In the case of B-RAS, DHCP server details are not displayed. All tabs of the Layer 3 VPN service are displayed in the case of the BNG service. The ALU Subcriber Service Details tab displays details of Dynamic Host Configuration Protocol (DHCP), Internet Group Management Protocol (IGMP), Physical Interface Module (PIM), and multicast virtual private network (MVPN).

Child-Endpoint Support for Broadband Network Gateway Services

For a BNG service, you can provision parent-child relationships between the endpoints. You can provision it as a single-task workflow or multitask workflow.

For a multitask workflow, you can select a parent endpoint in a task and then attach the child endpoint in the subsequent tasks.

API for Finding the Service Element ID

To modify or delete an endpoint, you must specify the service element ID and set the Record OP type tag as Modify or Delete.

The findServiceEndpointId API is used to find the service element ID. The GUI script validates the service element ID and identifies the end point that must be modified or deleted.

Following is the query to find the service element ID:

public String findServiceEndpointId(@QueryParam(serviceID) String serviceId, @QueryParam(deviceId) String deviceID,@QueryParam(port) String port, @QueryParam(outerEncap) String outerEncap)

This API returns the service element ID in string format with the following parameters:

  • serviceID—ID of the service that is modified

  • deviceId—Provider edge device ID

  • port—Port of an interface

  • outerEncap—Outer encapsulation VLAN value