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
     

    Related Documentation

     

    Example: Configuring and Deploying a Point-to-Point Ethernet Service

    This example deploys and verifies a point-to-point Ethernet service starting with two MX Series devices. Figure 1 shows the service.

    Figure 1: Simple Point-to-Point Service

    Simple Point-to-Point Service

    This service provides connectivity for one VLAN, using 802.1Q interface endpoints. Customer site A connects to the network through UNI ge-0/0/2 on an N-PE device named SJC. Customer site B connects to the network through UNI ge-0/0/3 on an N-PE device named SFO.

    The bandwidth for each UNI is limited to 1000 Mbps.

    You can create this service by performing the following tasks, in order:

    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 Network Activate task pane, select Devices > Discover Devices > Discover Targets.
    3. In the Discover Targets window, click +.

      The Add Device Target window appears.


    4. Select IP range.
    5. Enter the IP address information. This example uses a range of two addresses.
    6. Click Add, and then click Next.
    7. In the Devices: Specify Probes window, select both Ping and SNMP as probes.
    8. Click Next.
    9. In the Devices: Specify Credentials window, 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, two devices are discovered. When Junos Space has accessed both devices and brought them under its management, both 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.

    Preparing Devices for Prestaging

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

    • MPLS must run on each N-PE device.
    • LDP signaling must be established between N-PE devices that you want to participate in the same point-to-point service.

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

    interfaces {
        ge-0/0/0 {
            unit 0 {
                family inet {
                    address 10.1.18.2/30;
                }
                family mpls;
            }           
        }
    
       }
        lo0 {
            unit 0 {
                family inet {
                    address 192.168.1.20/32;
                }
            }
        }
    
    }
    protocols {
        mpls {
            interface ge-0/0/0.0;
            interface lo0.0;
        }
         ospf {
            traffic-engineering;
            area 0.0.0.0 {
                interface lo0.0 {
                    passive;
                }       
                interface ge-0/0/0.0;
        }
        ldp {
            interface ge-0/0/0.0;
            interface lo0.0;
        }

    Note: The OSPF configuration is not required in prestaging.

    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 Network Activate task pane, select Prestage Devices > Manage Device 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. In this example, the Role Discovery Status graph shows that the Network Activate software has discovered two such devices.

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

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

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

      The Manage Device Roles window shows two devices that can be used 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 our 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 will 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 screen lists only predefined service definitions.

      This example requires a 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 P2P Service Definition.

      The General window appears.

    3. Enter a name for the service definition. For this example, enter p2p-dot1q-sd-1.
    4. Click Next.

      The UNI Settings window appears.

    5. In the Connectivity Settings window, to pick the default connectivity settings, click Next.
    6. In the UNI Settings window, 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, select Select manually.
    9. In the VLAN range for manual input field, specify the range.
    10. In the Outer Tag protocol ID field, select 0x88a8
    11. In the Physical IF encapsulation field, select flexible-ethernet-services.
    12. In the Logical IF encapsulation field, select vlan-ccc.
    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 Min Bandwidth (Kbps), Max Bandwidth (Mbps), and Increment (Kbps) become active.

    16. In the Min Bandwidth (Kbps) field, enter 100.
    17. In the Max Bandwidth (Mbps) field, enter 10000.
    18. In the increment field, enter 64.

      These settings of the Bandwidth range and Increment fields allow the bandwidth to be set in the service to any 64-Kbps increment in the range of 100 Kbps through 10000 Mbps.


    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 p2p-dot1q-sd-1 service definition; then in the Actions menu, select Publish Service Definition.

      The Publish Service Definition window appears.

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

      In the Manage Service Definitions page, the symbol in the upper left corner of the service definition changes to a check mark, indicating that the status has changed 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 database. 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 Point-to-Point 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. To create and deploy a service order:

    1. In the Network Activate task pane, select Service Provisioning > Manage Service Orders > Create P2P Service Order.
    2. In the Create P2P Service Order window, select the service named p2p-dot1q-sd-1.

      This is the customized service definition you created earlier.

    3. Click Next.
    4. In the General/Connectivity Settings window, in the Name field, enter so_1.
    5. In the Customer field, select Best Customer.
    6. Click Next.

      The Endpoint Settings window appears.

    7. For endpoint A, in the PE device field, select SJC.
    8. In the UNI interface field, select ge-0/0/2.
    9. In the VLAN-ID field, enter 100.
    10. Click Next.
    11. In the Endpoint Settings window for endpoint Z, in the PE device field, select SFO.
    12. In the UNI interface field, select ge-0/0/3.
    13. In the Bandwidth field, select 25.
    14. Click Create.
    15. In the Deployment Options window, select Deploy now.
    16. Click OK to start the deployment.
    17. To monitor the progress and status of the deployment, in the Order Information window, click the job ID. The Job Management page shows the status of the job.
    18. When you see in the Job Management window that the deployment is successful, in the Network Activate task pane, select Service Provisioning > 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, you should 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. Right-click on the service instance or open the Actions menu and select Perform Functional Audit.
    3. In the Schedule Functional Audit window, you can choose to perform the audit now or schedule it for later. Select Audit now, then click OK.
    4. In the Order Information screen, click OK.
    5. Right-click on the service instance or open the Actions menu and select Perform Configuration Audit.
    6. In the Schedule Configuration Audit window, 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 window, click OK.

      When the audit jobs have finished, success is indicated by an up arrow in the top right corner of the service.

    8. To view the functional audit results:
      1. In the Manage Services page, select the so_1 service instance.
      2. Open the Actions menu and select View Functional Audit Results.
      3. In the Functional Audit Results window, select each device to view the results.
    9. To view the results of the configuration audit:
      1. Open the Actions menu and select View Configuration Audit Results.
      2. In the Configuration Audit Results window, 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 is inconsistent with the Junos Space database.

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

     

    Related Documentation

     

    Modified: 2017-02-15