Locate Payload Label Mismatch Path Alarms
Purpose
Payload mismatch path (PLM-P) alarms are reported by PTEs because the SONET byte used to determine the PLM-P alarm is located in the path overhead (the C2 byte). PLM-P alarms occur when the C2 byte received does not match the C2 byte transmitted by the PTE; for example, when the received C2 value is
Oxcf, the transmitted C2 value must also beOxcf.
NOTE: When the received C2 byte has a value of
0x01, the PTE accepts this value (regardless of the PTE setting) since0x01is considered a wildcard value.
Action
To display SONET alarms and errors, use the following JUNOS CLI operational mode command:
user@host>show interfacesso-fpc/pic/portextensiveSample Output
user@router2> show interfaces so-1/1/1 extensive[...Output truncated...]SONET alarms : PLM-PSONET defects : PLM-P[...Output truncated...]SONET path:BIP-B3 0 0REI-P 0 0LOP-P 0 0 OKAIS-P 0 0 OKRDI-P 2 1 OKUNEQ-P 0 0 OKPLM-P 96 1 Defect ActiveES-P 0SES-P 0UAS-P 0ES-PFE 2SES-PFE 2UAS-PFE 0Received SONET overhead:F1 : 0x00, J0 : 0x00, K1 : 0x00, K2 : 0x00S1 : 0x00, C2 : 0x13, C2(cmp) : 0xcf, F2 : 0x00Z3 : 0x00, Z4 : 0x00, S1(cmp) : 0x00, V5 : 0x00V5(cmp) : 0x00Transmitted SONET overhead:F1 : 0x00, J0 : 0x01, K1 : 0x00, K2 : 0x00S1 : 0x00, C2 : 0xcf, F2 : 0x00, Z3 : 0x00Z4 : 0x00, V5 : 0x00What It Means
In the
SONET pathsection of the sample output, the PLM-P counter is incrementing and defective. In theReceived SONET overheadandTransmitted SONET overheadsections, the received C2 value is0x13and the transmitted C2 value is0xcf. The C2 byte mismatch has caused a PLM-P alarm.The C2 byte tells the PTE what kind of information is in the synchronous payload envelope (SPE). For example, when the SPE contains Asynchronous Transfer Mode (ATM) cells, the C2 byte has a value of
0x13. If a Packet over SONET (POS) card is used on the Juniper Networks router, the link does not come up and a PLM-P alarm is raised (since the Juniper Networks router sends0xcfand receives0x13). However, if the C2 byte has a value of0x01, the PTE accepts this value (regardless of what the PTE is set to) since0x01is considered a wildcard value.The SONET specifications have assigned a small handful of values (of the 256 possible binary values), but Juniper Networks routers only use a few of these (
OxcforOx16for POS,Ox13for ATM, and so on). Table 32 shows the synchronous transport signal (STS) path signal label assignments as described in Issue 3 (Sept. 2000) of the GR-253 CORE.
On POS interfaces, Juniper Networks routers by default accept a C2 value of either
0xcfor0x16. Any other values raise a PLM-P alarm. An important thing to remember is that the C2 byte value of0x16is a standardized value (per RFC 2615, G.707, and GR-253) used for POS interfaces.0xcfis used by default since much SONET equipment still uses this value. If you need to change this byte, use therfc-2615option as follows:user@host#set interface so-fpc/pic/portsonet-options rfc-2615This option changes the following values:
C2 byte 22 (0x16)FCS 32payload-scrambling (this was already the default)