100-Gigabit DWDM OTN MIC with CFP2-ACO
Software release |
|
Description |
|
Hardware features |
Note:
The 1-port 100-Gigabit DWDM OTN MIC is not directly interoperable with the 2-port 100-Gigabit DWDM OTN PIC (P1-PTX-2-100G-WDM), but they can both operate over the same DWDM line system. |
Software features |
Note:
For information about configuring the MIC, see Configuring OTN Interfaces on MIC3-100G-DWDM MIC. For information about upgrading the firmware on the PIC, see Upgrading Firmware on the 100-Gigabit DWDM OTN MIC (MIC3-100G-DWDM) .
|
Cables and connectors |
Tip:
You can use the Hardware Compatibility Tool to find information about the pluggable transceivers supported on your Juniper Networks device. The list of supported transceivers for the MX Series is located at https://pathfinder.juniper.net/hct/category/#catKey=100001&modelType;=All&pf;=MX+Series. Note:
When inserting the C form-factor pluggable 2 (CFP2) transceiver, ensure that the transceiver sits tightly in the port. You hear a distinct click sound when the latch locks into the corresponding port. The latch must be fully engaged in the corresponding port for the CFP2 transceiver to function properly. Failing to do so can result in loss of connection. To verify that the CFP2 transceiver module is inserted properly, give a gentle pull by grasping the sides of the module. The module should sit tightly. |
LEDs |
OK/FAIL LED, one bicolor:
LINK LED, one bicolor per port:
Note:
The port is labeled Port 0. |
Alarms, Errors, and Events |
Note:
For OTN alarms, see Table 1. Chassis and MIC:
|
Port (interface):
|
|
Optical channel transport unit (OTU) TCAs:
Optical channel data unit (ODU) TCAs:
Tip:
You can view OTU and ODU TCAs by using the |
|
Note:
If you insert an invalid CFP module, the CLI displays Optics-related status:
Tip:
You can view optics-related status by using the |
|
Network lane receive-related status:
Tip:
You can view network lane receive-related status by using
the |
|
FEC statistics:
Tip:
You can view FEC statistics by using the |
Table 1 describes the OTN alarms and defects that can occur on the MIC and the link status when the alarm or defect occurs.
You can view OTN alarms and defects by using the show
interfaces interface-name extensive
operational-mode
CLI command.
Category |
Alarm |
Description |
Link Status |
---|---|---|---|
OTN |
LOS |
Loss of signal |
Link down |
LOF |
Loss of frame |
Link down |
|
LOM |
Loss of multiframe |
Link down |
|
OTN FEC |
FEC Degrade (OTU-FEC-DEG) |
Forward error correction degraded |
Link down if signal degrade or backward FRR thresholds are met |
FEC Excessive (OTU-FEC-EXE) |
There are uncorrected words and there are errors in the frame header |
Possible link down |
|
OTN OTU |
OTU-AIS |
Alarm indication signal or all ones signal |
Link down |
OTU-BDI |
Backward defect identification |
Link down |
|
OTU-IAE |
Incoming alignment error |
Warning |
|
OTU-TTIM |
Destination access point identifier (DAPI), source access point identifier (SAPI), or both mismatch from expected to received |
Can cause the link to be down if |
|
OTU-BIAE |
Backward incoming alignment error |
Warning |
|
OTU-TSF |
OTU trail signal fail |
Warning |
|
OTU-SSF |
OTU server signal fail |
Warning |
|
OTN ODU |
ODU-AIS |
Alarm indication signal or all ones signal |
Link down |
ODU-OCI |
Open connection error |
Link down |
|
ODU-LCK |
ODU lock triggers for path monitoring and TCM levels 1 through 6 |
Link down |
|
ODU-BDI |
Backward defect indication |
Link down |
|
ODU-TTIM |
DAPI or SAPI mismatch from expected to received |
Can cause the link to be down if |
|
ODU-IAE |
Incoming alignment error |
Warning |
|
ODU-LTC |
Loss of tandem connection |
Warning |
|
ODU-CSF |
Client signal failure |
Warning |
|
ODU-TSF |
Trail signal fail |
Warning |
|
ODU-SSF |
Server signal fail |
Warning |
|
ODU-PTIM |
Payload type mismatch |
Link down |