Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

About Build Mode in Service View of Connectivity Services Director


In Build mode, you can create services for devices that are managed by Connectivity Services Director. You can define service templates and attributes of different services, and also specify policies and filters to classify and control the manner in which packets must be handled by the various services.

Configuring a service has a major impact on the flow of routing information or packets within and through the router. For example, you can configure a routing service that does not allow routes associated with a particular customer to be placed in the routing table. As a result of this configured service, the customer routes are not used to forward data packets to various destinations and the routes are not advertised by the routing protocol to neighbors. The service designer uses the Build mode for managing the service definitions that the service provisioner uses as the basis for creating a service order. You can create a service definition that specifies the attributes that are common among a group of service orders that have similar service requirements, and a service order, which is an implementation object or a derivative of a service definition.

This topic describes the following functionalities that are available in Build mode of Service View:

Manage Service Definitions

Connectivity Services Director software provides a set of predefined service definitions for E-Line services, multipoint-to-multipoint (full mesh) services, and point-to-multipoint (hub and spoke) services. These service definitions are capable of providing the basis for most of the service orders your organization will need to create. In case these predefined service definitions are not adequate for all your needs, however, the Network Activate software enables you to create service definitions of your own.

Prestage Devices

Prestaging takes the devices already under Junos Space management and prepares them for service activation. The prestaging process discovers network provider edge (N-PE) devices in the Junos Space database and assigns roles to those devices and their interfaces. N-PE routers and user-to-network interfaces (UNIs) are basic building blocks required for Layer 2 and Layer 3 provisioning

Prestage Services

The Service Recovery feature functions within the pre-staging operation of the Network Activate application. Service Recovery has two parts. First, Service Recovery parses each device’s configuration searching for service configurations and existing Network Activate service elements (E-Line service, Layer 2 circuits, routing instances, firewalls, policy options, routing options, and OAM interface branches of Junos Space configurations that are being processed).

Service Definition Operations

You can perform several tasks on service definitions, such as editing, publishing, or unpublishing a service definition. You can modify a service definition to suit your network needs. The service designer must publish a customized service definition before a service provisioner can use that definition to create a service request. The service designer can unpublish a custom service definition to make it unavailable to service provisioners for creating a service request. You cannot unpublish a predefined service definition.

Audit and Troubleshooting of Services

After the service is deployed, a functional audit establishes whether the service is up or down. If the functional audit reports that the service is up, the customer can begin using the service. Once the service is active, the service provisioner can monitor the health of the service by running a functional audit or a configuration audit. Users assigned the Service Activator role can perform these service provisioning tasks.