PyldMism
Table 1: Alarm Details
Parameter | Description |
|---|---|
Code | pyldMism |
Description | Payload Mismatch: The payload type in the received signal is not the expected payload type. |
Entities Affected | OTN ODU interfaces (see respective table below). |
Possible Cause | The cross-connect configuration at the far-end NE does not match the cross-connect configuration at the local NE. |
Default Severity | Critical |
Service Affecting | Yes (true). |
Alarm Clearing | |
Related 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, 200G line port | On |
odu2e:<chassis>/<slot>/<2>/<1>/<subport.och.tributary.sub-interface> | |||
odu4:<chassis>/<slot>/<1>/<1> | UFM4 | Fault LED, 100G line port | |
odu4:<chassis>/<slot>/<subslot>/<port> | 1x CFP BIC | Fault LED, 100G line 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, 10G port | |
odu2e:<chassis>/<slot>/<subslot>/<port> Note: Supported on UFM3 only. | |||
Clearing a PyldMism Alarm
 | Note: Follow all applicable safety requirements as described in the BTI7800 Series Hardware Overview and Installation Guide. |
- Retrieve interface data to compare the values of the Payload Type and Received Payload Type parameters.
show interface name:identifier - Retrieve cross-connect information for the local NE and
the far-end NE to determine at which end the cross-connect is incorrectly
provisioned.
show cross-connect - Delete the correct cross-connect, and reprovision it to resolve the mismatch. For information, see the BTI7800 Series Software Configuration Guide.
- Check for alarms on the local interface.
- If the alarm has cleared, you have completed this procedure.
- If the alarm does not clear, contact your next level of support.
