JUNIPER NETWORKS Circuit Emulation Interfaces Routing Devices User Guide

: June 16, 2024
: JUNIPER NETWORKS

Table of Contents

Circuit Emulation Interfaces Routing Devices
Product Information
Specifications
Product Usage Instructions
1. Overview
2. Configuring Circuit Emulation Interfaces

Circuit Emulation Interfaces Routing Devices

Product Information

Specifications

Product Name: Circuit Emulation Interfaces User Guide for
Routing Devices
Published Date: 2023-10-05
Manufacturer: Juniper Networks, Inc.
Address: 1133 Innovation Way Sunnyvale, California 94089
USA
Contact: 408-745-2000
Website: www.juniper.net

Product Usage Instructions

1. Overview

The Circuit Emulation Interfaces User Guide provides information
on understanding circuit emulation interfaces and their
functionalities. It covers various topics such as circuit emulation
services, supported PIC types, circuit standards, clocking
features, ATM QoS or shaping, and support for converged
networks.

1.1 Understanding Circuit Emulation Interfaces

The guide explains the concept of circuit emulation interfaces
and their role in emulating traditional circuit-switched networks
over packet-switched networks.

1.2 Understanding Circuit Emulation Services and the Supported

PIC Types

This section provides an overview of different circuit emulation
services and the supported PIC (Physical Interface Card) types. It
includes information about the 4-Port Channelized OC3/STM1
(Multi-Rate) Circuit Emulation MIC with SFP, 12-Port Channelized
T1/E1 Circuit Emulation PIC, 8-Port OC3/STM1 or 12-port OC12/STM4
ATM MIC, and 16-Port Channelized E1/T1 Circuit Emulation MIC.

1.3 Understanding Circuit Emulation PIC Clocking Features

Here, you will learn about the clocking features of Circuit
Emulation PICs and how they ensure accurate timing synchronization
in circuit emulation scenarios.

1.4 Understanding ATM QoS or Shaping

This section explains the concept of ATM Quality of Service
(QoS) or shaping and its importance in circuit emulation
interfaces.

1.5 Understanding How Circuit Emulation Interfaces Support

Converged Networks That Accommodate Both IP And Legacy
Services

Learn how circuit emulation interfaces support converged
networks that integrate both IP (Internet Protocol) and legacy
services. This section also covers mobile backhaul
applications.

2. Configuring Circuit Emulation Interfaces

This section provides step-by-step instructions for configuring
circuit emulation interfaces.

2.1 Configuring SAToP Support on Circuit Emulation PICs

Follow these steps to configure SAToP (Structure-Agnostic TDM
over Packet) support on Circuit Emulation PICs.

2.2 Configuring SAToP Emulation on T1/E1 Interfaces on 12-Port

Channelized T1/E1 Circuit Emulation PICs

This subsection explains how to configure SAToP emulation on
T1/E1 interfaces specifically on the 12-Port Channelized T1/E1
Circuit Emulation PIC. It covers setting the emulation mode,
configuring SAToP options, and configuring the pseudowire
interface.

2.3 Configuring SAToP Support on Circuit Emulation MICs

Learn how to configure SAToP support on Circuit Emulation MICs,
focusing on the 16-Port Channelized E1/T1 Circuit Emulation MIC.
This section covers configuring T1/E1 framing mode, configuring CT1
ports, and configuring DS channels.

FAQ

Q: Are Juniper Networks hardware and software products Year

2000 compliant?

A: Yes, 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 may have
difficulty in the year 2036.

Q: Where can I find the End User License Agreement (EULA) for

Juniper Networks software?

A: The End User License Agreement (EULA) for Juniper Networks
software can be found at https://support.juniper.net/support/eula/.

Junos® OS
Circuit Emulation Interfaces User Guide for Routing Devices
Published
2023-10-05

ii
Juniper Networks, Inc. 1133 Innovation Way Sunnyvale, California 94089 USA 408-745-2000 www.juniper.net
Juniper Networks, the Juniper Networks logo, Juniper, and Junos are registered trademarks of Juniper Networks, Inc. in the United States and other countries. All other trademarks, service marks, registered marks, 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 Circuit Emulation Interfaces User Guide for Routing Devices Copyright © 2023 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.
END USER 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 https://support.juniper.net/support/eula/. By downloading, installing or using such software, you agree to the terms and conditions of that EULA.

iii

Table of Contents

Overview

Understanding Circuit Emulation Interfaces | 2

Understanding Circuit Emulation Services and the Supported PIC Types | 2 4-Port Channelized OC3/STM1 (Multi-Rate) Circuit Emulation MIC with SFP | 3 12-Port Channelized T1/E1 Circuit Emulation PIC | 4 8-Port OC3/STM1 or 12-port OC12/STM4 ATM MIC | 5 16-Port Channelized E1/T1 Circuit Emulation MIC | 5 Layer 2 Circuit Standards | 7
Understanding Circuit Emulation PIC Clocking Features | 8 Understanding ATM QoS or Shaping | 8

Understanding How Circuit Emulation Interfaces Support Converged Networks That Accommodate Both IP And Legacy Services | 12
Understanding Mobile Backhaul | 12 Mobile Backhaul Application Overview | 12 IP/MPLS-based Mobile Backhaul | 13

Configuring Circuit Emulation Interfaces

Configuring SAToP Support on Circuit Emulation PICs | 16

Configuring SAToP on 4-Port Channelized OC3/STM1 Circuit Emulation MICs | 16 Configuring SONET/SDH Rate-Selectability | 16 Configuring SONET/SDH Framing Mode at the MIC Level | 17 Configuring SONET/SDH Framing Mode at the Port Level | 18 Configuring SAToP Options on T1 interfaces | 19 Configuring COC3 Ports Down to T1 Channels | 19 Configuring SAToP Options on a T1 interface | 21 Configuring SAToP Options on E1 Interfaces | 22 Configuring CSTM1 Ports Down to E1 Channels | 22 Configuring SAToP Options on E1 Interfaces | 23
Configuring SAToP Emulation on T1/E1 Interfaces on 12-Port Channelized T1/E1 Circuit Emulation PICs | 25 Setting the Emulation Mode | 25 Configuring SAToP Emulation on T1/E1 Interfaces | 26 Setting the Encapsulation Mode | 26 Configuring Loopback for a T1 Interface or an E1 Interface | 27 Setting the SAToP Options | 27 Configuring the Pseudowire Interface | 28
Setting the SAToP Options | 30

v
Configuring the Pseudowire Interface | 39 SAToP Emulation on T1 and E1 Interfaces Overview | 41 Configuring SAToP Emulation on Channelized T1 and E1 Interfaces | 42
Setting the T1/E1 Emulation Mode | 43 Configuring One Full T1 or E1 Interface on Channelized T1 and E1 Interfaces | 44 Setting the SAToP Encapsulation Mode | 48 Configure the Layer 2 Circuit | 48
Configuring CESoPSN Support on Circuit Emulation MIC | 50
TDM CESoPSN Overview | 50 Configuring TDM CESoPSN on ACX Series Routers Overview | 51
Channelization up to the DS0 Level | 51 Protocol Support | 52 Packet Latency | 52 CESoPSN Encapsulation | 52 CESoPSN Options | 52 show Commands | 52 CESoPSN Pseudowires | 52 Configuring CESoPSN on Channelized E1/T1 Circuit Emulation MIC | 53 Configuring T1/E1 Framing Mode at the MIC Level | 53 Configuring CT1 Interface Down to DS Channels | 54 Setting the CESoPSN Options | 55 Configuring CESoPSN on DS Interfaces | 57 Configuring CESoPSN on Channelized OC3/STM1 (Multi-Rate) Circuit Emulation MIC with SFP | 58 Configuring SONET/SDH Rate-Selectability | 58 Configuring SONET/SDH Framing Mode at the MIC Level | 59 Configuring CESoPSN Encapsulation on DS Interfaces on CT1 Channels | 60
Configuring COC3 Ports Down to CT1 Channels | 60 Configuring CT1 Channels Down to DS Interfaces | 62 Configuring CESoPSN on DS Interfaces | 63 Configuring CESoPSN Encapsulation on DS Interfaces on CE1 Channels | 64 Configuring CSTM1 Ports Down to CE1 Channels | 64 Configuring CSTM4 Ports Down to CE1 Channels | 66 Configuring CE1 Channels Down to DS Interfaces | 68

vi
Configuring CESoPSN on DS Interfaces | 69 Configuring CESoPSN Encapsulation on DS Interfaces | 70
Setting the Encapsulation Mode | 70 Setting the CESoPSN Options | 71 Configuring the Pseudowire Interface | 73 Configuring CE1 Channels Down to DS Interfaces | 74 Configuring CESoPSN on Channelized E1/T1 Circuit Emulation MIC on ACX Series | 77 Configuring T1/E1 Framing Mode at the MIC Level | 77 Configuring CT1 Interface Down to DS channels | 78 Configuring CESoPSN on DS Interfaces | 79
Configuring ATM Support on Circuit Emulation PICs | 81
ATM Support on Circuit Emulation PICs Overview | 81 ATM OAM Support | 82 Protocol and Encapsulation Support | 83 Scaling Support | 83 Limitations to ATM Support on Circuit Emulation PICs | 84
Configuring the 4-Port Channelized COC3/STM1 Circuit Emulation PIC | 85 T1/E1 Mode Selection | 85 Configuring a Port for SONET or SDH Mode on a 4-Port Channelized COC3/STM1 Circuit Emulation PIC | 86 Configuring an ATM Interface on a Channelized OC1 interface | 87
Configuring the 12-Port Channelized T1/E1 Circuit Emulation PIC | 87 Configuring CT1/CE1 Interfaces | 88 Configuring T1/E1 Mode at the PIC level | 88 Creating an ATM Interface on a CT1 or CE1 | 89 Creating an ATM Interface on a CE1 Interface | 89 Configuring Interface-Specific Options | 90 Configuring ATM Interface-Specific Options | 90 Configuring E1 Interface-Specific Options | 91 Configuring T1 Interface-Specific Options | 92
Understanding Inverse Multiplexing for ATM | 93 Understanding Asynchronous Transfer Mode | 93 Understanding Inverse Multiplexing for ATM | 94 How Inverse Multiplexing for ATM Works | 94

viii

Disabling Swapping on Local and Remote Provider Edge Routers | 123 Configuring Layer 2 Circuit and Layer 2 VPN Pseudowires | 126 Configuring EPD Threshold | 127 Configuring ATM QoS or Shaping | 128

Troubleshooting Information

Troubleshooting Circuit Emulation Interfaces | 132

Configuration Statements and Operational Commands

Configuration Statements | 142

Operational Commands | 157
show interfaces (ATM) | 158 show interfaces (T1, E1, or DS) | 207 show interfaces extensive | 240

ix
About the Documentation
IN THIS SECTION Documentation and Release Notes | ix Using the Examples in This Manual | ix Documentation Conventions | xi Documentation Feedback | xiv Requesting Technical Support | xiv
Use this guide to configure circuit emulation interfaces to transmit data over ATM, Ethernet, or MPLS networks using Structure-Agnostic TDM over Packet (SAToP) and Circuit Emulation Service over Packet-Switched Network (CESoPSN) protocols.
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 https://www.juniper.net/documentation/. If the information in the latest release notes differs from the information in the documentation, follow the 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 https://www.juniper.net/books.
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. 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.

x
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, follow these steps:
1. From the 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 the following configuration to a file and name the file ex-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 platform configuration by issuing the load merge configuration mode command:
[edit] user@host# load merge /var/tmp/ex-script.conf load complete

xi
Merging a Snippet To merge a snippet, follow these steps: 1. From the 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; }
2. Move to the hierarchy level that is relevant for this snippet by issuing the following configuration mode command:
[edit] user@host# edit system scripts [edit system scripts] 3. Merge the contents of the file into your routing platform configuration by issuing the load merge relative configuration mode command:
[edit system scripts] user@host# load merge relative /var/tmp/ex-script- snippet.conf load complete
For more information about the load command, see CLI Explorer.
Documentation Conventions
Table 1 on page xii defines notice icons used in this guide.

Table 1: Notice Icons

Icon

Meaning

Informational note

Caution

Warning

xii
Description Indicates important features or instructions.
Indicates a situation that might result in loss of data or hardware damage. Alerts you to the risk of personal injury or death.

Laser warning

Alerts you to the risk of personal injury from a laser.

Tip Best practice

Indicates helpful information. Alerts you to a recommended use or implementation.

Table 2 on page xii defines the text and syntax conventions used in this guide.

Table 2: Text and Syntax Conventions

Convention

Description

Examples

Bold text like this

Represents text that you type.

Fixed-width text like this

Represents output that appears on the terminal screen.

To enter configuration mode, type the configure command:
user@host> configure
user@host> show chassis alarms No alarms currently active

Italic text like this

· Introduces or emphasizes important new terms.
· Identifies guide names. · Identifies RFC and Internet draft
titles.

· A policy term is a named structure that defines match conditions and actions.
· Junos OS CLI User Guide
· RFC 1997, BGP Communities Attribute

xiii

Table 2: Text and Syntax Conventions (continued)

Convention

Description

Examples

Italic text like this Text like this < > (angle brackets)

Represents variables (options for which you substitute a value) in commands or configuration statements.

Configure the machine’s domain name:
[edit] root@# set system domain-name
domain-name

Represents names of configuration statements, commands, files, and directories; configuration hierarchy levels; or labels on routing platform components.
Encloses optional keywords or variables.

· To configure a stub area, include the stub statement at the [edit protocols ospf area area-id] hierarchy level.
· The console port is labeled CONSOLE.
stub ;

| (pipe symbol)

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.

broadcast | multicast (string1 | string2 | string3)

(pound sign)

Indicates a comment specified on the same line as the configuration statement to which it applies.

rsvp { # Required for dynamic MPLS only

[ ] (square brackets)

Encloses a variable for which you can community name members [

substitute one or more values.

community-ids ]

Indention and braces ( { } ) ; (semicolon)
GUI Conventions

Identifies a level in the configuration hierarchy.
Identifies a leaf statement at a configuration hierarchy level.

[edit] routing-options {
static { route default { nexthop address; retain; }
} }

xiv

Table 2: Text and Syntax Conventions (continued)

Convention

Description

Examples

Bold text like this > (bold right angle bracket)

Represents graphical user interface (GUI) items you click or select.
Separates levels in a hierarchy of menu selections.

· In the Logical Interfaces box, select All Interfaces.
· To cancel the configuration, click Cancel.
In the configuration editor hierarchy, select Protocols>Ospf.

Documentation Feedback
We encourage you to provide feedback so that we can improve our documentation. You can use either of the following methods: · Online feedback system–Click TechLibrary Feedback, on the lower right of any page on the Juniper
Networks TechLibrary site, and do one of the following:

· Click the thumbs-up icon if the information on the page was helpful to you. · Click the thumbs-down icon if the information on the page was not helpful to you or if you have
suggestions for improvement, and use the pop-up form to provide feedback. · E-mail–Send your comments to techpubs-comments@juniper.net. Include the document or topic name,
URL or page number, and software version (if applicable).
Requesting Technical Support
Technical product support is available through the Juniper Networks Technical Assistance Center (JTAC). If you are a customer with an active Juniper Care or Partner Support Services support contract, or are

xv
covered under warranty, and need post-sales technical support, you can access our tools and resources online or open a case with JTAC. · JTAC policies–For a complete understanding of our JTAC procedures and policies, review the JTAC User
Guide located at https://www.juniper.net/us/en/local/pdf/resource- guides/7100059-en.pdf. · Product warranties–For product warranty information, visit https://www.juniper.net/support/warranty/. · JTAC hours of operation–The 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 problem resolution, Juniper Networks has designed an online self-service portal called the Customer Support Center (CSC) that provides you with the following features: · Find CSC offerings: https://www.juniper.net/customers/support/ · Search for known bugs: https://prsearch.juniper.net/ · Find product documentation: https://www.juniper.net/documentation/ · Find solutions and answer questions using our Knowledge Base: https://kb.juniper.net/ · Download the latest versions of software and review release notes:
https://www.juniper.net/customers/csc/software/ · Search technical bulletins for relevant hardware and software notifications:
https://kb.juniper.net/InfoCenter/ · Join and participate in the Juniper Networks Community Forum:
https://www.juniper.net/company/communities/ · Create a service request online: https://myjuniper.juniper.net To verify service entitlement by product serial number, use our Serial Number Entitlement (SNE) Tool: https://entitlementsearch.juniper.net/entitlementsearch/
Creating a Service Request with JTAC
You can create a service request with JTAC on the Web or by telephone. · Visit https://myjuniper.juniper.net. · 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 https://support.juniper.net/support/requesting- support/.

1 PART
Overview
Understanding Circuit Emulation Interfaces | 2 Understanding How Circuit Emulation Interfaces Support Converged Networks That Accommodate Both IP And Legacy Services | 12

2
CHAPTER 1
Understanding Circuit Emulation Interfaces
IN THIS CHAPTER Understanding Circuit Emulation Services and the Supported PIC Types | 2 Understanding Circuit Emulation PIC Clocking Features | 8 Understanding ATM QoS or Shaping | 8
Understanding Circuit Emulation Services and the Supported PIC Types
IN THIS SECTION 4-Port Channelized OC3/STM1 (Multi-Rate) Circuit Emulation MIC with SFP | 3 12-Port Channelized T1/E1 Circuit Emulation PIC | 4 8-Port OC3/STM1 or 12-port OC12/STM4 ATM MIC | 5 16-Port Channelized E1/T1 Circuit Emulation MIC | 5 Layer 2 Circuit Standards | 7
Circuit emulation service is a method through which data can be transmitted over ATM, Ethernet, or MPLS networks. This information is error-free and has a constant delay, thereby enabling you to use it for services that use time- division multiplexing (TDM). This technology can be implemented through Structure-Agnostic TDM over Packet (SAToP) and Circuit Emulation Service over Packet-Switched Network (CESoPSN) protocols. SAToP enables you to encapsulate TDM bit-streams such as T1, E1, T3, and E3 as pseudowires over packet-switched networks (PSNs). CESoPSN enables you to encapsulate structured (NxDS0) TDM signals as pseudowires over packet-switching networks. A pseudowire is a Layer 2 circuit or service, that emulates the essential attributes of a telecommunications service– such as a T1 line, over an MPLS PSN. The pseudowire is intended to provide only the minimum

3
necessary functionality to emulate the wire with the required degree of faithfulness for the given service definition.
The following Circuit Emulation PICs are specifically designed for mobile backhaul applications.
4-Port Channelized OC3/STM1 (Multi-Rate) Circuit Emulation MIC with SFP
The 4-port Channelized OC3/STM1 (Multi-Rate) Circuit Emulation MIC with SFP –MIC-3D-4COC3-1COC12-CE–is a channelized Circuit Emulation MIC with rate- selectability. You can specify its port speed as COC3-CSTM1 or COC12-CSTM4. The default port speed is COC3-CSTM1. To configure the 4-port Channelized OC3/STM1 Circuit Emulation MIC, see “Configuring SAToP on 4-Port Channelized OC3/STM1 Circuit Emulation MICs” on page 16.
All ATM interfaces are either T1 or E1 channels within the COC3/CSTM1 hierarchy. Each COC3 interface can be partitioned as 3 COC1 slices, each of which in turn can be partitioned further into 28 ATM interfaces and the size of each interface created is that of a T1 interface. Each CS1 interface can be portioned as 1 CAU4 interface, which can be further partitioned as E1-sized ATM interfaces.
The following features are supported on the MIC-3D-4COC3-1COC12-CE MIC:
· Per-MIC SONET/SDH framing · Internal and loop clocking · T1/E1 and SONET clocking · Mixed SAToP and ATM interfaces on any port · SONET mode–Each OC3 port can be channelized down to 3 COC1 channels, and then each COC1 can
channel down to 28 T1 channels. · SDH mode–Each STM1 port can be channelized down to 4 CAU4 channels, and then each CAU4 can
channel down to 63 E1 channels. · SAToP · CESoPSN · Pseudowire Emulation Edge to Edge (PWE3) control word for use over an MPLS PSN The MIC-3D- 4COC3-1COC12-CE MIC supports T1 and E1 options with the following exceptions:
· bert-algorithm, bert-error-rate, and bert-period options are supported for CT1 or CE1 configurations only.
· framing is supported for CT1 or CE1 configurations only. It is not applicable in SAToP configurations. · buildout is supported in CT1 configurations only. · line-encoding is supported in CT1 configurations only.

4
· loopback local and loopback remote are supported in CE1 and CT1 configurations only. By default, no loopback is configured.
· loopback payload is not supported. It is not applicable in SAToP configurations. · idle-cycle-flag is not supported. It is not applicable in SAToP configurations. · start-end-flag is not supported. It is not applicable in SAToP configurations. · invert-data is not supported. It is not applicable in SAToP configurations. · fcs16 is not supported in E1 and T1 configurations only. · fcs32 is not supported in E1 and T1 configurations only. It is not applicable in SAToP configurations. · timeslots is not supported. It is not applicable in SAToP or ATM configurations. · byte-encoding is not supported in T1 configurations only. It is not applicable in SAToP configurations.
nx56 byte encoding is not supported. · crc-major-alarm-threshold and crc- minor-alarm-threshold are T1 options supported in SAToP
configurations only. · remote-loopback-respond is not supported. It is not applicable in SAToP configurations. · If you attempt to configure the local loopback capability on an at- interface–ATM1 or ATM2 intelligent
queuing (IQ) interface or a virtual ATM interface on a Circuit Emulation (ce-) interface–by including the loopback local statement at the [edit interfaces at-fpc/pic/port e1-options], [edit interfaces at-fpc/pic/port e3-options], [edit interfaces at-fpc/pic/port t1-options], or the [edit interfaces at- fpc/pic/port t3-options] hierarchy level (to define the E1, E3, T1, or T3 physical interface properties) and commit the configuration, the commit is successful. However, local loopback on AT interfaces does not take effect and a system log message is generated stating that local loopback is not supported. You must not configure local loopback because it is not supported on at- interfaces. · Mixing T1 and E1 channels is not supported on individual ports.
For more information about MIC-3D-4COC3-1COC12-CE, see Channelized OC3/STM1 (Multi-Rate) Circuit Emulation MIC with SFP.
12-Port Channelized T1/E1 Circuit Emulation PIC
The 12-port Channelized T1/E1 Circuit Emulation PIC supports TDM interfaces by using the SAToP protocol [RFC 4553] encapsulation, and supports T1/E1 and SONET clocking features. The 12-port Channelized T1/E1 Circuit Emulation PIC can be configured to work as either 12 T1 interfaces or 12 E1 interfaces. Mixing T1 interfaces and E1 interfaces is not supported. To configure the 12-Port Channelized T1/E1 Circuit Emulation PIC, see “Configuring the 12-Port Channelized T1/E1 Circuit Emulation PIC” on page 87.

5
The 12-port Channelized T1/E1 Circuit Emulation PICs support T1 and E1 options, with the following exceptions: · bert-algorithm, bert-error-rate, and bert-period options are supported for CT1 or CE1 configurations
only. · framing is supported for CT1 or CE1 configurations only. It is not applicable in SAToP configurations. · buildout is supported in CT1 configurations only. · line-encoding is supported in CT1 configurations only. · loopback local and loopback remote are supported in CE1 and CT1 configurations only. · loopback payload is not supported. It is not applicable in SAToP configurations. · idle-cycle-flag is not supported. It is not applicable in SAToP or ATM configurations. · start-end-flag is not supported. It is not applicable in SAToP or ATM configurations. · invert-data is not supported. It is not applicable in SAToP configurations. · fcs32 is not supported. fcs is not applicable in SAToP or ATM configurations. · timeslots is not supported. It is not applicable in SAToP configurations. · byte- encoding nx56 is not supported. It is not applicable in SAToP or ATM configurations. · crc-major-alarm-threshold and crc-minor-alarm-threshold are not supported. · remote-loopback-respond is not supported. It is not applicable in SAToP configurations.
8-Port OC3/STM1 or 12-port OC12/STM4 ATM MIC
The 8-port OC3/STM1 or 2-port OC12/STM4 Circuit Emulation ATM MIC supports both SONET and SDH framing mode. The mode can be set at the MIC level or at the port level. ATM MICs are rate-selectable at the following rates: 2-port OC12 or 8-port OC3. The ATM MIC supports ATM pseudowire encapsulation and swapping of VPI and VCI values in both directions.
NOTE: Cell-relay VPI/VCI swapping and cell-relay VPI swapping on both egress and ingress are not compatible with the ATM policing feature.
16-Port Channelized E1/T1 Circuit Emulation MIC
The 16-port Channelized E1/T1 Circuit Emulation MIC (MIC-3D-16CHE1-T1-CE) is a channelized MIC with 16 E1 or T1 ports.

6
The following features are supported on the MIC-3D-16CHE1-T1-CE MIC: · Each MIC can be separately configured in either T1 or E1 framing mode. · Each T1 port supports superframe (D4) and extended superframe (ESF) framing modes. · Each E1 port supports G704 with CRC4, G704 without CRC4, and unframed framing modes. · Clear channel and NxDS0 channelization. For T1 the value of N ranges from 1 through 24 and for E1
the value of N ranges from 1 through 31. · Diagnostic features:
· T1/E1 · T1 facilities data link (FDL) · Channel service unit (CSU) · Bit error rate test (BERT) · Juniper Integrity Test (JIT) · T1/E1 alarm and performance monitoring (a Layer 1 OAM function) · External (loop) timing and internal (system) timing · TDM circuit emulation services CESoPSN and SAToP · CoS parity with IQE PICs. The CoS features supported on MPCs are supported on this MIC. · Encapsulations: · ATM CCC cell relay · ATM CCC VC multiplex · ATM VC multiplex · Multilink Point-to-Point Protocol (MLPPP) · Multilink Frame Relay (MLFR) FRF.15 · Multilink Frame Relay (MLFR) FRF.16 · Point-to-Point Protocol (PPP) · Cisco High-Level Data Link Control · ATM class-of-service (CoS) features–traffic shaping, scheduling, and policing · ATM Operation, Administration, and Maintenance · Graceful Routing Engine switchover (GRES)

7
NOTE: · When GRES is enabled you must execute the clear interface statistics (interface-name | all)
operational mode command to reset the cumulative values for local statistics. For more information, see Resetting Local Statistics. · Unified ISSU is not supported on the 16-port Channelized E1/T1 Circuit Emulation MIC (MIC-3D- 16CHE1-T1-CE).
For more information about MIC-3D-16CHE1-T1-CE, see Channelized E1/T1 Circuit Emulation MIC.
Layer 2 Circuit Standards
Junos OS substantially supports the following Layer 2 circuit standards: · RFC 4447, Pseudowire Setup and Maintenance Using the Label Distribution Protocol (LDP) (except section
5.3) · RFC 4448, Encapsulation Methods for Transport of Ethernet over MPLS Networks · Internet draft draft-martini-l2circuit-encap-mpls-11.txt, Encapsulation Methods for Transport of Layer 2
Frames Over IP and MPLS Networks (expires August 2006) Junos OS has the following exceptions: · A packet with a sequence number of 0 is treated as out of sequence.
· Any packet that does not have the next incremental sequence number is considered out of sequence. · When out-of-sequence packets arrive, the expected sequence number for the neighbor is set to the
sequence number in the Layer 2 circuit control word. · Internet draft draft- martini-l2circuit-trans-mpls-19.txt, Transport of Layer 2 Frames Over MPLS (expires
September 2006). These drafts are available on the IETF website at http://www.ietf.org/.
RELATED DOCUMENTATION Displaying Information About Circuit Emulation PICs | 132

8
Understanding Circuit Emulation PIC Clocking Features
All Circuit Emulation PICs support the following clocking features: · External clocking–Also known as loop timing. Clock is distributed via TDM interfaces. · Internal clocking with external synchronization–Also known as external timing or external synchronization. · Internal clocking with PIC-level line synchronization–The PIC’s internal clock is synchronized with a
clock recovered from a TDM interface local to the PIC. This feature set is useful for aggregation in mobile backhaul applications.
NOTE: The primary reference source (PRS) of the clock recovered from one interface may not be the same as that of another TDM interface. There is a limitation on the number of timing domains that can be supported in practice.
RELATED DOCUMENTATION Understanding Mobile Backhaul | 12
Understanding ATM QoS or Shaping
M7i, M10i, M40e, M120, and M320 routers with 4-port Channelized OC3/STM1 Circuit Emulation PICs and 12-port T1/E1 Circuit Emulation PICs and MX Series routers with Channelized OC3/STM1 (Multi-Rate) Circuit Emulation MIC with SFP and 16-port Channelized E1/T1 Circuit Emulation MIC support ATM pseudowire service with QoS features for ingress and egress direction traffic shaping. Policing is performed by monitoring the configured parameters on the incoming traffic and is also referred to as ingress shaping. Egress shaping uses queuing and scheduling to shape the outgoing traffic. Classification is provided per virtual circuit (VC). To configure ATM QoS or shaping, see “Configuring ATM QoS or Shaping” on page 128. The following QoS features are supported: · CBR, rtVBR, nrtVBR, and UBR · Policing on a per VC basis · Independent PCR and SCR policing · Counting policing actions

9
Circuit Emulation PICs provide pseudowire service towards the core. This section describes the ATM service QoS features. Circuit Emulation PICs support two types of ATM pseudowires: · cell–atm-ccc-cell-relay encapsulation · aal5 –atm-ccc-vc-mux
NOTE: Only ATM pseudowires are supported; no other encapsulation types are supported.

Since cells within a VC cannot be re-ordered, and since only the VC is mapped to a pseudowire, classification is not meaningful in the context of a pseudowire. However, different VCs can be mapped to different classes of traffic and can be classified in the core network. Such a service would connect two ATM networks with an IP/MPLS core. Figure 1 on page 9 shows that the routers marked PE are equipped with Circuit Emulation PICs.
Figure 1: Two ATM Networks with QoS Shaping and Pseudowire Connection
ATM pseudowire

ATM Network

QoS Shape/Policing

g017465

Figure 1 on page 9 shows that traffic is shaped in the egress direction towards the ATM networks. In the ingress direction towards the core, the traffic is policed and the appropriate action is taken. Depending on a very elaborate state machine in the PIC, the traffic is either discarded or sent towards the core with a particular QoS class.
Each port has four transmit queues and one receive queue. Packets arrive from the ingress network on this single queue. Remember that this is per port and multiple VCs arrive on this queue, each with its own QoS class. To simplify unidirectional connections, only a Circuit Emulation PIC (PE 1 router) to Circuit Emulation PIC (PE 2 router) configuration is shown in Figure 2 on page 10.

Figure 2: VC Mapping with Circuit Emulation PICs

ATM Network

vc 7.100

7.101

7.102

PE1

7.103

vc 7.100

7.101

7.102

PE2

7.103

ATM Network

g017466

Figure 2 on page 10 shows the four VCs with different classes mapped to different pseudowires in the core. Each VC has a different QoS class and is assigned a unique queue number. This queue number is copied to the EXP bits in the MPLS header as follows:

Qn concatenated with CLP -> EXP

Qn is 2 bits and can have four combinations; 00, 01, 10, and 11. Since CLP cannot be extracted from the PIC and put into each packet prefix, it is 0. The valid combinations are shown in Table 3 on page 10.

Table 3: Valid EXP Bit Combinations

CLP

For example, VC 7.100 has CBR, VC 7.101 has rt-VBR, 7.102 has nrt-VBR, 7.103 has UBR, and each VC is assigned a queue number as follows:
· VC 7.100 -> 00 · VC 7.101 -> 01 · VC 7.102 -> 10 · VC 7.103 -> 11

NOTE: Lower queue numbers have higher priorities.

11
Each VC will have the following EXP bits: · VC 7.100 -> 000 · VC 7.101 -> 010 · VC 7.102 -> 100 · VC 7.103 -> 110 A packet arriving on VC 7.100 at the ingress router has the queue number 00 before being forwarded to the Packet Forwarding Engine. The Packet Forwarding Engine then translates this to 000 EXP bits in the core. At the egress router, the Packet Forwarding Engine retranslates this to queue 00 and stamps the packet with this queue number. The PIC receiving this queue number sends the packet out on the transmit queue that is mapped to queue 0, which could be the highest priority transmit queue on the egress side. To briefly summarize, shaping and policing are possible. Classification is possible at the VC level by mapping a specific VC to a particular class.
RELATED DOCUMENTATION ATM Support on Circuit Emulation PICs Overview | 81 Configuring ATM QoS or Shaping | 128 shaping

12
CHAPTER 2
Understanding How Circuit Emulation Interfaces Support Converged Networks That Accommodate Both IP And Legacy Services
IN THIS CHAPTER Understanding Mobile Backhaul | 12
Understanding Mobile Backhaul
IN THIS SECTION Mobile Backhaul Application Overview | 12 IP/MPLS-based Mobile Backhaul | 13
In a network of core routers, edge routers, access networks, and other components, the network paths that exist between the core network and edge subnetworks are known as backhaul. This backhaul can be designed as a wired backhaul setup or a wireless backhaul setup or as a combination of both on the basis of your requirement. In a mobile network, the network path between the cell tower and service provider is considered to be backhaul and is called mobile backhaul. The following sections explain mobile backhaul application solution and IP/MPLS-based mobile backhaul solution. Mobile Backhaul Application Overview This topic provides an application example (see Figure 3 on page 13) based on the mobile backhaul reference model where customer edge 1 (CE1) is a base station controller (BSC), provider edge 1 (PE1) is a cell site router, PE2 is an M Series (aggregation) router, and CE2 is a BSC and Radio Network Controller (RNC). The Internet Engineering Task Force (RFC 3895) describes pseudowire as “a mechanism that emulates the

essential attributes of a telecommunications service (such as a T1 leased line or Frame Relay) over a PSN” (Packet Switching Network).

Figure 3: Mobile Backhaul Application

g016956

Emulated Service

Attachment Circuit

PSN tunnel

Attachment Circuit

Pseudowire 1

CE1

PE1

PE2

CE2

Pseudowire 2

Native service

For MX Series routers with ATM MICs with SFP, the mobile backhaul reference model is modified (see Figure 4 on page 13), where the provider edge 1 (PE1) router is an MX Series router with an ATM MIC with SFP. The PE2 router can be any router, such as an M Series (aggregation router) that might or might not support swapping (rewriting) of virtual path identifier (VPI) or virtual circuit identifier (VCI) values. An ATM pseudowire carries ATM cells over an MPLS network. The pseudowire encapsulation can be either cell relay or AAL5. Both modes enable sending of ATM cells between the ATM MIC and the Layer 2 network. You can configure the ATM MIC to swap the VPI value, VCI value, or both. You can also disable swapping of the values.

Figure 4: Mobile Backhaul Application on MX Series Routers with ATM MICs with SFP
Emulated Service

g017797

ATM

CE1

PE1

MPLS

MX Series router

ATM

PE2

CE2

IP/MPLS-based Mobile Backhaul
Juniper Networks IP/MPLS-based mobile backhaul solutions provide the following benefits:
· Flexibility to support converged networks that accommodate both IP and legacy services (leveraging proven circuit emulation techniques).
· Scalability to support emerging data-intensive technologies. · Cost- effectiveness to compensate for rising levels of backhaul traffic.
M7i, M10i, M40e, M120, and M320 routers with 12-port T1/E1 interfaces, 4-port Channelized OC3/STM1 interfaces, and MX Series routers with ATM MICs with SFP, with 2-port OC3/STM1 or 8-port OC12/STM4 circuit emulation interfaces, offer IP/MPLS-based mobile backhaul solutions that enable operators to combine diverse transport technologies onto a single transport architecture, to reduce operating costs while enhancing user features and increasing profits. This architecture accommodates the backhaul of

14
legacy services, emerging IP-based services, location-based services, mobile gaming and mobile TV, and new emerging technologies such as LTE and WiMAX.
RELATED DOCUMENTATION ATM Cell Relay Pseudowire VPI/VCI Swapping Overview | 117 no-vpivci-swapping | 151 psn-vci | 153 psn-vpi | 154

2 PART
Configuring Circuit Emulation Interfaces
Configuring SAToP Support on Circuit Emulation PICs | 16 Configuring SAToP Support on Circuit Emulation MICs | 33 Configuring CESoPSN Support on Circuit Emulation MIC | 50 Configuring ATM Support on Circuit Emulation PICs | 81

16
CHAPTER 3
Configuring SAToP Support on Circuit Emulation PICs
IN THIS CHAPTER Configuring SAToP on 4-Port Channelized OC3/STM1 Circuit Emulation MICs | 16 Configuring SAToP Emulation on T1/E1 Interfaces on 12-Port Channelized T1/E1 Circuit Emulation PICs | 25 Setting the SAToP Options | 30
Configuring SAToP on 4-Port Channelized OC3/STM1 Circuit Emulation MICs
IN THIS SECTION Configuring SONET/SDH Rate-Selectability | 16 Configuring SONET/SDH Framing Mode at the MIC Level | 17 Configuring SONET/SDH Framing Mode at the Port Level | 18 Configuring SAToP Options on T1 interfaces | 19 Configuring SAToP Options on E1 Interfaces | 22
To configure Structure-Agnostic TDM over Packet (SAToP) on a 4-port Channelized OC3/STM1 Circuit Emulation MIC (MIC-3D-4COC3-1COC12-CE), you must configure the framing mode at the MIC level or port level and then configure each port as E1 interface or T1 interface. Configuring SONET/SDH Rate- Selectability You can configure rate-selectability on the Channelized OC3/STM1 (Multi-Rate) MICs with SFP by specifying its port speed as COC3-CSTM1 or COC12-CSTM4. To configure rate-selectability: 1. In configuration mode, go to the [edit chassis fpc slot pic slot port slot] hierarchy level.

17
[edit] user@host# edit chassis fpc slot pic slot port slot For example:
[edit] user@host# edit chassis fpc 1 pic 0 port 0
2. Set the speed as coc3-cstm1 or coc12-cstm4. [edit chassis fpc slot pic slot port slot] user@host# set speed (coc3-cstm1 | coc12-cstm4)
For example:
[edit chassis fpc 1 pic 0 port 0] user@host# set speed coc3-cstm1
NOTE: When the speed is set as coc12-cstm4, instead of configuring COC3 ports down to T1 channels and CSTM1 ports down to E1 channels, you must configure COC12 ports down to T1 channels and CSTM4 channels down to E1 channels.
Configuring SONET/SDH Framing Mode at the MIC Level To configure framing mode at the MIC level: 1. Go to the [edit chassis fpc fpc-slot pic pic-slot] hierarchy level.
[edit] [edit chassis fpc fpc-slot pic pic-slot] 2. Configure the framing mode as SONET for COC3 or SDH for CSTM1. [edit chassis fpc fpc-slot pic pic-slot] user@host# set framing (sonet | sdh)

18
After a MIC is brought online, interfaces are created for the MIC’s available ports on the basis of the MIC type and the configured framing mode of each port: · When the framing sonet statement (for a COC3 Circuit Emulation MIC) is enabled, four COC3 interfaces
are created. · When the framing sdh statement (for a CSTM1 Circuit Emulation MIC) is enabled, four CSTM1 interfaces
are created. · Note that when you do not specify framing mode at the MIC level, then the default framing mode is
SONET for all the four ports.
NOTE: If you set the framing option incorrectly for the MIC type, the commit operation fails. Bit error rate test (BERT) patterns with all ones received by T1/E1 interfaces on Circuit Emulation MICs configured for SAToP do not result in an alarm indication signal (AIS) defect. As a result, the T1/E1 interfaces remain up.
Configuring SONET/SDH Framing Mode at the Port Level
Each port’s framing mode can be configured individually, as either COC3 (SONET) or STM1 (SDH). Ports not configured for framing retain the MIC framing configuration, which is SONET by default if you have not specified framing at the MIC level. To set the framing mode for individual ports, include the framing statement at the [edit chassis fpc fpc-slot pic pic-slot port port- number] hierarchy level: To configure the framing mode as SONET for COC3 or SDH for CSTM1 at port level: 1. Go to the [edit chassis fpc fpc-slot pic pic- slot port port-number] hierarchy level.
[edit] [edit chassis fpc fpc-slot pic pic-slot port port-number] 2. Configure the framing mode as SONET for COC3 or SDH for CSTM1.
[edit chassis fpc fpc-slot pic pic-slot port port-number] user@host# set framing (sonet | sdh)

19
NOTE: Configuring the framing mode at the port level overwrites the previous MIC-level framing mode configuration for the specified port. Subsequently, configuring the MIC-level framing mode overwrites the port-level framing configuration. For example, if you want three STM1 ports and one COC3 port, then it is practical to first configure the MIC for SDH framing and then configure one port for SONET framing.
Configuring SAToP Options on T1 interfaces To configure the SAToP on an T1 interface, you must perform the following tasks: 1. Configuring COC3 Ports Down to T1 Channels | 19 2. Configuring SAToP Options on a T1 interface | 21 Configuring COC3 Ports Down to T1 Channels On any port (numbered 0 through 3) configured for SONET framing, you can configure three COC1 channels (numbered 1 through 3). On each COC1 channel, you can configure 28 T1 channels (numbered 1 through 28). To configure COC3 channelization down to COC1 and then down to T1 channels: 1. In configuration mode, go to the [edit interfaces coc3-fpc- slot/pic-slot/port] [edit] user@host# edit interfaces coc3-fpc-slot/pic- slot/port
For example:
[edit] user@host# edit interfaces coc3-1/0/0
2. Configure the sublevel interface partition index, range of SONET/SDH slices, and sublevel interface type.
[edit interfaces coc3-fpc-slot/pic-slot/port] user@host# set partition partition-number oc-slice oc-slice interface-type coc1
For example:
[edit interfaces coc3-1/0/0]

20
user@host# set partition 1 oc-slice 1 interface-type coc1
3. Enter up command to go to [edit interfaces] hierarchy level. [edit interfaces coc3-fpc-slot/pic-slot/port] user@host# up
4. Configure the channelized OC1 interface, sublevel interface partition index, and the interface type. [edit interfaces] user@host# set coc1-fpc-slot /pic-slot/port:channel-number partition partition-number interface-type t1
For example:
[edit interfaces] user@host# set coc1-1/0/0:1 partition 1 interface-type t1
5. Enter up to go to [edit interfaces] hierarchy level. 6. Configure the FPC slot, MIC slot and the port for T1 interface. Configure the encapsulation as SAToP
and the logical interface for T1 interface. [edit interfaces] user@host# set t1-fpc-slot/pic-slot/port:channel encapsulation encapsulation-type unit interface-unit-number;
For example:
[edit interfaces] user@host# set t1-1/0/:1 encapsulation satop unit 0;
NOTE: Similarly, you can configure the COC12 ports down to T1 channels. When configuring COC12 ports down to T1 channels, on a port configured for SONET framing, you can configure twelve COC1 channels (numbered 1 through 12). On each COC1 channel, you can configure 28 T1 channels (numbered 1 through 28).
After you partition the T1 channels, configure the SAToP options.

21
Configuring SAToP Options on a T1 interface To configure SAToP options on a T1 interface: 1. In configuration mode, go to the [edit interfaces t1-fpc-slot /pic-slot/port] hierarchy level.
[edit] user@host# edit interfaces t1-fpc-slot/pic-slot/port
2. Use the edit command to go to the satop-options hierarchy level. [edit interfaces t1-fpc-slot/pic-slot/port] user@host# edit satop-options
3. Configure the following SAToP options: · excessive-packet-loss-rate–Set packet loss options. The options are sample-period and threshold. [edit interfaces t1-fpc-slot/pic-slot/port satop-options] user@host# set excessive- packet-loss-rate sample-period sample-period threshold percentile · idle- pattern–An 8-bit hexadecimal pattern to replace TDM data in a lost packet (from 0 through 255). [edit interfaces t1-fpc-slot/pic-slot/port satop- options] user@host# set idle-pattern pattern · jitter-buffer-auto- adjust–Automatically adjust the jitter buffer. [edit interfaces t1-fpc-slot /pic-slot/port satop-options] user@host# set jitter-buffer-auto-adjust
NOTE: The jitter-buffer-auto-adjust option is not applicable on MX Series routers.
· jitter-buffer-latency–Time delay in the jitter buffer (from 1 through 1000 milliseconds). [edit interfaces t1-fpc-slot/pic-slot/port satop-options] user@host# set jitter-buffer-latency milliseconds
· jitter-buffer-packets–Number of packets in the jitter buffer (from 1 through 64 packets).

22
[edit interfaces t1-fpc-slot/pic-slot/port satop-options] user@host# set jitter-buffer-packets packets · payload-size–Configure the payload size, in bytes (from 32 through 1024 bytes). [edit interfaces t1-fpc-slot/pic-slot/port satop-options] user@host# set payload-size bytes
Configuring SAToP Options on E1 Interfaces To configure the SAToP on an E1 interface. 1. Configuring CSTM1 Ports Down to E1 Channels | 22 2. Configuring SAToP Options on E1 Interfaces | 23 Configuring CSTM1 Ports Down to E1 Channels On any port (numbered 0 through 3) configured for SDH framing, you can configure one CAU4 channel. On each CAU4 channel, you can configure 63 E1 channels (numbered 1 through 63). To configure CSTM1 channelization down to CAU4 and then down to E1 channels. 1. In configuration mode, go to the [edit interfaces cstm1-fpc-slot/pic-slot/port] [edit] [edit interfaces cstm1-fpc- slot/pic-slot/port] For example:
[edit] [edit interfaces cstm1-1/0/1] 2. Configure the channelize interface as clear channel and the set the interface-type as cau4 [edit interfaces cstm1 -fpc-slot/pic-slot/port] user@host# set no-partition interface-type cau4;
3. Enter up to go to [edit interfaces] hierarchy level.
4. Configure the FPC slot, MIC slot and the port for CAU4 interface. Configure the sublevel interface partition index and the interface type as E1.

23
[edit interfaces] user@host# set cau4-fpc-slot/pic-slot/port partition partition-number interface-type e1 For example:
[edit interfaces] user@host# set cau4-1/0/1 partition 1 interface-type e1
5. Enter up to go to [edit interfaces] hierarchy level. 6. Configure the FPC slot, MIC slot and the port for E1 interface. Configure the encapsulation as SAToP
and the logical interface for E1 interface. [edit interfaces] user@host# set e1-fpc-slot/pic-slot/port:channel encapsulation encapsulation-type unit interface-unit-number;
For example:
[edit interfaces] user@host# set e1-1/0/:1 encapsulation satop unit 0;
NOTE: Similarly, you can configure the CSTM4 channels down to E1 channels.
After you configure the E1 channels, configure the SAToP options. Configuring SAToP Options on E1 Interfaces To configure SAToP options on E1 interfaces: 1. In configuration mode, go to the [edit interfaces e1-fpc-slot/pic-slot/port] hierarchy level.
[edit] user@host# edit interfaces e1-fpc-slot/pic-slot/port
2. Use the edit command to go to the satop-options hierarchy level. [edit interfaces e1-fpc-slot/pic-slot/port] user@host# edit satop-options

24
3. Configure the following SAToP options: · excessive-packet-loss-rate–Set packet loss options. The options are sample-period and threshold. [edit interfaces e1-fpc-slot/pic-slot/port satop-options] user@host# set excessive- packet-loss-rate sample-period sample-period threshold percentile · idle- pattern–An 8-bit hexadecimal pattern to replace TDM data in a lost packet (from 0 through 255). [edit interfaces e1-fpc-slot/pic-slot/port satop- options] user@host# set idle-pattern pattern · jitter-buffer-auto- adjust–Automatically adjust the jitter buffer. [edit interfaces e1-fpc-slot /pic-slot/port satop-options] user@host# set jitter-buffer-auto-adjust
NOTE: The jitter-buffer-auto-adjust option is not applicable on MX Series routers.
· jitter-buffer-latency–Time delay in the jitter buffer (from 1 through 1000 milliseconds). [edit interfaces e1-fpc-slot/pic-slot/port satop-options] user@host# set jitter-buffer-latency milliseconds
· jitter-buffer-packets–Number of packets in the jitter buffer (from 1 through 64 packets). [edit interfaces e1-fpc-slot/pic-slot/port satop-options] user@host# set jitter-buffer-packets packets
· payload-size–Configure the payload size, in bytes (from 32 through 1024 bytes). [edit interfaces e1-fpc-slot/pic-slot/port satop-options] user@host# set payload-size bytes
RELATED DOCUMENTATION Understanding Circuit Emulation Services and the Supported PIC Types | 2

25
Configuring SAToP Emulation on T1/E1 Interfaces on 12-Port Channelized T1/E1 Circuit Emulation PICs
IN THIS SECTION Setting the Emulation Mode | 25 Configuring SAToP Emulation on T1/E1 Interfaces | 26
The following sections describes configuring SAToP on the 12-port Channelized T1/E1 Circuit Emulation PICs:
Setting the Emulation Mode To set the framing emulation mode, include the framing statement at the [edit chassis fpc fpc-slot pic pic-slot] hierarchy level:
[edit chassis fpc fpc-slot pic pic-slot] user@host# set framing (t1 | e1);
After a PIC is brought online, interfaces are created for the PIC’s available ports according to the PIC type and the framing option used: · If you include the framing t1 statement (for a T1 Circuit Emulation PIC), 12 CT1 interfaces are created. · If you include the framing e1 statement (for an E1 Circuit Emulation PIC), 12 CE1 interfaces are created.
NOTE: If you set the framing option incorrectly for the PIC type, the commit operation fails. Circuit Emulation PICs with SONET and SDH ports require prior channelization down to T1 or E1 before you can configure them. Only T1/E1 channels support SAToP encapsulation or SAToP options. Bit error rate test (BERT) patterns with all ones received by T1/E1 interfaces on Circuit Emulation PICs configured for SAToP do not result in an alarm indication signal (AIS) defect. As a result, the T1/E1 interfaces remain up.

26
Configuring SAToP Emulation on T1/E1 Interfaces Setting the Encapsulation Mode | 26 Configuring Loopback for a T1 Interface or an E1 Interface | 27 Setting the SAToP Options | 27 Configuring the Pseudowire Interface | 28
Setting the Encapsulation Mode E1 channels on Circuit Emulation PICs can be configured with SAToP encapsulation at the provider edge (PE) router, as follows:
NOTE: The below mentioned procedure can be used to configure T1 channels on circuit emulation PICs with SAToP encapsulation at the PE router.
1. In the configuration mode, go to [edit interfaces e1-fpc-slot/pic- slot/port] hierarchy level. [edit] user@host# [edit interfaces e1 fpc-slot /pic-slot/port] For example:
[edit] [edit interfaces e1-1/0/0] 2. Configure SAToP encapsulation and the logical interface for E1 interface
[edit interfaces e1-1/0/0] user@host# set encapsulation encapsulation-typeunit interface-unit-number;
For example:
[edit interfaces e1-1/0/0] user@host# set encapsulation satop unit 0;
You do not need to configure any cross-connect circuit family because it is automatically created for the above encapsulation.

27
Configuring Loopback for a T1 Interface or an E1 Interface To configure loopback capability between the local T1 interface and the remote channel service unit (CSU), see Configuring T1 Loopback Capability. To configure loopback capability between the local E1 interface and the remote channel service unit (CSU), see Configuring E1 Loopback Capability.
NOTE: By default, no loopback is configured.
Setting the SAToP Options To configure SAToP options on T1/E1 interfaces: 1. In configuration mode, go to the [edit interfaces e1-fpc-slot/pic-slot/port] hierarchy level.
[edit] user@host# edit interfaces e1-fpc-slot/pic-slot/port
For example:
[edit] user@host# edit interfaces e1-1/0/0
2. Use the edit command to go to the satop-options hierarchy level.
[edit] user@host# edit satop-options
3. In this hierarchy level, using the set command you can configure the following SAToP options: · excessive-packet-loss-rate–Set packet loss options. The options are groups, sample-period, and threshold. · groups–Specify groups. · sample-period–Time required to calculate excessive packet loss rate (from 1000 through 65,535 milliseconds). · threshold–Percentile designating the threshold of excessive packet loss rate (1100 percent). · idle-pattern–An 8-bit hexadecimal pattern to replace TDM data in a lost packet (from 0 through 255). · jitter-buffer-auto-adjust–Automatically adjust the jitter buffer.

28
NOTE: The jitter-buffer-auto-adjust option is not applicable on MX Series routers.
· jitter-buffer-latency–Time delay in the jitter buffer (from 1 through 1000 milliseconds). · jitter-buffer-packets–Number of packets in the jitter buffer (from 1 through 64 packets). · payload-size–Configure the payload size, in bytes (from 32 through 1024 bytes).
NOTE: In this section, we are configuring only one SAToP option. You can follow the same method to configure all the other SAToP options.
[edit interfaces e1-1/0/0 satop-options] user@host# set excessive-packet-loss- rate sample-period sample-period For example:
[edit interfaces e1-1/0/0 satop-options] user@host# set excessive-packet-loss- rate sample-period 4000
To verify this configuration, use the show command at the [edit interfaces e1-1/0/0] hierarchy level:
[edit interfaces e1-1/0/0] user@host# show satop-options {
excessive-packet-loss-rate { sample-period 4000;
} }
SEE ALSO satop-options | 155
Configuring the Pseudowire Interface To configure the TDM pseudowire at the provider edge (PE) router, use the existing Layer 2 circuit infrastructure, as shown in the following procedure: 1. In the configuration mode, go to [edit protocols l2circuit] hierarchy level.

29
[edit] user@host# edit protocol l2circuit
2. Configure the IP address of the neighboring router or switch, interface forming the layer 2 circuit and the identifier for the layer 2 circuit.
[edit protocol l2circuit] user@host# set neighbor ip-address interface interface-name-fpc-slot/pic-slot/port.interface-unit-number
virtual-circuit-id virtual-circuit-id;
NOTE: To configure T1 interface as the layer 2 circuit, replace e1 with t1 in the below statement.
For example:
[edit protocol l2circuit] user@host# set neighbor 10.255.0.6 interface e1-1/0/0.0 virtual-circuit-id 1
3. To verify the configuration use the show command at the [edit protocols l2circuit] hierarchy level.
[edit protocols l2circuit] user@host# show neighbor 10.255.0.6 {
interface e1-1/0/0.0 { virtual-circuit-id 1;
} }
After the customer edge (CE)-bound interfaces (for both PE routers) are configured with proper encapsulation, payload size, and other parameters, the two PE routers try to establish a pseudowire with Pseudowire Emulation Edge- to-Edge (PWE3) signaling extensions. The following pseudowire interface configurations are disabled or ignored for TDM pseudowires: · ignore- encapsulation · mtu The supported pseudowire types are: · 0x0011 Structure- Agnostic E1 over Packet

30
· 0x0012 Structure-Agnostic T1 (DS1) over Packet When the local interface parameters match the received parameters, and the pseudowire type and control word bit are equal, the pseudowire is established. For detailed information about configuring TDM pseudowire, see the Junos OS VPNs Library for Routing Devices. For detailed information about PICs, see the PIC Guide for your router.
NOTE: When T1 is used for SAToP, the T1 facility data-link (FDL) loop is not supported on the CT1 interface device. The is because SAToP does not analyze T1 framing bits.
RELATED DOCUMENTATION Understanding Mobile Backhaul | 12 Understanding Circuit Emulation Services and the Supported PIC Types | 2 Configuring SAToP on 4-Port Channelized OC3/STM1 Circuit Emulation MICs | 16
Setting the SAToP Options
To configure SAToP options on T1/E1 interfaces: 1. In configuration mode, go to the [edit interfaces e1-fpc-slot/pic-slot/port] hierarchy level.
[edit] user@host# edit interfaces e1-fpc-slot/pic-slot/port For example:
[edit] user@host# edit interfaces e1-1/0/0
2. Use the edit command to go to the satop-options hierarchy level. [edit] user@host# edit satop-options

31
3. In this hierarchy level, using the set command you can configure the following SAToP options: · excessive-packet-loss-rate–Set packet loss options. The options are groups, sample-period, and threshold. · groups–Specify groups. · sample-period–Time required to calculate excessive packet loss rate (from 1000 through 65,535 milliseconds). · threshold–Percentile designating the threshold of excessive packet loss rate (1100 percent). · idle-pattern–An 8-bit hexadecimal pattern to replace TDM data in a lost packet (from 0 through 255). · jitter-buffer-auto-adjust–Automatically adjust the jitter buffer.
NOTE: The jitter-buffer-auto-adjust option is not applicable on MX Series routers.
· jitter-buffer-latency–Time delay in the jitter buffer (from 1 through 1000 milliseconds). · jitter-buffer-packets–Number of packets in the jitter buffer (from 1 through 64 packets). · payload-size–Configure the payload size, in bytes (from 32 through 1024 bytes).
NOTE: In this section, we are configuring only one SAToP option. You can follow the same method to configure all the other SAToP options.
[edit interfaces e1-1/0/0 satop-options] user@host# set excessive-packet-loss- rate sample-period sample-period
For example:
[edit interfaces e1-1/0/0 satop-options] user@host# set excessive-packet-loss- rate sample-period 4000
To verify this configuration, use the show command at the [edit interfaces e1-1/0/0] hierarchy level:
[edit interfaces e1-1/0/0] user@host# show satop-options {
excessive-packet-loss-rate {

32
sample-period 4000; } }
RELATED DOCUMENTATION satop-options | 155

33
CHAPTER 4
Configuring SAToP Support on Circuit Emulation MICs
IN THIS CHAPTER Configuring SAToP on 16-Port Channelized E1/T1 Circuit Emulation MIC | 33 Configuring SAToP Encapsulation on T1/E1 Interfaces | 36 SAToP Emulation on T1 and E1 Interfaces Overview | 41 Configuring SAToP Emulation on Channelized T1 and E1 Interfaces | 42
Configuring SAToP on 16-Port Channelized E1/T1 Circuit Emulation MIC
IN THIS SECTION Configuring T1/E1 Framing Mode at the MIC Level | 33 Configuring CT1 Ports Down to T1 Channels | 34 Configuring CT1 Ports Down to DS Channels | 35
The following sections describes configuring SAToP on the 16-Port Channelized E1/T1 Circuit Emulation MIC (MIC-3D-16CHE1-T1-CE). Configuring T1/E1 Framing Mode at the MIC Level To configure the framing emulation mode at the MIC level. 1. Go to the [edit chassis fpc fpc-slot pic pic-slot] hierarchy level.
[edit] [edit chassis fpc fpc-slot pic pic-slot] 2. Configure the framing emulation mode as E1 or T1.

34
[edit chassis fpc fpc-slot pic pic-slot] user@host# set framing (t1 | e1)
After a MIC is brought online, interfaces are created for the MIC’s available ports on the basis of the MIC type and the framing option used: · If you include the framing t1 statement, 16 channelized T1 (CT1) interfaces are created. · If you include the framing e1 statement, 16 channelized E1 (CE1) interfaces are created.
NOTE: If you set the framing option incorrectly for the MIC type, the commit operation fails. By default, t1 framing mode is selected. Circuit Emulation PICs with SONET and SDH ports require prior channelization down to T1 or E1 before you can configure them. Only T1/E1 channels support SAToP encapsulation or SAToP options.
Bit error rate test (BERT) patterns with all binary 1s (ones) received by CT1/CE1 interfaces on Circuit Emulation MICs configured for SAToP do not result in an alarm indication signal (AIS) defect. As a result, the CT1/CE1 interfaces remain up.
Configuring CT1 Ports Down to T1 Channels To configure a CT1 port down to a T1 channel, use the following procedure:
NOTE: To configure a CE1 port down to the E1 channel, replace ct1 with ce1 and t1 with e1 in the procedure.
1. In configuration mode, go to the [edit interfaces ct1-mpc-slot/mic-slot /port-number] hierarchy level. [edit] user@host# edit interfaces ct1-mpc-slot /mic-slot/port-number
For example:
[edit] user@host# edit interfaces ct1-1/0/0

35
2. On the CT1 interface, set the no-partition option and then set the interface type as T1. [edit interfaces ct1-mpc-slot/mic-slot/port-number] user@host# set no-partition interface-type t1
In the following example, the ct1-1/0/1 interface is configured to be of type T1 and to have no partitions.
[edit interfaces ct1-1/0/1] user@host# set no-partition interface-type t1
Configuring CT1 Ports Down to DS Channels To configure a channelized T1 (CT1) port down to a DS channel, include the partition statement at the [edit interfaces ct1-mpc-slot/mic-slot/port-number] hierarchy level:
NOTE: To configure a CE1 port down to a DS channel, replace ct1 with ce1 in the following procedure.
1. In configuration mode, go to the [edit interfaces ct1-mpc-slot/mic-slot /port-number] hierarchy level. [edit] user@host# edit interfaces ct1-mpc-slot /mic-slot/port-number
For example:
[edit] user@host# edit interfaces ct1-1/0/0
2. Configure the partition, the time slot, and the interface type. [edit interfaces ct1-mpc-slot/mic-slot/port-number] user@host# set partition partition-number timeslots timeslots interface-type ds
In the following example, the ct1-1/0/0 interface is configured as a DS interface with one partition and three time slots:
[edit interfaces ct1-1/0/0] user@host# set partition 1 timeslots 1-4,9,22-24 interface-type ds

36
To verify the configuration of the ct1-1/0/0 interface, use the show command at the [edit interfaces ct1-1/0/0] hierarchy level.
[edit interfaces ct1-1/0/0] user@host# show partition 1 timeslots 1-4,9,22-24 interface-type ds; An NxDS0 interface can be configured from channelized T1 interface. Here N represents the time slots on the CT1 interface. The value of N is: · 1 through 24 when a DS0 interface is configured from a CT1 interface. · 1 through 31 when a DS0 interface is configured from a CE1 interface. After you partition the DS interface, configure the SAToP options on it. See “Setting the SAToP Options” on page 27.
RELATED DOCUMENTATION Understanding Circuit Emulation Services and the Supported PIC Types | 2 Setting the SAToP Options | 27
Configuring SAToP Encapsulation on T1/E1 Interfaces
IN THIS SECTION Setting the Encapsulation Mode | 37 T1/E1 Loopback Support | 37 T1 FDL Support | 38 Setting the SAToP Options | 38 Configuring the Pseudowire Interface | 39
This configuration applies to the mobile backhaul application shown in Figure 3 on page 13. This topic includes the following tasks:

37
Setting the Encapsulation Mode E1 channels on Circuit Emulation MICs can be configured with SAToP encapsulation at the provider edge (PE) router, as follows:
NOTE: The following procedure can be used to configure T1 channels on Circuit Emulation MICs with SAToP encapsulation at the PE router.
1. In configuration mode, go to the [edit interfaces e1-fpc-slot/pic- slot/port] hierarchy level. [edit] user@host# edit interfaces e1-fpc-slot/pic- slot/port
For example:
[edit] user@host# edit interfaces e1-1/0/0
2. Configure the SAToP encapsulation and the logical interface for E1 interface. [edit interfaces e1-1/0/0] user@host# set encapsulation satop unit interface-unit-number
For example:
[edit interfaces e1-1/0/0] user@host# set encapsulation satop unit 0
You do not need to configure any cross-connect circuit family because it is automatically created for the SAToP encapsulation. T1/E1 Loopback Support Use the CLI to configure remote and local loopback as T1 (CT1) or E1 (CE1). By default, no loopback is configured. See Configuring T1 Loopback Capability and Configuring E1 Loopback Capability.

38
T1 FDL Support If T1 is used for SAToP, the T1 facility data-link (FDL) loop is not supported on the CT1 interface device because SAToP does not analyze T1 framing bits.
Setting the SAToP Options To configure SAToP options on T1/E1 interfaces: 1. In configuration mode, go to the [edit interfaces e1-fpc-slot/pic-slot/port] hierarchy level.
[edit] user@host# edit interfaces e1-fpc-slot/pic-slot/port
For example:
[edit] user@host# edit interfaces e1-1/0/0
2. Use the edit command to go to the satop-options hierarchy level.
[edit] user@host# edit satop-options
3. In this hierarchy level, using the set command you can configure the following SAToP options: · excessive-packet-loss-rate–Set packet loss options. The options are groups, sample-period, and threshold. · groups–Specify groups. · sample-period–Time required to calculate excessive packet loss rate (from 1000 through 65,535 milliseconds). · threshold–Percentile designating the threshold of excessive packet loss rate (1100 percent). · idle-pattern–An 8-bit hexadecimal pattern to replace TDM data in a lost packet (from 0 through 255). · jitter-buffer-auto-adjust–Automatically adjust the jitter buffer.
NOTE: The jitter-buffer-auto-adjust option is not applicable on MX Series routers.

39
· jitter-buffer-latency–Time delay in the jitter buffer (from 1 through 1000 milliseconds). · jitter-buffer-packets–Number of packets in the jitter buffer (from 1 through 64 packets). · payload-size–Configure the payload size, in bytes (from 32 through 1024 bytes).
NOTE: In this section, we are configuring only one SAToP option. You can follow the same method to configure all the other SAToP options.
[edit interfaces e1-1/0/0 satop-options] user@host# set excessive-packet-loss- rate sample-period sample-period For example:
[edit interfaces e1-1/0/0 satop-options] user@host# set excessive-packet-loss- rate sample-period 4000
To verify this configuration, use the show command at the [edit interfaces e1-1/0/0] hierarchy level:
[edit interfaces e1-1/0/0] user@host# show satop-options {
excessive-packet-loss-rate { sample-period 4000;
} }
SEE ALSO satop-options | 155
Configuring the Pseudowire Interface To configure the TDM pseudowire at the provider edge (PE) router, use the existing Layer 2 circuit infrastructure, as shown in the following procedure: 1. In configuration mode, go to the [edit protocols l2circuit] hierarchy level.
[edit]

40
user@host# edit protocol l2circuit
2. Configure the IP address of the neighboring router or switch, the interface forming the Layer 2 circuit, and the identifier for the Layer 2 circuit.
[edit protocol l2circuit] user@host# set neighbor ip-address interface interface-name-fpc-slot/pic-slot/port.interface-unit-number
virtual-circuit-id virtual-circuit-id
NOTE: To configure the T1 interface as the Layer 2 circuit, replace e1 with t1 in the configuration statement.
For example:
[edit protocol l2circuit] user@host# set neighbor 10.255.0.6 interface e1-1/0/0.0 virtual-circuit-id 1
3. To verify this configuration, use the show command at the [edit protocols l2circuit] hierarchy level.
[edit protocols l2circuit] user@host# show neighbor 10.255.0.6 {
interface e1-1/0/0.0 { virtual-circuit-id 1;
} }
After the customer edge (CE)-bound interfaces (for both PE routers) are configured with proper encapsulation, payload size, and other parameters, the two PE routers try to establish a pseudowire with Pseudowire Emulation Edge- to-Edge (PWE3) signaling extensions. The following pseudowire interface configurations are disabled or ignored for TDM pseudowires: · ignore- encapsulation · mtu The supported pseudowire types are: · 0x0011 Structure- Agnostic E1 over Packet

41
· 0x0012 Structure-Agnostic T1 (DS1) over Packet When the local interface parameters match the received parameters, and the pseudowire type and control word bit are equal, the pseudowire is established. For detailed information about configuring TDM pseudowire, see the Junos OS VPNs Library for Routing Devices. For detailed information about MICs, see the PIC Guide for your router.

RELATED DOCUMENTATION Understanding Mobile Backhaul | 12

SAToP Emulation on T1 and E1 Interfaces Overview
Structure-Agnostic time-division multiplexing (TDM) over Packet (SAToP), as defined in RFC 4553, Structure-Agnostic TDM over Packet (SAToP) is supported on the ACX Series Universal Metro routers with built-in T1 and E1 interfaces. SAToP is used for pseudowire encapsulation for TDM bits (T1, E1). The encapsulation disregards any structure imposed on the T1 and E1 streams, in particular the structure imposed by standard TDM framing. SAToP is used over packet-switched networks, where the provider edge (PE) routers do not need to interpret TDM data or participate in the TDM signaling.
NOTE: ACX5048 and ACX5096 routers do not support SAToP.

Figure 5 on page 41 shows a packet-switched network (PSN) in which two PE routers (PE1 and PE2) provide one or more pseudowires to customer edge (CE) routers (CE1 and CE2), establishing a PSN tunnel to provide a data path for the pseudowire.

Figure 5: Pseudowire Encapsulation with SAToP

g016956

Emulated Service

Attachment Circuit

PSN tunnel

Attachment Circuit

Pseudowire 1

CE1

PE1

PE2

CE2

Pseudowire 2

Native service

Pseudowire traffic is invisible to the core network, and the core network is transparent to the CEs. Native data units (bits, cells, or packets) arrive via the attachment circuit, are encapsulated in a pseudowire protocol

42
data unit (PDU), and carried across the underlying network via the PSN tunnel. The PEs perform the necessary encapsulation and the decapsulation of the pseudowire PDUs and handle any other function required by the pseudowire service, such as sequencing or timing.
RELATED DOCUMENTATION Configuring SAToP Emulation on Channelized T1 and E1 Interfaces | 42
Configuring SAToP Emulation on Channelized T1 and E1 Interfaces
IN THIS SECTION Setting the T1/E1 Emulation Mode | 43 Configuring One Full T1 or E1 Interface on Channelized T1 and E1 Interfaces | 44 Setting the SAToP Encapsulation Mode | 48 Configure the Layer 2 Circuit | 48
This configuration is the base configuration of SAToP on an ACX Series router as described in RFC 4553, Structure-Agnostic Time Division Multiplexing (TDM) over Packet (SAToP). When you configure SAToP on built-in channelized T1 and E1 interfaces, the configuration results in a pseudowire that acts as a transport mechanism for the T1 and E1 circuit signals across a packet-switched network. The network between the customer edge (CE) routers appears transparent to the CE routers, making it seem that the CE routers are directly connected. With the SAToP configuration on the provider edge (PE) router’s T1 and E1 interfaces, the interworking function (IWF) forms a payload (frame) that contains the CE router’s T1 and E1 Layer 1 data and control word. This data is transported to the remote PE over the pseudowire. The remote PE removes all the Layer 2 and MPLS headers added in the network cloud and forwards the control word and the Layer 1 data to the remote IWF, which in turn forwards the data to the remote CE.

Figure 6: Pseudowire Encapsulation with SAToP

g016956

Emulated Service

Attachment Circuit

PSN tunnel

Attachment Circuit

Pseudowire 1

CE1

PE1

PE2

CE2

Pseudowire 2

Native service

In Figure 6 on page 43 the Provider Edge (PE) router represents the ACX Series router that is being configured in these steps. The result of these steps is the pseudowire from PE1 to PE2. Topics include:

Setting the T1/E1 Emulation Mode
Emulation is a mechanism that duplicates the essential attributes of a service (such as T1 or E1) over a packet-switched network. You set the emulation mode so that the built-in channelized T1 and E1 interfaces on the ACX Series router can be configured to work in either T1 or E1 mode. This configuration is at the PIC level, so all ports operate as either T1 interfaces or E1 interfaces. A mix of T1 and E1 interfaces is not supported. By default all the ports operate as T1 interfaces.
· Configure the emulation mode: [edit chassis fpc fpc-slot pic pic-slot] user@host# set framing (t1 | e1) For example:
[edit chassis fpc 0 pic 0] user@host# set framing t1 After a PIC is brought online and depending on the framing option used (t1 or e1), on the ACX2000 router, 16 CT1 or 16 CE1 interfaces are created, and on the ACX1000 router, 8 CT1 or 8 CE1 interfaces are created.
The following output shows this configuration:

user@host# show chassis fpc 0 {
pic 0 { framing t1;
} }
The following output from the show interfaces terse command shows the 16 CT1 interfaces created with the framing configuration.

user@host# run show interfaces terse

Interface

Admin Link Proto

ct1-0/0/0

up down

ct1-0/0/1

up down

ct1-0/0/2

up down

ct1-0/0/3

up down

ct1-0/0/4

up down

ct1-0/0/5

up down

ct1-0/0/6

up down

ct1-0/0/7

up down

ct1-0/0/8

up down

ct1-0/0/9

up down

ct1-0/0/10

up down

ct1-0/0/11

up down

ct1-0/0/12

up down

ct1-0/0/13

up down

ct1-0/0/14

up down

ct1-0/0/15

up down

Local

Remote

NOTE: If you set the framing option incorrectly for the PIC type, the commit operation fails.
If you change the mode, the router will reboot the built-in T1 and E1 interfaces.
Bit error rate test (BERT) patterns with all ones received by T1 and E1 interfaces configured for SAToP do not result in an alarm indication signal (AIS) defect. As a result, the T1 and E1 interfaces remain up.

SEE ALSO
SAToP Emulation on T1 and E1 Interfaces Overview | 41
Configuring One Full T1 or E1 Interface on Channelized T1 and E1 Interfaces
You must configure a child T1 or E1 interface on the built-in channelized T1 or E1 interface created because the channelized interface is not a configurable interface and SAToP encapsulation must be configured (in the next step) for the pseudowire to function. The following configuration creates one full T1 interface on the channelized ct1 interface. You can follow the same process to create one E1 interface on the channelized ce1 interface. · Configure one full T1/E1 interface:

[edit interfaces ct1-fpc/pic /port] user@host# set no-partition interface-type (t1 | e1) For example: [edit interfaces ct1-0/0/0 user@host# set no-partition interface-type t1
The following output shows this configuration:
[edit] user@host# show interfaces ct1-0/0/0 {
no-partition interface-type t1; }

The preceding command creates the t1-0/0/0 interface on the channelized ct1-0/0/0 interface. Check the configuration with the show interfaces interface-name extensive command. Run the command to display output for the channelized interface and the newly created T1 or E1interface. The following output provides an example of the output for a CT1 interface and the T1 interface created from the preceding example configuration. Notice that ct1-0/0/0 is running at T1 speed and that the media is T1.

user@host> show interfaces ct1-0/0/0 extensive

Physical interface: ct1-0/0/0, Enabled, Physical link is Up

Interface index: 152, SNMP ifIndex: 780, Generation: 1294

Link-level type: Controller, Clocking: Internal, Speed: T1, Loopback: None, Framing:

ESF, Parent: None

Device flags : Present Running

Interface flags: Point-To-Point SNMP-Traps Internal: 0x0

Link flags

: None

Hold-times

: Up 0 ms, Down 0 ms

CoS queues

: 8 supported, 4 maximum usable queues

Last flapped : 2012-04-03 06:27:55 PDT (00:13:32 ago)

Statistics last cleared: 2012-04-03 06:40:34 PDT (00:00:53 ago)

DS1 alarms : None

DS1 defects : None

T1 media:

Seconds

Count State

SEF

0 OK

BEE

0 OK

AIS

0 OK

LOF

0 OK

LOS

0 OK

YELLOW

0 OK

CRC Major

0 OK

CRC Minor

0 OK

BPV

EXZ

LCV

PCV

CRC

LES

SES

SEFS

BES

UAS

Line encoding: B8ZS

Buildout

: 0 to 132 feet

DS1 BERT configuration:

BERT time period: 10 seconds, Elapsed: 0 seconds

Induced Error rate: 0, Algorithm: 2^15 – 1, O.151, Pseudorandom (9)

Packet Forwarding Engine configuration:

Destination slot: 0 (0x00)

In the following output for the T1 interface, the parent interface is shown as ct1-0/0/0 and the link level type and encapsulation are TDM-CCC-SATOP.

user@host> show interfaces t1-0/0/0 extensive

Physical interface: t1-0/0/0, Enabled, Physical link is Up

Interface index: 160, SNMP ifIndex: 788, Generation: 1302

Link-level type: TDM-CCC-SATOP, MTU: 1504, Speed: T1, Loopback: None, FCS: 16,

Parent: ct1-0/0/0 Interface index 152

Device flags : Present Running

Interface flags: Point-To-Point SNMP-Traps Internal: 0x0

Link flags

: None

Hold-times

: Up 0 ms, Down 0 ms

CoS queues

: 8 supported, 4 maximum usable queues

Last flapped : 2012-04-03 06:28:43 PDT (00:01:16 ago)

Statistics last cleared: 2012-04-03 06:29:58 PDT (00:00:01 ago)

Egress queues: 8 supported, 4 in use

Queue counters:

Queued packets Transmitted packets

Dropped packets

0 best-effort

1 expedited-fo

2 assured-forw

3 network-cont

Queue number:

Mapped forwarding classes

best-effort

expedited-forwarding

assured-forwarding

network-control

DS1 alarms : None

DS1 defects : None

SAToP configuration:

Payload size: 192

Idle pattern: 0xFF

Octet aligned: Disabled

Jitter buffer: packets: 8, latency: 7 ms, auto adjust: Disabled

Excessive packet loss rate: sample period: 10000 ms, threshold: 30%

Packet Forwarding Engine configuration:

Destination slot: 0

CoS information:

Direction : Output

CoS transmit queue

Bandwidth

Buffer Priority

Limit

bps

usec

0 best-effort

1459200 95

low

none

3 network-control

76800

low

none

Logical interface t1-0/0/0.0 (Index 308) (SNMP ifIndex 789) (Generation 11238)

Flags: Point-To-Point SNMP-Traps Encapsulation: TDM-CCC-SATOP

CE info

Packets

Bytes Count

CE Tx

CE Rx

CE Rx Forwarded

CE Strayed

CE Lost

CE Malformed

CE Misinserted

CE AIS dropped

CE Dropped

CE Overrun Events

CE Underrun Events

Protocol ccc, MTU: 1504, Generation: 13130, Route table: 0

48
Setting the SAToP Encapsulation Mode
The built-in T1 and E1 interfaces must be configured with SAToP encapsulation at the PE router so that the interworking function (IWF) can segment and encapsulate TDM signals into SAToP packets, and in the reverse direction, to decapsulate the SAToP packets and reconstitute them into TDM signals. 1. On the PE router, configure SAToP encapsulation on the physical interface:
[edit interfaces (t1 | e1)fpc/pic /port] user@host# set encapsulation satop For example: [edit interfaces t1-0/0/0 user@host# set encapsulation satop
2. On the PE router, configure the logical interface: [edit interfaces ] user@host# set (t1 | e1)fpc/pic/port unit logical-unit-number For example: [edit interfaces] user@host# set t1-0/0/0 unit 0 It is not necessary to configure the circuit cross-connect (CCC) family because it is automatically created for the preceding encapsulation. The following output shows this configuration.
[edit interfaces] user@host# show t1-0/0/0 encapsulation satop; unit 0;
Configure the Layer 2 Circuit
When you configure the Layer 2 circuit, you designate the neighbor for the provider edge (PE) router. Each Layer 2 circuit is represented by the logical interface connecting the local PE router to the local customer edge (CE) router. All the Layer 2 circuits that use a particular remote PE router, designated for remote CE routers, are listed under the neighbor statement. Each neighbor is identified by its IP address and is usually the end-point destination for the label-switched path (LSP) tunnel that transports the Layer 2 circuit. Configure the Layer 2 circuit: · [edit protocols l2circuit neighbor address] user@host# set interface interface-name virtual-circuit-id identifier

49
For example, for a T1 interface: [edit protocols l2circuit neighbor 2.2.2.2 user@host# set interface t1-0/0/0.0 virtual-circuit-id 1 The preceding configuration is for a T1 interface. To configure an E1 interface, use the E1 interface parameters. The following output shows this configuration.
[edit protocols l2circuit] user@host# show neighbor 2.2.2.2 interface t1-0/0/0.0 {
virtual-circuit-id 1; }
SEE ALSO Configuring Interfaces for Layer 2 Circuits Overview Enabling the Layer 2 Circuit When the MTU Does Not Match

50
CHAPTER 5
Configuring CESoPSN Support on Circuit Emulation MIC
IN THIS CHAPTER TDM CESoPSN Overview | 50 Configuring TDM CESoPSN on ACX Series Routers Overview | 51 Configuring CESoPSN on Channelized E1/T1 Circuit Emulation MIC | 53 Configuring CESoPSN on Channelized OC3/STM1 (Multi-Rate) Circuit Emulation MIC with SFP | 58 Configuring CESoPSN Encapsulation on DS Interfaces | 70 Configuring CE1 Channels Down to DS Interfaces | 74 Configuring CESoPSN on Channelized E1/T1 Circuit Emulation MIC on ACX Series | 77
TDM CESoPSN Overview
Circuit Emulation Service over Packet-Switched Network (CESoPSN) is an encapsulation layer intended to carry NxDS0 services over a packet-switched network (PSN). CESoPSN enables pseudowire emulation of some properties of structure-aware time division multiplexed (TDM) networks. Particularly, CESoPSN enables the deployment of bandwidth-saving fractional point-to-point E1 or T1 applications as follows: · A pair of customer edge (CE) devices operate as though they were connected by an emulated E1 or T1
circuit, which reacts to the alarm indication signal (AIS) and remote alarm indication (RAI) states of the devices’ local attachment circuits. · The PSN carries only an NxDS0 service, where N is the number of actually used time slots in the circuit connecting the pair of CE devices, thus saving bandwidth.
RELATED DOCUMENTATION Configuring TDM CESoPSN on ACX Series Routers Overview | 51

51
Configuring CESoPSN Encapsulation on DS Interfaces Configuring CE1 Channels Down to DS Interfaces | 74
Configuring TDM CESoPSN on ACX Series Routers Overview
IN THIS SECTION Channelization up to the DS0 Level | 51 Protocol Support | 52 Packet Latency | 52 CESoPSN Encapsulation | 52 CESoPSN Options | 52 show Commands | 52 CESoPSN Pseudowires | 52
Structure-aware time division multiplexed (TDM) Circuit Emulation Service over Packet-Switched Network (CESoPSN) is a method of encapsulating TDM signals into CESoPSN packets, and in the reverse direction, decapsulating CESoPSN packets back into TDM signals. This method is also termed as Interworking Function (IWF). The following CESoPSN features are supported on Juniper Networks ACX Series Universal Metro Routers:
Channelization up to the DS0 Level
The following numbers of NxDS0 pseudowires are supported for 16 T1 and E1 built-in ports and 8 T1 and E1 built-in ports, where N represents the time slots on the T1 and E1 built-in ports. 16 T1 and E1 built-in ports support the following number of pseudowires: · Each T1 port can have up to 24 NxDS0 pseudowires, which add up to a total of up to 384 NxDS0
pseudowires. · Each E1 port can have up to 31 NxDS0 pseudowires, which add up to a total of up to 496 NxDS0
pseudowires. 8 T1 and E1 built-in ports support the following number of pseudowires: · Each T1 port can have up to 24 NxDS0 pseudowires, which add up to a total of up to 192 NxDS0
pseudowires.

52
· Each E1 port can have up to 31 NxDS0 pseudowires, which add up to a total of up to 248 NxDS0 pseudowires.
Protocol Support All protocols that support Structure-Agnostic TDM over Packet (SAToP) support CESoPSN NxDS0 interfaces.
Packet Latency The time required to create packets (from 1000 through 8000 microseconds).
CESoPSN Encapsulation The following statements are supported at the [edit interfaces interface-name] hierarchy level: · ct1-x/y/z partition partition- number timeslots timeslots interface-type ds · ds-x/y/z:n encapsulation cesopsn
CESoPSN Options The following statements are supported at the [edit interfaces interface-name cesopsn-options] hierarchy level: · excessive-packet-loss-rate (sample-period milliseconds) · idle-pattern pattern · jitter-buffer-latency milliseconds · jitter-buffer-packets packets · packetization-latency microseconds
show Commands The show interfaces interface-name extensive command is supported for t1, e1, and at interfaces.
CESoPSN Pseudowires CESoPSN pseudowires are configured on the logical interface, not on the physical interface. So the unit logical-unit-number statement must be included in the configuration at the [edit interfaces interface-name] hierarchy level. When you include the unit logical-unit-number statement, circuit cross-connect (CCC) for the logical interface is created automatically.

53
RELATED DOCUMENTATION Setting the CESoPSN Options | 55
Configuring CESoPSN on Channelized E1/T1 Circuit Emulation MIC
IN THIS SECTION Configuring T1/E1 Framing Mode at the MIC Level | 53 Configuring CT1 Interface Down to DS Channels | 54 Setting the CESoPSN Options | 55 Configuring CESoPSN on DS Interfaces | 57
To configure Circuit Emulation Service over Packet-Switched Network (CESoPSN) protocol on a 16-port Channelized E1/T1 Circuit Emulation MIC (MIC-3D- 16CHE1-T1-CE), you must configure the framing mode, configure CT1 interface down to DS channels, and configure the CESoPSN encapsulation on DS interfaces.
Configuring T1/E1 Framing Mode at the MIC Level To set the framing mode at the MIC (MIC-3D-16CHE1-T1-CE) level, for all four ports on the MIC, include the framing statement at the [edit chassis fpc slot pic slot] hierarchy level.
[edit chassis fpc slot pic slot] user@host# set framing (t1 | e1); After a MIC is brought online, interfaces are created for the MIC’s available ports on the basis of the MIC type and the framing option used. · If you include the framing t1 statement, 16 CT1 interfaces are created. · If you include the framing e1 statement, 16 CE1 interfaces are created.

54
NOTE: If you set the framing option incorrectly for the MIC type, the commit operation fails. Bit error rate test (BERT) patterns with all binary 1s (ones) received by CT1/CE1 interfaces on Circuit Emulation MICs configured for CESoPSN do not result in an alarm indication signal (AIS) defect. As a result, the CT1/CE1 interfaces remain up.
Configuring CT1 Interface Down to DS Channels To configure a channelized T1 (CT1) interface down to DS channels, include the partition statement at the [edit interfaces ct1-mpc-slot/mic-slot/port-number] hierarchy level:
NOTE: To configure a CE1 interface down to DS channels, replace ct1 with ce1 in the following procedure.
1. In configuration mode, go to the [edit interfaces ct1-mpc-slot/mic-slot /port-number] hierarchy level. [edit] user@host# edit interfaces ct1-mpc-slot /mic-slot/port-number
For example:
[edit] user@host# edit interfaces ct1-1/0/0
2. Configure the sublevel interface partition index and the time slots, and set the interface type as ds. [edit interfaces ct1-mpc-slot/mic-slot/port- number] user@host# set partition partition-number timeslots timeslots interface-type ds
For example:
[edit interfaces ct1-1/0/0] user@host# set partition 1 timeslots 1-4 interface-type ds

55
NOTE: You can assign multiple time slots on a CT1 interface. In the set command, separate the time slots by commas and do not include spaces between them. For example:
[edit interfaces ct1-1/0/0] user@host# set partition 1 timeslots 1-4,9,22-24 interface-type ds
To verify this configuration, use the show command at the [edit interfaces ct1-1/0/0] hierarchy level.
[edit interfaces ct1-1/0/0] user@host# show partition 1 timeslots 1-4 interface-type ds; An NxDS0 interface can be configured from a CT1 interface. Here N represents the number of time slots on the CT1 interface. The value of N is: · 1 through 24 when a DS0 interface is configured from a CT1 interface. · 1 through 31 when a DS0 interface is configured from a CE1 interface. After you partition the DS interface, configure CESoPSN options on it.
Setting the CESoPSN Options To configure CESoPSN options: 1. In configuration mode, go to the [edit interfaces ds-fpc-slot/pic-slot/port:channel] hierarchy level.
[edit] user@host# edit interfaces ds-fpc-slot/pic-slot/port:channel For example:
[edit] user@host# edit interfaces ds-1/0/0:1:1:1
2. Use the edit command to go to the [edit cesopsn-options] hierarchy level. [edit interfaces ds-fpc-slot/pic-slot/port:channel] user@host# edit cesopsn- options

56
3. Configure the following CESoPSN options:
NOTE: When you stitch pseudowires by using interworking (iw) interfaces, the device stitching the pseudowire cannot interpret the characteristics of the circuit because the circuits originate and terminate in other nodes. To negotiate between the stitching point and circuit endpoints, you need to configure the following options.
· excessive-packet-loss-rate–Set packet loss options. The options are sample- period and threshold.
[edit interfaces ds-fpc-slot/pic-slot/port:channel cesopsn-options] user@host# set excessive-packet-loss-rate sample-period sample-period
· idle-pattern–An 8-bit hexadecimal pattern to replace TDM data in a lost packet (from 0 through 255).
· jitter-buffer-latency–Time delay in the jitter buffer (from 1 through 1000 milliseconds). · jitter-buffer-packets–Number of packets in the jitter buffer (from 1 through 64 packets). · packetization-latency–Time required to create packets (from 1000 through 8000 microseconds). · payload-size–Payload size for virtual circuits that terminate on Layer 2 interworking (iw) logical
interfaces (from 32 through 1024 bytes).
To verify the configuration using the values shown in the examples, use the show command at the [edit interfaces ds-1/0/0:1:1:1] hierarchy level:
[edit interfaces ds-1/0/0:1:1:1] user@host# show cesopsn-options {
excessive-packet-loss-rate { sample-period 4000;
} }
SEE ALSO Setting the Encapsulation Mode | 70 Configuring the Pseudowire Interface | 73

57
Configuring CESoPSN on DS Interfaces To configure CESoPSN encapsulation on a DS interface, include the encapsulation statement at the [edit interfaces ds- mpc-slot/mic-slot/port-number:channel] hierarchy level. 1. In configuration mode, go to the [edit interfaces ds-mpc-slot/mic-slot/port-number:channel] hierarchy
level. [edit] user@host# edit interfaces ds-mpc-slot/mic-slot/ port- number:channel
For example:
[edit] user@host# edit interfaces ds-1/0/0:1
2. Configure CESoPSN as the encapsulation type. [edit interfaces ds-mpc-slot /mic-slot/port-number:partition ] user@host# set encapsulation cesopsn
For example:
[edit interfaces ds-1/0/0:1 ] user@host# set encapsulation cesopsn
3. Configure the logical interface for the DS interface. [edit interfaces ds- mpc-slot/mic-slot/port-number:partition ] uset@host# set unit interface-unit- number
For example:
[edit interfaces ds-1/0/0:1 ] user@host# set unit 0
To verify this configuration, use the show command at the [edit interfaces ds-1/0/0:1] hierarchy level.
[edit interfaces ds-1/0/0:1]

58
user@host# show encapsulation cesopsn; unit 0;
RELATED DOCUMENTATION Understanding Circuit Emulation Services and the Supported PIC Types | 2
Configuring CESoPSN on Channelized OC3/STM1 (Multi-Rate) Circuit Emulation MIC with SFP
IN THIS SECTION Configuring SONET/SDH Rate-Selectability | 58 Configuring SONET/SDH Framing Mode at the MIC Level | 59 Configuring CESoPSN Encapsulation on DS Interfaces on CT1 Channels | 60 Configuring CESoPSN Encapsulation on DS Interfaces on CE1 Channels | 64
To configure CESoPSN options on a Channelized OC3/STM1 (Multi-Rate) Circuit Emulation MIC with SFP, you must configure the speed and framing mode at MIC level and configure the encapsulation as CESoPSN on DS interfaces. Configuring SONET/SDH Rate-Selectability You can configure rate-selectability on the Channelized OC3/STM1 (Multi-Rate) MICs with SFP(MIC-3D-4COC3-1COC12-CE) by specifying the port speed. The Channelized OC3/STM1 (Multi-Rate) Circuit Emulation MIC with SFP is rate-selectable and its port speed can be specified as COC3-CSTM1 or COC12-CSTM4. To configure port speed to select a speed option of coc3-cstm1 or coc12-cstm4: 1. In configuration mode, go to the [edit chassis fpc slot pic slot port slot] hierarchy level.
[edit]

59
user@host# edit chassis fpc slot pic slot port slot For example:
[edit] user@host# edit chassis fpc 1 pic 0 port 0
2. Set the speed as coc3-cstm1 or coc12-cstm4. [edit chassis fpc slot pic slot port slot] user@host# set speed (coc3-cstm1 | coc12-cstm4)
For example:
[edit chassis fpc 1 pic 0 port 0] user@host# set speed coc3-cstm1
NOTE: When the speed is set as coc12-cstm4, instead of configuring COC3 ports down to T1 channels and CSTM1 ports down to E1 channels, you must configure COC12 ports down to T1 channels and CSTM4 channels down to E1 channels.
Configuring SONET/SDH Framing Mode at the MIC Level To set the framing mode at the MIC (MIC-3D-4COC3-1COC12-CE) level, for all four ports on the MIC, include the framing statement at the [edit chassis fpc slot pic slot] hierarchy level.
[edit chassis fpc slot pic slot] user@host# set framing (sonet | sdh) # SONET for COC3/COC12 or SDH for CSTM1/CSTM4 After a MIC is brought online, interfaces are created for the MIC’s available ports on the basis of the MIC type and the framing option used. · If you include the framing sonet statement, four COC3 interfaces are created when the speed is configured as coc3-cstm1. · If you include the framing sdh statement, four CSTM1 interfaces are created when the speed is configured as coc3-cstm1.

60
· If you include the framing sonet statement, one COC12 interface is created when the speed is configured as coc12-cstm4.
· If you include the framing sdh statement, one CSTM4 interface is created when the speed is configured as coc12-cstm4.
· If you do not specify framing at the MIC level, then the default framing is SONET for all the ports.
NOTE: If you set the framing option incorrectly for the MIC type, the commit operation fails. Bit error rate test (BERT) patterns with all binary 1s (ones) received by CT1/CE1 interfaces on Circuit Emulation MICs configured for CESoPSN do not result in an alarm indication signal (AIS) defect. As a result, the CT1/CE1 interfaces remain up.
Configuring CESoPSN Encapsulation on DS Interfaces on CT1 Channels
This topic includes the following tasks: 1. Configuring COC3 Ports Down to CT1 Channels | 60 2. Configuring CT1 Channels Down to DS Interfaces | 62 3. Configuring CESoPSN on DS Interfaces | 63 Configuring COC3 Ports Down to CT1 Channels When configuring COC3 ports down to CT1 channels, on any MIC configured for SONET framing (numbered 0 through 3), you can configure three COC1 channels (numbered 1 through 3). On each COC1 channel, you can configure a maximum of 28 CT1 channels and a minimum of 1 CT1 channel based on the time slots. When configuring COC12 ports down to CT1 channels on a MIC configured for SONET framing, you can configure 12 COC1 channels (numbered 1 through 12). On each COC1 channel, you can configure 24 CT1 channels (numbered 1 through 28). To configure COC3 channelization down to COC1 and then down to CT1 channels, include the partition statement at the [edit interfaces (coc1 | coc3 )-mpc-slot/mic-slot/port-number] hierarchy level:
NOTE: To configure COC12 ports down to CT1 channels, replace coc3 with coc12 in the following procedure.
1. In configuration mode, go to the [edit interfaces coc3-mpc-slot/mic-slot /port-number] hierarchy level.

61
[edit] user@host# edit interfaces coc3-mpc-slot/mic-slot/port-number For example:
[edit] user@host# edit interfaces coc3-1/0/0
2. Configure the sublevel interface partition index and the range of SONET/SDH slices, and set the sublevel interface type as coc1. [edit interfaces coc3-mpc-slot/mic-slot/port-number] user@host# set partition partition-number oc-slice oc-slice interface-type coc1 For example:
[edit interfaces coc3-1/0/0] user@host# set partition 1 oc-slice 1 interface- type coc1
3. Enter the up command to go to the [edit interfaces] hierarchy level. [edit interfaces coc3-mpc-slot/mic-slot/port-number] user@host# up
For example:
[edit interfaces coc3-1/0/0] user@host# up
4. Configure the channelized OC1 interface and the sublevel interface partition index, and set the interface type as ct1. [edit interfaces] user@host# set coc1-1/0/0:1 partition partition-number interface-type ct1 For example:
[edit interfaces] user@host# set coc1-1/0/0:1 partition 1 interface-type ct1

62
To verify the configuration, use the show command at the [edit interfaces] hierarchy level.
[edit interfaces] user@host# show coc3-1/0/0 {
partition 1 oc-slice 1 interface-type coc1; } coc1-1/0/0:1 {
partition 1 interface-type ct1; }
Configuring CT1 Channels Down to DS Interfaces To configure CT1 channels down to a DS interface, include the partition statement at the [edit interfaces ct1 -mpc-slot/mic-slot/port-number:channel:channel] hierarchy level: 1. In configuration mode, go to the [edit interfaces ct1-mpc-slot/mic-slot/port- number:channel:channel] hierarchy level.
[edit] user@host# edit interfaces ct1-mpc-slot/mic-slot/port- number:channel:channel
For example:
[edit] user@host# edit interfaces ct1-1/0/0:1:1
2. Configure the partition, the time slots, and the interface type.
[edit interfaces ct1-mpc-slot/mic-slot/port-number:channel:channel] user@host# set partition partition-number timeslots timeslots interface-type ds
For example:
[edit interfaces ct1-1/0/0:1:1] user@host# set partition 1 timeslots 1-4 interface-type ds

63
NOTE: You can assign multiple time slots on a CT1 interface. In the set command, separate the time slots by commas and do not include spaces between them. For example:
[edit interfaces ct1-1/0/0:1:1] user@host# set partition 1 timeslots 1-4,9,22-24 interface-type ds
To verify this configuration, use the show command at the [edit interfaces ct1-1/0/0:1:1] hierarchy level.
[edit interfaces ct1-1/0/0:1:1] user@host# show partition 1 timeslots 1-4 interface-type ds;
An NxDS0 interface can be configured from channelized T1 interface (ct1). Here N represents the time slots on the CT1 interface. The value of N is 1 through 24 when a DS0 interface is configured from a CT1 interface. After you partition the DS interface, configure the CESoPSN options on it. See “Setting the CESoPSN Options” on page 55. Configuring CESoPSN on DS Interfaces To configure CESoPSN encapsulation on a DS interface, include the encapsulation statement at the [edit interfaces ds-mpc-slot/mic-slot/port- number:channel:channel:channel] hierarchy level. 1. In configuration mode, go to the [edit interfaces
ds-mpc-slot/mic-slot/port-number:channel:channel:channel] hierarchy level.
[edit] user@host# edit interfaces ds-mpc-slot/mic-slot/ port- number:channel:channel:channel
For example:
[edit] user@host# edit interfaces ds-1/0/0:1:1:1
2. Configure CESoPSN as the encapsulation type and the logical interface for the DS interface.
[edit interfaces ds-mpc-slot/mic-slot/port-number:channel:channel:channel] user@host# set encapsulation cesopsn unit interface-unit-number

64
For example:
[edit interfaces ds-1/0/0:1:1:1 ] user@host# set encapsulation cesopsn unit 0
To verify this configuration, use the show command at the [edit interfaces ds-1/0/0:1:1:1] hierarchy level.
[edit interfaces ds-1/0/0:1:1:1] user@host# show encapsulation cesopsn; unit 0;
SEE ALSO Understanding Mobile Backhaul | 12 Configuring CESoPSN Encapsulation on DS Interfaces | 70
Configuring CESoPSN Encapsulation on DS Interfaces on CE1 Channels
IN THIS SECTION Configuring CSTM1 Ports Down to CE1 Channels | 64 Configuring CSTM4 Ports Down to CE1 Channels | 66 Configuring CE1 Channels Down to DS Interfaces | 68 Configuring CESoPSN on DS Interfaces | 69
This topic includes the following tasks: Configuring CSTM1 Ports Down to CE1 Channels On any port configured for SDH framing (numbered 0 through 3), you can configure one CAU4 channel. On each CAU4 channel, you can configure 31 CE1 channels (numbered 1 through 31). To configure CSTM1 channelization down to CAU4 and then down to CE1 channels, include the partition statement at the [edit interfaces (cau4 | cstm1)-mpc-slot/mic-slot/port-number] hierarchy level, as shown in the following example: 1. In configuration mode, go to the [edit interfaces cstm1-mpc-slot/mic-slot/port-number] hierarchy level.

65
[edit] user@host# edit interfaces cstm1-mpc-slot/mic-slot/port-number For example:
[edit] user@host# edit interfaces cstm1-1/0/1
2. On the CSTM1 interface, set the no-partition option, and then set the interface type as cau4. [edit interfaces cstm1-mpc-slot/mic-slot/port-number] user@host# set no-partition interface-type cau4
For example:
[edit interfaces cstm1-1/0/1] user@host# set no-partition interface-type cau4
3. Enter the up command to go to the [edit interfaces] hierarchy level. [edit interfaces cstm1-mpc-slot/mic-slot/port-number] user@host# up
For example:
[edit interfaces cstm1-1/0/1] user@host# up
4. Configure the MPC slot, the MIC slot, and the port for the CAU4 interface. Set the sublevel interface partition index and set the interface type as ce1. [edit interfaces] user@host# set cau4-mpc-slot/mic-slot/port-number partition partition-number interface-type ce1 For example:
[edit interfaces] user@host# set cau4-1/0/1 partition 1 interface-type ce1

66
To verify this configuration, use the show command at the [edit interfaces] hierarchy level.
[edit interfaces] user@host# show cstm1-1/0/1 {
no-partition interface-type cau4; } cau4-1/0/1 {
partition 1 interface-type ce1; }
Configuring CSTM4 Ports Down to CE1 Channels
NOTE: When the port speed is configured as coc12-cstm4 at the [edit chassis fpc slot pic slot port slot] hierarchy level, you must configure CSTM4 ports down to CE1 channels.
On a port configured for SDH framing, you can configure one CAU4 channel. On the CAU4 channel, you can configure 31 CE1 channels (numbered 1 through 31). To configure CSTM4 channelization down to CAU4 and then down to CE1 channels, include the partition statement at the [edit interfaces (cau4|cstm4)-mpc-slot /mic-slot/port-number] hierarchy level. 1. In configuration mode, go to the [edit interfaces cstm4-mpc-slot/mic-slot/port-number] hierarchy level.
[edit] user@host# edit interfaces cstm4-mpc-slot/mic-slot/port-number
For example:
[edit] user@host# edit interfaces cstm4-1/0/0
2. Configure the sublevel interface partition index and the range of SONET/SDH slices, and set the sublevel interface type as cau4.
[edit interfaces cstm4-1/0/0] user@host# set partition partition-number oc- slice oc-slice interface-type cau4
For oc-slice, select from the following ranges: 13, 46, 79, and 1012. For partition, select a value from 1 through 4.

67
For example:
[edit interfaces cstm4-1/0/0] user@host# set partition 1 oc-slice 1-3 interface-type cau4
3. Enter the up command to go to the [edit interfaces] hierarchy level.
[edit interfaces cstm4-mpc-slot/mic-slot/port-number] user@host# up
For example:
[edit interfaces cstm4-1/0/0] user@host# up
4. Configure the MPC slot, the MIC slot, and the port for the CAU4 interface. Set the sublevel interface partition index and set the interface type as ce1.
[edit interfaces] user@host# set cau4-mpc-slot/mic-slot/port-number:channel partition partition-number interface-type ce1
For example:
[edit interfaces] user@host# set cau4-1/0/0:1 partition 1 interface-type ce1
To verify this configuration, use the show command at the [edit interfaces] hierarchy level.
[edit interfaces] user@host# show cstm4-1/0/0 {
partition 1 oc-slice 1-3 interface-type cau4; } cau4-1/0/0:1 {
partition 1 interface-type ce1; }

68
Configuring CE1 Channels Down to DS Interfaces To configure CE1 channels down to a DS interface, include the partition statement at the [edit interfaces ce1 -mpc-slot/mic-slot/port:channel] hierarchy level. 1. In configuration mode, go to the [edit interfaces ce1-mpc-slot/mic-slot/port:channel] hierarchy level.
[edit] user@host# edit interfaces ce1-mpc-slot/mic-slot/port:channel
[edit] user@host# edit interfaces ce1-1/0/0:1:1
2. Configure the partition and the time slots, and set the interface type as ds. [edit interfaces ce1-1/0/0:1:1] user@host# set partition partition-number timeslots timeslots interface-type ds
For example:
[edit interfaces ce1-1/0/0:1:1] user@host# set partition 1 timeslots 1-4 interface-type ds
NOTE: You can assign multiple time slots on a CE1 interface. In the set command, separate the time slots by commas and do not include spaces between them. For example:
[edit interfaces ce1-1/0/0:1:1] user@host# set partition 1 timeslots 1-4,9,22-31 interface-type ds
To verify this configuration, use the show command at the [edit interfaces ce1-1/0/0:1:1 hierarchy level.
[edit interfaces ce1-1/0/0:1:1 ] user@host# show partition 1 timeslots 1-4 interface-type ds;
An NxDS0 interface can be configured from a channelized E1 interface (CE1). Here N represents the number of time slots on the CE1 interface. The value of N is 1 through 31 when a DS0 interface is configured from a CE1 interface.

69
After you partition the DS interface, configure the CESoPSN options.
SEE ALSO Understanding Mobile Backhaul | 12 Configuring CESoPSN Encapsulation on DS Interfaces | 70
Configuring CESoPSN on DS Interfaces To configure CESoPSN encapsulation on a DS interface, include the encapsulation statement at the [edit interfaces ds- mpc-slot/mic-slot/port-number:channel:channel:channel] hierarchy level. 1. In configuration mode, go to the [edit interfaces
ds-mpc-slot/mic-slot/port-number:channel:channel:channel] hierarchy level.
[edit] user@host# edit interfaces ds-mpc-slot/mic-slot/port- number:channel:channel:channel
For example:
[edit] user@host# edit interfaces ds-1/0/0:1:1:1
2. Configure CESoPSN as the encapsulation type and then set the logical interface for the ds interface.
[edit interfaces ds-1/0/0:1:1:1 ] user@host# set encapsulation cesopsn unit interface-unit-number
For example:
[edit interfaces ds-1/0/0:1:1:1 ] user@host# set encapsulation cesopsn unit 0
To verify this configuration, use the show command at the [edit interfaces ds-1/0/0:1:1:1] hierarchy level.
[edit interfaces ds-1/0/0:1:1:1] user@host# show encapsulation cesopsn; unit 0;

70
RELATED DOCUMENTATION Understanding Mobile Backhaul | 12 Configuring CESoPSN Encapsulation on DS Interfaces | 70
RELATED DOCUMENTATION Understanding Mobile Backhaul | 12 Configuring CESoPSN Encapsulation on DS Interfaces | 70
Configuring CESoPSN Encapsulation on DS Interfaces
This configuration applies to the mobile backhaul application shown in Figure 3 on page 13. 1. Setting the Encapsulation Mode | 70 2. Setting the CESoPSN Options | 71 3. Configuring the Pseudowire Interface | 73
Setting the Encapsulation Mode To configure a DS interface on Circuit Emulation MICs with CESoPSN encapsulation at the provider edge (PE) router: 1. In configuration mode, go to the [edit interfaces ds-mpc-slot/mic- slot/port<:channel>] hierarchy level.
[edit] user@host# edit interfaces ds-mpc-slot/mic-slot/port<:channel> For example:
[edit] user@host# edit interfaces ds-1/0/0:1:1:1
2. Configure CESoPSN as the encapsulation type and set the logical interface for the DS interface. [edit interfaces ds-mpc-slot/mic-slot/port<:channel>] user@host# set encapsulation cesopsn unit logical-unit-number

71
For example:
[edit interfaces ds-1/0/0:1:1:1] user@host# set encapsulation cesopsn unit 0
To verify this configuration, use the show command at the [edit interfaces ds-1/0/0:1:1:1] hierarchy level:
[edit interfaces ds-1/0/0:1:1:1] user@host# show encapsulation cesopsn; unit 0; You do not need to configure any circuit cross-connect family because it is automatically created for the CESoPSN encapsulation.
SEE ALSO Setting the CESoPSN Options | 55 Configuring the Pseudowire Interface | 73
Setting the CESoPSN Options To configure CESoPSN options: 1. In configuration mode, go to the [edit interfaces ds-fpc-slot/pic-slot/port:channel] hierarchy level.
[edit] user@host# edit interfaces ds-fpc-slot/pic-slot/port:channel For example:
[edit] user@host# edit interfaces ds-1/0/0:1:1:1
2. Use the edit command to go to the [edit cesopsn-options] hierarchy level. [edit] user@host# edit cesopsn-options

72
3. At this hierarchy level, using the set command you can configure the following CESoPSN options:
NOTE: When you stitch pseudowires by using interworking (iw) interfaces, the device stitching the pseudowire cannot interpret the characteristics of the circuit because the circuits originate and terminate in other nodes. To negotiate between the stitching point and circuit endpoints, you need to configure the following options.
· excessive-packet-loss-rate–Set packet loss options. The options are sample- period and threshold. · sample-period–Time required to calculate excessive packet loss rate (from 1000 through 65,535 milliseconds). · threshold–Percentile designating the threshold of excessive packet loss rate (1100 percent).
· idle-pattern–An 8-bit hexadecimal pattern to replace TDM data in a lost packet (from 0 through 255).
· jitter-buffer-latency–Time delay in the jitter buffer (from 1 through 1000 milliseconds). · jitter-buffer-packets–Number of packets in the jitter buffer (from 1 through 64 packets). · packetization-latency–Time required to create packets (from 1000 through 8000 microseconds). · payload-size–Payload size for virtual circuits that terminate on Layer 2 interworking (iw) logical
interfaces (from 32 through 1024 bytes).
NOTE: This topic shows the configuration of only one CESoPSN option. You can follow the same method to configure all the other CESoPSN options.
[edit interfaces ds-fpc-slot/pic-slot/port:channel cesopsn-options] user@host# set excessive-packet-loss-rate sample-period sample-period
For example:
[edit interfaces ds-1/0/0:1:1:1 cesopsn-options] user@host# set excessive- packet-loss-rate sample-period 4000
To verify the configuration using the values shown in the examples, use the show command at the [edit interfaces ds-1/0/0:1:1:1] hierarchy level:
[edit interfaces ds-1/0/0:1:1:1]

73
user@host# show cesopsn-options {
excessive-packet-loss-rate { sample-period 4000;
} }
SEE ALSO Setting the Encapsulation Mode | 70 Configuring the Pseudowire Interface | 73
Configuring the Pseudowire Interface To configure the TDM pseudowire at the provider edge (PE) router, use the existing Layer 2 circuit infrastructure, as shown in the following procedure: 1. In configuration mode, go to the [edit protocols l2circuit] hierarchy level.
[edit] user@host# edit protocol l2circuit
2. Configure the IP address of the neighboring router or switch, the interface forming the Layer 2 circuit, and the identifier for the Layer 2 circuit.
[edit protocol l2circuit] user@host# set neighbor ip-address interface interface-name-fpc-slot/pic-slot/port.interface-unit-number
virtual-circuit-id virtual-circuit-id
For example:
[edit protocol l2circuit] user@host# set neighbor 10.255.0.6 interface ds-1/0/0:1:1:1 virtual-circuit-id 1
To verify this configuration, use the show command at the [edit protocols l2circuit] hierarchy level.
[edit protocols l2circuit] user@host# show

74
neighbor 10.255.0.6 { interface ds-1/0/0:1:1:1 { virtual-circuit-id 1; }
}
After the customer edge (CE)-bound interfaces (for both PE routers) are configured with proper encapsulation, packetization latency, and other parameters, the two PE routers try to establish a pseudowire with Pseudowire Emulation Edge-to-Edge (PWE3) signaling extensions. The following pseudowire interface configurations are disabled or ignored for TDM pseudowires: · ignore-encapsulation · mtu The supported pseudowire type is 0x0015 CESoPSN basic mode. When the local interface parameters match the received parameters, and the pseudowire type and control word bit are equal, the pseudowire is established. For detailed information about configuring TDM pseudowire, see the Junos OS VPNs Library for Routing Devices. For detailed information about PICs, see the PIC Guide for your router.
SEE ALSO Setting the Encapsulation Mode | 70 Setting the CESoPSN Options | 55
RELATED DOCUMENTATION Configuring CESoPSN on Channelized OC3/STM1 (Multi-Rate) Circuit Emulation MIC with SFP | 58 Understanding Mobile Backhaul | 12
Configuring CE1 Channels Down to DS Interfaces
You can configure a DS interface on a channelized E1 interface (CE1) and then apply CESoPSN encapsulation for the pseudowire to function. An NxDS0 interface can be configured from a channelized CE1 interface,

75
where N represents the time slots on the CE1 interface. The value of N is 1 through 31 when a DS0 interface is configured from a CE1 interface. To configure CE1 channels down to a DS interface, include the partition statement at the [edit interfaces ce1-fpc/pic/port] hierarchy level, as shown in the following example:
[edit interfaces] user@host# show ce1-0/0/1 {
partition 1 timeslots 1-4 interface-type ds; }
After you partition the DS interface, configure the CESoPSN options on it. See “Setting the CESoPSN Options” on page 55. To configure CE1 channels down to a DS interface: 1. Create the CE1 interface.
[edit interfaces] user@host# edit interfaces ce1-fpc/pic/port
For example:
[edit interfaces] user@host# edit interface ce1-0/0/1
2. Configure the partition, the time slot, and the interface type.
[edit interfaces ce1-fpc/pic/port] user@host# set partition partition-number timeslots timeslots interface-type ds;
For example:
[edit interfaces ce1-0/0/1] user@host# set partition 1 timeslots 1-4 interface-type ds;

76
NOTE: You can assign multiple time slots on a CE1 interface; in the configuration, separate the time slots by comma without spaces. For example:
[edit interfaces ce1-0/0/1] user@host# set partition 1 timeslots 1-4,9,2231 interface-type ds;
3. Configure the CESoPSN encapsulation for the DS interface.
[edit interfaces ds-fpc/pic/port:partition] user@host# set encapsulation encapsulation-type
For example:
[edit interfaces ds-0/0/1:1] user@host# set encapsulation cesopsn
4. Configure the logical interface for the DS interface.
[edit interfaces ds-fpc/pic/port:partition] user@host# set unit logical-unit- number;
For example:
[edit interfaces ds-0/0/1:1] user@host# set unit 0
When you are finished configuring CE1 channels down to a DS interface, enter the commit command from configuration mode. From configuration mode, confirm your configuration by entering the show command. For example:
[edit interfaces] user@host# show ce1-0/0/1 {
partition 1 timeslots 1-4 interface-type ds; } ds-0/0/1:1 {
encapsulation cesopsn;

77
unit 0; }
RELATED DOCUMENTATION Understanding Mobile Backhaul | 12 Configuring CESoPSN Encapsulation on DS Interfaces | 70
Configuring CESoPSN on Channelized E1/T1 Circuit Emulation MIC on ACX Series
IN THIS SECTION Configuring T1/E1 Framing Mode at the MIC Level | 77 Configuring CT1 Interface Down to DS channels | 78 Configuring CESoPSN on DS Interfaces | 79
This configuration applies to the mobile backhaul application shown in Figure 3 on page 13. Configuring T1/E1 Framing Mode at the MIC Level To set the framing mode at the MIC (ACX-MIC-16CHE1-T1-CE) level, for all four ports on the MIC, include the framing statement at the [edit chassis fpc slot pic slot] hierarchy level.
[edit chassis fpc slot pic slot] user@host# set framing (t1 | e1); After a MIC is brought online, interfaces are created for the MIC’s available ports on the basis of the MIC type and the framing option used. · If you include the framing t1 statement, 16 CT1 interfaces are created. · If you include the framing e1 statement, 16 CE1 interfaces are created.

78
NOTE: If you set the framing option incorrectly for the MIC type, the commit operation fails. Bit error rate test (BERT) patterns with all binary 1s (ones) received by CT1/CE1 interfaces on Circuit Emulation MICs configured for CESoPSN do not result in an alarm indication signal (AIS) defect. As a result, the CT1/CE1 interfaces remain up.
Configuring CT1 Interface Down to DS channels To configure a channelized T1 (CT1) interface down to DS channels, include the partition statement at the [edit interfaces ct1-mpc-slot/mic-slot/port-number] hierarchy level:
NOTE: To configure a CE1 interface down to DS channels, replace ct1 with ce1 in the following procedure.
1. In configuration mode, go to the [edit interfaces ct1-mpc-slot/mic-slot /port-number] hierarchy level. [edit] user@host# edit interfaces ct1-mpc-slot /mic-slot/port-number
For example:
[edit] user@host# edit interfaces ct1-1/0/0
2. Configure the sublevel interface partition index and the time slots, and set the interface type as ds. [edit interfaces ct1-mpc-slot/mic-slot/port- number] user@host# set partition partition-number timeslots timeslots interface-type ds
For example:
[edit interfaces ct1-1/0/0] user@host# set partition 1 timeslots 1-4 interface-type ds

79
NOTE: You can assign multiple time slots on a CT1 interface. In the set command, separate the time slots by commas and do not include spaces between them. For example:
[edit interfaces ct1-1/0/0] user@host# set partition 1 timeslots 1-4,9,22-24 interface-type ds
To verify this configuration, use the show command at the [edit interfaces ct1-1/0/0] hierarchy level.
[edit interfaces ct1-1/0/0] user@host# show partition 1 timeslots 1-4 interface-type ds;
An NxDS0 interface can be configured from a CT1 interface. Here N represents the number of time slots on the CT1 interface. The value of N is: · 1 through 24 when a DS0 interface is configured from a CT1 interface. · 1 through 31 when a DS0 interface is configured from a CE1 interface. After you partition the DS interface, configure CESoPSN options on it. See “Setting the CESoPSN Options” on page 55.
Configuring CESoPSN on DS Interfaces To configure CESoPSN encapsulation on a DS interface, include the encapsulation statement at the [edit interfaces ds- mpc-slot/mic-slot/port-number:channel] hierarchy level. 1. In configuration mode, go to the [edit interfaces ds-mpc-slot/mic-slot/port-number:channel] hierarchy
level.
[edit] user@host# edit interfaces ds-mpc-slot/mic-slot/ port-number:channel
For example:
[edit] user@host# edit interfaces ds-1/0/0:1
2. Configure CESoPSN as the encapsulation type.

80
[edit interfaces ds-mpc-slot/mic-slot/port-number:partition ] user@host# set encapsulation cesopsn For example:
[edit interfaces ds-1/0/0:1 ] user@host# set encapsulation cesopsn
3. Configure the logical interface for the DS interface. [edit interfaces ds- mpc-slot/mic-slot/port-number:partition ] uset@host# set unit interface-unit- number
For example:
[edit interfaces ds-1/0/0:1 ] user@host# set unit 0
To verify this configuration, use the show command at the [edit interfaces ds-1/0/0:1] hierarchy level.
[edit interfaces ds-1/0/0:1] user@host# show encapsulation cesopsn; unit 0;
RELATED DOCUMENTATION 16-Port Channelized E1/T1 Circuit Emulation MIC Overview

81
CHAPTER 6
Configuring ATM Support on Circuit Emulation PICs
IN THIS CHAPTER ATM Support on Circuit Emulation PICs Overview | 81 Configuring the 4-Port Channelized COC3/STM1 Circuit Emulation PIC | 85 Configuring the 12-Port Channelized T1/E1 Circuit Emulation PIC | 87 Understanding Inverse Multiplexing for ATM | 93 ATM IMA Configuration Overview | 96 Configuring ATM IMA | 105 Configuring ATM Pseudowires | 109 Configuring ATM Cell-Relay Pseudowire | 112 ATM Cell Relay Pseudowire VPI/VCI Swapping Overview | 117 Configuring ATM Cell-Relay Pseudowire VPI/VCI Swapping | 118 Configuring Layer 2 Circuit and Layer 2 VPN Pseudowires | 126 Configuring EPD Threshold | 127 Configuring ATM QoS or Shaping | 128
ATM Support on Circuit Emulation PICs Overview
IN THIS SECTION ATM OAM Support | 82 Protocol and Encapsulation Support | 83 Scaling Support | 83 Limitations to ATM Support on Circuit Emulation PICs | 84

82
The following components support ATM over MPLS (RFC 4717) and packet encapsulations (RFC 2684): · 4-port COC3/CSTM1 Circuit Emulation PIC on M7i and M10i routers. · 12-port T1/E1 Circuit Emulation PIC on M7i and M10i routers. · Channelized OC3/STM1 (Multi-Rate) Circuit Emulation MIC with SFP (MIC-3D-4COC3-1COC12-CE)
on MX Series routers. · 16-Port Channelized E1/T1 Circuit Emulation MIC (MIC- 3D-16CHE1-T1-CE) on MX Series routers. Circuit Emulation PIC ATM configuration and behavior is consistent with existing ATM2 PICs.
NOTE: Circuit Emulation PICs require firmware version rom-ce-9.3.pbin or rom- ce-10.0.pbin for ATM IMA functionality on M7i, M10i, M40e, M120, and M320 routers running JUNOS OS Release 10.0R1 or later.
ATM OAM Support
ATM OAM supports: · Generation and monitoring of F4 and F5 OAM cells types:
· F4 AIS (end-to-end) · F4 RDI (end-to-end) · F4 loopback (end-to-end) · F5 loopback · F5 AIS · F5 RDI · Generation and monitoring of end-to-end cells of type AIS and RDI · Monitor and terminate loopback cells · OAM on each VP and VC simultaneously VP Pseudowires (CCC Encapsulation)–In the case of ATM virtual path (VP) pseudowires–all virtual circuits (VCs) in a VP are transported over a single N-to-one mode pseudowire–all F4 and F5 OAM cells are forwarded through the pseudowire. Port Pseudowires (CCC Encapsulation)–Like VP pseudowires, with port pseudowires, all F4 and F5 OAM cells are forwarded through the pseudowire. VC Pseudowires (CCC Encapsulation)–In the case of VC pseudowires, F5 OAM cells are forwarded through the pseudowire, while F4 OAM cells are terminated at the Routing Engine.

83
Protocol and Encapsulation Support The following protocols are supported: · QoS or CoS queues. All virtual circuit (VCs) are unspecified bit rate (UBR).
NOTE: This protocol is not supported on M7i and M10i routers.

· ATM over MPLS (RFC 4717) · ATM via dynamic labels (LDP, RSVP-TE) NxDS0 grooming is not supported
The following ATM2 encapsulations are not supported:
· atm-cisco-nlpid–Cisco-compatible ATM NLPID encapsulation · atm-mlppp-llc–ATM MLPPP over AAL5/LLC · atm-nlpid–ATM NLPID encapsulation · atm-ppp-llc–ATM PPP over AAL5/LLC · atm-ppp-vc-mux–ATM PPP over raw AAL5 · atm-snap–ATM LLC/SNAP encapsulation · atm-tcc-snap–ATM LLC/SNAP for translational cross-connect · atm-tcc-vc-mux–ATM VC for translational cross-connect · vlan-vci-ccc–CCC for VLAN Q-in-Q and ATM VPI/VCI interworking · atm-vc-mux–ATM VC multiplexing · ether-over-atm-llc–Ethernet over ATM (LLC/SNAP) encapsulation · ether-vpls- over-atm-llc–Ethernet VPLS over ATM (bridging) encapsulation

Scaling Support

Table 4 on page 83 lists the maximum number of virtual circuits (VCs) that are supported on various components on the M10i router, on the M7i router, and on MX Series routers.

Table 4: Maximum Number of VCs

Component

Maximum Number of VCs

12-port Channelized T1/E1 Circuit Emulation PIC

1000 VCs

Table 4: Maximum Number of VCs (continued) Component 4-port Channelized COC3/STM1 Circuit Emulation PIC Channelized OC3/STM1 (Multi-Rate) Circuit Emulation MIC with SFP 16-Port Channelized E1/T1 Circuit Emulation MIC

Maximum Number of VCs 2000 VCs 2000 VCs 1000 VCs

Limitations to ATM Support on Circuit Emulation PICs
The following limitations apply to ATM support on Circuit Emulation PICs: · Packet MTU–Packet MTU is limited to 2048 bytes. · Trunk mode ATM pseudowires–Circuit Emulation PICs do not support trunk mode ATM pseudowires. · OAM-FM segment–Segment F4 flows are not supported. Only end-to-end F4 flows are supported. · IP and Ethernet encapsulations–IP and Ethernet encapsulations are not supported. · F5 OAM–OAM termination is not supported.

RELATED DOCUMENTATION
Configuring the 12-Port Channelized T1/E1 Circuit Emulation PIC | 87 Configuring the 4-Port Channelized COC3/STM1 Circuit Emulation PIC | 85 ATM IMA Configuration Overview | 96 Configuring ATM IMA | 105 Configuring ATM Pseudowires | 109 Configuring EPD Threshold | 127 Configuring Layer 2 Circuit and Layer 2 VPN Pseudowires | 126

85
Configuring the 4-Port Channelized COC3/STM1 Circuit Emulation PIC
IN THIS SECTION T1/E1 Mode Selection | 85 Configuring a Port for SONET or SDH Mode on a 4-Port Channelized COC3/STM1 Circuit Emulation PIC | 86 Configuring an ATM Interface on a Channelized OC1 interface | 87

T1/E1 Mode Selection
All ATM interfaces are either T1 or E1 channels within the COC3/CSTM1 hierarchy. Each COC3 interface can be partitioned as 3 COC1 slices, each of which in turn can be partitioned further into 28 ATM interfaces and the size of each interface created is that of a T1. Each CS1 can be portioned as 1 CAU4, which can be further partitioned as E1 sized ATM interfaces.
To configure the T1/E1 mode selection, note the following:
1. To create coc3-fpc/pic/port or cstm1-fpc/pic/port interfaces, chassisd will look for configuration at the [edit chassis fpc fpc-slot pic pic-slot port port framing (sonet | sdh)] hierarchy level. If the sdh option is specified, chassisd will create a cstm1-fpc/pic/port interface. Otherwise, chassisd will create coc3-fpc/pic/port interfaces.
2. Only interface coc1 can be created from coc3, and t1 can be created from coc1. 3. Only interface cau4 can be created from cstm1, and e1 can be created from cau4.
Figure 7 on page 85 and Figure 8 on page 86 illustrate the possible interfaces that can be created on the 4-port Channelized COC3/STM1 Circuit Emulation PIC.

Figure 7: 4-Port Channelized COC3/STM1 Circuit Emulation PIC Possible Interfaces (T1 Size)
coc3-x/y/z coc1-x/y/z:n

t1-x/y/z:n:m

at-x/y/z:n:m (T1 size)

g017388

Figure 8: 4-Port Channelized COC3/STM1 Circuit Emulation PIC Possible Interfaces (E1 Size)
cstm1-x/y/z cau4-x/y/z

g017389

e1-x/y/z:n

at-x/y/z:n (E1 size)

Subrate T1 is not supported.

ATM NxDS0 grooming is not supported.

External and internal loopback of T1/E1 (on ct1/ce1 physical interfaces) can be configured using the sonet-options statement. By default, no loopback is configured.

Configuring a Port for SONET or SDH Mode on a 4-Port Channelized COC3/STM1 Circuit Emulation PIC
Each port of the 4-port Channelized COC3/STM1 Circuit Emulation PIC can be independently configured for either SONET or SDH mode. To configure a port for either SONET or SDH mode, enter the framing (sonet | sdh) statement at the [chassis fpc number pic number port number] hierarchy level.
The following example shows how to configure FPC 1, PIC 1, and port 0 for SONET mode and port 1 for SDH mode:

set chassis fpc 1 pic 1 port 0 framing sonet set chassis fpc 1 pic 1 port 1 framing sdh
Or specify the following:

[edit] fpc 1 {
pic 1 { port 0 { framing sonet; } port 1 { framing sdh; }
} }

87
Configuring an ATM Interface on a Channelized OC1 interface To create an ATM interface on a channelized OC1 interface (COC1), enter the following command:
To create an ATM interface on CAU4, enter the following command: set interfaces cau4-fpc/pic/port partition interface-type at
Or specify the following: interfaces { cau4-fpc/pic/port { } }
You can use the show chassis hardware command to display a list of the installed PICs.
RELATED DOCUMENTATION ATM Support on Circuit Emulation PICs Overview | 81
Configuring the 12-Port Channelized T1/E1 Circuit Emulation PIC
IN THIS SECTION Configuring CT1/CE1 Interfaces | 88 Configuring Interface- Specific Options | 90
When the 12-port Channelized T1/E1 Circuit Emulation PIC is brought online, 12 channelized T1 (ct1) interfaces or 12 channelized E1 (ce1) interfaces are created, depending on the T1 or E1 mode selection of the PIC. Figure 9 on page 88 and Figure 10 on page 88 illustrate the possible interfaces that can be created on the 12-port T1/E1 Circuit Emulation PIC.

g017467

g017468

88
Figure 9: 12-Port T1/E1 Circuit Emulation PIC Possible Interfaces (T1 Size)
ct1-x/y/z
t1-x/y/z at-x/y/z (T1 size) ds-x/y/z:n at-x/y/z:n (NxDS0 size) t1-x/y/z (ima link) (M links) at-x/y/g (MxT1 size)
Figure 10: 12-Port T1/E1 Circuit Emulation PIC Possible Interfaces (E1 Size)
ce1-x/y/z
e1-x/y/z at-x/y/z (E1 size) ds-x/y/z:n at-x/y/z:n (NxDS0 size) e1-x/y/z (ima link) (M links) at-x/y/g (MxE1 size)
The following sections explain: Configuring CT1/CE1 Interfaces
IN THIS SECTION Configuring T1/E1 Mode at the PIC level | 88 Creating an ATM Interface on a CT1 or

JUNIPER NETWORKS Circuit Emulation Interfaces Routing Devices User Guide

Circuit Emulation Interfaces Routing Devices

Product Information

Specifications

Product Usage Instructions

1. Overview

1.1 Understanding Circuit Emulation Interfaces

1.2 Understanding Circuit Emulation Services and the Supported

1.3 Understanding Circuit Emulation PIC Clocking Features

1.4 Understanding ATM QoS or Shaping

1.5 Understanding How Circuit Emulation Interfaces Support

2. Configuring Circuit Emulation Interfaces

2.1 Configuring SAToP Support on Circuit Emulation PICs

2.2 Configuring SAToP Emulation on T1/E1 Interfaces on 12-Port

2.3 Configuring SAToP Support on Circuit Emulation MICs

FAQ

Q: Are Juniper Networks hardware and software products Year

Q: Where can I find the End User License Agreement (EULA) for

(pound sign)

References

Read User Manual Online (PDF format)

Download This Manual (PDF format)

JUNIPER NETWORKS User Manuals

Related Manuals