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. in the United States and other countries. JUNOSe is a trademark of Juniper Networks, Inc. All other trademarks, service marks, registered trademarks, or registered service marks are the property of their respective owners. [. . . ] Port 0 accepts one pair of SC-style fiber connectors. 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. Specify a clock source for the interface. Specify that the mode be SDH, or accept the default mode, SONET. (Optional) Assign a text description or an alias to the interface. (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. [. . . ] This identifier applies only to dedicated and shared tunnel-server ports configured on the E120 and E320 routers. Dedicated tunnel-server ports are always adapter 0; shared tunnel-server ports are always adapter 2. port--Number of the tunnel-server port on the module; for dedicated tunnel-server ports, this is a virtual port number that is always 0; for shared tunnel-server ports, this is a virtual port number dynamically assigned by the router Card Type or Active Type--Type of port: dedicated or shared Oper State or Max State--Physical state of the port or application up--Port or application is available down--Port or application is unavailable 224 Monitoring Tunnel-Service Interfaces Chapter 6: Managing Tunnel-Service and IPSec-Service Interfaces present--Module associated with this port is installed not present--Module associated with this port has been removed pending--Router has not yet detected all previously configured modules during a reboot or initial installation of the module Active Interfaces or Interfaces--Number of tunnel-service interfaces currently configured on this port Max Interfaces--Total number of tunnel-service interfaces available on this module Fill--Percentage of available interfaces used by a server port, an application on a server port, an application on all server ports, and all server ports Appl Totals--Statistics for each application Server Ports--Displays configuration information about dedicated and shared tunnel-server ports on the router; this display format appears only when the config keyword is specified Port--Identifier in slot/port format (ERX-7xx models, ERX-14xx models, and ERX-310 routers) or slot/adapter/port format (E120 and E320 routers) for the module on which the tunnel-server port resides Type--Type of tunnel-server port: dedicated or shared MaximumInterfaces--Total number of tunnel-service interfaces available on this module Provisioned Interfaces--Total number of tunnel-service interfaces currently provisioned on this port HwPresent--Indicates whether a module that supports the specified tunnel-server port is currently installed in the router: yes or no Example 1--Displays information about a dedicated tunnel-server port on an SM host1#show tunnel-server Card Port:Appl Type --------------- --------Port 8/0 dedicated ipsec-tunnel ipsec-transport l2tp gre/dvmrp Appl Totals ipsec-tunnel ipsec-transport l2tp gre/dvmrp total Oper Active Max State Interfaces Interfaces Fill ------- ---------- ---------- ---present 1 8000 0. 0% down 0 0 0. 0% down 0 0 0. 0% up 0 8000 0. 0% up 1 4000 0. 0% 0 0 0 1 2 0 0 8000 4000 12000 0. 0% 0. 0% 0. 0% 0. 0% 0. 0% Monitoring Tunnel-Service Interfaces 225 JUNOSe 10. 0. x Physical Layer Configuration Guide Example 2--Displays information about a dedicated tunnel-server port on an ISM host1#show tunnel-server Card Oper Active Port:Appl Type --------------- --------Port 2/0 dedicated ipsec-tunnel ipsec-transport l2tp gre/dvmrp Appl Totals ipsec-tunnel ipsec-transport l2tp gre/dvmrp total Max State Interfaces Interfaces Fill ------- ---------- ---------- ---present 1 8000 0. 0% up 0 0 0. 0% down 0 0 0. 0% down 0 8000 0. 0% up 1 4000 0. 0% 0 0 0 2 2 0 0 16000 8000 16000 0. 0% 0. 0% 0. 0% 0. 0% 0. 0% Example 3--Displays information about a specific shared tunnel-server port host1#show tunnel-server 2/2 Card Port:Appl Type --------------- --------Port 2/2 shared ipsec-tunnel ipsec-transport l2tp gre/dvmrp Oper Active Max State Interfaces Interfaces Fill ------- ---------- ---------- ---present 0 4000 0. 0% down 0 0 0. 0% down 0 0 0. 0% up 0 4000 0. 0% up 0 4000 0. 0% Example 4--Displays configuration information about dedicated and shared tunnel-server ports host1#show tunnel-server config Server Ports -----------Port -------Port 2/2 Port 8/0 Type MaximumInterfaces ----------------------shared 8000 dedicated 16000 Provisioned Interfaces ----------4000 16000 HwPresent --------yes yes See show tunnel-server. 226 Monitoring Tunnel-Service Interfaces Part 2 Index Index on page 229 Index 227 JUNOSe 10. 0. x Physical Layer Configuration Guide 228 Index Index Symbols 10-Gigabit Ethernet interfaces modules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188 specifying an interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197 4xDS3 ATM I/O modules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 B baseline commands baseline interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201 baseline interface serial channelized T3 interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 cOCx/STMx interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153 E3/T3 interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 baseline line interface sonet. . . . . . . . . . . . . . . . . . . . . . . . . . 98, 153 baseline path interface sonet. . . . . . . . . . . . . . . . . . . . . . . . 98, 153 baseline section interface sonet. . . . . . . . . . . . . . . . . . . . 98, 153 BERT (bit error rate test) patterns channelized T3 interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9, 23 cOCx/STMx interfaces. . . . . . . . . . . . . . . . . . . . . . . . . 117, 145, 146 E3/T3 interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50, 61 bert command channelized T3 interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 E3/T3 interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 bit error rate test patterns. See BERT patterns A Address Resolution Protocol. See ARP all option (show controllers). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29, 64 aps commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 aps events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 aps force. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 aps group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 aps lockout. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 aps manual. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 aps protect. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 aps revert. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 aps unidirectional. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 aps working. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 See also show aps commands APS/MSP (Automatic Protect Switching/Multiplex Section Protection) automatic switchover. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 channel numbers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81, 116 communication methods. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 configuration example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 configuring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89, 119 events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 K1 byte. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 K2 byte. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 manual switchover. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73, 95 monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106, 171 overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109 protect interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73, 81, 89, 116 reversion after switchover. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 switching mechanisms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 working interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73, 81, 89, 116 ARP (Address Resolution Protocol). . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175 Automatic Protect Switching. [. . . ]