Page 1 JUNOSe Software for E Series Broadband Services Routers Physical Layer Configuration Guide Release 11.0.x Juniper Networks, Inc. 1194 North Mathilda Avenue Sunnyvale, California 94089 408-745-2000 www.juniper.net Published: 2009-12-18...
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 11.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 Obtaining Documentation ................xxi Documentation Feedback ................xxi Requesting Technical Support ..............xxi Self-Help Online Tools and Resources ...........xxii Opening a Case with JTAC ..............xxii Part 1 Chapters...
Page 10 JUNOSe 11.0.x Physical Layer Configuration Guide Configuring an HDLC Channel ..............20 Optional Tasks .................20 Configuration Example ..................23 Testing Interfaces ..................23 Testing at the T3 Layer ................23 Testing at the T1 Layer ................26 Monitoring Interfaces ..................28 Setting a Baseline ..................29 Displaying Counters and Time Intervals ..........29 Output Filtering ..................29 Chapter 2 Configuring T3 and E3 Interfaces...
Page 11 Table of Contents 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 ES2 4G Line Module ................80 E120 Router Configuration ...............80 E320 Router Configuration ...............80 OCx/STMx ATM IOAs ...............81 OCx/STMx POS IOAs ................81...
Page 12 JUNOSe 11.0.x Physical Layer Configuration Guide HDLC ....................116 Numbering Scheme ................117 References ....................117 Before You Configure an Interface ...............118 Configuration Tasks ..................119 SONET/SDH Configuration Tasks ............119 Configuring Higher Layers ..............124 T1/E1 Configuration Tasks ..............124 Configuring an Unframed E1 Line ..........125 Configuring T1 and E1 Lines ............125 Configuring T1 Interfaces to Send FDL Messages ......128 Disabling Interfaces and Channel Groups ........130...
Page 13 Table of Contents Gigabit Ethernet I/O Modules and IOAs ............179 GE I/O Module ..................179 GE-2 SFP I/O Module ................180 Ports on GE-2 SFP I/O Module ............180 Bandwidth and Line Rate Considerations ........180 GE-8 I/O Module ..................180 Bandwidth and Line Rate Considerations ........181 Managing High-Density Ethernet ............182 OC3-2 GE APS I/O Module ..............182 ES2-S1 GE-4 IOA ...................182...
Page 14 JUNOSe 11.0.x Physical Layer Configuration Guide Chapter 6 Managing Tunnel-Service and IPSec-Service Interfaces Tunnel-Service and IPSec-Service Overview ..........215 Types of Tunnel-Server Ports ..............216 Dedicated Tunnel-Server Ports ............216 Shared Tunnel-Server Ports ............216 Types of Tunnel-Service Interfaces ............216 Tunnel-Service Interface Platform Considerations ........217 Supported Modules for Dedicated Tunnel-Server Ports ......217 ERX7xx Models, ERX14xx Models, and the ERX310 Router ...218 E120 and E320 Routers ..............218...
Page 15 List of Figures Part 1 Chapters Chapter 1 Configuring Channelized T3 Interfaces Figure 1: Stack for Channelized T3 Interface ...........7 Figure 2: T1 Channels and DS0 Timeslots on a T3 Line ........8 Chapter 2 Configuring T3 and E3 Interfaces Figure 3: Stack for T3 ATM Interfaces ............49 Figure 4: Stack for T3 Frame and E3 Frame Interfaces ........49 Chapter 3 Configuring Unchannelized OCx/STMx Interfaces...
Page 16 JUNOSe 11.0.x Physical Layer Configuration Guide List of Figures...
Page 17: List Of Tables
List of Tables About the Documentation Table 1: Notice Icons ..................xx Table 2: Text and Syntax Conventions ............xx Part 1 Chapters Chapter 1 Configuring Channelized T3 Interfaces Table 3: MDL and FDL Message Strings and Message Types ......4 Table 4: Sample T1 Subchannel/Timeslot Assignments ........8 Chapter 2 Configuring T3 and E3 Interfaces Table 5: MDL Message Strings and Message Types ........46...
Page 18 JUNOSe 11.0.x Physical Layer Configuration Guide Table 23: Average Data Rate for One ES2-S3 GE-20 IOA Installed with an ES2 10G LM ..................189 Table 24: Average Data Rate for One ES2-S3 GE-20 IOA Installed with an ES2 10G ADV LM ..................190 Chapter 6 Managing Tunnel-Service and IPSec-Service Interfaces Table 25: Sample Capacity, Configuration, and Utilization Values for...
Page 19: About The Documentation
If the information in the latest 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 product documentation page on the Juniper Networks website at http://www.juniper.net/techpubs/...
Page 20: Table 1: Notice Icons
JUNOSe 11.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: About The Documentation
{ permit | deny } { in | out } { clusterId | ipAddress } 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 22: Self-Help Online Tools And Resources
7 days a week, 365 days a year. Self-Help Online Tools and Resources For quick and easy problem resolution, Juniper Networks has designed an online self-service portal called the Customer Support Center (CSC) that provides you with the following features: Find CSC offerings: http://www.juniper.net/customers/support/...
Page 23: Chapters
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 215 Chapters...
Page 24 JUNOSe 11.0.x Physical Layer Configuration Guide Chapters...
Page 25: 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 Broadband Services 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...
Page 26: Mdl Standards
JUNOSe 11.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 27: Frequency Of Fdl Path Messages
See ERX Module Guide, Appendix A, Module Protocol Support for information about the higher-level protocols that channelized T3 interfaces support. Platform Considerations You can configure channelized T3 interfaces on the following Juniper Networks E Series Broadband Services Routers: ERX1440 router...
Page 28: Ct3/T3-F0 Line Modules And Ct3/T3 12 I/O Modules
JUNOSe 11.0.x Physical Layer Configuration Guide ERX705 router ERX310 router NOTE: The Juniper Networks E120 and E320 Broadband Services Routers do not support configuration of channelized T3 interfaces. For detailed information about the modules that support channelized T3 interfaces on ERX7xx models, ERX14xx models, and the ERX310 router: See ERX Module Guide, Table 1, Module Combinations for detailed module specifications.
Page 29: 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 30: T1 Channels
JUNOSe 11.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. To configure an entire T1 line, assign 24 timeslots to each channel.
Page 31: 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 32: Configuration Tasks
JUNOSe 11.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 33: Configuring Mdl Messages
Chapter 1: Configuring Channelized T3 Interfaces 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. See shutdown.
Page 34: Other Optional Tasks
JUNOSe 11.0.x Physical Layer Configuration Guide Use the no version to restore the default situation, in which the interface does not operate in the carrier environment. See mdl carrier. mdl string Use to specify an MDL message. Example host1(config-controll)#mdl string port 0800 Use the no version to restore the default value to the specified MDL message or to all MDL messages.
Page 35 Chapter 1: Configuring Channelized T3 Interfaces is greater than 225 feet. For example, if your cable size exceeds 225 feet, specify any number greater than 225 (and less than 451). Example host1(config-controll)#cablelength 300 Use the no version to restore the default value, 0 feet. See cablelength.
Page 36: Configuring T1 Channels
JUNOSe 11.0.x Physical Layer Configuration Guide Select c-bit framing if you intend to configure MDL messages. Example host1(config-controll)#framing c-bit Use the no version to restore the default value, c-bit. See framing. snmp trap ip link-status Use to enable SNMP link status processing on a T3 controller. Example host1(config-controll)#snmp trap link-status Use the no version to disable SNMP link status processing.
Page 37 Chapter 1: Configuring Channelized T3 Interfaces 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 host1(config)#controller t3 0/1 There is no no version.
Page 38 JUNOSe 11.0.x Physical Layer Configuration Guide t1 framing Use to configure the framing format for T1 channels. 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 39: Configuring Fdl Messages
Chapter 1: Configuring Channelized T3 Interfaces 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. channel T1 channel in the range 1–28 subchannel Number from 1–24 dash Represents a range of timeslots;...
Page 40 JUNOSe 11.0.x Physical Layer Configuration Guide host1(config-controll)#t1 1 yellow generate (Optional) Specify that the router should detect yellow alarms for the T1 channels. host1(config-controll)#t1 1 yellow detect t1 fdl Use to specify the FDL standard for the channel. Specify one or more T1 channels or a range of channels in the range 1–28. Specify the keyword ansi to support the ANSI FDL standard (see “References”...
Page 41 Chapter 1: Configuring Channelized T3 Interfaces Use the no version to restore the default value to the specified FDL message or to all FDL messages. See t1 fdl string. t1 fdl transmit Use to configure the router to send the specified type of FDL message. By default, the router sends only FDL performance data messages.
Page 42: Configuring An Hdlc Channel
JUNOSe 11.0.x Physical Layer Configuration Guide Configuring an HDLC Channel You must configure an HDLC channel for each group of fractional T1 lines and each full T1 line. To configure an HDLC channel, specify a serial interface (for example, HDLC channel in slot 0, port 1, channel 1, subchannel 5).
Page 43 Chapter 1: Configuring Channelized T3 Interfaces flags—Sets the idle character to 0x7E marks Sets the idle character to 0xFF Example host1(config-if)#idle-character marks Use the no version to restore the default value, 0x7E (flags). See idle-character. interface serial Use to configure a serial interface in the slot/port:channel/subchannel 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 channel T1 channel...
Page 44 JUNOSe 11.0.x Physical Layer Configuration Guide Use to configure the MRU size for the interface. Specify a value in the range 4–9996 bytes. You should coordinate this value with the network administrator on the other end of the line. If you configure a different MRU value in higher-level protocols, such as IP, the router uses the lower value.
Page 45: Configuration Example
Chapter 1: Configuring Channelized T3 Interfaces Configuration Example The following example illustrates how to configure the layers on a channelized T3 interface: host1(config)#controller t3 0/1 host1(config-controll)#no shutdown host1(config-controll)#framing c-bit host1(config-controll)#clock source internal module host1(config-controll)#cablelength 220 host1(config-controll)#t1 2 framing esf lihost1(config-controll)#t1 2 clock source internal host1(config-controll)#t1 2 loopback local host1(config-controll)#t1 2/1 timeslots 1,3-8,10 host1(config-controll)#exit...
Page 46 JUNOSe 11.0.x Physical Layer Configuration Guide 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 47 Chapter 1: Configuring Channelized T3 Interfaces equipment loopback Use to enable or disable the router’s ability to enter into a loopback initiated by a remote device connected on a channelized T3 interface. NOTE: Remote loopback is available only on channelized T3 interfaces configured to use C-bit framing.
Page 48: Testing At The T1 Layer
JUNOSe 11.0.x Physical Layer Configuration Guide Use the no version to restore the default configuration, no loopback. See loopback. Testing at the T1 Layer The T1 channel testing commands enable you to specify testing parameters for a single channel, multiple individual channels, ranges of channels, or any combination of the three types of specifications.
Page 49 Chapter 1: Configuring Channelized T3 Interfaces 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... NOTE: The BERT patterns supported when testing the T1 layer vary depending on the line module and I/O module assembly you are using.
Page 50: Monitoring Interfaces
JUNOSe 11.0.x Physical Layer Configuration Guide remote line inband—Sends a repeating 5-bit inband pattern (00001) to the remote end requesting that it enter into a network line loopback remote payload [ fdl ] [ ansi ] Sends a repeating, 16-bit, ESF data link code word (00010100 11111111) to the remote end requesting that it enter into a network payload loopback.
Page 51: Setting A Baseline
Chapter 1: Configuring Channelized T3 Interfaces host1#show controllers t3 serial 0/1 Setting a Baseline You can set a statistics baseline for serial interfaces, subinterfaces, and/or circuits using the baseline interface serial command. Use the delta keyword with the show commands to display statistics with the baseline subtracted. Displaying Counters and Time Intervals Counters and time intervals are MIB statistics, which are defined in the following specifications:...
Page 52 JUNOSe 11.0.x Physical Layer Configuration Guide Use the optional delta keyword with the show interfaces serial commands to view the baseline statistics. Example host1#baseline interface serial 2/0:1/1 There is no no version. See baseline interface. show controllers t1 show controllers t3 Use to display data and MIB statistics for a T3 interface or a T1 channel.
Page 53 Chapter 1: Configuring Channelized T3 Interfaces NOTE: The alarms detected field does not appear for interfaces that you disabled in the software. framing Type of framing format line code Type of line code format clock source Type of clock source cable length Cable length, in feet Loopback State of loopback for the controller: enabled or disabled.
Page 54 JUNOSe 11.0.x Physical Layer Configuration Guide Number of valid intervals Number of 15-minute intervals since the line module was last powered on or reset Time elapse in current interval Reported in 15-second intervals P-bit errored seconds Number of errored seconds encountered by a T3 in the current interval P-bit severely errored seconds Number of severely errored seconds encountered by a T3 in the current interval...
Page 55 Chapter 1: Configuring Channelized T3 Interfaces 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 C-bit coding violations C-bit errored seconds C-bit severely errored seconds = 0 Ds3 Last Interval Counters P-bit errored seconds...
Page 56 JUNOSe 11.0.x Physical Layer Configuration Guide Description Text description or alias if configured for the interface 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 Yellow Alarm detection Status of yellow alarm detection: active or not...
Page 57 Chapter 1: Configuring Channelized T3 Interfaces Sync count Number of times the pattern detector synchronized with the incoming data pattern Received bit count Number of bits received Error bit count Number of bits with errors Number of valid intervals Number of 15-minute intervals since the line module was last powered on or reset Time elapse in current interval Statistics are reported in 15-minute intervals Errored seconds Number of errored seconds encountered by a T1 in the...
Page 58 JUNOSe 11.0.x Physical Layer Configuration Guide Equipment Identification Code is the null string Line Identification Code is the null string Frame Identification Code is the null string Unit Identification Code is the null string Facility Identification Code is the null string Port Code is the null string Generator Number is the null string BERT test - 2 in 23...
Page 59 Chapter 1: Configuring Channelized T3 Interfaces Number of valid interval - 90 Time elapse in current interval - 580 Ds1 Current Interval Counters Errored seconds = 0 Severely errored second = 0 Severely errored frame seconds = 0 Unavailable seconds = 0 Clock slip seconds = 0 Path code violations = 0 Line errored seconds = 0...
Page 60 JUNOSe 11.0.x Physical Layer Configuration Guide snmp trap link-status of SNMP trapping (enabled or disabled) Ds0 time slot map Fractional T1 subchannel Ds0 mode Base data rate: either Nx56 or Nx64 The ft1 option displays the state of the serial interface. The optional slot and port parameters display information about a specific slot and port.
Page 61 Chapter 1: Configuring Channelized T3 Interfaces Number of valid intervals Number of 15-minute intervals since the line module was last powered on or reset Time elapse in current interval Number of seconds that have passed in the 15-minute (900-second) interval C-bit errored seconds Number of C-bit errored seconds encountered by a T3 in the current interval C-bit severely errored seconds Number of C-bit severely errored seconds...
Page 62 JUNOSe 11.0.x Physical Layer Configuration Guide DS1 Identifier of T1 channel Number of valid intervals Number of 15-minute intervals since the line module was last powered on or reset 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...
Page 63 Chapter 1: Configuring Channelized T3 Interfaces host1#show controllers t1 10/1:1 remote DS1 10/1:1 Number of valid interval - 0 Time elapse in current interval - 0 Far End FDL Carrier bit is not set 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...
Page 64 JUNOSe 11.0.x Physical Layer Configuration Guide Hdlc mru Current size of the maximum receive unit (MRU) Hdlc mtu Current size of the maximum transmission unit (MTU) Hdlc interface speed Current line speed of the interface Ds0 time slot map T1 subchannel Invert data disabled Status of the data inversion feature The optional slot and port parameters display information about a specific slot and port.
Page 65 Chapter 1: Configuring Channelized T3 Interfaces ifOperDown Interface is not functioning ifOperLowerDown Lower layer in the interface stack is not functioning snmp trap link-status Enabled or disabled Encapsulation Layer 2 encapsulation display; options include: ppp, frame-relay ietf, mlppp, mlframe-relay ietf, hdlc Crc type checking Size of the CRC Hdlc mru Current size of the MRU Hdlc mtu Current size of the MTU...
Page 66 JUNOSe 11.0.x Physical Layer Configuration Guide Invert data disabled Ds0 time slot map = 0xfff Ds0 mode = Nx64 Serial Interface at 13/0:2 Description: ottawa013 hdlc channel ifOperStatus = ifOperUp snmp trap link-status = disabled Crc type checking - CRC16 Hdlc mru = 1600 Hdlc mtu = 1600 Hdlc interface speed = 768000...
Page 67: 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 Broadband Services 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...
Page 68: Mdl Standards
JUNOSe 11.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 69: 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 70: Ocx/Stmx/Ds3-Atm Line Modules And 4Xds3 Atm I/O Modules
JUNOSe 11.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 ERX7xx models, ERX14xx models, and the ERX310 router support the OCx/STMx/DS3-ATM line modules and 4xDS3 ATM I/O modules.
Page 71: 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 72: References
JUNOSe 11.0.x Physical Layer Configuration Guide 8–13 (slots 6 and 7 are reserved for SRP modules). In the ERX310 router, the line module slots are numbered 0–2 (slot 0 is reserved for the SRP module). 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 73: 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 74: Configuring Mdl Messages
JUNOSe 11.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 75 Chapter 2: Configuring T3 and E3 Interfaces 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 Use to specify that an interface is used in the carrier environment.
Page 76: Optional Tasks
JUNOSe 11.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 77 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 78: Configuring Fractional T3
JUNOSe 11.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 79: Configuring An Hdlc Channel
Chapter 2: Configuring T3 and E3 Interfaces host1(config-controll)#dsu mode 0 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 80 JUNOSe 11.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 81 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 82: Configuration Examples
JUNOSe 11.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 83: 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 84: Enabling Local, Network, And Payload Loopback
JUNOSe 11.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 85 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 86: Monitoring Interfaces
JUNOSe 11.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 87: Output Filtering
Chapter 2: Configuring T3 and E3 Interfaces 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 88 JUNOSe 11.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 89 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 90 JUNOSe 11.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 91 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 92 JUNOSe 11.0.x Physical Layer Configuration Guide 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 93 Chapter 2: Configuring T3 and E3 Interfaces 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 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...
Page 94 JUNOSe 11.0.x Physical Layer Configuration Guide Monitoring Interfaces...
Page 95: 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 Broadband Services 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 97...
Page 96: Automatic Switchover
JUNOSe 11.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 97: 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 98: Table 7: Explanation Of K1 Byte
JUNOSe 11.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 7: Explanation of K1 Byte Bit Value (12345678) Meaning Bits 1–4 represent a request.
Page 99: Higher-Level Protocols
Chapter 3: Configuring Unchannelized OCx/STMx Interfaces Table 8: 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 100: Ocx/Stmx/Ds3-Atm Line Modules
JUNOSe 11.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 and E320 routers: See E120 and E320 Module Guide, Table 1, Modules and IOAs for detailed module specifications.
Page 101: 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 102: Es2 4G Line Module
JUNOSe 11.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 103: 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 104: Erx7Xx Models, Erx14Xx Models, And The Erx310 Router
JUNOSe 11.0.x Physical Layer Configuration Guide ERX7xx Models, ERX14xx Models, and the ERX310 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 ERX7xx models, line module slots are numbered 2–6;...
Page 105: Interface Specifier
Chapter 3: Configuring Unchannelized OCx/STMx Interfaces NOTE: The E120 and E320 routers 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. In the E320 router, line module slots are numbered 0–5 and 11–16.
Page 106: References
JUNOSe 11.0.x Physical Layer Configuration Guide IOA. See adapter accept or slot accept in chapter Managing Modules JUNOSe System Basics Configuration Guide. References For more information about MIB support for unchannelized SONET/SDH interfaces, see RFC 2558 Definitions of Managed Objects for the SONET/SDH Interface Type (March 1999).
Page 107 Chapter 3: Configuring Unchannelized OCx/STMx Interfaces Select an interface on which you want to configure SONET or SDH. Specify the type of interface: SONET or SDH. Specify a clock source for the interface. (Optional) Assign a text description or an alias to the interface. Disable processing of SNMP link status information for the section and line layers of the interface.
Page 108 JUNOSe 11.0.x Physical Layer Configuration Guide Use to select an interface on which you want to configure SONET or SDH. Use the interface specifier in slot/port:path-channel format (ERX14xx models, ERX7xx models, and the ERX310 Broadband Services Router ) or slot/adapter/port format (E120 and E320 routers).
Page 109 Chapter 3: Configuring Unchannelized OCx/STMx Interfaces 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. The E Series router sets this default value in accordance with RFC 2558.
Page 110 JUNOSe 11.0.x Physical Layer Configuration Guide Use to configure the router to use remote defect indications (RDIs) at the path layer to determine the operational status of a path. Do not specify a path identifier for unchannelized SONET/SDH interfaces. Example host1(config-controll)#path trigger alarm prdi Use the no version to restore the default setting, in which the software uses loss of pointer and AIS defects at the path layer to determine the operational status...
Page 111: Configuring Aps/Msp
Chapter 3: Configuring Unchannelized OCx/STMx Interfaces 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. The default is enabled. Example host1(config-controll)#no snmp trap link-status Use the no version to disable SNMP link status processing.
Page 112: Configuring The Working Interface
JUNOSe 11.0.x Physical Layer Configuration Guide Configuring the Working Interface To configure the working interface: Select the interface. host1(config)#controller sonet 4/0 Specify the APS group to which the working and protect interfaces will belong. host1(config-controll)#aps group boston Specify the interface as the working interface. host1(config-controll)#aps working aps group Use to specify the group to which the working and protect interfaces will belong.
Page 113: Configuring The Protect Interface
Chapter 3: Configuring Unchannelized OCx/STMx Interfaces Specify an integer n in one of the following ranges, where n corresponds to a rate of 10-n (10e-n) errors per second. For sd-ber, an integer in the range 5–9; the default value is 5 For sf-ber, an integer in the range 3–5;...
Page 114 JUNOSe 11.0.x Physical Layer Configuration Guide aps lockout Use to prevent the protect interface from taking over if the working interface fails. You can issue this command only for the protect interface, not for the working interface. The aps lockout command has a higher priority than the aps force command, aps manual command, a remote reversion request, a signal failure request, or a signal degradation.
Page 115: Configuring Sonet/Sdh Alarms
Chapter 3: Configuring Unchannelized OCx/STMx Interfaces host1(config-controll)#aps revert 7 Use the no version to restore the default setting, in which the router does not revert to the working interface when it recovers. See aps revert. aps unidirectional Use to specify that the router should switch to the protect interface using the unidirectional mode switching mechanism.
Page 116: Configuration Example
JUNOSe 11.0.x Physical Layer Configuration Guide For sd-ber, an integer in the range 5–9; the default value is 5 For sf-ber, an integer in the range 3–5; the default value is 3 Example host1(config-controll)#threshold sf-ber 4 Use the no version to restore the default, 5 (for sd-ber) or 3 (for sf-ber), for the specified alarm.
Page 117: Manual Switching To A Redundant Port
Chapter 3: Configuring Unchannelized OCx/STMx Interfaces Example host1(config)#aps events channel-mismatch Use the no version to disable the delivery of APS events from line modules to SNMP traps. See aps events. Manual Switching to a Redundant Port To switch from the working interface to the protect interface manually, issue the aps force command or the aps manual command.
Page 118: Testing Interfaces
JUNOSe 11.0.x Physical Layer Configuration Guide You must specify one of the following channel numbers: 0 Switches from the protect interface back to the working interface 1 Switches from the working interface to the protect interface Examples host1(config-controll)#aps manual 0 host1(config-controll)#aps manual 1 Use the no version to revert to the original working interface.
Page 119: Monitoring Sonet/Sdh Interfaces
Chapter 3: Configuring Unchannelized OCx/STMx Interfaces When you define a message that the interface sends, you must monitor receipt of that message at the remote end. When you define a message that the interface expects to receive, you should configure the remote device to transmit the same message to the interface.
Page 120 JUNOSe 11.0.x Physical Layer Configuration Guide To display statistics for SONET and SDH interfaces, use the show controllers sonet commands. Use the delta options to display statistics with the baseline subtracted. baseline line interface sonet Use to set a statistics baseline for the SONET/SDH line 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 121 Chapter 3: Configuring Unchannelized OCx/STMx Interfaces Use the total [ delta ] keywords with the show controllers sonet section commands to view the baseline statistics. Example 1 Sets a baseline for SONET section layer interfaces on ERX14xx models, ERX7xx models, or the ERX310 router host1#baseline section interface sonet 2/0 Example 2 Sets a baseline for SONET section layer interfaces on the E320 router...
Page 122 JUNOSe 11.0.x Physical Layer Configuration Guide chassis Internal clock is from the configured router clock Receive FIFO Overruns Number of times received FIFO was overrun Current section defects Number of suspect bit patterns found in several consecutive frames in section layer Current line defects Number of suspect bit patterns found in several consecutive frames in line layer Received SONET overhead Section and line overhead bytes present in the...
Page 123 Chapter 3: Configuring Unchannelized OCx/STMx Interfaces time since last status change: 07:33:12 Loopback State: none Mode: sonet Timing source: line Receive FIFO Overruns: 0, Framer stats: 0/0 Current section defects: none Current line defects: AIS Received SONET overhead: n/a, J0 n/a, K1 : 0xFF, K2 : 0xFF, S1...
Page 124 JUNOSe 11.0.x Physical Layer Configuration Guide SEFS Number of severely errored framing seconds encountered in an interval (Code Violations) Number of coding violations encountered in an interval (BIP-B1, BIP-B2, BIP-B3) RDI Number of remote defect indications AIS Number of alarm indication signals BERR-SF Number of bit error rate signal failures BERR-SD Number of bit error rate signal degrades LOS Number of loss of signal alarms...
Page 125 Chapter 3: Configuring Unchannelized OCx/STMx Interfaces Last Path Interval Counters Seconds Counts UNEQ BIP-B3 (Code Violation) Total Path Counters Seconds Counts 27255 27255 27255 UNEQ 27255 BIP-B3 (Code Violation) Current Far End Path Interval Counters Seconds Counts Far End Last Path Interval Counters Seconds Counts Total Far End Path Counters...
Page 126 JUNOSe 11.0.x Physical Layer Configuration Guide BERR-SF BERR-SD BIP-B2 (Code Violation) Total Line Counters Seconds Counts 27227 27227 BERR-SF BERR-SD BIP-B2 (Code Violation) Current Far End Line Interval Counters Seconds Counts Far End Last Line Interval Counters Seconds Counts Total Far End Line Counters Seconds Counts Example 3 Shows the MIB statistics for the section layer on interface 1/0.
Page 127: Monitoring Aps/Msp
Chapter 3: Configuring Unchannelized OCx/STMx Interfaces Total Section Counters Seconds Counts SEFS BIP-B1 (Code Violation) Example 4 Shows all statistics for all sessions for the section layer on interface 2/0. host1#show controllers sonet 2/0 section total Number of valid intervals - 31 Time elapsed in current interval - 244 Total Section Counters Seconds...
Page 128 JUNOSe 11.0.x Physical Layer Configuration Guide Unidirectional Router switches to the protect interface using the unidirectional mode switching mechanism Nonrevertive Router does not revert to the working interface when it recovers Revertive Router reverts to the working interface when it recovers Disabled APS/MSP is disabled on the interface Enabled APS/MSP is enabled on the interface Example 1...
Page 129 Chapter 3: Configuring Unchannelized OCx/STMx Interfaces ModeMismatch Number of differences detected in the local and remote switching mechanisms (unidirectional or bidirectional modes) ChanMismatch Number of differences detected between the number of the channel in the transmitted K1 byte and the number of the channel in the received K2 byte PSBF Number of protection switching byte failures detected (no 3 consecutive SONET/SDH frames out of the last 12 contain identical K1...
Page 130 JUNOSe 11.0.x Physical Layer Configuration Guide FEPLF Aps channel 0 (5/4) (aps-protect) Current Conditions: SF Counters SignalDegrades = 0 SignalFailures = 1 Aps channel 1 (5/0) (aps-working) Current Conditions: None Counters SignalDegrades = 0 SignalFailures = 0 Switchovers LastSwitchover = Not Applicable See show aps.
Page 131: 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 Broadband Services Routers. This chapter contains the following sections: Overview on page 109 Platform Considerations on page 112 References on page 117 Before You Configure an Interface on page 118 Configuration Tasks on page 119...
Page 132: Mdl Standards
JUNOSe 11.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 133: Frequency Of Fdl Path Messages
Chapter 4: Configuring Channelized OCx/STMx Interfaces Table 9: 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 134: Platform Considerations
JUNOSe 11.0.x Physical Layer Configuration Guide Platform Considerations You can configure cOCx/STMx interfaces on the following E Series Broadband Services Routers: ERX1440 router ERX1410 router ERX710 router ERX705 router ERX310 router NOTE: The E320 router does not support configuration of channelized OCx/STMx interfaces.
Page 135: Interface Stack
Chapter 4: Configuring Channelized OCx/STMx Interfaces Interface Stack Figure 8 on page 113 shows the stack for cOCx/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.
Page 136: Figure 9: Sonet Multiplexing
JUNOSe 11.0.x Physical Layer Configuration Guide default channel group speed for both T1 and E1 is 64 Kbps; 56 Kbps is also available. An unframed E1 line Unframed E1 lines have no timeslots reserved for framing. The router creates one channel for an unframed E1 line and assigns the number one to that channel. 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 137: 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 11 on page 115 shows the identifiers for these configurations, and Table 12 on page 115 provides definitions for the identifiers. Table 11: Identifiers for SONET/SDH VT Controllers Configuration Identifier...
Page 138: T3 Controllers
JUNOSe 11.0.x Physical Layer Configuration Guide Table 12: 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 139: Numbering Scheme
Chapter 4: Configuring Channelized OCx/STMx Interfaces Numbering Scheme A cOCx/STMx interface is identified by the slot/port format, where: slot Number of the slot in which the line module resides in the chassis. In ERX7xx models, line module slots are numbered 2-6 (slots 0 and 1 are reserved for SRP modules).
Page 140: Before You Configure An Interface
JUNOSe 11.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 141: 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 142 JUNOSe 11.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 143 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 144 JUNOSe 11.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 145 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 146: Configuring Higher Layers
JUNOSe 11.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 147: 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 148 JUNOSe 11.0.x Physical Layer Configuration Guide The description or alias can be a maximum of 80 characters. 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.
Page 149 Chapter 4: Configuring Channelized OCx/STMx Interfaces Use the no version to remove the timeslots from the channel group. See path ds1|e1 channel-group timeslots. 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 150: Configuring T1 Interfaces To Send Fdl Messages
JUNOSe 11.0.x Physical Layer Configuration Guide Use the no version to restore the default value. See path ds1|e1 framing. path ds1|e1 snmp trap link-status Use to enable SNMP link status processing for a T1 or an E1 interface and its associated tributary.
Page 151 Chapter 4: Configuring Channelized OCx/STMx Interfaces Specify the keyword all to support both the ANSI and AT&T standards. Specify the keyword none to remove the current FDL mode settings. You can configure a different standard on each T1 channel. Example host1(config-controll)#path 2 ds1 1/1/1 fdl att Use the no version to restore the default, none.
Page 152: Disabling Interfaces And Channel Groups
JUNOSe 11.0.x Physical Layer Configuration Guide NOTE: The router sends FDL messages specified with the path ds1 fdl string command only if you have issued the path ds1 fdl command with the ansi or all keyword. If you specified the att keyword with the path ds1 fdl command, the router sends only performance data.
Page 153: Configuring T3 Line Parameters
Chapter 4: Configuring Channelized OCx/STMx Interfaces Configure T3 line parameters (for both clear channel T3 lines and multiplexed T3 lines composed of fractional T1 lines). (Optional) Configure T1 or fractional T1 line parameters. For detailed examples, see “Configuration Examples” on page 142. path ds3 Use to create and configure a T3 path over SONET and SDH interfaces.
Page 154 JUNOSe 11.0.x Physical Layer Configuration Guide internal clock sources must use either the router’s clock or the module’s clock. You cannot configure some interfaces on the I/O module to use the router’s clock and others to use the module’s clock. To change the clock source of the interfaces on a cOC3/STM1 I/O module from the router’s clock to the module’s clock or vice versa, first change the clock source of all ports to the line setting, and then to the new internal clock setting.
Page 155: Configuring T3 Interfaces To Send Mdl Messages
Chapter 4: Configuring Channelized OCx/STMx Interfaces Use the no version to restart a disabled interface. See path ds3 shutdown. path ds3 snmp trap link-status Use to enable SNMP link status processing for a T3 interface. The default disables SNMP link status processing. Example host1(config-controll)#path 12 ds3 1 snmp trap link-status Use the no version to disable SNMP link status processing.
Page 156: Configuring T1 Channels On T3 Interfaces
JUNOSe 11.0.x Physical Layer Configuration Guide Use the no version to restore the default situation, in which the interface does not operate in the carrier environment. See path ds3 mdl carrier. path ds3 mdl string Use to specify an MDL message. Example host1(config-controll)#path 12 ds3 1 mdl string port 0800 Use the no version to restore the default value to the specified MDL message or...
Page 157 Chapter 4: Configuring Channelized OCx/STMx Interfaces (Optional) Enable processing of SNMP link status information about a channel group. path ds3 t1 Use to create and configure the T1 path over SONET and SDH interfaces. Example host1(config-controll)#path 12 ds3 1 t1 25-28 Use the no version to delete a path.
Page 158 JUNOSe 11.0.x Physical Layer Configuration Guide host1(config-controller)#path 12 ds3 1 t1 28 description boston_t1_on_t3 host1(config-controller)#path 12 ds3 1 t1 28/5 description washington_fractional_t1_on_t3 Use the no version to remove the text description or alias. See path ds3 t1 description. path ds3 t1 framing Use to configure the T1 framing format for a T3 interface.
Page 159: Configuring T1 Channels To Send Fdl Messages
Chapter 4: Configuring Channelized OCx/STMx Interfaces Examples host1(config-controll)#path 2 ds3 1 t1 28 timeslots 1-10 host1(config-controll)#path 2 ds3 1 t1 28/1 timeslots 1-10 speed 56 Use the no version to delete the fractional T1 circuit. See path ds3 t1 timeslots. Configuring T1 Channels to Send FDL Messages To configure T1 channels to send FDL messages: Specify a SONET interface.
Page 160 JUNOSe 11.0.x Physical Layer Configuration Guide Use the no version to restore the default, no specified FDL standard. See path ds3 t1 fdl. path ds3 t1 fdl carrier 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...
Page 161: Configuring Higher Layers
Chapter 4: Configuring Channelized OCx/STMx Interfaces Use the no version to disable transmission of the specified FDL message or all FDL messages. See path ds3 t1 fdl transmit. Configuring Higher Layers You must configure HDLC over the top layer of the T3 interface. See “HDLC Channel Configuration Tasks”...
Page 162 JUNOSe 11.0.x Physical Layer Configuration Guide 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 host1(config-ifs)#idle-character marks Use the no version to restore the default value, 0x7E (flags).
Page 163 Chapter 4: Configuring Channelized OCx/STMx Interfaces Use to configure the MRU size for the interface. Specify a value in the range 4–9996 bytes. 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.
Page 164: Configuration Examples
JUNOSe 11.0.x Physical Layer Configuration Guide Configuration Examples This section provides some configuration examples to illustrate how to use the CLI commands. 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.
Page 165: Example 2: Configuring Interfaces In Sdh Mode
Chapter 4: Configuring Channelized OCx/STMx Interfaces Configure an unchannelized T3 on SONET path channel 10. host1(config-controller)#path 10 ds3 1 unchannelized Configure a channelized T3 on SONET path channel 12. host1(config-controller)#path 12 ds3 1 channelized Configure a T1 channel on the channelized T3 on SONET path channel 12. host1(config-controller)#path 12 ds3 1 t1 4 Configure two fractional T1 lines on the T3 in path channel 12.
Page 166: Example 3: Configuring Frame Relay
JUNOSe 11.0.x Physical Layer Configuration Guide host1(config-controller)#path 20 stm1 2 host1(config-controller)#path 30 stm1 3 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 167: Testing Interfaces
Chapter 4: Configuring Channelized OCx/STMx Interfaces 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 Local loopback—The ability to loop the data back toward the router;...
Page 168 JUNOSe 11.0.x Physical Layer Configuration Guide 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. path ds3 bert Use to enable bit error rate tests using the specified pattern at the T3 layer. Unlike other configuration commands, “path ds3 bert”...
Page 169: Receiving Bert Patterns
Chapter 4: Configuring Channelized OCx/STMx Interfaces 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 Use the no version to stop the test that is running.
Page 170 JUNOSe 11.0.x Physical Layer Configuration Guide Example host1(config)#controller sonet 4/0 host1(config-controller)#loopback network Use the no version to disable loopback. See loopback. path ds1|e1 loopback Use to configure a loopback at the T1/E1 over SONET/SDH VT layer. Specify one of the following options: local Loops the router output data back toward the router at the T1/E1 framer;...
Page 171: Enabling Remote Loopback Testing
Chapter 4: Configuring Channelized OCx/STMx Interfaces 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 172 JUNOSe 11.0.x Physical Layer Configuration Guide 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 173 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 174: Testing Connectivity
JUNOSe 11.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 175: 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 176: Setting A Baseline
JUNOSe 11.0.x Physical Layer Configuration Guide 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. Use the delta options with the show commands to display statistics with the baseline subtracted.
Page 177 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 178 JUNOSe 11.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 179 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 180 JUNOSe 11.0.x Physical Layer Configuration Guide 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 181 Chapter 4: Configuring Channelized OCx/STMx Interfaces 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 Mode: sonet Timing source: internal module...
Page 182 JUNOSe 11.0.x Physical Layer Configuration Guide 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 Received bit count Number of bits received Error bit count Number of bits with errors...
Page 183 Chapter 4: Configuring Channelized OCx/STMx Interfaces 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 Severely errored frame seconds Unavailable seconds Clock slip seconds Path code violations Line errored seconds...
Page 184 JUNOSe 11.0.x Physical Layer Configuration Guide 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 Received bit count Number of bits received Error bit count Number of bits with errors...
Page 185 Chapter 4: Configuring Channelized OCx/STMx Interfaces 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 P-bit errored seconds P-bit severely errored seconds = 0 Severely errored frame seconds = 0 Unavailable seconds Line code violations...
Page 186 JUNOSe 11.0.x Physical Layer Configuration Guide 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 187 Chapter 4: Configuring Channelized OCx/STMx Interfaces 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 interface sonet command.
Page 188 JUNOSe 11.0.x Physical Layer Configuration Guide Unavailable seconds = 190 Last Line Interval Counters Errored seconds Severly errored seconds Coding violations Unavailable seconds = 900 Current Far End Line Interval Counters Errored seconds Severly errored seconds Coding violations Unavailable seconds Far End Last Line Interval Counters Errored seconds Severly errored seconds...
Page 189 Chapter 4: Configuring Channelized OCx/STMx Interfaces Errored seconds Severly errored seconds Coding violations Unavailable seconds Current Far End Path Interval Counters Errored seconds Severly errored seconds Coding violations Unavailable seconds Far End Last Tributary Interval Counters Errored seconds Severly errored seconds Coding violations Unavailable seconds Example 6 This example displays the tributary statistics for the tributary 1/1/1...
Page 190 JUNOSe 11.0.x Physical Layer Configuration Guide 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 Far End Frame Identification Code fic string sent by remote device for MDL...
Page 191 Chapter 4: Configuring Channelized OCx/STMx Interfaces Far End Equipment Identification Code eic string sent by remote device for FDL Far End Line Identification Code lic string sent by remote device for FDL Far End Frame Identification Code fic string sent by remote device for FDL Far End Unit Identification Code unit string sent by remote device for FDL Far End Facility Identification Code pfi string sent by remote device for Far End Generator Number generator string sent by remote device for FDL...
Page 192 JUNOSe 11.0.x Physical Layer Configuration Guide 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 Unavailable seconds Invalid seconds Ds3 24 Hour Total Counters...
Page 193 Chapter 4: Configuring Channelized OCx/STMx Interfaces host1#show controllers sonet 5/0:1/1/1/2/2 remote DS1 10/1:1 Number of valid interval - 0 Time elapse in current interval - 0 Far End FDL Carrier bit is not set 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...
Page 194 JUNOSe 11.0.x Physical Layer Configuration Guide snmp trap link-status Enabled or disabled Encapsulation Layer 2 encapsulation display; options: ppp, frame-relay ietf, mlppp, mlframe-relay ietf, hdlc Crc type checking Size of the CRC Hdlc mru Current size of the MRU Hdlc mtu Current size of the MTU Hdlc interface speed Current line speed of the interface Hdlc idle-character Current idle character Invert data disabled Status of the data inversion feature...
Page 195: Monitoring Aps/Msp
Chapter 4: Configuring Channelized OCx/STMx Interfaces Packets received Bytes received 1300 Errored packets received Packets sent Bytes send 1436 Errored packets sent See show interfaces. Monitoring APS/MSP For information about monitoring APS/MSP, see “Monitoring APS/MSP” on page 105 in “Configuring Unchannelized OCx/STMx Interfaces” on page 73. Monitoring Interfaces...
Page 196 JUNOSe 11.0.x Physical Layer Configuration Guide Monitoring Interfaces...
Page 197: Configuring Ethernet Interfaces
Chapter 5 Configuring Ethernet Interfaces This chapter describes how to configure Ethernet interfaces on E Series Broadband Services 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 198: Features
JUNOSe 11.0.x Physical Layer Configuration Guide Ethernet modules use the Address Resolution Protocol (ARP) to obtain MAC addresses for outgoing Ethernet frames. For more information about ARP, see JUNOSe IP, IPv6, and IGP Configuration Guide . NOTE: Read “Configuration Tasks for Ethernet” on page 198 before you begin to configure an Ethernet interface.
Page 199: Numbering Scheme
Chapter 5: Configuring Ethernet Interfaces For detailed information about the modules that support Fast Ethernet and Gigabit Ethernet interfaces on the ERX14xx models, ERX7xx models, and the ERX310 router: See ERX Module Guide, Table 1, Module Combinations for detailed specifications of these modules.
Page 200: Interface Specifier
JUNOSe 11.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 201: Ge-2 Sfp I/O Module
Chapter 5: Configuring Ethernet Interfaces FE-8 SFP I/O Module ERX7xx models, ERX14xx models, and the ERX310 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 202: Ge-2 Sfp I/O Module
JUNOSe 11.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 ERX1440 router and the ERX310 routers both support the GE-2 SFP I/O module. Other E Series routers do not support the GE-2 SFP I/O module.
Page 203: 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 204: Managing High-Density Ethernet
JUNOSe 11.0.x Physical Layer Configuration Guide Table 15: Average Data Rate When Installed in All Other Slots on an ERX1440 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 205: 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 206: Table 16: Average Data Rate For One Es2-S1 Ge-8 Ioa Installed With An Es2
JUNOSe 11.0.x Physical Layer Configuration Guide Table 16: Average Data Rate for One ES2-S1 GE-8 IOA Installed with an ES2 4G LM 120 Gbps and 320 Gbps 100 Gbps Configuration (E320 Configurations router) (E120 and E320 routers) Average Data Rate per GE-8 Average Data Rate Average Data per GE-8 IOA...
Page 207: Table 18: Average Data Rate For Es2-S1 Ge-8 Ioa Combined With Other Ioa Types In Same Slot
Chapter 5: Configuring Ethernet Interfaces Each OC12/STM4 port has a maximum theoretical bandwidth of 622 Mbps. Each OC3/STM1 port has a maximum theoretical bandwidth of 155 Mbps. Therefore, the OC12/STM4 IOAs have a maximum theoretical bandwidth of 1.244 Gbps and the OC3/STM1 IOA has an maximum theoretical bandwidth of 1.244 Gbps.
Page 208: Es2 10G Lm Combination
JUNOSe 11.0.x Physical Layer Configuration Guide For more information about high-density Ethernet on E Series routers, see “High-Density Ethernet” on page 196. 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.
Page 209: Es2 10G Adv Lm Combination
Chapter 5: Configuring Ethernet Interfaces Table 20: 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 210: Es2-S3 Ge-20 Ioa
JUNOSe 11.0.x Physical Layer Configuration Guide Table 21 on page 188 lists the average data rate on the ES2-S1 GE-8 IOA when installed in E120 and E320 routers with one ES2 10G ADV LM installed. Table 21: Average Data Rate for One ES2-S1 GE-8 IOA Installed with an ES2 10G ADV 100 Gbps, 120 Gbps, or 320 Gbps Configuration Average Data Rate per GE-8 IOA...
Page 211: Es2 10G Lm Combination
Chapter 5: Configuring Ethernet Interfaces The ES2-S3 GE-20 IOA pairs with the ES2 10G LM or the ES2 10G ADV LM to provide Gigabit Ethernet operation through 20 line interfaces. The ES2-S3 GE-20 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 212: Es2 10G Adv Lm Combination
JUNOSe 11.0.x Physical Layer Configuration Guide The line module can become oversubscribed because of the IOA available wire rate (20 Gbps). Currently, flow control using MAC pause frames is disabled on the ES2-S3 GE-20 IOA. The IOA does not transmit or receive pause frames. For more information about high-density Ethernet on E Series routers, see “High-Density Ethernet”...
Page 213: 10-Gigabit Ethernet Ioas
Chapter 5: Configuring Ethernet Interfaces Currently, flow control using MAC pause frames is disabled on the ES2-S3 GE-20 IOA. The IOA does not transmit or receive pause frames. For more information about high-density Ethernet on E Series routers, see “High-Density Ethernet” on page 196. 10-Gigabit Ethernet IOAs 10-Gigabit Ethernet interfaces are supported on the ES2-S1 10GE IOA and the ES2-S1 10GE PR IOA.
Page 214: Es2 10G Uplink Lm Combination
JUNOSe 11.0.x Physical Layer Configuration Guide The ES2-S2 10GE PR IOA is offered in a full-height size that uses both adapter bays. The IOA is identified by the software as adapter bay 0. For more information about installing IOAs, see the E120 and E320 Hardware Guide. The ES2-S2 10GE PR IOA has one port, uses a range of XFPs to support different optical modes and cabling distances, and accepts 10 LC-style fiber-optic connectors.
Page 215: Es2 10G Lm Combination
Chapter 5: Configuring Ethernet Interfaces Multicast The ES2 10G Uplink LM can receive multicast traffic, including all multicast control protocols. The ES2 10G Uplink LM can also transmit multicast control protocol frames and multicast data frames to perform multicast egress elaboration. L2TP An E Series router can be configured as either an L2TP access concentrator (LAC) or an L2TP network server (LNS).
Page 216: Es2 10G Adv Lm Combination
JUNOSe 11.0.x Physical Layer Configuration Guide Access Operation The ES2 10G LM and ES2-S2 10GE PR IOA combination provides traditional broadband access services such as PPPoE and subscriber interfaces. It also supports both sides of the L2TP LNS and LAC function. The combination can receive and transmit full duplex line rate of 10 GB (10 GB at the ingress and 10 GB at the egress).
Page 217: Ethernet References
Chapter 5: Configuring Ethernet Interfaces Access Operation The ES2 10G ADV LM and ES2-S2 10GE PR IOA combination provides traditional broadband access services such as PPPoE and subscriber interfaces. It also supports both sides of the L2TP LNS and LAC function. The combination can receive and transmit full duplex line rate of 10 GB (10 GB at the ingress and 10 GB at the egress).
Page 218: High-Density Ethernet
JUNOSe 11.0.x Physical Layer Configuration Guide For more information about MIB support for Ethernet interfaces, consult the following resources: RFC 2863 The Interfaces Group MIB (June 2000) RFC 2668 Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs) (August 1999) RFC 2665 Definitions of Managed Objects for the Ethernet-like Interface Types (August 1998) High-Density Ethernet...
Page 219: Managing Port Redundancy On Gigabit Ethernet I/O Modules
Chapter 5: Configuring Ethernet Interfaces Managing Port Redundancy on Gigabit Ethernet I/O Modules By default, the software manages port redundancy on Gigabit Ethernet I/O modules automatically. However, you can manage redundancy on GE I/O modules as follows: Specify the time that the router waits for a port on a Gigabit Ethernet I/O module to become active before the router switches to the redundant port.
Page 220: Configuration Tasks For Ethernet
JUNOSe 11.0.x Physical Layer Configuration Guide host1(config)#interface gigabitEthernet 5/0 host1(config-if)#link failover force 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.
Page 221: Configuring The Physical Interface
Chapter 5: Configuring Ethernet Interfaces Configuring VLANs and stacked VLANs (S-VLANs) After you configure the physical interface, you must decide whether to configure the Ethernet interface with or without VLANs or S-VLANs. VLANs and S-VLANs enable you to multiplex multiple IP interfaces and PPPoE interfaces over a single physical Ethernet port. If you are not configuring with VLANs or S-VLANs, proceed to “Configuring Ethernet Interfaces”...
Page 222 JUNOSe 11.0.x Physical Layer Configuration Guide Specify the interval, in seconds, for which an interface must maintain a given state before the state change is reported to the upper-layer links. The range is 1–5 seconds and the default interval is 1 second. Observe the following guidelines when you configure the debounce feature for Ethernet interfaces: In networks where a link alternates between the up and down state for brief...
Page 223 Chapter 5: Configuring Ethernet Interfaces Use the no version to restore the default value, 1 second. See debounce-interval. duplex Use to specify the duplex mode. This command also works on the Fast Ethernet port on the SRP module on all E Series routers.
Page 224 JUNOSe 11.0.x Physical Layer Configuration Guide Use the slot/port [.subinterface] format for Fast Ethernet interfaces on ERX7xx models, ERX14xx models, and the ERX310 router . Use the slot/adapter/port format for the SRP IOA on the E120 or E320 routers; the port on the SRP IOA is always identified by 0.
Page 225 Chapter 5: Configuring Ethernet Interfaces Use the no version to remove IP from an interface. You must issue the no version from the highest level down; you cannot remove an interface or subinterface if the one above it still exists. See interface gigabitEthernet.
Page 226 JUNOSe 11.0.x Physical Layer Configuration Guide Use to set the time interval at which the router calculates bit and packet rate counters. This command does not work for the Fast Ethernet port on the SRP module. Specify a multiple of 30 seconds, in the range 30–300 seconds. The default value is 300 seconds.
Page 227: Disabling Ethernet Interfaces
Chapter 5: Configuring Ethernet Interfaces Use the no version to revert to the default, either automatically negotiate or 100 Mbps (FE-8 SFP I/O module only). See speed. Disabling Ethernet Interfaces Use the shutdown command to disable an Ethernet interface. shutdown Use to disable an Ethernet interface.
Page 228: Using Ethernet Show Commands
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 Speed Line speed for this interface Operational Current rate at which packets are processed Administrative Setting for line speed 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...
Page 230 JUNOSe 11.0.x Physical Layer Configuration Guide Errors Total number of errors in all transmitted packets; some packets might contain more than one error Discards Total number of discarded outgoing packets Mac Errors Number of outgoing packets discarded because of MAC sublayer failures Deferred Number of packets that the router delayed sending because the line was busy.
Page 231 Chapter 5: Configuring Ethernet Interfaces host1:vr2#show interfaces fastEthernet 2/0 FastEthernet2/0 is Up, Administrative status is Up Hardware is Intel 21440, address is 0090.1a10.0552 MAU is 10BASE-T MTU: Operational 1518, Administrative 1518 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...
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 Only primary port is configured to operate secondary Only redundant port is configured to operate automatically Software controls port redundancy automatically Link Failover Timeout Time to wait for a failed link to be active before the router uses a different active link Primary link selected x times Number of times that the I/O has used the primary port since the module was last rebooted...
Page 234 JUNOSe 11.0.x Physical Layer Configuration Guide Bytes Number of bytes sent Unicast Number of unicast packets sent Multicast Number of multicast packets sent Broadcast Number of broadcast packets sent Errors Total number of errors in all transmitted packets; note that some packets might contain more than one error Discards Total number of discarded outgoing packets Mac Errors Number of outgoing packets discarded because of MAC...
Page 235 Chapter 5: Configuring Ethernet Interfaces downstream devices. Reports statistics in bytes in cells and accounts for cell encapsulation and padding overhead. none Shaping mode is not configured Operational qos-shaping-mode Actual shaping mode for the interface: disabled frame cell none queue Hardware packet queue associated with the specified traffic class and interface traffic class Name of traffic class bound to Interface to which queue is bound...
Page 236 JUNOSe 11.0.x Physical Layer Configuration Guide Out: Bytes 0, Unicast 0 Multicast 0, Broadcast 0 Errors 0, Discards 0, Mac Errors 0, Deferred 0, No Carrier 0 Collisions: Single 0, Multiple 0, Late 0, Excessive 0 Policed Statistics: In: 0, Out: 0 ARP Statistics: In: ARP requests 0, ARP responses 0 Errors 0, Discards 0...
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 Broadband Services Routers. This chapter contains the following sections: Tunnel-Service and IPSec-Service Overview on page 215 Tunnel-Service Interface Platform Considerations on page 217 Redundancy and Interface Distribution of Tunnel-Service Interfaces on page 221 Tunnel-Service Interface Considerations on page 223 Configuring Tunnel-Server Ports and Tunnel-Service Interfaces on page 225...
Page 238: Types Of Tunnel-Server Ports
JUNOSe 11.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 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. This mechanism means that you must manage the interfaces for tunnels manually: however, the router adds and removes tunnels when required.
Page 240: Erx7Xx Models, Erx14Xx Models, And The Erx310 Router
JUNOSe 11.0.x Physical Layer Configuration Guide ERX7xx Models, ERX14xx Models, and the ERX310 Router ERX7xx models, ERX14xx models, and the ERX310 router all support Service Modules (SMs) and IPSec Service Modules (ISMs). 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 11.0.x Physical Layer Configuration Guide For information about installing tunnel-server modules in the E120 and E320 routers, see E120 and E320 Hardware Guide, Chapter 4, Installing Modules. Interface Specifier The configuration task examples in this chapter use the format for ERX7xx models, ERX14xx models, and the ERX310 router to specify a tunnel-server port.
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 tunnel-server modules support on the E120 and E320 routers, see E120 and E320 Module Guide, Appendix A, IOA Protocol Support. Redundancy and Interface Distribution of Tunnel-Service Interfaces The redundancy and distribution mechanisms supported for tunnel-service ports configured on ISMs differ from those supported for SMs, the ES2-S1 Service IOA, and shared tunnel-server ports.
Page 244: Dynamic Tunnel-Service Interfaces
JUNOSe 11.0.x Physical Layer Configuration Guide Dynamic Tunnel-Service Interfaces The router dynamically creates and deletes dynamic tunnel-service interfaces as dictated by the operation of the relevant protocols. Currently, L2TP sessions are the only dynamic tunnel-service interfaces available. When the router creates a dynamic tunnel-service interface, it assigns that interface to a particular module.
Page 245: Tunnel-Service Interface Considerations
Chapter 6: Managing Tunnel-Service and IPSec-Service Interfaces ISM. If the reassignment is successful, the router immediately initiates an IPSec negotiation, also known as rekeying the interface. If the interface’s local IP address is greater than the remote IP address, the router attempts to reassign the interface to an available ISM.
Page 246: Bandwidth Limitations Of Shared Tunnel-Server Ports
JUNOSe 11.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 11.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 11.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 11.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 233 Index...
Page 254 JUNOSe 11.0.x Physical Layer Configuration Guide Index...
Page 255: Index
Index Symbols 10-Gigabit Ethernet interfaces baseline commands modules..............191 baseline interface..........205 specifying an interface........201 baseline interface serial 4xDS3 ATM I/O modules..........48 channelized T3 interfaces......28 cOCx/STMx interfaces........153 E3/T3 interfaces..........64 baseline line interface sonet......97, 153 Address Resolution Protocol. See ARP baseline path interface sonet......97, 153 all option (show controllers)........28, 64 baseline section interface sonet....97, 153 aps commands.............89...
Page 256 JUNOSe 11.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..........199 clock source, selecting debounce-interval command........200 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 Broadband Services Routers....77, 176, 217 channelized T3 interfaces.......13, 16 100 Gbps fabric..........80, 191 cOCx/STMx interfaces.........125, 130 120 Gbps fabric............80 E3/T3 line.............55 320 Gbps fabric..........80, 191 equipment loopback command channelized T3 interfaces........23 T3 interfaces............61...
Page 258 OCx/STMx interfaces..........96 ISMs (IPSec Service modules) monitoring............228 redundancy and interface distribution....221 MAC (media access control) addresses validation............201 MAC pause frames.............180 Juniper Networks E320 Broadband Services Routers maintenance data link. See MDL SONET/SDH interfaces..........77 manual switchover, APS/MSP........95 manuals comments on............xxi max-interfaces command..........227 K1 byte, APS/MSP............76...
Page 259 Index monitoring. See specific feature, product, or protocol MPLS (Multiprotocol Label Switching) packet classifier............196 fast reroute...........84, 119 packets MRU (maximum receive unit) intelligently dropping..........196 channelized T3 interfaces........21 path commands cOCx/STMx interfaces.........139 path..............120 E3/T3 interfaces............58 path description..........84, 120 mru command path e1 unframed..........125 channelized T3 interfaces........21 path overhead c2..........84, 120 cOCx/STMx interfaces.........139...
Page 260 JUNOSe 11.0.x Physical Layer Configuration Guide path ds3 t1 shutdown.........133 shared tunnel-server ports path ds3 t1 snmp trap link-status......133 configuring............225 path ds3 t1 timeslots..........133 overview.............216 path ds3 t1 fdl commands supported applications........219 path ds3 t1 fdl............133 supported modules..........217 path ds3 t1 fdl carrier.........133 show aps commands path ds3 t1 fdl transmit........133 show aps.............105...
Page 261 Index SONET APS 1+1 redundancy. See APS/MSP equipment loopback command......61 SONET/SDH (synchronous optical loopback command..........61 network/Synchronous Digital Hierarchy) monitoring............64 alarms, configuring..........92 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............xxi E3/T3 interfaces............54 testing interfaces...
Page 262 JUNOSe 11.0.x Physical Layer Configuration Guide Index...

This manual is also suitable for:

Junose 11.0.x

Juniper JUNOSE 11.0.X PHYSICAL LAYER Configuration Manual

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

Chapters

Chapter 4 Configuring Channelized Ocx/Stmx Interfaces

Configuring Channelized T3 Interfaces

Configuring T3 and E3 Interfaces

Configuring Unchannelized Ocx/Stmx Interfaces

Configuring Channelized Ocx/Stmx Interfaces

Configuring Ethernet Interfaces

Chapter 5 Configuring Ethernet Interfaces

Managing Tunnel-Service and Ipsec-Service Interfaces

Part 2 Index

Quick Links

Related Manuals for Juniper JUNOSE 11.0.X PHYSICAL LAYER

Summary of Contents for Juniper JUNOSE 11.0.X PHYSICAL LAYER