Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

OduMism

 

Table 1: Condition Details

Parameter

Description

Code

oduMism

Description/Cause

ODU Mismatch: The ODU type in the received ODU signal does not match the expected type.

Entities Affected

  • OTN ODU interfaces (see table)

Default Severity

Not alarmed

Service Affecting

No (false)

Condition Clearing

See Clearing an OduMism Alarm.

Related Fault Hierarchy

See OTN interface fault hierarchy.

Table 2: OTN ODU Interfaces

Entity Name

Fault Indicator

Module

Indicator

Status

odu4:<chassis>/<slot>/2/1/<subport.och.tributary>

UFM6

Fault LED, 200-Gbps port, 400G Coherent MSA XCVR

On

odu3:<chassis>/<slot>/2/1/<subport.och.tributary.sub-interface>

odu2:<chassis>/<slot>/2/1/<subport.och.tributary.sub-interface>

odu2e:<chassis>/<slot>/2/1/<subport.och.tributary.sub-interface>

odu4:<chassis>/<slot>/1/1

UFM4

Fault LED, 100-Gbps port, 100G Coherent MSA XCVR

odu4:<chassis>/<slot>/<subslot>/<port>

1x CFP BIC

Fault LED, 100-Gbps port

odu2:<chassis>/<slot>/<subslot>/<port.sub-interface>

odu2e:<chassis>/<slot>/<subslot>/<port.sub-interface>

Note: Supported on UFM3 only.

odu2:<chassis>/<slot>/<subslot>/<port>

12x SFP+ BIC

Fault LED, 10-Gbps port

odu2e:<chassis>/<slot>/<subslot>/<port>

Note: Supported on UFM3 only.

Clearing an OduMism Alarm

Note

Follow all applicable safety requirements as described in the BTI7800 Series Hardware Overview and Installation Guide.

  1. Ensure the ODU endpoints at both ends of the fiber are the same ODU type (that is, ensure both are ODU2 or both are ODU2e or both are ODU4). For information, see the BTI7800 Series Software Configuration Guide.
  2. Check for alarms on the local interface.
    • If the alarm clears, you have completed this procedure.

    • If the alarm does not clear, contact your next level of support.