Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation
Guide That Contains This Content
[+] Expand All
[-] Collapse All

    Getting Started with Connectivity Services Director

    Based on your network deployment needs and configuration settings, you might require different service types, such as point-to-point, Layer 3 VPN, VPLS, or RSVP LSP services, to be applied on devices in your topology. It is essential to discover or add the devices that you want to be administered using Connectivity Services Director to the application database, before you can enable and define services. Also, the devices must be configured with the basic and mandatory device settings, such as routing instances, routing protocols, interfaces, and administrative groups, before they are imported or discovered for additional modifications, such as configuration of services, using the network management application.

    When you install Connectivity Services Director, the single application package installs the capabilities for configuring network services, such as point-to-point, Layer 3 VPN, and VPLS, configuring MPLS and RSVP label-switched path (LSP) services, configuring Precision Time Protocol (PTP) and synchronous Ethernet services, configuring the OAM (Operations, Administration and Maintenance) functionality, and configuring class of service (CoS) profiles. To install Connectivity Services Director, see the "Installation Instructions for Connectivity Services Director, Release 2.1" section in the Junos Space Connectivity Services Director Release Notes, Release 2.1.

    For the Connectivity Services Director Release 2.1, you can also access the Services Activation Director GUI interface to launch workspaces to configure functionalities. To access the Services Activation Director GUI, see Accessing the Services Activation Director GUI .

    You need not separately install the different applications, such as Network Activate or Transport Activate, based on your deployment needs and device models to be managed, on a Junos Space JA1500 Appliance, Junos Space JA2500 Appliance, or a Junos Space Virtual Appliance that satisfied the hardware requirements. A consistent, uniform, consolidated, and streamlined user interface and elegant experience is introduced by using the Service View component in the Connectivity Services Director GUI. Besides offering a cohesive and user-friendly experience and interface for configuring point-to-point, Layer 3 VPN, VPLS, and RSVP LSP services, Network Activate, Transport Activate, Sync Design, and OAM Insight are available in the older GUI format in the same image package. The functionalities of QoS Design are available in Connectivity Services Director as CoS profiles, which you can reference in point-to-point, VPLS, and Layer 3 VPN services. QoS Design and Network Director cannot be installed on the same system as Connectivity Services Director.

    Figure 1: Dashboard Page

    Dashboard Page

    The following workflow describes the tasks that you need to perform after the installation of the application to enable effective and streamlined management, provisioning, and troubleshooting of devices and services configured using Connectivity Services Director.

    1. Discover devices using Connectivity Services Director GUI or the Junos Space Platform workspace. See Discovering Devices in a Physical Network for instructions on discovering devices from Build mode of Connectivity Services Director. See Discovering Devices in the Junos Space Network Application Platform User Guide for instructions on discovering devices using the Junos Space Platform workspace.

      Note: 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.

    2. Discover the roles of devices and assign network-provider edge (N-PE) roles as necessary. To prestage devices and assign device roles, see Discovering Device Roles and Excluding Devices from N-PE Role Assignment.

    3. Create service templates. Templates provide a powerful mechanism to configure advanced service-related options that are not exposed via the service order creation workflow. Templates are attached to a service definition. To work with service templates, see Service Templates Workflow and Applying a Service Template to a Service Definition.

    4. Review the predefined service definitions that are available by default, and determine whether you want to create a new customzied service definition. A service definition specifies the attributes that are common among a group of service orders that have similar service requirements. To work with service definitions, see Predefined Service Definitions, Creating a Point-to-Point Ethernet Service Definition, Creating a Multipoint-to-Multipoint VPLS Service Definition, Creating a Point-to-Multipoint VPLS Service Definition, Creating a Full Mesh Layer 3 VPN Service Definition, and Creating a Hub-and-Spoke (One Interface) Layer 3 VPN Service Definition.

    5. Create customers that denote the users to be associated with service orders. New customers must be identified to the system before you can provision and activate a service order for them. To create customers, see Adding a New Customer.

    6. Create class-of-service profiles to prioritize the traffic flow and define policies for handling received packets to avoid network congestion and traffic disruption. See Creating and Managing Wired CoS Profiles.

    7. Create service orders for the types of protocols that your network environment requires for optimal and cohesive management of large numbers of devices. A service order is an instance of the service definition that completes the definition for a specific customer’s use. To work with service orders, see Creating a Service Order.

    8. Deploy service orders to propagate the service configuration to the corresponding devices. To transfer service order configurations to devices and apply the settings on the devices, see Deploying Services Configuration to Devices and Managing Service Configuration Deployment Jobs.

    9. Perform audit operations, such as functional and configuration audit, to examine the status of interfaces, LDP sessions, neighbor links, and endpoints of point-to-point services. You can also identify whether the service configuration on the device has been changed out of band. In addition, you can use op scripts to perform any function available through the remote procedure calls (RPCs) supported by either the Junos XML management protocol or the Junos XML API. See Performing a Functional Audit, Performing a Configuration Audit, and Troubleshooting N-PE Devices Before Provisioning a Service for further information.

    10. Monitor the health (working condition), operating efficiency, traffic-handling capacity, and performance status of the managed devices and configured services. Several monitors or widgets are displayed to enable you to track, diagnose, and rectify problems and discrepancies associated with services configured on devices. To evaluate and diagnose the services, traffic-flow, and device states, see Service Monitoring Capabilities in Connectivity Services Director.

    11. View information about the health of your network and changing conditions of your equipment. Use Fault mode to find problems with equipment, pinpoint security attacks, or to analyze trends and categories of errors. For example, if you find that a particular device or a service has recorded a large number of critical or major alarms, you can then navigate to the appropriate device settings page or service order page to correct and modify the attributes or diagnose the problems that might be generating the alarms. To view alarms and events, see Understanding Fault Mode in Connectivity Services Director.

    Modified: 2017-08-13