Juniper JUNOSE 11.2.X PHYSICAL LAYER Configuration Manual

For e series broadband services routers - physical layer configuration

page of 256

/ 256
Contents
Table of Contents
Bookmarks

Table of Contents

Quick Links

Download this manual

JunosE™ Software

for E Series™ Broadband

Services Routers

Physical Layer Configuration Guide

Release

11.2.x

Published: 2010-06-17

Table of Contents

Summary of Contents for Juniper JUNOSE 11.2.X PHYSICAL LAYER

Page 2 Products made or sold by Juniper Networks or components thereof might be covered by one or more of the following patents that are owned by or licensed to Juniper Networks: U.S. Patent Nos. 5,473,599, 5,905,725, 5,909,440, 6,192,051, 6,333,650, 6,359,479, 6,406,312, 6,429,706, 6,459,579, 6,493,347, 6,538,518, 6,538,899, 6,552,918, 6,567,902, 6,578,186, and 6,590,785.
Page 3 REGARDING LICENSE TERMS. 1. The Parties. The parties to this Agreement are (i) Juniper Networks, Inc. (if the Customer’s principal office is located in the Americas) or Juniper Networks (Cayman) Limited (if the Customer’s principal office is located outside the Americas) (such applicable entity being referred to herein as “Juniper”), and (ii) the person or organization that originally purchased from Juniper or an authorized Juniper reseller the applicable...
Page 4 Customer shall be liable for any such violations. The version of the Software supplied to Customer may contain encryption or other capabilities restricting Customer’s ability to export the Software without an export license. Copyright © 2010, Juniper Networks, Inc.
Page 5 (including Juniper modifications, as appropriate) available upon request for a period of up to three years from the date of distribution. Such request can be made in writing to Juniper Networks, Inc., 1194 N. Mathilda Ave., Sunnyvale, CA http://www.gnu.org/licenses/gpl.html...
Page 19: About The Documentation
Audience This guide is intended for experienced system and network specialists working with Juniper Networks E Series Broadband Services Routers in an Internet access environment. E Series and JunosE Text and Syntax Conventions Table 1 on page xx defines notice icons used in this documentation.
Page 20: Table 1: Notice Icons
Indicates that you must press two or more Press Ctrl + b. keys simultaneously. Syntax Conventions in the Command Reference Guide Plain text like this Represents keywords. terminal length Italic text like this Represents variables. mask, accessListName Copyright © 2010, Juniper Networks, Inc.
Page 21: Obtaining Documentation
CD-ROMs or DVD-ROMs, see the Portable Libraries page at http://www.juniper.net/techpubs/resources/index.html Copies of the Management Information Bases (MIBs) for a particular software release are available for download in the software image bundle from the Juniper Networks Web site at http://www.juniper.net/...
Page 22: Self-Help Online Tools And Resources
7 days a week, 365 days a year. Self-Help Online Tools and Resources For quick and easy problem resolution, Juniper Networks has designed an online self-service portal called the Customer Support Center (CSC) that provides you with the following features: Find CSC offerings: http://www.juniper.net/customers/support/...
Page 23: Chapters
Configuring T3 and E3 Interfaces on page 45 Configuring Unchannelized OCx/STMx Interfaces on page 71 Configuring Channelized OCx/STMx Interfaces on page 105 Configuring Ethernet Interfaces on page 167 Managing Tunnel-Service and IPSec-Service Interfaces on page 207 Copyright © 2010, Juniper Networks, Inc.
Page 25: Configuring Channelized T3 Interfaces
You can use MDL and FDL messages to determine the status of a link and to display statistics for the remote end of a connection. MDL and FDL messages do not interfere with other data transmitted over the link. Copyright © 2010, Juniper Networks, Inc.
Page 26: Mdl Standards
Table 3: MDL and FDL Message Strings and Message Types Message Path Idle Signal Test Signal String Description Message Message Message Equipment identification code Frame identification code generator Generator number – – Line identification code Facility identification code – – Copyright © 2010, Juniper Networks, Inc.
Page 27: Frequency Of Fdl Path Messages
See ERX Module Guide, Appendix A, Module Protocol Support for information about the higher-level protocols that channelized T3 interfaces support. Platform Considerations You can configure channelized T3 interfaces on the following Juniper Networks E Series Broadband Services Routers: ERX1440 router...
Page 28: Ct3/T3-F0 Line Modules And Ct3/T3 12 I/O Modules
JunosE 11.2.x Physical Layer Configuration Guide NOTE: The Juniper Networks E120 and E320 Broadband Services Routers do not support configuration of channelized T3 interfaces. For detailed information about the modules that support channelized T3 interfaces on ERX7xx models, ERX14xx models, and the ERX310 router: See ERX Module Guide, Table 1, Module Combinations for detailed module specifications.
Page 29: Configuring Channelized T3 Interfaces
1–28. Each T1 channel is an aggregate of 24 DS0 timeslots, as shown in Figure 2 on page 8. To configure an entire T1 line, assign 24 timeslots to each channel. Copyright © 2010, Juniper Networks, Inc.
Page 30: Fractional T1
0/1 Then assign the timeslots to channel 1, subchannel 1. host1(config-controll)#t1 1/1 timeslots 1-4,10,22-24 host1(config-controll)#t1 1/2 timeslots 5-6 host1(config-controll)#t1 1/3 timeslots 7-9 host1(config-controll)#t1 1/4 timeslots 11 host1(config-controll)#t1 1/5 timeslots 12-15,20-21 host1(config-controll)#t1 1/6 timeslots 16-19 Copyright © 2010, Juniper Networks, Inc.
Page 31: Hdlc Channels
Each configured line module is able to transmit data to and receive data from your switch connections. For more information about installing line modules and I/O modules, see the ERX Hardware Guide. You should also have the following information available: Copyright © 2010, Juniper Networks, Inc.
Page 32: Configuration Tasks
I/O module Example host1(config)#controller t3 0/1 There is no no version. See controller t3. shutdown Use to disable a T3 controller. The T3 interface is disabled by default. Copyright © 2010, Juniper Networks, Inc.
Page 33: Configuring Mdl Messages
Use to specify an MDL message. Example host1(config-controll)#mdl string port 0800 Use the no version to restore the default value to the specified MDL message or to all MDL messages. See mdl string. Copyright © 2010, Juniper Networks, Inc.
Page 34: Other Optional Tasks
Use to configure the transmit clock source for a T3 controller. Configure one end of the line as internal and the other end as line. Specify the keyword line to use a transmit clock recovered from the line’s receive data stream. Copyright © 2010, Juniper Networks, Inc.
Page 35 Use to enable SNMP link status processing on a T3 controller. Example host1(config-controll)#snmp trap link-status Use the no version to disable SNMP link status processing. See snmp trap ip link-status. Copyright © 2010, Juniper Networks, Inc.
Page 36: Configuring T1 Channels
I/O module Example host1(config)#controller t3 0/1 There is no no version. See controller t3. t1 clock source Use to configure the transmit clock source for T1 channels. The router supports internal and line clocking. Copyright © 2010, Juniper Networks, Inc.
Page 37 The framing format you choose must be compatible with the framing format at the other end of the line. Example host1(config-controll)#t1 2 framing sf Use the no version to restore the default value, esf. See t1 framing. t1 shutdown Copyright © 2010, Juniper Networks, Inc.
Page 38 You can specify a line speed that applies to all DS0 timeslots assigned to a subchannel. The default line speed is 64 Kbps. Use the no version to delete the fractional T1 circuit. See t1 timeslots. Copyright © 2010, Juniper Networks, Inc.
Page 39: Configuring Fdl Messages
Specify the keyword all to support both the ANSI and AT&T standards Specify the keyword none to remove the current FDL mode settings You can configure a different standard on each T1 channel. Example host1(config-controll)#t1 14-20,24 fdl att Copyright © 2010, Juniper Networks, Inc.
Page 40 Specify the keyword path-id to transmit path identifications every second. Specify the keyword idle-signal to send idle signals every second. Specify the keyword test-signal to transmit test signals every second. Example host1(config-controll)#t1 28 fdl transmit path-id Copyright © 2010, Juniper Networks, Inc.
Page 41: Configuring An Hdlc Channel
Specify the HDLC idle character. Enable data inversion on the interface. Set the time interval for monitoring bit and packet rates. Set the MRU. Set the MTU. Assign a text description or an alias to the serial interface. Copyright © 2010, Juniper Networks, Inc.
Page 42 I/O module channel—T1 channel subchannel—Subchannel in the range 1–24 Example host1(config)#interface serial 0/1:1/5 Use the no version to disable the interface. See interface serial. invert data Copyright © 2010, Juniper Networks, Inc.
Page 43 You should coordinate this value with the network administrator on the other end of the line. If you configure a different MTU value in higher-level protocols, such as IP, the router uses the lower value. This can produce unexpected behavior in your network. Example host1(config-if)#mtu 1600 Copyright © 2010, Juniper Networks, Inc.
Page 44: Configuration Example
For a list of the modules that support bit error rate tests (BERTs) and remote loopback, see ERX Module Guide, Appendix A, Module Protocol Support. NOTE: BERTs are supported on frame-based channelized T3 interfaces, with the exception of the CT3/T3 line module used with the 3-port CT3/T3 I/O module. Copyright © 2010, Juniper Networks, Inc.
Page 45: Testing At The T3 Layer
0s—Repetitive test pattern of all zeros, 00000... 1s—Repetitive test pattern of all ones, 11111... 2^9—Pseudorandom test pattern, 511 bits in length 2^11—Pseudorandom test pattern, 2047 bits in length 2^15—Pseudorandom test pattern, 32,767 bits in length Copyright © 2010, Juniper Networks, Inc.
Page 47: Testing At The T1 Layer
Use to enable bit error rate tests using the specified pattern on a T1 interface. Unlike other configuration commands, bert is not stored in NVRAM. Specify one of the following test patterns: Copyright © 2010, Juniper Networks, Inc.
Page 48 { line | payload }—Specify the line keyword to loop the data back toward the network before the T1 framer and automatically set a local loopback at the HDLC controllers. Specify the payload keyword to loop the payload data back toward the Copyright © 2010, Juniper Networks, Inc.
Page 49: Monitoring Interfaces
Monitoring Interfaces From User Exec mode, use the following show commands to monitor and display the T3 interface, T1 interface, and HDLC serial data channel information: Monitor channelized T3 interfaces on a slot and port. Copyright © 2010, Juniper Networks, Inc.
Page 50: Setting A Baseline
You can use the output filtering feature of the show command to include or exclude lines of output based on a text string you specify. See Command Line Interface in JunosE System Basics Configuration Guide, for details. Copyright © 2010, Juniper Networks, Inc.
Page 51 Rcv RAI Failure—Remote device is sending a far end alarm failure Xmt RAI Failure—Local device is sending a far end alarm failure Rcv AIS—Remote device is sending an alarm indication signal (AIS) Xmt AIS—Local device is sending an AIS Copyright © 2010, Juniper Networks, Inc.
Page 52 Frame Identification Code—fic string for MDL Unit Identification Code—unit string for MDL Facility Identification Code—pfi string for MDL Port Code—port string for MDL Generator Number—generator string for MDL BERT test—Number of current test and total number of tests Copyright © 2010, Juniper Networks, Inc.
Page 53 T3 in the current interval Example 1—In this example, a T3 interface is specified. host1#show controllers t3 2/0 DS3 2/0 Description: toronto ct3 interface ifAdminStatus = ifAdminDown snmp trap link-status = enabled No alarms detected Copyright © 2010, Juniper Networks, Inc.
Page 54 C-bit severely errored seconds = 0 Example 2—In this example, the brief keyword is specified. host1#show controllers t3 brief Interfaces ifAdminStatus OperationalStatus 5/0(channelized) 5/1(channelized) 5/2(channelized) down 5/3(channelized) down down 5/4(channelized) down down 5/5(channelized) down down 5/6(channelized) down down Copyright © 2010, Juniper Networks, Inc.
Page 55 FDL Transmit Test-Signal—Status of test signal: active or not active Equipment Identification Code—eic string for FDL Line Identification Code—lic string for FDL Frame Identification Code—fic string for FDL Unit Identification Code—unit string for FDL Facility Identification Code—pfi string for FDL Copyright © 2010, Juniper Networks, Inc.
Page 56 Line code violations—Number of line code violations encountered by a T1 in the current interval Example 1—In this example, a T1 channel and the brief keyword are specified. host1#show controllers t1 2/0:1 brief DS3 2/0:1 Copyright © 2010, Juniper Networks, Inc.
Page 57 FDL is not configured FDL Transmit Path-Id is not active FDL Transmit Test-Signal is not active FDL Transmit Idle-Signal is not active Equipment Identification Code is the null string Line Identification Code is the null string Copyright © 2010, Juniper Networks, Inc.
Page 58 See show controllers t3. show controllers t3 ft1 Use to display information about the state of a fractional T1 subchannel. Field descriptions Description—Text description or alias if configured for the interface ifOperStatus—Physical status of the interface Copyright © 2010, Juniper Networks, Inc.
Page 59 Far End Equipment Identification Code—eic string sent by remote device for MDL Far End Line Identification Code—lic string sent by remote device for MDL Far End Frame Identification Code—fic string sent by remote device for MDL Copyright © 2010, Juniper Networks, Inc.
Page 60 C-bit coding violations Unavailable seconds Invalid seconds Ds3 Last Interval Counters C-bit errored seconds C-bit severely errored seconds = 0 C-bit coding violations Unavailable seconds Invalid seconds Ds3 24 Hour Total Counters C-bit errored seconds Copyright © 2010, Juniper Networks, Inc.
Page 61 Clock slip seconds—Number of clock slips encountered by a T1 in the current interval Path code violations—Number of coding violations encountered by a T1 in the current interval Line errored seconds—Number of line errored seconds encountered by a T1 in the current interval Copyright © 2010, Juniper Networks, Inc.
Page 62 Use to display the state of the serial interface. Field descriptions Description—Text description or alias if configured for the interface ifOperStatus—Physical status of the interface ifOperUp—Interface is functioning ifOperTesting—Interface is being tested Copyright © 2010, Juniper Networks, Inc.
Page 63 Ds0 time slot map = 0x1 Invert data disabled, Ds0 mode = Nx64 Found 2 Serial Interfaces See show controllers t3. show interfaces serial Use to display information about the serial interfaces you specify. Field descriptions Copyright © 2010, Juniper Networks, Inc.
Page 64 Errored packets received—Number of packets with errors received on the interface Packets sent—Number of packets sent on the interface Bytes sent—Number of bytes sent on the interface Errored packets sent—Number of packets with errors sent from the interface Example Copyright © 2010, Juniper Networks, Inc.
Page 65 Crc type checking - CRC16 Hdlc mru = 1600 Hdlc mtu = 1600 Hdlc interface speed = 768000 Invert data disabled Ds0 time slot map = 0xfff000 Ds0 mode = Nx64 Found 2 Serial Interfaces See show interfaces. Copyright © 2010, Juniper Networks, Inc.
Page 67: Chapter 2 Configuring T3 And E3 Interfaces
You can use MDL messages to determine the status of a link and to display statistics for the remote end of a connection. MDL messages do not interfere with other data transmitted over the link. Copyright © 2010, Juniper Networks, Inc.
Page 68: Mdl Standards
10-second timer for that message. However, if 10 seconds pass without the line module receiving a path identification, test signal, or idle signal message containing an eic string, the line module erases the local copy of the eic message string. Copyright © 2010, Juniper Networks, Inc.
Page 69: Higher-Level Protocols
I/O modules. There are twelve physical T3/E3 (DS3) ports per I/O module. Each port uses two SMB connectors: one for the transmit (TX) connection and one for the receive (RX) connection. COCX-F3 line modules and associated I/O modules support the following: Copyright © 2010, Juniper Networks, Inc.
Page 70: Configuring T3 And E3 Interfaces
I/O modules, ERX7xx models support up to five of these line modules and five corresponding I/O modules, and the ERX310 Broadband Services Router supports up to two of these line modules and two corresponding I/O modules. There are twelve physical Copyright © 2010, Juniper Networks, Inc.
Page 71: Interface Stack
In ERX14xx models, line module slots are numbered 0–5 and 8–13 (slots 6 and 7 are reserved for SRP modules). In the ERX310 router, the line module slots are numbered 0–2 (slot 0 is reserved for the SRP module). Copyright © 2010, Juniper Networks, Inc.
Page 72: References
I/O modules correctly. You need the following information for each T3 controller: Framing type Clock source Cable length You also need HDLC channel information, such as data inversion information, for interfaces that support HDLC. Copyright © 2010, Juniper Networks, Inc.
Page 73: Configuration Tasks
Use the no version to enable unchannelized T3 operation on an interface for a CT3/T3-F0 line module. See channelized. controller e3 Use to specify an E3 controller in slot/port format. slot—Number of the slot in which the line module resides in the chassis Copyright © 2010, Juniper Networks, Inc.
Page 74: Configuring Mdl Messages
(Optional) Configure the interface to operate in an MDL carrier environment. host1(config-controll)#mdl carrier Specify the MDL messages. host1(config-controll)#mdl string eic "ERX1410" host1(config-controll)#mdl string fic "FG786" host1(config-controll)#mdl string lic “ Bldg 10" host1(config-controll)#mdl string pfi "Site 25" host1(config-controll)#mdl string port 0800 Copyright © 2010, Juniper Networks, Inc.
Page 75: Optional Tasks
Use the no version to disable transmission of the specified MDL message or all MDL messages. See mdl transmit. Optional Tasks The following configuration tasks are optional for T3 and E3 interfaces: Specify the cable length (T3 only). Change the clock source. Change the framing format. Copyright © 2010, Juniper Networks, Inc.
Page 76 The description or alias can be a maximum of 80 characters. Use “show controllers t3” on page 64 or “show controllers e3” on page 64 to display the text description. Example host1(config-controll)#description westford t3 interface Copyright © 2010, Juniper Networks, Inc.
Page 77: Configuring Fractional T3
E3. Fractional T3 is a portion of a T3 transmission service and provides a set of lines with a speed that is greater than T1 (1.544 Mbps), but less than T3 (44.736 Mbps). Copyright © 2010, Juniper Networks, Inc.
Page 78 Use to enable cell scrambling on a T3 frame interface. If you issue this command, be sure to issue the dsu mode and dsu bandwidth commands. Otherwise, the interface might drop packets unexpectedly. Copyright © 2010, Juniper Networks, Inc.
Page 79: Configuring An Hdlc Channel
A 32-bit CRC should be used to protect longer streams at faster rates and, therefore, provide better ongoing error detection. Example host1(config-if)#crc 32 Use the no version to restore the default value, 16. See crc. idle-character Copyright © 2010, Juniper Networks, Inc.
Page 80 Use to set the time interval at which the router calculates bit and packet rate counters. Choose a multiple of 30 seconds, in the range 30–300 seconds. Example host1(config-if)#load-interval 90 Use the no version to restore the default value, 300 seconds. See load-interval. Copyright © 2010, Juniper Networks, Inc.
Page 81: Configuration Examples
Use the no version to remove the text description or alias. See serial description. Configuration Examples To configure a T3 interface, start at the Global Configuration mode, and issue the following commands: host1(config)#controller t3 0/1 Copyright © 2010, Juniper Networks, Inc.
Page 82: Testing Interfaces
The router can send BERT patterns from different layers in the interface stack on frame-based T3 interfaces. For a list of the modules that support bit error rate tests, see ERX Module Guide, Appendix A, Module Protocol Support. To send BERT patterns: Select a controller. Copyright © 2010, Juniper Networks, Inc.
Page 83: Enabling Local, Network, And Payload Loopback
To enable local, network, or payload loopback testing of a T3 or E3 line, use the clock source and loopback commands from Controller Configuration mode. Change the clock source to internal. host1(config-controll)#clock source internal module Specify a loopback. host1(config-controll)#loopback local Copyright © 2010, Juniper Networks, Inc.
Page 84: Enabling Remote Loopback
NOTE: Remote loopback is available only on frame-based T3 interfaces configured to use C-bit framing. Specify one of the following loopback options: customer—Enables the router to enter into loopback when it receives an appropriate signal from the remote interface Copyright © 2010, Juniper Networks, Inc.
Page 85: Monitoring Interfaces
3/2 Setting a Baseline You can set a statistics baseline for serial interfaces using the baseline interface serial command. Use the delta keyword with the show commands to display statistics with the baseline subtracted. Copyright © 2010, Juniper Networks, Inc.
Page 86: Displaying Counters And Time Intervals
Use to display the parameters and MIB statistics on an interface. Use the brief keyword to display the administrative and operational status of all configured T3 or E3 interfaces, or to display abbreviated information for the specified T3 or E3 interface. Copyright © 2010, Juniper Networks, Inc.
Page 87 Payload—Data loops toward the network after the framer has processed the data Line—Data loops toward the network before the data reaches the framer loopback state—State of loopback for the controller: enabled or disabled Copyright © 2010, Juniper Networks, Inc.
Page 88 Time elapse in current interval—Number of seconds that have passed in the 15-minute (900 second) interval Errored seconds—Number of errored seconds encountered by an E3 (not applicable for T3) in the current interval (this field is not present for T3 controllers) Copyright © 2010, Juniper Networks, Inc.
Page 89 Framing is C-BIT, Line Code is B3ZS, Clock Source is Line Cable Length is 0 ft Loopback Disabled DSU Mode is Larscom DSU Bandwidth is 4000 DSU Scrambler is off MDL Transmit Path is not active MDL Transmit Test-Signal is active Copyright © 2010, Juniper Networks, Inc.
Page 90 Example 2—In this example, the brief keyword is specified. host1#show controllers t3 brief Interfaces ifAdminStatus OperationalStatus 5/0(channelized) 5/1(channelized) 5/2(channelized) down 5/3(channelized) down down 5/4(channelized) down down 5/5(channelized) down down 5/6(channelized) down down 5/7(channelized) down down 5/8(channelized) down down 5/9(channelized) down down Copyright © 2010, Juniper Networks, Inc.
Page 91 C-bit severely errored seconds—Number of C-bit severely errored seconds encountered by a T3 in the current interval C-bit coding violations—Number of C-bit coding violations encountered by a T3 in the current interval Copyright © 2010, Juniper Networks, Inc.
Page 92 C-bit coding violations Unavailable seconds Invalid seconds Ds3 24 Hour Total Counters C-bit errored seconds C-bit severely errored seconds = 1 C-bit coding violations = 330 Unavailable seconds Invalid seconds See show controllers t3 remote. Copyright © 2010, Juniper Networks, Inc.
Page 93: Chapter 3 Configuring Unchannelized Ocx/Stmx Interfaces
For APS/MSP to work correctly, you must provide connections from a primary port and a corresponding redundant port to the remote device. The remote device must also support APS/MSP. Copyright © 2010, Juniper Networks, Inc.
Page 94: Automatic Switchover
Switching Mechanisms E Series Broadband Services Routers support both bidirectional and unidirectional APS switching modes. By default, the router uses bidirectional switching mode. Copyright © 2010, Juniper Networks, Inc.
Page 95: Reversion After Switchover
GR-253—Synchronous Optical Network (SONET) Transport Systems: Common Generic Criteria, Revision 3 (September 2000). See requirement objects R5-56 [179] and R5-58 [181] for information about bit ordering and meaning for the K1 byte; see R5-67 [190v2] for information about the K2 byte. Copyright © 2010, Juniper Networks, Inc.
Page 96: Table 7: Explanation Of K1 Byte
Bits 5–8 represent the channel number. Channel number of protect interface 0001–1110 Channel number of working interface Table 8: Explanation of K2 Byte Bit Value (12345678) Meaning Bits 1–4 represent the channel number. Channel number of protect interface Copyright © 2010, Juniper Networks, Inc.
Page 97: Configuring Unchannelized Ocx/Stmx Interfaces
This section describes the line modules and I/O modules that support SONET/SDH interfaces. For detailed information about the modules that support SONET/SDH interfaces on ERX14xx models, ERX7xx models, and the ERX310 router : See ERX Module Guide, Table 1, Module Combinations for detailed module specifications. Copyright © 2010, Juniper Networks, Inc.
Page 98: Ocx/Stmx/Ds3-Atm Line Modules
OC12/STM4 POS operation through one line interface. I/O modules that support single-mode (intermediate reach or long haul), or multimode operation through SC full duplex connectors are available. I/O modules that support APS/MSP are also available. Copyright © 2010, Juniper Networks, Inc.
Page 99: Oc48 Line Modules
OCx/STMx/DS3-ATM interfaces. (See Figure 5 on page 76.) For more information about configuring a Gigabit Ethernet interface on this I/O module, see “OC3-2 GE APS I/O Module” on page 174. Copyright © 2010, Juniper Networks, Inc.
Page 100: Es2 4G Line Module
The ES2 4G LM also pairs with the ES2-S1 OC12-2 STM4 ATM IOA to deliver unchannelized OC12/STM4 ATM operation through two line interfaces. You can install the ES2-S1 OC12-2 STM4 ATM IOA in both IOA bays. Copyright © 2010, Juniper Networks, Inc.
Page 101: Ocx/Stmx Pos Ioas
The number of the primary port, but not that of the redundant port, is used to identify the interface. The primary port is above the corresponding redundant port on the I/O modules. Copyright © 2010, Juniper Networks, Inc.
Page 102: E120 And E320 Routers
1 identifies the left IOA bay (E120 router) and the lower IOA bay (E320 router). port—Number of the port on the IOA. For information about installing line modules and IOAs in the E120 and E320 routers, see E120 and E320 Hardware Guide, Chapter 4, Installing Modules. Copyright © 2010, Juniper Networks, Inc.
Page 103: Interface Specifier
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) Copyright © 2010, Juniper Networks, Inc.
Page 104: Configuration Tasks
(MPLS fast reroute over SONET/SDH interfaces) Specify the time that the router waits to set an alarm when the router records a defect at the line or section layer. Shut down (disable) an interface. clock source Copyright © 2010, Juniper Networks, Inc.
Page 105 Use to assign a text description or an alias to an unchannelized SONET interface. You can use this command to help you identify the interface and keep track of interface connections. The description or alias can be a maximum of 64 characters. Copyright © 2010, Juniper Networks, Inc.
Page 106 Use the no version to restore the default setting, in which the value of the C2 byte is determined by the layers configured above the SONET/SDH interface. See path overhead c2. path shutdown Use to disable a path. Paths are enabled by default. Example host1(config-controll)#path shutdown Copyright © 2010, Juniper Networks, Inc.
Page 107 APS/MSP to have priority over MPLS. Do not specify a path identifier for unchannelized SONET/SDH interfaces. Example host1(config-controll)#path trigger delay msec 1000 Use the no version to restore the default setting, 2500 milliseconds. See path trigger delay. Copyright © 2010, Juniper Networks, Inc.
Page 108 Specify a value of at least 100 milliseconds if this interface uses APS/MSP and if you want APS/MSP to have priority over MPLS. Example host1(config-controll)#trigger delay msec 1000 Use the no version to restore the default setting, 2500 milliseconds. See trigger delay. Copyright © 2010, Juniper Networks, Inc.
Page 109: Configuring Aps/Msp
1, this is the only valid option. Examples host1(config-controll)#aps working host1(config-controll)#aps working 1 Use the no version to prevent the interface from acting as a working interface. See aps working. threshold Copyright © 2010, Juniper Networks, Inc.
Page 110: Configuring The Protect Interface
(Optional) Specify that switchover takes place in unidirectional mode. host1(config-controller)#aps unidirectional aps group Use to specify the group to which the working and protect interfaces will belong. Specify the name of the APS group. Example Copyright © 2010, Juniper Networks, Inc.
Page 111 Specify the number of minutes in the range 5–7, after which the router will switch to the working interface. You can issue this command only for the protect interface, not for the working interface. Example host1(config-controll)#aps revert 7 Copyright © 2010, Juniper Networks, Inc.
Page 112: Configuring Sonet/Sdh Alarms
10-n (10e-n) errors per second. For sd-ber, an integer in the range 5–9; the default value is 5 For sf-ber, an integer in the range 3–5; the default value is 3 Example host1(config-controll)#threshold sf-ber 4 Copyright © 2010, Juniper Networks, Inc.
Page 113: Configuration Example
APS protection signal byte failures switchover—Configure notification of APS switchovers Example host1(config)#aps events channel-mismatch Use the no version to disable the delivery of APS events from line modules to SNMP traps. See aps events. Copyright © 2010, Juniper Networks, Inc.
Page 114: Manual Switching To A Redundant Port
You must specify one of the following channel numbers: 0—Switches from the protect interface back to the working interface 1—Switches from the working interface to the protect interface Examples host1(config-controll)#aps manual 0 host1(config-controll)#aps manual 1 Copyright © 2010, Juniper Networks, Inc.
Page 115: Testing Interfaces
You must remove trace messages before you can change the port type from SONET to SDH or vice versa. Otherwise, you see the following error message: % Cannot set port mode (path trace message is set) path overhead j1 Copyright © 2010, Juniper Networks, Inc.
Page 116: Monitoring Sonet/Sdh Interfaces
Use the total [ delta ] keywords with the show controllers sonet line command to view the baseline statistics. Example 1—Sets a baseline for SONET line layer interfaces on ERX14xx models, ERX7xx models, or the ERX310 router Copyright © 2010, Juniper Networks, Inc.
Page 117 2/0 Example 2—Sets a baseline for SONET section layer interfaces on the E320 router host1#baseline section interface sonet 3/0/0 There is no no version. See baseline section interface sonet. show controllers sonet Copyright © 2010, Juniper Networks, Inc.
Page 118 Received SONET overhead—Section and line overhead bytes present in the receive side of the interface at any particular time Transmitted SONET overhead—Section and line overhead bytes present in the transmit side of the interface at any particular time Copyright © 2010, Juniper Networks, Inc.
Page 119 : 0x00, S1 : 0x00 Channel configuration: channel = 0, path = oc3, hierarchy = 1/0, current path defects: LowerLayerDefect ifAdminStatus: up snmp trap link-status: disabled alarms used for operational status calculation: LOP AIS Copyright © 2010, Juniper Networks, Inc.
Page 120 AIS—Number of alarm indication signals BERR-SF—Number of bit error rate signal failures BERR-SD—Number of bit error rate signal degrades LOS—Number of loss of signal alarms LOF—Number of loss of frame alarms LOP—Number of loss of pointers Copyright © 2010, Juniper Networks, Inc.
Page 121 = LowerLayerDefect Current Path Interval Counters Seconds Counts State Active Active UNEQ Active BIP-B3 (Code Violation) Last Path Interval Counters Seconds Counts UNEQ BIP-B3 (Code Violation) Total Path Counters Seconds Counts 27255 27255 27255 UNEQ Copyright © 2010, Juniper Networks, Inc.
Page 122 BIP-B2 (Code Violation) Last Line Interval Counters Seconds Counts BERR-SF BERR-SD BIP-B2 (Code Violation) Total Line Counters Seconds Counts 27227 27227 BERR-SF BERR-SD BIP-B2 (Code Violation) Current Far End Line Interval Counters Seconds Counts Copyright © 2010, Juniper Networks, Inc.
Page 123 Example 4—Shows all statistics for all sessions for the section layer on interface 2/0. host1#show controllers sonet 2/0 section total Number of valid intervals - 31 Time elapsed in current interval - 244 Total Section Counters Seconds Counts SEFS BIP-B1 (Code Violation) See show controllers sonet. Copyright © 2010, Juniper Networks, Inc.
Page 124: Monitoring Aps/Msp
4/0 working group group-4 channel 1 Selected Enabled sonet 4/1 protect group group-4 channel 0 ~Selected Unidirectional Nonrevertive sonet 2/0 working group group-2 channel 1 Selected Enabled sonet 2/1 protect group group-2 channel 0 ~Selected Unidirectional Copyright © 2010, Juniper Networks, Inc.
Page 125 Current Conditions—Current state of the interface for this channel lockedOut—Indicates that the router is configured to prevent the protect interface from taking over if the primary interface fails SD—Indicates that signal degradation is detected Copyright © 2010, Juniper Networks, Inc.
Page 126 (5/4) (aps-protect) Current Conditions: SF Counters SignalDegrades = 0 SignalFailures = 1 Aps channel 1 (5/0) (aps-working) Current Conditions: None Counters SignalDegrades = 0 SignalFailures = 0 Switchovers LastSwitchover = Not Applicable See show aps. Copyright © 2010, Juniper Networks, Inc.
Page 127: Configuring Channelized Ocx/Stmx Interfaces
73 in “Configuring Unchannelized OCx/STMx Interfaces” on page 71. MDL/FDL Support Interfaces on cOCx/STMx line modules support maintenance data link (MDL) messages at the T3 level and facilities data link (FDL) messages at the T1 level. For a list of the line Copyright © 2010, Juniper Networks, Inc.
Page 128: Mdl Standards
MDL/FDL message string and indicates, with a checkmark ( ), the types of messages in which it can be sent. Table 9: MDL and FDL Message Strings and Message Types Message Path Idle Signal Test Signal String Description Message Message Message Equipment identification code Copyright © 2010, Juniper Networks, Inc.
Page 129: Frequency Of Fdl Path Messages
See ERX Module Guide, Appendix A, Module Protocol Support for information about the higher-level protocols that cOCx/STMx interfaces support. Platform Considerations You can configure cOCx/STMx interfaces on the following E Series Broadband Services Routers: ERX1440 router ERX1410 router Copyright © 2010, Juniper Networks, Inc.
Page 130: Cocx/Stmx Fo Line Module
The cOCx/STMx line module and its corresponding I/O modules can support either E1 or T1 operation. These modules cannot support E1 and T1 operation simultaneously. Interface Stack Figure 8 on page 109 shows the stack for cOCx/STMx interfaces. Copyright © 2010, Juniper Networks, Inc.
Page 131: Sonet/Sdh Vt Controllers
T1 and E1 is 64 Kbps; 56 Kbps is also available. An unframed E1 line Unframed E1 lines have no timeslots reserved for framing. The router creates one channel for an unframed E1 line and assigns the number one to that channel. Copyright © 2010, Juniper Networks, Inc.
Page 132: Figure 9: Sonet Multiplexing
Tributaries in a Group Signal Standard VT1.5 TU-11 Not supported TU-12 Figure 9 on page 110 shows the structure for SONET, and Figure 10 on page 111 shows the structure for SDH. Figure 9: SONET Multiplexing Copyright © 2010, Juniper Networks, Inc.
Page 133: Figure 10: Sdh Multiplexing
An STS-1 or STM-1 line A number in the range 1–2147483648 pathPayload Number of the payload In SONET mode, pathPayload is always 1. In within the path SDH mode, pathPayload is the number of the TUG-3 group. Copyright © 2010, Juniper Networks, Inc.
Page 134: T3 Controllers
You must configure HDLC over the T3, unframed E1, or fractional T1/E1 line that you configure on an interface. As Figure 8 on page 109 shows, HDLC is at the top layer of the interface stack. Numbering Scheme A cOCx/STMx interface is identified by the slot/port format, where: Copyright © 2010, Juniper Networks, Inc.
Page 135: References
(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: Copyright © 2010, Juniper Networks, Inc.
Page 136: Before You Configure An Interface
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: Copyright © 2010, Juniper Networks, Inc.
Page 137: Configuration Tasks
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 quality Copyright © 2010, Juniper Networks, Inc.
Page 138 The description or alias can be a maximum of 64 characters. Use the show controllers sonet command to display the text description. Example host1(config-controll)#description boston-sonet-interface Use the no version to remove the text description or alias. See description. path Copyright © 2010, Juniper Networks, Inc.
Page 139 2 overhead c2 20 Use the no version to restore the default setting, in which the value of the C2 byte is determined by the layers configured above the SONET/SDH interface. See path overhead c2. Copyright © 2010, Juniper Networks, Inc.
Page 140 Specify a value of at least 100 milliseconds if this interface uses APS/MSP and if APS/MSP should have priority over MPLS. Example host1(config-controll)#path 2 trigger delay msec 1000 Use the no version to restore the default setting, 2500 milliseconds. See path trigger delay. Copyright © 2010, Juniper Networks, Inc.
Page 141: Configuring Higher Layers
Before you configure T1 or E1 on an interface, you must configure SONET or SDH. See “SONET/SDH Configuration Tasks” on page 115. To configure a T1 or an E1 over SONET or SDH on a cOCx/STMx interface: Configure a tributary for the path. Copyright © 2010, Juniper Networks, Inc.
Page 142: Configuring An Unframed E1 Line
You cannot configure a mixture of T1 and E1 lines on the same cOCx/STMx line module. When you issue this command, the router creates one channel for the unframed E1 line, and assigns the number one to that channel. Example host1(config-controller)#path 1 e1 1/7/4 host1(config-controller)#path 1 e1 1/7/4 unframed Copyright © 2010, Juniper Networks, Inc.
Page 143: Configuring T1 And E1 Lines
T1 and E1 channel groups are enabled by default. Example host1 (config-controll)#path 12 e1 1/4/1 channel-group 2 shutdown Use the no version to restart a disabled channel group. See path ds1|e1 channel-group shutdown. path ds1|e1 channel-group snmp trap link-status Copyright © 2010, Juniper Networks, Inc.
Page 144 However, all interfaces with internal clock sources must use either the router’s clock or the module’s clock. You cannot configure some interfaces on the I/O module to use the router’s clock and others to use the module’s clock. Copyright © 2010, Juniper Networks, Inc.
Page 145: Configuring T1 Interfaces To Send Fdl Messages
You can configure a T1 interface to send FDL messages. To configure FDL: Specify a SONET interface. host1(config)#controller sonet 8/0 Specify the standard for transmission of FDL messages on both ends of the T1 connection. host1(config-controll)#path 2 ds1 1/1/1 fdl ansi Copyright © 2010, Juniper Networks, Inc.
Page 146 2 ds1 1/1/1 fdl carrier Use the no version to restore the default situation, in which the T1 interface does not operate in the carrier environment. See path ds1 fdl carrier. path ds1 fdl string Copyright © 2010, Juniper Networks, Inc.
Page 147: Disabling Interfaces And Channel Groups
To disable interfaces and channel groups, use the following commands. path ds1|e1 shutdown Use to disable a T1 or an E1 interface. T1 and E1 interfaces are enabled by default. Example host1 (config-controll)#path 12 e1 1/4/1 shutdown Copyright © 2010, Juniper Networks, Inc.
Page 148: Configuring Higher Layers
(Optional) Assign a text description or an alias to the interface. (Optional) Configure the framing format. (Optional) Enable processing of SNMP link status information about an interface. (Optional) Configure MDL settings. (Optional) Configure T1 channels. path ds3 clock source Copyright © 2010, Juniper Networks, Inc.
Page 149 Use the no version to remove the text description or alias. See path ds3 description. path ds3 framing Use to configure the framing format for a T3 interface. Specify c-bit parity framing or m23 multiplexer framing. Copyright © 2010, Juniper Networks, Inc.
Page 150: Configuring T3 Interfaces To Send Mdl Messages
12 ds3 1 mdl string pfi "Site 1" host1(config-controll)#path 12 ds3 1 mdl string port 0800 host1(config-controll)#path 12 ds3 1 mdl string unit 080001 Enable transmissions of MDL messages. host1(config-controll)#path 12 ds3 1 mdl transmit path-id Copyright © 2010, Juniper Networks, Inc.
Page 151: Configuring T1 Channels On T3 Interfaces
You must coordinate this setting with the other end of the line to establish which end is the transmit (internal) clock and which is the receive (line) clock. (Optional) Assign a text description or an alias to the interface. (Optional) Configure the framing format. Copyright © 2010, Juniper Networks, Inc.
Page 152 Example host1(config-controll)#path 12 ds3 1 t1 28 clock source internal chassis Use the no version to restore the default value, line clocking. See path ds3 t1 clock source. path ds3 t1 description Copyright © 2010, Juniper Networks, Inc.
Page 153 Use to enable SNMP link status processing for T1 channels or a subchannel. The default disables SNMP link status processing. Examples host1(config-controll)#path 2 ds3 3 t1 28 snmp trap link-status host1(config-controll)#path 2 ds3 3 t1 28/5 snmp trap link-status Copyright © 2010, Juniper Networks, Inc.
Page 154: Configuring T1 Channels To Send Fdl Messages
Specify the keyword att to support the AT&T FDL standard (see “References” on page 113). Specify the keyword all to support both the ANSI and AT&T standards Specify the keyword none to remove the current FDL mode settings Copyright © 2010, Juniper Networks, Inc.
Page 156: Configuring Higher Layers
The CRC is an error-checking technique that uses a calculated numeric value to detect errors in transmitted data. A 32-bit CRC should be used to protect longer streams at faster rates and, therefore, provide better ongoing error detection. Example host1(config-if)#crc 32 Copyright © 2010, Juniper Networks, Inc.
Page 157 Use to enable data stream inversion for the interface. Enable data stream inversion only if it is turned on at the other end of the line. Example host1(config-if)#invert data Use the no version to disable the feature. See invert data. Copyright © 2010, Juniper Networks, Inc.
Page 158: Configuration Examples
Use the no version to remove the text description or alias. See serial description. Configuration Examples This section provides some configuration examples to illustrate how to use the CLI commands. Copyright © 2010, Juniper Networks, Inc.
Page 159: Example 1: Configuring Interfaces In Sonet Mode
10 ds3 1 unchannelized Configure a channelized T3 on SONET path channel 12. host1(config-controller)#path 12 ds3 1 channelized Configure a T1 channel on the channelized T3 on SONET path channel 12. host1(config-controller)#path 12 ds3 1 t1 4 Copyright © 2010, Juniper Networks, Inc.
Page 160: Example 2: Configuring Interfaces In Sdh Mode
Configure a fractional E1 line on tributary 2/7/1 of path 10. host1(config-controller)#path 10 e1 2/7/1 channel-group 1 timeslots 2-5 Configure an unframed E1 line on tributary 2/5/2 of path 10. host1(config-controller)#path 10 e1 2/5/2 unframed Copyright © 2010, Juniper Networks, Inc.
Page 161: Example 3: Configuring Frame Relay
Network loopback—The ability to loop the data toward the network before the data reaches the frame Remote loopback, which provides: The ability to request that remote devices enter into loopback The ability to be placed in loopback by remote devices Connectivity tests to remote devices Copyright © 2010, Juniper Networks, Inc.
Page 162: Sending Bert Patterns
0s—Repetitive test pattern of all zeros, 00000... 1s—Repetitive test pattern of all ones, 11111... 2^9—Pseudorandom test pattern, 511 bits in length 2^11—Pseudorandom test pattern, 2047 bits in length 2^15—Pseudorandom test pattern, 32,767 bits in length Copyright © 2010, Juniper Networks, Inc.
Page 163: Receiving Bert Patterns
To view these statistics, issue the show controllers sonet command. Enabling Local or Network Loopback You can enable loopback tests on the router at the following layers in the interface stack: Copyright © 2010, Juniper Networks, Inc.
Page 164 T1/E1 framer and automatically set a local loopback at the HDLC controllers. Example host1(config-controll)#path 12 ds1 1/3/4 loopback network line Use the no version to clear the local loopback configuration. See path ds1|e1 loopback. Copyright © 2010, Juniper Networks, Inc.
Page 165: Enabling Remote Loopback Testing
See path ds3 t1 loopback. Enabling Remote Loopback Testing You can configure the router to request that compatible devices connected at the following layers enter into a loopback: T1 over SONET/SDH VT layer T1 over T3 layer Copyright © 2010, Juniper Networks, Inc.
Page 166 See path ds1|e1 loopback. path ds1 remote-loopback Use to enable the router to accept remote loopback requests from a remote device connected at the T1 over SONET/SDH VT layer. Example host1(config-controll)#path 12 ds1 1/3/4 remote-loopback Copyright © 2010, Juniper Networks, Inc.
Page 167 NOTE: Remote loopback is available only on frame-based T3 interfaces configured to use C-bit framing. Example host1(config)#controller sonet 5/0 host1(config-controll)#path 12 ds3 1 loopback remote Use the no version to turn off the loopback. See path ds3 loopback. path ds3 t1 loopback remote Copyright © 2010, Juniper Networks, Inc.
Page 168: Testing Connectivity
A message that the router expects to receive on the specified interface from the SONET/SDH device at the other end of the line. When you define a message that the interface sends, you must monitor receipt of that message at the remote end. Copyright © 2010, Juniper Networks, Inc.
Page 169: Monitoring Interfaces
Display statistics for the section, line, path, and tributary layers. host1#show controllers sonet 2/1 section Display the configuration for channelized SONET and SDH interfaces. host1#show controllers sonet 2/0 configuration Display statistics for serial interfaces. host1#show interfaces serial 2/0:1/1/1/1/1 Copyright © 2010, Juniper Networks, Inc.
Page 170: Setting A Baseline
Use to set a statistics baseline for the SONET/SDH path layer. The router implements the baseline by reading and storing the MIB statistics at the time the baseline is set and then subtracting this baseline whenever baseline-relative statistics are retrieved. Copyright © 2010, Juniper Networks, Inc.
Page 172 Time since last status change—Time the controller has been up or down Alarms—Number of suspect bit patterns found in several consecutive frames snmp trap link-status—State of SNMP link status processing for the controller: enabled or disabled Copyright © 2010, Juniper Networks, Inc.
Page 173 LOS LOF AIS RDI defect trigger soaking delay: 2500 milliseconds Operational Status: up time since last status change: 00:03:30 Loopback State: none Mode: sonet Timing source: internal module Receive FIFO Overruns: 0, Reconfigurations: 0 Copyright © 2010, Juniper Networks, Inc.
Page 174 Example 3—This example displays the configuration for T3 1/1 on slot 2, port 1. host1#show controllers sonet 2/1:1/1 oc3 2/1 channelized (3 channels, oc1 minimum speed) ifAdminStatus: up description: link1 snmp trap link-status: enabled alarms used for operational status calculation: LOS LOF AIS RDI Copyright © 2010, Juniper Networks, Inc.
Page 175 Description—Text description or alias if configured for the interface BERT test—Number of current test and total number of tests Test interval—Length of the BERT test status—Sync (controller is synchronized with remote device) or NoSync (controller is not synchronized with remote device Copyright © 2010, Juniper Networks, Inc.
Page 176 Test Interval 1 minute(s), Running - Status is Sync 0 minute(s), 33 second(s) left in test interval Sync count Received bit count = 41472000 Error bit count Number of valid interval - 0 Time elapse in current interval - 0 Copyright © 2010, Juniper Networks, Inc.
Page 177 Description—Text description or alias if configured for the interface BERT test—Number of current test and total number of tests Test interval—Length of the BERT test status—Sync (controller is synchronized with remote device) or NoSync (controller is not synchronized with remote device Copyright © 2010, Juniper Networks, Inc.
Page 178 Current Interval Counters P-bit errored seconds P-bit severely errored seconds = 0 Severely errored frame seconds = 0 Unavailable seconds = 541 Line code violations P-bit coding violations Line errored seconds C-bit coding violations Copyright © 2010, Juniper Networks, Inc.
Page 179 Figure 8 on page 109 shows the layers in the interface. For definitions of the MIB statistics, see RFC 2558—Definitions of Managed Objects for the SONET/SDH Interface Type (March 1999). Specify an interface in slot/port format. Copyright © 2010, Juniper Networks, Inc.
Page 180 2/1 section Current Section Interval Counters Current status = No Defect Errored seconds Severly errored seconds Severely errored framing seconds = 0 Coding violations Last Section Interval Counters Errored seconds Severly errored seconds Copyright © 2010, Juniper Networks, Inc.
Page 181 Unavailable seconds = 190 Last Line Interval Counters Errored seconds Severly errored seconds Coding violations Unavailable seconds = 900 Current Far End Line Interval Counters Errored seconds Severly errored seconds Coding violations Unavailable seconds Copyright © 2010, Juniper Networks, Inc.
Page 182 Coding violations Unavailable seconds Current Far End Path Interval Counters Errored seconds Severly errored seconds Coding violations Unavailable seconds Far End Last Tributary Interval Counters Errored seconds Severly errored seconds Coding violations Unavailable seconds Copyright © 2010, Juniper Networks, Inc.
Page 183 Far End Frame Identification Code—fic string sent by remote device for MDL Far End Unit Identification Code—unit string sent by remote device for MDL Far End Facility Identification Code—pfi string sent by remote device for MDL Copyright © 2010, Juniper Networks, Inc.
Page 184 Far End Facility Identification Code—pfi string sent by remote device for FDL Far End Generator Number—generator string sent by remote device for FDL Far End Port Number—port string sent by remote device for FDL Copyright © 2010, Juniper Networks, Inc.
Page 185 C-bit errored seconds C-bit severely errored seconds = 0 C-bit coding violations Unavailable seconds Invalid seconds Ds3 24 Hour Total Counters C-bit errored seconds C-bit severely errored seconds = 1 C-bit coding violations = 330 Copyright © 2010, Juniper Networks, Inc.
Page 186 Far End Facility Identification Code is the null string Far End Port Number is the null string Far End Generator Number is the null string DS1 Current Interval Counters Errored seconds Severely errored second Severely errored frame seconds = 0 Copyright © 2010, Juniper Networks, Inc.
Page 187 Crc type checking—Size of the CRC Hdlc mru—Current size of the MRU Hdlc mtu—Current size of the MTU Hdlc interface speed—Current line speed of the interface Hdlc idle-character—Current idle character Invert data disabled—Status of the data inversion feature Copyright © 2010, Juniper Networks, Inc.
Page 188: Monitoring Aps/Msp
Errored packets received Packets sent Bytes send 1436 Errored packets sent See show interfaces. Monitoring APS/MSP For information about monitoring APS/MSP, see “Monitoring APS/MSP” on page 102 in “Configuring Unchannelized OCx/STMx Interfaces” on page 71. Copyright © 2010, Juniper Networks, Inc.
Page 189: Chapter 5 Configuring Ethernet Interfaces
Disabling Ethernet Interfaces on page 195 Monitoring Ethernet Interfaces on page 196 Ethernet Overview Ethernet modules support the following Ethernet interfaces: Fast Ethernet Gigabit Ethernet 10-Gigabit Ethernet This section describes features that are available with Ethernet interfaces. Copyright © 2010, Juniper Networks, Inc.
Page 190: Features
You can configure Ethernet interfaces on the following E Series Broadband Services Routers: E120 Broadband Services Router E320 Broadband Services Router ERX1440 router ERX1410 router ERX710 router ERX705 router ERX310 router This section describes the line modules and I/O modules that support Ethernet interfaces. Copyright © 2010, Juniper Networks, Inc.
Page 191: Numbering Scheme
0–5 and 11–16. For both routers, slots 6 and 7 are reserved for SRP modules; slots 8–10 are reserved for switch fabric modules (SFMs). adapter—Number of the bay in which the I/O adapter (IOA) resides. Copyright © 2010, Juniper Networks, Inc.
Page 192: Interface Specifier
Unlike all other Fast Ethernet and Gigabit Ethernet I/O modules, the FE-8 SFP I/O module does not support automatic negotiation of the line speed and duplex mode by the router. For more information, see “duplex” on page 192 and “speed” on page 195. Copyright © 2010, Juniper Networks, Inc.
Page 193: Configuring Ethernet Interfaces
You can install the GE-2 line module or the GE-HDE line module and its corresponding GE-2 SFP I/O module in slot 1 or slot 2 of an ERX310 router or in any slot of an ERX1440 router. Copyright © 2010, Juniper Networks, Inc.
Page 194: Ports On Ge-2 Sfp I/O Module
The GE-8 I/O module can use either fiber-optic or copper SFPs. The I/O module accepts up to eight pairs (Tx/Rx) of LC-style fiber-optic connectors that support different optical modes and cabling distances. Alternatively, the I/O module supports up to eight pairs of copper SFPs. Copyright © 2010, Juniper Networks, Inc.
Page 195: Bandwidth And Line Rate Considerations
500 Mbps per port Managing High-Density Ethernet The overall data rate for the GE-HDE line module is 2 Gbps; therefore, the I/O module becomes highly oversubscribed because of the wire rate of the line module. The data Copyright © 2010, Juniper Networks, Inc.
Page 196: Oc3-2 Ge Aps I/O Module
SFPs. The ES2-S1 GE-4 IOA does not support port redundancy. ES2-S1 GE-8 IOA The E120 and E320 routers support the ES2-S1 GE-8 IOA. Other E Series routers do not support the ES2-S1 GE-8 IOA. Copyright © 2010, Juniper Networks, Inc.
Page 197: Es2 4G Lm Combination
412.5 Mbps per 412.5 Mbps per 475 Mbps per port 475 Mbps per port port port Any four ports 825 Mbps per port 825 Mbps per 950 Mbps per port 950 Mbps per port port Copyright © 2010, Juniper Networks, Inc.
Page 198: Table 17: Average Data Rate For Two Es2-S1 Ge-8 Ioas Installed With An Es2
OC3/STM1 port has a maximum theoretical bandwidth of 155 Mbps. Therefore, the OC12/STM4 IOAs have a maximum theoretical bandwidth of 1.244 Gbps and the OC3/STM1 IOA has an maximum theoretical bandwidth of 1.244 Gbps. Copyright © 2010, Juniper Networks, Inc.
Page 199: Es2 10G Lm Combination
For more information about high-density Ethernet on E Series routers, see “High-Density Ethernet” on page 187. ES2 10G LM Combination When paired with the ES2 10G LM, you can only combine the ES2-S1 GE-8 IOA in a slot with another ES2-S1 GE-8 IOA. Copyright © 2010, Juniper Networks, Inc.
Page 200: Table 19: Average Data Rate For One Es2-S1 Ge-8 Ioa Installed With An Es2 10G Lm
100 Gbps, 120 Gbps, or 320 Gbps Configuration Average Data Rate per GE-8 IOA Port Combination (> 128 Byte Packets) All sixteen ports 625 Mbps per port Any five ports on each 1 Gbps per port Copyright © 2010, Juniper Networks, Inc.
Page 201: Es2 10G Adv Lm Combination
100 Gbps, 120 Gbps, or 320 Gbps Configuration Average Data Rate per GE-8 IOA Port Combination (> 128 Byte Packets) Any five ports 1 Gbps per port All eight ports 625 Mbps per port Copyright © 2010, Juniper Networks, Inc.
Page 202: Es2-S3 Ge-20 Ioa
ES2 10G LMs and ES2-S3 GE-20 IOAs. You must install a combination in either of the turbo slots (slot 2 or slot 4). The 100 Gbps allocates 10 Gbps of overall bandwidth to each of these slots. Copyright © 2010, Juniper Networks, Inc.
Page 203: Bandwidth And Line Rate Considerations
With a 320 Gbps fabric configuration, the E320 router can accommodate up to 12 combinations of ES2 ADV LMs and ES2-S3 GE-20 IOAs. You can install a combination in any of the line module slots, each of which is allocated 10 Gbps of overall bandwidth. Copyright © 2010, Juniper Networks, Inc.
Page 204: Bandwidth And Line Rate Considerations
E120 and E320 Hardware Guide. The ES2-S1 10GE IOA has one port, uses a range of 10-gigabit small form-factor pluggable transceivers (XFPs) to support different optical modes and cabling distances, and accepts one LC-style fiber-optic connector. Copyright © 2010, Juniper Networks, Inc.
Page 205: Managing High-Density Ethernet
With a 320 Gbps fabric configuration, the E320 router can accommodate up to 12 combinations of ES2 10G Uplink LMs and ES2-S2 10GE PR IOAs. You can install a combination in any of the line module slots, each of which is allocated 10 Gbps of overall bandwidth. Copyright © 2010, Juniper Networks, Inc.
Page 206: Es2 10G Lm Combination
ES2 10G LMs and ES2-S2 10GE PR IOAs. You must install a combination in either of the turbo slots (slot 2 or slot 4). The 100 Gbps allocates 10 Gbps of overall bandwidth to each of these slots. Copyright © 2010, Juniper Networks, Inc.
Page 207: Es2 10G Adv Lm Combination
With a 120 Gbps fabric configuration, the E120 router can accommodate up to 6 combinations of ES2 10G ADV LMs and ES2-S2 10GE PR IOAs. You can install a combination in any of the line module slots, each of which is allocated 10 Gbps of overall bandwidth. Copyright © 2010, Juniper Networks, Inc.
Page 208: Ethernet References
For more information about Ethernet implementations, consult the following resources: IEEE 802.1q (Virtual LANs) IEEE 802.1w (Rapid Reconfiguration of Spanning Tree) IEEE 802.3 (Fast Ethernet and Gigabit Ethernet) IEEE 802.3u (Fast Ethernet only) IEEE 802.3z (Gigabit Ethernet only) IEEE 802.3ae (10-Gigabit Ethernet only) Copyright © 2010, Juniper Networks, Inc.
Page 209: High-Density Ethernet
IPv4 and IPv6 Internet Group Management Protocol (IGMP) IPv4 packets with a type of service (ToS) precedence value set to Internetwork Control (C0) IPv6 packets with a traffic class precedence value set to Internetwork Control (C0) Copyright © 2010, Juniper Networks, Inc.
Page 210: Managing Port Redundancy On Gigabit Ethernet I/O Modules
Use to force a Gigabit Ethernet I/O module to switch operation from one port to the other. Select an interface on the Gigabit Ethernet I/O module before you issue this command. Example host1(config)#interface gigabitEthernet 5/0 host1(config-if)#link failover force Copyright © 2010, Juniper Networks, Inc.
Page 211: Configuration Tasks For Ethernet
VLANs or S-VLANs. VLANs and S-VLANs enable you to multiplex multiple IP interfaces and PPPoE interfaces over a single physical Ethernet port. If you are not configuring with VLANs or S-VLANs, proceed to “Configuring Ethernet Interfaces” on page 167. Copyright © 2010, Juniper Networks, Inc.
Page 212: Configuring The Physical Interface
The range is 1–5 seconds and the default interval is 1 second. Observe the following guidelines when you configure the debounce feature for Ethernet interfaces: Copyright © 2010, Juniper Networks, Inc.
Page 213 The setting of the debounce-interval command persists after you reboot the router. Example host1(config-if)#debounce—interval 4 Use the no version to restore the default value, 1 second. See debounce-interval. duplex Copyright © 2010, Juniper Networks, Inc.
Page 214 IOA on the E120 or E320 routers; the port on the SRP IOA is always identified by 0. Example 1—Selects a Fast Ethernet interface on ERX7xx models, ERX14xx models, or the ERX310 router host1(config)#interface fastEthernet 1/0 Copyright © 2010, Juniper Networks, Inc.
Page 215 Use the no version to remove IP from an interface. You must issue the no version from the highest level down; you cannot remove an interface or subinterface if the one above it still exists. See interface gigabitEthernet. interface tenGigabitEthernet Copyright © 2010, Juniper Networks, Inc.
Page 216 Use to set the time interval at which the router calculates bit and packet rate counters. This command does not work for the Fast Ethernet port on the SRP module. Specify a multiple of 30 seconds, in the range 30–300 seconds. The default value is 300 seconds. Example Copyright © 2010, Juniper Networks, Inc.
Page 217: Disabling Ethernet Interfaces
Use the no version to revert to the default, either automatically negotiate or 100 Mbps (FE-8 SFP I/O module only). See speed. Disabling Ethernet Interfaces Use the shutdown command to disable an Ethernet interface. shutdown Use to disable an Ethernet interface. Example Copyright © 2010, Juniper Networks, Inc.
Page 218: Monitoring Ethernet Interfaces
You can specify the following keywords: delta—Specifies that baselined statistics are to be shown brief—Displays the operational status of all configured interfaces Field descriptions FastEthernet interfaceSpecifier—Status of the hardware on this interface up—Hardware is operational Copyright © 2010, Juniper Networks, Inc.
Page 219 SFP (Empty)—SFPs that are empty SFP (Non-compliant Juniper Part)—SFPs that are installed in the FE-8 I/O module and do not have a Juniper Networks part number programmed MTU—Size of the MTU for this interface Operational—Size of the largest packet processed Administrative—Setting for MTU size that you specified...
Page 220 No Carrier—Number of packets sent when carrier sense was unavailable Collisions—Analysis of the collisions that occurred Single—Number of packets sent after one collision Multiple—Number of packets sent after multiple collisions Copyright © 2010, Juniper Networks, Inc.
Page 221 Errors 0, Discards 0, Mac Errors 0, Deferred 0, No Carrier 3 Collisions: Single 0, Multiple 0, Late 0, Excessive 0 ARP Statistics: In: ARP requests 0, ARP responses 0 Errors 0, Discards 0 Copyright © 2010, Juniper Networks, Inc.
Page 222 SFP—1000BASE-LH, 1000BASE-SX, 1000BASE-ZX; for SFPs that are empty, SFP (Empty) appears in this field; for SFPs that are installed in the OC3-2 GE APS I/O module and do not have a Juniper Networks part number programmed, SFP (GE Compliant) appears in this field XFP—10GBASE-SR (10 Gbps), 10GBASE-LR (10 Gbps), 10GBASE-ER (10 Gbps);...
Page 223 Primary link selected x times—Number of times that the I/O has used the primary port since the module was last rebooted Secondary link selected x times—Number of times that the I/O has used the secondary port since the module was last rebooted Copyright © 2010, Juniper Networks, Inc.
Page 224 Errors—Total number of errors in all transmitted packets; note that some packets might contain more than one error Discards—Total number of discarded outgoing packets Mac Errors—Number of outgoing packets discarded because of MAC sublayer failures Copyright © 2010, Juniper Networks, Inc.
Page 225 Reports statistics in bytes in cells and accounts for cell encapsulation and padding overhead. none—Shaping mode is not configured Operational qos-shaping-mode—Actual shaping mode for the interface: disabled frame Copyright © 2010, Juniper Networks, Inc.
Page 226 Out: ARP requests 0, ARP responses 0 Example—Displays the status of a 10 Gigabit Ethernet interface host1#show interfaces tenGigabitEthernet 4/0/0 TenGigabitEthernet4/0/0 is Up, Administrative status is Up Hardware is Marvell GT64260, address is 0090.1a42.14b5 Copyright © 2010, Juniper Networks, Inc.
Page 227 Keyword assigned to interface—Options: Strict or Loose Address—IP address of the entry Hardware Addr—Physical (MAC) address of the entry Example host1:boston#show ip mac-validate interface fastEthernet 11/0 FastEthernet11/0: Strict Address Hardware Addr 3.3.3.3 0090.1a30.3365 4.4.4.4 0090.1a30.3368 See show ip mac-validate interface. Copyright © 2010, Juniper Networks, Inc.
Page 229: Managing Tunnel-Service And Ipsec-Service Interfaces
Figure 13 on page 207 displays the interface stacking for tunnel-service interfaces on a tunnel-server module. Figure 13: Interface Stacking for Tunnel-Service Interfaces Copyright © 2010, Juniper Networks, Inc.
Page 230: Types Of Tunnel-Server Ports
L2TP Overview in JunosE Broadband Access Configuration Guide. Secure IP tunnels IPSec-service modules are associated with secure IP tunnels. You must configure and delete these interfaces statically; however, the router assigns tunnels to the interfaces Copyright © 2010, Juniper Networks, Inc.
Page 231: Tunnel-Service Interface Platform Considerations
E Series router that you have. ERX7xx Models, ERX14xx Models, and the ERX310 Router ERX7xx models, ERX14xx models, and the ERX310 router all support Service Modules (SMs) and IPSec Service Modules (ISMs). Copyright © 2010, Juniper Networks, Inc.
Page 232: E120 And E320 Routers
ES2 4G LM with OCx/STMx POS IOAs ES2 10G ADV LM with the ES2-S1 GE-8 IOA ES2 10G ADV LM with the ES2-S2 10GE PR IOA ES2 10G ADV LM with the ES2-S3 GE-20 IOA Copyright © 2010, Juniper Networks, Inc.
Page 233: Numbering Scheme
The configuration task examples in this chapter use the format for ERX7xx models, ERX14xx models, and the ERX310 router to specify a tunnel-server port. (The format is described in “Numbering Scheme” on page 211.) Copyright © 2010, Juniper Networks, Inc.
Page 234: Supported Applications For Dedicated And Shared Tunnel-Server Ports
Support. Redundancy and Interface Distribution of Tunnel-Service Interfaces The redundancy and distribution mechanisms supported for tunnel-service ports configured on ISMs differ from those supported for SMs, the ES2-S1 Service IOA, and shared tunnel-server ports. Copyright © 2010, Juniper Networks, Inc.
Page 235: Sms, Es2-S1 Service Ioa, And Shared Tunnel-Server Modules
Dynamic Tunnel-Service Interfaces The router dynamically creates and deletes dynamic tunnel-service interfaces as dictated by the operation of the relevant protocols. Currently, L2TP sessions are the only dynamic tunnel-service interfaces available. Copyright © 2010, Juniper Networks, Inc.
Page 236: Interface Allocation For Shared Tunnel-Server Modules
If the interface’s local IP address is greater than the remote IP address, the router attempts to reassign the interface to an available ISM. If the reassignment is successful, the router waits 3 minutes before initiating an IPSec negotiation. Copyright © 2010, Juniper Networks, Inc.
Page 237: Tunnel-Service Interface Considerations
For the ES2 10G ADV LMs shared tunnel-server ports, you can reserve a percentage of the total bandwidth available for forwarding using the reserve-bandwidth command. The reserve-bandwidth command is not supported for other line modules that support tunnel-server configuration. Copyright © 2010, Juniper Networks, Inc.
Page 238: Exchanging Tunnel-Server Modules
5000 16,000 5000 5000 8000 8000 8000 16,000 8000 8000 8000 all-available 8000 16,000 all-available 16,000 16,000 5000 5000 8000 5000 5000 16,000 16,000 16,000 8000 8000 8000 16,000 all-available 16,000 8000 all-available 8000 Copyright © 2010, Juniper Networks, Inc.
Page 239: Unprovisioned Tunnel-Service Interfaces
To provision the maximum number of interfaces on a tunnel-server port: From Global Configuration mode, specify the location of the dedicated tunnel-server port that you want to configure. On a dedicated tunnel-server port: host1(config)#tunnel-server 8/0/0 Copyright © 2010, Juniper Networks, Inc.
Page 240: Reserving Bandwidth On Shared Tunnel-Server Ports
5 Gbps for forwarding and 5 Gbps for tunnel processing. From Global Configuration mode, specify the location of the shared tunnel-server port that you want to configure. host1(config)#tunnel-server 2/2/0 host1(config-tunnel-server)# This command accesses Tunnel Server Configuration mode. Copyright © 2010, Juniper Networks, Inc.
Page 241: Verifying The Tunnel-Server Interface Configuration
To unprovision the tunnel-service interfaces on a tunnel-server port, use any of the following commands, all of which have the same effect: Issue the no max-interfaces command from Tunnel Server Configuration mode. host1(config-tunnel-server)#no max-interfaces Issue the max-interfaces 0 command from Tunnel Server Configuration mode. Copyright © 2010, Juniper Networks, Inc.
Page 242 You may not always obtain the exact percentage of bandwidth specified because of the overhead involved with identifying and assigning incoming traffic to the appropriate resources. You may actually obtain a value less than the configured value. Examples host1(config-tunnel-server)#reserve-bandwidth 80 host1(config-tunnel-server)#reserve-bandwidth 50 Copyright © 2010, Juniper Networks, Inc.
Page 243: Monitoring Tunnel-Service Interfaces
Use to display status and configuration information for dedicated and shared tunnel-server ports and tunnel-service interfaces configured on the router. Unconfigured tunnel-server ports are not displayed in the output. You can display information for a specific tunnel-server port or for all tunnel-server ports. Copyright © 2010, Juniper Networks, Inc.
Page 244 Port—Identifier in slot/port format (ERX7xx models, ERX14xx models, and ERX310 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 Copyright © 2010, Juniper Networks, Inc.
Page 245 Oper Active Port:Appl Type State Interfaces Interfaces Fill --------------- --------- ------- ---------- ---------- ---- Port 2/2 shared present 4000 0.0% ipsec-tunnel down 0 0.0% ipsec-transport down 0 0.0% l2tp 4000 0.0% gre/dvmrp 4000 0.0% Copyright © 2010, Juniper Networks, Inc.
Page 246 Server Ports ------------ Provisioned Port Type MaximumInterfaces Interfaces HwPresent Bandwidth-Reserved -------- ------- ----------------- ----------- --------- ----------------- Port 2/2/0 shared 8000 Port 8/0/0 dedicated 16000 8000 Port 12/0/0 shared 8000 See show tunnel-server. Copyright © 2010, Juniper Networks, Inc.
Page 249: Index
22 switching mechanisms..........71 configuring HDLC channel...........19 working interface........71, 79, 87, 112 equipment loopback command.......23 ARP (Address Resolution Protocol).......167 loopback command............23 Automatic Protect Switching. See APS/MSP monitoring parameters..........27 numbering scheme............7, 8 Copyright © 2010, Juniper Networks, Inc.
Page 250 T3 interfaces...........19 dynamic tunnel-server ports cOCx/STMx interfaces..........134 applications supported..........212 E3/T3 interfaces.............57 overview.................209 crc command unprovisioning..............217 channelized T3 interfaces...........19 dynamic tunnel-service interfaces cOCx/STMx interfaces..........134 monitoring...............221 E3/T3 interfaces.............57 overview.................208 CT3/T3 12 I/O modules............48 CT3/T3 12 line modules............6 Copyright © 2010, Juniper Networks, Inc.
Page 251 Ethernet high-density..............187 overview................187 IEEE 802.3ae............167, 182 packet classifier............187 line speed................195 supported modules........172, 174, 182 MAC address validation..........192 monitoring..............196 numbering scheme..........169, 211 idle character events channelized T3 interfaces...........19 APS/MSP................91 cOCx/STMx interfaces........121, 134 E3/T3 interfaces.............57 Copyright © 2010, Juniper Networks, Inc.
Page 252 ISMs (IPSec Service modules) E3/T3 interfaces.............57 monitoring...............221 IEEE 802.1w................186 redundancy and interface distribution....212 IEEE 802.3ae..............167, 182 IEEE 802.3u................186 Juniper Networks E320 Broadband Services Routers IEEE 802.3z................186 SONET/SDH interfaces..........75 intelligent dropping of packets........187 interface commands interface fastEthernet..........192 K1 byte, APS/MSP..............74 interface gigabitEthernet...........192 K2 byte, APS/MSP..............73...
Page 253 MSP....................71 path description.............82, 116 MSP (Multiplex Section Protection)......71, 105 path e1 unframed............120 MTU (maximum transmission unit) path overhead c2...........82, 116 channelized T3 interfaces..........20 path overhead j1.............93, 142 cOCx/STMx interfaces..........134 path snmp trap link-status........82, 116 Copyright © 2010, Juniper Networks, Inc.
Page 254 E3/T3 interfaces............58 path ds3 t1 remote-loopback........142 monitoring path ds3 t1 shutdown..........128 channelized T3 interfaces........36 path ds3 t1 snmp trap link-status......128 cOCx/STMx............165 path ds3 t1 timeslots...........128 Copyright © 2010, Juniper Networks, Inc.
Page 255 T1 subchannel............15, 128 t1 framing................15 T1/E1 channel..............125 t1 loopback................23 T1/E1 channel group.............121 t1 remote-loopback............23 T3 controller..............10 t1 shutdown...............15 SMs (Service modules) t1 snmp trap link-status..........16 monitoring...............221 t1 timeslots................16 redundancy and interface distribution....212 Copyright © 2010, Juniper Networks, Inc.
Page 256 E3/T3 interfaces.............54 OCx/STMx interfaces...........82, 115 transmit powers and cable length......11, 54 trigger delay command............86 tunnel-server ports dedicated................207 shared................208 tunnel-service interfaces configuring...............217 considerations...............215 E120 and E320 Broadband Services Routers...............209 monitoring...............221 overview.................208 redundancy and interface distribution....212 Copyright © 2010, Juniper Networks, Inc.

This manual is also suitable for:

Junose 11.2.x

Juniper JUNOSE 11.2.X PHYSICAL LAYER Configuration Manual

Chapter 1 Configuring Channelized T3 Interfaces

Chapter 2 Configuring T3 and E3 Interfaces

Chapter 3 Configuring Unchannelized Ocx/Stmx Interfaces

Chapter 4 Configuring Channelized Ocx/Stmx Interfaces

Chapter 5 Configuring Ethernet Interfaces

Chapter 6 Managing Tunnel-Service and Ipsec-Service Interfaces

Quick Links

Related Manuals for Juniper JUNOSE 11.2.X PHYSICAL LAYER

Summary of Contents for Juniper JUNOSE 11.2.X PHYSICAL LAYER

This manual is also suitable for:

Table of Contents