Optical Transport Network (OTN) Interfaces
The QFX10K-12C-DWDM line card supports the optical transport interfaces (OTN) which is used for high end packet forwarding by cloud providers, service providers and enterprises. There are various optic-specific options that can be configured on the QFX10K-12C-DWDM line card including the forward error correction (FEC) mode and enabling the threshold crossing alarms.
Understanding the QFX10K-12C-DWDM Line Card
The QFX10000-12C-DWDM line card provides up to 1.2 Tbps packet forwarding for cloud providers, service providers, and enterprises that need coherent dense wavelength-division multiplexing (DWDM) with MACsec security features.
The QFX10K-12C-DWDM line card is supported on Junos OS Release 17.2R1 and later.
The following sections explain the features of the QFX10K-12C-DWDM line card in detail:
Software Features
The following interface features are supported on the QFX10000-12C-DWDM:
Compliant with ITU G.709 and G.798
Performance monitoring features such as alarms, threshold-crossing alarms, OTU/ODU error seconds, and FEC and bit error rate (BER) statistics.
SNMP management of the MIC based on RFC 3591, Managed Objects for the Optical Interface Type, including the following:
Black Link MIB–jnx-bl.mib
IFOTN MIB–jnx-ifotn.mib
Optics MIB–jnx-optics.mib
FRU MIB–jnx-fru.mib
User-configurable optics options:
Modulation format: 16QAM, 8QAM, QPSK
FEC mode (15% SDFEC or 25% SDFEC)
Differential and non-differential encoding modes
Transmit (TX) laser enable and disable
TX output power
Wavelength
Threshold crossing alarms (TCAs)
IEEE 802.1ag OAM
IEEE 802.3ah OAM
IFINFO/IFMON
IEEE 802.3ad link aggregation
Flexible Ethernet services encapsulation
Flexible VLAN tagging
Source address MAC accounting per logical interface
Source address MAC filter per port
Source address MAC filter per logical interface
Destination address MAC filter per port
Up to 8000 logical interfaces shared across all ports on a single PFE
OTN Alarms and Defects
The following OTN alarms and defects are supported on the QFX10K-12C-DWDM line card:
Optical Channel(OC) Alarms and Defects
OC-LOS—Loss Of Signal
OC-LOF—Loss Of Frame
OC-LOM—Loss Of Multiframe
OC-Wavelength-Lock—Wavelength Lock
Optical Channel Data Unit (ODU) Defects
ODU-AIS—ODU Alarm Indication Signal
ODU-BDI—ODU Backward Defect Indication
ODU-IAE—ODU Incoming Alignment Error
ODU-LCK—ODU Locked
ODU-LTC—ODU Loss of Tandem Connection
ODU-OCI—ODU Open Connection Error
ODU-SSF—ODU Server Signal Failure
ODU-TSF—ODU Trail Signal Failure
ODU-TTIM—ODU Trail Trace Identifier Mismatch
Optical Channel Transport Unit (OTU) Defects
OTU-AIS—OTU Alarm Indication Signal
OTU-BDI—OTU Backward Defect Indication
OTU-BIAE—OTU Backward Incoming Alignment Error
OTU-FEC-DEG—OTU Forward Error Correction Degrade
OTU-FEC-EXCESS-FEC—OTU Forward Error Correction Excessive FEC Errors
OTU-IAE—OTU Incoming Alignment Error
OTU-SSF—OTU Server Signal Failure
OTU-TSF—OTU Trail Signal Failure
OTU-TTIM—OTU Trail Trace Identifier Mismatch
Threshold-Crossing Alarms
Threshold-crossing alarms (TCA) are alarms that are activated when a certain configurable threshold —near-end measurement threshold or far-end measurement threshold—is crossed and remains so until the end of the 15 minutes interval for parameters such as OTU and ODU. The following alarms are supported:
Background block error threshold (BBE)
Errored seconds threshold (ES)
Severely errored seconds threshold (SES)
Unavailable seconds threshold (UES)
Configuring OTN Interface Options on QFX10K-12C-DWDM
The QFX10000-12C-DWDM line card provides up to 1.2 Tbps packet forwarding for cloud providers, service providers, and enterprises that need coherent dense wavelength-division multiplexing (DWDM) with MACsec security features. The QFX10K-12C-DWDM line card is supported on Junos OS Release 17.2R1 and later.
Each QFX10K-12C-DWDM has 6 physical interfaces (ot-x/x/x) that connect to one of three built-in flexible rate optical transponders. Each transponder connects four 100-Gigabit Ethernet logical interfaces (et-x/x/x) to one of three forwarding ASICs.
To configure the optics-specific options on the interface:
To configure the OTN-specific options on the interface:
At the [
edit interfaces interface-name otn-options
] enable the laser on the OTN interface. The laser is disabled by default for all OTN interfaces.[edit interfaces interface-name otn-options] user@host# set laser-enable
Set an trail trace identifier for the source access point and for the destination access point for ODU and OTU on the OTN interface.
[edit interfaces interface-name otn-options] user@host# set tti (odu-dapi | odu-expected-receive-dapi | odu-expected-receive-sapi | odu-sapi | otu-dapi | otu-expected-receive-dapi | otu-expected-receive-sapi | otu-sapi)
By default, triggers are ignored. Specify defect triggers and the set the trigger hold time for the trigger. Possible values for the trigger hold time are as follows: down—Delay before marking interface down when defect occurs (1..65534 milliseconds) and up—Delay before marking interface up when defect is absent (1..65534 milliseconds).
Note:The hold time value only impacts the alarm reporting time and does not mark an interface down when the defect occurs. To mark the interface up or down, you must also configure the physical interface hold time at the [
edit interfaces interface-name
] hierarchy level.[edit interfaces interface-name otn-options] user@host# set trigger (oc-lof | oc-lom | oc-los | oc-tsf | odu-ais | odu-bdi | odu-bei | odu-iae | odu-lck | odu-oci | odu-sd | odu-ttim |opu-ptim | otu-ais | otu-bdi | otu-fec-deg | otu-fec-exe | otu-iae | otu-sd | otu-ttim) (hold-time (down value | up value) | ignore)
Enable the threshold crossing alarms for the OTN interface along with the trigger for the defect.
[edit interfaces interface-name otn-options] user@host# set tca (odu-tca-bbe | odu-tca-es | odu-tca-ses | odu-tca-uas | otu-tca-bbe | otu-tca-es | otu-tca-ses | otu-tca-uas ) (enable-tca | no-enable-tca | threshold)
Set the OTN header bytes as a transmit payload type from 0 bytes through 255 bytes for the packets that are transmitted on the OTN interface.
[edit interfaces interface-name otn-options] user@host# set bytes transmit-payload-type value
Configure the forward error correction (FEC) mode for the OTN interface. Possible values are: Generic Forward Error Correction (GFEC), or High Gain Forward Error Correction (HGFEC) or Soft Decision Forward Error Correction (SDFEC). The default forward error correction mode is SDFEC.
[edit interfaces interface-name otn-options] user@host# set fec (gfec | hgfec | sdfec)
Enable line loopback or local host loopback for the OTN interface.
[edit interfaces interface-name otn-options] user@host# set line-loopback user@host# set local-loopback
Enable an ODU locked maintenance signal on the OTN interface to send the signal pattern 01010101.
[edit interfaces interface-name otn-options] user@host# set insert-odu-lck
Enable an ODU open connection indication signal on the OTN interface to send to send the signal pattern 01100110.
[edit interfaces interface-name otn-options] user@host# set insert-odu-oci
Enable a consequent action as listed in the ITU-T G.798 standard for ODU trail trace identifier mismatch (TTIM) on the OTN interface.
[edit interfaces interface-name otn-options] user@host# set odu-ttim-action-enable
Enable a consequent action as listed in the ITU-T G.798 standard for OTU trail trace identifier mismatch (TTIM) on the OTN interface.
[edit interfaces interface-name otn-options] user@host# set out-ttim-action-enable
Configure the OTN payload pseudorandom binary sequence (PRBS) on the OTN interface.
[edit interfaces interface-name otn-options] user@host# set prbs
Configure the line rate or speed of the OTN signal to OTU4 (100Gbps) for the OTN interface.
Note:If you specify a value other than OTU4, the value is ignored. To verify the line rate, use the
show interfaces interface-name extensive
command.[edit interfaces interface-name otn-options] user@host# set rate otu4
Configure the threshold value for signal degradation when an alarm needs to be raised. Configure the threshold value after signal degradation when the alarm needs to be cleared. When you configure the interval along with the
ber-threshold-signal-degrade value
statement, the bit error rate (BER) must stay above the signal degradation threshold for the configured interval after which the alarm is raised. When the interval is configured along with theber-threshold-clear value
statement, then BER must stay below the clear threshold for the configured interval after which the alarm is cleared.[edit interfaces interface-name otn-options signal-degrade] user@host# set ber-threshold-signal-degrade value user@host# set ber-threshold-clear value user@host# set interval value
Enable the following actions for the preemptive-fast-reroute statement:
Backward FRR—Insert the local pre-FEC status into the transmitted OTN frames and monitor the received OTN frames for the pre-FEC status.
[edit interfaces interface-name otn-options preemptive-fast-reroute] user@host# set backward-frr-enable
ODU backward FRR—Insert the ODU status into the transmitted OTN frames and monitor the received OTN frames for the ODU BER status.
[edit interfaces interface-name otn-options preemptive-fast-reroute] user@host# set odu-backward-frr-enable
Monitoring of signal degradation of pre-FEC OTN frames.
[edit interfaces interface-name otn-options preemptive-fast-reroute] user@host# set signal-degrade-monitor-enable
Monitoring of signal degradation of ODU BER in the received OTN frames.
[edit interfaces interface-name otn-options preemptive-fast-reroute] user@host# set odu-signal-degrade-monitor-enable
Configure the following options for ODU BER signal degradation on the OTN interface:
Configure the threshold for signal degradation for ODU BER when an alarm needs to be raised.
[edit interfaces interface-name otn-options odu-signal-degrade] user@host# set ber-threshold-signal-degrade value
Configure the threshold for ODU BER after signal degradation when the alarm needs to be cleared.
[edit interfaces interface-name otn-options odu-signal-degrade] user@host# set ber-threshold-clear value
When you configure the interval along with the
ber-threshold-signal-degrade value
statement, the ODU bit error rate (BER) must stay above the signal degradation threshold for the configured interval after which the alarm is raised. When the interval is configured along with theber-threshold-clear value
statement, then ODU BER must stay below the clear threshold for the configured interval after which the alarm is cleared.[edit interfaces interface-name otn-options odu-signal-degrade] user@host# set interval value
See Also
Support for 400G-ZR Optics on QFX5220-32CD and QFX5130
400-ZR is a standard for transporting 400Gb Ethernet. The standard aims at a minimum distance of 80 kilometers and implemented on small, pluggable form factor modules such as QSFP-DD.
Some of the applications that use 400-ZR optics fiber are the following:
-
Data Center Interconnectivity (DCI) links
-
Campus DWDM
-
Metro DWDM
Benefit of 400G-ZR Optics Support
-
Low latency and high speed
The following are the guidelines when you configure the 400-ZR optics:
The number of ports supporting the 400G-ZR optics is restricted based on the power budget on the QFX5220-32CD and QFX5130-32CD devices. For better thermal handling and power consumption, 16 ports (0, 3, 4, 7, 8, 11, 12, 15, 16, 19, 20, 23, 24, 27, 28, 31) in zigzag pattern support the 400G-ZR optics. Each port supporting the 400G-ZR optic is mapped to another port. You must configure the mapped port to “unused”. You must also configure the supported ports with a high-power mode to power on the optics module.
For example:
Use the following command to set the corresponding port (port 1) to unused, if the 400G-ZR optic module is connected to port 0:
-
For QFX5220:
set chassis fpc 0 pic 0 port 1 unused
-
For QFX5130:
set interfaces et-0/0/1 unused
These commands power on the port 0.
Use the following commands if the 400G-ZR optics module is connected to port 0:
-
For QFX5220:
set interfaces et-0/0/0 optics-options high-power-mode
-
For QFX5130:
set interfaces et-0/0/0 optics-options high-power-mode
The following table shows the supported ports and corresponding unused ports:
Ports supporting 400G-ZR optic | Corresponding ports to be set unused |
---|---|
0 | 1 |
3 | 2 |
4 | 5 |
7 | 6 |
8 | 9 |
11 | 10 |
12 | 13 |
15 | 14 |
16 | 17 |
19 | 18 |
20 | 21 |
23 | 22 |
24 | 25 |
27 | 26 |
28 | 29 |
31 | 30 |
If the 400G-ZR optics is used in channelized mode (4x100G), the high-power mode configuration needs to be present on channel 0 (for both QFX5130-32CD and QFX5220-32CD).
set interfaces et-0/0/0:0 optics-options high-power-mode
If the 400G-ZR optics module is inserted in an unsupported port, the module is not powered on.
The following alarm is raised on the port:
High power optics can not be supported on the port
The following alarm is raised if the 400G-ZR optics module is plugged into the supported port, but high-power mode configuration is not configured.
optics-options high-power-mode config needed to support high power optics on the port
-
If none of the ports have a 400-ZR optics module, high-power mode and unused port settings are not required.