Instead of using Junos OS CLI statements and operational
commands to configure ODU settings and view the configured parameters,
you can view an image of the OTN port using Connectivity Services
Director to obtain an intuitive and high-level understanding of the
settings and alarms. This view enables you to modify the ODU settings
to suit your network deployment needs in a simplified and optimal
manner. Because the important ODU settings can be configured alongside
the visual representation of the entire chassis that is displayed,
this method of managing the ODU settings provides a consolidated and
cohesive interface for easy administration of the network.
You can perform the following tasks in the ODU Path pane:
View the optical channel data unit (ODU) specifications
that are currently applied on the device, such as wavelength and power
Modify the existing parameters of the optical port to
suit your network needs or resolve any alarms caused by certain interface
settings
To configure the ODU parameters for 10-Gigabit Ethernet
or 100-Gigabit Ethernet dense wavelength-division multiplexing (DWDM)
interfaces:
- From the Junos Space user interface, click the Build icon on the Connectivity Services Director banner.
The workspaces that are applicable to Build mode are displayed
on the Tasks pane.
- From the View selector, select Device View.
The functionalities that you can configure in this view are
displayed.
- From the Device View pane, click the plus sign (+) next
to the My Network tree to expand the tree and select the device for
which you want to define the optical port settings.
The network tree is expanded and the selected device is highlighted.
- From the Tasks pane, select Device Management > View
Physical Inventory.
An image of the device is displayed on the right pane.
- In the image of the device, select an OTN port or interface—for
example, a 100-Gigabit Ethernet OTN PIC installed in a PTX Series
router.
The Optical Port dialog box is displayed. At the lower part
of the dialog box, the OTU Section and ODU Path panes are displayed
in a collapsed form.
- Click the ODU Path header at the bottom of
the dialog box.
The ODU Path pane is expanded and displayed.
- Click the Status/Config tab at the bottom of
the dialog box.
The configuration settings that pertain to the ODU are displayed.
- In the Status section, the ODU Status field is displayed.
The ODU Status field displays the status of the ODU (optical
channel data unit). Possible values are:
CSF (client signal failure)
ODU-DM-TIMEOUT (DM timeout)
ODU-LCK (ODU lock triggers for PM [path monitoring]
and TCM levels 1 through 6)
ODU-AIS (alarm indication signal or all ones
signal)
ODU-OCI (open connection error)
ODU-BDI (backward defect indication)
ODU-DEG (ODU degraded)
ODU-IAE (incoming alignment error)
ODU-DAPI-TTIM (DAPI or DAPI/SAPI mismatch from
expected to receive)
ODU-SAPI-TTIM (SAPI or DAPI/SAPI mismatch from
expected to receive)
ODU-BEI (backward error indication)
ODU-BEI-ERR (backward error indication error)
ODU-BIP8-ERR (bit interleaved parity 8 error)
ODU-SSF (server signal fail)
ODU-TSF (trail signal fail)
ODU-SD (signal degrade
- In the Config section, do the following:
From the ODU Backward FRR list, specify whether you want
to enable or disable backward fast reroute (FRR) insertion. You can
insert the ODU status into the transmitted OTN frames and monitor
the received OTN frames for the ODU BER status. By default, FRR ODU
backward FRR insertion is disabled.
From the ODU Signal Degrade Monitor list, specify whether
you want to enable or disable monitoring of signal degradation of
ODU BER in the received OTN frames. By default, FRR signal degrade
monitoring disabled.
- Depending on the configured trace identifier (TTI), any
of the following TTI sections are displayed in the OTU Section pane:
odu-dapi—ODU Destination Access Point Identifier.
odu-expected-receive-dapi—ODU Expected Receive Destination
Access Point Identifier.
odu-expected-receive-sapi—ODU Expected Receive Source
Access Point Identifier.
odu-sapi—ODU Source Access Point Identifier.
out-dapi—OTU Destination Access Point Identifier.
out-expected-receive-dapi—OTU Expected Receive Destination
Access Point Identifier.
out-expected-receive-sapi—OTU Expected Receive Source
Access Point Identifier.
out-sapi—OTU Source Access Point Identifier
- In the TTI-DAPI section, do the following:
The Tx Trace and Rx Trace fields display the transmitted
and received path trace values. A path trace identifier is a text
string that identifies the circuit. The text string that identifies
the circuit. SONET/SDH interfaces allow path trace bytes to be sent
inband across the SONET/SDH link. Juniper Networks and other router
manufacturers use these bytes to help diagnose misconfigurations and
network errors by setting the transmitted path trace message so that
it contains the system hostname and name of the physical interface.
The received path trace value is the message received from the routing
device at the other end of the fiber. The transmitted path trace
value is the message that this routing device transmits.
In the Tx Trace config field, specify the propagated
path trace identifier. A common convention is to use the circuit identifier
as the path trace identifier.
In the Rx Trace Config field, specify the received path
trace identifier. A common convention is to use the circuit identifier
as the path trace identifier.
- In the TTI-DAPI section, do the following:
The Tx Trace and Rx Trace fields display the transmitted
and received path trace values. A path trace identifier is a text
string that identifies the circuit. The text string that identifies
the circuit. SONET/SDH interfaces allow path trace bytes to be sent
inband across the SONET/SDH link. Juniper Networks and other router
manufacturers use these bytes to help diagnose misconfigurations and
network errors by setting the transmitted path trace message so that
it contains the system hostname and name of the physical interface.
The received path trace value is the message received from the routing
device at the other end of the fiber. The transmitted path trace
value is the message that this routing device transmits.
In the Tx Trace config field, specify the propagated path
trace identifier. A common convention is to use the circuit identifier
as the path trace identifier.
In the Rx Trace Config field, specify the received path
trace identifier. A common convention is to use the circuit identifier
as the path trace identifier.
- Click Update at the top of the dialog box to
save the modified ODU settings.
You can click the Refresh (rotating arrow icon) button
at the top of the dialog box to enable the latest settings be retrieved
from the device and displayed.
You can collapse the contents of a particular section by clicking
the minus sign (-) beside the header and expand the contents of a
section by clicking the plus sign (+) beside the header.
