proNX Optical Director
Help Center User GuideRelease Notes
 
X
User Guide
Release Notes
Contents  

Services

Services Overview

An optical service provides wavelength connectivity between optical service endpoints and exists as a series of individual optical cross-connects that route the service wavelength through the multiplexers/demultiplexers, ROADMs, and line amplifiers that make up the optical network. The proNX Optical Director encapsulates this series of cross-connects into a single entity and displays it as an end-to-end light path.

Attached to each end of the optical service is the endpoint transponder. The endpoint transponder can be a standalone transponder or a transponding function integrated on packet equipment.

The connection between the endpoint transponder and the optical network edge is called the tail facility. The tail facility endpoint (that is, transponder) is not part of the optical network, but you can use the proNX Optical Director to configure the tail facility endpoint if the tail facility terminates on a supported transceiver port on Juniper Networks equipment. This is called a supported tail facility endpoint.

If the tail facility does not terminate on a supported transceiver port, the tail facility endpoint is known as an external or alien endpoint. You can connect an alien endpoint to the optical network but you will need to configure the alien endpoint using the external equipment’s management system.

When you create an optical service using the proNX Optical Director, you specify the wavelength and the two endpoints that the wavelength interconnects. The endpoint that you specify can be an optical service endpoint (that is, an optical port at the optical network edge) or a supported tail facility endpoint:

Optical Service and Tail Facility Endpoints

This document describes two types of endpoints: the optical service endpoint and the tail facility endpoint.

The optical service endpoint refers to the port at the optical network edge that connects to the client transponder. This endpoint is part of the optical network.

The tail facility endpoint is the port on the client transponder that connects to the optical network edge. This endpoint is a client or a user of the optical network.

Figure 5 and Table 53 describe the allowed endpoints when you create a service. You can create a service from endpoints A, B, C, or D to endpoints E, F, G, or H.

Figure 5: Optical Service and Tail Facility Endpoints

Optical Service
and Tail Facility Endpoints

Table 53: Optical Service and Tail Facility Endpoints

Endpoint

Label

Usage

An optical service endpoint where the endpoint is a topologically-unconnected universal port on a TCX1000-RDM20.

This is a universal port that does not have a link associated with it.

A or E

You typically use this endpoint when you set up a service to an alien device that is attached directly to a universal port on the TCX1000-RDM20.

An optical service endpoint where the endpoint is a universal port on a TCX1000-RDM20 that is topologically connected to a multiplexer/demultiplexer.

This is a universal port that has a link to a multiplexer/demultiplexer.

B or F

You typically use this endpoint when you set up a service to an alien device that is attached to a client port on the multiplexer/demultiplexer.

A supported tail facility endpoint where the endpoint is topologically connected to a universal port on a TCX1000-RDM20.

This is a transceiver port at the supported tail facility endpoint.

C or G

You typically use this endpoint when you set up a service to a supported tail facility endpoint that is attached directly to a universal port on the TCX1000-RDM20.

A supported tail facility endpoint where the endpoint is topologically connected to a client port on a multiplexer/demultiplexer.

This is a transceiver port at the supported tail facility endpoint.

D or H

You typically use this endpoint when you set up a service to a supported tail facility endpoint that is attached to a client port on the multiplexer/demultiplexer.

The TCX1000-RDM20 has a pool of 20 universal ports that you can use to connect to other ROADM elements and/or to client transponders. For lower wavelength fan-out, you can deploy the TCX1000-RDM20 without a multiplexer/demultiplexer and use any available universal ports to connect directly to client transponders (labels A, C, E, G). For larger wavelength fan-out, you can deploy the TCX1000-RDM20 alongside a multiplexer/demultiplexer to give access to more wavelengths (labels B, D, F, H).

When creating a service to an alien tail facility endpoint, the endpoint you specify resides in the optical network (labels A, B, E, F) and does not include the tail facility itself. It is your responsibility to ensure that the alien endpoint is configured properly to connect to the optical network at those points.

When creating a service to a supported tail facility endpoint, the endpoint that you specify is the supported port on Juniper Networks equipment (labels C, D, G, H). See Supported Tail Facility Endpoints for the list of supported tail facility endpoints.

Single Path Service

A single path service is a service that has a single path set up between the two service endpoints. A fault on the path might cause the service to go down.

Protected Service

Figure 6 shows a protected service using a pair of two-degree ROADM nodes connected in a basic two-node ring. More complex ring and mesh configurations are possible as well.

Figure 6: Protected Service

Protected Service

A protected service is a service that has a pair of paths set up between the two service endpoints. One path is placed administratively in-service (IS) and the other path is placed administratively out-of-service (OOS). Under normal conditions, the IS path provides the optical connectivity. If a fault occurs in the current IS path, you can manually restore service by administratively disabling the current IS path and administratively enabling the current OOS path so that the current OOS path becomes the new IS path. This is called manual restoration. See Editing or Deleting a Service for instructions on how to change a service’s administrative state.

Note It is up to the operator to ensure that one path is administratively in-service and the other path is administratively out-of-service. The proNX Optical Director does not enforce this but will raise an alarm if both paths are in-service.

A multi-degree colorless multiplexer/demultiplexer such as the TCX1000 2-Degree 8-Channel Colorless Mux/Demux (2D8CMD) is required at each end as the common endpoint for the protected service. The 2D8CMD has two line ports (L0 and L1) that connect to the two different degrees in the ROADM node, thereby supporting two paths between the endpoints.

A protected service is modeled as a pair of services where each service in the pair takes a different path across the network. The individual services in the pair are effectively single path services that share a common wavelength and common endpoints.

There are two ways to set up a protected service in the proNX Optical Director:

About the Services Provisioned Page

To access this page, click the Network tab and select Services>Provisioned in the left-nav bar.

This page lists all the provisioned optical services in the network.

Tasks You Can Perform

In addition to seeing the list of optical services in the network, you can view a specific optical service, edit a specific optical service including changing its administrative state, and delete a specific optical service from this page.

Field Descriptions

Table 54 explains the fields in the Services Provisioned page.

Table 54: Fields in the Services Provisioned Page

Field

Description

Name

The name of the service. The name is set when you create the service.

Frequency

The optical frequency of the service.

To see the corresponding wavelength and channel number, hover over the frequency value.

State

The end-to-end state of the service. The format is operational-status (administrative-state).

The operational-status includes the port status at the tail facility endpoints but the administrative-state does not.

The following are the valid values for the operational status:

  • Up - All ports along the service path are up.

  • Down - At least one port along the service path is down.

The following are the valid values for the administrative state:

  • In-Service - When you set the administrative state of an optical service to In-Service, all cross-connects along the service path are administratively placed in service.

  • Out-of-Service - When you set the administrative state of an optical service to Out-of-Service, all cross-connects along the service path are administratively placed out of service.

  • Degraded - The administrative state is displayed as Degraded if one or more TCX1000-RDM20 devices in the service’s path has a cross-connect configured for the light path in one direction but not the other. This is a configuration issue and typically indicates a service activation failure. Check the current alarms as well as the task history. This value cannot be set directly by the user.

Source Site

The name of the site where the source device is located.

Source Device

The name and/or the IP address of the device at the source.

The source device can be an endpoint transponder attached to the optical network, or a ROADM element at the optical network edge.

Note: The proNX Optical Director might display a device as a source or as a destination differently from how you assigned the device when you created the service.

Source Port

The port on the source device.

If the source device is an endpoint transponder, then this field refers to a port on that transponder.

If the source device is a ROADM element, then this field refers to a universal port on that ROADM.

Destination Site

The name of the site where the destination device is located.

Destination Device

The name and/or the IP address of the device at the destination.

The destination device can be an endpoint transponder attached to the optical network, or a ROADM element at the optical network edge.

Note: The proNX Optical Director might display a device as a source or as a destination differently from how you assigned the device when you created the service.

Destination Port

The port on the destination device.

If the destination device is an endpoint transponder, then this field refers to a port on that transponder.

If the destination device is a ROADM element, then this field refers to a universal port on that ROADM.

Critical

The number of critical alarms on devices along the service path.1

Major

The number of major alarms on devices along the service path.1

Minor

The number of minor alarms on devices along the service path.1

SA

If the SA indicator is present, then service affecting alarms exist.

1 This is a count of the following alarms in optical network equipment along the service path (including alarms at the tail facility endpoints):

  • port and EDFA alarms in the service path

  • connection and channel alarms in the service path

Orphan Service

An orphan service is a service without two add/drop endpoints. If you see an orphan service displayed, it is an indication that you have misconfigured the ROADM topology or otherwise altered the ROADM topology (such as unplugging and plugging fibers to different devices when LLDP is enabled) after the service is created.

The proNX Optical Director only allows you to create an optical service if a path exists between the two add/drop endpoints at the time that you create the service. If, after you create the service, you change the ROADM topology (such as by deleting links or undiscovering ROADM devices) such that the original path no longer exists between the two endpoints, the proNX Optical Director shows the service as two orphan services, one for each endpoint.

The reason for this is that, after the ROADM topology change, the proNX Optical Director cannot reconcile the intended service path with the new ROADM topology and therefore cannot display the full service path. It is only able to display the path from each endpoint to where the topology is broken. Note that this behavior can be different for a cut fiber. In the case of a cut fiber on a line span, the proNX Optical Director still knows where the intended path is as long as the associated external link is provisioned. In this case, the service is shown with a link that is down, and not as a pair of orphan services.

When you fix the ROADM topology, the proNX Optical Director will display the service correctly once again.

To prevent this from happening, ensure you do not change the ROADM topology after you create the service.

Viewing a Service

Procedure

Use this procedure to view a provisioned service.

  1. Click the Network tab and select Services>Provisioned in the left-nav bar.

    A list of services in your network appears.

  2. Select the service you want to view and click View.

    The service appears in a new window. The window shows a visual representation of the service and the list of alarms associated with the devices that are part of the service. Figure 7 shows an example of the service view:

    Figure 7: Service View Example

    Service View Example

    At the top is the title that indicates the source and destination devices and the wavelength used to connect them. The upper left corner of the main service view area shows a count of the number of alarms on the devices that are part of the service. In this case, there is one minor alarm. Below the alarm counts is a visual representation of the service, which shows the service endpoints connected to each other through two or more devices.

    An endpoint of a service is displayed as follows:

    • If the endpoint is a supported tail facility endpoint, then the endpoint is shown as an interface on the supported tail facility device.

    • If the endpoint is an alien endpoint attached to a universal port on a TCX1000-RDM20, then the endpoint is shown as a universal port on the TCX1000-RDM20.

    • If the endpoint is an alien endpoint attached to a client port on an FMD96, then the endpoint is shown as a client port on the FMD96.

    • If the endpoint is an alien endpoint attached to a client port on a 2D8CMD, then the endpoint is shown as a line port on the 2D8CMD. The reason for displaying the endpoint as a line port is that the 2D8CMD is colorless, so the wavelength is seen by all client ports (and not exclusively by a single client port) on the multiplexer/demultiplexer.

      Note The proNX Optical Director does not keep track of which 2D8CMD client port is physically connected to the alien endpoint. You will need to keep track of that physical connection yourself.

    In this example, the service view shows a service with an endpoint on an MX Series router on the left connecting across ROADM elements to an alien endpoint on the right. You can see that this is an alien endpoint because the service view shows the endpoint as a port on a ROADM element, in this case, a line port on a 2D8CMD, which you can confirm by hovering over the endpoint to see the endpoint details (see Figure 8).

    The service representation is color-coded as follows:

    • An endpoint is green if the port that it represents is administratively in-service. An endpoint is red if the port that it represents is administratively out-of-service.

    • Links between devices are shown with solid lines. The line is green if the link is operationally up. The line is red if the link is operationally down.

    Below the service view is an alarms table showing the current alarms on the devices that are part of the service. See Field Descriptions for a description of the table headings.

  3. Hover over links, devices, and ports to see more information on a link, device, or port. For example:

    Figure 8: Hovering on an Endpoint

    Hovering on an Endpoint
  4. You can pan the service view and zoom in and out using the scroll wheel as desired. To reset the view, click the Reset View icon.
  5. To view and graph telemetry data, click the Telemetry button. The Telemetry panel appears.
    1. Specify the time Duration that you want to view and graph the telemetry data.

    2. Select the telemetry Metric from the drop-down list. You have the option of selecting the transmit and receive power pairs in each direction. You can only select one direction at a time.

    3. Click Start to start telemetry data collection and graphing.

    4. Click Pause to pause the graphing of telemetry data. Telemetry data continues to be collected when paused. To continue graphing, click Start.

    5. Click Stop to stop telemetry data collection and graphing prior to duration expiry.

    6. Click Reset to clear the graph.

    Figure 9 shows an example of the type of graph you can generate:

    Figure 9: Service Telemetry Graph Example

    Service
Telemetry Graph Example
  6. Click Close to close the service window.

Editing or Deleting a Service

Procedure

Use this procedure to view, edit (including changing the administrative state), or delete a provisioned service.

  1. Click the Network tab and select Services>Provisioned in the left-nav bar.

    A list of services in your network appears.

  2. To edit a service, select a service and click Edit.

    The Edit Service dialog appears.

    • To change the Service Name, type the new service name in the box.

    • To change the Admin State, use the drop-down list to specify the new administrative state. When you change the state to IS, the proNX Optical Director sets all cross-connects along the service path to In-Service. When you change the state to OOS, the proNX Optical Director sets all cross-connects along the service path to Out-of-Service.

    Click Save to save your changes or Cancel to discard them.

  3. To delete a service, select a service and click Delete.

    A confirmation dialog appears. Click Delete to confirm.

About the Services Create Page

To access this page, click the Network tab and select Services>Create Service in the left-nav bar.

This is the main page where you create an optical service.

Tasks You Can Perform

You can create an optical service between specified endpoints. See Table 53 for the different endpoints that you can specify. As part of service creation, the proNX Optical Director automatically configures the cross-connects on all the devices along the service path.

Field Descriptions

Table 55 explains the fields in the Services Create page.

Table 55: Fields in the Services Create Page

Field

Description

Service Type

Specify whether the service is Single Path or Protected.

A single path service is a service that has only a single path set up between the two service endpoints.

A protected service is a service that has a pair of paths set up between the two service endpoints. When you create a protected service, you specify the in-service (IS) path, and the proNX Optical Director automatically determines and configures the out-of-service (OOS) path.

Source

 

Site

The name of the site where the source device is located.

 

Device

The name and/or the IP address of the source device.

The source device can be an endpoint transponder attached to the optical network, or a ROADM element at the optical network edge.

Note: A multiplexer/demultiplexer is modeled as part of a ROADM element.

 

Endpoint

The port on the source device.

If the source device is an endpoint transponder, then this field specifies a port on that transponder.

If the source device is a ROADM element, then this field specifies a universal port on that ROADM.

In both cases, the drop-down list shows entries with annotations that further describe the entries:

  • If the endpoint is a port on a transponder, the annotations show which universal port(s) the transponder port is connected to and whether the connection is going through a multiplexer/demultiplexer.

  • If the endpoint is a port on a ROADM element, the annotations show which universal ports are not connected, which universal ports are connected to a multiplexer/demultiplexer, and which universal ports are connected directly to an endpoint transponder.

Destination

 

Site

The name of the site where the destination device is located.

 

Device

The name and/or IP address of the destination device.

The destination device can be an endpoint transponder attached to the optical network, or a ROADM element at the optical network edge.

Note: A multiplexer/demultiplexer is modeled as part of a ROADM element.

 

Endpoint

The port on the destination device.

If the destination device is an endpoint transponder, then this field specifies a port on that transponder.

If the destination device is a ROADM element, then this field specifies a universal port on that ROADM.

In both cases, the drop-down list shows entries with annotations that further describe the entries:

  • If the endpoint is a port on a transponder, the annotations show which universal port(s) the transponder port is connected to and whether the connection is going through a multiplexer/demultiplexer.

  • If the endpoint is a port on a ROADM element, the annotations show which universal ports are not connected, which universal ports are connected to a multiplexer/demultiplexer, and which universal ports are connected directly to an endpoint transponder.

Details

 

Wavelength

The wavelength of the service.

 

Admin State

The administrative state of the service. For a protected service, this is the administrative state of the IS path.

 

Name

Optional, the name of the service.

Computed Path Options

 

Index

An index assigned by the proNX Optical Director for this entry. This index is only used on this page. It is not referred to or displayed on other pages.

 

Service Name

A name assigned by the proNX Optical Director to describe the service. This name is only used on this page. It is not referred to or displayed on other pages.

 

Path Description

The path that the service takes across the network.

 

Service Preview

A visual preview of the service. The service is shown from universal port to universal port. The tail facility and the multiplexer/demultiplexer ports (if applicable) are not displayed.

Creating a Single Path Service

Before You Begin

Prerequisites

Procedure

Use this procedure to create a new single path optical service.

  1. Click the Network tab and select Create Service in the left-nav bar.

    The Services Create page appears.

  2. Set the Service Type to Single Path.
  3. Use the drop-down lists to specify the source and destination Site, Device, and Endpoint. Once you select the Site, the Device drop-down list only shows the devices at the selected site. Once you select the Device, the Endpoint drop-down list only shows the ports on the selected device.

    Note  The source and destination assignments are used only to distinguish between the two endpoints and can be assigned arbitrarily.

    How you select the Endpoint from the drop-down lists differs slightly depending on the type of endpoint (see Table 56).

    Table 56: Port Selection Based on Type of Endpoint (Single Path)

    Type of Endpoint

    Port Selection

    Supported Tail Facility Endpoint

    Select the tail facility endpoint directly using the drop-down lists by selecting the tail facility device and port. This is the easiest method.

    Alternatively, you can proceed as follows:

    • If the supported tail facility endpoint is topologically connected to a universal port on a TCX1000-RDM20, select the universal port. To help you select the correct universal port, the Endpoint drop-down list shows annotations that identify the tail facility endpoint connected to that universal port.

    • If the supported tail facility endpoint is topologically connected to a client port on a multiplexer/demultiplexer, select the universal port on the TCX1000-RDM20 that is connected to the multiplexer/demultiplexer. To help you select the correct universal port, the Endpoint drop-down list shows entries with annotations that identify the tail facility endpoints reachable from that universal port. There can be more than one tail facility endpoint displayed for the same universal port because different tail facility endpoints can connect to different client ports on the same multiplexer/demultiplexer. Pick the entry with the annotation to the desired tail facility endpoint.

    Note: If you are setting up a service to a supported tail facility endpoint attached to a 2D8CMD, the Endpoint drop-down list might show multiple entries to the same tail facility endpoint because there might be multiple paths to that endpoint (via line port L0 or L1). Look through the annotated entries to pick the entry that uses the desired line port on that device.

    Alien Endpoint

    Select the universal port on the TCX1000-RDM20 as follows:

    • If the alien device is attached directly to the TCX1000-RDM20, select the universal port on the TCX1000-RDM20 that is attached to the alien device. This port is topologically unconnected.

    • If the alien device is attached to a client port on a multiplexer/demultiplexer, select the universal port on the TCX1000-RDM20 that is topologically connected to the multiplexer/demultiplexer. To help you select the correct universal port, the Endpoint drop-down list shows annotations that identify the multiplexer/demultiplexer connected to that universal port.

      Note: The same multiplexer/demultiplexer might have a mix of client ports, with some attached to alien endpoints and others attached to supported tail facility endpoints. In this case, the Endpoint drop-down list shows multiple annotated entries for the universal port connecting to that multiplexer/demultiplexer. Select the entry for the port and not the entries with the annotated supported tail facility endpoints.

      Note: The proNX Optical Director does not keep track of which 2D8CMD client port is physically connected to the alien endpoint. You will need to keep track of that physical connection yourself.

  4. Specify the Wavelength.

    You cannot change the wavelength if the endpoints that you specify are already associated with a wavelength. For example, if you specify a tail facility endpoint that is already configured for a specific wavelength, the proNX Optical Director uses that wavelength for the service.

  5. Set the Admin State of the service.
  6. Optionally, specify the Name of the service.
  7. Scroll down to verify the Computed Path Options.

    The Computed Path Options consist of a list of all possible paths and a service preview. The proNX Optical Director chooses one of the paths to display in the preview.

    Use the scroll wheel to zoom in or out in the service view. To reset the view, click the Reset View icon.

  8. Select the path you want to create (if multiple paths exist) and click Create to create the service. Otherwise, click Reset to discard your changes and start over.

The proNX Optical Director sets up the service by configuring the cross-connects on all devices along the service path. To monitor the progress of this task, see Viewing the Tasks List.

Creating a Protected Service

Before You Begin

Prerequisites

Procedure

Use this procedure to create a new protected optical service between endpoints attached to client ports on 2D8CMD multiplexer/demultiplexers.

  1. Click the Network tab and select Create Service in the left-nav bar.

    The Services Create page appears.

  2. Set the Service Type to Protected.

    When you set the Service Type to Protected, you configure the IS path in the steps below. You do not need to explicitly configure the OOS path. The proNX Optical Director automatically determines and configures the OOS path for you. The Computed Path Options for both the IS path and the OOS path are displayed at the bottom of the page.

  3. Use the drop-down lists to specify the source and destination Site, Device, and Endpoint for the IS path. Once you select the Site, the Device drop-down list only shows the devices at the selected site. Once you select the Device, the Endpoint drop-down list only shows the ports on the selected device.

    Note  The source and destination assignments are used only to distinguish between the two endpoints and can be assigned arbitrarily.

    How you select the Endpoint from the drop-down lists differs slightly depending on the type of endpoint (see Table 57).

    Table 57: Port Selection Based on Type of Endpoint (Protected)

    Type of Endpoint

    Port Selection

    Supported Tail Facility Endpoint

    Select the tail facility endpoint directly using the drop-down lists by selecting the tail facility device and port.

    Note: If you set up the topology correctly, the Endpoint drop-down list shows multiple entries to the same tail facility endpoint because there are multiple paths to that endpoint (via line port L0 or L1). Look through the annotated entries to pick the entry that corresponds to the desired IS path.

    Alien Endpoint

    Select the L0 or L1 port on the 2D8CMD that corresponds to the desired IS path.

    Note: The proNX Optical Director does not keep track of which 2D8CMD client port is physically connected to the alien endpoint. You will need to keep track of that physical connection yourself.

  4. Specify the Wavelength.

    You cannot change the wavelength if the endpoints that you specify are already associated with a wavelength. For example, if you specify a tail facility endpoint that is already configured for a specific wavelength, the proNX Optical Director uses that wavelength for the service.

  5. Set the Admin State of the service. This is the administrative state of the IS path.

    You cannot set the administrative state of the OOS path. It is always OOS when you create the service.

  6. Optionally, specify the Name of the service.
  7. Scroll down to verify the Computed Path Options for both the IS and OOS paths. The proNX Optical Director automatically determines and configures the OOS path based on the wavelength and endpoints you select for the IS path.

    Use the scroll wheel to zoom in or out in the service view. To reset the view, click the Reset View icon.

  8. Select the path you want to create (if multiple paths exist) and click Create to create the service. Otherwise, click Reset to discard your changes and start over.

The proNX Optical Director sets up the service by configuring the cross-connects on all devices along the IS and OOS service paths. To monitor the progress of this task, see Viewing the Tasks List.

Help us to improve. Rate this article.
Feedback Received. Thank You!

Ask questions in TechWiki

Check documentation in TechLibrary

Rating by you:      
X

Additional Comments

800 characters remaining

May we contact you if necessary?

Name:
Email:

Need product assistance? Contact Juniper Support

Submit