To access this page, start from the Devices Configuration page, expand the device tree to see the list of devices, expand a device to see the shelf, expand the shelf to see the circuit packs, expand the circuit pack hierarchy to see the ports, and click the port.
The contents of the Devices Port Config page vary depending on the port. In general, ports in the optical network have fewer parameters while transponder ports (tail facility endpoints) have more parameters because transponders operate at both the optical layer and the physical layer.
You can use the Devices Port Config page to perform the following actions:
View port parameters on TCX1000-RDM20 and TCX1000-ILA devices and on supported tail facility endpoints.
Configure parameters on optical ports on TCX1000-RDM20 devices and on supported tail facility endpoints.
Enable or disable a port on TCX1000-RDM20 devices and on supported tail facility endpoints.
Table 35 through Table 39 show a superset of the fields displayed for the different kinds of ports and transceivers. Not all fields are displayed or are configurable for all ports and transceivers. If a field is grayed out in the user interface page or does not appear at all, then that attribute is not supported for the specified port or transceiver.
Note This document only gives cursory treatment to the various configuration parameters on tail facility ports. Consult the appropriate Junos OS or BTI7800 documentation to see a fuller description of the parameters along with allowed values.
Table 35: Fields in the Devices Port Config Page for Optical Ports
Field | Description |
---|---|
Administrative State | The port’s administrative state:
You can change the administrative state of TCX1000-RDM20 ports only. You cannot change the administrative state of TCX1000-ILA ports. TCX1000-ILA ports are controlled exclusively by the optical control layer of the proNX Optical Director. |
Operational Status | The port’s operational status:
This attribute is read-only. |
Label | The port label for TCX1000-RDM20 ports. This is a character string that you can configure to further describe the port. This string is not used by the proNX Optical Director. |
Table 36: Fields in the Devices Port Optical Config (OCH) Page for Supported Tail Facility Ports
Field | Description |
---|---|
Note: This table contains attributes for the optical channel (OCH). The optical channel represents the optical signal, which, in some transceivers, can contain one or more constituent OTU4 signals. | |
Port State | |
Administrative State | The administrative state. |
Operational Status | The operational status. This is read-only. |
Loopbacks | |
Local Loopback | Enable or disable local loopback. |
Line Loopback | Enable or disable line loopback. |
Configuration | |
Interface Name | The interface name displayed in the format used by the device. This is read-only. |
Modulation Format | The modulation format specifies how an optical channel modulates its constituent OTU4 signal(s). When you configure an optical service between two transponder endpoints, the modulation format must match between the two endpoints. |
Wavelength | The wavelength is specified in the following format: <wavelength> / <frequency> (<channel>) where <channel> is the mutliplexer/demultiplexer channel number. |
Wavelength Spacing | The wavelength spacing (grid). |
FEC Mode | The FEC mode for the optical channel. When you configure an optical service between two transponder endpoints, the FEC Mode must match between the two endpoints. |
Encoding | The encoding for the optical channel. When you configure an optical service between two transponder endpoints, the Encoding must match between the two endpoints. |
Laser Enable | Enables or disables the laser. |
Tx Power | Sets the transmit power (dBm) of the laser. |
CPRWS | Carrier phase recovery window size used for coherent transceivers. |
LOS Alarm Threshold | Sets the Loss-of-Signal alarm threshold. When the received signal power drops below this threshold, an LOS alarm is raised. |
LOS Warning Threshold | Sets the Loss-of-Signal warning threshold. When the received signal power drops below this threshold, an LOS warning is raised. |
Signal Degrade Config | |
Signal Degrade Interval | Specify the interval (ms) over which the BER must stay above the BER Raise Threshold value for the Signal Degrade alarm to be raised. After the alarm is raised, if the BER returns below the BER Clear Threshold value for the specified interval, the alarm is cleared. |
BER Raise Threshold | Specify the BER threshold at which the Signal Degrade alarm is raised (subject to the Signal Degrade Interval requirement). |
BER Clear Threshold | Specify the BER threshold at which the Signal Degrade alarm is cleared (subject to the Signal Degrade Interval requirement). |
Auto-In-Service | |
Enable | Enables or disables auto-in-service (AINS) on the interface. |
Timer | The AINS countdown timer on the interface. |
Custom Settings | |
Custom Setting 1, 2, 3 | Optional customizable text fields for you to enter additional information for the port. These fields are displayed but are otherwise not used by the device. |
Table 37: Fields in the Devices Port OTU Config Page for Supported Tail Facility Ports
Field | Description |
---|---|
Port State | |
Administrative State | The administrative state. |
Operational Status | The operational status. This is read-only. |
Information | |
Interface Name | The interface name displayed in the format used by the device. This is read-only. |
Interface Type | The interface type. This is read-only. |
Configuration | |
Wavelength | The wavelength is specified in the following format: <wavelength> / <frequency> (<channel>) where <channel> is the mutliplexer/demultiplexer channel number. |
Wavelength Spacing | The wavelength spacing (grid). |
OTU Rate | This is read-only. |
FEC Mode | The FEC mode for the OTU signal. When you configure an optical service between two transponder endpoints, the FEC mode must match between the two endpoints. If the transceiver requires you to configure the FEC Mode on the optical channel, then the FEC Mode cannot be set for the OTU signal. |
Loopback Type | The type of loopback. |
PRBS Mode | Configures PRBS (pseudorandom binary sequence) signal generation. |
Laser Enable | Enables or disables the laser. |
Signal Degrade Config | |
Backward FRR | Enable or disable backward fast reroute insertion. When enabled, the local end embeds BER status information into transmitted OTN frames. This allows the far end router or switch to detect and react to signal degrade conditions more quickly. Enable only if the far end supports this feature. |
Signal Degrade | Enable or disable signal degrade monitoring. Signal degrade monitoring allows the router or switch to detect and react to signal degrade conditions. |
Signal Degrade Interval | Specify the interval (ms) over which the BER must stay above the BER Raise Threshold value for the Signal Degrade alarm to be raised. After the alarm is raised, if the BER returns below the BER Clear Threshold value for the specified interval, the alarm is cleared. |
BER Raise Threshold | Specify the BER threshold at which the Signal Degrade alarm is raised (subject to the Signal Degrade Interval requirement). |
BER Clear Threshold | Specify the BER threshold at which the Signal Degrade alarm is cleared (subject to the Signal Degrade Interval requirement). |
Seconds Degraded For Fault | The number of consecutive degraded intervals required to raise a signal degrade fault. When the value is set to 0, signal degrade monitoring is disabled. |
Degraded Threshold Per Second | The threshold used to evaluate whether a 1-second interval is considered a degraded interval. The threshold is the percentage of errored blocks in a 1-second interval. If the percentage of errored blocks detected in a 1-second interval exceeds this threshold, the interval is considered degraded. |
TTI Config | |
TTIM Action | Enable or disable OTU trail trace identifier mismatch verification. When enabled, the local end compares the received trace identifier with the expected trace identifier. If the expected trace identifier does not match the actual received trace identifier, an alarm is raised. A mismatch might indicate that the fiber is connected to the wrong destination. The trace identifier consists of a Source Access Point Identifier (SAPI) followed by a Destination Access Point Identifier (DAPI). Enable only if the far end supports this feature. |
SAPI Tx Trace Config | Sets the SAPI value in the transmitted trace identifier. |
SAPI Rx Trace Config | Displays the SAPI value from the received trace identifier. This is read-only. |
SAPI Expected Rx Trace | Sets the expected SAPI value for the received trace identifier. |
DAPI Tx Trace Config | Sets the DAPI value in the transmitted trace identifier. |
DAPI Rx Trace Config | Displays the DAPI value from the received trace identifier. This is read-only. |
DAPI Expected Rx Trace | Sets the expected DAPI value for the received trace identifier. |
Transmit Trace | Sets the transmitted trace identifier. |
Receive Trace | Displays the received trace identifier. This is read-only. |
Expected Trace | Sets the expected received trace identifier. |
Auto-In-Service | |
Enable | Enables or disables auto-in-service (AINS) on the interface. |
Timer | The AINS countdown timer on the interface. |
Custom Settings | |
Custom Setting 1, 2, 3 | Optional customizable text fields for you to enter additional information for the port. These fields are displayed but are otherwise not used by the device. |
Table 38: Fields in the Devices Port ODU Config Page for Supported Tail Facility Ports
Field | Description |
---|---|
Configuration | |
Interface Name | The interface name displayed in the format used by the device. This is read-only. |
Multiplex Mode | Specifies whether the ODU interface consists of multiplexed subinterfaces. |
Signal Degrade Config | |
Backward FRR | Enable or disable backward fast reroute insertion. When enabled, the local end embeds BER status information into transmitted OTN frames. This allows the far end router or switch to detect and react to signal degrade conditions more quickly. Enable only if the far end supports this feature. |
Signal Degrade | Enable or disable signal degrade monitoring. Signal degrade monitoring allows the router or switch to detect and react to signal degrade conditions. |
Signal Degrade Interval | Specify the interval (ms) over which the BER must stay above the BER Raise Threshold value for the Signal Degrade alarm to be raised. After the alarm is raised, if the BER returns below the BER Clear Threshold value for the specified interval, the alarm is cleared. |
BER Raise Threshold | Specify the BER threshold at which the Signal Degrade alarm is raised (subject to the Signal Degrade Interval requirement). |
BER Clear Threshold | Specify the BER threshold at which the Signal Degrade alarm is cleared (subject to the Signal Degrade Interval requirement). |
TTI Config | |
TTIM Action | Enable or disable ODU trail trace identifier mismatch verification. When enabled, the local end compares the received trace identifier with the expected trace identifier. If the expected trace identifier does not match the actual received trace identifier, an alarm is raised. A mismatch might indicate that the fiber is connected to the wrong destination. The trace identifier consists of a Source Access Point Identifier (SAPI) followed by a Destination Access Point Identifier (DAPI). Enable only if the far end supports this feature. |
SAPI Tx Trace Config | Sets the SAPI value in the transmitted trace identifier. |
SAPI Rx Trace Config | Displays the SAPI value from the received trace identifier. This is read-only. |
SAPI Expected Rx Trace | Sets the expected SAPI value for the received trace identifier. |
DAPI Tx Trace Config | Sets the DAPI value in the transmitted trace identifier. |
DAPI Rx Trace Config | Displays the DAPI value from the received trace identifier. This is read-only. |
DAPI Expected Rx Trace | Sets the expected DAPI value for the received trace identifier. |
Transmit Trace | Sets the transmitted trace identifier. |
Receive Trace | Displays the received trace identifier. This is read-only. |
Expected Trace | Sets the expected received trace identifier. |
Auto-In-Service | |
Enable | Enables or disables auto-in-service (AINS) on the interface. |
Timer | The AINS countdown timer on the interface. |
Table 39: Fields in the Devices Port Page (for all other ports)
Field | Description |
---|---|
Device | The name of the device containing this port. This is read-only. |
Name | The name of the port. This is read-only. |
Administrative State | The port’s administrative state. This is read-only. |
Operational Status | The port’s operational status. This is read-only. |
Use this procedure to configure an optical port on a TCX1000-RDM20 or a port on a supported tail facility endpoint.
To access this page, start from the Devices Configuration page, expand the device tree to see the list of devices, expand a device to see the shelf, expand the shelf to see the circuit packs, expand the circuit pack to see the ports, and click the port. From here, select the interface (OCH, OTU, ODU) from the drop-down list and click Threshold.
Note Not all devices support configurable thresholds. Devices that do not support configurable thresholds do not have the Threshold tab.
The Devices Port Threshold page displays the threshold crossing alert (TCA) configuration for the port. A threshold crossing alert is a configurable warning that triggers when its associated performance monitoring metric exceeds the configured threshold value. TCAs can be configured for both the 15-minute bin and the 24-hour bin. Typically only a subset of the performance monitoring metrics can be controlled using TCAs.
You can view and configure the threshold crossing alerts for the selected port and interface.
Table 40 through Table 42 explain the fields in the Devices Port Threshold page.
Note This document only gives cursory treatment to router and switch configuration parameters. Consult the appropriate Junos OS documentation to see a fuller description of the parameters along with usage tips and exceptions.
Table 40: Fields in the Devices Port Optical Threshold (OCH) Page for Supported Tail Facility Ports
Field | Description |
---|---|
Carrier Frequency Offset (MHz) | Set the maximum and minimum thresholds for the carrier frequency offset in the 15-minute and 24-hour bins, and select the check box to enable them. You can enable the maximum and minimum TCAs separately. |
Module Temperature (°C) | Set the maximum and minimum thresholds for the module temperature in the 15-minute and 24-hour bins, and select the check box to enable them. You can enable the maximum and minimum TCAs separately. |
Rx-Power (dBm) | Set the maximum and minimum thresholds for the receive power in the 15-minute and 24-hour bins, and select the check box to enable them. You can enable the maximum and minimum TCAs separately. |
Tx-Power (dBm) | Set the maximum and minimum thresholds for the transmit power in the 15-minute and 24-hour bins, and select the check box to enable them. You can enable the maximum and minimum TCAs separately. |
FEC-BER | Set the threshold for the FEC bit error rate in the 15-minute and 24-hour bins, and select the check box to enable the TCA. |
Table 41: Fields in the Devices Port OTU Threshold Page for Supported Tail Facility Ports
Field | Description |
---|---|
Near End | |
BBE | Set the threshold for background block errors in the 15-minute and 24-hour bins, and select the check box to enable the TCA. |
ES | Set the threshold for errored seconds in the 15-minute and 24-hour bins, and select the check box to enable the TCA. |
SES | Set the threshold for severely errored seconds in the 15-minute and 24-hour bins, and select the check box to enable the TCA. |
UAS | Set the threshold for unavailable seconds in the 15-minute and 24-hour bins, and select the check box to enable the TCA. |
Far End | |
BBE | Set the threshold for background block errors in the 15-minute and 24-hour bins, and select the check box to enable the TCA. |
ES | Set the threshold for errored seconds in the 15-minute and 24-hour bins, and select the check box to enable the TCA. |
SES | Set the threshold for severely errored seconds in the 15-minute and 24-hour bins, and select the check box to enable the TCA. |
UAS | Set the threshold for unavailable seconds in the 15-minute and 24-hour bins, and select the check box to enable the TCA. |
FEC-BER | |
FEC-BER | Set the threshold for the FEC bit error rate in the 15-minute and 24-hour bins, and select the check box to enable the TCA. |
Table 42: Fields in the Devices Port ODU Threshold Page for Supported Tail Facility Ports
Field | Description |
---|---|
Near End | |
BBE | Set the threshold for background block errors in the 15-minute and 24-hour bins, and select the check box to enable the TCA. |
ES | Set the threshold for errored seconds in the 15-minute and 24-hour bins, and select the check box to enable the TCA. |
SES | Set the threshold for severely errored seconds in the 15-minute and 24-hour bins, and select the check box to enable the TCA. |
UAS | Set the threshold for unavailable seconds in the 15-minute and 24-hour bins, and select the check box to enable the TCA. |
Far End | |
BBE | Set the threshold for background block errors in the 15-minute and 24-hour bins, and select the check box to enable the TCA. |
ES | Set the threshold for errored seconds in the 15-minute and 24-hour bins, and select the check box to enable the TCA. |
SES | Set the threshold for severely errored seconds in the 15-minute and 24-hour bins, and select the check box to enable the TCA. |
UAS | Set the threshold for unavailable seconds in the 15-minute and 24-hour bins, and select the check box to enable the TCA. |
Use this procedure to configure threshold crossing alerts for a port and interface.
The TCAs for the selected port and interface are displayed.
To access this page, start from the Devices Configuration page, expand the device tree to see the list of devices, expand a device to see the shelf, expand the shelf to see the circuit packs, expand the circuit pack to see the ports, and click the port. From here, click Metrics (in releases 2.2 and lower) or Metrics>Historical PMs (in releases 18.4 and higher).
The Devices Port Historical PMs (Metrics) page allows you view selected metrics.
Note To ensure that the metrics are displayed with the correct timestamps, ensure that the devices are configured to use NTP servers. See About the Device NTP Servers Page.
You can use the Devices Port Historical PMs (Metrics) page to perform the following actions:
View the performance monitoring metrics for the port.
Analyze the metrics using Grafana.
Table 43 explains the fields in the Devices Port Historical PMs (Metrics) page.
Table 43: Fields in the Devices Port Historical PMs (Metrics) Page
Field | Description |
---|---|
Time Series | Set the time series or bin length for which you want to display the counters. The counters are collected in 1-minute, 15-minute, and 24-hour bins. Note: Not all devices support the 1-minute bin. |
Time Range | Specify the time period that you want to view. |
Entity | Specify the interface from the drop-down list. |
Metric | Specify the metric from the drop-down list. |
Prerequisites
You have collected the metrics for the device you want to view. See Metric Collection.
Note Management network instability might cause the proNX Optical Director to lose one or more historical PM bins. If you see that some PM bins are missing, you can wait for the next scheduled PM collection or you can perform a manual PM collection to retrieve all bins from the device again. See Collecting Metrics from a Device Manually.
Use this procedure to view historical performance monitoring metrics (PMs) for a port.
The proNX Optical Director stores collected PMs in a database for 30 days and makes them available for viewing. PM data points older than 30 days are purged from the database. The proNX Optical Director supports the collection and display of 1-minute, 15-minute, and 1-day bins. The actual bins collected and displayed depend on what the device supports. PM points in 15-minute bins are timestamped on the hour and at every 15 minutes thereafter. PM points for the 1-day bin are timestamped at midnight (local time of the machine running the web browser accessing the GUI).
The metrics for the port are displayed in table form.
Note Not all devices support the 1 Minute bin. If the 1 Minute bin option does not appear in the drop-down list, then the 1 Minute bin option is not supported for the selected device.
Click inside the Time Range box to open a calendar where you can select the time range. You can choose one of the quick selections (Today, Yesterday, Last 7 Days, Last 30 Days) or you can fully customize your range. Ensure that you specify the correct time in addition to the date.
When you finish specifying the time range, click Apply.
The table displays a snapshot of the selected metric. To refresh
the table at any time, click the button.
Note The graph displays the selected metric without units. To obtain the units for the selected metric, consult the MIB where the selected metric is found.
See the TCX Series Optical Transport System Feature Guide for the list of performance monitoring metrics supported.
To access this page, start from the Devices Configuration page, expand the device tree to see the list of devices, expand an optical device to see the shelf, expand the shelf to see the circuit packs, expand the circuit pack to see the ports, and click an optical port. From here, click Metrics>Telemetry.
The Devices Port Telemetry page allows you view and graph real-time telemetry metrics starting in release 18.4.
You can use the Devices Port Telemetry page to graph real-time telemetry data from an optical port.
Table 44 explains the fields in the Devices Port Telemetry page.
Table 44: Fields in the Devices Port Telemetry Page
Field | Description |
---|---|
Duration | Set the duration in which you want to view and graph the selected telemetry metric(s). |
Metrics | Select the metric(s) you want to view. |
Progress | This field shows the progress of the telemetry metric collection relative to the specified duration. |
Use this procedure to view real-time telemetry data from an optical port.
The proNX Optical Director receives streams of telemetry data from optical devices in the network. This data is used by the Optical Control Layer to manage the optical controls of the optical ports on the devices. A subset of this data is available for viewing using the procedure in this section.
Figure 3 shows an example of the type of graph you can generate:
Figure 3: Port Telemetry Graph Example
The Devices Port Telemetry page appears.
See the TCX Series Optical Transport System Feature Guide for the list of telemetry metrics supported.