Page 1 JUNOSe Software for E-series Routing Platforms Physical Layer Configuration Guide Release 10.0.x Juniper Networks, Inc. 1194 North Mathilda Avenue Sunnyvale, California 94089 408-745-2000 www.juniper.net Part Number: 162-02027-00, Revision A00...
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 AND (B) YOU MAY CONTACT JUNIPER NETWORKS 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 license(s) for use of the Software (“Customer”)
Page 4 (“GPL”) or the GNU Library General Public License (“LGPL”)), Juniper will make such source code portions (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 http://www.gnu.org/licenses/gpl.html...
Page 5 agreements relating to the Software, whether oral or written (including any inconsistent terms contained in a purchase order), except that the terms of a separate written agreement executed by an authorized Juniper representative and Customer shall govern to the extent such terms are inconsistent or conflict with terms contained herein.
Page 7 Abbreviated Table of Contents About the Documentation Part 1 Chapters 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 Part 2...
Page 8 JUNOSe 10.0.x Physical Layer Configuration Guide viii...
Page 9: Table Of Contents
Table of Contents About the Documentation E-series and JUNOSe Documentation and Release Notes ......xix Audience ......................xix E-series and JUNOSe Text and Syntax Conventions ........xix Related E-series and JUNOSe Documentation ..........xxi Obtaining Documentation ................xxiv Documentation Feedback ................xxv Requesting Technical Support ..............xxv Part 1 Chapters Chapter 1...
Page 10 JUNOSe 10.0.x Physical Layer Configuration Guide Configuration Tasks ..................10 Configuring a T3 Controller ..............10 Configuring MDL Messages ..............11 Other Optional Tasks ................12 Configuring T1 Channels .................14 Optional Tasks .................14 Configuring FDL Messages ...............17 Configuring an HDLC Channel ..............20 Optional Tasks .................20 Configuration Example ..................23 Testing Interfaces ..................23 Testing at the T3 Layer ................23...
Page 11 Table of Contents Chapter 3 Configuring Unchannelized OCx/STMx Interfaces Overview .......................73 APS and MSP ..................73 Automatic Switchover ..............74 Manual Switchover ................74 Switching Mechanisms ..............74 Reversion After Switchover ..............75 Communication Methods ..............75 Higher-Level Protocols ................77 Platform Considerations ................77 OCx/STMx/DS3-ATM Line Modules ............78 OCx/STMx POS Line Modules ..............78 OC48 Line Modules .................79 OC3/STM1 GE/FE Line Module ..............79...
Page 12 JUNOSe 10.0.x Physical Layer Configuration Guide Timeout of Received MDL and FDL Messages ........110 Frequency of FDL Path Messages ...........111 Higher-Level Protocols ................111 Platform Considerations ................111 cOCx/STMx FO Line Module ..............112 Interface Stack ..................112 SONET/SDH VT Controllers ............113 T3 Controllers .................116 HDLC ....................116 Numbering Scheme ................116 References ....................117...
Page 13 Table of Contents Chapter 5 Configuring Ethernet Interfaces Ethernet Overview ..................175 Features ....................176 Ethernet Interface Platform Considerations ..........176 Numbering Scheme ................177 ERX-7xx Models, ERX-14xx Models, and the ERX-310 Router ..177 E120 Router and E320 Router ............177 Interface Specifier .................178 Fast Ethernet I/O Modules ................178 FE-8 I/O Module ..................178 FE-8 SFP I/O Module ................179 Gigabit Ethernet I/O Modules and IOAs ............179...
Page 14 JUNOSe 10.0.x Physical Layer Configuration Guide Chapter 6 Managing Tunnel-Service and IPSec-Service Interfaces Tunnel-Service and IPSec-Service Overview ..........211 Types of Tunnel-Server Ports ..............212 Dedicated Tunnel-Server Ports ............212 Shared Tunnel-Server Ports ............212 Types of Tunnel-Service Interfaces ............212 Tunnel-Service Interface Platform Considerations ........213 Supported Modules for Dedicated Tunnel-Server Ports ......213 ERX-7xx Models, ERX-14xx Models, and the ERX-310 Router ..214 E120 Router and E320 Router ............214...
Page 15 List of Figures Figure 1: Stack for Channelized T3 Interface ...........7 Figure 2: T1 Channels and DS0 Timeslots on a T3 Line ........8 Figure 3: Stack for T3 ATM Interfaces ............49 Figure 4: Stack for T3 Frame and E3 Frame Interfaces ........49 Figure 5: Interface Stack for OCx/STMx/DS3-ATM Interfaces ......78 Figure 6: Interface Stack for OCx/STMx POS and OC48/STM16 Interfaces ....................79...
Page 16 JUNOSe 10.0.x Physical Layer Configuration Guide List of Figures...
Page 17: List Of Tables
Table 1: Notice Icons ..................xx Table 2: Text and Syntax Conventions ............xx Table 3: Juniper Networks E-series and JUNOSe Technical Publications ..xxi Table 4: MDL and FDL Message Strings and Message Types ......4 Table 5: Sample T1 Subchannel/Timeslot Assignments ........8 Table 6: MDL Message Strings and Message Types ........46...
Page 18 JUNOSe 10.0.x Physical Layer Configuration Guide xviii List of Tables...
Page 19: About The Documentation
If the information in the latest JUNOSe Release Notes differs from the information in the documentation, follow the JUNOSe Release Notes. To obtain the most current version of all Juniper Networks technical documentation, see the products documentation page on the Juniper Networks Web site at http://www.juniper.net/...
Page 20: Table 1: Notice Icons
JUNOSe 10.0.x Physical Layer Configuration Guide Table 1: Notice Icons Icon Meaning Description Informational note Indicates important features or instructions. Caution Indicates a situation that might result in loss of data or hardware damage. Warning Alerts you to the risk of personal injury or death. Laser warning Alerts you to the risk of personal injury from a laser.
Page 21: Table 3: Juniper Networks E-Series And Junose Technical Publications
{ permit | deny } { in | out } { clusterId | ipAddress } Related E-series and JUNOSe Documentation Table 3 on page xxi lists and describes the E-series and JUNOSe document set. Table 3: Juniper Networks E-series and JUNOSe Technical Publications Document Description E-series Hardware Documentation E120 and E320 Quick Start Guide Shipped in the box with all new E120 and E320 routers.
Page 22 JUNOSe 10.0.x Physical Layer Configuration Guide Table 3: Juniper Networks E-series and JUNOSe Technical Publications (continued) Document Description ERX Hardware Guide Provides the necessary procedures for getting ERX-14xx models, ERX-7xx models, and ERX-310 routers operational, including information about: Installing the chassis and modules...
Page 23 About the Documentation Table 3: Juniper Networks E-series and JUNOSe Technical Publications (continued) Document Description JUNOSe IP Services Configuration Guide Explains how to configure and monitor IP routing services. Topics include: Routing policies Firewalls Network Address Translation (NAT) J-Flow statistics...
Page 24 Release notes are included on the corresponding software CD and are available on the Web. Obtaining Documentation To obtain the most current version of all Juniper Networks technical documentation, see the products documentation page on the Juniper Networks Web site at http://www.juniper.net/...
Page 25 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 26 JUNOSe 10.0.x Physical Layer Configuration Guide To verify service entitlement by product serial number, use our Serial Number Entitlement (SNE) Tool located at https://tools.juniper.net/SerialNumberEntitlementSearch/ Opening a Case with JTAC You can open a case with JTAC on the Web or by telephone. Use the Case Management tool in the CSC at http://www.juniper.net/cm/ Call 1-888-314-JTAC (1-888-314-5822 toll-free in the USA, Canada, and Mexico).
Page 27: Chapters
Part 1 Chapters Configuring Channelized T3 Interfaces on page 3 Configuring T3 and E3 Interfaces on page 45 Configuring Unchannelized OCx/STMx Interfaces on page 73 Configuring Channelized OCx/STMx Interfaces on page 109 Configuring Ethernet Interfaces on page 175 Managing Tunnel-Service and IPSec-Service Interfaces on page 211 Chapters...
Page 28 JUNOSe 10.0.x Physical Layer Configuration Guide Chapters...
Page 29: Configuring Channelized T3 Interfaces
Chapter 1 Configuring Channelized T3 Interfaces Use the procedures described in this chapter to configure channelized T3 (CT3) interfaces on E-series routers. This chapter contains the following sections: Overview on page 3 Platform Considerations on page 5 References on page 9 Before You Configure an Interface on page 9 Configuration Tasks on page 10 Configuration Example on page 23...
Page 30: Mdl Standards
JUNOSe 10.0.x Physical Layer Configuration Guide MDL Standards You can configure channelized T3 interfaces to send MDL messages that comply with ANSI T1.107a-1990 Standard for Telecommunications Digital Hierarchy – Supplement to Formats Specification (August 1990). MDL messages identify a particular link by sharing common codes for data such as the equipment identifier, line identifier, frame identifier, and unit.
Page 31: Frequency Of Fdl Path Messages
Chapter 1: Configuring Channelized T3 Interfaces Table 4: MDL and FDL Message Strings and Message Types (continued) Message Path Idle Signal Test Signal String Description Message Message Message Line identification code Facility identification code – – port Equipment port number –...
Page 32: Ct3/T3-F0 Line Modules And Ct3/T3 12 I/O Modules
JUNOSe 10.0.x Physical Layer Configuration Guide ERX-705 router ERX-310 router NOTE: The E120 router and the E320 router do not support configuration of channelized T3 interfaces. For detailed information about the modules that support channelized T3 interfaces on ERX-7xx models, ERX-14xx models, and the ERX-310 router: See ERX Module Guide, Table 1, Module Combinations for detailed module specifications.
Page 33: Interface Stack
Chapter 1: Configuring Channelized T3 Interfaces Interface Stack Figure 1 on page 7 shows the stack for a channelized T3 interface. To configure a channelized T3 interface, configure a T3 controller, followed by a T1 channel, and then a fractional T1 channel. Finally, you must configure a High-Speed Data Link Control (HDLC) data channel on the interface.
Page 34: T1 Channels
JUNOSe 10.0.x Physical Layer Configuration Guide T1 Channels A T3 line consists of 28 T1 channels (or data streams). A T1 channel is identified by its number in the range 1–28. Each T1 channel is an aggregate of 24 DS0 timeslots, as shown in Figure 2 on page 8.
Page 35: Hdlc Channels
Chapter 1: Configuring Channelized T3 Interfaces 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 HDLC Channels To identify an HDLC channel or the complete channelized T3 interface, use the format slot/port:T1 channel/subchannel.
Page 36: Configuration Tasks
JUNOSe 10.0.x Physical Layer Configuration Guide You have installed the line module and the I/O module correctly. 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.
Page 37: Configuring Mdl Messages
Chapter 1: Configuring Channelized T3 Interfaces port Number of the port on the 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. Example host1(config-controll)#no shutdown Use the no version to restart a disabled interface.
Page 38: Other Optional Tasks
JUNOSe 10.0.x Physical Layer Configuration Guide Use to specify that an interface is used in the carrier environment. Example host1(config-controll)#mdl carrier Use the no version to restore the default situation, in which the interface does not operate in the carrier environment. See mdl carrier.
Page 39 Chapter 1: Configuring Channelized T3 Interfaces Use to adjust the transmit power appropriate to the length of the T3 cable. Specify a cable length in the range 1–450 feet. The router supports two transmit powers, one for a cable length 1–225 feet and another for a cable length 226–450 feet.
Page 40: Configuring T1 Channels
JUNOSe 10.0.x Physical Layer Configuration Guide Use to configure the framing format for a T3 controller. Specify either m23 or c-bit framing. Choose the framing format that is compatible with the framing format of the Telco network device at the other end of the line. Select c-bit framing if you intend to configure MDL messages.
Page 41 Chapter 1: Configuring Channelized T3 Interfaces Disable T1 channels. Change the clock source. Assign a text description or an alias to the interface. Change the framing format. Enable or disable SNMP link status processing. Configure FDL messages. controller t3 Use to specify a T3 controller in slot/port format. slot Number of the slot in which the line module resides in the chassis port Number of the port on the I/O module Example...
Page 42 JUNOSe 10.0.x Physical Layer Configuration Guide Use “show controllers t3” on page 30 to display the text description. Examples host1(config-controll)#t1 2 description london t1 interface host1(config-controll)#t1 2/1 description london first ft1 interface Use the no version to remove the text description or alias. See t1 description.
Page 43: Configuring Fdl Messages
Chapter 1: Configuring Channelized T3 Interfaces host1(config-controll)#t1 2 snmp trap link-status Use the no version to disable SNMP link status processing. See t1 snmp trap link-status. t1 timeslots Use to assign a range of DS0 timeslots to a subchannel as a single data stream. To configure a subchannel, specify a T1 channel in channel/subchannel format and a range of timeslots.
Page 44 JUNOSe 10.0.x Physical Layer Configuration Guide host1(config-controll)#t1 1 fdl string port 0800 host1(config-controll)#t1 1 fdl string generator "Test generator" Enable transmission of FDL messages. host1(config-controll)#t1 1 fdl transmit path-id (Optional) Specify that the router should generate yellow alarms for the T1 channels.
Page 45 Chapter 1: Configuring Channelized T3 Interfaces Use to specify an FDL message as defined in the ANSI T1.403 specification. NOTE: The router sends these FDL messages only if you have issued the t1 fdl command with the ansi or all keyword and then issued the t1 fdl transmit command. Example host1(config-controll)#t1 6 fdl string eic "ERX-1440"...
Page 46: Configuring An Hdlc Channel
JUNOSe 10.0.x Physical Layer Configuration Guide Use to generate a yellow alarm when a loss of frame or loss of signal condition is detected on T1 channels. By default, T1 channels generate alarms. Example host1(config-controll)#t1 6,10-14,19 yellow generate Use the no version to disable generation of yellow alarms. See t1 yellow.
Page 47 Chapter 1: Configuring Channelized T3 Interfaces Use the no version to restore the default value, 16. See crc. idle-character Use to configure the HDLC idle character. The idle character is sent between HDLC packets. Specify one of the following idle characters: flags—Sets the idle character to 0x7E marks Sets the idle character to 0xFF Example...
Page 48 JUNOSe 10.0.x Physical Layer Configuration Guide Use to set the time interval at which the router calculates bit and packet rate counters. You can 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.
Page 49: Configuration Example
Chapter 1: Configuring Channelized T3 Interfaces The description or alias can be a maximum of 80 characters. Use “show interfaces serial” on page 43 to display the text description. Example host1(config-if)#serial description ottawa012 hdlc channel Use the no version to remove the text description or alias. See serial description.
Page 50 JUNOSe 10.0.x Physical Layer Configuration Guide Configure one of the following tests: Set the loopback to local to test the line without connecting to the network. host1(config-controll)#loopback local Set the loopback to network to test the line connected to the network. host1(config-controll)#loopback network line (Optional) Configure one of the following tests for remote loopback: Set the loopback to remote to request that a remote device connected on a...
Page 51 Chapter 1: Configuring Channelized T3 Interfaces 2^23 Pseudorandom test pattern, 8,388,607 bits in length alt-0-1 Repetitive alternating test pattern of zeros and ones, 01010101... Specify the duration of the test in the range 1–1440 minutes. Example host1(config-controll)#bert pattern 2^15 interval 20 Use the no version to stop the test that is running.
Page 52: Testing At The T1 Layer
JUNOSe 10.0.x Physical Layer Configuration Guide payload Loops the data toward the network after the framer processes the data remote Sends a far end alarm code in the C-bit framing, as defined in ANSI T1.404, to notify the remote end to activate or (when you use the no version) deactivate the line loopback NOTE: Remote loopback is available only on channelized T3 interfaces configured to use C-bit framing.
Page 53 Chapter 1: Configuring Channelized T3 Interfaces Specify one of the following test patterns: NOTE: The CT3/T3-F0 line module supports only the 2^11, 2^15, and 2^20-O153 options. 0s Repetitive test pattern of all zeros, 00000... 1s Repetitive test pattern of all ones, 11111... 2^11 Pseudorandom test pattern, 2047 bits in length 2^15 Pseudorandom test pattern, 32,767 bits in length 2^20-O153 Pseudorandom test pattern, 1,048,575 bits in length...
Page 54 JUNOSe 10.0.x Physical Layer Configuration Guide payload data back toward the network at the T1 framer and automatically set a local loopback at the HDLC controllers. remote line fdl ansi Sends a repeating 16-bit ESF data link code word (00001110 11111111) to the remote end requesting that it enter into a network line loopback.
Page 55: Monitoring Interfaces
Chapter 1: Configuring Channelized T3 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. host1#show controllers t3 0/1 Monitor a T1 interface.
Page 56: Output Filtering
JUNOSe 10.0.x Physical Layer Configuration Guide T1 current interval counters Counters for the current interval T1 last interval counters Counters for the previous interval T1 24-hour total counters Cumulative counters for the last 24 hours or since the interface was started The last 24 hours of 15-minute reporting intervals (96 intervals) Output Filtering You can use the output filtering feature of the show command to include or exclude...
Page 57 Chapter 1: Configuring Channelized T3 Interfaces snmp trap link-status—Status of SNMP trapping (enabled or disabled) alarms detected One of the following T3 alarms: No alarm present No alarms present on the line 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...
Page 58 JUNOSe 10.0.x Physical Layer Configuration Guide 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 Test interval Length of the BERT test status Sync (controller is synchronized with remote device) or NoSync (controller is not synchronized with remote device) Sync count Number of times the pattern detector synchronized with...
Page 59 Chapter 1: Configuring Channelized T3 Interfaces host1#show controllers t3 2/0 DS3 2/0 Description: toronto ct3 interface ifAdminStatus = ifAdminDown snmp trap link-status = enabled No alarms detected Framing is C-BIT, Line Code is B3ZS, Clock Source is Line Cable Length is 0 ft Loopback Disabled MDL Transmit Path is not active MDL Transmit Test-Signal is active...
Page 60 JUNOSe 10.0.x Physical Layer Configuration Guide 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 5/10(channelized) down down 5/11(channelized) down down 3/0(channelized) down down...
Page 61 Chapter 1: Configuring Channelized T3 Interfaces 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 Port Code port string for FDL Generator Number generator string for FDL BERT test Number of current test and total number of tests...
Page 62 JUNOSe 10.0.x Physical Layer Configuration Guide Degraded minutes Number of minutes that a T1 line is degraded 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 ifOperStatus = ifOperUp...
Page 63 Chapter 1: Configuring Channelized T3 Interfaces DS1 1/0:1 Description: toronto t1 channel ifOperStatus = ifOperUp Yellow Alarm detection is active Yellow Alarm generation is active snmp trap link-status = disabled Framing is D4, Line Code is Ami, Clock Source is Internal - Module Allocated Ds0 time slot map = 0x0 Last Remote Loopback Request Sent - Deactivate FDL is not configured...
Page 64 JUNOSe 10.0.x Physical Layer Configuration Guide Degraded minutes = 0 Line code violations = 0 See show controllers t1. 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 ifOperUp Interface is functioning...
Page 65 Chapter 1: Configuring Channelized T3 Interfaces Field descriptions for a T3 interface Far End MDL Carrier bit Status of MDL configuration on remote device connected to T3 interface set MDL is configured for carrier mode not set MDL is not configured for carrier mode 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...
Page 66 JUNOSe 10.0.x Physical Layer Configuration Guide Number of valid interval - 3 Time elapse in current interval - 756 Ds3 Current Interval Counters C-bit errored seconds C-bit severely errored seconds = 0 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...
Page 67 Chapter 1: Configuring Channelized T3 Interfaces Severely errored seconds Number of severely errored seconds encountered by a T1 in the current interval Severely errored frame seconds Number of severely errored framing seconds encountered by a T1 in the current interval Unavailable seconds Number of unavailable seconds encountered by a T1 in the current interval Clock slip seconds Number of clock slips encountered by a T1 in the current...
Page 68 JUNOSe 10.0.x Physical Layer Configuration Guide Bursty errored seconds Degraded minutes See show controllers t3 remote. show controllers t3 serial 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...
Page 69 Chapter 1: Configuring Channelized T3 Interfaces Crc type checking - CRC16 Hdlc mru = 9996 Hdlc mtu = 9996 Hdlc interface speed = 64000 Ds0 time slot map = 0x1 Invert data disabled, Ds0 mode = Nx64 Found 2 Serial Interfaces See show controllers t3.
Page 70 JUNOSe 10.0.x Physical Layer Configuration Guide 5 minute output rate Data rates based on the traffic sent in the last five minutes Interface statistics Packets received Number of packets received on the interface Bytes received Number of bytes received on the interface Errored packets received Number of packets with errors received on the interface Packets sent Number of packets sent on the interface...
Page 71: Configuring T3 And E3 Interfaces
Chapter 2 Configuring T3 and E3 Interfaces Use the procedures described in this chapter to configure T3 and E3 interfaces on E-series routers. This chapter contains the following sections: Overview on page 45 Platform Considerations on page 47 References on page 50 Before You Configure an Interface on page 50 Configuration Tasks on page 51 Configuration Examples on page 60...
Page 72: Mdl Standards
JUNOSe 10.0.x Physical Layer Configuration Guide MDL Standards You can configure T3 interfaces to send MDL messages that comply with ANSI T1.107a-1990 Standard for Telecommunications Digital Hierarchy – Supplement to Formats Specification (August 1990). MDL messages identify a particular link by sharing common codes for data such as the equipment identifier, line identifier, frame identifier, and unit.
Page 73: Higher-Level Protocols
Chapter 2: Configuring T3 and E3 Interfaces For message strings that are unique to a particular message type, the line module must receive another message of the same type containing this string in order to retain the local copy of the string and reset the timer. For example, if the line module receives a test signal message containing a generator string and does not receive another test signal message within 10 seconds, it will erase the local copy of the generator string.
Page 74: Ocx/Stmx/Ds3-Atm Line Modules And 4Xds3 Atm I/O Modules
JUNOSe 10.0.x Physical Layer Configuration Guide Clocking Redundancy Frame Relay logical interface support Unique IP interface support for each PPP or Frame Relay PVC interface HDLC Fractional T3 (T3 only) Line speeds of 45 Mbps (T3) and 34 Mbps (E3) OCx/STMx/DS3-ATM Line Modules and 4xDs3 ATM I/O Modules ERX-7xx models, ERX-14xx models, and the ERX-310 router support the OCx/STMx/DS3-ATM line modules and 4xDS3 ATM I/O modules.
Page 75: Interface Stack
Chapter 2: Configuring T3 and E3 Interfaces CT3/T3-F0 line modules and CT3/T3 12 I/O I/O modules to support the following: Clocking Redundancy Frame Relay logical interface support Unique IP interface support for each PPP or Frame Relay PVC interface Line speeds of 45 Mbps Interface Stack Figure 3 on page 49 shows the stack for T3 ATM interfaces.
Page 76: References
JUNOSe 10.0.x Physical Layer Configuration Guide and 8–13 (slots 6 and 7 are reserved for SRP modules). In the ERX-310 router, the line module slots are numbered 0–2 (slot 0 is reserved for the SRP module). port Number of the port on the I/O module. On the CT3/T3 12 I/O and E3-12 FRAME I/O modules, ports are numbered 0–11.
Page 77: Configuration Tasks
Chapter 2: Configuring T3 and E3 Interfaces Configuration Tasks Configure a T3 interface by entering Global Configuration mode and performing the following tasks: Configure a T3 controller. (Optional) Configure MDL settings. (Optional) Configure other settings for the interface. Configure HDLC channels for T3 frame and E3 frame controllers. (Optional) Configure fractional T3 for T3 frame controllers.
Page 78: Configuring Mdl Messages
JUNOSe 10.0.x Physical Layer Configuration Guide slot Number of the slot in which the line module resides in the chassis port Number of the port on the I/O module Example host1(config)#controller e3 3/2 There is no no version. See controller e3. controller t3 Use to specify a T3 controller in slot/port format.
Page 79 Chapter 2: Configuring T3 and E3 Interfaces Specify the MDL messages. host1(config-controll)#mdl string eic "ERX-1410" 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 Enable transmission of MDL messages. host1(config-controll)#mdl transmit path-id host1(config-controll)#mdl transmit idle-signal host1(config-controll)#mdl transmit test-signal mdl carrier...
Page 80: Optional Tasks
JUNOSe 10.0.x Physical Layer Configuration Guide 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. Enable cell scrambling (ATM interfaces only). Assign a text description or an alias to the interface. cablelength Use to adjust the transmit power appropriate to the length of a T3 cable.
Page 81 Chapter 2: Configuring T3 and E3 Interfaces Use to assign a text description or an alias to a T3 or E3 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 80 characters. Use “show controllers t3”...
Page 82: Configuring Fractional T3
JUNOSe 10.0.x Physical Layer Configuration Guide Use the no version to restore the default value. See framing. Configuring Fractional T3 You can configure fractional T3 on T3 frame interfaces. E3 frame interfaces do not support fractional 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).
Page 83: Configuring An Hdlc Channel
Chapter 2: Configuring T3 and E3 Interfaces Use the no version to clear the DSU mode. If you issue the no version, be sure to issue the no dsu bandwidth and no scramble commands. Otherwise, the interface might drop packets unexpectedly. See dsu mode.
Page 84 JUNOSe 10.0.x Physical Layer Configuration Guide Use to configure the size of the CRC. Specify the number of bits per frame (16 or 32) that are used to calculate the frame check sequence (FCS). Both the sender and receiver must use the same setting.
Page 85 Chapter 2: Configuring T3 and E3 Interfaces Example host1(config-if)#invert data Use the no version to disable the feature. See invert data. load-interval 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.
Page 86: Configuration Examples
JUNOSe 10.0.x Physical Layer Configuration Guide Use the no version to restore the default, 1600 bytes. See mtu. serial description Use to assign a text description or an alias to a serial HDLC interface. You can use this command to help you identify the interface and keep track of interface connections.
Page 87: Testing Interfaces
Chapter 2: Configuring T3 and E3 Interfaces Testing Interfaces Testing interfaces allows you to troubleshoot problems and to check the quality of links at various layers in the interface stack. The router supports the following test options: Transmission of BERT patterns to remote devices Local loopback—Loops the data back toward the router;...
Page 88: Enabling Local, Network, And Payload Loopback
JUNOSe 10.0.x Physical Layer Configuration Guide 2^11 Pseudorandom test pattern, 2047 bits in length 2^15 Pseudorandom test pattern, 32,767 bits in length 2^20 Pseudorandom test pattern, 1,048,575 bits in length 2^20-QRSS Pseudorandom QRSS test pattern, 1,048,575 bits in length 2^23 Pseudorandom test pattern, 8,388,607 bits in length alt-0-1 Repetitive alternating test pattern of zeros and ones, 01010101...
Page 89 Chapter 2: Configuring T3 and E3 Interfaces Configure one of the following loopback tests: Set the loopback to remote to request that a remote device connected on a T3 interface enter into a loopback. host1(config-controll)#loopback remote Configure the T3 interface to enable or disable the ability to enter into a loopback initiated by a remote device, as follows: Issue the equipment customer loopback command to enable the router to enter into loopback when it receives an appropriate signal from the...
Page 90: Monitoring Interfaces
JUNOSe 10.0.x Physical Layer Configuration Guide local Loops the data back toward the router; on supported line modules, also sends an alarm indication signal (AIS) out toward the network network Loops the data toward the network before the framer processes the data payload Loops the data toward the network after the framer processes the data...
Page 91: Output Filtering
Chapter 2: Configuring T3 and E3 Interfaces T3 last interval counters Displays the counters for the previous interval T3 24-hour total counters Displays the cumulative counters for the last 24-hours or since the interface was started The last 24-hours of 15-minute reporting intervals (96 intervals) The show controllers e3 slot/port all command displays identical information for an E3 controller (except where noted).
Page 92 JUNOSe 10.0.x Physical Layer Configuration Guide snmp trap link-status Status of SNMP trapping (enabled or disabled) alarms detected One of the following T3 alarms (not applicable for E3): No alarm present No alarms present on the line 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...
Page 93 Chapter 2: Configuring T3 and E3 Interfaces MDL Transmit Idle-Signal Indicates if the transmission is active or not active (T3 only) Equipment Identification Code eic string for MDL (T3 only) Line Identification Code lic string for MDL (T3 only) Frame Identification Code fic string for MDL (T3 only) Facility Identification Code fic string for MDL (T3 only) Equipment Port port string for MDL (T3 only) Unit Identification Code unit string for MDL (T3 only)
Page 94 JUNOSe 10.0.x Physical Layer Configuration Guide Severely errored frame seconds Number of severely errored framing seconds encountered by a T3 or E3 in the current interval Unavailable seconds Number of unavailable seconds encountered by a T3 or E3 in the current interval Line code violations Number of line code violations encountered by a T3 or E3 in the current interval P-bit coding violations Number of coding violations encountered by a T3...
Page 95 Chapter 2: Configuring T3 and E3 Interfaces Number of valid interval - 96 Time elapse in current interval - 861 Ds3 Current Interval Counters P-bit errored seconds P-bit severely errored seconds = 0 Severely errored frame seconds = 0 Unavailable seconds Line code violations P-bit coding violations Line errored seconds...
Page 96 JUNOSe 10.0.x Physical Layer Configuration Guide 4/0:1/1(unchannelized) down 4/2:1/1(channelized) lowerLayerDown See show controllers e3. See show controllers t3. show controllers t3 remote Use to display MIB statistics for the remote end of a T3 interface configured for MDL. Specify the all option to display detailed information for all 15-minute intervals. For definitions of the MIB statistics for a T3 interface, see RFC 2496 Definitions of Managed Objects for the DS3/E3 Interface Types (January 1999).
Page 97 Chapter 2: Configuring T3 and E3 Interfaces Unavailable seconds Number of unavailable seconds encountered by a T3 in the current interval Invalid seconds Number of seconds when statistics were not collected Example This example specifies a T3 interface. host1#show controllers t3 5/0 remote Far End MDL Carrier bit is not set Far End Equipment Identification Code is the null string Far End Line Identification Code is the null string...
Page 98 JUNOSe 10.0.x Physical Layer Configuration Guide Monitoring Interfaces...
Page 99: Configuring Unchannelized Ocx/Stmx Interfaces
Chapter 3 Configuring Unchannelized OCx/STMx Interfaces This chapter provides information you need to configure unchannelized SONET/SDH interfaces on E-series routers. This chapter contains the following sections: Overview on page 73 Platform Considerations on page 77 References on page 84 Configuration Tasks on page 84 Testing Interfaces on page 96 Monitoring SONET/SDH Interfaces on page 98 Overview...
Page 100: Automatic Switchover
JUNOSe 10.0.x Physical Layer Configuration Guide You configure a working interface on the primary port and a corresponding protect interface on the redundant port of the I/O module. The working interface provides the primary connection, and the protect interface provides the redundant connection. The router sends and receives data through both interfaces;...
Page 101: Reversion After Switchover
Chapter 3: Configuring Unchannelized OCx/STMx Interfaces Bidirectional Switching Mode In bidirectional switching mode, the router switches both ends of an APS pair to the same working interface or to the same protect interface when either end determines that a switch is required. Possible reasons for initiating a bidirectional switch include: Detection of a signal failure Receipt of an “aps force”...
Page 102: Table 8: Explanation Of K1 Byte
JUNOSe 10.0.x Physical Layer Configuration Guide 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. Table 8: Explanation of K1 Byte Bit Value (12345678) Meaning Bits 1–4 represent a request.
Page 103: Higher-Level Protocols
Chapter 3: Configuring Unchannelized OCx/STMx Interfaces Table 9: Explanation of K2 Byte (continued) Bit Value (12345678) Meaning 0001–1110 Channel number of working interface Bit 5 indicates the type of redundancy. 1+1 architecture Bits 6–8 indicate the switching mode. 000– 011 Reserved for future use Unidirectional mode Bidirectional mode...
Page 104: Ocx/Stmx/Ds3-Atm Line Modules
JUNOSe 10.0.x Physical Layer Configuration Guide See ERX Module Guide, Appendix A, Module Protocol Support for information about the protocols and applications that SONET/SDH modules support. For detailed information about the modules that support SONET/SDH interfaces on the E120 router and the E320 router: See E120 and E320 Module Guide, Table 1, Modules and IOAs for detailed module specifications.
Page 105: Oc48 Line Modules
Chapter 3: Configuring Unchannelized OCx/STMx Interfaces 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. Figure 6 on page 79 shows the interface stack for OCx/STMx POS interfaces. Figure 6: Interface Stack for OCx/STMx POS and OC48/STM16 Interfaces OC48 Line Modules OC48 line modules pair with OC48 FRAME I/O modules to deliver unchannelized...
Page 106: Es2 4G Line Module
JUNOSe 10.0.x Physical Layer Configuration Guide The interface stack for OC3/STM1 ATM interfaces on the OC3-2 GE APS I/O module is the same as for OCx/STMx/DS3-ATM interfaces. (See Figure 5 on page 78.) For more information about configuring a Gigabit Ethernet interface on this I/O module, see “OC3-2 GE APS I/O Module”...
Page 107: Ocx/Stmx Atm Ioas
Chapter 3: Configuring Unchannelized OCx/STMx Interfaces packet sizes from 64–1518 bytes or a mixture of packet sizes that represent Internet mix traffic (IMIX). OCx/STMx ATM IOAs The ES2 4G LM pairs with the ES2-S1 OC3-8 STM1 ATM IOA to deliver unchannelized OC3/STM1 ATM operation through eight line interfaces.
Page 108: Erx-7Xx Models, Erx-14Xx Models, And The Erx-310 Router
JUNOSe 10.0.x Physical Layer Configuration Guide ERX-7xx Models, ERX-14xx Models, and the ERX-310 Router Use the slot/port format to identify unchannelized SONET/SDH interfaces. Interfaces that support APS/MSP also use the APS/MSP channel number. slot Number of the slot in which the line module resides in the chassis. In ERX-7xx models, line module slots are numbered 2–6;...
Page 109: E120 Router And E320 Router
Chapter 3: Configuring Unchannelized OCx/STMx Interfaces E120 Router and E320 Router Use the slot/adapter/port format to identify unchannelized SONET/SDH interfaces. NOTE: The E120 router and the E320 router do not support path channelization. slot Number of the slot in which the line module resides in the chassis. In the E120 router, line module slots are numbered 0–5.
Page 110: Exchanging Modules
JUNOSe 10.0.x Physical Layer Configuration Guide Exchanging Modules If you replace an OC3 I/O module with an OCx/STMx line module and a corresponding OC3-4 I/O module or vice versa, you must erase the configuration of the existing modules. See slot accept in JUNOSe System Basics Configuration Guide. On the E120 and E320 routers, if you replace an ES2-S1 OC3-8 STM1 ATM IOA with an ES2-S1 OC12 STM4 POS IOA, you must erase the configuration of the existing IOA.
Page 111: Configuring The Sonet/Sdh Layers
Chapter 3: Configuring Unchannelized OCx/STMx Interfaces On an ES2 4G LM with an ES2-S1 OC12-2 STM4 POS IOA or an ES2-S1 OC48 STM16 POS IOA, you can configure only POS interfaces. On an ES2 4G LM with an ES2-S1 OC3-8 STM1 ATM IOA or an ES2-S1 OC12-2 STM4 ATM IOA, you can configure only ATM interfaces.
Page 112 JUNOSe 10.0.x Physical Layer Configuration Guide To change the clock source of the ports on a cOC3/STM1 I/O module from the router’s clock to the module’s clock or vice versa, change the clock source of all ports firstly to the line setting, and then to the new internal clock setting. Example host1(config-controll)#clock source internal module Use the no version to revert to the default, line.
Page 113 Chapter 3: Configuring Unchannelized OCx/STMx Interfaces The description or alias can be a maximum of 64 characters. Example host1(config-controll)#path description westford Use the no version to remove the description. See path description. path overhead c2 Use to overwrite the automatic setting for the path signal label (C2) byte. By default, the value of the C2 byte for the path is determined by the layers configured above the SONET/SDH interface and set automatically.
Page 114 JUNOSe 10.0.x Physical Layer Configuration Guide host1(config-controll)#path snmp trap link-status Use the no version to disable SNMP link status processing. See path snmp trap link-status. path trigger alarm prdi Use to configure the router to use remote defect indications (RDIs) at the path layer to determine the operational status of a path.
Page 115: Configuring Aps/Msp
Chapter 3: Configuring Unchannelized OCx/STMx Interfaces Use to disable a SONET/SDH interface. SONET/SDH interfaces are enabled by default. Example host1 (config-controll)#shutdown Use the no version to restart a disabled interface. See shutdown. snmp trap link-status Use to enable SNMP link-status processing for the section and line layers of the interface.
Page 116: Configuring The Working Interface
JUNOSe 10.0.x Physical Layer Configuration Guide NOTE: Configuring the working interface before you configure the protect interface is not required. You can configure the working interface before or after you configure the protect interface. The E120 router and the E320 router does not support APS/MSP. Configuring the Working Interface To configure the working interface: Select the interface.
Page 117: Configuring The Protect Interface
Chapter 3: Configuring Unchannelized OCx/STMx Interfaces Use to set thresholds for the bit error rates associated with APS/MSP alarms. This command does not apply to the working interface. You can issue this command only for the protect interface. Specify one of the following keywords to indicate the alarm level: sd-ber Bit error rate that specifies signal degradation sf-ber Bit error rate that specifies signal failure Specify an integer n in one of the following ranges, where n corresponds to a...
Page 118 JUNOSe 10.0.x Physical Layer Configuration Guide aps group Use to specify the group to which the working and protect interfaces will belong. Specify the name of the APS group. Example host1(config-controll)#aps group boston Use the no version to remove a group of APS interfaces. See aps group.
Page 119: Configuring Sonet/Sdh Alarms
Chapter 3: Configuring Unchannelized OCx/STMx Interfaces Use the no version to remove the protect interface from the APS group. See aps protect. aps revert Use to revert to the original working interface when it recovers. Specify the number of minutes in the range 5–7, after which the router will switch to the working interface.
Page 120: Configuration Example
JUNOSe 10.0.x Physical Layer Configuration Guide threshold Use to set thresholds for the bit error rates associated with APS/MSP alarms. You can issue this command only for the protect interface. It does not apply to the working interface. Specify one of the following keywords to indicate the alarm level: sd-ber Bit error rate that specifies signal degradation sf-ber Bit error rate that specifies signal failure Specify an integer n in one of the following ranges, where n corresponds to a...
Page 121: Manual Switching To A Redundant Port
Chapter 3: Configuring Unchannelized OCx/STMx Interfaces Use to enable line modules to deliver APS events to the necessary SNMP traps. Use the list variable to deliver the following types of APS events: all Configure notification of all APS events channel-mismatch Configure notification of APS channel mismatches feplf Configure notification of APS far-end protection line failures mode-mismatch Configure notification of APS mode mismatches psbf Configure notification of APS protection signal byte failures...
Page 122: Testing Interfaces
JUNOSe 10.0.x Physical Layer Configuration Guide Use the no version to revert to the original working interface. See aps force. aps manual Use to switch from the working interface to the protect interface unless a command of equal or higher priority is in effect. You can issue this command only for the working interface, not for the protect interface.
Page 123: Testing Connectivity
Chapter 3: Configuring Unchannelized OCx/STMx Interfaces Use the no version to disable loopback. See loopback. Testing Connectivity Use the path overhead j1 command to check for connectivity between the router and a SONET/SDH device at the other end of the line. This command defines: A message that the router sends from the specified interface to the SONET/SDH device at the other end of the line.
Page 124: Monitoring Sonet/Sdh Interfaces
JUNOSe 10.0.x Physical Layer Configuration Guide Monitoring SONET/SDH Interfaces You can monitor interface statistics and APS/MSP settings. 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).
Page 125 Chapter 3: Configuring Unchannelized OCx/STMx Interfaces host1#baseline path interface sonet 2/0 Example 2 Sets a baseline for SONET path layer interfaces on the E320 router host1#baseline path interface sonet 3/0/0 There is no no version. See baseline path interface sonet. baseline section interface sonet Use to set a statistics baseline for the SONET/SDH section layer.
Page 126 JUNOSe 10.0.x Physical Layer Configuration Guide defect trigger soaking delay Time that the router waits to set an alarm when the router records a defect at the section or line layer Operational Status Physical state of the interface: up Interface is operational down, failure alarm Interface is not operational;...
Page 127 Chapter 3: Configuring Unchannelized OCx/STMx Interfaces Operational Status Physical state of the controller: up, down, or lowerLayerDown time since last status change: time the controller has been in the current physical state Received SONET Path overhead Path overhead bytes present in the receive side of the interface at any particular time Transmitted SONET Path overhead Path overhead bytes present in the transmit side of the interface at any particular time...
Page 128 JUNOSe 10.0.x Physical Layer Configuration Guide Use to display statistics for the different layers in channelized SONET and SDH interfaces. Figure 5 on page 78 and Figure 6 on page 79 show the layers in the interfaces. For definitions of the MIB statistics, see RFC 2558 Definitions of Managed Objects for the SONET/SDH Interface Type (March 1999).
Page 129 Chapter 3: Configuring Unchannelized OCx/STMx Interfaces REI Number of remote error indications Far End Last Interval Counters Statistics for the remote connection associated with the SONET/SDH path in the previous 15-minute interval Total Interval Counters Statistics for all intervals or baselined statistics Total Far End Counters Statistics for all remote connections associated with the SONET/SDH path Example 1 Shows the MIB statistics for the path layer on interface 1/0.
Page 130 JUNOSe 10.0.x Physical Layer Configuration Guide Far End Last Path Interval Counters Seconds Counts Total Far End Path Counters Seconds Counts 27255 Example 2 Shows the MIB statistics for the line layer on interface 1/0. host1#show controllers sonet 1/0 line Number of valid intervals - 31 Time elapsed in current interval - 114 Current status...
Page 131 Chapter 3: Configuring Unchannelized OCx/STMx Interfaces Total Far End Line Counters Seconds Counts Example 3 Shows the MIB statistics for the section layer on interface 1/0. host1#show controllers sonet 1/0 section Number of valid intervals - 31 Time elapsed in current interval - 49 Current status = No Defect Current Section Interval Counters...
Page 132: Monitoring Aps/Msp
JUNOSe 10.0.x Physical Layer Configuration Guide See show controllers sonet. Monitoring APS/MSP You can use the show aps commands to monitor APS/MSP. show aps Use to display information about interfaces on which APS/MSP is configured. Use the all keyword to display information from all APS/MSP groups. In the output, partially configured controllers are displayed with none and include only the group name.
Page 133 Chapter 3: Configuring Unchannelized OCx/STMx Interfaces 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 Nonrevertive sonet 12/0 sonet 12/1 sonet 12/2 none group partial-group sonet 12/3 sonet 12/4...
Page 134 JUNOSe 10.0.x Physical Layer Configuration Guide 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 SF Indicates that signal failure is detected switched Indicates that the router has switched from the working interface to the protect interface Counters Statistics for APS channel...
Page 135: Configuring Channelized Ocx/Stmx Interfaces
Chapter 4 Configuring Channelized OCx/STMx Interfaces Use the procedures described in this chapter to configure channelized OC3/STM1 and OC12/STM4 (cOCx/STMx) interfaces on E-series routers. This chapter contains the following sections: Overview on page 109 Platform Considerations on page 111 References on page 117 Before You Configure an Interface on page 118 Configuration Tasks on page 119 Configuration Examples on page 141...
Page 136: Mdl Standards
JUNOSe 10.0.x Physical Layer Configuration Guide line modules that support MDL and FDL, see ERX Module Guide, Appendix A, Module Protocol Support. 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.
Page 137: Frequency Of Fdl Path Messages
Chapter 4: Configuring Channelized OCx/STMx Interfaces Table 10: 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 –...
Page 138: Cocx/Stmx Fo Line Module
JUNOSe 10.0.x Physical Layer Configuration Guide ERX-1440 router ERX-1410 router ERX-710 router ERX-705 router ERX-310 router NOTE: The E320 router does not support configuration of channelized OCx/STMx interfaces. For detailed information about the modules that support cOCx/STMx interfaces on ERX-7xx models, ERX-14xx models, and the ERX-310 router: See ERX Module Guide, Table 1, Module Combinations for detailed module specifications.
Page 139: Sonet/Sdh Vt Controllers
Chapter 4: Configuring Channelized OCx/STMx Interfaces Figure 8: Stack for cOCx/STMx Interfaces NOTE: For a detailed description of interface types and specifiers, see Interface Types and Specifiers in JUNOSe Command Reference Guide. For information about interfaces, see Planning Your Network in JUNOSe System Basics Configuration Guide. The section layer manages the transport of STS/STM frames across the physical path.
Page 140: Figure 9: Sonet Multiplexing
JUNOSe 10.0.x Physical Layer Configuration Guide 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. NOTE: To configure a whole T1 or E1 line, assign 24 T1 or 31 E1 timeslots to a channel group or configure an unframed E1 line.
Page 141: Figure 10: Sdh Multiplexing
Chapter 4: Configuring Channelized OCx/STMx Interfaces Figure 10: SDH Multiplexing For both SONET/SDH VT configurations, you must identify the path and controllers above the path layer. Table 12 on page 115 shows the identifiers for these configurations, and Table 13 on page 115 provides definitions for the identifiers. Table 12: Identifiers for SONET/SDH VT Controllers Configuration Identifier...
Page 142: T3 Controllers
JUNOSe 10.0.x Physical Layer Configuration Guide Table 13: Definitions for Identifiers for SONET/SDH VT Controllers (continued) Identifier Definition Value tributaryGroup Number of the tributary In SONET mode, tributary group is the group within the path number of the VT group. In SDH mode, tributaryGroup is the number of the TUG-2 group.
Page 143: References
Chapter 4: Configuring Channelized OCx/STMx Interfaces slot Number of the slot in which the line module resides in the chassis. In ERX-7xx models, line module slots are numbered 2-6 (slots 0 and 1 are reserved for SRP modules). In ERX-14xx models, line module slots are numbered 0–5 and 8–13 (slots 6 and 7 are reserved for SRP modules).
Page 144: Before You Configure An Interface
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...
Page 145: Configuration Tasks
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.
Page 146 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.
Page 147 Chapter 4: Configuring Channelized OCx/STMx Interfaces Use the no version to remove the text description or alias. See description. path Use to configure paths over channelized SONET and SDH interfaces. Specify the correct identifier for the type of interface. See Interface Types and Specifiers in JUNOSe Command Reference Guide for details of the syntax.
Page 148 JUNOSe 10.0.x Physical Layer Configuration Guide Example host1(config-controll)#path 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. path shutdown Use to disable a specified path.
Page 149 Chapter 4: Configuring Channelized OCx/STMx Interfaces Specify a value of 0 milliseconds if this interface does not use APS/MSP or if MPLS should have priority over APS/MSP. Specify a value of at least 100 milliseconds if this interface uses APS/MSP and if APS/MSP should have priority over MPLS.
Page 150: Configuring Higher Layers
JUNOSe 10.0.x Physical Layer Configuration Guide Use the no version to restore the default setting, 2500 milliseconds. See trigger delay. Configuring Higher Layers You must now configure the next layer on the interface: E1, T1, or T3. See “T1/E1 Configuration Tasks” on page 124 or “T3 Configuration Tasks” on page 130. T1/E1 Configuration Tasks Before you configure T1 or E1 on an interface, you must configure SONET or SDH.
Page 151: Configuring An Unframed E1 Line
Chapter 4: Configuring Channelized OCx/STMx Interfaces Use the no version to remove the text description or alias. See path ds1|e1 description. Configuring an Unframed E1 Line Use the following command to configure an unframed E1 line. path e1 unframed Use to configure an unframed E1 on the path. You cannot configure a mixture of T1 and E1 lines on the same cOCx/STMx line module.
Page 152 JUNOSe 10.0.x Physical Layer Configuration Guide Use “show controllers sonet ds1|e1” on page 159 to display the text description. Example host1(config-controller)#path 10 e1 1/5/1 channel-group 4 description westford e1 151.4 Use the no version to remove the text description or alias. See path ds1|e1 channel-group description.
Page 153 Chapter 4: Configuring Channelized OCx/STMx Interfaces path ds1|e1 clock source Use to configure the transmit clock source for the T1 or E1 interface. Select a clock as follows: Specify the keyword line to use a transmit clock recovered from the line’s receive data stream.
Page 154: Configuring T1 Interfaces To Send Fdl Messages
JUNOSe 10.0.x Physical Layer Configuration Guide Use to enable SNMP link status processing for a T1 or an E1 interface and its associated tributary. The default is disabled. Example host1(config-controll)#path 2 ds1 1/1/1 snmp trap link-status Use the no version to disable SNMP link status processing. See path ds1|e1 snmp trap link-status.
Page 155 Chapter 4: Configuring Channelized OCx/STMx Interfaces Example host1(config-controll)#path 2 ds1 1/1/1 fdl att Use the no version to restore the default, none. See path ds1 fdl. path ds1 fdl carrier Use to specify that an interface is used in the carrier environment. Example host1(config-controll)#path 2 ds1 1/1/1 fdl carrier Use the no version to restore the default situation, in which the T1 interface does...
Page 156: Disabling Interfaces And Channel Groups
JUNOSe 10.0.x Physical Layer Configuration Guide Specify the keyword test-signal to transmit test signals every second. Example host1(config-controll)#path 2 ds1 1/1/1 fdl transmit path-id Use the no version to disable transmission of the specified FDL message or all FDL messages. See path ds1 fdl transmit.
Page 157: Configuring T3 Line Parameters
Chapter 4: Configuring Channelized OCx/STMx Interfaces host1(config-controller)#path 2 ds3 1 channelized Use the no version to delete a path. See path ds3. Configuring T3 Line Parameters Complete the following steps to configure T3 line parameters. Configure these parameters for both clear channel and multiplexed T3 lines. Configure the clock source.
Page 158 JUNOSe 10.0.x Physical Layer Configuration Guide Use the no version to restore the default value, line. See path ds3 clock source. path ds3 description Use to assign a text description or an alias to a T3 (DS3) over channelized SONET/SDH interface. You can use this command to help you identify the interface and keep track of interface connections.
Page 159: Configuring T3 Interfaces To Send Mdl Messages
Chapter 4: Configuring Channelized OCx/STMx Interfaces Use the no version to disable SNMP link status processing. See path ds3 snmp trap link-status. Configuring T3 Interfaces to Send MDL Messages You can configure a T3 interface to send MDL messages. MDL messages are supported only when the T3 framing is set for C-bit parity, the default setting.
Page 160: Configuring T1 Channels On T3 Interfaces
JUNOSe 10.0.x Physical Layer Configuration Guide Use the no version to restore the default value to the specified MDL message or to all MDL messages. See path ds3 mdl string. path ds3 mdl transmit Use to enable transmission of MDL messages. Specify the keyword path-id to transmit path identifications every second.
Page 161 Chapter 4: Configuring Channelized OCx/STMx Interfaces Use the no version to delete a path. See path ds3 t1. path ds3 t1 clock source Use to configure the transmit clock source for the T3 line. Use a transmit clock recovered from the line’s receive data stream, except in rare cases such as back-to-back router tests.
Page 162 JUNOSe 10.0.x Physical Layer Configuration Guide Use to configure the T1 framing format for a T3 interface. You must specify either esf (extended superframe) or sf (superframe) framing. The framing format you choose must be compatible with the framing format at the other end of the line.
Page 163: Configuring T1 Channels To Send Fdl Messages
Chapter 4: Configuring Channelized OCx/STMx Interfaces Configuring T1 Channels to Send FDL Messages To configure T1 channels to send FDL messages: 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.
Page 164 JUNOSe 10.0.x Physical Layer Configuration Guide Use to specify that T1 channels are used in the carrier environment. Example host1(config-controll)#path 2 ds3 1 t1 4,6,10-14 fdl carrier Use the no version to restore the default situation, in which the T1 channel does not operate in the carrier environment.
Page 165: Configuring Higher Layers
Chapter 4: Configuring Channelized OCx/STMx Interfaces Configuring Higher Layers You must configure HDLC over the top layer of the T3 interface. See “HDLC Channel Configuration Tasks” on page 139. HDLC Channel Configuration Tasks You must configure HDLC over the T3, T1, unframed E1, or fractional T1/E1 line that you configure on an interface.
Page 166 JUNOSe 10.0.x Physical Layer Configuration Guide Specify one of the following idle characters: flags Sets the idle character to 0x7E marks Sets the idle character to 0xFF Example host1(config-ifs)#idle-character marks Use the no version to restore the default value, 0x7E (flags). See idle-character.
Page 167: Configuration Examples
Chapter 4: Configuring Channelized OCx/STMx Interfaces Coordinate this value with the network administrator on the other end of the line. If you set this value with a different value for another protocol, such as IP, the router uses the lower value. The lower MRU might cause unexpected results in the network.
Page 168: Example 1: Configuring Interfaces In Sonet Mode
JUNOSe 10.0.x Physical Layer Configuration Guide Example 1: Configuring Interfaces in SONET Mode The following example illustrates how to configure T1 lines on channelized SONET interfaces, as shown in Figure 11 on page 142. Figure 11: Configuring Fractional T1 in SONET Mode Select an OC-12 SONET controller.
Page 169: Example 2: Configuring Interfaces In Sdh Mode
Chapter 4: Configuring Channelized OCx/STMx Interfaces 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 Configure two fractional T1 lines on the T3 in path channel 12. host1(config-controller)#path 12 ds3 1 t1 4/1 timeslots 3-8 host1(config-controller)#path 12 ds3 1 t1 4/2 timeslots 20 Example 2: Configuring Interfaces in SDH Mode...
Page 170: Example 3: Configuring Frame Relay
JUNOSe 10.0.x Physical Layer Configuration Guide host1(config-controller)#path 40 stm1 4 Configure a TU-12 on TUG-2 #7 on TUG-3 #2 of path 10. host1(config-controller)#path 10 e1 2/7/1 tu12 Configure a TU-12 on TUG-2 #5 on TUG-3 #2 of path 10. host1(config-controller)#path 10 e1 2/5/2 tu12 Configure a fractional E1 line on tributary 2/7/1 of path 10.
Page 171: Testing Interfaces
Chapter 4: Configuring Channelized OCx/STMx Interfaces Specify PPP as the encapsulation method on the interface. host1(config-if)#encapsulation ppp Testing Interfaces Testing interfaces allows you to troubleshoot problems and to check the quality of links at various layers in the interface stack. The router supports the following test options: Transmission of BERT patterns to remote devices Receipt of BERT patterns from remote devices...
Page 172 JUNOSe 10.0.x Physical Layer Configuration Guide Specify the duration of the test in the range 1–1440 minutes. Optionally, specify the unframed keyword to overwrite the framing bits. Example host1(config-controll)#path 12 ds1 1/3/4 bert pattern 2^11 interval 10 unframed Use the no version to stop the test that is running. See path ds1|e1 bert.
Page 173: Receiving Bert Patterns
Chapter 4: Configuring Channelized OCx/STMx Interfaces 2^15 Pseudorandom test pattern, 32,767 bits in length 2^20-O153 Pseudorandom test pattern, 1,048,575 bits in length Specify the duration of the test in the range 1–1440 minutes. Optionally, specify the unframed keyword to overwrite the framing bits. Example host1(config-controll)#path 12 ds3 2 t1 14 bert pattern 2^11 interval 10 unframed...
Page 174 JUNOSe 10.0.x Physical Layer Configuration Guide local Loops the data back toward the router; on supported line modules, also sends an alarm indication signal (AIS) out toward the network. network Loops the data toward the network before the data reaches the frame.
Page 175: Enabling Remote Loopback Testing
Chapter 4: Configuring Channelized OCx/STMx Interfaces host1(config-controll)#controller sonet 5/0 host1(config-controll)#path 12 ds3 1 loopback local Use the no version to turn off the loopback. See path ds3 loopback. path ds3 t1 loopback Use to configure a loopback at the T1 over T3 layer. Specify one of the following options: local Loops the router output data back toward the router at the T1 framer;...
Page 176 JUNOSe 10.0.x Physical Layer Configuration Guide Select a controller. Configure remote loopback at the desired layers in the interface. path ds1|e1 loopback remote Use to place a remote device, connected at the T1 over SONET/SDH VT layer, in loopback. Specify one of the following options: line fdl ansi (T1 only) Sends a repeating 16-bit ESF data link code word (00001110 11111111) to the remote end requesting that it enter into a network line loopback.
Page 177 Chapter 4: Configuring Channelized OCx/STMx Interfaces Use to enable or disable the router’s ability to enter into a loopback initiated by a remote device connected at the T3 layer. NOTE: Remote loopback is available only on frame-based T3 interfaces configured to use C-bit framing.
Page 178: Testing Connectivity
JUNOSe 10.0.x Physical Layer Configuration Guide loopback. Specify the ansi keyword to enable the remote line FDL ANSI bit loopback on the T1 line, according to the ANSI T1.403 specification. line fdl bellcore Sends a repeating 16-bit ESF data link code word (00010010 11111111) to the remote end requesting that it enter into a network line loopback.
Page 179: Monitoring Interfaces
Chapter 4: Configuring Channelized OCx/STMx Interfaces the show controllers sonet command to compare the expected and received messages. path overhead j1 Use to define messages that the router sends to or expects to receive from a SONET/SDH device connected to a cOCx/STMx interface. Specify a path identifier between 1 and 2,147,483,648 for a cOCx/STMx interface.
Page 180: Setting A Baseline
JUNOSe 10.0.x Physical Layer Configuration Guide Display statistics for serial interfaces. host1#show interfaces serial 2/0:1/1/1/1/1 Setting a Baseline You can set statistics baselines for serial interfaces, subinterfaces, and circuits using the baseline interface serial command. You can also set statistics baselines for the section, line, and path layers using the baseline interface sonet command.
Page 181 Chapter 4: Configuring Channelized OCx/STMx Interfaces 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.
Page 182 JUNOSe 10.0.x Physical Layer Configuration Guide alarms used for operational status calculation Types of defects that the router uses to determine the operational status of the interface at the section and line layers defect trigger soaking delay Time that the router waits to set an alarm when the router records a defect at the section or line layer Operational Status Physical state of the interface: up Interface is operational...
Page 183 Chapter 4: Configuring Channelized OCx/STMx Interfaces 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 alarms used for operational status calculation Types of defects that the router uses to determine the operational status of the interface at the path layer defect trigger soaking delay Time that the router waits to set an alarm...
Page 184 JUNOSe 10.0.x Physical Layer Configuration Guide time since last status change: 00:03:30 Loopback State: none Mode: sonet Timing source: internal module Receive FIFO Overruns: 0, Reconfigurations: 0 Current section defects: none Current line defects: none Channel configuration: channel = 0, path = oc12, hierarchy = 1/1/0/0, current path defects: none ifAdminStatus: up snmp trap link-status: disabled alarms used for operational status calculation: LOP AIS...
Page 185 Chapter 4: Configuring Channelized OCx/STMx Interfaces 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 defect trigger soaking delay: 2500 milliseconds Operational Status: up time since last status change: 00:03:30 Loopback State: none...
Page 186 JUNOSe 10.0.x Physical Layer Configuration Guide 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 Sync count Number of times the pattern detector synchronized with the incoming data pattern...
Page 187 Chapter 4: Configuring Channelized OCx/STMx Interfaces 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 Current Interval Counters Errored seconds Severely errored second...
Page 188 JUNOSe 10.0.x Physical Layer Configuration Guide 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 Sync count Number of times the pattern detector synchronized with the incoming data pattern...
Page 189 Chapter 4: Configuring Channelized OCx/STMx Interfaces 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 C-bit errored seconds C-bit severely errored seconds = 0 24 Hour Total Counters...
Page 190 JUNOSe 10.0.x Physical Layer Configuration Guide show controllers sonet line | path | section | tributary Use to display statistics for the different layers in channelized SONET and SDH interfaces. Figure 8 on page 113 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).
Page 191 Chapter 4: Configuring Channelized OCx/STMx Interfaces host1#show controllers sonet 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 Severely errored framing seconds = 0 Coding violations Example 2 This example illustrates the behavior of the baseline section...
Page 192 JUNOSe 10.0.x Physical Layer Configuration Guide host1#show controllers sonet 2/1 line Current Line Interval Counters Current status = No Defect Errored seconds Severly errored seconds Coding violations Unavailable seconds = 190 Last Line Interval Counters Errored seconds Severly errored seconds Coding violations Unavailable seconds = 900...
Page 193 Chapter 4: Configuring Channelized OCx/STMx Interfaces host1#show controllers sonet 4/0:1 tributary Tributary 1/1/1 Current Tributary Interval Counters Errored seconds Severly errored seconds Coding violations Unavailable seconds Last Tributary Interval Counters Errored seconds Severly errored seconds Coding violations Unavailable seconds Current Far End Path Interval Counters Errored seconds Severly errored seconds Coding violations...
Page 194 JUNOSe 10.0.x Physical Layer Configuration Guide For definitions of the MIB statistics for a T3 connections, see RFC 2496 Definitions of Managed Objects for the DS3/E3 Interface Types (January 1999). For definitions of the MIB statistics for a T1 connections, see RFC 2495 Definitions of Managed Objects for the DS1, E1, DS2 and E2 Interface Types (January 1999).
Page 195 Chapter 4: Configuring Channelized OCx/STMx Interfaces Time elapse in current interval Number of seconds that have passed in the 15-minute (900-second) interval Far End FDL Carrier bit Status of FDL configuration on remote device connected to T1 channel set FDL is configured for carrier mode not set FDL is not configured for carrier mode Far End Equipment Identification Code eic string sent by remote device for FDL...
Page 196 JUNOSe 10.0.x Physical Layer Configuration Guide Far End Equipment Identification Code is the null string Far End Line Identification Code is the null string Far End Frame Identification Code is the null string Far End Unit Identification Code is the null string Far End Facility Identification Code is the null string Far End Generator Number is the null string Far End Port Number is the null string...
Page 197 Chapter 4: Configuring Channelized OCx/STMx Interfaces DS1 24 Hour Total Counters Errored seconds Severely errored second Severely errored frame seconds = 0 Unavailable seconds Clock slip seconds Path code violations Line errored seconds Bursty errored seconds Degraded minutes Example 3 In this example, a T1 over channelized SONET interface is specified. host1#show controllers sonet 5/0:1/1/1/2/2 remote DS1 10/1:1 Number of valid interval - 0...
Page 198 JUNOSe 10.0.x Physical Layer Configuration Guide ifOperStatus Physical state of the interface ifOperDown Interface is not functioning ifOperLowerLayerDown Lower layer in the interface stack is not functioning ifOperNotPresent Module has been removed from the chassis ifOperTesting Interface is being tested ifOperUp Interface is functioning snmp trap link-status Enabled or disabled Encapsulation Layer 2 encapsulation display;...
Page 199: Monitoring Aps/Msp
Chapter 4: Configuring Channelized OCx/STMx Interfaces ifOperStatus = ifOperUp snmp trap link-status = disabled Encapsulation hdlc Crc type checking - CRC16 Hdlc mru = 1600 Hdlc mtu = 1600 Hdlc interface speed = 1536000 Hdlc idle-character marks Invert data disabled, Ds0 time slot map = 0xffffff Ds0 mode = Nx64 5 minute input rate 0 bits/sec, 0 packets/sec 5 minute output rate 0 bits/sec, 0 packets/sec...
Page 200 JUNOSe 10.0.x Physical Layer Configuration Guide Monitoring Interfaces...
Page 201: Configuring Ethernet Interfaces
Chapter 5 Configuring Ethernet Interfaces This chapter describes how to configure Ethernet interfaces on E-series routers. Most of the procedures described here do not apply to the Fast Ethernet management port on the SRP module. You can, however, select and display statistics for that port by using commands described in this chapter.
Page 202: Features
JUNOSe 10.0.x Physical Layer Configuration Guide NOTE: Read “Configuration Tasks for Ethernet” on page 194 before you begin to configure an Ethernet interface. Features Ethernet interfaces support the following features: Routing of IP packets. Quality of Service (QoS) classification. High-density Ethernet. (For information, see “High-Density Ethernet” on page 192 .) Virtual LAN (VLAN) configurations.
Page 203: Numbering Scheme
Chapter 5: Configuring Ethernet Interfaces See ERX Module Guide, Table 1, Module Combinations for detailed specifications of these modules. See ERX Module Guide, Appendix A, Module Protocol Support for information about the protocols and applications that Ethernet modules support. For detailed information about the modules that support Gigabit Ethernet and 10-Gigabit Ethernet interfaces on the E120 router and the E320 router: See E120 and E320 Module Guide, Table 1, Modules and IOAs for detailed specifications of these modules.
Page 204: Interface Specifier
JUNOSe 10.0.x Physical Layer Configuration Guide slot Number of the slot in which the line module resides in the chassis. In the E120 router, line module slots are numbered 0–5. In the E320 router, line module slots are numbered 0–5 and 11–16. For both routers, slots 6 and 7 are reserved for SRP modules;...
Page 205: Fe-8 Sfp I/O Module
Chapter 5: Configuring Ethernet Interfaces FE-8 SFP I/O Module ERX-7xx models, ERX-14xx models, and the ERX-310 router all support the FE-8 SFP I/O module. The FE-8 SFP I/O module uses a range of small form-factor pluggable transceivers (SFPs) to support different optical modes and cabling distances. The I/O module supports up to eight LC-style fiber-optic connectors.
Page 206: Ge-2 Sfp I/O Module
JUNOSe 10.0.x Physical Layer Configuration Guide You can configure only port 0 for a Gigabit Ethernet interface; you cannot configure redundant port 0R. Cabling both ports provides a redundant path to the Gigabit Ethernet interface. GE-2 SFP I/O Module The ERX-1440 router and the ERX-310 router both support the GE-2 SFP I/O module. Other E-series routers do not support the GE-2 SFP I/O module.
Page 207: Bandwidth And Line Rate Considerations
Chapter 5: Configuring Ethernet Interfaces The GE-8 I/O module pairs with the GE-HDE line module to provide Gigabit Ethernet operation through eight line interfaces. NOTE: The GE-8 I/O module has a logical port, numbered port 8, that is reserved for the hardware multicast packet replication feature.
Page 208: Managing High-Density Ethernet
JUNOSe 10.0.x Physical Layer Configuration Guide Table 16: Average Data Rate When Installed in All Other Slots on an ERX-1440 Router Average Data Rate per GE-8 I/O Average Data Rate per GE-HDE Port Combination Module (> 174 Byte Packets) Line Module Ports 1–8 125 Mbps per port 125 Mbps per port...
Page 209: Es2-S1 Ge-8 Ioa
Chapter 5: Configuring Ethernet Interfaces The ES2-S1 GE-4 IOA is offered in a halfheight size that enables you to configure it in one of two IOA bays that are available for each slot. You can install the ES2-S1 GE-4 IOA in only one of the IOA bays per slot.For more information about installing IOAs, see the E120 and E320 Hardware Guide.
Page 210: Table 17: Average Data Rate For One Es2-S1 Ge-8 Ioa Installed With An Es2
JUNOSe 10.0.x Physical Layer Configuration Guide Table 17: Average Data Rate for One ES2-S1 GE-8 IOA Installed with an ES2 4G LM 100 Gbps Configuration (E320 120 Gbps and 320 Gbps Configurations Router) (E120 and E320 Routers) Average Data Average Data Rate Rate per GE-8 per GE-8 IOA Average Data...
Page 211: Table 19: Average Data Rate For Es2-S1 Ge-8 Ioa Combined With Other Ioa Types In Same Slot
Chapter 5: Configuring Ethernet Interfaces 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. Table 19: Average Data Rate for ES2-S1 GE-8 IOA Combined with Other IOA Types in Same Slot 120 Gbps and 320 Gbps Average Data...
Page 212: Es2 10G Lm Combination
JUNOSe 10.0.x Physical Layer Configuration Guide 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. With a 100 Gbps fabric configuration, the E320 router can accommodate up to 2 combinations of ES2 10G LMs and ES2-S1 GE-8 IOAs.
Page 213: Es2-S3 Ge-20 Ioa
Chapter 5: Configuring Ethernet Interfaces Table 21: Average Data Rate for Two ES2-S1 GE-8 IOAs Installed with an ES2 10G 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...
Page 214: Bandwidth And Line Rate Considerations
JUNOSe 10.0.x Physical Layer Configuration Guide With a 120 Gbps fabric configuration, the E120 router can accommodate up to 6 combinations of ES2 10G LMs and ES2-S3 GE-20 IOAs. You can install a combination in any of the line module slots, each of which are allocated 10 Gbps of overall bandwidth.
Page 215: Managing High-Density Ethernet
Chapter 5: Configuring Ethernet Interfaces The ES2-S1 10GE IOA pairs with the ES2 4G LM to provide a 10-Gigabit Ethernet interface. For more information about the ES2 4G LM, see “ES2 4G Line Module” on page 80. The ES2-S1 10GE IOA is offered in a full-height size that uses both adapter bays. The IOA is identified by the software as adapter bay 0.
Page 216: Es2 10G Uplink Lm Combination
JUNOSe 10.0.x Physical Layer Configuration Guide ES2 10G Uplink LM Combination With a 100 Gbps fabric configuration, the E320 router can accommodate up to 2 combinations of ES2 10G Uplink LMs and ES2-S2 10GE PR IOAs. You must install a combination in either of the turbo slots (slot 2 or slot 4).
Page 217: Es2 10G Lm Combination
Chapter 5: Configuring Ethernet Interfaces priority packets. Packets that arrive at the line module are processed and transmitted using a flow-through scheme. Currently, flow control using MAC pause frames is disabled on the ES2-S2 10GE PR IOA. The IOA does not transmit or receive pause frames. Instead, the system prioritizes control traffic over non-control traffic (that is, data).
Page 218: Ethernet References
JUNOSe 10.0.x Physical Layer Configuration Guide prioritizes control traffic over non-control traffic (that is, data). For a list of types of control traffic, see “High-Density Ethernet” on page 192 . For information about configuring policies on the ES2 10G LM and ES2-S2 10GE PR IOA, see JUNOSe Policy Management Configuration Guide.
Page 219: Managing Port Redundancy On Gigabit Ethernet I/O Modules
Chapter 5: Configuring Ethernet Interfaces When the I/O module or IOA is oversubscribed, the packet classifier prioritizes the following types of control traffic: PPP discovery or PPP session Address Resolution Protocol (ARP) 802.3ad (link aggregation) 802.3 Spanning Tree Protocol (STP) IPv4 and IPv6 DHCP server IPv4 and IPv6 DHCP host IPv6 Neighbor Discovery...
Page 220: Configuration Tasks For Ethernet
JUNOSe 10.0.x Physical Layer Configuration Guide There is no no version. See link failover force. link failover timeout Use to specify the time that the router waits for a port on a GE I/O module to become active before the router switches to the redundant port. Select an interface on the GE I/O module before you issue this command.
Page 221: Configuring The Physical Interface
Chapter 5: Configuring Ethernet Interfaces 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 175. Configuring upper-layer protocols You must determine which upper-layer protocols, such as MPLS, to configure on the interface.
Page 222 JUNOSe 10.0.x Physical Layer Configuration Guide In networks where a link alternates between the up and down state for brief periods, we recommend that you set a longer debounce interval to prevent the router from prematurely and unnecessarily tearing down and rebuilding the PPPoE connections during brief network outages.
Page 223 Chapter 5: Configuring Ethernet Interfaces Use to specify the duplex mode. This command also works on the Fast Ethernet port on the SRP module on all E-series routers. For more information, see JUNOSe System Basics Configuration Guide. NOTE: If you set either the line speed or duplex mode to automatically negotiate by using the automatically negotiate keyword, the router negotiates both parameters.
Page 224 JUNOSe 10.0.x Physical Layer Configuration Guide Example 1 Selects a Fast Ethernet interface on ERX-7xx models, ERX-14xx models, or the ERX-310 router host1(config)#interface fastEthernet 1/0 Example 2 Selects the Fast Ethernet management port on an E320 router host1(config)#interface fastEthernet 6/0/0 Use the no version to remove IP from an interface or subinterface.
Page 225 Chapter 5: Configuring Ethernet Interfaces interface tenGigabitEthernet Use to select a 10-Gigabit Ethernet interface on the E120 router or the E320 router. NOTE: On the ES2-S2 10GE PR IOA, you can configure only the primary port, 0. The router automatically uses the redundant port, 0R, if the primary port fails. Use the slot/adapter/port format.
Page 226 JUNOSe 10.0.x Physical Layer Configuration Guide The default value is 300 seconds. Example host1(config-if)#load-interval 90 Use the no version to restore the default time interval, 300 seconds. See load-interval. Use to specify the MTU for an interface. Specify a value in the range 64–9188 bytes. The range for FE-8 I/O modules is 64–9042 bytes.
Page 227: Disabling Ethernet Interfaces
Chapter 5: Configuring Ethernet Interfaces Disabling Ethernet Interfaces Use the shutdown command to disable an Ethernet interface. shutdown Use to disable an Ethernet interface. Example host1(config-if)#shutdown Use the no version to restart a disabled Ethernet interface. See shutdown. Monitoring Ethernet Interfaces This section explains how to use the show commands to display the physical characteristics and the configured settings for Ethernet interfaces.
Page 228 100BASE-LX-SM (100 Mbps) 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...
Page 229 Chapter 5: Configuring Ethernet Interfaces 5 minute input rate Data rates based on traffic received in the last 5 minutes 5 minute output rate Data rates based on traffic sent in the last 5 minutes De-bounce Debounce configuration for this interface State is Enabled, Disabled Interval is Number of seconds that this interface maintains a given state before the state change is reported to the upper-layer links...
Page 230 JUNOSe 10.0.x Physical Layer Configuration Guide Mac Errors Number of outgoing packets discarded because of MAC sublayer failures Deferred Number of packets that the router delayed sending because the line was busy. In half duplex mode, a high number of deferrals means the link is very busy with traffic from other stations.
Page 231 Chapter 5: Configuring Ethernet Interfaces Duplex Mode: Operational Full Duplex, Administrative Auto Negotiate Speed: Operational 100 Mbps, Administrative Auto Negotiate De-bounce: State is Enabled, interval is 2 seconds 5 minute input rate 0 bits/sec, 0 packets/sec 5 minute output rate 0 bits/sec, 0 packets/sec In: Bytes 39256, Unicast 612 Multicast 0, Broadcast 0 Errors 0, Discards 0, Mac Errors 0, Alignment 0...
Page 232 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 233 Chapter 5: Configuring Ethernet Interfaces Primary/Secondary link signal detected, Primary/Secondary link signal not detected Specifies the port (primary or secondary) on which the router detects a signal (not displayed on GE I/O modules that do not support SFPs) 5 minute input rate Data rates based on the traffic received in the last 5 minutes 5 minute output rate Data rates based on the traffic sent in the last 5 minutes...
Page 234 JUNOSe 10.0.x Physical Layer Configuration Guide Deferred Number of packets that the router delayed sending because the line was busy. In half duplex mode, a high number of deferrals means the link is very busy with traffic from other stations. In full duplex mode, when the link is always available for transmission, this number is zero.
Page 235 Chapter 5: Configuring Ethernet Interfaces Link: Operational Secondary Link Selected, Administrative Link Selected Automatically Link Failover Timeout: Operational 652 ms, Administrative default Primary link selected 6302 times, Secondary link selected 6302 times Primary link signal detected, Secondary link signal detected 5 minute input rate 0 bits/sec, 0 packets/sec 5 minute output rate 0 bits/sec, 0 packets/sec In: Bytes 0, Unicast 0...
Page 236 JUNOSe 10.0.x Physical Layer Configuration Guide Address Hardware Addr 3.3.3.3 0090.1a30.3365 4.4.4.4 0090.1a30.3368 See show ip mac-validate interface. Monitoring Ethernet Interfaces...
Page 237: Managing Tunnel-Service And Ipsec-Service Interfaces
Chapter 6 Managing Tunnel-Service and IPSec-Service Interfaces This chapter describes how to configure tunnel-server ports, tunnel-service interfaces, and IPSec-service interfaces on E-series routers. This chapter contains the following sections: Tunnel-Service and IPSec-Service Overview on page 211 Tunnel-Service Interface Platform Considerations on page 213 Redundancy and Interface Distribution of Tunnel-Service Interfaces on page 217 Tunnel-Service Interface Considerations on page 219 Configuring Tunnel-Server Ports and Tunnel-Service Interfaces on page 221...
Page 238: Types Of Tunnel-Server Ports
JUNOSe 10.0.x Physical Layer Configuration Guide This section describes the types of tunnel-server ports that you can configure on tunnel-server modules and the types of tunnel-service interfaces that you can run on these ports. Types of Tunnel-Server Ports E-series routers support two types of tunnel-server ports: dedicated tunnel-server ports and shared tunnel-server ports.
Page 239: Tunnel-Service Interface Platform Considerations
Chapter 6: Managing Tunnel-Service and IPSec-Service Interfaces use these dynamic interfaces, see 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 dynamically.
Page 240: Erx-7Xx Models, Erx-14Xx Models, And The Erx-310 Router
JUNOSe 10.0.x Physical Layer Configuration Guide ERX-7xx Models, ERX-14xx Models, and the ERX-310 Router ERX-7xx models, ERX-14xx models, and the ERX-310 router all support Service Modules (SMs) and IPSec Service Modules (ISMs). Unlike other line modules, SMs and ISMs do not pair with corresponding I/O modules that provide ingress and egress ports.
Page 241: Numbering Scheme
Chapter 6: Managing Tunnel-Service and IPSec-Service Interfaces ES2 4G LM with the ES2-S1 GE-4 IOA ES2 4G LM with the ES2-S1 GE-8 IOA ES2 4G LM with the ES2-S1 10GE IOA ES2 4G LM with OCx/STMx ATM IOAs ES2 4G LM with OCx/STMx POS IOAs Numbering Scheme When configuring or managing tunnel-server ports, you must know the numbering scheme for identifying the physical location of the port in the E-series router.
Page 242: Interface Specifier
JUNOSe 10.0.x Physical Layer Configuration Guide For more information about identifying the port number on a tunnel-server port, see “Configuring Tunnel-Server Ports and Tunnel-Service Interfaces” on page 221 . For information about installing tunnel-server modules in the E120 and E320 routers, see E120 and E320 Hardware Guide, Chapter 4, Installing Modules.
Page 243: Redundancy And Interface Distribution Of Tunnel-Service Interfaces
Chapter 6: Managing Tunnel-Service and IPSec-Service Interfaces For a list of applications and services that dedicated and shared tunnel-server modules support on ERX-7xx models, ERX-14xx models, and the ERX-310 router, see ERX Module Guide, Appendix A, Module Protocol Support. For a list of applications and services that dedicated tunnel-server modules support on the E120 and E320 routers, see E120 and E320 Module Guide, Appendix A, IOA Protocol Support.
Page 244: Dynamic Tunnel-Service Interfaces
JUNOSe 10.0.x Physical Layer Configuration Guide Consequently, if you reinstall a module that was formerly unavailable or removed, the distribution of static tunnel-service interfaces over the modules might be uneven. Because users create and remove static tunnels, the distribution might remain uneven indefinitely.
Page 245: Tunnel-Service Interface Considerations
Chapter 6: Managing Tunnel-Service and IPSec-Service Interfaces The router then manages the interface as follows: If the interface’s local IP address (tunnel source) is less than the remote IP address (tunnel destination), the router attempts to reassign the interface to an available ISM.
Page 246: Bandwidth Limitations Of Shared Tunnel-Server Ports
JUNOSe 10.0.x Physical Layer Configuration Guide Bandwidth Limitations of Shared Tunnel-Server Ports Bandwidth limitations for shared tunnel-server ports and tunnel-service interfaces depend on bandwidth restrictions, if any, that are in effect for the module on which the shared tunnel-server port resides. Exchanging Tunnel-Server Modules Tunnel-server modules are available in different hardware revisions that support varying numbers of tunnel-service interfaces.
Page 247: Configuring Tunnel-Server Ports And Tunnel-Service Interfaces
Chapter 6: Managing Tunnel-Service and IPSec-Service Interfaces all of the tunnel-service interfaces on a tunnel-server port by issuing the no max-interfaces command or the no tunnel-server command. You can also restore the default configuration by issuing the default max-interfaces command. On dedicated tunnel-server ports, the default configuration is the maximum number of interfaces that the port supports.
Page 248: Verifying The Tunnel-Server Interface Configuration
JUNOSe 10.0.x Physical Layer Configuration Guide Provision the maximum number of tunnel-service interfaces to be used on the dedicated tunnel-server port. host1(config-tunnel-server)#max-interfaces all-available NOTE: When you issue the tunnel-server command, ensure that you specify the same interface specifier that was displayed for this tunnel-server port in the show tunnel-server config command in the output described in “Identifying the Physical Location of the Tunnel-Server Port”...
Page 249 Chapter 6: Managing Tunnel-Service and IPSec-Service Interfaces Issue the no tunnel-server command from Global Configuration mode. This command unprovisions the tunnel-service interfaces on the specified tunnel-server port but does not delete the port itself. host1(config)#no tunnel-server 2/2 max-interfaces Use from Tunnel Server Configuration mode to provision the maximum number of tunnel-service interfaces to be used on a tunnel-server port.
Page 250: Monitoring Tunnel-Service Interfaces
JUNOSe 10.0.x Physical Layer Configuration Guide tunnel-service interfaces that the tunnel-service module supports. On shared tunnel-server ports, the default configuration is zero tunnel-service interfaces. Use the no version to reduce the number of provisioned tunnel-service interfaces to zero. See tunnel-server. Monitoring Tunnel-Service Interfaces You can monitor tunnel-service interfaces by using the show tunnel-server command.
Page 251 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...
Page 252 JUNOSe 10.0.x Physical Layer Configuration Guide Example 2 Displays information about a dedicated tunnel-server port on an host1#show tunnel-server Card Oper Active Port:Appl Type State Interfaces Interfaces Fill --------------- --------- ------- ---------- ---------- ---- Port 2/0 dedicated present 8000 0.0% ipsec-tunnel 0 0.0% ipsec-transport...
Page 253: Part 2 Index
Part 2 Index Index on page 229 Index...
Page 254 JUNOSe 10.0.x Physical Layer Configuration Guide Index...
Page 255: Index
Index Symbols 10-Gigabit Ethernet interfaces baseline commands modules..............188 baseline interface..........201 specifying an interface........197 baseline interface serial 4xDS3 ATM I/O modules..........48 channelized T3 interfaces......29 cOCx/STMx interfaces........153 E3/T3 interfaces..........64 baseline line interface sonet......98, 153 Address Resolution Protocol. See ARP baseline path interface sonet......98, 153 all option (show controllers)........29, 64 baseline section interface sonet....98, 153 aps commands.............89...
Page 256 JUNOSe 10.0.x Physical Layer Configuration Guide clock commands clock source data stream inversion, enabling channelized T3 interfaces......13, 23 channelized T3 interfaces........21 cOCx/STMx interfaces......119, 125 cOCx/STMx interfaces.........139 E3/T3 interfaces........54, 61 E3/T3 interfaces............58 OCx/STMx interfaces........84 debounce command..........195 clock source, selecting debounce-interval command........196 channelized T3 interfaces.......13, 14 dedicated tunnel-server ports cOCx/STMx interfaces.........133...
Page 257 Index loopback command..........61 framing command monitoring interfaces..........64 channelized T3 interfaces........13 references.............50 E3/T3 interfaces............55 e3-scramble command..........54 framing format E320 routers..........77, 176, 213 channelized T3 interfaces.......13, 16 100 Gbps fabric..........80, 188 cOCx/STMx interfaces.........125, 130 120 Gbps fabric............80 E3/T3 line.............55 320 Gbps fabric..........80, 188 SONET/SDH interfaces..........77 equipment loopback command channelized T3 interfaces........23...
Page 258 JUNOSe 10.0.x Physical Layer Configuration Guide serial interfaces........21, 59, 139 link commands unchannelized SONET interfaces....84, 120 link failover force..........193 interface stack link failover timeout..........193 cOCx/STMx interfaces.........112 link selection............193 E3/T3 interfaces............47 LNS (L2TP network server) ES2-21 OC48/STM16 POS........81 termination............212 OCx/STMx POS interfaces........79 load-interval command OCx/STMx/DS3-ATM interfaces......78 channelized T3 interfaces........21...
Page 259 Index MRU (maximum receive unit) packets channelized T3 interfaces........21 intelligently dropping..........192 cOCx/STMx interfaces.........139 path commands E3/T3 interfaces............58 path..............120 mru command path description..........84, 120 channelized T3 interfaces........21 path e1 unframed..........125 cOCx/STMx interfaces.........139 path overhead c2..........84, 120 E3/T3 interfaces............58 path overhead j1...........97, 147 MSP................73 path snmp trap link-status......84, 120 MSP (Multiplex Section Protection).......73, 109...
Page 260 JUNOSe 10.0.x Physical Layer Configuration Guide path ds3 t1 snmp trap link-status......133 supported applications........215 path ds3 t1 timeslots..........133 supported modules..........213 path ds3 t1 fdl commands show aps commands path ds3 t1 fdl............133 show aps.............106 path ds3 t1 fdl carrier.........133 show aps group...........106 path ds3 t1 fdl transmit........133 show controllers commands pause frames.............180...
Page 261 Index SONET/SDH (synchronous optical loopback command..........61 network/Synchronous Digital Hierarchy) monitoring............64 alarms, configuring..........93 numbering scheme..........49 line modules supported.........77 testing..............147 MPLS fast reroute..........84, 119 T3, fractional..............56 source, clock technical support channelized T3 interfaces.......13, 14 contacting JTAC...........xxv E3/T3 interfaces............54 testing interfaces OCx/STMx interfaces........84, 119 channelized T3.............23 speed command............200 cOCx/STMx..........145, 147...
Page 262 JUNOSe 10.0.x Physical Layer Configuration Guide Index...

Juniper JUNOSE 10.0.X PHYSICAL LAYER Configuration Manual

About the Documentation

Chapters

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

Part 2 Index

Quick Links

Need help?

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for Juniper JUNOSE 10.0.X PHYSICAL LAYER

Summary of Contents for Juniper JUNOSE 10.0.X PHYSICAL LAYER

Table of Contents