100GbE, 40GbE, and 10GbE

Overview

Optical transmission leverages properties of light waves, including amplitude, phase, and polarization to optimize the capacity of a fiber optic link.

Optics supports Optical Transport Network (OTN), a standard defined by ITU G.709. The standard defines OTN as a set of optical network elements that are connected by optical fiber links.

Optics performs the following functions on optical channels that carry client signals:

Transport
Multiplexing
Switching
Management
Supervision

Optics bridges the gap between next-generation IP and legacy TDM networks. When you add optics to a Dense Wavelength Division Multiplexing (DWDM) network, you can easily manage a channel. For example, you can configure, troubleshoot, or see alarms. It is a standardized method for transparent transport of services over optical wavelengths. Hence, modification of the client signal does not occur when it passes through the DWDM network.

ITU G.709 standard ensures:

Performance monitoring and alarm management as specified in ITU standard.
Transparent transport of Ethernet signals with optical channel data unit 2 (ODU2) and ODU2e framing on a per-port basis.
Bit error rate (BER) based on pre-forward error correction (pre-FEC). Fast reroute (FRR) uses the pre-FEC BER as an indication of the an OTN link condition.

Benefits

The OTN provides the following benefits:

Enables FEC and thus improves system performance.
Enables alarm handling and thus improves system monitoring.
Protects the network from mixing of heterogeneous services, saves bandwidth, and transfers any traffic transparently.
Supports dedicated Ethernet links at 1GbE, 10GbE, 40GbE, and 100GbE and thus improves scalability.

Supported Features

Table 1: Supported optics features
Features	Description
Interface	Supports: Minimum channel spacing of 6.25GHz and compliant with ITU G.709 FEC statistics, generic FEC, ultra-forward FEC, enhanced FEC, and no-FEC modes of operation GbE local loopback, External clock. Diagnostic tools: Line loopback and local loopback.
	Attributes: The interface names start with prefixes et and ot. OTN payload pseudorandom binary sequence (PRBS) generation and checking by enabling or disabling PRBS. Link-level pause frames can halt the Ethernet interface from transmitting packets for a configured period. SNMP management of the interface based on RFC 3591, Definitions of Managed Objects for the Optical Interface Type: Set functionality Juniper Networks Black-Link MIB Optics MIB FRU MIB
	Performance monitoring (15-minute and 1-day performance monitoring and historic statistics): Near-end and far-end TCA BER FEC Optical
L2 and L3 Features	Supports: MAC statistics, MPLS fast reroute, SNMP, and Flow control. MAC oversized packet counters based on default MTU value or user-configured MTU value. Per-port source address MAC filter, per-destination address MAC filter, per-physical interface source address MAC filter, per-logical interface source address MAC accounting, and source MAC filter per physical interface. 802.3 ah OAM and 802.1 ag OAM. Logical interfaces on an aggregated Ethernet physical interface. VLAN tagging, flexible VLAN tagging, per-VLAN queuing (using Packet Forwarding Engine), and S-VLAN tagging.
Threshold Crossing Alarms	You receive TCA when you cross a certain configurable threshold (near-end measurement threshold or far-end measurement threshold). The TCA remains until the end of the 15-minute interval for parameters such as OTU and ODU
	Supported alarms: Background block error threshold (BBE) Errored seconds (ES) threshold Severely errored second (SES) threshold Unavailable seconds (UAS) threshold

OTN Alarms and Defects

Table 2: OTN Alarms and Defects
OTN Alarms and Defects	Description
CSF	Client Signal Failure
LOS	Loss of signal
LOF	Loss of frame
LOM	Loss of multi frame
SSF	Server Signal Failure
TSF	Trail Signal Fail
OTU-FEC-DEG	FEC Degraded
OTU-FEC-EXE	Excessive Errors, FEC_FAIL from the transponder
OTU-AIS	Alarm Indication Signal
OTU-BDI	Backward Defect Identification
OTU-IAE	Incoming Alignment Error
OTU-TTIM	Destination Access Point Identifier [DAPI], Source Access Point Identifier [SAPI], or both mismatch from expected to be received.
OTU-SD	Signal Degrade
OTU-SF	Signal Fail
ODU-LCK	ODU lock triggers for PM [path monitoring]
ODU-AIS	Alarm indication signal
ODU-OCI	Open connection indication
ODU-BDI	Backward defect indication
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-SSF	Server Signal Fail
ODU-TSF	Trail Signal Fail
ODU-SD	Signal Degrade.
ODU-SF	Signal Fail
OPU-PTM	Payload Type Mismatch.

Supported PICs

Table 1 describes PICs that support optics.

Table 3: Supported PICs
PIC
P1-PTX-24-10G-W-SFPP	PTX3000: Junos OS Release 13.2R2 and later PTX5000: Junos OS Release 12.3R2 and later Junos OS Release 13.2R1 and later
P2-100GE-OTN	Junos OS Release 15.1F6 Junos OS Release 16.1R2 and later Junos OS Release 17.1R1 and later
MIC3-100G-DWDM	Junos OS Release 15.1F5 and 15.1F6 Junos OS Release 17.1R1 and later
PTX-5-100G-WDM	PTX3000: Junos OS Release 15.1F6, Junos OS Release 17.1R1 and later PTX5000: Junos OS Release 15.1F6, Junos OS Release 17.1R1 and later

Configure Optics

This topic provides information about how to configure optics interface, OTN options on an interface, and optics options on an interface.

Configure Interfaces.

To configure the interface-specific options:

Go to the [edit interface interface-name] hierarchy level, where interface-name is in the et-fpc/pic/port format.
Configure the VLAN tagging option on the OTN interface to enable the reception and transmission of 802.1Q VLAN-tagged frames on the interface.
Configure the maximum transmission unit (MTU) size in bytes for the interface.

Configure a VLAN ID for the interface.

Configure the family for the interface.

Configure an IP address for the interface.

Configure OTN Options on the interface

To configure the OTN-related options on the interface:

Go to the [edit interface interface-name otn-options] hierarchy level:
Enable the OTN mode as OTU2e, OTU1e, or OTU2 for the interface.
Note:
fixed-stuff-bytes is for OTU2e rate, no-fixed-stuff-bytes is for OTU1e rate and oc192 is for OTU2 rate. OTU2e and OTU1e rates are applicable for LAN PHY framing mode. OTU2 is applicable for WAN PHY framing mode. Framing mode is to set through the set interfaces framing configuration statement.
Enable the laser on the OTN interface. The laser is disabled by default for all OTN interfaces.

Set a trail trace identifier for the source access point and for the destination access point for ODU and OTU on the OTN interface.

Ignore the trigger for the defect or set the hold time.

Configure the hold time for the defect trigger as:
- up with a value—Wait for the hold time delay before clearing the alarm when the defect is absent on the OTN interface.
- down with a value—Wait for the hold time delay before raising the alarm when the defect occurs for the OTN interface.

Enable the threshold crossing alarms for the OTN interface along with the trigger for the defect.

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.
Configure the forward error correction (FEC) mode as Generic Forward Error Correction (GFEC), Enhanced Forward Error Correction (EFEC), Ultra Forward Error Correction (UFEC), or no-FEC (none) for the OTN interface.
Enable a consequent action as listed in the ITU-T G.798 standard for ODU trail trace identifier mismatch (TTIM) on the OTN interface.
Enable a consequent action as listed in the ITU-T G.798 standard for OTU trail trace identifier mismatch (TTIM) on the OTN interface.
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 remain above the signal degradation threshold for the configured interval after which the alarm is raised. When the interval is configured along with the ber-threshold-clear value statement, then BER must remain below the clear threshold for the configured interval after which the alarm is cleared.
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.
- Monitoring of signal degradation of pre-FEC OTN frames.

Configure Optics Options on the interface

To configure the optics-specific options on the interface:

Specify the modulation format at the [edit interface interface-name optics-options] hierarchy level.

Specify encoding.

Specify the optical transmit laser output power in dBm at the [edit interface interface-name optics-options] hierarchy level. The default transmit laser output value is 0 dBm.

Specify the wavelength of the optics in nanometers.

Supported OTN and Optics Options

Read this topic for information about the supported optics options and OTN options on specific devices.

Supported OTN Options on ACX6360 and ACX5448 Routers
Supported OTN Options on MX Series Routers
Supported OTN Options on PTX Series Routers
Supported Optics Options on ACX6360 and ACX5448-D Routers
Supported Optics Options on PTX10008 and PTX10016 Series Routers

Supported OTN Options on ACX6360 and ACX5448 Routers

Table 4 lists the statements that are supported on Juniper Networks® ACX6360 and ACX5448 routers at the [edit interfaces interface-name otn-options] hierarchy level. Note that the term NA denotes that the statement is not applicable for that particular component:

Table 4: Statements Supported on ACX6360 and ACX5448 Routers
Statement	Options	ACX6360 (18.3R1)	ACX5448 (19.2R1)
`bytes (otn-options)`	`transmit-payload- type value`	Yes	Yes
`insert- odu-lck`	-	Yes	Yes
`insert- odu-oci`	-	Yes	Yes
`is-ma \| no-is-ma`	-	Yes	Yes
`line-loopback \| no-line-loopback`	-	Yes	Yes
`local-loopback \| no-local-loopback`	-	Yes	Yes
`odu-ttim-action- enable \| no-odu-ttim-action- enable`	-	Yes	Yes
`otu-ttim-action- enable \| no-otu-ttim-action- enable`	-	Yes	Yes
`prbs \| no-prbs`	-	Yes	Yes
`preemptive-fast- reroute`	`backward-frr -enable \| no-backward-frr- enable`	Yes	Yes
	`signal- degrade- monitor- enable \| no-signal- degrade- monitor-enable`	Yes	Yes
	`odu-backward- frr-enable \| no-odu-backward- frr-enable`	No	No
	`odu-signal-degrade- monitor-enable \| no-odu-signal-degrade- monitor-enable`	No	No
`tca`	`odu-tca-bbe (enable-tca \| no-enable-tca \| threshold \| threshold-24hrs)`	Yes	Yes
	`odu-tca-bbe-fe (enable-tca \| no-enable-tca \| threshold \| threshold-24hrs)`	Yes	Yes
	`odu-tca-es (enable-tca \| no-enable-tca \| threshold \| threshold-24hrs)`	Yes	Yes
	`odu-tca-es-fe (enable-tca \| no-enable-tca \| threshold \| threshold-24hrs)`	Yes	Yes
	`odu-tca-ses (enable-tca \| no-enable-tca \| threshold \| threshold-24hrs)`	Yes	Yes
	`odu-tca-ses-fe (enable-tca \| no-enable-tca \| threshold \| threshold-24hrs)`	Yes	Yes
	`odu-tca-uas (enable-tca \| no-enable-tca \| threshold \| threshold-24hrs)`	Yes	Yes
	`otu-tca-bbe (enable-tca \| no-enable-tca \| threshold \| threshold-24hrs)`	Yes	Yes
	`otu-tca-bbe-fe (enable-tca \| no-enable-tca \| threshold \| threshold-24hrs)`	Yes	Yes
	`otu-tca-es (enable-tca \| no-enable-tca \| threshold \| threshold-24hrs)`	Yes	Yes
	`otu-tca-es-fe (enable-tca \| no-enable-tca \| threshold \| threshold-24hrs)`	Yes	Yes
	`otu-tca-ses (enable-tca \| no-enable-tca \| threshold \| threshold-24hrs)`	Yes	Yes
	`otu-tca-ses-fe (enable-tca \| no-enable-tca \| threshold \| threshold-24hrs)`	Yes	Yes
	`otu-tca-uas (enable-tca \| no-enable-tca \| threshold \| threshold-24hrs)`	Yes	Yes
	`otu-tca-uas-fe (enable-tca \| no-enable-tca \| threshold \| threshold-24hrs)`	Yes	Yes
`trigger trigger-identifier`	`oc-lof (hold-time (down \| up) \| ignore)`	Yes	Yes
	`oc-lom (hold-time (down \| up) \| ignore)`	Yes	Yes
	`oc-tsf (hold-time (down \| up) \| ignore)`	Yes	Yes
	`odu-ais (hold-time (down \| up) \| ignore)`	Yes	Yes
	`odu-bdi (hold-time (down \| up) \| ignore)`	Yes	Yes
	`odu-bei (hold-time (down \| up) \| ignore)`	Yes	Yes
	`odu-iae (hold-time (down \| up) \| ignore)`	Yes	Yes
	`odu-lck (hold-time (down \| up) \| ignore)`	Yes	Yes
	`odu-oci (hold-time (down \| up) \| ignore)`	Yes	Yes
	`odu-sd (hold-time (down \| up) \| ignore)`	Yes	Yes
	`odu-ttim`	Yes	Yes
	`opu-ptim (hold-time (down \| up) \| ignore)`	Yes	Yes
	`otu-ais (hold-time (down \| up) \| ignore)`	Yes	Yes
	`otu-bdi (hold-time (down \| up) \| ignore)`	Yes	Yes
	`otu-iae (hold-time (down \| up) \| ignore)`	Yes	Yes
	`otu-sd (hold-time (down \| up) \| ignore)`	Yes	Yes
	`otu-ttim (hold-time (down \| up) \| ignore)`	Yes	Yes
`tti tti-identifier`	`odu-dapi identifier`	Yes	Yes
	`odu-expected- receive-dapi identifier`	Yes	Yes
	`odu-expected- receive-sapi identifier`	Yes	Yes
	`odu-sapi identifier`	Yes	Yes
	`otu-dapi identifier`	Yes	Yes
	`otu-expected- receive-dapi identifier`	Yes	Yes
	`otu-expected- receive-sapi identifier`	Yes	Yes
	`otu-sapi identifier`	Yes	Yes

Supported OTN Options on MX Series Routers

Table 5 lists the statements that are supported on 100-Gigabit Ethernet MICs on Juniper Networks® MX Series Universal Routers at the [edit interfaces interface-Nome otn-options] hierarchy level.

Table 5: Statements Supported on 100-Gigabit Ethernet MICs on MX Series Routers
Statement	Options	MIC6-100G-CFP2(MX2010 / MX2020) (13.3R3)	MIC3-100G-DWDM (MX240, MX480, MX960, MX2010, and MX2020) (15.1F5)
`bytes`	`transmit-payload-type value`	No	Yes
`fec`	`(efec \| gfec \| gfec-sdfec \| hgfec\| none \| dsfec\| ufec)`	Yes (`ufec`)	Yes (`gfec`,`hgfec`,`sdfec`)
`insert- odu-lck`	-	Yes	Yes
`insert- odu-oci`	-	Yes	Yes
`is-ma \| no-is-ma`	-	Yes	Yes
`laser-eNoble \| no-laser-eNoble`	-	Yes	Yes
`line-loopback \| no-line-loopback`	-	Yes	Yes
`local-loopback \| no-local-loopback`	-	Yes	Yes
`odu-delay- maNogement`	`bypass \| no-bypass`	No	Yes
	`monitor- end-point \| no-monitor-end-point`	No	Yes
	`number- of-frames value`	No	Yes
	`no-start- measurement \| start- measurement`	No	Yes
`sigNol-degrade`	`ber-threshold -clear value`	Yes	Yes
	`ber-threshold -sigNol-degrade value`	Yes	Yes
	`interval value`	Yes	Yes
`odu-ttim-action- eNoble \| no-odu-ttim-action- eNoble`	-	Yes	Yes
`otu-ttim-action- eNoble \| no-otu-ttim-action- eNoble`	-	Yes	Yes
`prbs \| no-prbs`	-	Yes	Yes
`preemptive-fast- reroute`	`backward-frr -eNoble \| no-backward-frr- eNoble`	Yes	Yes
	`sigNol- degrade- monitor- eNoble \| no-sigNol- degrade- monitor-eNoble`	Yes	Yes
	`odu-backward-frr-eNoble \| no-odu-backward-frr-eNoble`	No	Yes
	`odu-sigNol-degrade- monitor-eNoble \| no-odu-sigNol-degrade- monitor-eNoble`	No	Yes
`rate`	`fixed-stuff-bytes \| no-fixed-stuff-bytes`	Yes	Yes
	`oc192`	Yes	Yes
	`otu4`	Yes	Yes
	`pass-through`	Yes (`pass-through`)	Yes (`pass-through`)
`sigNol-degrade`	`ber-threshold-clear value`	Yes	Yes
	`ber-threshold-sigNol-degrade value`	Yes	Yes
	`interval value`	Yes	Yes
	`q-threshold-sigNol-degrade`	No	Yes
	`q-threshold-sigNol-degrade-clear`	No	Yes
`tca`	`odu-tca-bbe (eNoble-tca \| no-eNoble-tca \| threshold \| threshold-24hrs)`	Yes	Yes
	`odu-tca-bbe-fe (eNoble-tca \| no-eNoble-tca \| threshold \| threshold-24hrs)`	Yes	Yes
	`odu-tca-es (eNoble-tca \| no-eNoble-tca \| threshold \| threshold-24hrs)`	Yes	Yes
	`odu-tca-es-fe (eNoble-tca \| no-eNoble-tca \| threshold \| threshold-24hrs)`	Yes	Yes
	`odu-tca-ses (eNoble-tca \| no-eNoble-tca \| threshold \| threshold-24hrs)`	Yes	Yes
	`odu-tca-ses-fe (eNoble-tca \| no-eNoble-tca \| threshold \| threshold-24hrs)`	Yes	Yes
	`odu-tca-uas (eNoble-tca \| no-eNoble-tca \| threshold \| threshold-24hrs)`	Yes	Yes
	`otu-tca-bbe (eNoble-tca \| no-eNoble-tca \| threshold \| threshold-24hrs)`	Yes	Yes
	`otu-tca-bbe-fe (eNoble-tca \| no-eNoble-tca \| threshold \| threshold-24hrs)`	Yes	Yes
	`otu-tca-es (eNoble-tca \| no-eNoble-tca \| threshold \| threshold-24hrs)`	Yes	Yes
	`otu-tca-es-fe (eNoble-tca \| no-eNoble-tca \| threshold \| threshold-24hrs)`	Yes	Yes
	`otu-tca-fec-ber (eNoble-tca \| no-eNoble-tca \| threshold \| threshold-24hrs)`	Yes	Yes
	`otu-tca-ses (eNoble-tca \| no-eNoble-tca \| threshold \| threshold-24hrs)`	Yes	Yes
	`otu-tca-ses-fe (eNoble-tca \| no-eNoble-tca \| threshold \| threshold-24hrs)`	Yes	Yes
	`otu-tca-uas (eNoble-tca \| no-eNoble-tca \| threshold \| threshold-24hrs)`	Yes	Yes
	`otu-tca-uas-fe (eNoble-tca \| no-eNoble-tca \| threshold \| threshold-24hrs)`	Yes	Yes
transport-monitoring	-	No	Yes
`trigger trigger-identifier`	`oc-lof (hold-time (down \| up) \| ignore)`	Yes	Yes
	`oc-lom (hold-time (down \| up) \| ignore)`	Yes	Yes
	`oc-los (hold-time (down \| up) \| ignore)`	Yes	Yes
	`oc-tsf (hold-time (down \| up) \| ignore)`	No	Yes
	`oc-wavelength-lock (hold-time (down \| up) \| ignore)`	No	Yes
	`odu-ais (hold-time (down \| up) \| ignore)`	Yes	Yes
	`odu-bdi (hold-time (down \| up) \| ignore)`	Yes	Yes
	`odu-bei (hold-time (down \| up) \| ignore)`	Yes	Yes
	`odu-iae (hold-time (down \| up) \| ignore)`	Yes	Yes
	`odu-lck (hold-time (down \| up) \| ignore)`	Yes	Yes
	`odu-oci (hold-time (down \| up) \| ignore)`	Yes	Yes
	`odu-sd (hold-time (down \| up) \| ignore)`	Yes	Yes
	`odu-tca-es`	Yes	No
	`odu-tca-ses`	Yes	No
	`odu-tca-uas`	Yes	No
	`odu-ttim`	Yes	Yes
	`opu-ptim (hold-time (down \| up) \| ignore)`	Yes	Yes
	`otu-ais (hold-time (down \| up) \| ignore)`	Yes	Yes
	`otu-bdi (hold-time (down \| up) \| ignore)`	Yes	Yes
	`otu-fec-deg (hold-time (down \| up) \| ignore)`	No	Yes
	`otu-fec-exe (hold-time (down \| up) \| ignore)`	No	Yes
	`otu-iae (hold-time (down \| up) \| ignore)`	Yes	Yes
	`otu-sd (hold-time (down \| up) \| ignore)`	Yes	Yes
	`odu-tca-es`	Yes	No
	`odu-tca-ses`	Yes	No
	`odu-tca-uas`	Yes	No
	`otu-ttim (hold-time (down \| up) \| ignore)`	Yes	Yes
`tti tti-identifier`	`odu-dapi identifier`y	Yes	Yes
	`odu-dapi-first-byte-nul \| no-odu-dapi-first-byte-nul`	No	Yes
	`odu-expected-receive-dapiidentifier`	Yes	Yes
	`odu-expected-receive-dapi-first-byte-nul\| no-odu-expected-receive-dapi-first-byte-nul`	No	Yes
	`odu-expected-receive-sapi identifier`	Yes	Yes
	`odu-sapi identifier`y	Yes	Yes
	`odu-sapi-first-byte-nul \| no-odu-sapi-first-byte-nul`	No	Yes
	`otu-dapi identifier`	Yes	Yes
	`otu-dapi-first-byte-nul \| no-otu-dapi-first-byte-nul`	No	Yes
	`otu-expected- receive-dapi identifier`	Yes	Yes
	`otu-expected-receive-dapi-first-byte-nul\| no-odu-expected-receive-dapi-first-byte-nul`	No	Yes
	`otu-expected- receive-sapi identifier`	Yes	Yes
	`otu-expected-receive-sapi-first-byte-nul\| no-odu-expected-receive-dapi-first-byte-nul`	No	Yes
	`otu-sapi identifier`	Yes	Yes
	`otu-sapi-first-byte-nul`	No	Yes

Supported OTN Options on PTX Series Routers

Table 6 lists the statements that are supported on 100-Gigabit Ethernet PICs on Juniper Networks® PTX Series Routers at the [edit interfaces interface-name otn-options] hierarchy level.

Table 6: Statements Supported on 100-Gigabit Ethernet PICs on PTX Series Routers
Statement	Options	P1-PTX-2-100G-WDM (PTX5000 / PTX3000) (13.2R1 / 13.3R1)	P2-100GE-OTN (PTX5000) (14,1R2 / 14.2R1)	P1-PTX-24-10G-W-SFPP (PTX5000) (14.2R1)	PTX10K-LC1104 (PTX10008 and PTX10016) (18.3R1)
`bytes (otn-options)`	`transmit-payload- type value`	Yes	Yes	Yes	Yes
`fec`	`(efec \| gfec \| gfec-sdfec \| none \| ufec)`	Yes	Yes (`gfec`, `none`)	Yes	Yes
`insert- odu-lck`	-	Yes	Yes	Yes	Yes
`insert- odu-oci`	-	Yes	Yes	Yes	Yes
`is-ma \| no-is-ma`	-	Yes	NA	Yes	Yes
`laser-enable \| no-laser-enable`	-	Yes	Yes	Yes	Yes
`line-loopback \| no-line-loopback`	-	Yes	Yes	Yes	Yes
`local-loopback \| no-local-loopback`	-	Yes	Yes	Yes	Yes
`odu-delay- management`	`bypass \| no-bypass`	Yes	No	No	Yes
	`monitor- end-point \| no-monitor-end-point`	Yes	No	No	Yes
	`number- of-frames value`	Yes	No	No	Yes
	`no-start- measurement \| start- measurement`	Yes	No	No	Yes
`odu-signal- degrade`	`ber-threshold -clear value`	No No	Yes	No	Yes
	`ber-threshold -signal-degrade value`	No No	Yes	No	Yes
	`interval value`	No	Yes	No	Yes
`odu-ttim-action- enable \| no-odu-ttim-action- enable`	-	Yes	Yes	Yes	Yes
`otu-ttim-action- enable \| no-otu-ttim-action- enable`	-	Yes	Yes	Yes	Yes
`prbs \| no-prbs`	-	Yes	Yes	Yes	Yes
`preemptive-fast- reroute`	`backward-frr -enable \| no-backward-frr- enable`	Yes	Yes	Yes	Yes
	`signal- degrade- monitor- enable \| no-signal- degrade- monitor-enable`	Yes	Yes	Yes	Yes
	`odu-backward- frr-enable \| no-odu-backward- frr-enable`	No	Yes	No	Yes
	`odu-signal-degrade- monitor-enable \| no-odu-signal-degrade- monitor-enable`	No	Yes	No	Yes
`rate`	`fixed-stuff-bytes \| no-fixed-stuff-bytes`	Yes	No	Yes	Yes
	`oc192`	Yes	No	Yes	Yes
	`otu4`	Yes	Yes	No	Yes
	`pass-through \| no-pass-through`	Yes	No	No	Yes
`signal-degrade`	`ber-threshold-clear value`	Yes	Yes	Yes	Yes
	`ber-threshold-signal-degrade value`	Yes	Yes	Yes	Yes
	`interval value`	Yes	Yes	Yes	Yes
`tca`	`odu-tca-bbe (enable-tca \| no-enable-tca \| threshold \| threshold-24hrs)`	Yes	Yes	Yes	Yes
	`odu-tca-bbe-fe (enable-tca \| no-enable-tca \| threshold \| threshold-24hrs)`	Yes	No	Yes	Yes
	`odu-tca-es (enable-tca \| no-enable-tca \| threshold \| threshold-24hrs)`	Yes	Yes	Yes	Yes
	`odu-tca-es-fe (enable-tca \| no-enable-tca \| threshold \| threshold-24hrs)`	Yes	No	Yes	Yes
	`odu-tca-ses (enable-tca \| no-enable-tca \| threshold \| threshold-24hrs)`	Yes	Yes	Yes	Yes
	`odu-tca-ses-fe (enable-tca \| no-enable-tca \| threshold \| threshold-24hrs)`	Yes	No	Yes	Yes
	`odu-tca-uas (enable-tca \| no-enable-tca \| threshold \| threshold-24hrs)`	Yes	Yes	Yes	Yes
	`otu-tca-bbe (enable-tca \| no-enable-tca \| threshold \| threshold-24hrs)`	Yes	Yes	Yes	Yes
	`otu-tca-bbe-fe (enable-tca \| no-enable-tca \| threshold \| threshold-24hrs)`	Yes	No	Yes	Yes
	`otu-tca-es (enable-tca \| no-enable-tca \| threshold \| threshold-24hrs)`	Yes	Yes	Yes	Yes
	`otu-tca-es-fe (enable-tca \| no-enable-tca \| threshold \| threshold-24hrs)`	Yes	No	Yes	Yes
	`otu-tca-fec-ber (enable-tca \| no-enable-tca \| threshold \| threshold-24hrs)`	Yes	Yes	Yes	Yes
	`otu-tca-ses (enable-tca \| no-enable-tca \| threshold \| threshold-24hrs)`	Yes	Yes	Yes	Yes
	`otu-tca-ses-fe (enable-tca \| no-enable-tca \| threshold \| threshold-24hrs)`	Yes	No	Yes	Yes
	`otu-tca-uas (enable-tca \| no-enable-tca \| threshold \| threshold-24hrs)`	Yes	Yes	Yes	Yes
	`otu-tca-uas-fe (enable-tca \| no-enable-tca \| threshold \| threshold-24hrs)`	Yes	No	Yes	Yes
transport-monitoring	-	No	No	Yes	Yes
`trigger trigger-identifier`	`oc-lof (hold-time (down \| up) \| ignore)`	Yes	Yes	Yes	Yes
	`oc-lom (hold-time (down \| up) \| ignore)`	Yes	Yes	Yes	Yes
	`oc-los (hold-time (down \| up) \| ignore)`	Yes	Yes	Yes	Yes
	`oc-tsf (hold-time (down \| up) \| ignore)`	Yes	Yes	Yes	Yes
	`oc-wavelength-lock (hold-time (down \| up) \| ignore)`	Yes	No	Yes	Yes
	`odu-ais (hold-time (down \| up) \| ignore)`	Yes	Yes	Yes	Yes
	`odu-bdi (hold-time (down \| up) \| ignore)`	Yes	Yes	Yes	Yes
	`odu-bei (hold-time (down \| up) \| ignore)`	Yes	Yes	Yes	Yes
	`odu-iae (hold-time (down \| up) \| ignore)`	Yes	Yes	Yes	Yes
	`odu-lck (hold-time (down \| up) \| ignore)`	Yes	Yes	Yes	Yes
	`odu-oci (hold-time (down \| up) \| ignore)`	Yes	Yes	Yes	Yes
	`odu-sd (hold-time (down \| up) \| ignore)`	Yes	Yes	Yes	Yes
	`odu-ttim`	Yes	Yes	Yes	Yes
	`opu-ptim (hold-time (down \| up) \| ignore)`	Yes	Yes	Yes	Yes
	`otu-ais (hold-time (down \| up) \| ignore)`	Yes	Yes	Yes	Yes
	`otu-bdi (hold-time (down \| up) \| ignore)`	Yes	Yes	Yes	Yes
	`otu-fec-deg (hold-time (down \| up) \| ignore)`	Yes	Yes	Yes	Yes
	`otu-fec-exe (hold-time (down \| up) \| ignore)`	Yes	Yes	Yes	Yes
	`otu-iae (hold-time (down \| up) \| ignore)`	Yes	Yes	Yes	Yes
	`otu-sd (hold-time (down \| up) \| ignore)`	Yes	Yes	Yes	Yes
	`otu-ttim (hold-time (down \| up) \| ignore)`	Yes	Yes	Yes	Yes
`tti tti-identifier`	`odu-dapi identifier`	Yes	14.1R2 14.2	Yes	Yes
	`odu-expected- receive-dapi identifier`	Yes	Yes	Yes	Yes
	`odu-expected- receive-sapi identifier`	Yes	Yes	Yes	Yes
	`odu-sapi identifier`	Yes	Yes	Yes	Yes
	`otu-dapi identifier`	Yes	Yes	Yes	Yes
	`otu-expected- receive-dapi identifier`	Yes	Yes	Yes	Yes
	`otu-expected- receive-sapi identifier`	Yes	Yes	Yes	Yes
	`otu-sapi identifier`	Yes	Yes	Yes	Yes

Supported Optics Options on ACX6360 and ACX5448-D Routers

Table 7 lists the statements that are supported on ACX6360 and ACX5448-D routers at the [edit interfaces interface-name optics-options] hierarchy level.

Table 7: Statements Supported on ACX6360 and ACX5448-D Routers
Statement	Options	Release (18.2R1, 18.3R1, and 19.2R1-S1)	Interfaces Supported
fec	`sdfec \| sdfec15`	Yes	ot
high-polarization	-	Yes	ot
`laser-enable \| no-laser-enable`	-	Yes	ot
`los-alarm-threshold`	-	Yes	ot
`los-warn-threshold`	-	Yes	ot
modulation-format	`(16qam \| 8qam \| qpsk)`	Yes	ot
`signal-degrade`	`ber-threshold-clear value`	Yes	ot
	`ber-threshold-signal-degrade value`	Yes
	`interval value`	Yes
	`q-threshold-signal-degrade`	Yes
	`q-threshold-signal-degrade-clear`	Yes
`tca`	`carrier-frequency-offset-high-tca (enable-tca \| no-enable-tca \| threshold \| threshold-24hrs)`	Yes	ot
	`carrier-frequency-offset-low-tca (enable-tca \| no-enable-tca \| threshold \| threshold-24hrs)`	Yes
	`fec-ber (enable-tca \| no-enable-tca \| threshold \| threshold-24hrs)`	Yes
	`fec-corrected-errors-high-tca (enable-tca \| no-enable-tca \| threshold \| threshold-24hrs)`	Yes
	`fec-ucorrected-words-high-tca (enable-tca \| no-enable-tca \| threshold \| threshold-24hrs)`	Yes
	`laser-frequency-error-high-tca (enable-tca \| no-enable-tca \| threshold \| threshold-24hrs)`	Yes
	`laser-frequency-error-low-tca (enable-tca \| no-enable-tca \| threshold \| threshold-24hrs)`	Yes
	`pam-histogram-high-tca (enable-tca \| no-enable-tca \| threshold \| threshold-24hrs)`	Yes
	`residual-isi-high-tca (enable-tca \| no-enable-tca \| threshold \| threshold-24hrs)`	Yes
	`residual-isi-low-tca (enable-tca \| no-enable-tca \| threshold \| threshold-24hrs)`	Yes
	`rx-power-high-tca (enable-tca \| no-enable-tca \| threshold \| threshold-24hrs)`	Yes
	`rx-power-low-tca (enable-tca \| no-enable-tca \| threshold \| threshold-24hrs)`	Yes
	`snr-low-tca (enable-tca \| no-enable-tca \| threshold \| threshold-24hrs)`	Yes
	`tec-current-high-tca (enable-tca \| no-enable-tca \| threshold \| threshold-24hrs)`	Yes
	`tec-current-low-tca (enable-tca \| no-enable-tca \| threshold \| threshold-24hrs)`	Yes
	`temperature-high-tca (enable-tca \| no-enable-tca \| threshold \| threshold-24hrs)`	Yes
	`temperature-low-tca (enable-tca \| no-enable-tca \| threshold \| threshold-24hrs)`	Yes
	`tx-power-high-tca (enable-tca \| no-enable-tca \| threshold \| threshold-24hrs)`	Yes
	`tx-power-low-tca (enable-tca \| no-enable-tca \| threshold \| threshold-24hrs)`	Yes
tx-power	dbm	Yes	ot
wavelength	nm	Yes	ot

Supported Optics Options on PTX10008 and PTX10016 Series Routers

Table 8 lists the statements that are supported on Juniper Networks® PTX10008 Router and Juniper Networks® PTX10016 Series Router at the [edit interfaces interface-name optics-options] hierarchy level.

Table 8: Statements Supported on PTX10008 and PTX10016 Series Routers
Statement	Options	Release (18.3R1)	Interfaces Supported
alarm low-light-alarm	link-down \| syslog	Yes	ot
tca carrier-frequency-offset-high-tca	`(enable-tca \| no-enable-tca \| threshold \| threshold-24hrs)`	Yes	ot
tx-power	dbm	Yes	ot
warning low-light-warning	link-down \| syslog	Yes	ot
`laser-enable \| no-laser-enable`	-	Yes	ot
`line-loopback \| no-line-loopback`	-	Yes	ot
`prbs \| no-prbs`	-	Yes	ot
`signal-degrade`	`ber-threshold-clear value`	Yes	ot
	`ber-threshold-signal-degrade value`	Yes
	`interval value`	Yes
`tca`	`odu-tca-bbe (enable-tca \| no-enable-tca \| threshold \| threshold-24hrs)`	Yes	ot
	`odu-tca-bbe-fe (enable-tca \| no-enable-tca \| threshold \| threshold-24hrs)`	Yes
	`odu-tca-es (enable-tca \| no-enable-tca \| threshold \| threshold-24hrs)`	Yes
	`odu-tca-es-fe (enable-tca \| no-enable-tca \| threshold \| threshold-24hrs)`	Yes
	`odu-tca-ses (enable-tca \| no-enable-tca \| threshold \| threshold-24hrs)`	Yes
	`odu-tca-ses-fe (enable-tca \| no-enable-tca \| threshold \| threshold-24hrs)`	Yes
	`odu-tca-uas (enable-tca \| no-enable-tca \| threshold \| threshold-24hrs)`	Yes
	`otu-tca-bbe (enable-tca \| no-enable-tca \| threshold \| threshold-24hrs)`	Yes
	`otu-tca-bbe-fe (enable-tca \| no-enable-tca \| threshold \| threshold-24hrs)`	Yes
	`otu-tca-es (enable-tca \| no-enable-tca \| threshold \| threshold-24hrs)`	Yes
	`otu-tca-es-fe (enable-tca \| no-enable-tca \| threshold \| threshold-24hrs)`	Yes
	`otu-tca-ses (enable-tca \| no-enable-tca \| threshold \| threshold-24hrs)`	Yes
	`otu-tca-ses-fe (enable-tca \| no-enable-tca \| threshold \| threshold-24hrs)`	Yes
	`otu-tca-uas (enable-tca \| no-enable-tca \| threshold \| threshold-24hrs)`	Yes
	`otu-tca-uas-fe (enable-tca \| no-enable-tca \| threshold \| threshold-24hrs)`	Yes
`trigger trigger-identifier`	`oc-lof (hold-time (down \| up) \| ignore)`	Yes	ot
	`oc-lom (hold-time (down \| up) \| ignore)`	Yes
	`oc-los (hold-time (down \| up) \| ignore)`	Yes
	`oc-tsf (hold-time (down \| up) \| ignore)`	Yes
	`oc-wavelength-lock (hold-time (down \| up) \| ignore)`	Yes
	`odu-ais (hold-time (down \| up) \| ignore)`	Yes
	`odu-bdi (hold-time (down \| up) \| ignore)`	Yes
	`odu-bei (hold-time (down \| up) \| ignore)`	Yes
	`odu-iae (hold-time (down \| up) \| ignore)`	Yes
	`odu-lck (hold-time (down \| up) \| ignore)`	Yes
	`odu-oci (hold-time (down \| up) \| ignore)`	Yes
	`odu-sd (hold-time (down \| up) \| ignore)`	Yes
	`odu-ttim`	Yes
	`opu-ptim (hold-time (down \| up) \| ignore)`	Yes
	`otu-ais (hold-time (down \| up) \| ignore)`	Yes
	`otu-bdi (hold-time (down \| up) \| ignore)`	Yes
	`otu-fec-deg (hold-time (down \| up) \| ignore)`	Yes
	`otu-fec-exe (hold-time (down \| up) \| ignore)`	Yes
	`otu-iae (hold-time (down \| up) \| ignore)`	Yes
	`otu-sd (hold-time (down \| up) \| ignore)`	Yes
	`otu-ttim (hold-time (down \| up) \| ignore)`	Yes

Forward Error Correction and Bit Error Rate

OTN interfaces use pre-forward error correction (pre-FEC) BER for monitoring the condition of an OTN link. Read this topic to understand more about how OTN links and the supported FEC modes on devices.

Overview
Supported Forward Error Correction Modes
ODU Path Delay Measurement for Performance Monitoring

Overview

Optical interfaces on PTX Series support monitoring the condition of an optical link by using the pre-forward error correction (pre-FEC) bit error rate (BER). The following PICs support pre-FEC BER monitoring:

P1-PTX-2-100G-WDM
P2-100GE-OTN
P1-PTX-24-10G-W-SFPP

The PICs use forward error correction (FEC) to correct bit errors in the received data. As long as the pre-FEC BER is below the FEC limit, all bit errors are successfully identified and corrected and, therefore, no packet loss occurs. The system monitors the pre-FEC BER on each port. This gives an early warning of link degradation. By configuring an appropriate pre-FEC BER threshold and interval, you enable the PIC to take preemptive action before the FEC limit is reached. If you combine the pre-FEC BER threshold logic with MPLS fast reroute, then you can prevent or minimize packet loss.

You must specify both the signal degradation threshold (ber-threshold-signal-degrade) and the interval (interval) for the interface. The threshold defines the BER criteria for a signal degrade condition and the interval defines the minimum duration over which the BER must exceed the threshold before an alarm is raised. The relationship between the threshold and the interval is illustrated in Figure 1. After an alarm is raised, if the BER returns to a level below the threshold clear value (ber-threshold-clear), the alarm is cleared.

Figure 1: Pre-FEC BER Monitoring

With pre-FEC BER monitoring enabled, when the configured pre-FEC BER signal degrade threshold is reached, the PIC stops forwarding packets to the remote interface and raises an interface alarm. Ingress packets continue to be processed. If pre-FEC BER monitoring is used with MPLS fast reroute or another link protection method, then traffic is rerouted to a different interface.

You can also configure backward fast reroute to insert the local pre-FEC status into transmitted optical frames, notifying the remote interface of signal degradation. The remote interface can use the information to reroute traffic to a different interface. If you use pre-FEC BER monitoring together with backward fast reroute, then notification of signal degradation and rerouting of traffic occurs in less time than that required through a Layer 3 protocol.

Include the signal-degrade-monitor-enable and backward-frr-enable statements at the [edit interfaces interface-name otn-options preemptive-fast-reroute] hierarchy level to enable pre-FEC BER monitoring and backward fast reroute.

Note:

When you configure pre-FEC BER signal degrade monitoring, we recommend that you configure both the signal-degrade-monitor-enable and the backward-frr-enable statements.

You can also configure the pre-FEC BER thresholds that raise or clear a signal degrade alarm and the time interval for the thresholds. If the BER thresholds and interval are not configured, the default values are used.

When a received signal degrade alarm is active and backward fast reroute is enabled, a specific flag is inserted into the trasmitted optics overhead. The remote PIC at the opposite end of the link monitors the optics overhead, thus enabling both ends to initiate traffic rerouting in the event of a signal degrade condition. When the signal degrade condition is cleared, the overhead flag is returned to a normal state.

The pre-FEC BER signal degrade threshold value defines a specific amount of system margin relative to the BER correction limit (or FEC limit) of the PIC’s receive FEC decoder. Each PIC has a set FEC limit—it is intrinsic to the FEC decoder implementation.

Note:

The examples below use Q²-factor measurements (also known as Q-factor). Q²-factor is expressed in units of decibels relative to a Q²-factor of zero (dBQ). Q²-factor enables you to describe system margin in linear terms in contrast to BER values, which are nonlinear in nature. After you determine the thresholds, you must convert the threshold values from Q²-factor to BER to enter them in the CLI by using scientific notation. BER can be converted to Q²-factor by using the following equation:

Tip:

To convert between Q²-factor and BER in a spreadsheet program, you can approximate the values by using the following formulas:

To calculate Q²-factor:

To calculate BER:

Include the ber-threshold-signal-degrade, ber-threshold-clear, and interval statements at the [edit interfaces interface-name otn-options signal-degrade] hierarchy level to configure the BER thresholds and time interval.

Note:

Configuring a high BER threshold for signal degradation and a long interval might cause the internal counter register to be saturated. Such a configuration is ignored by the router, and the default values are used instead. A system log message is logged for this error.

Signal Degrade and Clear Threshold Values for PICs

Table 9 shows the relationship between the fixed FEC limit, the configurable signal degrade threshold, and the configurable clear threshold for different PICs. In this example, approximately 1 dBQ of system margin has been set between the FEC limit, signal degrade threshold, and clear threshold.

Table 9: Example—Signal Degrade and Clear Threshold Values at 1 dBQ
PIC	FEC Type	FEC Limit		Signal Degrade Threshold		Clear Threshold
PIC	FEC Type	Q²-Factor	BER	Q²-Factor	BER	Q²-Factor	BER
P1-PTX-2-100G-WDM	SD-FEC	6.7 dBQ	1.5E–2	7.7 dBQ	7.5E–3	8.7 dBQ	3.0E–3
P2-100GE-OTN	G.709 GFEC	11.5 dBQ	8.0E–5	12.5 dBQ	1.1E–5	13.5 dBQ	1.0E–6
P1-PTX-24-10G-W-SFPP	G.975.1 I.4 (UFEC)	9.1 dBQ	2.2E–3	10.1 dBQ	6.9E–4	11.1 dBQ	1.6E–4
	G.975.1 I.7 (EFEC)	9.6 dBQ	1.3E–3	10.6 dBQ	3.6E–4	11.6 dBQ	7.5E–5
	G.709 GFEC	11.5 dBQ	8.0E–5	12.5 dBQ	1.1E–5	13.5 dBQ	1.0E–6

To adjust the signal degrade threshold, you must first decide on a new system margin target and then calculate the respective BER value (using the equation to convert from Q²-factor to BER). Table 10 shows the values if 3 dBQ of system margin relative to the FEC limit is required for the signal degrade threshold (while maintaining the clear threshold at 1 dBQ relative to the signal degrade threshold).

The choice of system margin is subjective, as you might want to optimize your thresholds based on different link characteristics and fault tolerance and stability objectives. For guidance about configuring pre-FEC BER monitoring and BER thresholds, contact your Juniper Networks representative.

Table 10: Example—Signal Degrade and Clear Thresholds after Configuration
PIC	FEC Type	FEC Limit		Signal Degrade Threshold		Clear Threshold
PIC	FEC Type	Q²-Factor	BER	Q²-Factor	BER	Q²-Factor	BER
P1-PTX-2-100G-WDM	SD-FEC	6.7 dBQ	1.5E–2	9.7 dBQ	1.1E–3	10.7 dBQ	2.9E–4
P2-100GE-OTN	G.709 GFEC	11.5 dBQ	8.0E–5	14.5 dBQ	4.9E–8	15.5 dBQ	1.1E–9
P1-PTX-24-10G-W-SFPP	G.975.1 I.4 (UFEC)	9.1 dBQ	2.2E–3	12.1 dBQ	2.8E–5	13.1 dBQ	3.1E–6
	G.975.1 I.7 (EFEC)	9.6 dBQ	1.3E–3	12.6 dBQ	1.1E–5	13.6 dBQ	9.1E–7
	G.709 GFEC	11.5 dBQ	8.0E–5	14.5 dBQ	4.8E–8	15.5 dBQ	1.1E–9

Supported Forward Error Correction Modes

This section describes FEC modes supported on different routers at the [edit interfaces interface-name otn-options] level.

MX Series Routers

Table 11: FEC modes Supported on MX Series Routers
Line Card	FEC Mode	Port Speed
MPC5E-40G10G	`(gfec \| efec \| none \| ufec)`	10G
MPC5E-100G10G	`(gfec \| efec \| none \| ufec)`	10G and 100G (GFEC only)
MIC6-10G-OTN	`(gfec \| efec \| none \| ufec)`	10G
MIC6-100G-CFP2	`(gfec \| none )`	100G (GFEC only)
MIC3-100G-DWDM	`gfec \| hgfec \| sdfec`	100G

PTX Series Routers

Table 12: FEC Modes Supported on PTX Series Routers
Line Card	FEC Mode	Port Speed
P1-PTX-24-10G-W-SFPP	(gfec \| efec \| none \| ufec)	10G
P2-10G-40G-QSFPP	(gfec \| efec \| none \| ufec)	10G
P2-100GE-OTN	(gfec \| none)	100G (GFEC only)
P1-PTX-2-100G-WDM	(gfec-sdfec)	100G
PTX-5-100G-WDM	(gfec \| sdfec)	100G

Table 13: ACX Series Routers
Device	FEC Mode	Modulation Format	Port Speed
, ACX5448-D	sdfec	QPSK	100G
, ACX5448-D	sdfec15	QPSK	100G
ACX5448-D	hgfec	QPSK	100G
, ACX5448-D	sdfec15	8-QAM	200G
, ACX5448-D	sdfec15	16-QAM	200G

ODU Path Delay Measurement for Performance Monitoring

Read this topic to understand ODU path delay measurement and performance monitoring.

Overview
Enabling ODU Path Delay Measurement
Disabling ODU Path Delay Measurement

Overview

Performance monitoring is an important requirement in any network, including the optical networks. The key parameters that impact performance are bit error rate (BER) and delay. Delays in data communication over a network impact the network latency. Network latency is the time taken for a packet of data to travel from a designated point to another designated point. If there are less delays, the network latency is low. You can measure latency by sending a packet and then receiving it as it is returned to you; the time taken for the round-trip indicates the latency.

The optical channel data unit (ODU) path delay measurement offers in-service delay measurement. Delay (or latency) is measured by transmitting a known pattern (delay measurement pattern) in a selected bit of the delay measurement (DM) field and measuring the number of frames that are missed when the delay measurement pattern is received at the transmitting end. For instance, if the transmitted delay measurement bit is 1 1 1 1 1 1 1 1 1 0 0 and the received delay measurement bit is 1 1 1 0 0 0 0 0 0 0 0, the delay measurement starts at frame 2 and ends at frame 8. This can be detected by the change in value between the transmitted bit and the received bit.

The result of the delay measurement is 6 frames (8 - 2).

Guidelines to Configure Delay Measurement

Follow these guidelines to ensure that you obtain accurate delay measurement when you configure in-service delay measurement:

Unidirectional delay measurement is not supported. The in-service delay measurement is specific to round-trip delay measurement and for optical channel data units only.
Delay measurement on different framers for the MIC and PIC is different. So, the delay measurement values are different.
Resiliency is not supported for path delay measurement.
Links at the local and remote interfaces must be active before you configure delay measurement.
Do not perform delay measurement tests when ODU maintenance signals are injected.
Do not configure local loopback and network loopback with remote loopback because the loopback data is overwritten by the delay measurement pattern.
If a link failure occurs after you begin measuring delay, delay measurement fails. You must enable the delay measurement again on the local interface to measure delay.

Enabling ODU Path Delay Measurement

Delay measurement is disabled by default. This topic explains the broad steps for measuring the optical channel data units (ODU) path delay on optical transport networks (OTN). First, enable remote loopback on the remote interface and commit the configuration. This enables the remote interface to loop back the delay measurement pattern to the local interface. Then, start delay measurement at the local interface and view the results.

Note:

Do not enable remote loopback on both ends (local and remote). If you enable remote loopback on both interfaces, the delay measurement pattern is looped back continuously between the two interfaces.

Before you start measuring delay in the ODU path on OTN, complete the following tasks:

Ensure that the links are active at the local and remote interfaces and alarms are not configured.
Ensure that there is a delay of 10 seconds before enabling remote loopback. Also, ensure that there is a delay of 10 seconds after enabling remote loopback at the remote interface and before you start measuring delay.
Ensure that the delay measurement tests are not performed when ODU maintenance signals are injected.
Ensure that the local loopback and network loopback are also not specified because the looped-back data is overwritten by the delay measurement pattern.

Note:

If link failure occurs after you begin measuring delay, delay measurement fails. You must re-enable measurement of delay on the local interface to measure delay.

To enable ODU path delay measurement, perform the following steps:

Enable remote loopback on the remote interface by including the remote-loop-enable statement at the [edit] hierarchy level.
After enabling remote loopback, commit the configuration.
Start delay measurement on the local interface by including the start-measurement statement at the [edit] hierarchy level.
After enabling measurement of delay on the local interface, commit the configuration.

To view the delay measurement values, from the operational mode, enter the show interfaces extensive command.

Disabling ODU Path Delay Measurement

Delay measurement is disabled by default. If you enabled optical channel data unit (ODU) path delay measurement by using the remote-loop-enable and start-measurement statements, you can use this procedure to disable delay measurement.

Note:

You can also use the delete or deactivate command to disable remote loopback on the remote interface. For instance, you can use the delete interfaces interfacename otn-options odu-delay-management remote-loop-enable or deactivate interface interfacename otn-options odu-delay-management remote-loop-enable command to disable remote loopback on the remote interface.

To disable ODU path delay measurement, first disable remote loopback of the delay measurement pattern on the remote interface and then stop delay measurement:

Stop delay measurement on the local interface by including the stop-measurement statement at the [edit] hierarchy level.
After you stop delay measurement on the local interface, commit the configuration.
Disable remote loopback on the remote interface by including the no-remote-loop-enable statement at the [edit] hierarchy level.
After disabling remote loopback on the remote interface, commit the configuration.

To verify that remote loopback is disabled and delay is not measured, enter the show interfaces extensive command, from the operational mode.

Interface Mapping and Modulation format for PTX10K-LC1104 Line Card

The PTX10K-LC1104 line card supports 3 optical modules and 2 ports per optical modules. 2 ot interfaces are created for an optical module. Hence, 6 ot interfaces are created for a line card. The optical interface to et interface mapping is shown in the following table:

“ot-“ interface	Modulation Format	Mapped “et” interface(s)
ot-0/0/0	QPSK	et-x/0/0
	8QAM	et-x/0/0 et-x/0/1
	16QAM	et-x/0/0 et-x/0/1
ot-0/0/1	QPSK	et-x/0/2
	8QAM	et-x/0/1 et-x/0/2
	16QAM	et-x/0/2 et-x/0/3
ot-0/0/2	QPSK	et-x/0/4
	8QAM	et-x/0/4 et-x/0/5
	16QAM	et-x/0/4 et-x/0/5
ot-0/0/3	QPSK	et-x/0/6
	8QAM	et-x/0/5 et-x/0/6
	16QAM	et-x/0/6 et-x/0/7
ot-0/0/4	QPSK	et-x/0/8
	8QAM	et-x/0/8 et-x/0/9
	16QAM	et-x/0/8 et-x/0/9
ot-0/0/5	QPSK	et-x/0/10
	8QAM	et-x/0/9 et-x/0/10
	16QAM	et-x/0/10 et-x/0/11

ON THIS PAGE

Overview

Benefits

Supported Features

Supported PICs

Configure Optics

Supported OTN and Optics Options

Supported OTN Options on ACX6360 and ACX5448 Routers

Supported OTN Options on MX Series Routers

Supported OTN Options on PTX Series Routers

Supported Optics Options on ACX6360 and ACX5448-D Routers

Supported Optics Options on PTX10008 and PTX10016 Series Routers

Forward Error Correction and Bit Error Rate

Overview

Signal Degrade and Clear Threshold Values for PICs

Supported Forward Error Correction Modes

ODU Path Delay Measurement for Performance Monitoring

Overview

Guidelines to Configure Delay Measurement

Enabling ODU Path Delay Measurement

Disabling ODU Path Delay Measurement

Interface Mapping and Modulation format for PTX10K-LC1104 Line Card

Change History Table

ON THIS PAGE

100GbE, 40GbE, and 10GbE

Overview

Benefits

Supported Features

Supported PICs

Configure Optics

See Also

Supported OTN and Optics Options

Supported OTN Options on ACX6360 and ACX5448 Routers

See Also

Supported OTN Options on MX Series Routers

See Also

Supported OTN Options on PTX Series Routers

See Also

Supported Optics Options on ACX6360 and ACX5448-D Routers

See Also

Supported Optics Options on PTX10008 and PTX10016 Series Routers

See Also

Forward Error Correction and Bit Error Rate

Overview

Signal Degrade and Clear Threshold Values for PICs

Supported Forward Error Correction Modes

See Also

ODU Path Delay Measurement for Performance Monitoring

Overview

Guidelines to Configure Delay Measurement

Enabling ODU Path Delay Measurement

Disabling ODU Path Delay Measurement

See Also

See Also

See Also

See Also

Interface Mapping and Modulation format for PTX10K-LC1104 Line Card

See Also

Related Documentation

Change History Table