Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

SONET/SDH Header Byte Values Overview

 

Header bytes are regenerated in every router in the network path. They help us to identify error conditions.

You can configure the following SONET/SDH header bytes:

  • c2—Path signal label SONET/SDH overhead byte. SONET/SDH frames use the C2 byte to indicate the contents of the payload inside the frame. SONET/SDH interfaces use the C2 byte to indicate whether the payload is scrambled. For the c2 byte, value can be from 0 through 255. The default value is 0xCF.

  • e1-quiet—Default idle byte sent on the orderwire SONET/SDH overhead bytes. The router does not support the orderwire channel, and hence sends this byte continuously.

  • f1, f2, z3, z4—SONET/SDH overhead bytes. For these bytes, value can be from 0 through 255. The default value is 0x00.

  • s1—Synchronization message SONET/SDH overhead byte. This byte is normally controlled as a side effect of the system reference clock configuration and the state of the external clock coming from an interface if the system reference clocks have been configured to use an external reference. For the s1 byte, value can be from 0 through 255.

Table 1 displays Junos OS framing bytes for several specific speeds.

Table 1: SONET/SDH Framing Bytes for Specific Speeds

Overhead Bytes

STM4

STM16

STM64

OC12

OC48

OC192

A1

F6

F6

F6

F6

F6

F6

A2

28

28

28

28

28

28

C1

1..12

1..48

1..192

H1/H2

6A0A

6A0A

6A0A

620A

620A

620A

Z0

01/CC

01/CC

01/CC

Concatenated mode

93FF

93FF

93FF

93FF

93FF

93FF

When you configure SONET/SDH header bytes, note the following:

  • The C2 byte is the path signal label. If the C2 byte value on an interface does not match the C2 byte value on the remote interface, the path label mismatch (PLM-P) or unequipped (UNEQ-P) alarm might occur.

  • When you configure SONET/SDH OC48 interfaces for channelized (multiplexed) mode (by including the no-concatenate statement at the [edit chassis fpc slot-number pic pic-number] hierarchy level), the bytes f1 statement has no effect.

  • Currently, the bytes e1-quiet statement is ignored if you include it in the configuration.

  • The bytes f2, bytes z3, bytes z4, and path-trace options work correctly on channel 0 and work in the transmit direction only on channels 1, 2, and 3.

  • For DS3 channels on a channelized OC12 interface, the bytes f1, bytes f2, bytes z3, and bytes z4 options have no effect.

  • The bytes s1 option is supported only for channel 0; it is ignored if configured on channels 1 through 11. The bytes s1 value configured on channel 0 applies to all channels on the interface.

  • Embedded operations channel (EOC) D1, D2, and D3 bytes are not supported.

  • For channelized OC12 IQE and channelized OC48 IQE PICs with SFPs:

    • Only C2 (Path signal label) and S1 byte setting is supported.

    • Following header bytes are not supported. The router will syslog an INFO message if a command for an unsupported header byte is received.

      F1—Section user channel byte

      F2—Path user channel byte

      Z3, Z4—SONET/SDH overhead bytes

      E1—quiet default idle byte

    • The following header bytes are supported on the SONET/SDH OC3/STM1 (Multi-Rate) MICs with SFP.

      Z0, F1—Section user channel bytes

      K1, K2, S1— Line user channel bytes

      G1, F2, Z3, Z4, C2, E1—Path user channel bytes

    • The following header bytes are supported on the Channelized SONET/SDH OC3/STM1 (Multi-Rate) MIC with SFP.

      Z0, F1—Section user channel bytes

      S1— Line user channel bytes

      G1, F2, Z3, Z4, C2, E1—Path user channel bytes

    • The following header bytes are supported on the OC192/STM64 MIC with XFP.

      F1—Section user channel bytes

      K1, K2, S1— Line user channel bytes

      G1, F2, Z3, Z4, C2, E1—Path user channel bytes