Junos

OS
Channelized STM1 Interfaces Feature Guide for
Routing Devices
Release
13.3
Published: 2014-01-13
Copyright 2014, Juniper Networks, Inc.
Juniper Networks, Inc.
1194 North Mathilda Avenue
Sunnyvale, California 94089
USA
408-745-2000
www.juniper.net
Juniper Networks, Junos, Steel-Belted Radius, NetScreen, and ScreenOS are registered trademarks of Juniper Networks, Inc. in the United
States and other countries. The Juniper Networks Logo, the Junos logo, and JunosE are trademarks of Juniper Networks, Inc. All other
trademarks, service marks, registered trademarks, or registered service marks are the property of their respective owners.
Juniper Networks assumes no responsibility for any inaccuracies in this document. Juniper Networks reserves the right to change, modify,
transfer, or otherwise revise this publication without notice.
Junos

OS Channelized STM1 Interfaces Feature Guide for Routing Devices

13.3
Copyright 2014, Juniper Networks, Inc.
All rights reserved.
The information in this document is current as of the date on the title page.
YEAR 2000 NOTICE
Juniper Networks hardware and software products are Year 2000 compliant. Junos OS has no known time-related limitations through the
year 2038. However, the NTP application is known to have some difficulty in the year 2036.
ENDUSER LICENSE AGREEMENT
The Juniper Networks product that is the subject of this technical documentation consists of (or is intended for use with) Juniper Networks
software. Use of such software is subject to the terms and conditions of the End User License Agreement (EULA) posted at
http://www.juniper.net/support/eula.html. By downloading, installing or using such software, you agree to the terms and conditions of
that EULA.
Copyright 2014, Juniper Networks, Inc. ii
Table of Contents
About the Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Documentation and Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Supported Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Using the Examples in This Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Merging a Full Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x
Merging a Snippet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x
Documentation Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
Documentation Feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii
Requesting Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii
Self-Help Online Tools and Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii
Opening a Case with JTAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiv
Part 1 Overview
Chapter 1 Channelized STM1 Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Channelized STM1 Interfaces Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Part 2 Configuration
Chapter 2 Channelized STM1 Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Configuring Channelized STM1 IQ and IQE Interfaces . . . . . . . . . . . . . . . . . . . . . . . . 7
Configuring an STM1 IQ or STM1 IQE Interface . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Configuring E1 IQand IQE Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Example: Configuring E1 IQand IQE Interfaces . . . . . . . . . . . . . . . . . . . . . . 8
Configuring Fractional E1 IQ and IQE Interfaces . . . . . . . . . . . . . . . . . . . . . . . . 8
Example: Configuring Fractional E1 Interfaces . . . . . . . . . . . . . . . . . . . . . . 9
Configuring an NxDS0 IQ Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Example: Configuring an NxDS0 IQ Interface . . . . . . . . . . . . . . . . . . . . . . 10
Example: Configuring Channelized STM1 IQand IQE Interfaces . . . . . . . . . . . . 11
Configuring Channelized STM1 Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Configuring Channelized STM1 Interface Properties . . . . . . . . . . . . . . . . . . . . . 12
Configuring Virtual Tributary Mapping of Channelized STM1 Interfaces . . . . . 14
Configuring Link PIC Failover on Channelized STM1 Interfaces . . . . . . . . . . . . . . . . 21
Example: Configuring Channelized STM1 Interfaces . . . . . . . . . . . . . . . . . . . . . . . . 21
Chapter 3 Network Interfaces Configuration Statements and Hierarchy . . . . . . . . . . . 23
[edit chassis] Hierarchy Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
[edit interfaces] Hierarchy Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
[edit logical-systems] Hierarchy Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
iii Copyright 2014, Juniper Networks, Inc.
Chapter 4 Statement Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
advertise-interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
aps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
authentication-key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
bert-error-rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
bert-period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
bytes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
e1-options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
fast-aps-switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
fcs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
force . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
framing (E1, E3, and T1 Interfaces) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
hold-time (APS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
idle-cycle-flag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
interface-type (Interfaces) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
lockout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
loopback (ADSL, DS0, E1/E3, SONET/SDH, SHDSL, and T1/T3) . . . . . . . . . . . . . 65
neighbor (Automatic Protection Switching for SONET/SDH) . . . . . . . . . . . . . . . . 66
no-partition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
no-termination-request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
paired-group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
partition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
protect-circuit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
revert-time (Interfaces) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
sonet-options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
start-end-flag . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
switching-mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
timeslots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
vtmapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
working-circuit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Part 3 Administration
Chapter 5 Monitoring Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
show interfaces (Channelized STM1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Chapter 6 Command Summaries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Channelized E1 Interface Operational Mode Commands . . . . . . . . . . . . . . . . . . . . 97
Channelized OC Interface Operational Commands . . . . . . . . . . . . . . . . . . . . . . . . 98
Channelized STM1 Interface Operational Mode Commands . . . . . . . . . . . . . . . . . 98
Channelized T1 and T3 Interface Operational Mode Commands . . . . . . . . . . . . . 99
Copyright 2014, Juniper Networks, Inc. iv
Channelized STM1 Interfaces Feature Guide for Routing Devices
Part 4 Troubleshooting
Chapter 7 Interface Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Interface Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Configuring Loopback Testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Interface Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Starting and Stopping a BERT Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Example: Configuring Bit Error Rate Testing . . . . . . . . . . . . . . . . . . . . . . 109
Part 5 Index
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
v Copyright 2014, Juniper Networks, Inc.
Table of Contents
Copyright 2014, Juniper Networks, Inc. vi
Channelized STM1 Interfaces Feature Guide for Routing Devices
List of Tables
About the Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Table 1: Notice Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
Table 2: Text and Syntax Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
Part 2 Configuration
Chapter 2 Channelized STM1 Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Table 3: Channelized STM1-to-E1 Channel Mapping . . . . . . . . . . . . . . . . . . . . . . . . 14
Table 4: Channelized STM1-to-T1 Channel Mapping . . . . . . . . . . . . . . . . . . . . . . . . 17
Part 3 Administration
Chapter 5 Monitoring Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Table 5: Channelized STM1 show interfaces Output Fields . . . . . . . . . . . . . . . . . . 82
Chapter 6 Command Summaries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Table 6: Channelized E1 Interface Operational Mode Commands . . . . . . . . . . . . . 97
Table 7: Channelized OC Interface Operational Mode Commands . . . . . . . . . . . . 98
Table 8: Channelized STM1 Interface Operational Mode Commands . . . . . . . . . . 98
Table 9: Channelized T1 and T3 Interface Operational Mode Commands . . . . . . 99
Part 4 Troubleshooting
Chapter 7 Interface Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Table 10: Loopback Modes by Interface Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Table 11: BERT Capabilities by Interface Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
vii Copyright 2014, Juniper Networks, Inc.
Copyright 2014, Juniper Networks, Inc. viii
Channelized STM1 Interfaces Feature Guide for Routing Devices
About the Documentation
Documentation and Release Notes on page ix
Supported Platforms on page ix
Using the Examples in This Manual on page ix
Documentation Conventions on page xi
Documentation Feedback on page xiii
Requesting Technical Support on page xiii
Documentation and 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/.
If the information in the latest release notes differs fromthe information in the
documentation, followthe product Release Notes.
Juniper Networks Books publishes books by Juniper Networks engineers and subject
matter experts. These books go beyond the technical documentation to explore the
nuances of network architecture, deployment, and administration. The current list can
be viewed at http://www.juniper.net/books.
Supported Platforms
For the features described in this document, the following platforms are supported:
MSeries
MX Series
T Series
J Series
Using the Examples in This Manual
If you want to use the examples in this manual, you can use the load merge or the load
merge relative command. These commands cause the software to merge the incoming
configuration into the current candidate configuration. The example does not become
active until you commit the candidate configuration.
ix Copyright 2014, Juniper Networks, Inc.
If the example configuration contains the top level of the hierarchy (or multiple
hierarchies), the example is a full example. In this case, use the load merge command.
If the example configuration does not start at the top level of the hierarchy, the example
is a snippet. In this case, use the load merge relative command. These procedures are
described in the following sections.
Merging a Full Example
To merge a full example, followthese steps:
1. Fromthe HTML or PDF version of the manual, copy a configuration example into a
text file, save the file with a name, and copy the file to a directory on your routing
platform.
For example, copy thefollowingconfigurationtoafileandnamethefileex-script.conf.
Copy the ex-script.conf file to the /var/tmp directory on your routing platform.
system{
scripts {
commit {
file ex-script.xsl;
}
}
}
interfaces {
fxp0 {
disable;
unit 0 {
family inet {
address 10.0.0.1/24;
}
}
}
}
2. Merge the contents of the file into your routing platformconfiguration by issuing the
load merge configuration mode command:
[edit]
user@host# load merge /var/tmp/ex-script.conf
load complete
Merging a Snippet
To merge a snippet, followthese steps:
1. Fromthe HTML or PDF version of the manual, copy a configuration snippet into a text
file, save the file with a name, and copy the file to a directory on your routing platform.
For example, copy the following snippet to a file and name the file
ex-script-snippet.conf. Copy the ex-script-snippet.conf file to the /var/tmp directory
on your routing platform.
commit {
file ex-script-snippet.xsl; }
Copyright 2014, Juniper Networks, Inc. x
Channelized STM1 Interfaces Feature Guide for Routing Devices
2. Move to the hierarchy level that is relevant for this snippet by issuing the following
configuration mode command:
[edit]
user@host# edit systemscripts
[edit systemscripts]
3. Merge the contents of the file into your routing platformconfiguration by issuing the
load merge relative configuration mode command:
[edit systemscripts]
user@host# load merge relative /var/tmp/ex-script-snippet.conf
load complete
For more information about the load command, see the CLI User Guide.
Documentation Conventions
Table 1 on page xi defines notice icons used in this guide.
Table 1: Notice Icons
Description Meaning Icon
Indicates important features or instructions. Informational note
Indicates a situation that might result in loss of data or hardware damage. Caution
Alerts you to the risk of personal injury or death. Warning
Alerts you to the risk of personal injury froma laser. Laser warning
Table 2 on page xi defines the text and syntax conventions used in this guide.
Table 2: Text and Syntax Conventions
Examples Description Convention
To enter configuration mode, type the
configure command:
user@host> configure
Represents text that you type. Bold text like this
user@host> showchassis alarms
No alarms currently active
Represents output that appears on the
terminal screen.
Fixed-width text like this
xi Copyright 2014, Juniper Networks, Inc.
About the Documentation
Table 2: Text and Syntax Conventions (continued)
Examples Description Convention
A policy termis a named structure
that defines match conditions and
actions.
Junos OS CLI User Guide
RFC1997, BGPCommunities Attribute
Introduces or emphasizes important
newterms.
Identifies guide names.
Identifies RFCand Internet draft titles.
Italic text like this
Configure the machines domain name:
[edit]
root@# set systemdomain-name
domain-name
Represents variables (options for which
you substitute a value) in commands or
configuration statements.
Italic text like this
To configure a stub area, include the
stub statement at the [edit protocols
ospf area area-id] hierarchy level.
Theconsoleport is labeledCONSOLE.
Represents names of configuration
statements, commands, files, and
directories; configurationhierarchy levels;
or labels on routing platform
components.
Text like this
stub <default-metric metric>; Encloses optional keywords or variables. < > (angle brackets)
broadcast | multicast
(string1 | string2 | string3)
Indicates a choice between the mutually
exclusive keywords or variables on either
side of the symbol. The set of choices is
often enclosed in parentheses for clarity.
| (pipe symbol)
rsvp { #Required for dynamic MPLS only Indicates a comment specified on the
samelineas theconfigurationstatement
to which it applies.
# (pound sign)
community name members [
community-ids ]
Encloses a variable for which you can
substitute one or more values.
[ ] (square brackets)
[edit]
routing-options {
static {
route default {
nexthop address;
retain;
}
}
}
Identifies a level in the configuration
hierarchy.
Indention and braces ( { } )
Identifies a leaf statement at a
configuration hierarchy level.
; (semicolon)
GUI Conventions
In the Logical Interfaces box, select
All Interfaces.
To cancel the configuration, click
Cancel.
Representsgraphical user interface(GUI)
items you click or select.
Bold text like this
In the configuration editor hierarchy,
select Protocols>Ospf.
Separates levels in a hierarchy of menu
selections.
> (bold right angle bracket)
Copyright 2014, Juniper Networks, Inc. xii
Channelized STM1 Interfaces Feature Guide for Routing Devices
Documentation Feedback
We encourage you to provide feedback, comments, and suggestions so that we can
improve the documentation. You can send your comments to
techpubs-comments@juniper.net, or fill out the documentation feedback format
https://www.juniper.net/cgi-bin/docbugreport/. If you are using e-mail, be sure to include
the following information with your comments:
Document or topic name
URL or page number
Software release version (if applicable)
Requesting Technical Support
Technical product support is availablethroughtheJuniper Networks Technical Assistance
Center (JTAC). If you are a customer with an active J-Care or JNASC support contract,
or are covered under warranty, and need post-sales technical support, you can access
our tools and resources online or open a case with JTAC.
JTAC policiesFor a complete understanding of our JTAC procedures and policies,
reviewthe JTAC User Guide located at
http://www.juniper.net/us/en/local/pdf/resource-guides/7100059-en.pdf.
Product warrantiesFor product warranty information, visit
http://www.juniper.net/support/warranty/.
JTAC hours of operationThe JTAC centers have resources available 24 hours a day,
7 days a week, 365 days a year.
Self-Help Online Tools and Resources
For quick and easy problemresolution, 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/
Search for known bugs: http://www2.juniper.net/kb/
Find product documentation: http://www.juniper.net/techpubs/
Find solutions and answer questions using our Knowledge Base: http://kb.juniper.net/
Download the latest versions of software and reviewrelease notes:
http://www.juniper.net/customers/csc/software/
Search technical bulletins for relevant hardware and software notifications:
https://www.juniper.net/alerts/
xiii Copyright 2014, Juniper Networks, Inc.
About the Documentation
Join and participate in the Juniper Networks Community Forum:
http://www.juniper.net/company/communities/
Open a case online in the CSC Case Management tool: http://www.juniper.net/cm/
Toverify serviceentitlement by product serial number, useour Serial Number Entitlement
(SNE) Tool: https://tools.juniper.net/SerialNumberEntitlementSearch/
Opening a Case with JTAC
You can open a case with JTAC on the Web or by telephone.
Use the Case Management tool in the CSC at http://www.juniper.net/cm/.
Call 1-888-314-JTAC (1-888-314-5822 toll-free in the USA, Canada, and Mexico).
For international or direct-dial options in countries without toll-free numbers, see
http://www.juniper.net/support/requesting-support.html.
Copyright 2014, Juniper Networks, Inc. xiv
Channelized STM1 Interfaces Feature Guide for Routing Devices
PART 1
Overview
Channelized STM1 Interfaces on page 3
1 Copyright 2014, Juniper Networks, Inc.
Copyright 2014, Juniper Networks, Inc. 2
Channelized STM1 Interfaces Feature Guide for Routing Devices
CHAPTER 1
Channelized STM1 Interfaces
Channelized STM1 Interfaces Overviewon page 3
Channelized STM1 Interfaces Overview
Each Channelized STM1 PIC and Channelized STM1 Intelligent Queuing (IQ) PIC has one
STM1 port.
For the Channelized STM1 IQor IQE PIC, you can channelize the single port to the NxDS0
level. Each E1 interface has 32 time slots (DS0), in which time slot 0 is reserved.
You can combine one or more of these DS0 time slots (channels) to create a channel
group (NxDS0).
Related
Documentation
Configuring Channelized STM1 Interfaces on page 12
3 Copyright 2014, Juniper Networks, Inc.
Copyright 2014, Juniper Networks, Inc. 4
Channelized STM1 Interfaces Feature Guide for Routing Devices
PART 2
Configuration
Channelized STM1 Interfaces on page 7
Network Interfaces Configuration Statements and Hierarchy on page 23
Statement Summary on page 47
5 Copyright 2014, Juniper Networks, Inc.
Copyright 2014, Juniper Networks, Inc. 6
Channelized STM1 Interfaces Feature Guide for Routing Devices
CHAPTER 2
Channelized STM1 Interfaces
Configuring Channelized STM1 IQand IQE Interfaces on page 7
Configuring Channelized STM1 Interfaces on page 12
Configuring Link PIC Failover on Channelized STM1 Interfaces on page 21
Example: Configuring Channelized STM1 Interfaces on page 21
Configuring Channelized STM1 IQand IQE Interfaces
This section includes the following topics:
Configuring an STM1 IQor STM1 IQE Interface on page 7
Configuring E1 IQand IQE Interfaces on page 7
Configuring Fractional E1 IQand IQE Interfaces on page 8
Configuring an NxDS0 IQInterface on page 9
Example: Configuring Channelized STM1 IQand IQE Interfaces on page 11
Configuring an STM1 IQor STM1 IQE Interface
Onaone-port ChannelizedSTM1 IQPIC, or eachindividual port of the4-port Channelized
STM1 IQE PIC, you can configure one SDH STM1 interface. To configure an SDH STM1
interface, include the no-partition interface-type statement at the [edit interfaces
cstm1-fpc/pic/port] hierarchy level, specifying the so interface type:
[edit interfaces cstm1-fpc/pic/port]
no-partition interface-type so;
This configuration creates interface so-fpc/pic/port.
NOTE: Class-of-service(CoS)rulescannot beappliedtoanindividual channel
configured on channelized IQand IQE interfaces. You can only apply CoS
rules to the aggregate bit streams.
Configuring E1 IQand IQE Interfaces
To configure an E1 interface on a Channelized STM1 IQor IQE PIC, performthe following
tasks:
7 Copyright 2014, Juniper Networks, Inc.
1. Include the no-partition and interface-type statements at the [edit interfaces
cstm1-fpc/pic/port] hierarchy level, specifying the cau4 interface type. This converts
the channelized STM1 interface into a channelized AU-4 interface. The resulting
interface name is cau4-fpc/pic/port:
[edit interfaces cstm1-fpc/pic/port]
no-partition interface-type cau4;
2. Partition the channelized AU-4 interface into E1 interfaces by including the partition
and interface-type statements at the [edit interfaces cau4-fpc/pic/port] hierarchy
level, specifying the e1 interface type. This configuration creates interface
e1-fpc/pic/port:channel. The partition number is the sublevel interface partition index
andis correlatedwith the channel number. For channelizedE1 interfaces, the partition
number can be from1 through 63. The interface type is the channelized interface type
or clear channel you are creating. For channelized AU-4 interfaces, type can be ce1 or
e1.
[edit interfaces cau4-fpc/pic/port]
partition partition-number interface-type e1;
NOTE: Class-of-service(CoS)rulescannot beappliedtoanindividual channel
configured on channelized IQor IQE interfaces. You can only apply CoS rules
to the aggregate bit streams.
NOTE: For channelized STM1 interfaces, channel numbering begins with 0
(:0). For channelized STM1 IQand IQE interfaces, channel numbering begins
with 1 (:1).
Example: Configuring E1 IQand IQE Interfaces
Configure the following five E1 interfaces:
e1-0/0/0:1
e1-0/0/0:2
e1-0/0/0:3
e1-0/0/0:4
e1-0/0/0:5
[edit interfaces cstm1-0/0/0]
no-partition interface-type cau4;
[edit interfaces cau4-0/0/0]
partition 1-5 interface-type e1;
For a full configuration example, see the Junos OS Feature Guides.
Configuring Fractional E1 IQand IQE Interfaces
By default, all the time slots on a channelized E1 interface are used. To configure a
fractional E1 interface on a Channelized STM1 IQor IQE PIC, performthe following tasks:
Copyright 2014, Juniper Networks, Inc. 8
Channelized STM1 Interfaces Feature Guide for Routing Devices
1. Include the no-partition and interface-type statements at the [edit interfaces
cstm1-fpc/pic/port] hierarchy level, specifying the cau4 interface type. This converts
the channelized STM1 interface into a channelized AU-4 interface. The resulting
interface name is cau4-fpc/pic/port:
[edit interfaces cstm1-fpc/pic/port]
no-partition interface-type cau4;
2. Partition the channelized AU-4 interface into E1 interfaces by including the partition
and interface-type statements at the [edit interfaces cau4-fpc/pic/port] hierarchy
level, specifying the e1 interface type. The partition number is the sublevel interface
partitionindexandis correlatedwiththechannel number. For channelizedE1 interfaces,
the partition number can be from1 through 63. The interface type is the channelized
interface type or clear channel you are creating. For channelized AU-4 interfaces, type
can be ce1 or e1. This configuration creates interface e1-fpc/pic/port:channel:
[edit interfaces cau4-fpc/pic/port]
partition partition-number interface-type e1;
3. Configure the number of time slots allocated to the E1 IQor IQE interface by including
the timeslots statement at the [edit interfaces e1-fpc/pic/port:channel e1-options]
hierarchy level. NxDS0 time slots configured on either a channelized STM1 IQor IQE
interfaceor channelizedE1 IQor IQEinterfacearenumberedfrom1 to31 (0is reserved),
while fractional E1 time slots range from2 to 32 (1 is reserved). To configure ranges,
use hyphens. To configure discontinuous time slots, use commas. Do not include
spaces.
[edit interfaces e1-fpc/pic/port:channel e1-options]
timeslots time-slot-range;
NOTE: For channelized STM1 interfaces, channel numbering begins with 0
(:0). For channelized STM1 IQor IQE interfaces, channel numbering begins
with 1 (:1).
For more information about E1 time slots, see Configuring Fractional E1 Time Slots.
Example: Configuring Fractional E1 Interfaces
Configure a fractional E1 interface that uses time slots 2 through 10:
[edit interfaces cstm1-0/0/0]
no-partition cau4;
[edit interfaces cau4-0/0/0]
partition 1 interface-type e1;
[edit interfaces e1-0/0/0 e1-options]
timeslots 2-10;
For a full configuration example, see the Junos OS Feature Guides.
Configuring an NxDS0IQInterface
By default, all the time slots on a channelized STM1 interface are used. To configure an
NxDS0 IQinterface on a Channelized STM1 IQor IQE PIC, performthe following tasks:
9 Copyright 2014, Juniper Networks, Inc.
Chapter 2: Channelized STM1 Interfaces
1. Include the no-partition and interface-type statements at the [edit interfaces
cstm1-fpc/pic/port] hierarchy level, specifying the cau4 interface type. This converts
the channelized STM1 interface into a channelized AU-4 interface. The resulting
interface name is cau4-fpc/pic/port:
[edit interfaces cstm1-fpc/pic/port]
no-partition interface-type cau4;
2. Partition the channelized AU-4 interface into E1 interfaces by including the partition
and interface-type statements at the [edit interfaces cau4-fpc/pic/port] hierarchy
level, specifying the ce1 interface type. This configuration creates interface
ce1-fpc/pic/port:channel. Thepartitionnumber is thesublevel interfacepartitionindex
andis correlatedwith the channel number. For channelizedE1 interfaces, the partition
number can be from1 through 63. The interface type is the channelized interface type
or clear channel you are creating. For channelized AU-4 interfaces, type can be ce1 or
e1:
[edit interfaces cau4-fpc/pic/port]
partition partition-number interface-type ce1;
3. Configure the number of time slots allocated to the NxDS0 IQinterface by including
the partition, timeslots, and interface-type statements at the [edit interfaces
e1-fpc/pic/port:channel] hierarchylevel, specifyingthedsinterfacetype. For channelized
E1 IQinterfaces, the partition number range is from1 through 31. For E1 IQinterfaces
(e1-fpc/pic/port), the time-slot range is from2 through 31. For channelized E1 IQ
interfaces (ce1-fpc/pic/port), thetime-slot rangeis from1 through31. Youcandesignate
any combination of time slots. To configure ranges, use hyphens. To configure
discontinuous time slots, use commas. Do not include spaces:
[edit interfaces ce1-fpc/pic/port:channel]
partition partition-number timeslots time-slot-range interface-type ds;
NOTE: Class-of-service(CoS)rulescannot beappliedtoanindividual channel
configured on channelized IQand IQE interfaces. You can only apply CoS
rules to the aggregate bit streams.
NOTE: For channelized STM1 interfaces, channel numbering begins with 0
(:0). For channelized STM1 IQand IQE interfaces, channel numbering begins
with 1 (:1).
For more information about E1 time slots, see Configuring Fractional E1 Time Slots.
Example: Configuring an NxDS0IQInterface
ConfigureanNxDS0interfacethat uses timeslots 1 through10. This configurationcreates
the ds-0/0/0:1:1 interface.
[edit interfaces cstm1-0/0/0]
no-partition interface-type cau4;
[edit interfaces cau4-0/0/0]
Copyright 2014, Juniper Networks, Inc. 10
Channelized STM1 Interfaces Feature Guide for Routing Devices
partition 1 interface-type ce1;
[edit interfaces ce1-0/0/0:1]
partition 1 timeslots 1-10 interface-type ds;
For a full configuration example, see the Junos OS Feature Guides.
Example: Configuring Channelized STM1 IQand IQE Interfaces
Configure STM1, E1, fractional E1, and NxDS0 interfaces:
STM1 Interface [edit interfaces]
cstm1-0/0/0 {
no-partition interface-type so;
}
so-0/0/0 {
unit 0 {
family inet {
address 10.10.12.1/30;
}
}
}
E1 Interface [edit interfaces]
cstm1-1/1/0 {
no-partition interface-type cau4;
}
[edit interfaces]
cau4-1/1/0 {
partition 1-63 interface-type e1;
}
[edit interfaces]
e1-1/1/0:1 {
unit 0 {
family inet {
address 10.10.10.1/30;
}
}
}
...
Fractional E1 Interface [edit interfaces]
cstm1-1/0/0 {
no-partition interface-type cau4;
}
[edit interfaces]
cau4-1/0/0 {
partition 1-63 interface-type e1;
}
[edit interfaces]
e1-1/1/0:1 {
e1-options {
timeslots 2-10;
}
unit 0 {
family inet {
address 10.10.10.1/30;
11 Copyright 2014, Juniper Networks, Inc.
Chapter 2: Channelized STM1 Interfaces
}
}
}
...
DS0Interface [edit interfaces]
cstm1-2/0/0 {
no-partition interface-type cau4;
}
[edit interfaces]
cau4-2/0/0 {
partition 1-10 interface-type ce1;
}
[edit interfaces]
ce1-2/0/0:1 {
partition 1 interface-type ds timeslots 2-10;
[edit interfaces]
ds-2/0/0:1:1 {
unit 0 {
family inet {
address 10.12.12.1/30;
}
}
}
...
}
For a full configuration example, see the Junos OS Feature Guides.
Configuring Channelized STM1 Interfaces
To specify the channel number, include it after the colon (:) in the interface name. For
example, aChannelizedSTM1-to-E1 PICinFPC1 andslot 1 will havethefollowingphysical
interface, depending on the media type:
e1-1/1/0:x
The E1 channel number can be from0 through 62.
This section contains the following topics:
Configuring Channelized STM1 Interface Properties on page 12
Configuring Virtual Tributary Mapping of Channelized STM1 Interfaces on page 14
Configuring Channelized STM1 Interface Properties
To configure the interface properties for Channelized STM1-to-E1 PICs, include the
e1-options and sonet-options statements for both sides of the connection. The following
configurations list all the valid statements.
Tospecify options for eachof theE1 channels ontheChannelizedSTM1-to-E1 PIC, include
the e1-options statement at the [edit interfaces interface-name] hierarchy level:
[edit interfaces interface-name]
e1-options {
Copyright 2014, Juniper Networks, Inc. 12
Channelized STM1 Interfaces Feature Guide for Routing Devices
bert-error-rate;
bert-period;
fcs (16 | 32);
framing (g704 | g704-no-crc4 | unframed);
idle-cycle-flag (flags | ones);
loopback (local | remote);
start-end-flag (filler | shared);
timeslots time-slot-number;
}
NOTE: When a channelized STM1 interface experiences a line transition, the
E1 channelsconfiguredinunframedmodelogalargenumber of drops(around
24,000) as the channelized STM1 interface clocks resynchronize. This does
not occur on framed channels, because the framing resynchronizes clocks
very quickly.
To specify options for the SONET/SDHside of the connection, include the sonet-options
statement at the [edit interfaces interface-name] hierarchy level:
[edit interfaces interface-name]
sonet-options {
aps {
advertise-interval milliseconds;
authentication-key key;
force;
hold-time milliseconds;
lockout;
neighbor address;
paired-group group-name;
protect-circuit group-name;
request;
revert-time seconds;
switching-mode (bidirectional | unidirectional);
working-circuit group-name;
}
bytes {
e1-quiet value;
f1 value;
f2 value;
s1 value;
z3 value;
z4 value;
}
loopback (local | remote);
}
NOTE: OnchannelizedSTM1 interfaces, youshouldconfiguretheclocksource
ononesideof theconnectiontobeinternal (thedefault Junos configuration)
and on the other side of the connection to be external.
13 Copyright 2014, Juniper Networks, Inc.
Chapter 2: Channelized STM1 Interfaces
For information about Frame Relay DLCI limitations for channelized interfaces, see
Data-Link Connection Identifiers on Channelized Interfaces. For more information about
FrameRelay DLCIs, seeConfiguringFrameRelay DLCIs. For informationabout DLCI sparse
mode, see the Junos OS Administration Library for Routing Devices.
For more information about specific statements, see E1 Interfaces Overview, SONET/SDH
Interfaces Overview, andT1 Interfaces Overview. For aconfigurationexample, seeExample:
Configuring Channelized STM1 Interfaces on page 21.
Configuring Virtual Tributary Mapping of Channelized STM1 Interfaces
Youcanconfigurevirtual tributary mappingtouseKLMmodeor ITU-Tmode. Toconfigure
virtual tributary mapping, include the vtmapping statement at the [edit chassis fpc
slot-number pic pic-number] hierarchy level:
[edit chassis fpc slot-number pic pic-number]
vtmapping (klm| itu-t);
By default, virtual tributary mappinguses KLMmode. For moreinformation, seetheJunos
OS Administration Library for Routing Devices.
For the Channelized STM1 IQand IQE PICs, you can configure virtual tributary mapping
by including the vtmapping statement at the [edit interfaces cau4-fpc/pic/port
sonet-options] hierarchy level:
[edit interfaces cau4-fpc/pic/port sonet-options]
vtmapping (klm| itu-t);
Table 3 on page 14 lists the KLMmappings used by the channelized STM1-to-E1 PIC
interfaces. The PIC defaults to KLMnumbering with an offset of 1; for example, KLM1=
STM1 PIC 0.
Table 3: Channelized STM1-to-E1 Channel Mapping
ITU-T
Number
Virtual
Tributary
Tributary
Unit Group 2
Tributary
Unit Group 3 KLMNumber
Channel
Number
1 1 1 1 1 0
22 2 1 1 2 1
43 3 1 1 3 2
4 1 2 1 4 3
25 2 2 1 5 4
46 3 2 1 6 5
7 1 3 1 7 6
28 2 3 1 8 7
49 3 3 1 9 8
Copyright 2014, Juniper Networks, Inc. 14
Channelized STM1 Interfaces Feature Guide for Routing Devices
Table 3: Channelized STM1-to-E1 Channel Mapping (continued)
ITU-T
Number
Virtual
Tributary
Tributary
Unit Group 2
Tributary
Unit Group 3 KLMNumber
Channel
Number
10 1 4 1 10 9
31 2 4 1 11 10
52 3 4 1 12 11
13 1 5 1 13 12
34 2 5 1 14 13
55 3 5 1 15 14
16 1 6 1 16 15
37 2 6 1 17 16
58 3 6 1 18 17
19 1 7 1 19 18
40 2 7 1 20 19
61 3 7 1 21 20
2 1 1 2 22 21
23 2 1 2 23 22
44 3 1 2 24 23
5 1 2 2 25 24
26 2 2 2 26 25
47 3 2 2 27 26
8 1 3 2 28 27
29 2 3 2 29 28
50 3 3 2 30 29
11 1 4 2 31 30
32 2 4 2 32 31
15 Copyright 2014, Juniper Networks, Inc.
Chapter 2: Channelized STM1 Interfaces
Table 3: Channelized STM1-to-E1 Channel Mapping (continued)
ITU-T
Number
Virtual
Tributary
Tributary
Unit Group 2
Tributary
Unit Group 3 KLMNumber
Channel
Number
53 3 4 2 33 32
14 1 5 2 34 33
35 2 5 2 35 34
56 3 5 2 36 35
17 1 6 2 37 36
38 2 6 2 38 37
59 3 6 2 39 38
20 1 7 2 40 39
41 2 7 2 41 40
62 3 7 2 42 41
3 1 1 3 43 42
24 2 1 3 44 43
45 3 1 3 45 44
6 1 2 3 46 45
27 2 2 3 47 46
48 3 2 3 48 47
9 1 3 3 49 48
30 2 3 3 50 49
51 3 3 3 51 50
12 1 4 3 52 51
33 2 4 3 53 52
54 3 4 3 54 53
15 1 5 3 55 54
Copyright 2014, Juniper Networks, Inc. 16
Channelized STM1 Interfaces Feature Guide for Routing Devices
Table 3: Channelized STM1-to-E1 Channel Mapping (continued)
ITU-T
Number
Virtual
Tributary
Tributary
Unit Group 2
Tributary
Unit Group 3 KLMNumber
Channel
Number
36 2 5 3 56 55
57 3 5 3 57 56
18 1 6 3 58 57
39 2 6 3 59 58
60 3 6 3 60 59
21 1 7 3 61 60
42 2 7 3 62 61
63 3 7 3 63 62
Table 4 on page 17 lists the KLMmappings used by the channelized STM1-to-T1 PIC
interfaces. The PIC defaults to KLMnumbering with an offset of 1; for example, KLM1=
STM1 PIC 0.
Table 4: Channelized STM1-to-T1 Channel Mapping
ITU-T
Number
Virtual
Tributary
Tributary
Unit Group 2
Tributary
Unit Group 3 KLMNumber
Channel
Number
1 1 1 1 1 0
22 2 1 1 2 1
43 3 1 1 3 2
4 1 2 1 4 3
25 2 2 1 5 4
46 3 2 1 6 5
7 1 3 1 7 6
28 2 3 1 8 7
49 3 3 1 9 8
10 1 4 1 10 9
31 2 4 1 11 10
17 Copyright 2014, Juniper Networks, Inc.
Chapter 2: Channelized STM1 Interfaces
Table 4: Channelized STM1-to-T1 Channel Mapping (continued)
ITU-T
Number
Virtual
Tributary
Tributary
Unit Group 2
Tributary
Unit Group 3 KLMNumber
Channel
Number
52 3 4 1 12 11
13 1 5 1 13 12
34 2 5 1 14 13
55 3 5 1 15 14
16 1 6 1 16 15
37 2 6 1 17 16
58 3 6 1 18 17
19 1 7 1 19 18
40 2 7 1 20 19
61 3 7 1 21 20
2 1 1 2 22 21
23 2 1 2 23 22
44 3 1 2 24 23
5 1 2 2 25 24
26 2 2 2 26 25
47 3 2 2 27 26
8 1 3 2 28 27
29 2 3 2 29 28
50 3 3 2 30 29
11 1 4 2 31 30
32 2 4 2 32 31
53 3 4 2 33 32
14 1 5 2 34 33
Copyright 2014, Juniper Networks, Inc. 18
Channelized STM1 Interfaces Feature Guide for Routing Devices
Table 4: Channelized STM1-to-T1 Channel Mapping (continued)
ITU-T
Number
Virtual
Tributary
Tributary
Unit Group 2
Tributary
Unit Group 3 KLMNumber
Channel
Number
35 2 5 2 35 34
56 3 5 2 36 35
17 1 6 2 37 36
38 2 6 2 38 37
59 3 6 2 39 38
20 1 7 2 40 39
41 2 7 2 41 40
62 3 7 2 42 41
3 1 1 3 43 42
24 2 1 3 44 43
45 3 1 3 45 44
6 1 2 3 46 45
27 2 2 3 47 46
48 3 2 3 48 47
9 1 3 3 49 48
30 2 3 3 50 49
51 3 3 3 51 50
12 1 4 3 52 51
33 2 4 3 53 52
54 3 4 3 54 53
15 1 5 3 55 54
36 2 5 3 56 55
57 3 5 3 57 56
19 Copyright 2014, Juniper Networks, Inc.
Chapter 2: Channelized STM1 Interfaces
Table 4: Channelized STM1-to-T1 Channel Mapping (continued)
ITU-T
Number
Virtual
Tributary
Tributary
Unit Group 2
Tributary
Unit Group 3 KLMNumber
Channel
Number
18 1 6 3 58 57
39 2 6 3 59 58
60 3 6 3 60 59
21 1 7 3 61 60
42 2 7 3 62 61
63 3 7 3 63 62
24 1 1 4 64 63
45 2 1 4 65 64
66 3 1 4 66 65
27 1 2 4 67 66
48 2 2 4 68 67
69 3 2 4 69 68
30 1 3 4 70 69
51 2 3 4 71 70
72 3 3 4 72 71
33 1 4 4 73 72
54 2 4 4 74 73
75 3 4 4 75 74
36 1 5 4 76 75
57 2 5 4 77 76
78 3 5 4 78 77
39 1 6 4 79 78
60 2 6 4 80 79
Copyright 2014, Juniper Networks, Inc. 20
Channelized STM1 Interfaces Feature Guide for Routing Devices
Table 4: Channelized STM1-to-T1 Channel Mapping (continued)
ITU-T
Number
Virtual
Tributary
Tributary
Unit Group 2
Tributary
Unit Group 3 KLMNumber
Channel
Number
81 3 6 4 81 80
42 1 7 4 82 81
63 2 7 4 83 82
84 3 7 4 84 83
Configuring Link PIC Failover on Channelized STM1 Interfaces
For Channelized STM1 IQand IQE PICs used as linking PICs in redundant LSQ
configurations, youcaninhibit therouter fromsendingPPPtermination-request messages
to the remote host if the link PIC fails. To do this, include the no-termination-request
statement at the [edit interfaces interface-name ppp-options] hierarchy level:
no-termination-request;
The no-termination-request statement is supported only with MLPPP and SONET APS
configurations and works with PPP, PPP over Frame Relay, and MLPPP interfaces only.
For informationabout interchassis andintrachassis LSQfailover, seetheJunos OSServices
Interfaces Library for Routing Devices.
Example: Configuring Channelized STM1 Interfaces
The following configuration is sufficient to get the Channelized STM1-to-E1 PIC interface
up and running. The channelized STM1-to-E1 interface is an STM1 that is divided into
63 E1 interfaces. E1 interfaces can use the following encapsulation types:
PPP, PPP CCC, and PPP TCC
Frame Relay, Frame Relay CCC, and Frame Relay TCC
Cisco HDLC, Cisco HDLC CCC, and Cisco HDLC TCC
The channels can also have logical interfaces. For information about Frame Relay DLCI
limitations for channelizedinterfaces, seeData-Link ConnectionIdentifiers onChannelized
Interfaces. For more information about Frame Relay DLCIs, see Configuring Frame Relay
DLCIs. For more information about DLCI sparse mode, see the Junos OS Administration
Library for Routing Devices.
You apply all STM1 interface SONET/SDH options to the first E1 interface in the
configuration by including the sonet-options statement at the [edit interfaces
e1-fpc/pic/port:channel] hierarchy level:
[edit]
interfaces {
e1-0/0/1:0 {
21 Copyright 2014, Juniper Networks, Inc.
Chapter 2: Channelized STM1 Interfaces
encapsulation cisco-hdlc;
sonet-options {
no-z0-increment;
}
e1-options {
framing g704;
}
unit 0 {
family inet {
address 10.11.30.1/30;
}
}
}
e1-0/0/1:1 {
encapsulation frame-relay;
e1-options {
framing g704;
}
unit 1 {
dlci 16;
family inet {
address 10.11.31.9/30;
}
}
}
e1-0/0/1:2 {
encapsulation ppp;
no-keepalives;
unit 0 {
family inet {
address 10.11.31.47/30;
}
}
}
}
[edit]
chassis {
fpc 2 {
pic 0 {
vtmapping klm;
}
}
}
Copyright 2014, Juniper Networks, Inc. 22
Channelized STM1 Interfaces Feature Guide for Routing Devices
CHAPTER 3
Network Interfaces Configuration
Statements and Hierarchy
[edit chassis] Hierarchy Level on page 23
[edit interfaces] Hierarchy Level on page 24
[edit logical-systems] Hierarchy Level on page 40
[edit chassis] Hierarchy Level
chassis {
aggregated-devices {
ethernet {
device-count number;
}
sonet {
device-count number;
}
}
maximum-links {
}
channel-group number {
ethernet {
device-count number;
}
fpc slot-number{
pic pic-number {
adaptive-services{
service-package (layer-2 | layer-3);
}
aggregate-ports;
atm-cell-relay-accumulation;
atm-l2circuit-mode (aal5 | cell | trunk trunk);
ce1 {
e1 link-number {
channel-group group-number;
timeslots time-slot-range;
}
}
channelization;
ct1 {
t1 link-number {
23 Copyright 2014, Juniper Networks, Inc.
channel-group group-number;
timeslots time-slot-range;
}
}
ct3 {
port port-number {
t1 link-number {
channel-group group-number;
timeslots time-slot-range;
}
}
framing sdh;
}
max-queues-per-interface number;
mlfr-uni-nni-bundles num-intf;
no-concatenate;
shdsl {
pic-mode (1-port-atm| 2-port-atm);
}
vtmapping (klm| itu-t);
}
}
fpc slot-number{
pic pic-number{
account-layer2-overhead
egress-policer-overhead bytes;
ingress-policer-overhead bytes;
}
}
}
[edit interfaces] Hierarchy Level
The statements at the [edit interfaces interface-name unit logical-unit-number] hierarchy
level can also be configured at the [edit logical-systems logical-system-name interfaces
interface-name unit logical-unit-number] hierarchy level.
NOTE: The accounting-profile statement is an exception to this rule. The
accounting-profile statement can be configured at the [edit interfaces
interface-name unit logical-unit-number] hierarchy level, but it cannot be
configured at the [edit logical-systems logical-system-name interfaces
interface-name unit logical-unit-number] hierarchy level.
interfaces {
traceoptions {
filefilename <files number><matchregular-expression><sizesize><world-readable|
no-world-readable> ;
flag flag <disable>;
}
interface-name {
accounting-profile name;
aggregated-ether-options {
Copyright 2014, Juniper Networks, Inc. 24
Channelized STM1 Interfaces Feature Guide for Routing Devices
(flow-control | no-flow-control);
lacp {
(active | passive);
link-protection {
disable;
(revertive | non-revertive);
periodic interval;
system-priority priority;
}
link-protection;
link-speed speed;
(loopback | no-loopback);
mc-ae{
chassis-id chassis-id;
mc-ae-id mc-ae-id;
mode (active-active | active-standby);
redundancy-group group-id;
status-control (active | standby);
}
minimum-links number;
source-address-filter {
mac-address;
}
(source-filtering | no-source-filtering);
}
shared-scheduler;
aggregated-sonet-options {
link-speed speed | mixed;
minimum-links number;
}
atm-options {
cell-bundle-size cells;
ilmi;
linear-red-profiles profile-name {
high-plp-max-threshold percent;
low-plp-max-threshold percent;
queue-depth cells high-plp-threshold percent low-plp-threshold percent;
}
mpls {
pop-all-labels {
required-depth number;
}
}
pic-type (atm1 | atm2);
plp-to-clp;
promiscuous-mode {
vpi vpi-identifier;
}
scheduler-maps map-name {
forwarding-class class-name {
epd-threshold cells plp1 cells;
linear-red-profile profile-name;
priority (high | low);
transmit-weight (cells number | percent number);
}
vc-cos-mode (alternate | strict);
25 Copyright 2014, Juniper Networks, Inc.
Chapter 3: Network Interfaces Configuration Statements and Hierarchy
}
use-null-cw;
vpi vpi-identifier {
maximum-vcs maximum-vcs;
oam-liveness {
down-count cells;
up-count cells;
}
oam-period (seconds | disable);
shaping {
(cbr rate| rtvbr peak ratesustainedrateburst length| vbr peak ratesustainedrate
burst length);
queue-length number;
}
}
}
clocking clock-source;
data-input (system| interface interface-name);
dce;
serial-options {
clock-rate rate;
clocking-mode (dce | internal | loop);
control-polarity (negative | positive);
cts-polarity (negative | positive);
dcd-polarity (negative | positive);
dce-options {
control-signal (assert | de-assert | normal);
cts (ignore | normal | require);
dcd (ignore | normal | require);
dsr (ignore | normal | require);
dtr signal-handling-option;
ignore-all;
indication (ignore | normal | require);
rts (assert | de-assert | normal);
tm(ignore | normal | require);
}
dsr-polarity (negative | positive);
dte-options {
control-signal (assert | de-assert | normal);
cts (ignore | normal | require);
dcd (ignore | normal | require);
dsr (ignore | normal | require);
dtr signal-handling-option;
ignore-all;
indication (ignore | normal | require);
rts (assert | de-assert | normal);
tm(ignore | normal | require);
}
dtr-circuit (balanced | unbalanced);
dtr-polarity (negative | positive);
encoding (nrz | nrzi);
indication-polarity (negative | positive);
line-protocol protocol;
loopback mode;
rts-polarity (negative | positive);
tm-polarity (negative | positive);
Copyright 2014, Juniper Networks, Inc. 26
Channelized STM1 Interfaces Feature Guide for Routing Devices
transmit-clock invert;
}
description text;
alias alias-name;
dialer-options {
pool pool-name <priority priority>;
}
disable;
ds0-options {
bert-algorithmalgorithm;
bert-error-rate rate;
bert-period seconds;
byte-encoding (nx56 | nx64);
fcs (16 | 32);
idle-cycle-flag (flags | ones);
invert-data;
loopback payload;
start-end-flag (filler | shared);
}
e1-options {
bert-error-rate rate;
bert-period seconds;
fcs (16 | 32);
framing (g704 | g704-no-crc4 | unframed);
idle-cycle-flag (flags | ones);
invert-data;
loopback (local | remote);
start-end-flag (filler | shared);
timeslots time-slot-range;
}
e3-options {
atm-encapsulation (direct | plcp);
bert-algorithmalgorithm;
bert-error-rate rate;
bert-period seconds;
framing feet;
compatibility-mode (digital-link | kentrox | larscom) <subrate value>;
fcs (16 | 32);
framing (g.751 | g.832);
idle-cycle-flag (filler | shared);
invert-data;
loopback (local | remote);
(payload-scrambler | no-payload-scrambler);
start-end-flag (filler | shared);
(unframed | no-unframed);
}
encapsulation type;
es-options {
backup-interface es-fpc/pic/port;
}
fastether-options {
802.3ad aex;
(flow-control | no-flow-control);
ignore-l3-incompletes;
ingress-rate-limit rate;
(loopback | no-loopback);
27 Copyright 2014, Juniper Networks, Inc.
Chapter 3: Network Interfaces Configuration Statements and Hierarchy
mpls {
pop-all-labels {
required-depth number;
}
}
source-address-filter {
mac-address;
}
(source-filtering | no-source-filtering);
}
flexible-vlan-tagging;
gigether-options {
802.3ad aex;
(asynchronous-notification | no-asynchronous-notification);
(auto-negotiation | no-auto-negotiation) remote-fault <local-interface-online |
local-interface-offline>;
auto-reconnect seconds;
(flow-control | no-flow-control);
ignore-l3-incompletes;
(loopback | no-loopback);
mpls {
pop-all-labels {
required-depth number;
}
}
no-auto-mdix;
source-address-filter {
mac-address;
}
(source-filtering | no-source-filtering);
ethernet-switch-profile {
(mac-learn-enable | no-mac-learn-enable);
tag-protocol-id [ tpids ];
ethernet-policer-profile {
input-priority-map {
ieee802.1p premium[ values ];
}
output-priority-map {
classifier {
premium{
forwarding-class class-name {
loss-priority (high | low);
}
}
}
}
policer cos-policer-name {
aggregate {
bandwidth-limit bps;
burst-size-limit bytes;
}
premium{
bandwidth-limit bps;
burst-size-limit bytes;
}
}
Copyright 2014, Juniper Networks, Inc. 28
Channelized STM1 Interfaces Feature Guide for Routing Devices
}
}
}
(gratuitous-arp-reply | no-gratuitous-arp-reply);
hold-time up milliseconds down milliseconds;
ima-group-options {
differential-delay number;
frame-length (32 | 64 | 128 | 256);
frame-synchronization {
alpha number;
beta number;
gamma number;
}
minimum-links number;
symmetry (symmetrical-config-and-operation |
symmetrical-config-asymmetrical-operation);
test-procedure {
ima-test-start;
ima-test-stop;
interface name;
pattern number;
period number;
}
transmit-clock (common | independent);
version (1.0 |1.1);
}
ima-link-options group-id group-id;
interface-set interface-set-name {
interface ethernet-interface-name {
(unit unit-number | vlan-tags-outer vlan-tag);
}
interface interface-name {
(unit unit-number);
}
}
isdn-options {
bchannel-allocation (ascending | descending);
calling-number number;
pool pool-name <priority priority>;
spid1 spid-string;
spid2 spid-string;
static-tei-val value;
switch-type (att5e | etsi | ni1 | ntdms100 | ntt);
t310 seconds;
tei-option (first-call | power-up);
}
keepalives <down-count number> <interval seconds> <up-count number>;
link-mode mode;
lmi {
lmi-type (ansi | itu | c-lmi);
n391dte number;
n392dce number;
n392dte number;
n393dce number;
n393dte number;
t391dte seconds;
29 Copyright 2014, Juniper Networks, Inc.
Chapter 3: Network Interfaces Configuration Statements and Hierarchy
t392dce seconds;
}
lsq-failure-options {
no-termination-request;
[ trigger-link-failure interface-name ];
}
mac mac-address;
mlfr-uni-nni-bundle-options {
acknowledge-retries number;
acknowledge-timer milliseconds;
action-red-differential-delay (disable-tx | remove-link);
drop-timeout milliseconds;
fragment-threshold bytes;
cisco-interoperability send-lip-remove-link-for-link-reject;
hello-timer milliseconds;
link-layer-overhead percent;
lmi-type (ansi | itu | c-lmi);
minimum-links number;
mrru bytes;
n391 number;
n392 number;
n393 number;
red-differential-delay milliseconds;
t391 seconds;
t392 seconds;
yellow-differential-delay milliseconds;
}
modem-options {
dialin (console | routable);
init-command-string initialization-command-string;
}
mtu bytes;
multi-chassis-protection {
peer a.b.c.d {
interfaceinterface-name;
}
}
multiservice-options {
(core-dump | no-core-dump);
(syslog | no-syslog);
}
native-vlan-id number;
no-gratuitous-arp-request;
no-keepalives;
no-partition {
interface-type type;
}
no-vpivci-swapping;
otn-options {
fec (efec | gfec | none);
(laser-enable | no-laser-enable);
(line-loopback | no-line-loopback);
pass-thru;
rate (fixed-stuff-bytes | no-fixed-stuff-bytes | pass-thru);
transmit-payload-type number;
Copyright 2014, Juniper Networks, Inc. 30
Channelized STM1 Interfaces Feature Guide for Routing Devices
trigger (oc-lof | oc-lom| oc-los | oc-wavelength-lock | odu-ais | odu-bbe-th| odu-bdi
| odu-es-th | odu-lck | odu-oci | odu-sd | odu-ses-th | odu-ttim| odu-uas-th |
opu-ptm| otu-ais | otu-bbe-th | otu-bdi | otu-es-th | otu-fec-deg | otu-fec-exe |
otu-iae | otu-sd | otu-ses-th | otu-ttim| otu-uas-th);
tti;
}
optics-options {
wavelength nm;
alarmalarm-name {
(syslog | link-down);
}
warning warning-name {
(syslog | link-down);
}
}
partition partition-number oc-slice oc-slice-range interface-type type;
timeslots time-slot-range;
passive-monitor-mode;
per-unit-scheduler;
ppp-options {
chap {
access-profile name;
default-chap-secret name;
local-name name;
passive;
}
compression {
acfc;
pfc;
}
dynamic-profile profile-name;
no-termination-request;
pap {
access-profile name;
local-name name;
local-password password;
compression;
}
}
psn-vcipsn-vci-identifier;
psn-vpipsn-vpi-identifier;
receive-bucket {
overflow(discard | tag);
rate percentage;
threshold bytes;
}
redundancy-options {
priority sp-fpc/pic/port;
secondary sp-fpc/pic/port;
hot-standby;
}
satop-options {
payload-size n;
}
schedulers number;
serial-options {
31 Copyright 2014, Juniper Networks, Inc.
Chapter 3: Network Interfaces Configuration Statements and Hierarchy
clock-rate rate;
clocking-mode (dce | internal | loop);
control-polarity (negative | positive);
cts-polarity (negative | positive);
dcd-polarity (negative | positive);
dce-options {
control-signal (assert | de-assert | normal);
cts (ignore | normal | require);
dcd (ignore | normal | require);
dsr (ignore | normal | require);
dtr signal-handling-option;
ignore-all;
indication (ignore | normal | require);
rts (assert | de-assert | normal);
tm(ignore | normal | require);
}
dsr-polarity (negative | positive);
dte-options {
control-signal (assert | de-assert | normal);
cts (ignore | normal | require);
dcd (ignore | normal | require);
dsr (ignore | normal | require);
dtr signal-handling-option;
ignore-all;
indication (ignore | normal | require);
rts (assert | de-assert | normal);
tm(ignore | normal | require);
}
dtr-circuit (balanced | unbalanced);
dtr-polarity (negative | positive);
encoding (nrz | nrzi);
indication-polarity (negative | positive);
line-protocol protocol;
loopback mode;
rts-polarity (negative | positive);
tm-polarity (negative | positive);
transmit-clock invert;
}
services-options {
inactivity-timeout seconds;
open-timeout seconds;
session-limit {
maximumnumber;
rate new-sessions-per-second;
}
syslog {
host hostname {
facility-override facility-name;
log-prefix prefix-number;
services priority-level;
}
}
}
shdsl-options {
annex (annex-a | annex-b);
line-rate line-rate;
Copyright 2014, Juniper Networks, Inc. 32
Channelized STM1 Interfaces Feature Guide for Routing Devices
loopback (local | remote);
snr-margin {
current margin;
snext margin;
}
}
sonet-options {
aggregate asx;
aps {
advertise-interval milliseconds;
annex-b;
authentication-key key;
fast-aps-switch;
force;
hold-time milliseconds;
lockout;
neighbor address;
paired-group group-name;
preserve-interface;
protect-circuit group-name;
request;
revert-time seconds;
switching-mode (bidirectional | unidirectional);
working-circuit group-name;
}
bytes {
c2 value;
e1-quiet value;
f1 value;
f2 value;
s1 value;
z3 value;
z4 value;
}
fcs (16 | 32);
loopback (local | remote);
mpls {
pop-all-labels {
required-depth number;
}
}
path-trace trace-string;
(payload-scrambler | no-payload-scrambler);
rfc-2615;
trigger {
defect ignore;
hold-time up milliseconds down milliseconds;
}
vtmapping (itu-t | klm);
(z0-increment | no-z0-increment);
}
speed (10m| 100m| 1g | oc3 | oc12 | oc48);
stacked-vlan-tagging;
switch-options {
switch-port port-number {
(auto-negotiation | no-auto-negotiation);
33 Copyright 2014, Juniper Networks, Inc.
Chapter 3: Network Interfaces Configuration Statements and Hierarchy
speed (10m| 100m| 1g);
link-mode (full-duplex | half-duplex);
}
}
t1-options {
bert-algorithmalgorithm;
bert-error-rate rate;
bert-period seconds;
buildout value;
byte-encoding (nx56 | nx64);
crc-major-alarm-threshold (1e-3 | 5e-4 | 1e-4 | 5e-5 | 1e-5);
crc-minor-alarm-threshold (1e-3 | 5e-4 | 1e-4 | 5e-5 | 1e-5 | 5e-6 | 1e-6);
fcs (16 | 32);
framing (esf | sf);
idle-cycle-flag (flags | ones);
invert-data;
line-encoding (ami | b8zs);
loopback (local | payload | remote);
remote-loopback-respond;
start-end-flag (filler | shared);
timeslots time-slot-range;
}
t3-options {
atm-encapsulation (direct | plcp);
bert-algorithmalgorithm;
bert-error-rate rate;
bert-period seconds;
buildout feet;
(cbit-parity | no-cbit-parity);
compatibility-mode (adtran | digital-link | kentrox | larscom| verilink) <subrate
value>;
fcs (16 | 32);
(feac-loop-respond | no-feac-loop-respond);
idle-cycle-flag value;
(long-buildout | no-long-buildout);
(loop-timing | no-loop-timing);
loopback (local | payload | remote);
(mac | no-mac);
(payload-scrambler | no-payload-scrambler);
start-end-flag (filler | shared);
}
traceoptions {
flag flag <flag-modifier> <disable>;
}
transmit-bucket {
overflowdiscard;
rate percentage;
threshold bytes;
}
(traps | no-traps);
unidirectional;
vlan-tagging;
vlan-vci-tagging;
unit logical-unit-number {
accept-source-mac {
mac-address mac-address {
Copyright 2014, Juniper Networks, Inc. 34
Channelized STM1 Interfaces Feature Guide for Routing Devices
policer {
input cos-policer-name;
output cos-policer-name;
}
}
}
accounting-profile name;
advisory-options {
downstream-rate rate;
upstream-rate rate;
}
allow-any-vci;
atm-scheduler-map (map-name | default);
backup-options {
interface interface-name;
}
bandwidth rate;
cell-bundle-size cells;
clear-dont-fragment-bit;
compression {
rtp {
f-max-period number;
maximum-contexts number <force>;
queues [ queue-numbers ];
port {
minimumport-number;
maximumport-number;
}
}
}
compression-device interface-name;
copy-tos-to-outer-ip-header;
demux-destination family;
demux-source family;
demux-options {
underlying-interface interface-name;
}
description text;
alias alias-name;
interface {
l2tp-interface-id name;
(dedicated | shared);
}
dialer-options {
activation-delay seconds;
callback;
callback-wait-period time;
deactivation-delay seconds;
dial-string [ dial-string-numbers ];
idle-timeout seconds;
incoming-map {
caller (caller-id | accept-all);
initial-route-check seconds;
load-interval seconds;
load-threshold percent;
pool pool-name;
35 Copyright 2014, Juniper Networks, Inc.
Chapter 3: Network Interfaces Configuration Statements and Hierarchy
redial-delay time;
watch-list {
[ routes ];
}
}
}
disable;
disable-mlppp-inner-ppp-pfc;
dlci dlci-identifier;
drop-timeout milliseconds;
dynamic-call-admission-control {
activation-priority priority;
bearer-bandwidth-limit kilobits-per-second;
}
encapsulation type;
epd-threshold cells plp1 cells;
fragment-threshold bytes;
inner-vlan-id-range start start-id end end-id;
input-vlan-map {
(pop | pop-pop | pop-swap | push | push-push | swap | swap-push | swap-swap);
inner-tag-protocol-id tpid;
inner-vlan-id number;
tag-protocol-id tpid;
vlan-id number;
}
interleave-fragments;
inverse-arp;
layer2-policer {
input-policer policer-name;
input-three-color policer-name;
output-policer policer-name;
output-three-color policer-name;
}
link-layer-overhead percent;
minimum-links number;
mrru bytes;
multicast-dlci dlci-identifier;
multicast-vci vpi-identifier.vci-identifier;
multilink-max-classes number;
multipoint;
oam-liveness {
down-count cells;
up-count cells;
}
oam-period (seconds | disable);
output-vlan-map {
(pop | pop-pop | pop-swap | push | push-push | swap | swap-push | swap-swap);
inner-tag-protocol-id tpid;
inner-vlan-id number;
tag-protocol-id tpid;
vlan-id number;
}
passive-monitor-mode;
peer-unit unit-number;
plp-to-clp;
point-to-point;
Copyright 2014, Juniper Networks, Inc. 36
Channelized STM1 Interfaces Feature Guide for Routing Devices
ppp-options {
chap {
access-profile name;
default-chap-secret name;
local-name name;
passive;
}
compression {
acfc;
pfc;
pap;
default-pap-password password;
local-name name;
local-password password;
passive;
}
dynamic-profile profile-name;
lcp-max-conf-req number;
lcp-restart-timer milliseconds;
loopback-clear-timer seconds;
ncp-max-conf-req number;
ncp-restart-timer milliseconds;
}
pppoe-options {
access-concentrator name;
auto-reconnect seconds;
(client | server);
service-name name;
underlying-interface interface-name;
}
proxy-arp;
service-domain (inside | outside);
shaping {
(cbr rate | rtvbr peak rate sustained rate burst length | vbr peak rate sustained rate
burst length);
queue-length number;
}
short-sequence;
transmit-weight number;
(traps | no-traps);
trunk-bandwidth rate;
trunk-id number;
tunnel {
backup-destination address;
destination address;
key number;
routing-instance {
destination routing-instance-name;
}
source source-address;
ttl number;
}
vci vpi-identifier.vci-identifier;
vci-range start start-vci end end-vci;
vpi vpi-identifier;
vlan-id number;
37 Copyright 2014, Juniper Networks, Inc.
Chapter 3: Network Interfaces Configuration Statements and Hierarchy
vlan-id-list [vlan-id vlan-idvlan-id];
vlan-id-range number-number;
vlan-tags inner tpid.vlan-id outer tpid.vlan-id;
vlan-tags-outer tpid.vlan-id inner-list [vlan-id vlan-idvlan-id];
family family {
accounting {
destination-class-usage;
source-class-usage {
direction;
}
}
access-concentrator name;
address address {
destination address;
}
bundle ml-fpc/pic/port | ls-fpc/pic/port);
direct-connect;
duplicate-protection;
dynamic-profile profile-name;
filter {
group filter-group-number;
input filter-name;
input-list {
[ filter-names ];
output filter-name;
}
output-list {
[ filter-names ];
}
}
ipsec-sa sa-name;
keep-address-and-control;
max-sessions number;
max-sessions-vsa-ignore;
mtu bytes;
multicast-only;
negotiate-address;
no-redirects;
policer {
arp policer-template-name;
input policer-template-name;
output policer-template-name;
}
primary;
proxy inet-address address;
receive-options-packets;
receive-ttl-exceeded;
remote (inet-address address | mac-address address);
rpf-check {
fail-filter filter-name;
mode loose;
}
sampling {
direction;
}
service {
Copyright 2014, Juniper Networks, Inc. 38
Channelized STM1 Interfaces Feature Guide for Routing Devices
input {
service-set service-set-name <service-filter filter-name>;
post-service-filter filter-name;
}
output {
service-set service-set-names <service-filter filter-name>;
}
}
service-name-table table-name;
short-cycle-protection <lockout-time-min minimum-seconds lockout-time-max
maximum-seconds>;
targeted-broadcast {
forward-and-send-to-re;
forward-only;
}
(translate-discard-eligible | no-translate-discard-eligible);
(translate-fecn-and-becn | no-translate-fecn-and-becn);
translate-plp-control-word-de;
unnumbered-address interface-name <destination address destination-profile
profile-name | preferred-source-address address>;
address address {
arp ip-address (mac | multicast-mac) mac-address <publish>;
broadcast address;
destination address;
destination-profile name;
eui-64;
multipoint-destination address (dlci dlci-identifier | vci vci-identifier);
multipoint-destination address {
epd-threshold cells plp1 cells;
inverse-arp;
oam-liveness {
up-count cells;
down-count cells;
}
oam-period (seconds | disable);
shaping {
(cbr rate | rtvbr peak rate sustainedrate burst length| vbr peak rate sustained
rate burst length);
queue-length number;
}
vci vpi-identifier.vci-identifier;
}
preferred;
primary;
(vrrp-group | vrrp-inet6-group) group-number {
(accept-data | no-accept-data);
advertiseinterval seconds;
authentication-type authentication;
authentication-key key;
fast-interval milliseconds;
(preempt | no-preempt) {
hold-time seconds;
}
priority-number number;
track {
priority-cost seconds;
39 Copyright 2014, Juniper Networks, Inc.
Chapter 3: Network Interfaces Configuration Statements and Hierarchy
priority-hold-time interface-name {
bandwidth-threshold bits-per-second {
priority;
}
interface priority;
}
route ip-address/mask routing-instance instance-name priority-cost cost;
}
virtual-address [ addresses ];
}
}
}
}
}
}
Related
Documentation
Junos OS Hierarchy and RFC Reference
Ethernet Interfaces
Junos OS Network Interfaces Library for Routing Devices
[edit logical-systems] Hierarchy Level
The following lists the statements that can be configured at the [edit logical-systems]
hierarchy level that are also documented in this manual. For more information about
logical systems, see the Logical Systems Feature Guide for Routing Devices.
logical-systems logical-system-name {
interfaces interface-name {
unit logical-unit-number {
accept-source-mac {
mac-address mac-address {
policer {
input cos-policer-name;
output cos-policer-name;
}
}
}
allow-any-vci;
atm-scheduler-map (map-name | default);
bandwidth rate;
backup-options {
interface interface-name;
}
cell-bundle-size cells;
clear-dont-fragment-bit;
compression {
rtp {
f-max-period number;
port {
minimumport-number;
maximumport-number;
}
queues [ queue-numbers ];
Copyright 2014, Juniper Networks, Inc. 40
Channelized STM1 Interfaces Feature Guide for Routing Devices
}
}
compression-device interface-name;
description text;
interface {
l2tp-interface-id name;
(dedicated | shared);
}
dialer-options {
activation-delay seconds;
deactivation-delay seconds;
dial-string [ dial-string-numbers ];
idle-timeout seconds;
initial-route-check seconds;
load-threshold number;
pool pool;
remote-name remote-callers;
watch-list {
[ routes ];
}
}
disable;
dlci dlci-identifier;
drop-timeout milliseconds;
dynamic-call-admission-control {
activation-priority priority;
bearer-bandwidth-limit kilobits-per-second;
}
encapsulation type;
epd-threshold cells plp1 cells;
fragment-threshold bytes;
input-vlan-map {
inner-tag-protocol-id;
inner-vlan-id;
(pop | pop-pop | pop-swap | push | push-push | swap | swap-push | swap-swap);
tag-protocol-id tpid;
vlan-id number;
}
interleave-fragments;
inverse-arp;
layer2-policer {
input-policer policer-name;
input-three-color policer-name;
output-policer policer-name;
output-three-color policer-name;
}
link-layer-overhead percent;
minimum-links number;
mrru bytes;
multicast-dlci dlci-identifier;
multicast-vci vpi-identifier.vci-identifier;
multilink-max-classes number;
multipoint;
oam-liveness {
up-count cells;
down-count cells;
41 Copyright 2014, Juniper Networks, Inc.
Chapter 3: Network Interfaces Configuration Statements and Hierarchy
}
oam-period (seconds | disable);
output-vlan-map {
inner-tag-protocol-id;
inner-vlan-id;
(pop | pop-pop | pop-swap | push | push-push | swap | swap-swap);
tag-protocol-id tpid;
vlan-id number;
}
passive-monitor-mode;
peer-unit unit-number;
plp-to-clp;
point-to-point;
ppp-options {
chap {
access-profile name;
default-chap-secret name;
local-name name;
passive;
}
compression {
acfc;
pfc;
}
}
dynamic-profile profile-name;
pap {
default-pap-password password;
local-name name;
local-password password;
passive;
}
}
proxy-arp;
service-domain (inside | outside);
shaping {
(cbr rate | rtvbr peak rate sustained rate burst length | vbr peak rate sustained rate
burst length);
queue-length number;
}
short-sequence;
transmit-weight number;
(traps | no-traps);
trunk-bandwidth rate;
trunk-id number;
tunnel {
backup-destination address;
destination address;
key number;
routing-instance {
destination routing-instance-name;
}
source source-address;
ttl number;
}
vci vpi-identifier.vci-identifier;
Copyright 2014, Juniper Networks, Inc. 42
Channelized STM1 Interfaces Feature Guide for Routing Devices
vlan-id number;
vlan-id-list [vlan-id vlan-idvlan-id]
vlan-tags inner tpid.vlan-id outer tpid.vlan-id;
vlan-tags outer tpid.vlan-id inner-list [vlan-id vlan-idvlan-id]
vpi vpi-identifier;
family family {
accounting {
destination-class-usage;
source-class-usage {
direction;
}
}
bundle interface-name;
filter {
group filter-group-number;
input filter-name;
input-list {
[ filter-names ];
}
output filter-name;
output-list {
[ filter-names ];
}
}
ipsec-sa sa-name;
keep-address-and-control;
mtu bytes;
multicast-only;
no-redirects;
policer {
arp policer-template-name;
input policer-template-name;
output policer-template-name;
}
primary;
proxy inet-address address;
receive-options-packets;
receive-ttl-exceeded;
remote (inet-address address | mac-address address);
rpf-check <fail-filter filter-name> {
<mode loose>;
}
sampling {
direction;
}
service {
input {
service-set service-set-name <service-filter filter-name>;
post-service-filter filter-name;
}
output {
service-set service-set-name <service-filter filter-name>;
}
}
(translate-discard-eligible | no-translate-discard-eligible);
(translate-fecn-and-becn | no-translate-fecn-and-becn);
43 Copyright 2014, Juniper Networks, Inc.
Chapter 3: Network Interfaces Configuration Statements and Hierarchy
unnumbered-address interface-name destination address destination-profile
profile-name;
address address {
arp ip-address (mac | multicast-mac) mac-address <publish>;
broadcast address;
destination address;
destination-profile name;
eui-64;
multipoint-destination address (dlci dlci-identifier | vci vci-identifier);
multipoint-destination address {
epd-threshold cells plp1 cells;
inverse-arp;
oam-liveness {
up-count cells;
down-count cells;
}
oam-period (seconds | disable);
shaping {
(cbr rate | rtvbr peak rate sustainedrate burst length| vbr peak rate sustained
rate burst length);
queue-length number;
}
vci vpi-identifier.vci-identifier;
}
preferred;
primary;
(vrrp-group | vrrp-inet6-group) group-number {
(accept-data | no-accept-data);
advertiseinterval seconds;
authentication-type authentication;
authentication-key key;
fast-interval milliseconds;
(preempt | no-preempt) {
hold-time seconds;
}
priority-number number;
track {
priority-cost seconds;
priority-hold-time interface-name {
interface priority;
bandwidth-threshold bits-per-second {
priority;
}
}
route ip-address/mask routing-instance instance-name priority-cost cost;
}
}
virtual-address [ addresses ];
}
}
}
}
}
Copyright 2014, Juniper Networks, Inc. 44
Channelized STM1 Interfaces Feature Guide for Routing Devices
Related
Documentation
Junos OS Hierarchy and RFC Reference
Ethernet Interfaces
Junos OS Network Interfaces Library for Routing Devices
45 Copyright 2014, Juniper Networks, Inc.
Chapter 3: Network Interfaces Configuration Statements and Hierarchy
Copyright 2014, Juniper Networks, Inc. 46
Channelized STM1 Interfaces Feature Guide for Routing Devices
CHAPTER 4
Statement Summary
advertise-interval on page 48
aps on page 49
authentication-key on page 50
bert-error-rate on page 51
bert-period on page 53
bytes on page 55
e1-options on page 56
fast-aps-switch on page 57
fcs on page 58
force on page 59
framing (E1, E3, and T1 Interfaces) on page 60
hold-time (APS) on page 61
idle-cycle-flag on page 62
interface-type (Interfaces) on page 63
lockout on page 64
loopback (ADSL, DS0, E1/E3, SONET/SDH, SHDSL, and T1/T3) on page 65
neighbor (Automatic Protection Switching for SONET/SDH) on page 66
no-partition on page 67
no-termination-request on page 68
paired-group on page 68
partition on page 69
protect-circuit on page 70
request on page 70
revert-time (Interfaces) on page 71
sonet-options on page 72
start-end-flag on page 74
switching-mode on page 75
timeslots on page 76
47 Copyright 2014, Juniper Networks, Inc.
vtmapping on page 77
working-circuit on page 77
advertise-interval
Syntax advertise-interval milliseconds;
Hierarchy Level [edit interfaces interface-name sonet-options aps]
Release Information Statement introduced before Junos OS Release 7.4.
Description Modify the Automatic Protection Switching (APS) interval at which the protect and
working routers send packets to their neighbors to advertise that they are operational. A
router considers its neighbor to be operational for a period, called the hold time, that is,
by default, three times the advertisement interval.
Options millisecondsInterval between advertisement packets.
Range: 1 through 65,534 milliseconds
Default: 1000 milliseconds
Required Privilege
Level
interfaceTo viewthis statement in the configuration.
interface-controlTo add this statement to the configuration.
Related
Documentation
Configuring APS Timers
Copyright 2014, Juniper Networks, Inc. 48
Channelized STM1 Interfaces Feature Guide for Routing Devices
aps
Syntax aps {
advertise-interval milliseconds;
annex-b
authentication-key key;
(break-before-make | no-break-before-make);
fast-aps-switch;
force;
hold-time milliseconds;
lockout;
neighbor address;
paired-group group-name;
preserve-interface;
protect-circuit group-name;
request;
revert-time seconds;
switching-mode (bidirectional | unidirectional);
working-circuit group-name;
}
Hierarchy Level [edit interfaces interface-name sonet-options]
Release Information Statement introduced before Junos OS Release 7.4.
Description Configure Automatic Protection Switching (APS) on the router.
For DS3 channels on a channelized OC12 interface, configure APS on channel 0 only. If
you configure APS on channels 1 through 11, it is ignored.
The statements are explained separately.
Required Privilege
Level
interfaceTo viewthis statement in the configuration.
interface-controlTo add this statement to the configuration.
Related
Documentation
Automatic Protection Switching and Multiplex Section Protection Overview
49 Copyright 2014, Juniper Networks, Inc.
Chapter 4: Statement Summary
authentication-key
Syntax authentication-key key;
Hierarchy Level [edit interfaces interface-name sonet-options aps]
Release Information Statement introduced before Junos OS Release 7.4.
Description Configure the Automatic Protection Switching (APS) authentication key (password).
Options keyAuthentication password. It can be 1 through 8 characters long. Configure the same
key for both the working and protect routers.
Required Privilege
Level
interfaceTo viewthis statement in the configuration.
interface-controlTo add this statement to the configuration.
Related
Documentation
Configuring Basic Automatic Protect Switching
For information about the authentication-key statement at the [edit interfaces
interface-name unit unit-number family inet address address (vrrp-group |
vrrp-inet6-group)group-number] or [edit logical-systemslogical-system-nameinterfaces
interface-name unit unit-number family (inet | inet6) address address (vrrp-group |
vrrp-inet6-group) group-number] hierarchy level, see the Junos OS High Availability
Library for Routing Devices.
Copyright 2014, Juniper Networks, Inc. 50
Channelized STM1 Interfaces Feature Guide for Routing Devices
bert-error-rate
Syntax bert-error-rate rate;
Hierarchy Level [edit interfaces ce1-fpc/pic/port],
[edit interfaces ct1-fpc/pic/port],
[edit interfaces interface-name ds0-options],
[edit interfaces interface-name e1-options],
[edit interfaces interface-name e3-options],
[edit interfaces interface-name t1-options],
[edit interfaces interface-name t3-options]
Release Information Statement introduced before Junos OS Release 7.4.
Statement introduced in Junos OS Release 12.2 for the ACX Series Universal Access
Routers.
Description Configure the bit error rate to use in a BERT procedure. Applies to E1, E3, T1, or T3
interfaces, and to the channelized interfaces (DS3, OC3, OC12, and STM1).
NOTE: When configuring CE1 or CT1 interfaces on 10-port Channelized E1/T1
IQEPICs, thebert-error-ratestatement must beincludedat the[edit interfaces
ce1-fpc/pic/port] or [edit interfaces ct1-fpc/pic/port] hierarchy level as
appropriate.
When configuring t3-options bert-error-rate on J Series routers, only 0 and 3
through 7 are valid values. If you enter 1 or 2, Junos OS will return the error
message configuration check-out failed.
Options rateBit error rate.
Range: 0 through 7, which corresponds to 10
1
(1 error per bit) to 10
7
(1 error per 10
million bits)
Default: 0
Required Privilege
Level
interfaceTo viewthis statement in the configuration.
interface-controlTo add this statement to the configuration.
Related
Documentation
bert-algorithm
bert-period on page 53
ds0-options
e1-options on page 56
e3-options
t1-options
t3-options
51 Copyright 2014, Juniper Networks, Inc.
Chapter 4: Statement Summary
Interface Diagnostics on page 105
Configuring E1 BERT Properties
Configuring E3 BERT Properties
Configuring T1 BERT Properties
Configuring T3 BERT Properties
Examples: Configuring T3 Interfaces
Copyright 2014, Juniper Networks, Inc. 52
Channelized STM1 Interfaces Feature Guide for Routing Devices
bert-period
Syntax bert-period seconds;
Hierarchy Level [edit interfaces ce1-fpc/pic/port],
[edit interfaces ct1-fpc/pic/port],
[edit interfaces interface-name ds0-options],
[edit interfaces interface-name e1-options],
[edit interfaces interface-name e3-options],
[edit interfaces interface-name t1-options],
[edit interfaces interface-name t3-options]
Release Information Statement introduced before Junos OS Release 7.4.
Statement introduced in Junos OS Release 12.2 for the ACX Series Universal Access
Routers.
Description Configure the duration of a BERT test. Applies to E1, E3, T1, and T3 interfaces, and to E1,
E3, T1, and T3 partitions on the channelized interfaces (CE1, CT1, DS3, OC3, OC12, OC48,
STM1, STM4, and STM16).
E1 and T1 IQ, IQE, and standard interfaces support an extended BERT period range, up
to 86,400 seconds (24 hours).
NOTE: When configuring CE1 or CT1 interfaces on 10-port Channelized E1/T1
IQE PICs, the bert-period statement must be included at the [edit interfaces
ce1-fpc/pic/port] or [edit interfaces ct1-fpc/pic/port] hierarchy level as
appropriate.
Options secondsTest duration. Range and default values vary by interface type.
Range:
PIC-dependentNormal BERT period: either 1 through 239 seconds or 1 through 240
seconds
PIC-dependentExtended BERT period: from1 through 86,400 seconds
Default:
Normal BERT period: 10 seconds
Extended BERT period (on supported E1 interfaces): 10 seconds
Extended BERT period (on supported T1 interfaces): 240 seconds
Required Privilege
Level
interfaceTo viewthis statement in the configuration.
interface-controlTo add this statement to the configuration.
Related
Documentation
Interface Diagnostics on page 105
Configuring E1 BERT Properties
53 Copyright 2014, Juniper Networks, Inc.
Chapter 4: Statement Summary
Configuring E3 BERT Properties
Configuring T1 BERT Properties
Configuring T3 BERT Properties
bert-algorithm
bert-error-rate on page 51
Copyright 2014, Juniper Networks, Inc. 54
Channelized STM1 Interfaces Feature Guide for Routing Devices
bytes
Syntax bytes {
c2 value;
e1-quiet value;
f1 value;
f2 value;
s1 value;
z3 value;
z4 value;
}
Hierarchy Level [edit interfaces interface-name sonet-options]
Release Information Statement introduced before Junos OS Release 7.4.
Description Set values in some SONET/SDH header bytes.
Options c2 valuePath signal label SONET/SDH overhead byte. SONET/SDH frames use the C2
bytetoindicatethecontents of thepayloadinsidetheframe. SONET/SDHinterfaces
use the C2 byte to indicate whether the payload is scrambled.
Range: 0 through 255
Default: 0xCF
e1-quiet valueDefault idle byte sent on the orderwire SONET/SDHoverhead bytes. The
router does not support the orderwire channel, and hence sends this byte
continuously.
Range: 0 through 255
Default: 0x7F
f1 value, f2 value, z3 value, z4 valueSONET/SDH overhead bytes.
Range: 0 through 255
Default: 0x00
s1 valueSynchronizationmessageSONEToverheadbyte. This byteis normallycontrolled
as a side effect of the systemreference clock configuration and the state of the
external clock coming froman interface if the systemreference clocks have been
configured to use an external reference.
Range: 0 through 255
Default: 0xCC
Required Privilege
Level
interfaceTo viewthis statement in the configuration.
interface-controlTo add this statement to the configuration.
Related
Documentation
Configuring SONET/SDH Header Byte Values
no-concatenate
55 Copyright 2014, Juniper Networks, Inc.
Chapter 4: Statement Summary
e1-options
Syntax e1-options {
bert-algorithmalgorithm;
bert-error-rate rate;
bert-period seconds;
fcs (16 | 32);
framing (g704 | g704-no-crc4 | unframed);
idle-cycle-flag (flags | ones);
invert-data;
loopback (local | remote);
start-end-flag (filler | shared);
timeslots time-slot-range;
}
Hierarchy Level [edit interfaces interface-name]
Release Information Statement introduced before Junos OS Release 7.4.
Statement introduced in Junos OS Release 12.2 for the ACX Series Universal Access
Routers.
Description Configure E1-specific physical interface properties.
The statements are explained separately.
Required Privilege
Level
interfaceTo viewthis statement in the configuration.
interface-controlTo add this statement to the configuration.
Related
Documentation
Channelized E1 IQand IQE Interfaces Overview
Channelized STM1 Interfaces Overviewon page 3
E1 Interfaces Overview
T1 Interfaces Overview
Copyright 2014, Juniper Networks, Inc. 56
Channelized STM1 Interfaces Feature Guide for Routing Devices
fast-aps-switch
Syntax fast-aps-switch;
Hierarchy Level [edit interfaces interface-name sonet-options aps]
Release Information Statement introduced in Junos OS Release 12.1.
Description (M320 routers with Channelized OC3/STM1 Circuit Emulation PIC with SFP only and EX
Series switches) Reduce the Automatic Protection Switching (APS) switchover time in
Layer 2 circuits.
NOTE:
Configuring this statement reduces the APS switchover time only when
theLayer 2circuit encapsulationtypefor theinterfacereceivingtrafficfrom
a Layer 2 circuit neighbor is SAToP.
When the fast-aps-switch statement is configured in revertive APS mode,
youmust configureanappropriatevaluefor revert timetoachievereduction
in APS switchover time.
To prevent the logical interfaces in the data path frombeing shut down,
configure appropriate hold-time values on all the interfaces in the data
path that support TDM.
Thefast-aps-switchstatement cannot beconfiguredwhentheAPSannex-b
option is configured.
The interfaces that have the fast-aps-switch statement configured cannot
be used in virtual private LANservice (VPLS) environments.
Required Privilege
Level
interfaceTo viewthis statement in the configuration.
interface-controlTo add this statement to the configuration.
Related
Documentation
Reducing APS Switchover Time in Layer 2 Circuits
57 Copyright 2014, Juniper Networks, Inc.
Chapter 4: Statement Summary
fcs
Syntax fcs (16 | 32);
Hierarchy Level [edit interfaces e1-fpc/pic/port],
[edit interfaces t1-fpc/pic/port],
[edit interfaces interface-name ds0-options],
[edit interfaces interface-name e1-options],
[edit interfaces interface-name e3-options],
[edit interfaces interface-name sonet-options],
[edit interfaces interface-name t1-options],
[edit interfaces interface-name t3-options]
Release Information Statement introduced before Junos OS Release 7.4.
Statement introduced in Junos OS Release 12.2 for the ACX Series Universal Access
Routers.
Description For E1/E3, SONET/SDH, and T1/T3 interfaces, configure the frame checksum(FCS) on
the interface. The checksummust be the same on both ends of the interface.
On a channelized OC12 interface, the SONET/SDH fcs statement is not supported. To
configure FCS on each DS3 channel, you must include the t3-options fcs statement in
the configuration for each channel. For SONET/SDH, the channelized OC12 interface
supports DS3toSTS-1 toOC12. For SDH, thechannelizedOC12interfacesupports NxDS3
to NxVC3 to AU3 to STM.
NOTE: WhenconfiguringE1 or T1 interfaces on10-port ChannelizedE1/T1 IQE
PICs, thefcsstatement must beincludedat the[edit interfacese1-fpc/pic/port]
or [edit interfaces t1-fpc/pic/port] hierarchy level as appropriate.
Options 16Use a 16-bit frame checksumon the interface.
32Use a 32-bit frame checksumon the interface. Using a 32-bit checksumprovides
morereliablepacket verification, but someolder equipment might not support 32-bit
checksums.
Default: 16
Required Privilege
Level
interfaceTo viewthis statement in the configuration.
interface-controlTo add this statement to the configuration.
Related
Documentation
Configuring the E1 Frame Checksum
Configuring the E3 Frame Checksum
Configuring the SONET/SDH Frame Checksum
Configuring the T1 Frame Checksum
Configuring the T3 Frame Checksum
Copyright 2014, Juniper Networks, Inc. 58
Channelized STM1 Interfaces Feature Guide for Routing Devices
force
Syntax force (protect | working);
Hierarchy Level [edit interfaces interface-name sonet-options aps]
Release Information Statement introduced before Junos OS Release 7.4.
Description Performa forced switch between the protect and working circuits. This statement is
honored only if there are no higher-priority reasons to switch. It can be overridden by a
signal failure on the protect circuit, thus causing a switch to the working circuit.
Options protectRequest the circuit to become the protect circuit.
workingRequest the circuit to become the working circuit.
Required Privilege
Level
interfaceTo viewthis statement in the configuration.
interface-controlTo add this statement to the configuration.
Related
Documentation
Configuring Switching Between the Working and Protect Circuits
request on page 70
59 Copyright 2014, Juniper Networks, Inc.
Chapter 4: Statement Summary
framing (E1, E3, and T1 Interfaces)
Syntax framing (g704 | g704-no-crc4 | g.751 | g.832 | unframed | sf | esf);
Hierarchy Level [edit interfaces ce1-fpc/pic/port],
[edit interfaces ct1-fpc/pic/port],
[edit interfaces at-fpc/pic/port e3-options],
[edit interfaces e1-fpc/pic/port e1-options],
[edit interfaces t1-fpc/pic/port t1-options]
Release Information Statement introduced before Junos OS Release 7.4.
Statement introduced in Junos OS Release 12.2 for the ACX Series Universal Access
Routers.
Description Configure the framing format.
NOTE: When configuring CE1 or CT1 interfaces on 10-port Channelized E1/T1
IQE PICs, the framing statement must be included at the [edit interfaces
ce1-fpc/pic/port] or [edit interfaces ct1-fpc/pic/port] hierarchy level as
appropriate.
Default esf for T1 interfaces; g704 for E1 interfaces. There is no default value for E3 over ATM
interfaces.
Options esfExtended superframe (ESF) mode for T1 interfaces.
g704G.704 framing format for E1 interfaces.
g704-no-crc4G.704framingwithnocyclicredundancy check 4(CRC4) for E1 interfaces.
g.751G.751 framing format for E3 over ATMinterfaces.
g.832G.832 framing format for E3 over ATMinterfaces.
sfSuperframe (SF) mode for T1 interfaces.
unframedUnframed mode for E1 interfaces.
Required Privilege
Level
interfaceTo viewthis statement in the configuration.
interface-controlTo add this statement to the configuration.
Related
Documentation
Configuring E1 Framing
Configuring E3 and T3 Parameters on ATMInterfaces
Configuring T1 Framing
Copyright 2014, Juniper Networks, Inc. 60
Channelized STM1 Interfaces Feature Guide for Routing Devices
hold-time (APS)
Syntax hold-time milliseconds;
Hierarchy Level [edit interfaces interface-name sonet-options aps]
Release Information Statement introduced before Junos OS Release 7.4.
Description Hold-time value to use to determine whether a neighbor APS router is operational.
Options millisecondsHold-time value.
Range: 1 through 65,534 milliseconds
Default: 3000 milliseconds (3 times the advertisement interval)
Required Privilege
Level
interfaceTo viewthis statement in the configuration.
interface-controlTo add this statement to the configuration.
Related
Documentation
Configuring APS Timers
advertise-interval on page 48
61 Copyright 2014, Juniper Networks, Inc.
Chapter 4: Statement Summary
idle-cycle-flag
Syntax idle-cycle-flag value;
Hierarchy Level [edit interfaces e1-fpc/pic/port],
[edit interfaces t1-fpc/pic/port],
[edit interfaces interface-name ds0-options],
[edit interfaces interface-name e1-options],
[edit interfaces interface-name e3-options],
[edit interfaces interface-name serial-options],
[edit interfaces interface-name t1-options],
[edit interfaces interface-name t3-options]
Release Information Statement introduced before Junos OS Release 7.4.
Statement introduced in Junos OS Release 12.2 for the ACX Series Universal Access
Routers.
Description Configure the value that the DS0, E1, E3, T1, or T3 interface transmits during idle cycles.
NOTE: WhenconfiguringE1 or T1 interfaces on10-port ChannelizedE1/T1 IQE
PICs, the idle-cycle-flag statement must be included at the [edit interfaces
e1-fpc/pic/port] or [edit interfaces t1-fpc/pic/port] hierarchy level as
appropriate.
Options valueValue to transmit in the idle cycles:
flagsTransmit the value 0x7E.
onesTransmit the value 0xFF (all ones).
Default: Flags
Required Privilege
Level
interfaceTo viewthis statement in the configuration.
interface-controlTo add this statement to the configuration.
Related
Documentation
Configuring the E1 Idle Cycle Flag
Configuring the E3 Idle Cycle Flag
Configuring the T1 Idle Cycle Flag
Configuring the T3 Idle Cycle Flag
Copyright 2014, Juniper Networks, Inc. 62
Channelized STM1 Interfaces Feature Guide for Routing Devices
interface-type (Interfaces)
Syntax interface-type (bc | coc1 | ct1 | ct3 | dc | ds |so | t1 | t3);
Hierarchy Level [edit interfaces interface-range name no-partition],
[edit interfaces interface-range name partition partition-number],
[edit interfaces interface-range name partition partition-number oc-slice oc-slice-range],
[edit interfaces interface-range name partition partition-number timeslot timeslot-range]
Release Information Statement introduced before Junos OS Release 7.4.
Description For IQand IQE interfaces only, configure the sublevel interface type.
Options bcDualPort Channelized E1 and T1 ISDN PRI interface type. You can specify this
interfacetypeat the[edit interfacesinterface-namepartitionpartition-number timeslot
timeslot-range] hierarchy level to create a bearer (B) channel bc-pim/0/port:channel
interface for each time you want to function as an ISDN PRI B-channel.
coc1Channelized OC1 interface type. You can specify this interface type at the [edit
interfaces interface-name partition partition-number oc-slice oc-slice-range
interface-type coc12-fpc/pic/port] hierarchy level.
ct1Channelized T1 interface type. You can specify this interface type at the [edit
interfaces interface-name partition partition-number interface-type
ct3-fpc/pic/port<:channel>] hierarchy level.
ct3Channelized T3 interface type. You can specify this interface type at the [edit
interfaces interface-name partition partition-number oc-slice oc-slice-range
interface-type coc1-fpc/pic/port:channel no-partition] hierarchy level.
dcDual-Port ChannelizedE1 andT1 ISDNPRI interfacetype. Youcanspecifythisinterface
type at the [edit interfaces interface-name partition partition-number timeslot
timeslot-range] hierarchy level to create a (D) channel dc-pim/0/port to control the
B-channels.
dsDS0 interface type. You can specify this interface type at the [edit interfaces
interface-namepartition partition-number interface-type (ce1-fpc/pic/port |
ct1-fpc/pic/port<:channel>)] hierarchy level.
soSONET/SDHinterface type. You can specify this interface type at the [edit interfaces
interface-name partition partition-number oc-slice oc-slice-range interface-type
coc12-fpc/pic/port] hierarchy level.
t1T1 interface type. You can specify this interface type at the [edit interfaces
interface-name partition partition-number oc-slice oc-slice-range interface-type
(coc12-fpc/pic/port | coc1-fpc/pic/port)] hierarchy level.
t3T3 interface type. You can specify this interface type at the [edit interfaces
interface-name partition partition-number oc-sliceoc-slice-range interface-type
(coc12-fpc/pic/port | coc1-fpc/pic/port:channel no-partition)] hierarchy level.
63 Copyright 2014, Juniper Networks, Inc.
Chapter 4: Statement Summary
Required Privilege
Level
interfaceTo viewthis statement in the configuration.
interface-controlTo add this statement to the configuration.
Related
Documentation
Channelized E1 IQand IQE Interfaces Overview
Channelized OC12/STM4 IQand IQE Interfaces Overview
Configuring Channelized T3 IQInterfaces
lockout
Syntax lockout;
Hierarchy Level [edit interfaces interface-name sonet-options aps]
Release Information Statement introduced before Junos OS Release 7.4.
Description Configure a lockout of protection, forcing the use of the working circuit and locking out
the protect circuit regardless of anything else.
Required Privilege
Level
interfaceTo viewthis statement in the configuration.
interface-controlTo add this statement to the configuration.
Related
Documentation
Configuring Switching Between the Working and Protect Circuits
Copyright 2014, Juniper Networks, Inc. 64
Channelized STM1 Interfaces Feature Guide for Routing Devices
loopback (ADSL, DS0, E1/E3, SONET/SDH, SHDSL, and T1/T3)
Syntax loopback (local | payload | remote);
Hierarchy Level [edit interfaces ce1-fpc/pic/port],
[edit interfaces ct1-fpc/pic/port],
[edit interfaces t1-fpc/pic/port],
[edit interfaces interface-name ds0-options],
[edit interfaces interface-name dsl-options],
[edit interfaces interface-name e1-options],
[edit interfaces interface-name e3-options],
[edit interfaces interface-name shdsl-options},
[edit interfaces interface-name sonet-options],
[edit interfaces interface-name t1-options],
[edit interfaces interface-name t3-options]
Release Information Statement introduced before Junos OS Release 7.4.
Statement introduced in Junos OS Release 12.2 for the ACX Series Universal Access
Routers.
Description Configurealoopbackconnection. Toturnoff theloopbackcapability, removetheloopback
statement fromthe configuration.
NOTE: When configuring CE1 or CT1 interfaces on 10-port Channelized E1/T1
IQE PICs, the loopback statement must be included with the local or remote
option at the [edit interfaces ce1-fpc/pic/port] or [edit interfaces
ct1-fpc/pic/port] hierarchy level as appropriate.
When configuring T1 interfaces on 10-port Channelized E1/T1 IQE PICs, the
loopback statement must be included with the payload option at the [edit
interfaces t1-fpc/pic/port] hierarchy level.
NOTE: When configuring CE1 or CT1 interfaces on the 16-port Channelized
E1/T1 MIC(MIC-3D-16CHE1-T1-CE), youmust includetheloopbackstatement
at the [edit interfaces ce1-fpc/pic/port] hierarchy level, or [edit interfaces
ct1-fpc/pic/port]
To configure loopback on channelized IQand IQE PICs, SONET/SDH level, use the
sonet-options loopback statement local and remote options at the controller interface
(coc48, cstm16, coc12, cstm4, coc3, cstm1). It is ignored for path-level interfaces
so-fpc/pic/port or so-fpc/pic/port:channel.
Options localLooppackets, includingbothdataandtiminginformation, backonthelocal routers
PIC. NxDS0 IQinterfaces do not support local loopback.
65 Copyright 2014, Juniper Networks, Inc.
Chapter 4: Statement Summary
payloadFor channelized T3, T1, and NxDS0 IQinterfaces only, loop back data only
(without clocking information) on the remote routers PIC. With payload loopback,
overhead is recalculated. Neither ATM-over-asymmetrical digital subscriber line
(ADSL) interfaces nor ATM-over-SHDSL interfaces support payload loopback.
remoteLoop packets, including both data and timing information, back on the remote
routers interface card. NxDS0 IQinterfaces do not support remote loopback.
Required Privilege
Level
interfaceTo viewthis statement in the configuration.
interface-controlTo add this statement to the configuration.
Related
Documentation
Configuring E3 and T3 Parameters on ATMInterfaces
Configuring E1 Loopback Capability
Configuring E3 Loopback Capability
Configuring SONET/SDH Loopback Capability
Configuring SHDSL Operating Mode on an ATMPhysical Interface
Configuring T1 Loopback Capability
Configuring T3 Loopback Capability
feac-loop-respond
neighbor (Automatic Protection Switching for SONET/SDH)
Syntax neighbor address;
Hierarchy Level [edit interfaces interface-name sonet-options aps]
Release Information Statement introduced before Junos OS Release 7.4.
Description If you are configuring one router to be the working router and a second to be the protect
router, configure the address of the remote interface. You configure this on one or both
of the interfaces.
The address you specify for the neighbor must never be routed through the interface on
whichAPSis configured, or instability will result. Westrongly recommendthat youdirectly
connect the working and protect routers and that you configure the interface address of
this shared network as the neighbor address.
Options addressNeighbors address.
Required Privilege
Level
interfaceTo viewthis statement in the configuration.
interface-controlTo add this statement to the configuration.
Related
Documentation
Configuring Basic Automatic Protect Switching
Copyright 2014, Juniper Networks, Inc. 66
Channelized STM1 Interfaces Feature Guide for Routing Devices
no-partition
Syntax no-partition interface-type (e1 | (cau4 | so) | (ct3 | t3) | so | t3);
Hierarchy Level [edit interfaces ce1-fpc/pic/port],
[edit interfaces coc1-fpc/pic/port:channel],
[edit interfaces coc12-fpc/pic/port],
[edit interfaces cstm1-fpc/pic/port],
[edit interfaces ct3-fpc/pic/port]
Release Information Statement introduced before Junos OS Release 7.4.
Description For ChannelizedE1 IQPICs only, configurethechannelizedE1 interfaceas anunpartitioned,
clear channel.
For ChannelizedOC12PIConly, convert thechannelizedOC1 IQinterfaceintoachannelized
T3 interface or a T3 interface. You performthis configuration task for C-bit parity and
M13-mapped configurations.
For Channelized OC12 IQPICs only, configure the channelized OC12 interface as an
unpartitioned, clear channel.
For Channelized STM1 PIC only, convert the channelized STM1 IQinterface into a
channelized Administrative Unit 4 (AU-4) interface or a SONET/SDH STM1 interface.
For ChannelizedDS3PIConly, configurethechannelizedT3interfaceas anunpartitioned,
clear channel.
Default If you do not include either this statement or the partition statement, the Channelized IQ
PIC is not partitioned, and no data channels are configured.
Options The option used must correspond to the physical interface type:
e1E1 interface type.
coc12 soChannelized OC12 interface type, in SONET mode.
cau4Channelized AU-4 interface type.
cstm1SONET/SDH STM1 interface type, in SDH mode.
ct3Channelized T3 interface type.
t3T3 interface type.
Required Privilege
Level
interfaceTo viewthis statement in the configuration.
interface-controlTo add this statement to the configuration.
Related
Documentation
Channelized E1 IQand IQE Interfaces Overview
Channelized OC12/STM4 IQand IQE Interfaces Overview
Configuring an OC12/STM4 Interface
67 Copyright 2014, Juniper Networks, Inc.
Chapter 4: Statement Summary
Configuring Channelized STM1 IQand IQE Interfaces on page 7
Configuring T3 IQInterfaces
partition on page 69
no-partition
no-termination-request
Syntax no-termination-request;
Hierarchy Level [edit interfaces interface-name ppp-options],
[edit interfaces lsq-fpc/pic/port lsq-failure-options]
Release Information Statement introduced in Junos OS Release 7.4.
Support at the[edit interfacesinterface-nameppp-options] hierarchy level addedinJunos
OS Release 8.3.
Description For LSQPICs or link PICs in redundant LSQconfigurations, you can inhibit the router from
sending PPP termination-request messages to the remote host if the PIC fails.
Required Privilege
Level
interfaceTo viewthis statement in the configuration.
interface-controlTo add this statement to the configuration.
Related
Documentation
Configuring Link PIC Failover on Channelized OC3 IQand IQE Interfaces
Configuring Link PIC Failover on Channelized OC12/STM4 IQand IQE Interfaces
Configuring Link PIC Failover on Channelized STM1 Interfaces on page 21
Junos OS Services Interfaces Library for Routing Devices
paired-group
Syntax paired-group group-name;
Hierarchy Level [edit interfaces interface-name sonet-options aps]
Release Information Statement introduced before Junos OS Release 7.4.
Description Configure load sharing between two working protect circuit pairs.
Options group-nameCircuits groupname, as configuredwiththeprotect-circuit or working-circuit
statement.
Required Privilege
Level
interfaceTo viewthis statement in the configuration.
interface-controlTo add this statement to the configuration.
Related
Documentation
Configuring APS Load Sharing
working-circuit on page 77
Copyright 2014, Juniper Networks, Inc. 68
Channelized STM1 Interfaces Feature Guide for Routing Devices
partition
Syntax partition partition-number oc-slice oc-slice-range interface-type type timeslots
time-slot-range;
Hierarchy Level [edit interfaces interface-name]
Release Information Statement introduced before Junos OS Release 7.4.
Description For IQinterfaces and J Series interfaces on the Dual-Port Channelized E1 and T1PIM,
configure the channelized interface partition. The partition number is correlated with the
channel number. Partition and channel numbering on IQinterfaces begins with :1, not :0.
Default If you omit this statement, the channelized PIC or PIMis not partitioned, and no data
channels are configured.
Options partition-numberSublevel interface partition index.
Range:
1 through 4 for an OC3 interface on a channelized OC12 IQinterface.
1 through 12 for a T3 interface on a channelized OC12 IQinterface.
1 through 4 for a T3 interface on a channelized T3 IQinterface.
1 through28for aT1 IQinterfaceonachannelizedOC12IQor channelizedT3IQinterface.
1 through 10 for an E1 interface on a channelized E1 IQinterface.
1 through 30 on a channelized E1 interface.
1 through 23 on a channelized T1 interface.
1 through 24 for NxDS0 interfaces on either channelized OC12 IQor channelized DS3
IQinterfaces.
0 through 31(with 0 reserved for framing) for NxDS0 interfaces on channelized E1 IQ
interfaces.
The remaining statements are explained separately.
Required Privilege
Level
interfaceTo viewthis statement in the configuration.
interface-controlTo add this statement to the configuration.
Related
Documentation
Channelized E1 IQand IQE Interfaces Overview
Channelized OC12/STM4 IQand IQE Interfaces Overview
Configuring Channelized T3 IQInterfaces
no-partition on page 67
69 Copyright 2014, Juniper Networks, Inc.
Chapter 4: Statement Summary
protect-circuit
Syntax protect-circuit group-name;
Hierarchy Level [edit interfaces interface-name sonet-options aps]
Release Information Statement introduced before Junos OS Release 7.4.
Description Configure the protect router in an APS circuit pair. When the working interface fails, APS
brings up the protection circuit and the traffic is moved to the protection circuit.
Options group-nameCircuits group name.
Required Privilege
Level
interfaceTo viewthis statement in the configuration.
interface-controlTo add this statement to the configuration.
Related
Documentation
Configuring Basic Automatic Protect Switching
working-circuit on page 77
request
Syntax request (protect | working);
Hierarchy Level [edit interfaces interface-name sonet-options aps]
Release Information Statement introduced before Junos OS Release 7.4.
Description Performa manual switch between the protect and working circuits. This statement is
honored only if there are no higher-priority reasons to switch.
Options protectRequest that the circuit become the protect circuit.
workingRequest that the circuit become the working circuit.
Required Privilege
Level
interfaceTo viewthis statement in the configuration.
interface-controlTo add this statement to the configuration.
Related
Documentation
Configuring Switching Between the Working and Protect Circuits
force on page 59
Copyright 2014, Juniper Networks, Inc. 70
Channelized STM1 Interfaces Feature Guide for Routing Devices
revert-time (Interfaces)
Syntax revert-time seconds;
Hierarchy Level [edit interfaces interface-name sonet-options aps]
Release Information Statement introduced before Junos OS Release 7.4.
Description Configure APS revertive mode.
Default APS operates in nonrevertive mode.
Options secondsAmount of time to wait after the working circuit has again become functional
before making the working circuit active again.
Range: 1 through 65,535 seconds
Default: None (APS operates in nonrevertive mode)
Required Privilege
Level
interfaceTo viewthis statement in the configuration.
interface-controlTo add this statement to the configuration.
Related
Documentation
Configuring Revertive Mode
71 Copyright 2014, Juniper Networks, Inc.
Chapter 4: Statement Summary
sonet-options
Syntax sonet-options {
aps {
advertise-interval milliseconds;
annex-b
authentication-key key;
(break-before-make | no-break-before-make);
fast-aps-switch;
force;
hold-time milliseconds;
lockout;
neighbor address;
paired-group group-name;
protect-circuit group-name;
request;
revert-time seconds;
switching-mode (bidirectional | unidirectional);
working-circuit group-name;
}
bytes {
c2 value;
e1-quiet value;
f1 value;
f2 value;
s1 value;
z3 value;
z4 value;
}
fcs (16 | 32);
loopback (local | remote);
mpls {
pop-all-labels {
required-depth number;
}
}
path-trace trace-string;
(payload-scrambler | no-payload-scrambler);
rfc-2615;
trigger {
defect ignore;
defect hold-time up milliseconds down milliseconds;
}
}
vtmapping (itu-t | klm);
(z0-increment | no-z0-increment);
Hierarchy Level [edit interfaces interface-name]
Release Information Statement introduced before Junos OS Release 7.4.
Description Configure SONET/SDH-specific interface properties.
Copyright 2014, Juniper Networks, Inc. 72
Channelized STM1 Interfaces Feature Guide for Routing Devices
OnSONET/SDHOC48interfaces that youconfigure for channelized(multiplexed) mode
(by including the no-concatenate statement at the [edit chassis fpc slot-number pic
pic-number] hierarchy level), the bytes e1-quiet and bytes f1 options have no effect. The
bytes f2, bytes z3, bytes z4, and path-trace options work correctly on channel 0 and work
in the transmit direction only on channels 1, 2, and 3.
On a channelized OC12 interface, the bytes e1-quiet, bytes f1, bytes f2, bytes z3, and bytes
z4 options are not supported. The fcs and payload-scrambler statements are also not
supported; you must configure these for each DS3 channel using the t3-options fcs and
t3-optionspayload-scrambler statements. Theapsandloopbackstatementsaresupported
only on channel 0and are ignored if included in the configurations for channels 1 through
11. You can configure loopbacks for each DS3 channel with the t3-options loopback
statement. The path-trace statement can be included in the configuration for each DS3
channel, thereby configuring a unique path trace for each channel.
To configure loopback on channelized IQand IQE PICs, SONET/SDH level, use the
loopback statement local and remote options at the controller interface (coc48, cstm16,
coc12, cstm4, coc3, and cstm1). It is ignored for path-level interfaces so-fpc/pic/port or
so-fpc/pic/port:channel.
If youarerunningIntermediateSystem-to-IntermediateSystem(IS-IS) over SONET/SDH
interfaces, use PPP if you are running Cisco IOS Release 12.0 or later. If you need to run
HDLC, configure an ISOfamily MTU of 4469 on the router.
The statements are explained separately.
Required Privilege
Level
interfaceTo viewthis statement in the configuration.
interface-controlTo add this statement to the configuration.
Related
Documentation
Configuring SONET/SDH Parameters on ATMInterfaces
Channelized OC12/STM4 IQand IQE Interfaces Overview
Channelized STM1 Interfaces Overviewon page 3
SONET/SDH Physical Interface Properties Overview
no-concatenate
73 Copyright 2014, Juniper Networks, Inc.
Chapter 4: Statement Summary
start-end-flag
Syntax start-end-flag (filler | shared);
Hierarchy Level [edit interfaces e1-fpc/pic/port],
[edit interfaces t1-fpc/pic/port],
[edit interfaces interface-name ds0-options],
[edit interfaces interface-name e1-options],
[edit interfaces interface-name e3-options],
[edit interfaces interface-name t1-options],
[edit interfaces interface-name t3-options]
Release Information Statement introduced before Junos OS Release 7.4.
Statement introduced in Junos OS Release 12.2 for the ACX Series Universal Access
Routers.
Description For DS0, E1, E3, T1, and T3 interfaces, configure the interface to share the transmission
of start and end flags.
NOTE: WhenconfiguringE1 or T1 interfaces onthe10-port ChannelizedE1/T1
IQE PIC, the start-end-flag statement must be included at the [edit interfaces
e1-fpc/pic/port] or [edit interfaces t1-fpc/pic/port] hierarchy level as
appropriate.
Options fillerWait two idle cycles between the start and end flags.
sharedShare the transmission of the start and end flags. This is the default.
Required Privilege
Level
interfaceTo viewthis statement in the configuration.
interface-controlTo add this statement to the configuration.
Related
Documentation
Configuring E1 Start and End Flags
Configuring the E3 Start and End Flags
Configuring T1 Start and End Flags
Configuring T3 Start and End Flags
Copyright 2014, Juniper Networks, Inc. 74
Channelized STM1 Interfaces Feature Guide for Routing Devices
switching-mode
Syntax switching-mode (bidirectional | unidirectional);
Hierarchy Level [edit interfaces interface-name sonet-options aps]
Release Information Statement introduced before Junos OS Release 7.4.
Description For unchannelized OC3, OC12, and OC48 SONET/SDH interfaces on T Series routers
only, configuretheinterfacetointeroperatewithSONET/SDHline-terminatingequipment
(LTE) that is provisioned for unidirectional linear APS in 1+1 architecture.
Default If the switching-mode statement is not configured, the mode is bidirectional, and the
interface does not interoperate with a unidirectional SONET/SDH LTE.
Options bidirectionalSupport bidirectional mode only.
unidirectionalInteroperatewithaSONET/SDHLTEprovisionedfor unidirectional mode.
Required Privilege
Level
interfaceTo viewthis statement in the configuration.
interface-controlTo add this statement to the configuration.
Related
Documentation
Configuring Switching Mode
75 Copyright 2014, Juniper Networks, Inc.
Chapter 4: Statement Summary
timeslots
Syntax timeslots time-slot-range;
Hierarchy Level [edit interfaces e1-fpc/pic/port],
[edit interfaces t1-fpc/pic/port],
[edit interfaces interface-name e1-options],
[edit interfaces interface-name partition partition-number],
[edit interfaces interface-name t1-options]
Release Information Statement introduced before Junos OS Release 7.4.
Description For E1 and T1interfaces, allocate the specific time slots by number.
NOTE: WhenconfiguringE1 or T1 interfaces onthe10-port ChannelizedE1/T1
IQE PIC, the timeslots statement must be included at the [edit interfaces
e1-fpc/pic/port] or [edit interfaces t1-fpc/pic/port] hierarchy level as
appropriate.
Options time-slot-rangeActual time slot numbers allocated:
Range: Ranges vary by interface type and configuration option as follows:
1 through 24 for T1 interfaces (0 is reserved)
1 through 31 for 4-port E1 PICs (0 is reserved)
1 through 31 for NxDS0 interfaces (0 is reserved)
2 through 32 for 10-port Channelized E1 and 10-port Channelized E1 IQPICs (1 is
reserved)
2through32for thesettingunder e1-options withIQEPICs (1 is reserved) (whencreating
fractional E1)
1 through 31 for the setting under partition with IQE PICs (0is reserved) (when creating
NxDS0)
NOTE: When creating fractional E1 interfaces only, if you connect a 4-port
E1 PICinterface to a device that uses time slot numbering from2 through 32,
you must subtract 1 fromthe configured number of time slots.
Required Privilege
Level
interfaceTo viewthis statement in the configuration.
interface-controlTo add this statement to the configuration.
Related
Documentation
Configuring Fractional E1 IQand IQE Interfaces
Configuring Fractional T1 IQand IQE Interfaces
Copyright 2014, Juniper Networks, Inc. 76
Channelized STM1 Interfaces Feature Guide for Routing Devices
Configuring Fractional E1 Time Slots
Configuring Fractional T1 Time Slots
Configuring a Channelized T1/E1 Interface to Drop and Insert Time Slots
vtmapping
Syntax vtmapping (itu-t | klm);
Hierarchy Level [edit interfaces interface-name sonet-options];
[edit chassis fpc number pic number]
Release Information Statement introduced before Junos OS Release 7.4.
Description For the Channelized STM1 IQPIC or Channelized STM1 PIC, configure virtual tributary
mapping.
For theChannelizedSTM1 PIC, youconfigurevirtual tributary mappingat the[edit chassis
fpc number pic number] hierarchy level.
Options itu-tInternational Telephony Union standard.
klmKLMstandard.
Default: klm
Required Privilege
Level
interfaceTo viewthis statement in the configuration.
interface-controlTo add this statement to the configuration.
Related
Documentation
Configuring Virtual Tributary Mapping of Channelized STM1 Interfaces on page 14
ConfiguringtheJunos OStoSupport ChannelizedSTM1 InterfaceVirtual Tributary Mapping
working-circuit
Syntax working-circuit group-name;
Hierarchy Level [edit interfaces interface-name sonet-options aps]
Release Information Statement introduced before Junos OS Release 7.4.
Description Configure the working router in an APS circuit pair.
Options group-nameCircuits group name.
Required Privilege
Level
interfaceTo viewthis statement in the configuration.
interface-controlTo add this statement to the configuration.
Related
Documentation
Configuring Basic Automatic Protect Switching
protect-circuit on page 70
77 Copyright 2014, Juniper Networks, Inc.
Chapter 4: Statement Summary
Copyright 2014, Juniper Networks, Inc. 78
Channelized STM1 Interfaces Feature Guide for Routing Devices
PART 3
Administration
Monitoring Commands on page 81
Command Summaries on page 97
79 Copyright 2014, Juniper Networks, Inc.
Copyright 2014, Juniper Networks, Inc. 80
Channelized STM1 Interfaces Feature Guide for Routing Devices
CHAPTER 5
Monitoring Commands
showinterfaces (Channelized STM1)
81 Copyright 2014, Juniper Networks, Inc.
showinterfaces (Channelized STM1)
Syntax showinterfaces e1-fpc/pic/port:e1channel
<brief | detail | extensive | terse>
<descriptions>
<media>
<snmp-index snmp-index>
<statistics>
Release Information Command introduced before Junos OS Release 7.4.
Description (MSeries and T Series routers only) Display status information about the specified
channelized STM1 interface.
Options e1-fpc/pic/port:e1channelDisplay standard status information about the specified
channelized STM1 interface.
brief | detail | extensive | terse(Optional) Display the specified level of output.
descriptions(Optional) Display interface description strings.
media(Optional) Display media-specific information about network interfaces.
snmp-index snmp-index(Optional) Display information for the specified SNMP index
of the interface.
statistics(Optional) Display static interface statistics.
Required Privilege
Level
view
List of Sample Output showinterfaces extensive (Channelized STM1, SDH) on page 93
Output Fields Table 5 on page 82 lists the output fields for the showinterfaces (all Channelized STM1
interfaces) command. Output fields are listed in the approximate order in which they
appear.
Table 5: Channelized STM1 showinterfaces Output Fields
Level of Output Field Description Field Name
Physical Interface
All levels Name of the physical interface. Physical interface
All levels State of the interface. Possible values are described in the Enabled Field
section under Common Output Fields Description.
Enabled
detail extensive none Physical interface's index number, which reflects its initialization sequence. Interface index
detail extensive none SNMP index number for the physical interface. SNMP ifIndex
detail extensive Unique number for use by Juniper Networks technical support only. Generation
Copyright 2014, Juniper Networks, Inc. 82
Channelized STM1 Interfaces Feature Guide for Routing Devices
Table 5: Channelized STM1 showinterfaces Output Fields (continued)
Level of Output Field Description Field Name
All levels Encapsulation being used on the physical interface. Link-level type
All levels MTU size on the physical interface. MTU
All levels Reference clock source. It can be Internal or External. Clocking
All levels Speed at which the interface is running. Speed
All levels Whether loopback is enabled and the type of loopback (local or remote). Loopback
All levels Frame check sequence on the interface (either 16 or 32). The default is 16 bits. FCS
All levels Physical layer framing format used on the link. It can be G704, G704-NO-CRC4,
or Unframed. The default is G704.
Framing
All levels (ChannelizedSTM1 IQinterfaces only) Nameandinterfaceindex of theinterface
to which a particular child interface belongs. None indicates that this interface
is the top level.
Parent
All levels Information about the physical device. Possible values are described in the
Device Flags section under Common Output Fields Description.
Device flags
All levels Information about the interface. Possible values are described in the Interface
Flags section under Common Output Fields Description.
Interface flags
All levels Information about the link. Possible values are described in the Link Flags
section under Common Output Fields Description.
Link flags
detail extensive Current interface hold-time up and hold-time down, in milliseconds. Hold-times
detail extensive none (PPP and HDLC) Configured settings for keepalives.
intervalsecondsThetimeinseconds betweensuccessivekeepaliverequests.
Therangeis 10seconds through32,767 seconds, withadefault of 10 seconds.
down-count numberThe number of keepalive packets a destination must
fail to receive before the network takes a link down. The range is1 through
255, with a default of 3.
up-count numberThenumber of keepalivepacketsadestinationmust receive
to change a links status fromdown to up. The range is 1 through 255, with a
default of 1.
Keepalive settings
83 Copyright 2014, Juniper Networks, Inc.
Chapter 5: Monitoring Commands
Table 5: Channelized STM1 showinterfaces Output Fields (continued)
Level of Output Field Description Field Name
detail extensive none (PPP and HDLC) Information about keepalive packets.
InputNumber of keepalive packets received by PPP.
(last seen 00:00:00ago)Time since the last keepalive packet was
received, in the formathh:mm:ss.
OutputNumber of keepalive packets sent by PPPandhowlong agothe last
keepalive packets were sent and received.
(last seen 00:00:00ago)Time since the last keepalive packet was sent,
in the format hh:mm:ss.
Keepalive statistics
detail extensive none (Frame Relay) Local Management Interface settings. The format is (ANSI or
ITU) LMI settings: value, value... xx seconds, where value can be:
n391dteDTE full status polling interval (1- 255)
n392dceDCE error threshold (1-10)
n392dteDTE error threshold (1-10)
n393dceDCE monitored event count (1-10)
n393dteDTE monitored event count (1-10)
t391dteDTE polling timer (5-30 seconds)
t392dceDCE polling verification timer (5-30 seconds)
ANSI LMI settingsor
ITULMI settings
detail extensive none (Frame Relay) Statistics about the link management.
InputNumber of packets coming in on the interface (nn) and howmuch
time has passed since the last packet arrived. The format is Input: nn (last
seen hh:mm:ss ago).
OutputNumber of packets sent out on the interface (nn) and howmuch
time has passedsince the last packet was sent. The format is Output: nn(last
seen hh:mm:ss ago).
LMI
detail extensive none (Frame Relay) Statistics about messages transmitted fromthe data terminal
equipment (DTE) to the data circuit-terminating equipment (DCE):
EnquiriessentNumber of link status enquiries sent fromtheDTEtotheDCE.
Full enquiries sentNumber of full enquiries sent fromthe DTE to the DCE.
Enquiry responses receivedNumber of enquiry responses received by the
DTE fromthe DCE.
Full enquiry responses receivedNumber of full enquiry responses sent from
the DTE to the DCE.
DTE statistics
detail extensive none (Frame Relay) Statistics about messages transmittedfromthe DCEtothe DTE:
Enquiries receivedNumber of enquiries received by the DCE fromthe DTE.
Full enquiries receivedNumber of full enquiries received by the DCE from
the DTE.
Enquiry responses sentNumber of enquiry responses sent fromthe DCE to
the DTE.
Full enquiry responses sentNumber of full enquiry responses sent fromthe
DCE to the DTE.
DCE statistics
Copyright 2014, Juniper Networks, Inc. 84
Channelized STM1 Interfaces Feature Guide for Routing Devices
Table 5: Channelized STM1 showinterfaces Output Fields (continued)
Level of Output Field Description Field Name
detail extensive none (Frame Relay) Statistics about messages sent between the DTE and the DCE:
Unknown messages receivedNumber of received packets that do not fall
into any category.
AsynchronousupdatesreceivedNumber of linkstatus peer changes received.
Out-of-sequencepacketsreceivedNumber of packetsfor whichthesequence
of the packets received is different fromthe expected sequence.
Keepalive responses timedoutNumber of keepalive responses that timed
out when no LMI packet was reported for n392dte or n393dce intervals. (See
LMI settings.)
Common statistics
detail extensive none (Frame Relay, displayed only fromthe DTE) Number of DLCIs configured from
the DCE.
Nonmatching
DCE-end DLCIs
detail extensive none (PPP) Link Control Protocol state.
Conf-ack-receivedAcknowledgement was received.
Conf-ack-sentAcknowledgement was sent.
Conf-req-sentRequest was sent.
DownLCP negotiation is incomplete (not yet completed or has failed).
Not-configuredLCP is not configured on the interface.
OpenedLCP negotiation is successful.
LCP state
detail extensive none (PPP) Network Control Protocol state.
Conf-ack-receivedAcknowledgement was received.
Conf-ack-sentAcknowledgement was sent.
Conf-req-sentRequest was sent.
DownNCP negotiation is incomplete (not yet completed or has failed).
Not-configuredNCP is not configured on the interface.
OpenedNCP negotiation is successful.
NCP state
detail extensive none (PPP) Displays the state of the Challenge Handshake Authentication Protocol
(CHAP) during its transaction.
Chap-Chal-receivedChallenge was received but response not yet sent.
Chap-Chal-sentChallenge was sent.
Chap-Resp-receivedResponse was received for the challenge sent, but
CHAP has not yet moved into the Success state. (Most likely with RADIUS
authentication.)
Chap-Resp-sentResponse was sent for the challenge received.
ClosedCHAP authentication is incomplete.
FailureCHAP authentication failed.
Not-configuredCHAP is not configured on the interface.
SuccessCHAP authentication was successful.
CHAP state
detail extensive none Date, time, and howlong ago the interface went fromdown to up. The format
is Last flapped: year-month-day hour:minute:secondtimezone(hour:minute:second
ago). For example, Last flapped: 2002-04-26 10:52:40PDT (04:33:20ago).
Last flapped
85 Copyright 2014, Juniper Networks, Inc.
Chapter 5: Monitoring Commands
Table 5: Channelized STM1 showinterfaces Output Fields (continued)
Level of Output Field Description Field Name
detail extensive Time when the statistics for the interface were last set to zero. Statistics last
cleared
detail extensive Number andrate of bytes andpackets receivedandtransmittedonthe physical
interface.
Input bytesNumber of bytes received on the interface.
Output bytesNumber of bytes transmitted on the interface.
Input packetsNumber of packets received on the interface.
Output packetsNumber of packets transmitted on the interface.
Traffic statistics
extensive Input errors on the interface. The following paragraphs explain the counters
whose meaning might not be obvious:
ErrorsSumof the incoming frame aborts and FCS errors.
DropsNumber of packets dropped by the input queue of the I/OManager
ASIC. If the interface is saturated, this number increments once for every
packet that is dropped by the ASIC's RED mechanism.
Framing errorsNumber of packets received with an invalid frame checksum
(FCS).
Policed discardsNumber of frames that the incoming packet match code
discarded because they were not recognized or not of interest. Usually, this
field reports protocols that the Junos OS does not handle.
L3 incompletesNumber of incoming packets discarded because they failed
Layer 3 (usually IPv4) sanity checks of the header. For example, a frame with
less than 20 bytes of available IP header is discarded.
L2 channel errorsNumber of times the software did not find a valid logical
interface for an incoming frame.
L2 mismatch timeoutsNumber of malformed or short packets that caused
the incoming packet handler to discard the frame as unreadable.
HS link CRC errorsNumber of errors on the high-speed links between the
ASICs responsible for handling the router interfaces.
SRAMerrorsNumber of hardware errors that occurred in the static RAM
(SRAM) on the PIC. If the value of this field increments, the PIC is
malfunctioning.
Input errors
Copyright 2014, Juniper Networks, Inc. 86
Channelized STM1 Interfaces Feature Guide for Routing Devices
Table 5: Channelized STM1 showinterfaces Output Fields (continued)
Level of Output Field Description Field Name
extensive Output errors on the interface. The following paragraphs explain the counters
whose meaning might not be obvious:
Carrier transitionsNumber of times the interface has gone fromdown to up.
This number does not normally increment quickly, increasing only when the
cable is unplugged, the far-end systemis powered down and then up, or
another problemoccurs. If thenumber of carrier transitions increments quickly
(perhaps once every 10 seconds), the cable, the far-end system, or the PIC
is malfunctioning.
ErrorsSumof the outgoing frame aborts and FCS errors.
DropsNumber of packets dropped by the output queue of the I/OManager
ASIC. If the interface is saturated, this number increments once for every
packet that is dropped by the ASIC's RED mechanism.
Aged packetsNumber of packets that remained in shared packet SDRAM
so long that the systemautomatically purged them. The value in this field
should never increment. If it does, it is most likely a software bug or possibly
malfunctioning hardware.
Output errors
detail extensive none E1 media-specific defects that can prevent the interface frompassing packets.
When a defect persists for a certain period, it is promoted to an alarm. Based
on the router configuration, an alarmcan ring the red or yellowalarmbell on
the router, or turn on the red or yellowalarmLED on the craft interface. The
following lists all possible alarms and defects. For complete explanations of
most of these alarms and defects, see Bellcore Telcordia GR-499-CORE.
LOSLoss of signal.
LOFLoss of frame.
AISAlarmindication signal.
YLWYellowalarm. Indicates errors at the remote site receiver.
DS1 alarms
DS1 defects
All levels SDHmedia-specificdefects that canprevent theinterfacefrompassingpackets.
When a defect persists for a certain period, it is promoted to an alarm. Based
on the router configuration, an alarmcan ring the red or yellowalarmbell on
the router or light the red or yellowalarmLED on the craft interface. See these
fields for possible alarms and defects: SDH PHY, SDH regenerator section,
SDH multiplex section, and SDH path.
NOTE: For controller-based SONET PICs, the SDH alarms and SDH defects
output in the showinterface cstm1 extensive command output only shows the
section and line level defects. The path level defects can be found under the
SONET (so) interface output.
SDHalarms
SDHdefects
87 Copyright 2014, Juniper Networks, Inc.
Chapter 5: Monitoring Commands
Table 5: Channelized STM1 showinterfaces Output Fields (continued)
Level of Output Field Description Field Name
extensive Active alarms and defects, plus counts of specific E1 errors with detailed
information.
SecondsNumber of seconds the defect has been active.
CountNumber of times that the defect has gone frominactive to active.
StateState of the error. State other than OK indicates a problem.
Error types can be:
AISAlarmindication signal
BEEBit error
BESBit error seconds
BPVBipolar violation
CSCarrier state
ESErrored seconds
EXZExcessive zeros
FEBEFar-end block error
LCVLine code violation
LESLine error seconds
LOFLoss of frame
LOSLoss of signal
PCVPulse code violation
SEFSeverely errored framing
SEFS-SSeverely errored framing seconds (section)
SESSeverely errored seconds
UASUnavailable seconds
YELLOWErrors at the remote site receiver
E1 media
extensive Names of thetransmit queues andtheir associatedstatistics for eachE1 channel
on the Channelized STM1-to-E1 PIC.
B/WQueue bandwidth as a percentage of the total interface bandwidth.
WRRWeighted round-robin (in percent).
PacketsNumber of packets transmitted.
BytesNumber of bytes transmitted.
DropsNumber of packets dropped.
ErrorsNumber of packet errors.
Interface transmit
queues
extensive Information about the HDLC configuration.
Giant thresholdGiant threshold programmed into the hardware.
Runt thresholdRunt threshold programmed into the hardware.
TimeslotsConfigured time slots for the interface.
Line encodingLine encoding used. It is always HDB3.
HDLCconfiguration
Copyright 2014, Juniper Networks, Inc. 88
Channelized STM1 Interfaces Feature Guide for Routing Devices
Table 5: Channelized STM1 showinterfaces Output Fields (continued)
Level of Output Field Description Field Name
detail extensive none BERT (bit error rate test) checks the quality of the line. This output appears
only when a BERT is run on the interface.
BERT time periodConfigured total time period that the BERT is to run.
ElapsedActual time elapsed since the start of the BERT (in seconds).
Induced error rateConfigured rate at which the bit errors are induced in the
BERT pattern.
AlgorithmType of algorithmselected for the BERT.
DS1 BERT
configuration
extensive Active alarms and defects, plus counts of specific SDH errors with detailed
information.
SecondsNumber of seconds the defect has been active.
CountNumber of times that the defect has gone frominactive to active.
StateState of the error. State other than OK indicates a problem.
Subfields are:
PLL LockPhase-locked loop
PHY LightLoss of optical signal
SDHPHY
extensive Active alarms and defects, plus counts of specific SDH errors with detailed
information.
SecondsNumber of seconds the defect has been active.
CountNumber of times that the defect has gone frominactive to active.
StateState of the error. State other than OK indicates a problem.
Subfields are:
RS-BIP824-bit BIP for multiplex section overhead (B2 bytes)
OOFOut of frame
LOSLoss of signal
LOFLoss of frame
RS-ESErrored seconds (near-end regenerator section)
RS-SESSeverely errored seconds (near-end regenerator section)
RS-SEFSSeverely errored framing seconds (regenerator section)
SDHregenerator
section
89 Copyright 2014, Juniper Networks, Inc.
Chapter 5: Monitoring Commands
Table 5: Channelized STM1 showinterfaces Output Fields (continued)
Level of Output Field Description Field Name
extensive Active alarms and defects, plus counts of specific SDH errors with detailed
information.
SecondsNumber of seconds the defect has been active.
CountNumber of times that the defect has gone frominactive to active.
StateState of the error. State other than OK indicates a problem.
Subfields are:
MS-BIP248-bit BIP for high-order path overhead (B3 byte)
MS-FEBEFar-end block error (multiplex section)
MS-FERFFar-end remote fail (multiplex section)
MS-AISalarmindication signal (multiplex section)
BERR-SFBit error rate fault (signal failure)
BERR-SDBit error rate defect (signal degradation)
MS-ESErrored seconds (near-end multiplex section)
MS-SESSeverely errored seconds (near-end multiplex section)
MS-UASUnavailable seconds (near-end multiplex section)
MS-ES-FEErrored seconds (far-end multiplex section)
MS-SES-FESeverely errored seconds (far-end multiplex section)
MS-UAS-FEUnavailable seconds (far-end multiplex section)
SDHmultiplex
section
extensive Active alarms and defects, plus counts of specific SDH errors with detailed
information.
SecondsNumber of seconds the defect has been active.
CountNumber of times that the defect has gone frominactive to active.
StateState of the error. State other than OK indicates a problem.
Subfields are:
HP-BIP88-bit BIP for regenerator section overhead (B1 byte)
HP-FEBEFar-end block error (high-order path)
HP-LOPLoss of pointer (high-order path)
HP-AISHigh-order-path alarmindication signal
HP-FERFFar-end remote fail (high-order path)
HP-UNEQUnequipped (high-order path)
HP-PLMPayload label mismatch (high-order path)
HP-ESErrored seconds (near-end high-order path)
HP-SESSeverely errored seconds (near-end high-order path)
HP-UASUnavailable seconds (near-end high-order path)
HP-ES-FEErrored seconds (far-end high-order path)
HP-SES-FESeverely errored seconds (far-end high-order path)
HP-UAS-FEUnavailable seconds (far-end high-order path)
SDHpath
Copyright 2014, Juniper Networks, Inc. 90
Channelized STM1 Interfaces Feature Guide for Routing Devices
Table 5: Channelized STM1 showinterfaces Output Fields (continued)
Level of Output Field Description Field Name
extensive Activealarms anddefects, plus counts of specific SDHtributary unit (TU) errors
with detailed information.
SecondsNumber of seconds the defect has been active.
CountNumber of times that the defect has gone frominactive to active.
StateState of the error. State other than OK indicates a problem.
Subfields are:
TU-BIP-2Bit interleaved parity for SONET line overhead
TU-FEBE(near-end TU)
TU-LOPLoss of pointer (near-end TU)
TU-AISAlarmindication signal (near-end TU)
TU-FERF(near-end TU)
TU-UNEQUnequipped (near-end TU)
TU-PLMPayload label mismatch (near-end TU)
TU-ESErrored seconds (near-end TU)
TU-SESSeverely errored seconds (near-end TU)
TU-UASUnavailable seconds (near-end TU)
TU-ES-FEErrored seconds (far-end TU)
TU-SES-FESeverely errored seconds (far-end TU)
TU-UAS-FEUnavailable seconds (far-end TU)
SDHtu
extensive Values of the received and transmitted SONET overhead:
C2Signal label. Allocated to identify the construction and content of the
STS-level SPE and for PDI-P.
F1Sectionuser channel byte. This byte is set aside for the purposes of users.
K1 and K2These bytes are allocated for APS signaling for the protection of
the multiplex section.
J0Section trace. This byte is defined for STS-1 number 1 of an STS-Nsignal.
Used to transmit a 1-byte fixed-length string or a 16-byte message so that a
receiving terminal in a section can verify its continued connection to the
intended transmitter.
S1Synchronization status. The S1 byte is located in the first STS-1 of an
STS-N signal.
Z3 and Z4Allocated for future use.
Received SDH
overhead
Transmitted SDH
overhead
extensive Channelized OC12 interfaces allowpath trace bytes to be sent inband across
the SONET/SDH link. The received path trace value is the message received
fromthe router at the other end of the fiber. The transmitted path trace value
is the message that this router transmits. This information is specific to each of
the 12 channelized OC12 interfaces.
Receivedpathtrace
Transmitted path
trace
extensive Information about the configuration of the Packet Forwarding Engine:
Destination slotFPC slot number.
PLP bytePacket Level Protocol byte.
Packet Forwarding
Engine
configuration
91 Copyright 2014, Juniper Networks, Inc.
Chapter 5: Monitoring Commands
Table 5: Channelized STM1 showinterfaces Output Fields (continued)
Level of Output Field Description Field Name
extensive Information about the CoS queue for the physical interface.
CoS transmit queueQueue number and its associated user-configured
forwarding class name.
Bandwidth %Percentage of bandwidth allocated to the queue.
Bandwidth bpsBandwidth allocated to the queue (in bps).
Buffer %Percentage of buffer space allocated to the queue.
Buffer usecAmount of buffer spaceallocatedtothequeue, inmicroseconds.
This value is nonzero only if the buffer size is configured in terms of time.
PriorityQueue priority: low or high.
LimitDisplayed if rate limiting is configured for the queue. Possible values
are none and exact. If exact is configured, the queue transmits only up to the
configured bandwidth, even if excess bandwidth is available. If none is
configured, the queue transmits beyond the configured bandwidth if
bandwidth is available.
CoS information
Logical Interface
All levels Name of the logical interface. Logical interface
All levels State of the interface. Possible values are described in the Enabled Field
section under Common Output Fields Description.
Enabled
detail extensive none Logical interface index number, which reflects its initialization sequence. Index
detail extensive none Logical interface SNMP interface index number. SNMP ifIndex
All levels Information about the logical interface. Possible values are described in the
Logical Interface Flags section under Common Output Fields Description.
Flags
All levels Encapsulation on the logical interface. Encapsulation
detail extensive none Protocol family configured on the logical interface, such as iso, inet6, or mpls. Protocol
detail extensive Unique number for use by Juniper Networks technical support only. Generation
detail extensive Routing table in which the logical interface address is located. For example, 0
refers to the routing table inet.0.
Route table
detail extensive none Information about the protocol family flags. Possible values are described in
the Family Flags section under Common Output Fields Description.
Flags
detail extensive none Information about the address flags. Possible values are described in the
Addresses Flags section under Common Output Fields Description.
Addresses, Flags
detail extensive none IP address of the remote side of the connection. Destination
Copyright 2014, Juniper Networks, Inc. 92
Channelized STM1 Interfaces Feature Guide for Routing Devices
Table 5: Channelized STM1 showinterfaces Output Fields (continued)
Level of Output Field Description Field Name
detail extensive none IP address of the logical interface. Local
detail extensive none Broadcast address. Broadcast
detail extensive none (Frame Relay) DLCI number of the logical interface. The following DLCI
informationis displayed: Flags, Total downtime, Last down, andTrafficstatistics.
Flags is one or more of the following:
ActiveSet when the link is active and the DTE and DCE are exchanging
information.
DownSet when the link is active, but no information is received fromthe
DCE.
UnconfiguredSet whenthecorrespondingDLCI intheDCEis not configured.
ConfiguredSet when the corresponding DLCI in the DCE is configured.
Dce-configuredDisplayed when the command is issued fromthe DTE.
DLCI
detail extensive none (Frame Relay) Data-link connection identifier (DLCI) statistics.
Active DLCINumber of active DLCIs.
Inactive DLCINumber of inactive DLCIs.
DLCI statistics
Sample Output
showinterfaces extensive (Channelized STM1, SDH)
user@host> showinterfaces e1-1/0/0:1 extensive
Physical interface: e1-1/0/0:1, Enabled, Physical link is Up
Interface index: 148, SNMP ifIndex: 285, Generation: 2915
Link-level type: Frame-relay, MTU: 1504, SDH mode, Speed: E1, Loopback: None,
FCS: 16, Framing: G704
Device flags : Present Running
Interface flags: Point-To-Point SNMP-Traps
Link flags : Keepalives DTE
ANSI LMI settings: n391dte 6, n392dte 3, n393dte 4, t391dte 10 seconds
LMI: Input: 51700 (00:00:02 ago), Output: 51701 (00:00:02 ago)
DTE statistics:
Enquiries sent : 43186
Full enquiries sent : 8515
Enquiry responses received : 43185
Full enquiry responses received : 8515
DCE statistics:
Enquiries received : 0
Full enquiries received : 0
Enquiry responses sent : 0
Full enquiry responses sent : 0
Common statistics:
Unknown messages received : 0
Asynchronous updates received : 0
Out-of-sequence packets received : 0
Keepalive responses timedout : 0
Nonmatching DCE-end DLCIs:
2
Hold-times : Up 0 ms, Down 0 ms
93 Copyright 2014, Juniper Networks, Inc.
Chapter 5: Monitoring Commands
Last flapped : 2002-05-23 17:02:59 PDT (17:23:45 ago)
Statistics last cleared: Never
Traffic statistics:
Input bytes : 592 48 bps
Output bytes : 644 48 bps
Input packets: 46 0 pps
Output packets: 46 0 pps
Input errors:
Errors: 0, Drops: 9, Framing errors: 0, Policed discards: 0,
L3 incompletes: 0, L2 channel errors: 11, L2 mismatch timeouts: 0,
HS link CRC errors: 0, SRAM errors: 0
Output errors:
Carrier transitions: 1, Errors: 0, Drops: 0, Aged packets: 0
DS1 alarms : None
DS1 defects : None
SDH alarms : None
SDH defects : None
E1 media: Seconds Count State
SEF 0 0 OK
BEE 0 0 OK
AIS 124 1 OK
LOF 124 1 OK
LOS 0 0 OK
YELLOW 0 0 OK
BPV 0 0
EXZ 0 0
LCV 0 0
PCV 0 0
CS 0 0
FEBE 0 0
LES 124
ES 125
SES 124
SEFS 124
BES 0
UAS 37
Interface transmit queues:
B/W WRR Packets Bytes Drops Errors
Queue0 95 95 0 0 0 0
Queue1 5 5 529 6348 0 0
HDLC configuration:
Giant threshold: 0, Runt threshold: 0
Timeslots : All active
Line encoding: HDB3
DS1 BERT configuration:
BERT time period: 10 seconds, Elapsed: 0 seconds
Induced Error rate: 10e-0, Algorithm: 2^15 - 1, O.151, Pseudorandom (9)
SDH PHY: Seconds Count State
PLL Lock 0 0 OK
PHY Light 0 0 OK
SDH regenerator section:
RS-BIP8 0 0
OOF 125 1 OK
LOS 125 1 OK
LOF 125 1 OK
RS-ES 125
RS-SES 125
RS-SEFS 125
SDH multiplex section:
MS-BIP24 0 0
MS-FEBE 0 0
Copyright 2014, Juniper Networks, Inc. 94
Channelized STM1 Interfaces Feature Guide for Routing Devices
MS-FERF 0 0 OK
MS-AIS 125 1 OK
BERR-SF 0 0 OK
BERR-SD 0 0 OK
MS-ES 125
MS-SES 125
MS-UAS 115
MS-ES-FE 0
MS-SES-FE 0
MS-UAS-FE 0
SDH path:
HP-BIP8 0 0
HP-FEBE 0 0
HP-LOP 0 0 OK
HP-AIS 125 1 OK
HP-FERF 0 0 OK
HP-UNEQ 0 0 OK
HP-PLM 125 1 OK
HP-ES 125
HP-SES 125
HP-UAS 115
HP-ES-FE 0
HP-SES-FE 0
HP-UAS-FE 0
SDH tu:
TU-BIP2 0 0
TU-FEBE 124 1
TU-LOP 0 0 OK
TU-AIS 124 1 OK
TU-FERF 124 1 OK
TU-UNEQ 0 0 OK
TU-PLM 124 1 OK
TU-ES 125
TU-SES 125
TU-UAS 115
TU-ES-FE 0
TU-SES-FE 0
TU-UAS-FE 0
Received SDH overhead:
F1 : 0x00, J0 : 0x00, K1 : 0x00, K2 : 0x00
S1 : 0x00, C2 : 0x02, C2(cmp) : 0x02, F2 : 0x00
Z3 : 0x00, Z4 : 0x00, S1(cmp) : 0x00, V5 : 0x02
V5(cmp) : 0x02
Transmitted SDH overhead:
F1 : 0x00, J0 : 0x00, K1 : 0x00, K2 : 0x00
S1 : 0x00, C2 : 0x02, F2 : 0x00, Z3 : 0x00
Z4 : 0x00, V5 : 0x02
Received path trace:
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
Transmitted path trace:
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
Packet Forwarding Engine configuration:
Destination slot: 1, PLP byte: 2 (0x07)
CoS information:
CoS transmit queue Bandwidth Buffer Priority Limit
% bps % usec
0 best-effort 95 1945600 95 0 low none
3 network-control 5 102400 5 0 low none
Logical interface e1-1/0/0:1.0 (Index 10) (SNMP ifIndex 369) (Generation 496)
Flags: Point-To-Point SNMP-Traps Encapsulation: PPP
Protocol inet, MTU: 1500, Generation: 575, Route table: 0
95 Copyright 2014, Juniper Networks, Inc.
Chapter 5: Monitoring Commands
Flags: None
Addresses, Flags: Is-Preferred Is-Primary
Destination: 19.19.19.3, Local: 19.19.19.4, Broadcast: Unspecified,
Generation: 975
DLCI 100
Flags: Active, Dce-configured
Total down time: 0 sec, Last down: Never
Traffic statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
DLCI statistics:
Active DLCI :2 Inactive DLCI : 0
Copyright 2014, Juniper Networks, Inc. 96
Channelized STM1 Interfaces Feature Guide for Routing Devices
CHAPTER 6
Command Summaries
Channelized E1 Interface Operational Mode Commands on page 97
Channelized OC Interface Operational Commands on page 98
Channelized STM1 Interface Operational Mode Commands on page 98
Channelized T1 and T3 Interface Operational Mode Commands on page 99
Channelized E1 Interface Operational Mode Commands
Table 6 on page 97 summarizes the command-line interface (CLI) commands that you
can use to monitor and troubleshoot channelized E1 interfaces. Commands are listed in
alphabetical order.
Table 6: Channelized E1 Interface Operational Mode Commands
Command Task
showinterfaces (Channelized E1) Display status information about channelized E1
interfaces.
showinterfaces (Channelized E1 IQ) Display channelized E1 IQinterface information.
showinterfaces controller (Channelized
E1 IQ)
Display theinterfacenames of thephysical channelized
E1 IQinterface and the channels configured on each
interface.
NOTE: For more information about the channel type and level of
channelization, and for information about the number of channels that are
supportedonthechannelizedE1 interface, seetheJunosOSNetworkInterfaces
Library for Routing Devices.
For channelization illustrations and configuration examples for channelized
IQinterfaces, see the Junos Feature Guide.
97 Copyright 2014, Juniper Networks, Inc.
Channelized OC Interface Operational Commands
Table7 onpage98summarizes thecommand-lineinterface(CLI) commands tomonitor
and troubleshoot channelized OCinterfaces. Commands are listed in alphabetical order.
Table 7: Channelized OC Interface Operational Mode Commands
CLI Command Task or Information to Monitor
showinterfaces (ChannelizedOC3IQand
IQE)
Display channelized OC3 IQand IQE interface
information.
showinterfaces (Channelized OC12) Display status information about channelized OC12
interfaces.
showinterfaces (Channelized OC12 IQ
and IQE)
Display channelized OC12 IQand IQE interface
information.
showinterfaces controller (Channelized
OC3 IQand IQE)
Displaytheinterfacenamesof thephysical channelized
OC3 IQand IQE interface and the channels configured
on each interface.
showinterfaces controller (Channelized
OC12 IQand IQE)
Displaytheinterfacenamesof thephysical channelized
OC12IQandIQEinterfaceandthechannels configured
on each interface.
showinterfaces (Channelized OC48 IQ
and IQE)
Display channelized OC48 IQand IQE interface
information.
NOTE: For more information about the channel type and level of
channelization, and for information about the number of channels that are
supported on channelized OC interfaces, see the Junos Network Interfaces
Configuration Guide.
For channelization illustrations and configuration examples for channelized
IQand IQE interfaces, see the Junos Feature Guide.
Channelized STM1 Interface Operational Mode Commands
Table 8 on page 98 summarizes the command-line interface (CLI) commands that you
can use to monitor and troubleshoot channelized STM1 interfaces. Commands are listed
in alphabetical order.
Table 8: Channelized STM1 Interface Operational Mode Commands
Command Task
showinterfaces (Channelized STM1) Display status information about channelized STM1
interfaces.
Copyright 2014, Juniper Networks, Inc. 98
Channelized STM1 Interfaces Feature Guide for Routing Devices
Table 8: Channelized STM1 Interface Operational Mode
Commands (continued)
Command Task
showinterfaces (Channelized STM1 IQ) Display channelized STM1 IQinterface information.
showinterfaces controller (Channelized
STM1 IQ)
Displaytheinterfacenamesof thephysical channelized
STM1 IQinterfaceandthechannelsconfiguredoneach
interface.
NOTE: For more information about the channel type and level of
channelization, and for information about the number of channels that are
supportedonthechannelizedSTM1 interface, seetheJunosNetworkInterfaces
Configuration Guide.
For channelization illustrations and configuration examples for channelized
IQinterfaces, see the Junos Feature Guide.
Channelized T1 and T3 Interface Operational Mode Commands
Table 9 on page 99 summarizes the command-line interface (CLI) commands that you
can use to monitor and troubleshoot channelized T1 and T3 interfaces. Commands are
listed in alphabetical order.
Table 9: Channelized T1 and T3 Interface Operational Mode Commands
Command Task
showinterfaces (Channelized
DS3-to-DS0)
Display status information about channelized
DS3-to-DS0 interfaces.
showinterfaces (Channelized
DS3-to-DS1)
Display status information about channelized
DS3-to-DS1 interfaces.
showinterfaces (Channelized T1 IQ) Display channelized T1 IQinterface information.
showinterfaces (Channelized T3 IQ) Display channelized T3 IQinterface information.
showinterfaces controller (Channelized
T1 IQ)
Display theinterfacenames of thephysical channelized
T1 IQinterface and the channels configured on each
interface.
showinterfaces controller (Channelized
T3 IQ)
Display theinterfacenames of thephysical channelized
T3 IQinterface and the channels configured on each
interface.
99 Copyright 2014, Juniper Networks, Inc.
Chapter 6: Command Summaries
NOTE: For more information about the channel type and level of
channelization, and for information about the number of channels that are
supportedon the different types of channelizedT1 andT3 interfaces, see the
Junos Network Interfaces Configuration Guide.
For more information on monitoring and troubleshooting channelized
DS3-to-DS0 and DS3-to-DS1 interfaces, see the Junos Interfaces Network
Operations Guide.
For channelization illustrations and configuration examples for channelized
IQinterfaces, see the Junos Feature Guide.
Copyright 2014, Juniper Networks, Inc. 100
Channelized STM1 Interfaces Feature Guide for Routing Devices
PART 4
Troubleshooting
Interface Diagnostics on page 103
101 Copyright 2014, Juniper Networks, Inc.
Copyright 2014, Juniper Networks, Inc. 102
Channelized STM1 Interfaces Feature Guide for Routing Devices
CHAPTER 7
Interface Diagnostics
Interface Diagnostics on page 103
Interface Diagnostics
You can use two diagnostic tools to test the physical layer connections of interfaces:
loopback testing and bit error rate test (BERT) testing. Loopback testing enables you to
verify the connectivity of acircuit. BERTtesting enables youtoidentify poor signal quality
on a circuit. This section contains the following topics:
Configuring Loopback Testing on page 103
Interface Diagnostics on page 105
Configuring Loopback Testing
Loopback testing allows you to verify the connectivity of a circuit. You can configure any
of thefollowinginterfaces toexecutealoopback test: AggregatedEthernet, Fast Ethernet,
Gigabit Ethernet, E1, E3, NxDS0, serial, SONET/SDH, T1, and T3.
The physical path of a network data circuit usually consists of segments interconnected
by devices that repeat and regenerate the transmission signal. The transmit path on one
device connects to the receive path on the next device. If a circuit fault occurs in the form
of a line break or a signal corruption, you can isolate the problemby using a loopback
test. Loopbacktests allowyoutoisolatesegments of thecircuit andtest themseparately.
To do this, configure a line loopback on one of the routers. Instead of transmitting the
signal towardthefar-enddevice, thelineloopback sends thesignal back totheoriginating
router. If the originating router receives back its own data link layer packets, you have
verified that the problemis beyond the originating router. Next, configure a line loopback
farther away fromthe local router. If this originating router does not receive its own data
link layer packets, you can assume the problemis on one of the segments between the
local router and the remote routers interface card. In this case, the next troubleshooting
step is to configure a line loopback closer to the local router to find the source of the
problem.
There are several types of loopback testing supported by the Junos OS, as follows:
DCE localLoops packets back on the local DCE.
DCE remoteLoops packets back on the remote DCE.
103 Copyright 2014, Juniper Networks, Inc.
LocalUseful for troubleshooting physical PIC errors. Configuring local loopback on
aninterface allows transmissionof packets tothe channel service unit (CSU) andthen
to the circuit toward the far-end device. The interface receives its own transmission,
whichincludes dataandtiminginformation, onthelocal router's PIC. Thedatareceived
fromthe CSU is ignored. To test a local loopback, issue the showinterfaces
interface-name command. If PPP keepalives transmitted on the interface are received
by the PIC, the Device Flags field contains the output Loop-Detected.
PayloadUseful for troubleshooting the physical circuit problems between the local
router and the remote router. A payload loopback loops data only (without clocking
information) on the remote routers PIC. With payload loopback, overhead is
recalculated.
RemoteUseful for troubleshooting the physical circuit problems between the local
router and the remote router. A remote loopback loops packets, including both data
and timing information, back on the remote routers interface card. Arouter at one end
of thecircuit initiatesaremoteloopbacktowarditsremotepartner. Whenyouconfigure
aremoteloopback, thepackets receivedfromthephysical circuit andCSUarereceived
by the interface. Those packets are then retransmitted by the PIC back toward the
CSU and the circuit. This loopback tests all the intermediate transmission segments.
Table10onpage104shows theloopbackmodes supportedonthevarious interfacetypes.
Table 10: Loopback Modes by Interface Type
Usage Guidelines Loopback Modes Interface
Configuring Ethernet Loopback Capability Local Aggregated Ethernet,
Fast Ethernet, Gigabit
Ethernet
Configuring E1 Loopback Capability Local and remote Circuit Emulation E1
Configuring T1 Loopback Capability Local and remote Circuit Emulation T1
Configuring E1 Loopback Capability and
Configuring E3 Loopback Capability
Local and remote E1 and E3
ConfiguringChannelizedE1 IQandIQEInterfaces,
ConfiguringT1 andNxDS0Interfaces, Configuring
Channelized OC12/STM4 IQand IQE Interfaces
(SONET Mode), Configuring an NxDS0 IQ
Interface on page 9, and Configuring
Channelized T3 IQInterfaces
Payload NxDS0
Configuring Serial Loopback Capability Local and remote Serial (V.35 and X.21)
Configuring Serial Loopback Capability DCE local, DCE
remote, local, and
remote
Serial (EIA-530)
Configuring SONET/SDH Loopback Capability Local and remote SONET/SDH
Copyright 2014, Juniper Networks, Inc. 104
Channelized STM1 Interfaces Feature Guide for Routing Devices
Table 10: Loopback Modes by Interface Type (continued)
Usage Guidelines Loopback Modes Interface
Configuring T1 Loopback Capability and
Configuring T3 Loopback Capability
See also Configuring the T1 Remote Loopback
Response
Local, payload, and
remote
T1 and T3
To configure loopback testing, include the loopback statement:
loopback mode;
You can include this statement at the following hierarchy levels:
[edit interfaces interface-name aggregated-ether-options]
[edit interfaces interface-name ds0-options]
[edit interfaces interface-name e1-options]
[edit interfaces interface-name e3-options]
[edit interfaces interface-name fastether-options]
[edit interfaces interface-name gigether-options]
[edit interfaces interface-name serial-options]
[edit interfaces interface-name sonet-options]
[edit interfaces interface-name t1-options]
[edit interfaces interface-name t3-options]
Interface Diagnostics
BERT allows you to troubleshoot problems by checking the quality of links. You can
configure any of the following interfaces to execute a BERT when the interface receives
a request to run this test: E1, E3, T1, T3; the channelized DS3, OC3, OC12, and STM1
interfaces; and the channelized DS3 IQ, E1 IQ, and OC12 IQinterfaces.
A BERT test requires a line loop to be in place on either the transmission devices or the
far-endrouter. Thelocal router generates aknownbit patternandsends it out thetransmit
path. The received pattern is then verified against the sent pattern. The higher the bit
error rate of the received pattern, the worse the noise is on the physical circuit. As you
move the position of the line loop increasingly downstreamtoward the far-end router,
you can isolate the troubled portion of the link.
To configure BERT, you must configure the duration of the test, the bit pattern to send
on the transmit path, and the error rate to monitor when the inbound pattern is received.
To configure the duration of the test, the pattern to send in the bit stream, and the error
ratetoincludeinthebit stream, includethebert-period, bert-algorithm, andbert-error-rate
statements, respectively, at the [edit interfaces interface-name interface-type-options]
hierarchy level:
105 Copyright 2014, Juniper Networks, Inc.
Chapter 7: Interface Diagnostics
[edit interfaces interface-name interface-type-options]
bert-algorithmalgorithm;
bert-error-rate rate;
bert-period seconds;
By default, the BERT period is 10 seconds. You can configure the BERT period to last
from1 through239seconds onsome PICs andfrom1 through240seconds onother PICs.
rate is the bit error rate. This can be an integer from0 through 7, which corresponds to a
bit error rate from10
0
(1 error per bit) to 10
7
(1 error per 10 million bits).
algorithmis the pattern to send in the bit stream. For a list of supported algorithms, enter
a ? after the bert-algorithmstatement; for example:
[edit interfaces t1-0/0/0 t1-options]
user@host# set bert-algorithm?
Possible completions:
pseudo-2e11-o152 Pattern is 2^11 -1 (per O.152 standard)
pseudo-2e15-o151 Pattern is 2^15 - 1 (per O.152 standard)
pseudo-2e20-o151 Pattern is 2^20 - 1 (per O.151 standard)
pseudo-2e20-o153 Pattern is 2^20 - 1 (per O.153 standard)
...
For specific hierarchy information, see the individual interface types.
NOTE: The 4-port E1 PIC supports only the following algorithms:
pseudo-2e11-o152 Pattern is 2^11 -1 (per O.152 standard)
pseudo-2e15-o151 Pattern is 2^15 - 1 (per O.151 standard)
pseudo-2e20-o151 Pattern is 2^20 - 1 (per O.151 standard)
pseudo-2e23-o151 Pattern is 2^23 (per O.151 standard)
When you issue the help command fromthe CLI, all BERT algorithmoptions
are displayed, regardless of the PIC type, and no commit check is available.
Unsupported patterns for a PIC type can be viewed in systemlog messages.
Copyright 2014, Juniper Networks, Inc. 106
Channelized STM1 Interfaces Feature Guide for Routing Devices
NOTE: The 12-port T1/E1 Circuit Emulation (CE) PIC supports only the
following algorithms:
all-ones-repeating Repeating one bits
all-zeros-repeating Repeating zero bits
alternating-double-ones-zeros Alternating pairs of ones and zeros
alternating-ones-zeros Alternating ones and zeros
pseudo-2e11-o152 Pattern is 2^11 -1 (per O.152 standard)
pseudo-2e15-o151 Pattern is 2^15 - 1 (per O.151 standard)
pseudo-2e20-o151 Pattern is 2^20 - 1 (per O.151 standard)
pseudo-2e7 Pattern is 2^7 - 1
pseudo-2e9-o153 Pattern is 2^9 - 1 (per O.153 standard)
repeating-1-in-4 1 bit in 4 is set
repeating-1-in-8 1 bit in 8 is set
repeating-3-in-24 3 bits in 24 are set
When you issue the help command fromthe CLI, all BERT algorithmoptions
are displayed, regardless of the PIC type, and no commit check is available.
Unsupported patterns for a PIC type can be viewed in systemlog messages.
NOTE: The IQE PICs support only the following algorithms:
all-ones-repeating Repeating one bits
all-zeros-repeating Repeating zero bits
alternating-double-ones-zeros Alternating pairs of ones and zeros
alternating-ones-zeros Alternating ones and zeros
pseudo-2e9-o153 Pattern is 2^9 -1 (per O.153 (511 type) standard)
pseudo-2e11-o152 Pattern is 2^11 -1 (per O.152 and O.153 (2047 type)
standards)
pseudo-2e15-o151 Pattern is 2^15 -1 (per O.151 standard)
pseudo-2e20-o151 Pattern is 2^20 -1 (per O.151 standard)
pseudo-2e20-o153 Pattern is 2^20 -1 (per O.153 standard)
pseudo-2e23-o151 Pattern is 2^23 -1 (per O.151 standard)
repeating-1-in-4 1 bit in 4 is set
repeating-1-in-8 1 bit in 8 is set
repeating-3-in-24 3 bits in 24 are set
When you issue the help command fromthe CLI, all BERT algorithmoptions
are displayed, regardless of the PIC type, and no commit check is available.
Unsupported patterns for a PIC type can be viewed in systemlog messages.
107 Copyright 2014, Juniper Networks, Inc.
Chapter 7: Interface Diagnostics
NOTE: BERT is supported on the PDHinterfaces of the Channelized
SONET/SDHOC3/STM1 (Multi-Rate) MIC with SFP and the DS3/E3 MIC.
The following BERT algorithms are supported:
all-ones-repeating Repeating one bits
all-zeros-repeating Repeating zero bits
alternating-double-ones-zeros Alternating pairs of ones and zeros
alternating-ones-zeros Alternating ones and zeros
repeating-1-in-4 1 bit in 4 is set
repeating-1-in-8 1 bit in 8 is set
repeating-3-in-24 3 bits in 24 are set
pseudo-2e9-o153 Pattern is 2^9 - 1 (per O.153 standard)
pseudo-2e11-o152 Pattern is 2^11 - 1 (per O.152 standard)
pseudo-2e15-o151 Pattern is 2^15 - 1 (per O.151 standard)
pseudo-2e20-o151 Pattern is 2^20 - 1 (per O.151 standard)
pseudo-2e20-o153 Pattern is 2^20 - 1 (per O.153 standard)
pseudo-2e23-o151 Pattern is 2^23 (per O.151 standard)
Table 11 on page 108 shows the BERT capabilities for various interface types.
Table 11: BERT Capabilities by Interface Type
Comments T3 BERT T1 BERT Interface
Limited algorithms Yes (ports 011) 12-port T1/E1
Circuit Emulation
Limited algorithms Yes (port 03) 4-port
Channelized
OC3/STM1
Circuit Emulation
Single port at a time
Limited algorithms
Yes (port 03) Yes (port 03) E1 or T1
Single port at a time Yes (port 03) Yes (port 03) E3 or T3
Single channel at a time
Limited algorithms
No bit count
Yes (channel
011)
N/A Channelized
OC12
Multiple channels
Only one algorithm
No error insert
No bit count
N/A Yes (channel
062)
Channelized
STM1
Multiple ports and channels
Limited algorithms for T1
No error insert for T1
No bit count for T1
Yes (port 03 on
channel 0)
Yes (channel
027)
Channelized T3
andMultichannel
T3
Copyright 2014, Juniper Networks, Inc. 108
Channelized STM1 Interfaces Feature Guide for Routing Devices
These limitations do not apply to channelized IQinterfaces. For information about BERT
capabilities onchannelizedIQinterfaces, seeChannelizedIQandIQEInterfaces Properties.
Starting and Stopping a BERT Test
Before you can start the BERT test, you must disable the interface. To do this, include
the disable statement at the [edit interfaces interface-name] hierarchy level:
[edit interfaces interface-name]
disable;
After you configure the BERT properties and commit the configuration, begin the test by
issuing the test interface interface-name interface-type-bert-start operational mode
command:
user@host> test interface interface-name interface-type-bert-start
The test runs for the duration you specify with the bert-period statement. If you wish to
terminate the test sooner, issue the test interface interface-name interface-type-bert-stop
command:
user@host> test interface interface-name interface-type-bert-stop
For example:
user@host> test interface t3-1/2/0t3-bert-start
user@host> test interface t3-1/2/0t3-bert-stop
To viewthe results of the BERT test, issue the showinterfaces extensive | find BERT
command:
user@host> showinterfaces interface-name extensive | find BERT
For more information about running and evaluating the results of the BERT procedure,
see the CLI Explorer.
NOTE: To exchange BERT patterns between a local router and a remote
router, include the loopback remote statement in the interface configuration
at the remote end of the link. Fromthe local router, issue the test interface
command.
Example: Configuring Bit Error Rate Testing
Configure a BERT test on a T3 interface. In this example, the run duration lasts for 120
seconds. The configured error rate is 0, which corresponds to a bit error rate of 10
0
(1
error per bit). The configured bit pattern of all-ones-repeating means that every bit the
interface sends is a set to a value of 1.
[edit interfaces]
t3-1/2/0 {
t3-options {
bert algorithmall-ones-repeating;
bert-error-rate 0;
bert-period 120;
109 Copyright 2014, Juniper Networks, Inc.
Chapter 7: Interface Diagnostics
}
}
Copyright 2014, Juniper Networks, Inc. 110
Channelized STM1 Interfaces Feature Guide for Routing Devices
PART 5
Index
Index on page 113
111 Copyright 2014, Juniper Networks, Inc.
Copyright 2014, Juniper Networks, Inc. 112
Channelized STM1 Interfaces Feature Guide for Routing Devices
Index
Symbols
#, comments in configuration statements....................xii
( ), in syntax descriptions......................................................xii
< >, in syntax descriptions....................................................xii
[ ], in configuration statements..........................................xii
{ }, in configuration statements.........................................xii
| (pipe), in syntax descriptions...........................................xii
A
advertise-interval statement.............................................48
aps statement.........................................................................49
authentication-key statement..........................................50
B
BERT
configuring interface diagnostics...........................105
bert-algorithmstatement
usage guidelines...........................................................105
bert-error-rate statement.....................................................51
usage guidelines...........................................................105
bert-period statement..........................................................53
usage guidelines...........................................................105
bit error rate test See BERT
braces, in configuration statements.................................xii
brackets
angle, in syntax descriptions.......................................xii
square, in configuration statements........................xii
bytes statement......................................................................55
C
channelized E1 interfaces
example configuration..................................................12
interface naming..............................................................12
channelized E1 IQand IQE interfaces
time slots.............................................................................8
channelized STM1 interfaces
example configuration..................................................21
status information, displaying...................................82
time slots.............................................................................9
channelized STM1 IQinterfaces
example configuration...................................................11
comments, in configuration statements........................xii
conventions
text and syntax..................................................................xi
curly braces, in configuration statements......................xii
customer support...................................................................xiii
contacting JTAC..............................................................xiii
D
documentation
comments on..................................................................xiii
ds0-options statement
usage guidelines..............................................................12
E
E1 interfaces
example configuration..................................................12
E1 IQinterfaces
example configuration...................................................8
E1 IQE interfaces
example configuration...................................................8
e1-options statement............................................................56
usage guidelines..............................................................12
F
fast-aps-switch statement.................................................57
fcs statement...........................................................................58
font conventions.......................................................................xi
force statement.......................................................................59
fractional E1 IQand IQE interfaces
time slots.............................................................................8
fractional E1 IQinterfaces
example configuration...................................................9
framing statement
E1, E3, and T1 interfaces..............................................60
H
hold-time statement
APS.......................................................................................61
I
idle-cycle-flag statement....................................................62
interface-type statement....................................................63
channelized T1 IQinterfaces
usage guidelines.......................................................7
interfaces
configuration statements...........................................24
113 Copyright 2014, Juniper Networks, Inc.
L
link PIC failover
channelized STM1 IQ and IQE PICs..........................21
lockout statement..................................................................64
logical systems
configuration statements...........................................40
loopback statement
ADSL, DS0, E1/E3, SONET/SDH, SHDSL, and
T1/T3..............................................................................65
loopback testing....................................................................103
M
manuals
comments on..................................................................xiii
N
neighbor statement...............................................................66
no-partition statement.........................................................67
channelized T3 IQinterfaces
usage guidelines.......................................................7
no-termination-request statement................................68
NxDS0 IQinterfaces
example configuration..................................................10
P
paired-group statement......................................................68
parentheses, in syntax descriptions.................................xii
partition statement...............................................................69
channelized T1 IQinterfaces
usage guidelines.......................................................7
physical interfaces
time slots.............................................................................9
fractional E1 IQ and IQE interfaces...................8
protect-circuit statement....................................................70
R
request statement..................................................................70
revert-time statement............................................................71
S
showinterfaces (Channelized STM1)
command..............................................................................82
sonet-options statement.....................................................72
start-end-flag statement.....................................................74
support, technical See technical support
switching-mode statement................................................75
syntax conventions..................................................................xi
T
technical support
contacting JTAC..............................................................xiii
time slots
channelized E1 IQ and IQE interfaces.......................8
channelized NxDS0 IQ interfaces..............................9
fractional E1 IQ and IQE interfaces............................8
timeslots statement..............................................................76
channelized E1 IQand IQE interfaces
usage guidelines......................................................8
channelized NxDS0 IQinterfaces
usage guidelines......................................................9
fractional E1 IQand IQE interfaces
usage guidelines......................................................8
V
vtmapping statement............................................................77
usage guidelines..............................................................14
W
working-circuit statement....................................................77
Copyright 2014, Juniper Networks, Inc. 114
Channelized STM1 Interfaces Feature Guide for Routing Devices