User manual JUNIPER NETWORKS JUNOSE 10.0.X PHYSICAL LAYER CONFIGURATION

[. . . ] JUNOSeTM Software for E-seriesTM Routing Platforms Physical Layer Configuration Guide Release 10. 0. x Juniper Networks, Inc. 1194 North Mathilda Avenue Sunnyvale, California 94089 USA 408-745-2000 www. juniper. net Part Number: 162-02027-00, Revision A00 Juniper Networks, the Juniper Networks logo, JUNOS, NetScreen, ScreenOS, and Steel-Belted Radius are registered trademarks of Juniper Networks, Inc. All other trademarks, service marks, registered trademarks, or registered service marks are the property of their respective owners. Juniper Networks assumes no responsibility for any inaccuracies in this document. Juniper Networks reserves the right to change, modify, transfer, or otherwise revise this publication without notice. [. . . ] In an ERX-310 router, line module slots are numbered 1­2 (slot 0 is reserved for the SRP module). port--Number of the port on the I/O module A cOC3/STM1 I/O module has four ports. On an I/O module that supports two ports, one port is active (primary) and the other is redundant. If the active port fails, the redundant port automatically becomes active. On I/O modules that support APS/MSP, the port numbers for the working (primary) interfaces are assigned the lower half of the numbered interfaces, whereas the port numbers for the protect (redundant) interfaces are assigned the upper half of the numbered interfaces. For example, on an I/O module that provides one primary port and one redundant port, the working interface is port 0 and the protect interface is port 1. APS/MSP channel number--Identifier of the working or protect interface for configuration purposes The protect interface is always assigned channel number 0. The working interface is always assigned channel number 1. For information about installing line modules and I/O modules in ERX routers, see ERX Hardware Guide, Chapter 4, Installing Modules. References For more information about MIB support for cOCx/STMx interfaces, consult the following resources: RFC 1661--The Point-to-Point Protocol (PPP) (July 1994) RFC 2495--Definitions of Managed Objects for the DS1, E1, DS2 and E2 Interface Types (January 1999) RFC 2496--Definitions of Managed Objects for the DS3/E3 Interface Types (January 1999) RFC 2558--Definitions of Managed Objects for the SONET/SDH Interface Type (March 1999) For more information about APS/MSP, consult the following resources: References 117 JUNOSe 10. 0. x Physical Layer Configuration Guide Telcordia document GR-253--Synchronous Optical Network (SONET) Transport Systems: Common Generic Criteria, Revision 3 (September 2000) ITU-T G. 783--Characteristics Of Synchronous Digital Hierarchy (SDH) Multiplexing Equipment Functional Blocks: Annex A ­ Multiplex Section Protection (MSP) Protocol, Commands And Operation (1990) Definitions of Managed Objects for SONET Linear APS Architectures--draft-ietf-atommib-sonetaps-mib-05. txt (November 2001 expiration) RFC 3498--Definitions of Managed Objects for Synchronous Optical Network (SONET) Linear Automatic Protection Switching (APS) Architectures (March 2003) For more information about bit error rate test (BERT) patterns, consult the following resources: ITU O. 151--Error performance measuring equipment operating at the primary rate and above (October 1992) ITU O. 153--Basic parameters for the measurement of error performance at bit rates below the primary rate (October 1992) T1M1. 3 Working Group--A Technical Report on Test Patterns for DS1 Circuits (November 1993) ANSI T1. 404-1994 Standard for Telecommunications--Network-to-Customer ­ DS3 Metallic Interface Specification (1994) For more information about MDL/FDL support on cOCx/STMx interfaces, consult the following resources: ANSI T1. 107a-1990 Standard for Telecommunications--Digital Hierarchy ­ Supplement to Formats Specification (August 1990) ANSI T1. 403-1989 Standard for Telecommunications--Network and Customer Installation Interfaces ­ DS1 Metallic Interface ­ Robbed-bit Signaling State Definitions (1989) AT&T Technical Reference 54016--Requirements for Interfacing Digital Terminal Equipment to Services Employing the Extended Superframe Format (September 1989) Before You Configure an Interface Before you configure a cOCx/STMx interface, verify the following: You have installed the line module and the I/O module correctly. Each configured line is able to transmit data to and receive data from your switch connections. For more information about installing modules, see ERX Hardware Guide, Chapter 4, Installing Modules. Make sure you also have the following information available: 118 Before You Configure an Interface Chapter 4: Configuring Channelized OCx/STMx Interfaces Framing type, clock source, and the cable length for each controller Framing type, line code, and clock source for each channel Timeslot mapping and line speed for each fractional channel HDLC channel information, such as data inversion information, CRC type, idle character, MTU, and MRU Configuration Tasks The following sections describe how to configure the layers on cOCx/STMx interfaces. SONET/SDH Configuration Tasks To configure SONET/SDH on a cOCx/STMx interface: 1. (Optional) Disable processing of SNMP link status information for the section and line layers of the interface. (Optional--not recommended) Overwrite the automatic setting for the path signal label (C2) byte. (Optional) Enable processing of SNMP link status information for the path layer of the interface. (Optional) Configure the router to use remote defect indications (RDIs) at the path layer to determine the operational status of a path. which the router sets an alarm when it records a defect at the path layer. 10. (MPLS fast reroute over SONET/SDH interfaces) Specify the time duration after 11. (MPLS fast reroute over SONET/SDH interfaces) Specify the time duration after which the router sets an alarm when it records a defect at the line or section layer. 12. Configure APS/MSP for the interface. For information about configuring APS/MSP, see "Configuring APS/MSP" on page 89 in "Configuring Unchannelized OCx/STMx Interfaces" on page 73. You must now configure the next layer on the interface: E1, T1, or E3. See "T1/E1 Configuration Tasks" on page 124 or "T3 Configuration Tasks" on page 130. clock source Use to configure the transmit clock source for the interface. For production networks, configure all STMx ports on the line module for internal chassis timing. You must also ensure that the chassis reference clock is of good Configuration Tasks 119 JUNOSe 10. 0. x Physical Layer Configuration Guide quality -- Stratum 3 or better, recovered either from a known good STM port or from one of the BITS inputs. Although the CLI enables you to specify the keywords internal module to use the line module's internal clock, in a production network we recommend that you do not do this. [. . . ] See tunnel-server. Monitoring Tunnel-Service Interfaces You can monitor tunnel-service interfaces by using the show tunnel-server command. NOTE: The E120 router and E320 router output for monitor and show commands is identical to output from other E-series routers, except that the E120 and E320 router output also includes information about the adapter identifier in the interface specifier (slot/adapter/port). show tunnel-server Use to display status and configuration information for dedicated and shared tunnel-server ports and tunnel-service interfaces configured on the router. You can display information for a specific tunnel-server port or for all tunnel-server ports. Use the optional config keyword to display information about available and provisioned tunnel-service interfaces on each port, and to indicate whether modules that support the use of dedicated or shared tunnel-server ports are currently installed in the router. Field descriptions Port:Appl--Identifier in slot/port or slot/adapter/port format for the module or tunneling application slot--Number of the slot in the chassis where the module resides adapter--Number of the bay in which the I/O adapter (IOA) resides. [. . . ]