3

Junos Space Connectivity Services Director

Use Case

Service Supported

Service Type

Timing

Precision Time Protocol

(PTP)

• Ordinary Clock

• Boundary Clock

Synchronous Ethernet

• Network Option-1

• Network Option-2

Juniper Networks

NorthStar

Controller

integration

RSVP LSP (PCEP,

NETCONF-based)

• P2P

• P2MP

• Full mesh

Segment routing (PCEP-

based)

• P2P

• P2MP

• Full mesh

Device Pre-Staging

As part of device pre-staging, Connectivity Services Director

automatically identifies the devices which are capable of MPLS

services. This involves assigning network provider edge (N_PE)

and provider (P) roles to devices. It also identifies corresponding

user-to-network interfaces (UNIs) and network-to-network

interfaces (NNIs) on the devices. Assigning device and UNI roles

helps simplify service provisioning by allowing only qualified

devices and interfaces to be selected for services.

Device Monitoring

Device monitoring for device status, interface status, and

interface utilization is an important requirement for any service

provider. Connectivity Services Director offers additional

features on top of those provided by the Junos Space Network

Management platform. One such feature, Chassis View, provides

a three-dimensional view of the actual chassis, showing the real-

time status of the device, installed PICs, and interface status.

Figure 2: Chassis View for a Juniper Networks MX240 3D Universal Edge Router

As part of the device monitoring process, the Connectivity

Services Director collects all traffic statistics including unicast

packets, multicast packets, error counters, and utilization data of

all interfaces on the device.

Figure 3: Device monitoring traffic summary

Automated MPLS Resource Management

Deploying carrier Ethernet services requires multiple network

resources to be allocated and tracked. These resources can be

network-wide, device-specific, or per customer-specific. The

most common resources are:

• Network Resources: Route target, route distinguisher,

Ethernet segment identifier (ESI), L2 VPN IDs, virtual

private LAN service (VPLS) ID, virtual circuit (VC) ID

• Device Resources: Unit, VLAN (Dot1q, QinQ)

• Customer Resources: IP pools

When a service provider is handling hundreds of customers,

each being provisioned for hundreds of services, tracking

network resources can quickly become unmanageable and

unscalable—particularly when the resources are tracked

manually. For example, if a customer is experiencing packet loss

from one site to another, how quickly can a help desk operator

troubleshoot the problem?

Connectivity Services Director provides automated MPLS

resource management as well as an auto allocating feature:

• Unit, VLAN IDs (Dot1q, QinQ), ESI to the UNIs

• VC IDs, VPLS ID, route target, route distinguisher, L2VPN IDs

• IPV4 addresses to provider edge-customer edge (PE-CE)

interfaces

This not only minimizes user input during provisioning but also

guarantees that the service provisioning pushed to the devices

does not conflict with existing resources on the network.

Service Design

Service Design allows service providers to customize services by

allowing dynamic association of attributes to the service based

on customer needs. A single design can be used to provision

hundreds of services. The service design also allows the service