Alcatel-Lucent 1830 PSS-16 - Page 499

Service affecting? No
Applicability 11DPE12, 11DPE12E, 11QPA4, 11STAR1, 11STMM10,
43STA1P, 43STX4, 43STX4P, 4DPA4
Corrective Action
This procedure details the corrective action for clearing a PLM condition on an OT port.
...................................................................................................................................................................................................
1
Identify the far-end peer of the local OT port where the PLM condition exists.
...................................................................................................................................................................................................
2
Check the service configuration document to determine which signal type and/or mapping
mode is expected to be configured on the ODUkP segment that has PLM condition.
...................................................................................................................................................................................................
3
Modify signal type and/or mapping mode to match the service configuration document
(and match on both ends of the segment).
...................................................................................................................................................................................................
4
If the source of one end of the ODUkP segment is in another operator’s network (this
would be the case if there is an OTM-0.2 hand off between 1830 PSS network domain
and client OTN network) contact the operator and resolve the mismatch in setting.
PLMEGR
PLMEGR (Egress Payload Mismatch Indication - ODU)
The OT port has detected a Payload Type Mismatch condition at ODUk Path layer. This
defect indicates that the service and/or mapping types on two ends of the ODUkP link
don’t match. The Payload Type indicator is encoded in the Payload Structure Identifier
field of ODUkP. When expected and received PT values don’t match, a PLM condition is
declared. This condition is typically declared on both ends of the ODUkP path. This may
be caused due to inconsistent provisioning of service/mapping types on the two ends of
the ODUkP segment.
Severity CR
Trouble-clearing procedures
PLM
PLM (Payload Mismatch Indication - ODU)
....................................................................................................................................................................................................................................
....................................................................................................................................................................................................................................
1830 PSS-36/PSS–32/PSS-16/PSS-4
8DG60888CAAA Release 3.6.0 and 3.6.1
Issue 1 June 2011
2-249
E ND OF STEPS
...................................................................................................................................................................................................