Known Issues

This section lists the known issues in this release of the TCX Series Optical Transport System.

For the most complete and latest information about known defects, use the Juniper Networks online Problem Report Search application.

• Known Issues for the TCX1000-RDM20
• Known Issues for the proNX Optical Director

Known Issues for the TCX1000-RDM20

• In some situations, a very low span loss (less than 2 dB) combined with a higher transmit output power at the far end OSC might cause a Receiver Overload alarm to be raised on a TCX1000-RDM20 OSC port.

  Workaround: Add a fixed loss attenuator on either the far end transmit line port or the local receive line port to increase span loss by approximately 3 dB. PR1334598

• If a single fiber is cut in a fiber pair, the receiving device detects the failure and invokes automatic laser shutdown (ALS) procedures. This causes the device at the transmitting end of the fiber to correctly raise an Optical Line Failure alarm. However, this alarm is not properly masked, which results in the alarm being raised and cleared every 5 seconds (approximately) for the duration of the failure. ALS functionality continues to operate and is not affected by this issue.

  Workaround: None. The alarm will clear and remain cleared once the fiber is repaired. PR1318917

Known Issues for the proNX Optical Director

General

• After power is restored following a power outage, the proNX Optical Director might occasionally not recover.

  Workaround: This is a rare occurrence. If, after 15 minutes, the output of the kubectl get pods command from the master node shows that one or more pods have still not changed STATUS to Running, contact JTAC. PR1337857

• When changing port parameters in tail facility ports (for example, a transponder port on a supported router or switch), the changes take effect but are sometimes not displayed.

  Workaround: If the port parameter changes are not displayed on a refreshed page after a few minutes, manually rediscover the tail facility device. PR1330856

• After the proNX Optical Director discovers a TCX1000-RDM20 device that is in factory default state (either because the device is being brought up for the first time or the device has been explicitly reset to factory defaults), some of the initialization tasks that the proNX Optical Director runs on the device might fail. These are shown as failed Device Edit tasks in the Administration>Tasks page.

  Workaround: None required. The proNX Optical Director automatically retries the failed tasks. PR1330318

• The DEMUX Output Power historical PM metric on a TCX1000-RDM20 universal port is not supported but it is collected and displayed in the Port Metrics page. PR1329226
• The web socket between the web browser GUI and the proNX Optical Director server might time out too quickly, causing “Failed to connect to device-service for events” and similar messages to be displayed in the notification area.

  Workaround: None required. The GUI reconnects automatically. Dismiss the message. PR1322304

• The GUI displays the internal software version number for MX Series and PTX Series routers and QFX Series switches.

  Workaround: None required. The last part of the internal software version number indicates the external software version number. PR1316840

Optical Control

• A Tx Span Loss Out of Range alarm, an Rx Span Loss Out of Range alarm, and/or an OTI Communication Failure alarm might occasionally remain raised even when the underlying issue that caused the alarm is resolved.

  Workaround: Rediscover the device with the stuck alarm. PR1332922

Network Topology and Services

• When creating a service with a tail facility endpoint, you can select the tail facility endpoint as the Source Device and Source Endpoint but not as the Destination Device and Destination Endpoint.

  Workaround: To select a tail facility endpoint at the Destination, select the TCX1000-RDM20 as the Destination Device and then use the Destination Endpoint drop-down list to select the desired tail facility endpoint. PR1338788

• When you delete a topology link from the Network>Topology page, the link sometimes remains undeleted.

  Workaround: If the link remains undeleted on a refreshed page after a few minutes, manually rediscover the devices at each end of the link. PR1330606

• A port can be provisioned as an endpoint for more than one topology link.

  Workaround: Before creating a link, ensure the endpoints are not already configured for another link. PR1324934

• Since physical links are not displayed in the service view, the state of physical links does not affect the service view. This can lead to a perceived anomaly where the service view shows all links as green but the service itself is operationally down because a physical link is down.

  Workaround: Use the service state in the Network>Services>Provisioned page as the indicator on whether a service is up or down. PR1324929