Juniper JUNOS 10.1 - CONFIGURATION GUIDE 1-2010 Configuration Manual page 972

JUNOS 10.1 Network Interfaces Configuration Guide
Table 85: SONET/SDH Framing Bytes for Specific Speeds (continued)
When you configure SONET/SDH header bytes, note the following:
Configuring an Incrementing STM ID
When configured in SDH framing mode, SONET/SDH interfaces on a Juniper Networks
router might not interoperate with some older versions of ADMs or regenerators that
require an incrementing STM ID.
Current SDH standards specify a set of 3*n overhead bytes in an STMn that includes
the J0 section trace byte. The rest are essentially unused (spare Z0) and contain
hexadecimal values (0x01, 0xCC, 0xCC ... 0xCC). The older version of the standard
specified that the same set of bytes should contain an incrementing sequence: 1, 2,
902
Configuring SONET/SDH Physical Interface Properties
Overhead
Bytes STM4
Concatenated 93FF
mode
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
slot-number pic pic-number]
Currently, the bytes e1-quiet
configuration.
The , ,
bytes f2 bytes z3 bytes z4
0 and work in the transmit direction only on channels 1, 2, and 3.
For DS3 channels on a channelized OC12 interface, the
and options have no effect.
z3, bytes z4
The bytes s1 option is supported only for channel 0; it is ignored if configured
on channels 1 through 11. The
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
STM16 STM64 OC12
93FF 93FF 93FF
no-concatenate statement at the
hierarchy level), the
bytes f1
statement is ignored if you include it in the
, and options work correctly on channel
path-trace
value configured on channel 0 applies
bytes s1
OC48 OC192
93FF 93FF
[edit chassis fpc
statement has no effect.
bytes f1, bytes f2, bytes