14.12.2012 Views

Junos OS Interfaces Command Reference - Juniper Networks

Junos OS Interfaces Command Reference - Juniper Networks

Junos OS Interfaces Command Reference - Juniper Networks

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Table 128: Channelized STM1 show interfaces Output Fields (continued)<br />

Field Name<br />

SDH tu<br />

Received SDH<br />

overhead<br />

Transmitted SDH<br />

overhead<br />

Received path trace<br />

Transmitted path<br />

trace<br />

Packet Forwarding<br />

Engine<br />

configuration<br />

Field Description<br />

Active alarms and defects, plus counts of specific SDH tributary unit (TU) errors<br />

with detailed information.<br />

• Seconds—Number of seconds the defect has been active.<br />

• Count—Number of times that the defect has gone from inactive to active.<br />

• State—State of the error. State other than OK indicates a problem.<br />

Subfields are:<br />

Copyright © 2012, <strong>Juniper</strong> <strong>Networks</strong>, Inc.<br />

• TU-BIP-2—Bit interleaved parity for SONET line overhead<br />

• TU-FEBE—(near-end TU)<br />

• TU-LOP—Loss of pointer (near-end TU)<br />

• TU-AIS—Alarm indication signal (near-end TU)<br />

• TU-FERF—(near-end TU)<br />

• TU-UNEQ—Unequipped (near-end TU)<br />

• TU-PLM—Payload label mismatch (near-end TU)<br />

• TU-ES—Errored seconds (near-end TU)<br />

• TU-SES—Severely errored seconds (near-end TU)<br />

• TU-UAS—Unavailable seconds (near-end TU)<br />

• TU-ES-FE—Errored seconds (far-end TU)<br />

• TU-SES-FE—Severely errored seconds (far-end TU)<br />

• TU-UAS-FE—Unavailable seconds (far-end TU)<br />

Values of the received and transmitted SONET overhead:<br />

• C2—Signal label. Allocated to identify the construction and content of the<br />

STS-level SPE and for PDI-P.<br />

• F1—Section user channel byte. This byte is set aside for the purposes of users.<br />

• K1 and K2—These bytes are allocated for APS signaling for the protection of<br />

the multiplex section.<br />

• J0—Section trace. This byte is defined for STS-1 number 1 of an STS-N signal.<br />

Used to transmit a 1-byte fixed-length string or a 16-byte message so that a<br />

receiving terminal in a section can verify its continued connection to the<br />

intended transmitter.<br />

• S1—Synchronization status. The S1 byte is located in the first STS-1 of an<br />

STS-N signal.<br />

• Z3 and Z4—Allocated for future use.<br />

Channelized OC12 interfaces allow path trace bytes to be sent inband across<br />

the SONET/SDH link. The received path trace value is the message received<br />

from the router at the other end of the fiber. The transmitted path trace value<br />

is the message that this router transmits. This information is specific to each of<br />

the 12 channelized OC12 interfaces.<br />

Information about the configuration of the Packet Forwarding Engine:<br />

• Destination slot—FPC slot number.<br />

• PLP byte—Packet Level Protocol byte.<br />

Chapter 17: Channelized STM1 Interface Operational Mode <strong>Command</strong>s<br />

Level of Output<br />

extensive<br />

extensive<br />

extensive<br />

extensive<br />

737

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!