323-1851-102.7 (6500 R12.6 Data Layer2 CPS) Issue1

6500 Packet-Optical Platform
Data and Layer 2 Circuit Packs

Release 12.6
What’s inside...
New in this release and documentation roadmap
Data circuit packs (Ethernet Private Line and FLEX MOTR)
Layer 2 circuit packs
323-1851-102.7 - Standard Issue 1

September 2019
Copyright© 2010-2019 Ciena® Corporation. All rights reserved.
LEGAL NOTICES
THIS DOCUMENT CONTAINS CONFIDENTIAL AND TRADE SECRET INFORMATION OF CIENA
CORPORATION AND ITS RECEIPT OR POSSESSION DOES NOT CONVEY ANY RIGHTS TO REPRODUCE
OR DISCLOSE ITS CONTENTS, OR TO MANUFACTURE, USE, OR SELL ANYTHING THAT IT MAY DESCRIBE.
REPRODUCTION, DISCLOSURE, OR USE IN WHOLE OR IN PART WITHOUT THE SPECIFIC WRITTEN
AUTHORIZATION OF CIENA CORPORATION IS STRICTLY FORBIDDEN.
EVERY EFFORT HAS BEEN MADE TO ENSURE THAT THE INFORMATION IN THIS DOCUMENT IS
COMPLETE AND ACCURATE AT THE TIME OF PUBLISHING; HOWEVER, THE INFORMATION CONTAINED IN
THIS DOCUMENT IS SUBJECT TO CHANGE.
While the information in this document is believed to be accurate and reliable, except as otherwise expressly agreed
to in writing CIENA PROVIDES THIS DOCUMENT “AS IS” WITHOUT WARRANTY OR CONDITION OF ANY
KIND, EITHER EXPRESS OR IMPLIED. The information and/or products described in this document are subject to
change without notice. For the most up-to-date technical publications, visit www.ciena.com.
Copyright© 2010-2019 Ciena® Corporation. All Rights Reserved
Use or disclosure of data contained in this document is subject to the Legal Notices and restrictions in this section
and, unless governed by a valid license agreement signed between you and Ciena, the Licensing Agreement that
follows.
The material contained in this document is also protected by copyright laws of the United States of America and
other countries. It may not be reproduced or distributed in any form by any means, altered in any fashion, or stored
in a data base or retrieval system, without express written permission of the Ciena Corporation.
Security
Ciena® cannot be responsible for unauthorized use of equipment and will not make allowance or credit for
unauthorized use or access.
Contacting Ciena
Corporate Headquarters 410-694-5700 or 800-921-1144 www.ciena.com
Customer Technical Support/Warranty
In North America 1-800-CIENA-24 (243-6224)
410-865-4961
In Europe, Middle East, 800-CIENA-24-7 (800-2436-2247)
and Africa +44-207-012-5508
00 0800 77 454 (Slovenia)
In Asia-Pacific 800-CIENA-24-7 (800-2436-2247)
+81-3-6367-3989
+91-124-4340-600
120 11104 (Vietnam)
000 8004401369 (India)
In Caribbean and Latin 800-CIENA-24-7 (800-2436-2247)
America 1230-020-0845 (Chile)
009 800-2436-2247 (Colombia)
0800-77-454 (Mexico and Peru)
00 008000442510 (Panama)
Sales and General Information North America: 1-800-207-3714 E-mail: [email protected]
International: +44 20 7012 5555
In North America 410-694-5700 or 800-207-3714 E-mail: [email protected]
In Europe +44-207-012-5500 (UK) E-mail: [email protected]
In Asia +81-3-3248-4680 (Japan) E-mail: [email protected]
In India +91-22-42419600 E-mail: [email protected]
In Latin America 011-5255-1719-0220 (Mexico City) E-mail: [email protected]
Training E-mail: [email protected]
6500 Packet-Optical Platform Data and Layer 2 Circuit Packs

Release 12.6 323-1851-102.7 Standard Issue 1
Copyright© 2010-2019 Ciena® Corporation September 2019
For additional office locations and phone numbers, please visit the Ciena web site at www.ciena.com.
READ THIS LICENSE AGREEMENT (“LICENSE”) CAREFULLY BEFORE INSTALLING OR USING CIENA
SOFTWARE OR DOCUMENTATION. THIS LICENSE IS AN AGREEMENT BETWEEN YOU AND CIENA
COMMUNICATIONS, INC. (OR, AS APPLICABLE, SUCH OTHER CIENA CORPORATION AFFILIATE
LICENSOR) (“CIENA”) GOVERNING YOUR RIGHTS TO USE THE SOFTWARE. BY INSTALLING OR USING
THE SOFTWARE, YOU ACKNOWLEDGE THAT YOU HAVE READ THIS LICENSE AND AGREE TO BE BOUND
BY IT.
1. License Grant. Ciena may provide “Software” to you either (1) embedded within or running on a hardware
product or (2) as a standalone application, and Software includes upgrades acquired by you from Ciena or a Ciena
authorized reseller. Subject to these terms, and payment of all applicable License fees including any usage-based
fees, Ciena grants you, as end user, a non-exclusive, non-transferable, personal License to use the Software only in
object code form and only for its intended use as evidenced by the applicable product documentation. Unless the
context does not permit, Software also includes associated documentation.
2. Open Source and Third Party Licenses. Software excludes any open source or third-party programs supplied
by Ciena under a separate license, and you agree to be bound by the terms of any such license. If a separate
license is not provided, any open source and third party programs are considered “Software” and their use
governed by the terms of this License.
3. Title. You are granted no title or ownership rights in or to the Software. Unless specifically authorized by Ciena in
writing, you are not authorized to create any derivative works based upon the Software. Title to the Software,
including any copies or derivative works based thereon, and to all copyrights, patents, trade secrets and other
intellectual property rights in or to the Software, are and shall remain the property of Ciena and/or its licensors.
Ciena's licensors are third party beneficiaries of this License. Ciena reserves to itself and its licensors all rights in
the Software not expressly granted to you.
4. Confidentiality. The Software contains trade secrets of Ciena. Such trade secrets include, without limitation, the
design, structure and logic of individual Software programs, their interactions with other portions of the Software,
internal and external interfaces, and the programming techniques employed. The Software and related technical
and commercial information, and other information received in connection with the purchase and use of the
Software that a reasonable person would recognize as being confidential, are all confidential information of Ciena
(“Confidential Information”).
5. Obligations. You shall:
i) Hold the Software and Confidential Information in strict confidence for the benefit of Ciena using your best efforts
to protect the Software and Confidential Information from unauthorized disclosure or use, and treat the Software
and Confidential Information with the same degree of care as you do your own similar information, but no less than
reasonable care;
ii) Keep a current record of the location of each copy of the Software you make;
iii) Use the Software only in accordance with the authorized usage level;
iv) Preserve intact any copyright, trademark, logo, legend or other notice of ownership on any original or copies of
the Software, and affix to each copy of the Software you make, in the same form and location, a reproduction of the
copyright notices, trademarks, and all other proprietary legends and/or logos appearing on the original copy of the
Software delivered to you; and
v) Issue instructions to your authorized personnel to whom Software is disclosed, advising them of the confidential
nature of the Software and provide them with a summary of the requirements of this License.
6. Restrictions. You shall not:
i) Use the Software or Confidential Information a) for any purpose other than your own internal business purposes;
and b) other than as expressly permitted by this License;
ii) Allow anyone other than your authorized personnel who need to use the Software in connection with your rights
or obligations under this License to have access to the Software;
iii) Make any copies of the Software except such limited number of copies, in machine readable form only, as may
be reasonably necessary for execution in accordance with the authorized usage level or for archival purposes only;
iv) Make any modifications, enhancements, adaptations, derivative works, or translations to or of the Software;
v) Reverse engineer, disassemble, reverse translate, decompile, or in any other manner decode the Software;
vi) Make full or partial copies of the associated documentation or other printed or machine-readable matter provided
with the Software unless it was supplied by Ciena in a form intended for reproduction;

vii) Export or re-export the Software from the country in which it was received from Ciena or its authorized reseller
unless authorized by Ciena in writing; or
viii) Publish the results of any benchmark tests run on the Software.
7. Audit: Upon Ciena's reasonable request you shall permit Ciena to audit the use of the Software to ensure
compliance with this License.
8. U.S. Government Use. The Software is provided to the Government only with restricted rights and limited rights.
Use, duplication, or disclosure by the Government is subject to restrictions set forth in FAR Sections 52-227-14 and
52-227-19 or DFARS Section 52.227-7013(C)(1)(ii), as applicable. The Software and any accompanying technical
data (collectively “Materials”) are commercial within the meaning of applicable Federal acquisition regulations. The
Materials were developed fully at private expense. U.S. Government use of the Materials is restricted by this
License, and all other U.S. Government use is prohibited. In accordance with FAR 12.212 and DFAR Supplement
227.7202, the Software is commercial computer software and the use of the Software is further restricted by this
License.
9. Term of License. This License is effective until the applicable subscription period expires or the License is
terminated. You may terminate this License by giving written notice to Ciena. This License will terminate
immediately if (i) you breach any term or condition of this License or (ii) you become insolvent, cease to carry on
business in the ordinary course, have a receiver appointed, enter into liquidation or bankruptcy, or any analogous
process in your home country. Termination shall be without prejudice to any other rights or remedies Ciena may
have. Upon any termination of this License you shall destroy and erase all copies of the Software in your
possession or control, and forward written certification to Ciena that all such copies of Software have been
destroyed or erased. Your obligations to hold the Confidential Information in confidence, as provided in this License,
shall survive the termination of this License.
10. Compliance with laws. You agree to comply with all laws related to your installation and use of the Software.
Software is subject to U.S. export control laws, and may be subject to export or import regulations in other
countries. If Ciena authorizes you to import or export the Software in writing, you shall obtain all necessary licenses
or permits and comply with all applicable laws.
11. Limitation of Liability. ANY LIABILITY OF CIENA SHALL BE LIMITED IN THE AGGREGATE TO THE
AMOUNTS PAID BY YOU TO CIENA OR ITS AUTHORIZED RESELLER FOR THE SOFTWARE. THIS
LIMITATION APPLIES TO ALL CAUSES OF ACTION, INCLUDING WITHOUT LIMITATION BREACH OF
CONTRACT, BREACH OF WARRANTY, NEGLIGENCE, STRICT LIABILITY, MISREPRESENTATION AND OTHER
TORTS. THE LIMITATIONS OF LIABILITY DESCRIBED IN THIS SECTION ALSO APPLY TO ANY LICENSOR OF
CIENA. NEITHER CIENA NOR ANY OF ITS LICENSORS SHALL BE LIABLE FOR ANY INJURY, LOSS OR
DAMAGE, WHETHER INDIRECT, SPECIAL, INCIDENTAL OR CONSEQUENTIAL INCLUDING WITHOUT
LIMITATION ANY LOST PROFITS, CONTRACTS, DATA OR PROGRAMS, AND THE COST OF RECOVERING
SUCH DATA OR PROGRAMS, EVEN IF INFORMED OF THE POSSIBILITY OF SUCH DAMAGES IN ADVANCE.
12. General. Ciena may assign this License to an affiliate or to a purchaser of the intellectual property rights in the
Software. You shall not assign or transfer this License or any rights hereunder, and any attempt to do so will be void.
This License shall be governed by the laws of the State of New York without regard to conflict of laws provisions.
The U.N. Convention on Contracts for the International Sale of Goods shall not apply hereto. This License
constitutes the complete and exclusive agreement between the parties relating to the license for the Software and
supersedes all proposals, communications, purchase orders, and prior agreements, verbal or written, between the
parties. If any portion hereof is found to be void or unenforceable, the remaining provisions shall remain in full force
and effect.

v
Contents 0
New in this release and documentation roadmap xi
Data circuit packs (Ethernet Private Line and FLEX MOTR) 1-1
4xGE EPL circuit packs (NTK535LAE5 and NTK535LBE5) 1-2
Overview 1-2
Supported functionality 1-5
Cross-connection types 1-7
Cross-connection rates 1-7
Supported SFPs 1-7
Performance monitoring 1-8
Alarms 1-9
Equipping rules 1-10
Engineering rules 1-11
Technical specifications 1-11
Latency 1-12
1x10GE EPL circuit pack (NTK533AAE5) 1-13
Overview 1-13
Supported XFPs 1-16
Alarms 1-18
Latency 1-21
24x10/100BT EPL circuit packs (NTK548BAE5 and NTK548MAE5) 1-22
Overview 1-22
10/100BT I/O panels 1-27
Supported SFPs 1-31
Alarms 1-32

vi Contents

Latency 1-36
FLEX MOTR circuit pack (NTK531YAE5) 1-37
Overview 1-37
Supported SFPs/XFPs 1-41
Alarms 1-49
Latency 1-54
4xGE EPL, 1x10GE EPL, 24x10/100 BT EPL, and FLEX MOTR provisioning
procedures 1-55
4xGE EPL 1-55
1x10GE EPL 1-56
24x10/100BT EPL 1-57
FLEX MOTR 1-58
Provisioning rules summary for the FLEX MOTR circuit packs 1-59
List of procedures
1-1 Provisioning a circuit pack automatically 1-61
1-2 Provisioning a pluggable automatically 1-62
1-3 Installing I/O panels in the 14-slot 6500 shelf 1-63
1-4 Routing Category 5e cables into the electrical interface area 1-70
1-5 Routing fiber-optic cables onto the 6500 shelf 1-75
1-6 Connecting or disconnecting fiber-optic cables to or from circuit packs 1-76
1-7 Adding a facility to an equipment 1-77
1-8 Editing facility parameters 1-81
1-9 Adding a path connection 1-82
1-10 Adding an EVPL connection 1-86
1-11 Provisioning the network element timing mode and references 1-88
1-12 Changing the primary state of a facility 1-92
1-13 Changing the primary state of a circuit pack or pluggable 1-94
1-14 Deleting a facility from an equipment 1-95
1-15 Deleting a circuit pack or pluggable 1-97
Equipment and facility provisioning parameters 1-98
Equipment and facility primary and secondary states 1-98
OCn layer facility parameters 1-100
ETH, ETH100, and ETH10G facility parameters 1-101
WAN facility parameters 1-121
OTM2 facility parameters 1-133
FLEX facility parameters 1-135
ADJ facility parameters 1-138
Synchronization parameters 1-140
Path connections parameters 1-141
EVPL connections parameters 1-149

Contents vii
Layer 2 circuit packs 2-1

L2SS VT1.5/LO 4xGE circuit pack (NTK531BAE5) 2-2
Overview 2-2
Supported SFPs 2-6
Alarms 2-7
L2SS DS1/E1/DS3/E3 4xGE circuit pack (NTK531MAE5) 2-13
Overview 2-13
Supported SFPs 2-19
Alarms 2-20
20G L2SS 16 Port I/O 2xXFP / 8xSFP circuit pack (NTK531HAE5) 2-25
Overview 2-25
Front I/O panel (Multi-Service) 2-28
Alarms 2-36
L2 MOTR 2xXFP/10xSFP circuit pack (NTK531VAE5) 2-41
Overview 2-41
Alarms 2-55
Latency 2-61
eMOTR circuit packs (NTK536AA, NTK536AB, NTK536BE, NTK536FA,
NTK536FB) 2-62

viii Contents
Overview 2-62
Supported SFPs/SFP+s/XFPs 2-81
Alarms 2-90
Latency 2-99
Layer 2 circuit packs summary table 2-100
RPR 10G STS-1/HO 4xGE circuit pack (NTK534BAE5) 2-106
Overview 2-106
Supported SFPs 2-109
Alarms 2-111
Layer 2 circuit pack provisioning procedures 2-115
eMOTR 2-115
L2SS and PDH gateway 2-116
20G L2SS 2-117
RPR 2-118
L2 MOTR 2-119
Provisioning rules summary for the L2 MOTR circuit packs 2-120
Provisioning rules summary for the eMOTR circuit packs 2-120
List of procedures
2-1 Provisioning a circuit pack automatically 2-124
2-2 Provisioning a pluggable automatically 2-126
2-3 Routing fiber-optic cables onto the 6500 shelf 2-127
2-4 Connecting or disconnecting fiber-optic cables to or from circuit packs 2-128
2-5 Adding a facility to an equipment 2-129
2-6 Adding a path connection 2-134
2-7 Adding an EVPL connection 2-139
2-8 Adding a resilient packet ring 2-141
2-9 Adding east and west protection spans in resilient packet rings 2-142
2-10 Performing profiles provisioning tasks 2-144
2-11 Performing service activation for virtual circuits 2-147
2-12 Provisioning the network element timing mode and references 2-155
2-13 Creating a ring in a G.8032 ERP 2-158
2-14 Creating a ring port in a G.8032 ERP 2-160
2-15 Creating a ringlet in a G.8032 ERP 2-161
2-16 Creating a ringlet port in a G.8032 ERP 2-162
2-17 Changing the L2 MOTR equipment profile 2-163
2-18 Editing facility parameters 2-165
2-19 Creating an equipment group and adding members 2-166

Contents ix
2-20 Changing the eMOTR equipment profile 2-169

2-21 Changing the primary state of a facility 2-170
2-22 Changing the primary state of a circuit pack or pluggable 2-172
2-23 Deleting a facility from an equipment 2-174
2-24 Deleting a circuit pack or pluggable 2-177
Equipment and facility provisioning parameters 2-178
Equipment and facility primary and secondary states 2-178
ETH, ETH100, and ETH10G facility parameters 2-180
WAN facility parameters 2-206
LAG facility parameters 2-218
OTM2 facility parameters 2-229
PTP facility parameters 2-232
OTUTTP facility parameters 2-233
ETTP facility parameters 2-235
FTTP facility parameters 2-237
ODUTTP facility parameters 2-237
Synchronization parameters 2-239
RPR Ring provisioning parameters 2-240
RPR Protection parameters 2-245
Profiles Provisioning task 2-247
Virtual Circuit Service Activation task 2-250
Ring parameters in a G.8032 ERP 2-268
Ring port parameters in a G.8032 ERP 2-271
Ringlet parameters in a G.8032 ERP 2-277
Ringlet port parameters in a G.8032 ERP 2-281
Path connections parameters 2-286
EVPL connections parameters 2-298

x Contents

xi
New in this release and documentation

roadmap 0
This Technical Publication supports 6500 Packet-Optical Platform (6500)

Release 12.6 software and subsequent maintenance releases for Release
12.6.
Issue 1
No new/enhanced features are covered in this document for this release.
6500 Packet-Optical Platform technical publications

The following two roadmaps identify the technical publications that support the
6500 D-Series and S-Series platforms and the technical publications that
support the 6500 T-Series platform for Release 12.6.

xii New in this release and documentation roadmap
6500 D-Series and S-Series roadmap
Planning a Network Installing, Managing and Maintaining and Circuit Pack-Based

Commissioning and Provisioning Troubleshooting Documentation
Testing a Network a Network a Network
Documentation Installation - Administration Fault Management - Common Equipment

Roadmap General Information and Security Performance (323-1851-102.1)
(323-1851-090) (323-1851-201.0) (323-1851-301) Monitoring
(323-1851-520) Electrical
Planning - Installation - Configuration -
(323-1851-102.2)
Parts 1, 2, and 3 2-slot Shelves Provisioning &
(NTRN10EY) Operating Parts 1 & 2 Fault Management -
(323-1851-201.1) OC-n/STM-n
Data Comms (323-1851-310) Alarm Clearing
(323-1851-102.3)
Planning & User Guide Installation - 7-slot & Parts 1 and 2
(323-1851-101) 6500-7 packet-optical Configuration - (323-1851-543) WaveLogic Ai, Flex,
Shelves Protection Switching 100G+, 40G,
Ordering Information
(323-1851-201.2) (323-1851-315) Fault Management - OSIC ISS, & SLIC10
(323-1851-151)
Module (323-1851-102.4)
Manufacturing Installation - Configuration - Replacement
Discontinued Parts 14-slot Shelves Bandwidth & Data (323-1851-545)
(323-1851-155) (323-1851-201.3) Services Parts 1,2,3 Broadband/SMUX
(323-1851-320) OTN FLEX MOTR
NBI Fundamentals Installation - Fault Management - (323-1851-102.5)
(323-1851-165) 32-slot Shelves Configuration - SNMP
(323-1851-201.4) Control Plane (323-1851-740) Photonics
Latency
(323-1851-330) Equipment
Specifications Passive Chassis
(323-1851-170) Encryption and FIPS Fault Management - (323-1851-102.6)
(2150 & Photonics), Customer Visible
Pluggable Security Policy
Filters, and Modules Logs Data and Layer 2
Datasheets Overview and
(323-1851-201.5) (323-1851-840) (323-1851-102.7)
and Reference Procedures
(323-1851-180) (323-1851-340)
Licensing OTN I/F, PKT I/F, &
TL-1 Description (323-1851-210) MyCryptoTool PKT/OTN I/F
(323-1851-190) Certificate (323-1851-102.8)
Commissioning Management and
CLI Reference and Testing Quick Start
(323-1851-193) (323-1851-221) (323-1851-341)
Site Manager
Fundamentals
(323-1851-195)
SAOS-based Command Fault and MIB

Configuration Reference
Packet Services Reference Performance
(323-1851-630) (323-1851-690)
Documentation (323-1851-610) (323-1851-650)
Supporting WaveLogic Photonics 6500 Data 6500 Control Plane Submarine Networking
Documentation Coherent Select Application Guide Application Guide Application Guide
(323-1851-980) (NTRN15BA) (NTRN71AA) (NTRN72AA)
6500 Photonic Common 6500 - 5400 / 8700 Fiber Node Return 6500 AC Rectifier
Layer Guide Photonic Layer Interworking Solution Configuration (323-1851-900)
(NTRN15DA) Technical Publications (323-1851-160) (323-1851-985)

New in this release and documentation roadmap xiii
6500 T-Series roadmap
Planning a Network Installing, Managing and Maintaining and

Commissioning and Provisioning Troubleshooting
Testing a Network a Network a Network
T-Series Administration Fault Management -

Installation - Performance
Shelf Guide and Security
T-Series Shelves Monitoring
(323-1851-103) (323-1851-301)
(323-1851-201.6) (323-1851-520)
Data Communications Configuration -
Planning and Licensing Provisioning and Fault Management -
User Guide (323-1851-210) Operating Parts 1 & 2 Alarm Clearing
(323-1851-101) for T-Series Parts 1 and 2
T-Series Shelf (323-1851-311) for T-Series
Manufacturing Guide
(323-1851-544)
Discontinued Parts (323-1851-103) Configuration -
(323-1851-155) Protection Switching Fault Management -
(323-1851-315) Module
NBI Fundamentals
Replacement
(323-1851-165) Configuration - for T-Series
Bandwidth (323-1851-546)
TL-1 Description for T-Series
for T-Series (323-1851-321) Fault Management -
(323-1851-191) SNMP
CLI Reference Configuration - (323-1851-740)
for T-Series Control Plane
(323-1851-194) (323-1851-330) Fault Management -
Customer Visible
Site Manager Logs
Fundamentals (323-1851-840)
(323-1851-195)
SAOS-based Command Fault and MIB

Packet Services Configuration Reference
Reference Performance
Documentation (323-1851-630) (323-1851-690)
(323-1851-610) (323-1851-650)

xiv New in this release and documentation roadmap

1-1
Data circuit packs (Ethernet Private Line

and FLEX MOTR) 1-
This section provides an overview of the 6500 Packet-Optical Platform (6500)

data circuit packs and their associated procedures. See the following table for
different circuit packs covered in this section.
Table 1-1
Data circuit packs in this section
Topic
“4xGE EPL circuit packs (NTK535LAE5 and NTK535LBE5)” on page 1-2
“1x10GE EPL circuit pack (NTK533AAE5)” on page 1-13
“24x10/100BT EPL circuit packs (NTK548BAE5 and NTK548MAE5)” on page 1-22
“FLEX MOTR circuit pack (NTK531YAE5)” on page 1-37
Refer to 6500 Packet-Optical Platform Data Application Guide, NTRN15BA,

for detailed information on data concepts, applications, and engineering rules
supported in this release of 6500.

1-2 Data circuit packs (Ethernet Private Line and FLEX MOTR)
4xGE EPL circuit packs (NTK535LAE5 and NTK535LBE5)

Overview
The 4xGE EPL circuit packs (also referred to as GE) are used to transport
point-to-point Gigabit Ethernet traffic. GE services are mapped into SONET/
SDH containers which are connected to SONET/SDH or Ethernet based ports
on other circuit packs. They can therefore use the traffic protection schemes
supported by the OC-n/STM-n interface circuit packs to provide a protected
GE service without the requirement of a redundant handoff from the
subtending GE equipment. The 4xGE EPL circuit packs use SFP optics for
different applications.
There are two variants of the 4xGE Ethernet Private Line (EPL) circuit pack:
• 4xGE EPL circuit pack (NTK535LAE5)
• 4xGE EPL Ethernet in the First Mile (EFM) circuit pack (NTK535LBE5)
Both variants provide the same functionality except that the 4xGE EPL EFM
circuit pack also provides OAM management over Ethernet for remote failure
indication and control of customer premises equipment (CPE) (802.3ah).
The 4xGE EPL circuit pack consists of two entities (client facing and line
facing):
• client facing interfaces referred to as LAN ETH ports
• line facing (mapped for transport via SONET/SDH containers) interfaces
of the circuit pack referred to as WAN ports
The following figure shows the LAN-WAN concept of the 4xGE EPL circuit
pack.
Figure 1-1
4xGE EPL LAN-WAN concept
Line facing
Client facing (GFP-F mapped)
GE LAN/ETH port 1 WAN port 1 STS/VC containers

Figure 1-2 on page 1-3 shows the faceplate of a 4xGE EPL circuit pack. Figure
1-3 on page 1-4 and Figure 1-4 on page 1-5 provide functional block diagrams
of the 4xGE circuit packs.

Figure 1-2
4xGE EPL circuit pack faceplate
Red triangle (Fail)

GE
- Used to communicate hardware or software failure state
EPL
4 Ports SFP
Fail
- Card not failed = LED off, Card failed = LED on
Ready
In Use
Green rectangle (Ready)
- Used to communicate hardware or software functional state
- Card initializing = Blinking LED; Card OK = LED on; Card not ready = LED off
Blue diamond (In Use)

- Used to communicate whether circuit pack can be extracted
1 Tx (on->no pull, off->can be pulled)
Rx
- Equipment in-service = LED on; Equipment out-of-service = LED off
2 Tx
Rx
3 Tx
Rx Red/yellow bi-color circle (Fail/LOS)

4 Tx - Used to communicate Rx Loss of Signal/optical module fail
Rx
- Red = module fail;
- Yellow = Rx Loss of Signal
Hazard
level:
Transmit/receive SFP dual LC connector

R99
EEEEE99999
S/N NT030MEE9999E
NTUD99EE
Type A

Figure 1-3
4xGE EPL circuit pack block diagram (NTK535LAE5)
PHY SFP 1
GFP
Mapper
XC
PHY SFP 2
Backplane
5G SONET/SDH
OHP
PHY SFP 3
XC
GFP
Mapper
PHY SFP 4
Processor Power
Module Supply
Legend
GFP Generic framing procedure
OHP Overhead processor
PHY Physical layer adapter

Figure 1-4
4xGE EPL EFM circuit pack block diagram (NTK535LBE5)
PHY SFP 1
GFP Mapper
with EFM
XC
PHY SFP 2
Backplane
5G SONET/SDH
OHP
PHY SFP 3
XC
GFP Mapper
with EFM
PHY SFP 4
Processor Power
Module Supply
Legend
EFM Ethernet in the first mile
Supported functionality
The 4xGE EPL circuit packs (NTK535LAE5 and NTK535LBE5) provide the
following functionality.
• up to four pluggable (SFP) GE interfaces (ports 1 to 4)
• the transport of GE services
• auto-detection of SFP modules, which are hot pluggable
• manual provisioning of SFP modules
• point-to-point GE application.
• full-rate and sub-rate GE service transport
• provisionable Ethernet auto-negotiation (Enable or Disable) with the local
Ethernet link partner as per clause 37 of IEEE Std 802.3
• full duplex mode only

• supports Inter-Packet Gap (IPG) on all variants of 4xGE EPL circuit packs
(NTK535LAE5 and NTK535LBE5). The IPG determines the minimum idle
period between transmission of packets and can be set for each LAN port.
• 64 byte to 9600 byte Ethernet frames
• provisionable Ethernet maximum transfer unit (MTU) of 1600 bytes
(default) or 9600 bytes
• Ethernet flow control capabilities (this attribute is ignored when auto-
negotiation is disabled)
— None (advertises flow control not supported)
— Asymmetric (default) (advertises asymmetric flow control toward the
link partner)
— Symmetric (advertises symmetric flow control or asymmetric flow
control toward the local device)
— supports loss less local flow control for distances up to 10 km (local
loop) for all MTU sizes (1600 and 9600)
— automatically adjusts the PAUSE transmit thresholds to maximize the
supported distance based on the MTU attribute
• enabling/disabling Ethernet control frames transport
— the only currently standardized Ethernet control frame (T/L=0x8808) is
the PAUSE frame
— determine if received Ethernet control frames (T/L=0x8808) are
discarded or passed through transparently, editable to DISABLE
(default) or ENABLE
— Ethernet frames received with T/L=0x8809 (slow protocols) are always
transparently passed through
• supports unprotected and 1+1 linear traffic protection schemes
• has 92.8 KB allocated for the ingress buffer and 28.8 KB for the egress
buffer. These buffers have been sized for transmission of 9600 byte jumbo
packets at 5km reach, or 20km reach of 1522 byte packets.
• supports Control Plane (GE facility is only supported as add/drop Control
Plane facility and not Network Control Plane facility)
Note 1: Refer to the 6500 Packet-Optical Platform Control Plane
Application Guide, NTRN71AA, for detailed information on Control Plane
concepts, applications, and engineering rules supported in this release of
6500.
Note 2: For more GE information and applications, see the 6500 Packet-
Optical Platform Data Application Guide, NTRN15BA.

Cross-connection types
The 4xGE EPL and 4xGE EPL EFM circuit packs support the following cross-
connection types:
• 1WAY (Unidirectional)
• 1WAYPR (Unidirectional Path Ring)
• 2WAY (Bidirectional)
• 2WAYPR (Bidirectional Path Ring)
• sub-network connection (SNC) when OSRP Control Plane enabled
• virtual end point (VEP) when OSRP Control Plane enabled
Cross-connection rates
The 4xGE EPL and 4xGE EPL EFM circuit packs support the following cross-
connection rates:
• non-concatenated rates of STS1/HO VC3 and VC4
• concatenated rates of STS3c, STS12c/VC4-4c, STS24c/VC4-8c
• virtual concatenation rates of STS1-nv/LO VC3-nv (n = 1 to 21) and
STS3c-nv/VC4-nv (n = 1 to 7)
WAN signals can be mapped to non-concatenated, concatenated and virtual

concatenated rates.
• STS1/HO_VC3 and STS3c/VC4 connection rates are supported with all
SONET/SDH cross-connect circuit packs.
• LO_VC3 support depends on the type of cross-connect circuit packs used
in the shelf:
— when LO cross-connect circuit packs are used in the shelf, LO_VC3
mapping is supported.
— when 240G+ STS-1/VC3 (240/0G) or 640G+ STS-1/VC-3 (640/0G)
cross-connect circuit pack are used in the shelf, LO_VC3 mapping is
supported.
— when 80G STS-1/VC3 (80/0G) or 160G+ STS-1/VC-3 (160/0G) cross-
connect circuit packs are used in the shelf, LO_VC3 mapping is not
supported.
Supported SFPs
The following table provides a list of the SFPs that are supported on the 4xGE
EPL circuit pack.

Table 1-2
Supported SFP modules for the 4xGE EPL circuit packs (NTK535LAE5 and NTK535LBE5)
Pluggable Equipment and Supported SFP modules and rates Part Number
Facilities
PGE GE 1000-Base-ZX 1550 nm SFP NTTP07FF

— ETH (WAN) — 1000Base-X (1.25Gb/s)
GE 1000-Base-BX 10-U Bidirectional-upstream, NTTP58BD

1310 nm Tx, 10 km SFP
— 1000Base-X (1.25Gb/s)
GE 1000-Base-BX 10-D Bidirectional- NTTP59BD

downstream, 1490 nm Tx, 10 km SFP
— 1000Base-X (1.25Gb/s)
1000-BaseT RJ45 SFP NTTP61AAE6

— 1000Base-T (1.00Gb/s)
PGEFC GE/FC100 1000-BaseSX 850 nm SFP NTTP01AF

GE/FC100 1000-BaseLX 1310 nm SFPs NTTP01CF and

— 1000Base-X (1.25Gb/s) NTTP01CDE6
GE/FC100 1.25 Gbit/s 24 dB CWDM SFPs NTK591xB where

— 1000Base-X (1.25Gb/s) x= L, M, N, P, Q,
R, S, T
GE/FC100 1.25 Gbit/s 32 dB CWDM SFPs NTK591xH where

— 1000Base-X (1.25Gb/s) x= L, M, N, P, Q,
R, S, T)
PGEFC200 GE/FC100/FC200 1000-BaseSX 850 nm SFP NTTP06AF

GE/FC100/FC200 1000-BaseLX 1310 nm SFP NTTP06CF

— 1000Base-X (1.25Gb/s)
Performance monitoring
The 4xGE EPL and 4xGE EPL EFM circuit packs support the following
monitored entities:
• PM collection for ETH and WAN facilities
• operational measurements collection for ETH and WAN facilities
For detailed information and procedures associated with performance

monitoring, refer to Fault Management - Performance Monitoring, 323-1851-
520.

Alarms
Equipment alarms
• Autoprovisioning Mismatch
• Circuit Pack Missing
• Circuit Pack Mismatch
• Circuit Pack Failed
• Circuit Pack Latch Open
• Circuit Pack Upgrade Failed
• Cold Restart Required
• Database Not Recovered For Slot
• Intercard Suspected
• Internal Mgmt Comms Suspected
• Provisioning Incompatible
Pluggable alarms
• Autoprovisioning Mismatch - Pluggable
• Circuit Pack Missing - Pluggable
• Circuit Pack Mismatch - Pluggable
• Circuit Pack Failed - Pluggable
• Circuit Pack Unknown - Pluggable
• Intercard Suspected - Pluggable
Ethernet alarms
• CPE Discovery Protocol Fail
• Client Service Mismatch
• Excessive Error Ratio
• Far End Client Rx Signal Failure
• Forced Switch Active
• Link Down
• Lockout Active
• Loopback Active - Facility
• Loopback Active - Terminal
• Loss Of Signal
• Loss of data Synch
• Manual Switch Active
• Protection Switch complete

• Remote Invalid Configuration

• Remote Power Fail Indication
• Remote Client Link Down
• Remote Loopback Active
• Remote Loopback Fail
• Remote Receiver Fail
• Rx Ethernet Idle
• Signal Degrade
WAN alarms
• Link Down
• Loss of Frame delineation
• Signal Degrade
STS Path alarms

• Loss of Alignment - VCAT
• Loss of Sequence - VCAT
• Loss of Multiframe
Common alarms
• Software Auto-Upgrade in Progress
Equipping rules
The following equipping rules apply to 4xGE EPL circuit packs:
• is a single four-port slot interface.
• can be installed in slots 1-6 and 9-14 in an 14-slot shelf type.
ATTENTION
This circuit pack is not supported in 14-slot shelf types when the shelf is
equipped with PKT/OTN cross-connect circuit packs.
• can be installed in slots 1-8, 11-18, 21-28, and 31-38 in a 32-slot packet-
optical shelf type when the shelf is equipped with 640G+ STS-1/VC-3
(640/0) (NTK610BBE5) cross-connect circuit packs.
ATTENTION
This circuit pack is not supported in 32-slot packet-optical shelf types when
the shelf is equipped with PKT/OTN cross-connect circuit packs.

• is not supported in a 7-slot optical shelf type (NTK503PAE5 or

NTK503KA).
• cannot be equipped in a 6500-7 packet-optical shelf type (NTK503RA) in
this release.
• is not supported in a 2-slot shelf type.
• can be installed in 6500 shelves containing LO (Low Order) and HO (High
Order) XC circuit packs.
• are not supported when used with 20/20 cross-connect circuit packs.
Engineering rules
For more information about 4xGE EPL engineering rules, refer to 6500
Packet-Optical Platform Data Application Guide, NTRN15BA.
Technical specifications
The following table lists the weight, power consumption, and SFP
specifications for the 4xGE EPL optical interface circuit packs.
Table 1-3
Technical specifications for 4xGE EPL optical interface circuit packs
Parameter 4xGE EPL (NTK535LAE5/NTK535LBE5)

Weight (estimated) 1.2 kg (2.6 lb)
Power consumption Typical (W): 35 (Note 1, Note 3, and Note 4)
Power Budget (W): 35 (Note 2, Note 3, and Note 4)
SFP specifications (Note 5)
Note 1: The typical power consumption values are based on operation at an ambient temperature of
25 (+/-3oC) and voltage of 54 Vdc (+/-2.5 V) or in the full operational voltage range in the case of AC-
powered equipment. For practical purposes, the rounded typical power consumption of an equipment
can be used as the equipment heat dissipation when calculating facilities thermal loads (an estimate of
the long term heat release of the item in a system).
Note 2: The power budget values are based on the maximum power consumption in an ambient
temperature range from 5oC to 40oC at a voltage of 40 Vdc (+/-2.5 V) or in the full operational voltage
range in the case of AC-powered equipment. These rounded power values must be used in sizing
feeders and estimating theoretical maximum power draw.
Note 3: The power consumption values are derated so that pluggables transceivers must be
considered separately. When estimating the total power for the equipment in a slot or in a system, you
must add the power values for each of the required pluggable devices For pluggable transceiver power
values, refer to Pluggable Datasheets and Reference, 323-1851-180.
Note 4: For this circuit pack that must be equipped with SFPs, the power values published in this table
do not include SFPs power values. You must add 1 W to typical or power budget values per SFP.
Note 5: For optical SFP specifications, see chapter 3 of Pluggable Datasheets and Reference, 323-
1851-180.

Latency
This Technical Publication no longer provides latency specifications. All
latency information is available in Latency Specifications, 323-1851-170.

1x10GE EPL circuit pack (NTK533AAE5)

Overview
The 1x10GE EPL circuit packs (also referred to as 10GE) are used to
transport the point-to-point 10 Gigabit Ethernet (10GE) services. 10GE
services are mapped into SONET/SDH containers which are connected to
SONET/SDH or Ethernet based ports on other circuit packs. They can
therefore use the traffic protection schemes supported by the OC-n/STM-n
interface circuit packs to provide a protected 10GE service without the
requirement of a redundant handoff from the subtending 10GE equipment.
The 1x10GE EPL circuit packs use XFP optics for different applications.
The 1x10GE EPL circuit pack consists of two entities (client facing and line
facing):
• a client facing interface referred to as the LAN port (ETH10G)
• a line facing interface (GFP-F mapped for transport via SONET/SDH
containers) referred to as the WAN port
There is one to one relationship between the LAN port and the WAN port.
Figure 1-5 on page 1-14 shows the faceplate of a 1x10GE EPL circuit pack.
Figure 1-6 on page 1-15 provides functional block diagram of the 1x10GE EPL
circuit pack.

Figure 1-5
1x10GE EPL circuit pack faceplate
Red triangle (Fail)

10GE LAN/WAN
10G EPL
1 Port XFP
- Card not failed = LED off, Card Failed = LED on
Fail
Ready
In Use
(on->no pull, off->can be pulled)
Red/yellow bi-color circle (Fail/LOS)

- Used to communicate Rx Loss of Signal/optical module (XFP) fail
- Red = module fail; Yellow = Rx Loss of Signal
Transmit/receive XFP dual LC connector
Hazard
level:
R99
EEEEE99999
S/N NT030MEE9999E
NTUD99EE
Type A

Figure 1-6
1x10GE EPL circuit pack block diagram (NTK533AAE5)
XC
Backplane
10G SONET/SDH GFP PHY XFP 1

OHP Mapper
XC
Processor Power
Module Supply
Legend
The 1x10GE EPL circuit pack (NTK533AAE5) provides the following
functionality.
• one pluggable (XFP) 10GE interfaces (port 1)
• auto-detection of XFP module, which is hot pluggable
• manual provisioning of XFP module
• point-to-point 10GE applications
• full-rate and sub-rate 10GE service transport
• 64 byte to 9018 byte Ethernet frames (default 1600)
• full duplex mode with asymmetric flow control
• Ethernet control Pause frames (T/L=0x8808) are discarded

• Ethernet frames received with T/L=0x8809 (slow protocols) are always

• has 2MB of memory shared between ingress and egress buffers. 40km
reach has been tested with pause frame enabled.
• supports Control Plane (10GE facility is only supported as add/drop
Control Plane facility and not Network Control Plane facility)
6500.
The 1x10GE EPL circuit pack supports the following cross-connection types:
The 1x10GE EPL circuit pack supports the following cross-connection rates:
• concatenated rates of STS192c/VC4-64c
• virtual concatenation rate of STS3c-nv/VC4-nv (n = 1 to 64)
ATTENTION
100% utilization cannot be achieved with the 1x10GE EPL circuit pack when
subjected to test traffic patterns comprised solely of small Ethernet frame
sizes between 64 bytes and 80 bytes over STS-3c-61v/VC4-61v or higher
VCAT connections. The issue is solely limited to VCAT connections and does
not impact CCAT connections. 100% throughput can be achieved over any
VCAT or CCAT connection rate for real-world traffic patterns comprised of
random Ethernet frame sizes.
Supported XFPs
The following table provides a list of the XFPs that are supported on the
1x10GE EPL circuit pack.

Table 1-4
Supported XFP modules for the 1x10GE EPL circuit pack (NTK533AAE5)
Pluggable Equipment and Supported XFP modules and rates Part Number
Facilities (Note 1)
P10GSEL OC192/STM64 SR-1 / I-64.1 / 10GBase-LR,LW NTTP80BA

— ETH10G (WAN) (auto) XFP
— 9.953 Gb/s OC192/STM64/10GBaseW
OC192/STM64 IR-2 / S-64.2 / 10GBase-ER,EW NTTP80DA

XFP
P10GEL 10GBASE-SR/SW, 850 nm, 30-300 m, MMF NTTP81AA

— ETH10G (WAN) (auto) XFP (Note 2)
— 10.3125 Gb/s 10GBaseR (10GE)
10G-Base-LR/LW (1310nm, SMF, 10km), 0-70C NTTP81BA

XFP
— 10.3125 Gb/s 10GBaseR (10GE)
10GBASE-ER/EW, 1550 nm, 30 km, SMF XFP NTTP81DA

— 10.3125 Gb/s 10GBaseR (10GE)
P10GSOEL OC192/STM64 SR-1 / I-64.1 / VSR-2000-2R1 / NTTP83BA

— ETH10G (WAN) (auto) 10GBase-LR,LW
— 10.3125 Gb/s 10GBaseR (10GE)
9.95G-11.09G multirate, 1550 nm, SMF, 40 km NTTP84AAE6

XFP
— 10.3125 Gb/s 10GBaseR (10GE)
OC192/STM64 SR-1/ I-64.1 / 10GBase-LR,LW / NTTP84BA

OTU2 / 10G FC1200 XFP
— 10.3125 Gb/s 10GBaseR (10GE)
Note 1: The (auto) means the facility is auto-provisioned upon equipment/pluggable equipment
creation. The facilities in brackets are facilities auto-created on the same port as the main facility or
equipment. These facilities inherit the primary state of the main facility/equipment and are auto-deleted
when the main facility/equipment is deleted.
Note 2: MMF stands for multi-mode fiber.
The 1x10GE EPL circuit pack supports the following monitored entities:
• PM collection for ETH10G and WAN facilities
• operational measurements collection for ETH10G and WAN facilities


520.
Alarms
For a complete list of alarm clearing procedures for 6500, refer to Part 1 and
Part 2 of Fault Management - Alarm Clearing, 323-1851-543.
Equipment alarms
Pluggable alarms
• Provisioning Incompatible - Pluggable
Ethernet alarms
• Local Fault
• Loss of Signal

• Loss of Data Synch

• Remote Fault
• Signal Degrade
WAN alarms
• Link Down
• Signal Degrade
STS Path alarms

Common alarms
Equipping rules
The following equipping rules apply to 1x10GE EPL circuit packs:
• is a single one-port slot interface.
• can be installed in slots 1 to 6 and slots 9 to 14 in a 14-slot shelf type when
used with the 160G+ STS-1/VC-3 cross-connect circuit pack, 240G+ STS-
1/VC-3 cross-connect circuit pack, or 240G+/80G VT1.5/VC-12 cross-
connect circuit pack. In 14-slot packet-optical shelf type, all supported
cross-connect circuit packs in this shelf can be used to install the circuit
pack in slots 1 to 6 and slots 9 to 14.
ATTENTION
• slots 5, 6, 9, and 10 in a 14-slot shelf type (except for packet-optical shelf

type) when used with 80G cross-connect circuit packs (80/20, 80/80, and
80/0) (slots 1 to 4 and 11 to 14 can be also used with 80G cross-connect
circuit packs when only 5G of bandwidth is required).
ATTENTION
The 1x10GE EPL circuit packs are not supported when used with the 20G
cross-connect circuit packs (20G/20G VT1.5/VC-12 XC and MXC). The
1x10GE EPL circuit pack is not supported on the Metro front/electrical shelf.

• can be installed in slots 1-8, 11-18, 21-28, and 31-38 in a 32-slot packet-
optical shelf type when the shelf is equipped with 640G+ STS-1/VC-3
(640/0) (NTK610BBE5) cross-connect circuit packs.
ATTENTION

NTK503KA).
this release.
Engineering rules
For more information about 1x10GE EPL engineering rules, refer to 6500
The following table lists the weight, power consumption, and XFP
specifications for the 1x10GE EPL optical interface circuit packs.
Table 1-5
Technical specifications for 1x10GE EPL optical interface circuit packs
Parameter 1x10GE EPL (NTK533AAE5)


Table 1-5
Technical specifications for 1x10GE EPL optical interface circuit packs (continued)
Parameter 1x10GE EPL (NTK533AAE5)

XFP specifications (Note 5)
can be used as the equipment heat dissipation when calculating facilities thermal loads (an estimate of
the long term heat release of the item in a system).
Note 4: For this circuit pack that must be equipped with XFP, the power values published in this table
do not include XFP power values. You must add 2 W to typical power value and 3 W to power budget
for each XFP module with reach less than IR-2/S-64.2b. You must add 3 W to typical power value and
4 W to power budget for each XFP module with IR-2/S-64.2b reach or greater.
Note 5: For optical XFP specifications, see chapter 2 of Pluggable Datasheets and Reference, 323-
1851-180.
Latency

24x10/100BT EPL circuit packs (NTK548BAE5 and NTK548MAE5)

Overview
There are two variants of the 24x10/100BT EPL circuit packs:
• 24x10/100BT EPL circuit pack (NTK548BAE5). This circuit provides 24
10/100BT ports accessed from an I/O panel in the electrical interface area
of the 14-slot shelf.
• 24x10/100BT EPL with 8xSFP circuit pack (NTK548MAE5). This circuit
pack supports up to 24 10/100BT ports accessed from an I/O panel in the
electrical interface area of the 14-slot shelf. In addition, the faceplate of the
circuit pack can accommodate up to eight 100FX SFPs. This allows the
first eight ports to be user selectable between electrical (I/O panel) or
optical (100FX SFP). This variant also provides OAM management over
Ethernet for remote failure indication and control of customer premises
equipment (CPE) (802.3ah).
The 24x100/100BT EPL circuit pack consists of two entities (client facing and
line facing):
• client facing interfaces referred to as LAN ETH100 ports
• line facing (mapped for transport via SONET/SDH containers) aspects of
the circuit pack referred to as WAN ports
10/100BT services map to SONET/SDH containers and are assigned as

connections to OC-n/STM-n interface circuit packs. They can therefore use
the traffic protection schemes supported by the OC-n/STM-n interface circuit
packs to provide a protected 10/100BT service without the requirement of a
redundant handoff from the subtending 10/100BT equipment.
Figure 1-7 on page 1-23 shows the faceplate of a 24x10/100BT EPL circuit
pack. Figure 1-8 on page 1-24 and Figure 1-9 on page 1-25 provide a
functional block diagrams of the 24x10/100BT EPL circuit packs.

Figure 1-7
24x10/100BT EPL circuit pack faceplate
Red triangle (Fail)

10/100BT 10/100BT
EPL
24 Ports
Fail
EPL
24 Ports SFP
Fail
Ready
In Use
Ready
In Use
1 Tx
Rx
2 Tx Blue diamond (In Use)

Rx
Rx
4 Tx
Rx
5 Tx

Rx
7 Tx - Yellow = Rx Loss of Signal
Rx
8
Yellow circle (LOS)
Rx
- Used to communicate Loss of Sync of any 10/100 BT input
Hazard
level:
Hazard
level: on the I/O panel
R99
R99
EEEEE99999
EEEEE99999
S/N NT030MEE9999E
S/N NT030MEE9999E
NTUD99EE
NTUD99EE
Type A Type A Transmit/receive SFP dual LC connector

Figure 1-8
24x10/100BT EPL circuit pack block diagram (NTK548BAE5)
I/O Panel 24 x PHY

Backplane
GFP Mapper
XC
2.5G SONET/SDH
OHP
XC
Processor Power
Module Supply
Legend
PHY Physical layer dapter

Figure 1-9
24x10/100BT EPL with 8xSFP circuit pack block diagram (NTK548MAE5)
PHY SFP 1
I/O Panel 24 x PHY PHY SFP 2
PHY SFP 3
Backplane
PHY SFP 4
GFP Mapper with EFM
PHY SFP 5
PHY SFP 6
XC
PHY SFP 7
2.5G SONET/SDH
OHP
PHY SFP 8
XC
Processor Power
Module Supply
Legend
EFM Ethernet in the first mile
The 24x10/100BT EPL circuit packs (NTK548BAE5 and NTK548MAE5)
support the following:
• the transport of 24 10/100BT services
• auto-detection of SFP modules on 8xSFP variant, which are hot
pluggable, unless facility on corresponding I/O panel port already
provisioned
• manual provisioning of SFP modules on 8xSFP variant
• point-to-point 10/100BT applications
• full-rate and sub-rate 10/100BT service transport
• AU3 and AU4 mapping (user provisionable)
• provisionable Ethernet auto-negotiation (Enable or Disable) with the local
Ethernet link partner as per clause 37 of IEEE Std 802.3

• automatic detection of duplex mode (full/half) and speed (10/100 Mbit/s)

• supports Inter-Packet Gap (IPG) on all variants of 24x10/100BT EPL
circuit packs (NTK548BAE5 and NTK548MAE5). The IPG determines the
minimum idle period between transmission of packets and can be set for
each LAN port.
• 64 byte to 9216 byte Ethernet frames (default 1600)
• has 64 MB of memory shared for egress and ingress buffers. These
buffers are shared by all 24 ports and dynamically assigned as needed.
• Ethernet flow control capabilities (this attribute is ignored when auto-
negotiation is disabled)
— None (advertises flow control not supported)
— Asymmetric (default) (advertises asymmetric flow control toward the
link partner)
— Symmetric (advertises symmetric flow control or asymmetric flow
control toward the local device)
— supports loss less local flow control for distances up to 10 km (local
loop) for all MTU sizes (1600 and 9216)
— automatically adjusts the PAUSE transmit thresholds to maximize the
supported distance based on the MTU attribute
• Ethernet control Pause frames (T/L=0x8808) are discarded
• Ethernet frames received with T/L=0x8809 (slow protocols) are always
• Ethernet in the first mile (EFM) on 24x10/100BT EPL with 8xSFP variant,
compliant to IEEE Std 802.3
• supports Control Plane (FE facility is only supported as add/drop Control

6500.

10/100BT I/O panels

I/O panels in the electrical interface chassis of the 14-slot optical/front
electrical shelf, the converged optical/front electrical shelf, the optical/rear
electrical shelf, the converged optical/rear electrical shelf, or the Metro front
electrical shelf provide the electrical interfaces for the 24x10/100BT EPL
circuit packs. Each I/O panel supports 48 10/100BT inputs/outputs. The
electrical interface chassis contains four slots for mounting the I/O panels, one
for each I/O panel:
• the I/O panel connected to slot 1 in the electrical interface chassis
supports the 24x10/100BT EPL circuit packs in slots 1 and 2
Alignment pins on the backplane and an insertion/ejector bar on the I/O

panels aid alignment during installation of the I/O modules.
The following variants of the 48x10/100BT I/O panels are available (see
Figure 1-10 on page 1-28):
• 48x10/100BT front I/O panel, NTK574CA (unprotected)
• 48x10/100BT rear I/O panel, NTK574QA (unprotected)

Figure 1-10
10/100BT I/O panels
Figure 1-11 and Figure 1-12 on page 1-30 provide functional block diagrams
of the 10/100BT I/O panels.

Figure 1-11
48x10/100BT front I/O panel block diagram (NTK574CAE5)
Backplane
Even slot
Odd slot
Even slot - 1-24 RJ45

Odd slot - 1-24 RJ45

Figure 1-12
48x10/100BT rear I/O panel block diagram (NTK574QAE5)
Even slot - 1-24 RJ45
Odd slot - 1-24 RJ45

Even slot
Odd slot
Backplane
The 24x10/100BT EPL circuit pack supports the following cross-connection
types:
The 24x10/100BT EPL circuit pack supports the following connection rates:
• non-concatenated rate of STS1/LO VC3, STS1/HO VC3, and VC4
• concatenated rates of STS3c
• virtual concatenation rates of VT1.5-nv/VC11-nv (n=1 to 63), VT2-nv/
VC12-nv (n=1 to 45), STS1-nv/LO VC3-nv (n=1 to 3), and STS1-nv/HO
VC3-nv (n=1 to 3)

WAN signals can be mapped to non-concatenated, concatenated and virtual

concatenated rates.
• STS1/HO_VC3 and STS3c/VC4 connection rates are supported with all
SONET/SDH cross-connect circuit packs.
• VT1.5/VT2/VC11/VC12 rates are only supported with LO-capable (VT1.5/
VC12) cross-connects except 240G+ 80G VT1.5/VC12 (240/80).
• LO_VC3 support depends on the type of cross-connect circuit packs used
in the shelf:
— when LO cross-connect circuit packs are used in the shelf, LO_VC3
mapping is supported.
— when 240G+ STS-1/VC3 (240/0G) or 640G+ STS-1/VC-3 (640/0G)
cross-connect circuit pack are used in the shelf, LO_VC3 mapping is
supported.
— when 80G STS-1/VC3 (80/0G) or 160G+ STS-1/VC-3 (160/0G) cross-
connect circuit packs are used in the shelf, LO_VC3 mapping is not
supported.
Supported SFPs
The following table provides a list of the SFPs that are supported on the
24x10/100BT EPL circuit pack.
Table 1-6
Supported SFP modules for the 24x10/100BT EPL with 8xSFP circuit pack (NTK548MAE5)
Facilities
PFE 100-Base-FX 100 Mbit/s 1310 nm multimode 2 NTTP08AC

— ETH100 (WAN) km
— 100Base-X (125Mb/s)
100-Base-LX FE 1310 nm 10km NTTP08SD

— 100Base-X (125Mb/s)
100-Base-BX 10-U Bidirectional-upstream, 1310 NTTP09BD

nm Tx, 10 km
— 100Base-X (125Mb/s)
100-Base-BX 10-D Bidirectional-downstream, NTTP10BD

1530 nm Tx, 10 km
— 100Base-X (125Mb/s)

The 24x10/100BT EPL circuit pack supports the following monitored entities:
• PM collection for ETH100 and WAN facilities
• operational measurements for ETH100 and WAN facilities

520.
Alarms
Equipment alarms
• I/O Panel Missing
• I/O Panel Mismatch
• I/O Panel Unknown
Pluggable alarms

Ethernet alarms
• Link Down
• Loss Of Signal
• Loss Of Data Synch
• Signal Degrade
WAN alarms
• Link Down
• Signal Degrade
STS Path alarms

VT Path alarms
• Payload Extended Label Mismatch

Common alarms
Equipping rules
The following equipping rules apply to 24x10/100BT EPL and 24x10/100BT
EPL with 8xSFP circuit packs:
• In a 14-slot shelf type, the 24x10/100BT EPL circuit packs can be installed
in slots 1-4 and 9-12 in electrical shelves other than Metro front electrical
shelf and only in slots 5 and 6 in Metro front electrical shelf.
• The 24x10/100BT EPL circuit pack is not supported in a 2-slot, 6500-7
packet-optical, 7-slot, or 32-slot shelf type.
• In a 14-slot shelf type, the 24x10/100BT EPL with 8xSFP circuit packs can
be installed in slots 1-4 and 9-12 in shelves other than Metro front
electrical shelf and in slots 1-6 and 9-12 in Metro front electrical shelf.
When installed in slots 1-4 or 9-12 of optical, packet-optical, or Metro front
electrical shelves, only the eight SFP ports on each circuit pack are
supported (ports 9 to 24 are blocked).
ATTENTION
The 240G+/80G VT1.5/VC-12 (240/80) cross-connect circuit packs
(NTK557GAE5/NTK557GS) do not support VT1.5/VC11 or VT2/VC12 traffic
on 24x10/100BT EPL circuit packs.
ATTENTION
In a 14-slot packet-optical shelf (NTK503SA), this circuit pack supports HO
and LO_VC3 connections when using X-Conn 240G+ STS-1/VC-3 (240/0)
(NTK557ES) or X-Conn 240G+/80G VT1.5/VC-12 circuit pack (240/80)
(NTK557GS) circuit packs (VT1.5/VC11 and VT2/VC12 connections are not
supported).
ATTENTION
• In a 32-slot shelf type, the 24x10/100BT EPL with 8xSFP circuit packs can
be installed in slots 1-8, 11-18, 21-28, and 31-38 when the shelf is
equipped with 640G+ STS-1/VC-3 (640/0) (NTK610BBE5) cross-connect
circuit packs.
ATTENTION
• The 24x10/100BT EPL with 8xSFP circuit pack is not supported in a 2-slot
or 7-slot shelf type (NTK503PAE5 or NTK503KA).


this release.
• The 24x10/100BT EPL or 24x10/100BT EPL with 8xSFP circuit packs
cannot be cross-connected to OCn/STMn or GE ports of a SuperMux
circuit pack using the shelf cross-connect (in “XC” Equipment Mode).
Engineering rules
For more information about 24x10/100BT EPL engineering rules, refer to 6500
specifications for the 24x10/100BT EPL optical interface circuit packs.
Table 1-7
Technical specifications for 24x10/100BT EPL optical interface circuit packs
Parameter 24x10/100BT EPL 24x10/100BT EPL with

(NTK548BAE5) 8xSFP (NTK548MAE5)
Weight (estimated) 0.7 kg (1.5 lb) 0.8 kg (1.8 lb)
Power consumption Typical (W): 35 (Note 1, Typical (W): 39 (Note 1,
Note 3, and Note 4) Note 3, and Note 4)
Power Budget (W): 35 Power Budget (W): 39
(Note 2, Note 3, and Note 4) (Note 2, Note 3, and
Note 4)
can be used as the equipment heat dissipation when calculating facilities thermal loads (an estimate
of the long term heat release of the item in a system).
Note 4: For this circuit pack that must be equipped with SFP, the power values published in this table
do not include SFP power values. You must add 1 W to typical or power budget values per SFP.
Note 5: For optical SFP specifications, see chapter 3 of Pluggable Datasheets and Reference, 323-
1851-180.

Latency

FLEX MOTR circuit pack (NTK531YAE5)

Overview
The Flex MOTR 8xSFP, 2xXFP circuit pack (also known as FLEX MOTR) uses
up to eight SFP optics for the FLEX interfaces and up to two XFP optics for
10GE LAN or OTM2 interfaces from the circuit pack faceplate to provide client
service aggregation over 2x10GE lines and the line capacity depends on the
latency parameter of the FLEX facility (point-to-point service transport of eight
client SFP ports to 10G XFP OTU Line). The FLEX uses a flexible facility
concept where there is a common facility type (FLEX) that has a protocol
attribute to indicate what facility it can support. The intent is to provide a
flexible client that can carry a wide variety of protocols. The supported
protocols will be described later on in this section. Figure 1-13 shows the
faceplate of a FLEX MOTR circuit pack. Figure 1-14 on page 1-38 provides
functional block diagram of the FLEX MOTR circuit pack.
Figure 1-13
FLEX MOTR circuit pack faceplate
Red triangle (Fail)

Flex MOTR
2xXFP/8xSFP
Fail
Ready
In Use
1

2
3 Tx
Rx
4 Tx
Rx
5 Tx
Rx
6 Tx
Rx
7 Tx
Rx - Used to communicate Rx Loss of Signal/optical module fail
8 Tx
Rx
9 Tx
Rx
10 Tx
Rx
Hazard
level: Transmit/receive SFP dual LC connector
R99
EEEEE99999
S/N NT030MEE9999E
NTUD99EE
Type A

Figure 1-14
FLEX MOTR circuit pack block diagram (NTK531YAE5)
PHY OTN XFP 1

Mapper
OTN
PHY Mapper XFP 2
SFP 3
SFP 4
Mate
SFP 5
Backplane
Cross Point Flex Mapper

SFP 6
SFP 7
Mate
SFP 8
SFP 9
SFP 10
Processor Power
Sync Supply
Module
Legend
The FLEX MOTR circuit pack (NTK531YAE5) provides the following
functionality.
• pluggable line ports via XFP optics (ports 1 and 2):
— up to two 10G XFP-based line ports (ports 1 and 2) supporting 10GE
LAN (ETH10G) or OTM2 (10.7G, 11.05G and 11.09G) modes.
— offers multirate CWDM, DWDM, SR/SW, LR/LW, and ER/EW reach
— offers fixed C-band 100 GHz-compliant DWDM XFP line interfaces
(1528.77 nm to 1565.09 nm)
— offers tunable C-band 50 GHz-compliant DWDM XFP tunable line
interfaces (1528.38 nm to 1568.77 nm)
— supports up to 175 km reach (when the OTM2 line port is equipped
with the DWDM XFPs supported by the FLEX MOTR circuit packs
such as NTK588xxE5 or NTK589xxE6 or less reach when equipped
with NTK583AAE6, NTK583AB, or NTK587xxE5 XFPs)
— auto-detection of XFP modules, which are hot pluggable

— manual provisioning of XFP modules

— FEC provisionable to Off, SCFEC and RS8
Note: The RS8 FEC algorithm is also known as ITU-T G.709 RS-8. The
SCFEC FEC algorithm is also known as ITU-T G.975 I.4.
— facility loopback on 10GE and OTM2 line facilities

• pluggable client ports via SFP optics (ports 3 to 10):
— SONET/SDH monitored (with PMs and alarming) transparent clients
for these rates: OC3/STM1, OC12/STM4, and OC48/STM16 (note
that SONET/SDH protocols can only be provisioned on client ports 7
to 10)
— Fibre Channel (FC) clients: FC100/FICON, FC200/FICON Express,
and FC400/FICON Express 4G
— Ethernet clients: GbE (ETH, optical 1000Base-X, and electrical
1000BaseT)
— 8B10B clients: IBM ISC-3 Peer Mode (1Gbps and 2 Gbps) and
Generic 8B10B
— generic transparent clients (can carry any signal running at the
following data rates: 155.52, 200.00, 622.08, 1000.00, 1062.50,
1250.00, 2125.00, 2488.32 and 4250.00 Mbps)
— ESCON
— auto-detection of SFP modules, which are hot pluggable
— manual provisioning of SFP modules
— facility and terminal loopbacks on client facilities
ATTENTION
GE clients on FLEX MOTR circuit packs do not have auto negotiation
settings but will pass through the client service. If the delay of the devices
that connect to the client ports is low enough so as not to cause auto
negotiation timeouts, auto negotiation can be enabled on the connecting
devices. Otherwise, auto negotiation on the connecting devices must be
disabled. For GE clients, maximum transfer unit (MTU) is not configurable
and 9600 byte jumbo frames will pass through the client service.
• Supports E-LINE Ethernet Virtual Private Line (EVPL) service between a

client port and a line port:
— simplified provisioning model (i.e. no VCS/VCE provisioning required
by customer)
— full rate
— signal conditioning

• Protection support
— supports 1+1 OTN line protection
– The 1+1 protection is an intra-card (single-card) protection where
the two OTM2 line ports must be equipped on the same circuit
pack (no inter-card 1+1 line protection). Port 1 must be the working
port and port 2 must be the protection port.
– 1+1 TPT protection on client ports between two FLEX MOTR
circuit packs on a per client port basis
— supports protection exerciser
• Synchronization support
— can be shelf timed, internally timed using on-board Stratum 3 clock, or
line timed from an OTM2 line port. Also supports 10GE line sync with
Ethernet Sync messaging.
— no Shelf X-Conn circuit pack required when internally or line timed
ATTENTION
The synchronization topology requires planning to ensure that all circuit
packs involved in carrying traffic are traceable to a single synchronization
master. Otherwise traffic will be impacted.
• GCC0 and GCC1 on OTM2 line facility
The following restrictions on using a cross-connect circuit pack are applied

when deploying a FLEX MOTR circuit pack:
• does not use any cross-connect capacity and can be installed in shelves
equipped with or without cross-connect circuit packs.
• In a 14-slot shelf type, you cannot provision a FLEX MOTR circuit pack in
slot 7 or 8 if one of these slots already contains a cross-connect circuit
pack.
• In a 14-slot shelf type, you cannot provision a cross-connect circuit pack
in slot 7 or 8 if one of these slots already contains a FLEX MOTR circuit
pack (or any other broadband circuit pack).
• In a 14-slot shelf type, when the FLEX MOTR circuit packs are installed in
slot 7 or 8, only Broadband circuit packs or Photonic circuit packs can be
provisioned in the other interface slots (slots 1 to 6 and 9 to14), as PKT/
OTN or MSPP interface circuit packs require a cross-connect circuit pack.
See Part 1 of 6500 Planning, NTRN10EY (Chapter 3) for a full list of
supported Broadband and Photonic circuit packs.

The FLEX MOTR circuit pack only supports the 2WAY (Bidirectional) cross-
connection type.
The FLEX MOTR circuit pack only supports the EVPL cross-connection rate.
Supported SFPs/XFPs
Table 1-8 provides a list of the SFPs that are supported on the FLEX MOTR
circuit pack. Table 1-9 provides a list of the XFPs that are supported on the
FLEX MOTR circuit pack.

Table 1-8
Supported SFP modules for the FLEX MOTR circuit packs (NTK531YAE5)
Facilities (Note 1 and Note 2)
P155M OC-3/STM-1 SR-0 (multimode) 1310 nm SFP NTTP02AD

— FLEX (ETH, OC3/STM1 — OC-3/STM-1 (155.52Mb/s)
Note 3)
OC-3/STM-1 SR1/I1 1310 nm SFP NTTP02BF
— OC-3/STM-1 (155.52Mb/s)
OC-3/STM-1 IR1/S1.1 1310 nm SFP NTTP02CD

— OC-3/STM-1 (155.52Mb/s)
OC-3/STM-1 LR1/L1.1 1310 nm SFP NTTP02ED

— OC-3/STM-1 (155.52Mb/s)
OC-3/STM-1 LR2/L1.2 1550 nm SFP NTTP02FF

— OC-3/STM-1 (155.52Mb/s)
P622M OC-12/STM-4 LR1/L4.1 1310 nm SFP NTTP05EF

— FLEX (ETH, OC12/STM4 — OC-12/STM-4 (622.08Mb/s)
Note 3)
OC-12/STM-4 LR2/L4.2 1550 nm SFP NTTP05FF
— OC-12/STM-4 (622.08Mb/s)
P155622M OC-3/12/STM-1/4 SR1/I1.1_I4.1 1310 nm SFP NTTP04BF

— FLEX (ETH, OCn/STMn — OC-3/STM-1 (155.52Mb/s)
Note 3) — OC-12/STM-4 (622.08Mb/s)
OC-3/12/STM-1/4 IR1/S1.1_S4.1 1310 nm XCT NTTP04CDE6

Enhanced SFPs and NTTP04CF
— OC-3/STM-1 (155.52Mb/s)
— OC-12/STM-4 (622.08Mb/s)
P2G5 OC48/STM16 SR/IR/LR SFPs NTTP03BF,

— FLEX (ETH, OC48/STM16 — OC-48/STM-16 (2.48832 Gb/s) NTTP03CF,
Note 3) NTTP03EF,
NTTP03FF
OC-48/STM-16 DWDM SFPs NTK585xx where

— OC-48/STM-16 (2.48832 Gb/s) xx= see Note 4
PCWDMS 155M/622M/2.5G CWDM SFPs NTK590xH where

— FLEX (ETH, OCn/STMn — OC-3/STM-1 (155.52Mb/s) x= L, M, N, P, Q,
Note 3) R, S, T
— OC-12/STM-4 (622.08Mb/s)
— OC-48/STM-16 (2.48832 Gb/s)

Table 1-8
Supported SFP modules for the FLEX MOTR circuit packs (NTK531YAE5) (continued)

— FLEX (ETH) — 1000Base-X (1.25Gb/s)

— 1000Base-X (1.25Gb/s)
GE 1000-Base-BX 10-D Bidirectional- NTTP59BD

downstream, 1490 nm Tx, 10 km SFP
— 1000Base-X (1.25Gb/s)

— 1000Base-T (1.00Gb/s)

— FLEX (ETH) — FC-100/ IBM FICON (1.0625 Gb/s)
— 1000Base-X (1.25Gb/s)
GE/FC100 1000-BaseLX 1310 nm SFPs NTTP01CF

— FC-100/ IBM FICON (1.0625 Gb/s)
— 1000Base-X (1.25Gb/s)

— FC-100/ IBM FICON (1.0625 Gb/s) x= L, M, N, P, Q,
R, S, T
— 1000Base-X (1.25Gb/s)

— FC-100/ IBM FICON (1.0625 Gb/s) x= L, M, N, P, Q,
R, S, T)
— 1000Base-X (1.25Gb/s)

— FC-200/ IBM FICON Express (2.125 Gb/s)
— 1000Base-X (1.25Gb/s)

— FC-100/ IBM FICON (1.0625 Gb/s)
— 1000Base-X (1.25Gb/s)

Table 1-8
PFC400 FC100 MX/FC200 MX/FC400 MX 850 nm SFP NTTP11AF

— FC-400/ IBM FICON 4G (4.250Gb/s)
FC100 SM-L/FC200 SM-L/FC400 SM-M 1310 NTTP11BF

nm SFP
— FC-100/ IBM FICON (1.0625 Gb/s)
FC100 SM-L/FC200 SM-L/FC400 SM-L 1310 NTTP11CF

nm SFP
— FC-100/ IBM FICON (1.0625 Gb/s)

Table 1-8
PSFP Multi-rate 1310 nm, SMF SFP B-700-1036-001

— FLEX (ETH, OCn/STMn — OC-3/STM-1 (155.52Mb/s)
Note 3) — OC-12/STM-4 (622.08Mb/s)
— OC-48/STM-16 (2.48832Gb/s)
— FC-100/ IBM FICON (1.0625 Gb/s)
— IBM ISC-3 Peer Mode @ 1.0625 Gbps
— IBM ISC-3 Peer Mode @ 2.125 Gbps
— GEN8B10B
— GENTRANSP
— 1000Base-X (1.25Gb/s)
Note: The SFP B-700-1036-001 with REV “A”
written on the faceplates is not supported in
6500. Only SFP B-700-1036-001 marked REV
“B” can be supported in 6500.
200 Mbps ESCON, 1310 nm SFP, MMF, 2 km B-730-0003-001

(Note 5)
— ESCON (200 Mbps)
— GEN8B10B
— GENTRANSP
Note 1: On the FLEX MOTR circuit packs, ports 1 and 2 are the line interface ports (10GE LAN, or
OTM2 (at 10.7G, 11.05G or 11.09G) and ports 3 to 10 are the client interface ports (FLEX).
Note 2: The facilities in brackets are facilities auto-created on the same port as the main facility or
Note 3: the OCn/STMn facility is auto-created in addition to the ETH facility if the OCn/STMn protocol
is selected when the FLEX facility is provisioned.
Note 4: Refer to Planning - Ordering Information, 323-1851-151, Chapter 3: Table “OC-48/STM-16
DWDM small form-factor (SFP) pluggable modules”, for the complete list of ordering codes.

Table 1-9
Supported XFP modules for the FLEX MOTR circuit packs (NTK531YAE5)
Pluggable Equipment Supported XFP modules and rates Part Number

and Facilities (Note 1)
P10GEL 10GBASE-SR/SW, 850 nm, 30-300 m, MMF XFP (Note NTTP81AA

— ETH10G 2)
— 10.3125 Gb/s 10GBaseR (10GE)
10G-Base-LR/LW (1310nm, SMF, 10km), 0-70C XFP NTTP81BA

— 10.3125 Gb/s 10GBaseR (10GE)

— 10.3125 Gb/s 10GBaseR (10GE)
P10GSEL OC192/STM64 SR-1 / I-64.1 / 10GBase-LR,LW XFP NTTP80BA

— ETH10G — 10.3125 Gb/s 10GBaseR (10GE)
OC192/STM64 IR-2 / S-64.2 / 10GBase-ER,EW XFP NTTP80DA

— 10.3125 Gb/s 10GBaseR (10GE)

Table 1-9
Supported XFP modules for the FLEX MOTR circuit packs (NTK531YAE5) (continued)


— OTM2 (ADJ), ETH10G 10GBase-LR,LW
(WAN Note 3) — 10.709 Gb/s OTU2
— 10.3125 Gb/s 10GBaseR (10GE)
9.95G-11.09G multirate, 1550 nm, SMF, 40 km XFP NTTP84AAE6

— 10.709 Gb/s OTU2
— 11.05 Gb/s OTU1e/11.09 Gb/s OTU2e
— 10.3125 Gb/s 10GBaseR (10GE)
OC192/STM64 SR-1/ I-64.1 / 10GBase-LR,LW / OTU2 NTTP84BA

/ 10G FC1200 XFP
— 10.709 Gb/s OTU2
— 10.3125 Gb/s 10GBaseR (10GE)
Multirate 15xx.yy nm EML DWDM 1600 ps/nm XFP NTK587Ax to

— 10.709 Gb/s OTU2 NTK587Dx,
where x= see
— 11.05 Gb/s OTU1e/11.09 Gb/s OTU2e Note 4
— 10.3125 Gb/s 10GBaseR (10GE)
9.95G-11.09G multirate, 1550 nm, SMF, 80 km XFP NTTP81KAE6

— 10.709 Gb/s OTU2
— 10.3125 Gb/s 10GBaseR (10GE)
Multirate LongHaul ITU CWDM XFP NTTP84Hx,

— 10.709 Gb/s OTU2 where x= A, B, C,
D, E, F, G, or H
— 10.3125 Gb/s 10GBaseR (10GE)

Table 1-9
Supported XFP modules for the FLEX MOTR circuit packs (NTK531YAE5) (continued)

PXFP Multirate 15xx.yy nm EML DWDM 800 ps/nm XFP NTK587Ex to

— OTM2 (ADJ), ETH10G — 10.709 Gb/s OTU2 NTK587Hx,
(WAN Note 3) where x= see
— 11.05 Gb/s OTU1e/11.09 Gb/s OTU2e Note 4
Multirate 15xx.yy nm DWDM 3200 ps/nm XFP NTK588xx,

— 10.709 Gb/s OTU2 where xx= see
Note 5
Multirate 1528.38 nm to 1568.77 nm (1-88) 50GHz NTK583AAE6

Tunable DWDM XFP
— 10.709 Gb/s OTU2
Multirate 1528.38 nm to 1568.77 nm (1-88) 50GHz NTK583AB

Tunable Type 2 DWDM XFP
— 10.709 Gb/s OTU2
Multirate 15xx.yy – 15xx.yy Tunable Dispersion Tolerant NTK589xxE6

DWDM 3200 ps/nm XFP where xx= see
— 10.709 Gb/s OTU2 Note 4
Note 1: On the FLEX MOTR circuit packs, ports 1 and 2 are the line interface ports (10GE LAN, or
OTM2 (at 10.7G, 11.05G or 11.09G) and ports 3 to 10 are the client interface ports (FLEX).
Note 3: The WAN facility is auto-created only when the packet mapping of the ETH10G facility is set to
“10.7G - GFP/OPU2 (Standard MAC transparent)”.
Note 4: Refer to Planning - Ordering Information, 323-1851-151, Chapter 3: Table “Multirate DWDM/
CWDM pluggable optics modules (XFP)”, for the complete list of ordering codes.
Note 5: Refer to Planning - Ordering Information, 323-1851-151, Chapter 7: Table “Multirate DWDM
pluggable optics modules (XFP) (manufacture discontinued)”, for the complete list of ordering codes.

The FLEX MOTR circuit pack supports the following monitored entities:
• OTM2 line interface
— PM collection for OTU2 layer
— PM collection for ODU2 layer
— PM collection of protection switch count/duration for ODU2 layer
— PM collection for Physical layer
• Client interfaces
— PM collection of SONET section (S)/SDH regenerator section (RS)
and SONET line (L)/SDH multiplex section (MS) for OC-n/STM-n
facilities
— PM collection for ETH, ETH10G, FLEX, and WAN facilities
— operational measurements for ETH, ETH10G, and WAN facilities

520.
Alarms
Equipment alarms
• Database Not Recovered for Slot
• Timing Generation Entry to Freerun
• Timing Generation Entry to Holdover
• Timing Generation Failure To Lock

Pluggable alarms
OTM facility alarms

• Loss of Signal
• Loss of Frame
• Pre-FEC Signal Fail
• Pre-FEC Signal Degrade
• Rx Power Out of Range
• OTU Trace Identifier Mismatch
• OTU Signal Degrade
• OTU BDI
• ODU AIS
• ODU LCK
• ODU OCI
• ODU Trace Identifier Mismatch
• ODU BDI
• OPU AIS
• OPU Payload Type Mismatch
• GCC0 Link Fail
• GCC1 Link Fail
• GCC0 OSPF Adjacency Loss
• Loopback Active – Facility
• Protection Scheme Mismatch
• Protection Mode Mismatch
• Protection Switch Byte Fail
• Auto Protection Switch Acknowledge Time Out

• Protection Exerciser Failed

• Protection Switch Complete – Revertive
• Protection Switch Complete
• Lockout Active
• Far End Protection Line Fail
• Tx Manual Provisioning required
• Tx Tuning in Progress
OCn/STMn facility alarms
• Loss of Frame
• AIS
• Trace Identifier Mismatch
• Signal Fail
• Signal Degrade
• RFI
Ethernet 10GE alarms
• Link Down
• Loss of Signal
• Signal Degrade
• Local Fault
• Remote Fault
Flex Facility alarms

• Loss of Signal
• Loss of Clock
• Loss of Lock
• Loss of Service Delineation

• Network Trace Identifier Mismatch

• Fibre Channel Link Not Operational
• Remote Defect Indication
• Loopback Active – Terminal
• Remote Port OOS
• Remote Port Unreachable
• Protection Channel Match Fail
• Protection Exerciser Failed
• Protection Switch Complete - Revertive
• Lockout Active
• Far End Protection Line Fail
WAN alarms
• Link Down
• Loss of Frame Delineation
• Signal Degrade
Photonic alarms
• Adjacency Mismatch
• Duplicate Adjacency Discovered
Common alarms
• Timing Distribution Loss Of Reference - n Ref (n=1 to 2)

• Timing Distribution Forced Switch - n Ref (n=1 to 2)

• Timing Distribution Lockout - n Ref (n=1 to 2)
• Timing Generation Loss Of Reference - n Ref - Major (n=1 to 2)
• Timing Generation Loss Of Reference - n Ref - Minor (n=1 to 2)
• Timing Generation Forced Switch - n Ref (n=1 to 2)
• Timing Generation Lockout - n Ref (n=1 to 2)
Equipping rules
The following equipping rules apply to FLEX MOTR circuit packs:
• is a single 10-port slot interface.
• can be equipped in any slot (1-14 except slots 7 and 8 if cross-connect
circuit packs are provisioned in slots 7 and/or 8) of the 14-slot packet-
optical, optical, converged optical, optical/front electrical, converged
optical/front electrical, optical/rear electrical, converged optical/rear
electrical shelves. Slots 7 and 8 of a 14-slot packet-optical shelf
(NTK503SA) cannot be equipped with this circuit pack.
ATTENTION
The FLEX MOTR circuit packs are not supported in the Metro front electrical
shelf.
• can be equipped in slots 1-8, 11-18, 21-28, and 31-38 of the 32-slot
packet-optical shelf.
• can be equipped in slots 1 to 7 of the 7-slot optical shelf (NTK503PAE5 or
NTK503KA).
• can be equipped in slots 1 to 6 of the 6500-7 packet-optical shelf
(NTK503RA).
• can be equipped in slots 1 and 2 of the 2-slot shelf.
• 14 FLEX MOTR circuit packs per 14-slot shelf (full-filled) are supported
regardless of the type of power input cards used (2x50A, 40A, or 60A).
Engineering rules
For more information about FLEX MOTR engineering rules, refer to 6500
The following table lists the weight, power consumption, and SFP/XFP
specifications for the FLEX MOTR optical interface circuit packs.

Table 1-10
Technical specifications for FLEX MOTR optical interface circuit packs
Parameter FLEX MOTR (NTK531YAE5)

can be used as the equipment heat dissipation when calculating facilities thermal loads (an estimate
of the long term heat release of the item in a system).
Note 4: For this circuit pack that must be equipped with SFPs and XFPs, the power values published
in this table do not include SFPs and XFPs power values. You must add:
— 1 W to typical or power budget values per SFP.
— 2 W to typical power value and 3 W to power budget for each XFP module with reach less than IR-
2/S-64.2b.
— 3 W to typical power value and 4 W to power budget for each XFP module with IR-2/S-64.2b reach
or greater.
Note 5: For optical SFP specifications, chapter 3 of Pluggable Datasheets and Reference, 323-1851-
180.
Note 6: For optical XFP specifications, see chapter 2 of Pluggable Datasheets and Reference, 323-
1851-180.
Latency

4xGE EPL, 1x10GE EPL, 24x10/100 BT EPL, and FLEX MOTR

provisioning procedures
The following flowcharts provide the various steps/procedures that must be
performed in order to have the 4xGE EPL, 1x10GE EPL, 24x10/100 BT EPL,
and FLEX MOTR circuit packs ready to carry traffic.
4xGE EPL
6500 4xGE EPL

Provisioning Diagram
Start
Install 4xGE EPL circuit pack and

pluggable(s) using “Provisioning a
circuit pack automatically” and
“Provisioning a pluggable
automatically” procedures
Fiber client ports using

“Routing fiber-optic cables onto the
6500 shelf” and “Connecting or
disconnecting fiber-optic cables to or
from circuit packs” procedures
Add the ETH facility as out-of-service

using “Adding a facility to an
equipment” procedure
Edit ETH facility parameters using

“Editing facility parameters” procedure
Virtual
Edit the WAN facility to VCAT
concatenation Yes
enable using “Editing facility
(VCAT)
parameters” procedure
required?
No
Edit other WAN parameters as

required using “Editing facility
Edit the ETH facility in-service using

“Changing the primary state of a
facility” procedure
Path Provision optical VCAT or

connections to Yes CCAT cross-connection(s)
be provisioned? using “Adding a path
connection” procedure
Note: For control plane
provisioning procedures, refer to No
Configuration – Control Plane,
323-851-330. End

1x10GE EPL
6500 1x10GE EPL

Start
Install 1x10GE EPL circuit pack and

pluggable(s) using “Provisioning a
circuit pack automatically” and
“Provisioning a pluggable
automatically” procedures
Fiber client ports using

Edit the ETH10G facility out-of-service

using “Changing the primary state of a
Edit ETH10G facility parameters using

“Editing facility parameters” procedure
Virtual
Edit ETH10G WAN facility to
concatenation Yes
VCAT enable using “Editing
(VCAT)
facility parameters” procedure
required?
No
Edit other ETH10G WAN parameters

as required using “Editing facility
Edit the ETH10G facility in-service

using “Changing the primary state of a
Path Provision optical VCAT or

connections to Yes CCAT cross-connection(s)
be provisioned? using “Adding a path
connection” procedure
323-851-330. End

24x10/100BT EPL
6500 24x10/100BT EPL

Start
Install 24x10/100BT EPL circuit pack using

“Provisioning a circuit pack automatically” procedure
Electrical Install 48x10/100BT I/O panel(s) as

10/100BT Yes required using “Installing I/O panels in
services the 14-slot 6500 shelf” procedure
required?
No Route category 5e cables to I/O panel

using “Routing Category 5e cables into
the electrical interface area” procedure
Fast
Ethernet Yes Install PFE SFPs using “Provisioning a
services pluggable automatically” procedure
required?
No Fiber client ports using

Add the ETH100 facilities as
out-of-service and edit
parameters as needed using
“Adding a facility to an
equipment” procedure
Virtual
concatenation Yes Edit the ETH100 WAN facility to VCAT
(VCAT) enable using “Editing facility
required? parameters” procedure
No
Edit other ETH100 WAN parameters as required

using “Editing facility parameters” procedure
Edit the ETH100 facility in-service using

“Changing the primary state of a facility” procedure
Path Provision optical VCAT or CCAT

connections to Yes cross-connection(s) using “Adding a
be provisioned? path connection” procedure

323-851-330. End

FLEX MOTR

Provisioning rules summary for the FLEX MOTR circuit packs

• Port 1 and port 2 can be provisioned as OTM2 (10.7G, 11.05G, 11.09G)
or native ETH10G. When configuring an OTM2 facility, you must also
configure an ETH10G NNI facility on the same port. Otherwise, no
Ethernet traffic can enter or exit these ports.
• Port 1 and port 2 are line ports only. FLEX MOTR only support NNI
ETH10G facilities.
• Ports from port 3 to port 10 are the client ports.
• Changing the primary state of the OTM2 facility automatically changes the
primary state of the associated ETH10G and/or WAN facility if the
ETH10G and/or WAN facility exists.
The following table provides references to different procedures covered in this

section.
For protection switching information and procedures, refer to Configuration -

Protection Switching, 323-1851-315.
Table 1-11
Procedures in this section
Topic
Procedure 1-1, “Provisioning a circuit pack automatically”
Procedure 1-2, “Provisioning a pluggable automatically”
Procedure 1-3, “Installing I/O panels in the 14-slot 6500 shelf”
Procedure 1-4, “Routing Category 5e cables into the electrical interface area”
Procedure 1-5, “Routing fiber-optic cables onto the 6500 shelf”
Procedure 1-6, “Connecting or disconnecting fiber-optic cables to or from circuit packs”
Procedure 1-7, “Adding a facility to an equipment”
Procedure 1-8, “Editing facility parameters”
Procedure 1-9, “Adding a path connection”
Procedure 1-10, “Adding an EVPL connection”
Procedure 1-11, “Provisioning the network element timing mode and references”
Procedure 1-12, “Changing the primary state of a facility”

Table 1-11
Topic
Procedure 1-13, “Changing the primary state of a circuit pack or pluggable”
Procedure 1-14, “Deleting a facility from an equipment”
Procedure 1-15, “Deleting a circuit pack or pluggable”

Procedure 1-1
Provisioning a circuit pack automatically
When automatic equipping is enabled, a circuit pack is automatically
provisioned when inserted in the shelf, along with any pluggables present.
To enable automatic equipping, refer to the “Enabling/disabling slot-based

automatic equipping” procedure in Administration and Security, 323-1851-
301.
See “Equipping rules” on page 1-10, “Equipping rules” on page 1-19,

“Equipping rules” on page 1-34, and “Equipping rules” on page 1-53 for
supported slots for 4xGE EPL, 1x10GE EPL, 24x10/100BT EPL, and
FLEX MOTR circuit packs. If a circuit pack is inserted in an unsupported slot,
an Autoprovisioning Mismatch alarm is raised.
CAUTION
Risk of equipment damage
Electrostatic discharge can damage electrostatic sensitive
devices. Use antistatic protection to avoid damaging circuit
packs.
Prerequisites
• To provision equipment for an empty equipment slot, ensure the last
equipment that occupied the slot and its related facilities and cross-
connects have been deleted.
• Ensure the plastic pin protector on the circuit pack has been removed.
• Ensure automatic equipping is enabled.
Step Action
1 Wear an appropriate ESD personal grounding device to dissipate

electrostatic charges. If you are wearing an antistatic wrist strap, connect the
cord on the shelf installed in a grounded rack/cabinet or clip to a suitable
ground point.
2 Insert the circuit pack in the correct slot in the shelf.
If you are logged in to Site Manager when you automatically provision a circuit
pack, click Refresh in the Equipment & Facility Provisioning application to
display the circuit pack in the list of available equipment.
—end—

Procedure 1-2
Provisioning a pluggable automatically
When automatic equipping is enabled, a pluggable is automatically
provisioned when inserted into the circuit pack port.
For the 24x10/100BT EPL circuit packs, the SFP equipment will not be
automatically provisioned if the corresponding I/O panel equipment is already
created. For manual provisioning instructions, refer to the “Provisioning a
circuit pack, module, or pluggable manually” procedure in Part 1 of
Configuration - Provisioning and Operating, 323-1851-310.

automatic equipping” procedure in Administration and Security, 323-1851-
301.
If a pluggable is inserted in an unsupported circuit pack and automatic

equipping is enabled, an Autoprovisioning Mismatch - Pluggable alarm is
raised.
CAUTION
packs.
Prerequisites
• Ensure the last pluggable that occupied the circuit pack port and its related
facilities and cross-connects have been deleted.
• Ensure the plastic pluggable port protector has been removed.
Step Action

ground point.
2 Insert the pluggable in the correct circuit pack port in the shelf.
—end—

Procedure 1-3
Installing I/O panels in the 14-slot 6500 shelf
Use this procedure to install electrical I/O hardware and 10/100Base-T panels
in a 6500 shelf, as follows:
• 48xDS3/E3/EC-1 I/O panels (optical/front electrical shelf, converged
optical/front electrical shelf, optical/rear electrical shelf, converged optical/
rear electrical shelf, or metro front electrical shelf)
• 48x10/100BT I/O panels (optical/front electrical shelf, converged optical/
front electrical shelf, optical/rear electrical shelf, converged optical/rear
electrical shelf, or metro front electrical shelf)
The interfaces described in this procedure are intended for intrabuilding use
only.
CAUTION
packs.
Step Action

ground point.
2 Select the equipment you are installing:
If you Then
are installing 48x10/100BT I/O panels, or Front I/O panel go to step 3
(Multi-Service) in the14-slot optical/front electrical or14-
slot converged optical/front electrical shelf
are installing go to step 23
48x10/100BT I/O panels in the14-slot optical/rear
electrical or14-slot converged optical/rear electrical shelf
are installing a 48x10/100BT I/O panel in the14-slot go to step 35
metro front electrical shelf
have installed all the electrical I/O hardware and I/O you have
panels as applicable to your configuration completed the
procedure

Procedure 1-3 (continued)

Step Action
Installing 48x10/100BT I/O panels (see Figure 1-16 on page 1-69), or Front I/O panel (Multi-Service)
in the14-slot optical/front electrical or 14-slot converged optical/front electrical shelf
3 In the electrical interface area, metal covers protect the electrical I/O section
of the backplane. Unfasten the thumbscrews that secure the covers.
4 Remove the covers for I/O slots 1-2, 3-4, 9-10, and 11-12 as required.
5 Unfasten the thumbscrew on the top left hand side of the drip tray.
6 While gripping the thumbscrew, pull the retractable pin on the right hand side,
pull the drip tray forward, down and out. Store the tray in a safe place.
You will install the drip tray back in step 22.
7 Open the Fibre Channel door by pulling the tabs on both sides.
8 Press the black button in the middle of the Fibre Channel to unlock the filter
tray. The front side of the filter tray unlocks and exposes the filter.
9 Lift and remove the filter and store it in a safe place.
You will install the filter back in step 21.
10 Look into the electrical interface area under the filter tray and locate the left
and right retractable pins at the bottom rear of the filter tray.
11 While pulling the retractable pins on each side, pull the filter tray forward,
down and out. Store the tray in a safe place.
You will install the filter tray back in step 21.
12 Remove the panel from its packaging.
13 Remove the cover on the connectors at the back of the panel.
14
CAUTION
Risk of connector damage
Exercise caution when you insert the panel into the
opening of the electrical interface area to avoid
damaging the backplane connector pins.
Hold the panel with two hands and insert it into the opening of the electrical
interface area at the bottom of the14-slot converged optical/front electrical
or14-slot converged optical/front electrical shelf until the panel passes the
tabs on the inside walls of the shelf (on which the air intake baffle sits).
15 Position the panel vertically so that the coarse guide pin bushing in the middle
of the panel engages the coarse middle guide pin.
16 Push the panel toward the backplane to engage the fine guide pins.


Step Action
17
CAUTION
Exercise caution when you engage the panel into the
backplane connector to avoid bending connector pins.
Lift the insertion/ejection bar and while keeping the bar lifted continue to
carefully slide the panel horizontally into the shelf until you engage the panel
into the backplane connector.
18 Press the insertion/ejection bar down to completely engage the panel into the
backplane. Do not push the bottom of the panel when you press the bar down.
19 Tighten the three fixing thumbscrews to secure the panel in place. Torque to
1 N-m (9 lb-in.).
20 Repeat step 12 to step 19 for the remaining panels, if required. Then go to
step 21.
21 Re-install the filter tray and the filter by performing step 7 to step 11 in the
reverse order. Make sure that the arrows on the outside edges of the filter that
indicate the direction of the air flow are pointing upwards.
22 Re-install the drip tray by performing step 5 to step 6 in the reverse order.
Then go to step 1.
Installing 48x10/100BT I/O panels in the 14-slot optical/rear or 14-slot converged optical/front
electrical shelf
23 To install I/O hardware in the14-slot optical/rear or14-slot converged optical/
front electrical shelf, you are working on the rear of the shelf. At the rear of the
shelf, metal covers protect the electrical I/O section of the backplane.
Unfasten the thumbscrews that secure the covers.
24 Remove the covers for I/O slots 1-2, 3-4, 9-10, 11-12, as required, and store
them for future use.
25 Remove the I/O panel from its packaging.
27 Carefully align the slot at the top of the panel in front of the tab at the back of
the shelf, and then slide the slot over the tab.
28 Make sure that the panel vertically aligned against the guide pins.
29 Push the panel towards the shelf until it engages the fine guide pins.


Step Action
30
CAUTION
Pull the insertion/ejection bar towards you and while keeping the bar pulled
carefully push the I/O panel horizontally along the guide pins until you engage
the module into the backplane connector.
31 Press the insertion/ejection bar to completely engage the panel into the
backplane.
1 Nm (9 lb-in.).
33 Repeat step 23 to step 32 for the remaining I/O panels, if required. Then go
to step 1.
Installing a 48x10/100BT I/O panel in the14-slot metro front electrical shelf
Removing the filter
34
CAUTION
Remove the filter before removing and inserting E1 I/O
modules to avoid damaging the filter.
Press the clips on both sides of the filter and slide the filter out. Store the filter
in a safe place, you will re-install it in step 46.
35 Select your next step.
If Then go to
you want to install a step 36
a 48x10/100BT I/O panel
you have installed all the required equipment go to step 46 to
re-install the filter
Installing a 48x10/100BT I/O panel in the14-slot metro front electrical shelf

36 In the electrical interface area, a metal cover protects the middle section of
the backplane, where you will install the panel. Unfasten the thumbscrews
that secure the cover.
37 Remove the cover.
38 Remove the panel from its packaging.


Step Action

40
CAUTION
Exercise caution when you insert the panel into the
opening of the electrical interface area to avoid
damaging the backplane connector pins.
Hold the panel with two hands and insert it into the opening of the electrical
interface area at the bottom of the14-slot Metro front electrical shelf.
41 Position the panel vertically so that the coarse guide pin bushing in the middle
of the panel engages the coarse middle guide pin.
42 Push the panel toward the backplane to engage the fine guide pins.
43
CAUTION
Lift the insertion/ejection bar and while keeping the bar lifted continue to
carefully slide the panel horizontally into the shelf until you engage the panel
into the backplane connector.
44 Press the insertion/ejection bar down to completely engage the panel into the
backplane. Do not push the bottom of the panel when you press the bar down.
1 N-m (9 lb-in.).
Re-installing the filter
46 Hold the filter such that the arrows on the outside edges of the filter that
indicate the direction of the air flow are pointing upwards.
47 Slide the filter back into the shelf. Press the filter all the way in. Then go to
step 1.
—end—

Figure 1-15
Removing and installing the drip tray and the filter tray (example shows an optical/front
electrical shelf)

Figure 1-16
Example of 48x10/100BT I/O panels installed in the electrical interface area of the
14-slot optical/front electrical shelf

Procedure 1-4
Routing Category 5e cables into the electrical
interface area
Use this procedure to route Category 5e (Cat 5e) cables into the electrical
interface area (area where installation of electrical hardware is supported).
For details, see the section on the electrical interface area in the “Shelf and
equipment descriptions” chapter in Part 1 of Planning, NTRN10EY. This
procedure does not apply to the optical shelf.
The interfaces described in this procedure are intended for intrabuilding use
only.
For cable routing to circuit pack faceplates, see Procedure 1-5, “Routing
fiber-optic cables onto the 6500 shelf”.
See the following illustrations for examples of the respective cable routing in
this procedure.
6500 shelf type
Shelf Optical/front Optical/ 14-slot 14-slot 14-slot, 7- 14-slot

electrical rear converged converged slot, or metro
electrical optical/front optical/ 32-slot front
electrical rear packet- electrical
electrical optical
Cable Cat 5e Applicable Applicable Applicable Applicable Not Applicable

type (Figure 1-17, applicable
Figure 1-18)
CAUTION
packs.


Routing Category 5e cables into the electrical interface area
Figure 1-17
Installing Cat 5e cables in the14-slot optical/front electrical shelf


Figure 1-18
Cat 5e cables routed from two optical/front electrical shelves (example shows the side view of an
ETSI rack)
Prerequisites
Make sure you have:
• a torque flathead screwdriver (to secure cable headshells in place)
• a mini-BNC insertion/removal tool (A00554187) to connect DS-3 cables
• STM-1e cables are single-ended. If required, you must cut the cables at
the required length and connectorize them with the connectors ordered
• the engineering documentation package (EDP), installation
documentation package (IDP), or equivalent site/network engineering
plans, which include the cable routing information for your configuration.


Guidelines
If you are installing multiple shelves and you are routing cables overhead, start
routing the cables from the bottom shelf up. If you are routing cables through
the floor, start from the top shelf down.
If you are routing cables for multiple I/O modules or panels, start with the
innermost module or panel and continue towards the side of the rack. For
each vertical pair of I/O modules, start by routing the cables from the bottom
module.
Make sure that at the front of the shelf the cables allow the shelf cover to close.
Step Action

ground point.
If the shelf cover is Then
installed on the area of the shelf you must access remove the shelf cover
not installed go to step 3

If you Then
are routing Cat 5e cables to the 14-slot optical/ go to step 4
front electrical or 14-slot converged optical/front
electrical shelf
are routing Cat 5e cables to the 14-slot optical/ go to step 6
rear electrical or 14-slot converged optical/rear
electrical shelf
have routed all the Cat 5e cables as applicable to you have completed the
your application procedure


Step Action
Routing Cat 5e cables to the 14-slot optical/front electrical shelf

4 Route the cable along the side of the rack and through the side cutout into the
electrical interface area of the shelf (see Figure 1-17 on page 1-71). If the
48x10/100BT I/O panel to which you are connecting is on the right hand side,
route the cable on the right hand side. If on the left, route on the left.
5 Repeat step 4 for all remaining Cat 5e cables you must route to the
14-slot optical/front electrical or 14-slot converged optical/front electrical
shelf. Then go to step 3.
Routing Cat 5e cables to the 14-slot optical/rear electrical or 14-slot converged optical/rear
electrical shelf
6 Route the Cat 5e cables along the side of the rack, inside the rack.
If you are connecting the cables to panel slots Then as you are facing
the rear of the shelf,
route and connect the
cable to the
1-2 and 3-4 right-hand side
9-10 and 11-12 left-hand side
8 Repeat step 6 and step 7 for all remaining Cat 5e cables that you must route
to the 14-slot optical/rear electrical shelf. Then go to step 3.
—end—

Procedure 1-5
Routing fiber-optic cables onto the 6500 shelf
Refer to the procedure on routing fiber-optical cables onto the 6500 shelf, in
the Installation technical publication specific to the respective 6500 shelf type.
—end—

Procedure 1-6
Connecting or disconnecting fiber-optic cables to or
from circuit packs
Refer to the procedure on connecting or disconnecting fiber-optic cables to or
from circuit packs, in the Installation technical publication specific to the
respective 6500 shelf type.
—end—

Procedure 1-7
Adding a facility to an equipment
Use this procedure to:
• add a facility that was manually deleted
• add a facility for a pluggable on which the facility is not auto-created
See Table 1-12 on page 1-78 for facilities that auto-provision and facilities that
must be manually provisioned.
Auto-provisioning of Ethernet facilities in 24x10/100BT EPL circuit packs is

only supported on 10/100BT ports associated with the SFP equipment
(ETH100-1 to ETH100-8 of a 24x10/100BT EPL circuit pack). Auto-
provisioning is not supported on 10/100BT ports associated with IO Panel
(ETH100-9 to ETH100-24 of a 24x10/100BT EPL circuit pack). Multiple add is
supported for ETH100 on 24x10/100BT equipment.
Prerequisites
To perform this procedure you must
• use an account with a level 3 or higher UPC
Step Action
1 Select the required network element in the navigation tree.

2 Select Equipment & Facility Provisioning from the Configuration drop-
down menu to open the Equipment & Facility Provisioning application.
3 Select the required shelf from the Shelf drop-down list.
4 In the Equipment area, select the pluggable that will support the facility.
5 Click Add in the Facility area to open the Add facility dialog box.
6 Select the required parameters from the drop-down lists. See the following for
facility attribute descriptions (note that read-only parameters are greyed out
or not displayed):
• “ETH, ETH100, and ETH10G facility parameters” on page 1-101
• “OTM2 facility parameters” on page 1-133
• “FLEX facility parameters” on page 1-135
7 Click OK to add the facility and close the Add facility dialog box.
—end—

Table 1-12
Facilities supported on 4xGE EPL, 1x10GE EPL, 24x10/100BT EPL and FLEX MOTR circuit packs
Circuit pack Facilities on the Pluggable Facilities on the pluggable

(Equipment) circuit pack equipment (Note 2)
• 4xGE SFP (GE) • none • PGEFC • ETH (WAN)

NTK535LA/LB
• PGE • ETH (WAN)
• PGEFC200 • ETH (WAN)
• 1x10GE EPL (XGE) • none • P10GSEL • ETH10G (WAN) (auto)

NTK533AAE5
• P10GEL • ETH10G (WAN) (auto)
• P10GSOEL • ETH10G (WAN) (auto)
• 24x10/100BT EPL • ETH100 (WAN) • N/A • N/A

(FE) NTK548BA
• 24x10/100BT EPL • ETH100 (WAN) • PFE • ETH100 (WAN)

with 8xSFP (FE)
NTK548MA
• FLEXMOTR 8xSFP • none • PGE (Note 6) • FLEX (ETH)

2x10G XFP
(FLEXMOTR) • PGEFC • FLEX (ETH)
(Note 5) (Note 6)
NTK531YAE5 • PGEFC200 • FLEX (ETH)
(Note 6)
• PFC400 • FLEX (ETH)

(Note 6)
• P155M (Note 6) • FLEX (ETH, OC3/STM1 Note 3)
• P622M (Note 6) • FLEX (ETH, OC12/STM4 Note 3)
• P155622M • FLEX (ETH, OCn/STMn Note 3)

(Note 6)
• P2G5 (Note 6) • FLEX (ETH, OC48/STM16 Note 3)
• PCWDMS • FLEX (ETH, OCn/STMn Note 3)

(Note 6)
• P10GEL • ETH10G
• P10GSEL • ETH10G
• P10GSOEL • OTM2 (ADJ), ETH10G (WAN Note 4)
• PXFP • OTM2 (ADJ), ETH10G (WAN Note 4)
• PSFP (Note 6) • FLEX (ETH, OCn/STMn Note 3)

Table 1-12
Facilities supported on 4xGE EPL, 1x10GE EPL, 24x10/100BT EPL and FLEX MOTR circuit packs

Note 1: Refer to Table 1-2 on page 1-8, Table 1-4 on page 1-17, Table 1-6 on page 1-31, Table 1-8 on
page 1-42 and Table 1-9 on page 1-46 for supported pluggable modules on the 4xGE EPL, 1x10GE
EPL, 24x10/100BT EPL, and FLEX MOTR circuit packs.
Note 3: The OCn/STMn facility is auto-created in addition to the ETH facility if the OCn/STMn protocol
is selected when the FLEX facility is provisioned.
Note 4: The WAN facility is auto-created only when the packet mapping of the ETH10G facility is set
to “10.7G - GFP/OPU2 (Standard MAC transparent).
Note 5: On FLEXMOTR, P10GEL, P10GSEL, P10GSOEL, and PXFP are supported on line ports (port
1 and port 2). All other pluggable types are supported on the client ports (port 3 to port 10).
Note 6: See Table 1-13 on page 1-80 for FLEX protocol support per pluggable type.

Table 1-13
Flex protocol support per pluggable type
Circuit pack Pluggable Supported protocols

equipment
FLEX MOTR • PGE 1000BASEX (except NTTP61AAE6),

1000BASET(NTTP61AAE6 only), GEN8B10B, GENTRANSP
• PGEFC 1000BASEX, FC100/FICON (NTTP01AF/CF only), GEN8B10B,

GENTRANSP
• PGEFC200 1000BASEX, FC100/FICON, FC200/FICONEXPRESS,

GEN8B10B, GENTRANSP
On NTTP06CF only: ISC3P1G, ISC3P2G
• PFC400 FC100/FICON, FC200/FICONEXPRESS, FC400/FICON4G,

GEN8B10B, GENTRANSP
• P155M OC3/STM1, GEN8B10B, GENTRANSP
• P622M OC12/STM4, GEN8B10B, GENTRANSP
• P155622M OC3/STM1, OC12/STM4, GEN8B10B, GENTRANSP
• P2G5 OC48/STM16, GEN8B10B, GENTRANSP
• PCWDMS OC3/STM1, OC12/STM4, OC48/STM16, GEN8B10B,

GENTRANSP
• PSFP B-700-1036-001 supports OC3/STM1, OC12/STM4, OC48/

STM16, FC100/FICON, FC200/FICONEXPRESS, ISC3P1G,
ISC3P2G, 1000BASEX, GEN8B10B, and GENTRANSP
B-730-0003-001 supports ESCON, GEN8B10B, and
GENTRANSP

Procedure 1-8
Editing facility parameters
Use this procedure to edit the facility parameters for a facility.
Prerequisites
To perform this procedure, you must
• use an account with a level 3 or higher UPC.
• make sure the ETH, ETH100, ETH10G, or WAN facility is out-of-service.
See Procedure 1-12, “Changing the primary state of a facility”.
Step Action

4 In the Equipment area of the Equipment & Facility Provisioning application,
select the pluggable whose facilities you want to edit.
5 Select the appropriate facility from the Facility Type drop-down list.
6 In the Facility area, select the facility you want to edit.
7 Click Edit in the Facility area to open the Edit Facility dialog box.
8 Select the required parameters from the drop-down lists.
See the following for facility attribute descriptions (note that read-only
parameters are greyed out or not displayed):
• “WAN facility parameters” on page 1-121
• “FLEX facility parameters” on page 1-135
• “ADJ facility parameters” on page 1-138
9 Click OK.
10 Put the facility back in-service (IS) if required. See Procedure 1-12,
“Changing the primary state of a facility”.
—end—

Procedure 1-9
Adding a path connection
Use this procedure to add a 1WAY, 1WAYPR, 2WAY, or 2WAYPR path
connection to a network element for 4xGE EPL, 1x10GE EPL, and 24x10/
100BT EPL circuit packs. To create EVPL connections on FLEX MOTR circuit
packs, use Procedure 1-10, “Adding an EVPL connection”.
Note: This is a generic procedure to enter a path connection using the

circuit packs listed above. For detailed information on each connection
type, recommendations for use of connection types for support of a
particular network configuration, and example networks, refer to "Path
connections management" in Part 1 of Configuration - Bandwidth and
Data Services, 323-1851-320.
This procedure does not apply to unidirectional connections (1WAY and

1WAYPR) for WAN facilities on 1x10GE EPL and 10/100BT EPL circuit packs.
Note: If you encounter a "Backplane bandwidth is fragmented" error

message during this procedure, refer to the “Backplane bandwidth
fragmentation” and “Backplane Bandwidth Query toolset” sections in Part
1 of Configuration - Bandwidth and Data Services, 323-1851-320.
Prerequisites
To perform this procedure, you must:
• ensure that Virtual concatenation is set to Enabled on the WAN port if
you require virtual concatenation. If virtual concatenation is required, in
drop nodes in Ethernet drop-and-continue applications, ensure that you
set virtual concatenation to Enabled: Grouped for 4xGE circuit packs.
Refer to Procedure 1-8, “Editing facility parameters” for information on
how to edit facility parameters.


Step Action

2 Select Cross Connections: Path Connections from the Configuration
menu.
3 If this is the initial launch of the Path Connections application, no path
connections appear until you perform a Retrieve. Subsequent launches of
the Path Connections application display path connections based on the last
filter criteria.
4 Click Add to display the Add Cross-Connect dialog box.
5 If you Then go to
want to provision a Connection ID step 6
do not want to provision a Connection ID step 8
6 Click once in the Connection ID text field.

7 Type the connection identifier.
Refer to Table 1-26 on page 1-141 for supported options.
8 From the Rate drop-down list, select a signal rate.
Refer to Table 1-26 on page 1-141 for supported connection rates.
Note 1: If VCAT is disabled on the WAN facility on a 4xGE EPL circuit pack,
then STS-12c/VC-4-4c and STS-24c/VC-4-8c are the only supported rates.
VCAT can be enabled or disabled on the WAN facility on the 4xGE EPL circuit
pack for other supported rates on the 4xGE EPL circuit pack (STS1/VC3 or
STS3c/VC-4). Refer to Part 1 of Configuration - Provisioning and Operating,
323-1851-310 to check the VCAT state. Refer to Procedure 1-8, “Editing
facility parameters” on how to change the VCAT state.
Note 2: If VCAT is enabled on the WAN facility on a 1x10GE EPL circuit pack,
then STS-3c/VC-4 is the only supported rate. If VCAT is disabled on the WAN
facility on a 1x10GE EPL circuit pack, then STS-192c/VC-4-64c is the only
supported rate. Refer to Part 1 of Configuration - Provisioning and Operating,
323-1851-310 on how to check the VCAT state. Refer to Procedure 1-8,
“Editing facility parameters” on how to change the VCAT state.
9 From the Type drop-down list, select a connection type.
Refer to Table 1-27 on page 1-142 for supported connection types.


Step Action
10 Select the required equipment, facility, and payload parameters from the
drop-down lists for each of the following panels:
• From
• To
• Switch Mate (applicable to 1WAYPR and 2WAYPR connections only)
Refer to Table 1-28 on page 1-142 for equipment and facility parameters for
path connections.
Site Manager automatically populates the available parameter fields after you
select the Rate and Type.
Note: For a VCAT connection, ensure ALL members of a VCAT group are
uniquely connected to a WAN port and there is no duplicated VCAT member.
For more information about VCAT and VCAT engineering rules refer to 6500
UPSR/SNCP is not supported on 10/100BT endpoints. When you provision
2WAYPR connections, you must set the 10/100BT endpoints for 10/
100BT EPL circuit packs as the To endpoint and not the From endpoint.
When you use a given pair of From Switch Mate endpoints of a 1WAYPR
connection in multicast connections, you must ensure that if WAN endpoints
are the To endpoints, all WAN endpoints are different. You cannot use the
same WAN endpoint as a destination of multicast connections used from the
same pair of source endpoints. For example:
Connection 1: 1WAYPR
From: slot 1, port 2, channel 3
Switch Mate: slot 4, port 5, channel 6
To: slot 7, port 8, channel 9
Connection 2: 1WAYPR
From: slot 1, port 2, channel 3
Switch Mate: slot 4, port 5, channel 6
To: slot n, port n, channel n, where n represents any slot, port, and
channel number not already used in connection 1 or 2 if you want to use
a WAN endpoint as the To endpoint.
11 Click Advanced in the From panel to open the Multi-Channel Selector
dialog box.


Step Action
12 In the Multi-Channel Selector dialog box, under Available, select the

required channels for the path connections.
To select multiple channels, select the first channel and then:
• Hold down the Ctrl key while individually clicking once on each of the
remaining channels.
• Hold down the Shift key and select the last channel required in the list.
• Select Ctrl_A (the Ctrl and A keys together) to select all channels.
The path connections depend on the order of selection.

Multiple channels are only available for GE, 10/100BT, and 10GE facilities if
virtual concatenation is enabled (refer to Procedure 1-8, “Editing facility
parameters” for information on how to edit facility parameters).
13 Click the arrow pointing to the right (->).
14 Perform step 12 and step 13 for each remaining channel to be in the path
connections.
15 When all the channels you require are under the Selected column, click OK.
16 Repeat step 11 to step 15 for the To, Switch Mate (applicable to 1WAYPR
and 2WAYPR, and 2WAYDPR connections only) panels.
When selecting multiple channels, you must select the same number of
channels in each of the From, To, and Switch Mate (if applicable) panels.
17 If you want to enter this connection and Then click
provision additional connections Apply
return to the main cross connect screen OK (Apply & Close)
If you are adding a single path connection, the path connection is added. If
the path connection cannot be added, an error message appears. Go to step
18.
If you are adding multiple path connections, the Multiple Cross Connect
Add Confirmation dialog box appears. Check that the multiple path
connections are correct, and then click Yes. If the path connections cannot be
added, an error message appears.
18 If in step 17 you clicked Then
Apply go to step 5
OK (Apply & Close) the procedure is complete
—end—

Procedure 1-10
Adding an EVPL connection
Use this procedure to add a 2WAY EVPL connection to a network element for
FLEX MOTR circuit packs. To create path connections on 4xGE EPL, 1x10GE
EPL, and 24x10/100BT EPL circuit packs, use Procedure 1-9, “Adding a path
connection”.
Prerequisites
• have provisioned the equipment and facilities required for the planned
EVPL connections
Step Action

2 Select Cross Connections: EVPL Connections from the Configuration
menu.
If this is the initial launch of the EVPL Connections application, no EVPL
the EVPL Connections application display EVPL connections based on the
last filter criteria.
4 Type the Connection ID.
Refer to Table 1-29 on page 1-149 for the supported options.
5 Select a signal rate from the Rate drop-down list.
Refer to Table 1-29 on page 1-149 supported EVPL connection rates.
6 Select a connection type from the Type drop-down list.
Refer to Table 1-30 on page 1-149 for supported EVPL connection types.


Step Action
7 Select the required equipment and facility from the drop-down lists for each
of the following panels:
• From
• To
Note: The From and To endpoints must be on the same slot.
EVPL connections.
8 Type the virtual circuit segment identifier in the VCID (1-1048575) field.
Refer to Table 1-29 on page 1-149 for supported VCID values.
Note: The From and To endpoints must have the same VCID.
9 Type the service provider VLAN identifier in the SVID (1-4094) field.
Refer to Table 1-29 on page 1-149 for supported SVID values.
provision additional connections Apply and go to step 4
—end—

Procedure 1-11
Provisioning the network element timing mode and
references
Use this procedure to provision the timing generation (timing mode and
references) for the network element. The timing mode can be set to:
• internal timing—the shelf timing is derived from an internal clock on the
cross-connect circuit pack
• line timing—the shelf timing is derived from received OC-n/STM-n/STM1J/
STM4J signal
• external timing—the shelf timing is derived from the BITSIN/ESI ports
• mixed timing—the shelf timing is derived from OC-n/STM-n/STM1J/
STM4J ports or BITSIN/ESI ports
For line timing, external timing, and mixed timing, a hierarchy of up to four
reference sources can be provisioned. The timing generation selects the
source in the hierarchy with the highest derived quality level for the shelf
timing. If there is more than one source at the highest derived quality level, the
timing generation selects the highest priority source in the hierarchy from
references with the same derived quality level (first is the highest priority and
fourth is the lowest priority). To provision a timing source from an OC-n/STM-
n/STM1J/STM4J port, the reference source must be logically equipped.
If a reference source is selected as the active source, the reference source

cannot be deprovisioned (Source changed to None). To deprovision the active
source, you first must either perform a manual switch to another source or a
lockout on the active source.
If a reference source is not selected as the active source, it can be

deprovisioned (Source changed to None). It is recommended that you perform
a lockout of the reference source before deprovisioning it.
The internal timing source is provided by a SONET/SDH-compliant Stratum 3/

G.813 Option 1 free running clock (±4.6 ppm) produced within the network
element. Sources of line timing are OC-3/STM-1, OC-12/STM-4, OC-48/STM-
16, OC-192/STM-64, STM-1J, and STM-4J facilities.
If a FLEX MOTR circuit pack is provisioned in an independent timing group

with two timing references on the same circuit pack, provision the incoming
quality level of port 2 to be Stratum 3 (SONET) or SEC (SDH) so that the
active reference is port 1 by default.


Provisioning the network element timing mode and references
Prerequisites
• use an account with a level 3 UPC or higher
• have a network synchronization plan for the network element
Step Action

2 Select Synchronization from the Configuration drop-down menu to open
the Synchronization application.
4 If you want to provision Then go to
the timing mode and references of an independent timing step 5
group
otherwise step 6
5 Select the required Timing Group Name for the independent timing group for
which you wish to change the mode.
6 Select the Timing Generation tab.
7 Click Edit to open the Synchronization Edit dialog box.
8 Select Timing Mode & References from the Type drop-down list.
9 From the network synchronization plan, determine the timing mode required.
Select the required Timing mode radio button to set the timing mode for the
network element.
CAUTION
Risk of timing loops
To avoid timing loops, verify the clock source setting of
each network element in the network. An incorrect
clock source setting can cause a service outage.


Step Action
In case of provisioning an independent timing group, you can select only the
Line Timing and Internal Timing options. External or mixed timing modes
are not supported. If Line Timing is selected, you can choose up to two
references for this timing group. You must note that:
• all references must be chosen from valid facilities which are on the
equipment contained within the independent timing group
• at most, one reference per circuit pack
In general, the Timing mode radio buttons are disabled if both cross-connect
circuit packs are missing.
Except when changing the timing mode from line timing or external timing to
mixed timing, you must remove all references from the hierarchy (set the
references to None, see step 10) before changing the timing mode.
10 From the network synchronization plan, determine the references to be
provisioned. For each timing generation reference to be provisioned, select
the timing reference from the appropriate source drop-down list, leave all
other possible references as None. See Table 1-25 on page 1-140.
• Only one port of each multi-port circuit pack can be used as a timing
reference source.
• The available options from the source drop-down lists are dependent on
the selected timing mode. Only logically equipped sources are available
for selection.
• You cannot remove the active reference source from the hierarchy. To
remove the active source from the timing generation hierarchy, you first
must either perform a manual switch away from the active source or a
• If a reference source is not selected as the active source, it can be
removed from the timing generation hierarchy. It is recommended that
you perform a lockout of the reference source before removing it from the
timing generation hierarchy.
• E1, E3, DS3, EC-1, DS1DS3, E1DS3, E1E3, STM1E, GE, 10GE, 10/
100BT, L2SS, PDH gateway, and RPR facilities cannot be set as
synchronization source references.
• DS1 DSM facilities and OC-3 ports which are provisioned as DSM hosts
cannot be set as line synchronization source references.
11 Click OK.
12 Click Yes in the confirmation dialog box.


Step Action
13 If the Synchronization Protection application is open, click Refresh in the

Synchronization Protection application to update the application with the
changes you have made to the hierarchy.
Note: For the FLEX MOTR, once it is set to the line timing mode, the “Timing
Generation Loss of Reference - 1st Ref”, “Timing Generation Failure To
Lock”, “Timing Generation Entry to Holdover”, and “Timing Generation Entry
to Freerun” alarms can be present until at least one client to line connection
is provisioned at both the near end and the far end.
—end—

Procedure 1-12
Changing the primary state of a facility
Use this procedure to change the primary state of a facility.
CAUTION
Risk of service interruption
If you place a facility out-of-service, you can cause a loss of
traffic.
Note 1: After manually changing the primary state of an ETH, ETH10G

or ETH100 facility, the primary state of the corresponding WAN facility is
automatically changed to the same new primary state. In other words, to
change the primary state of the WAN facility, you must change the primary
state of the corresponding ETH, ETH10G, or ETH100 facility.
Note 2: For the FLEXMOTR circuit pack, if an OTM2 facility is provisioned
on the same line port as the ETH10G, the primary state of the ETH10G is
controlled through the OTM2.
The conditioning actions at the far end LAN link of taking the ETH facility out-
of-service depend on the setting of the Conditioning type parameter. The far
end ETH facility (if on a 6500 network element) will turn off the laser if the near
end ETH facility is taken out-of-service (if Conditioning type is set to Enable
on the near end ETH facility). See Table 1-20 on page 1-101.
Prerequisites
To perform this procedure you must use an account with a level 3 or higher
UPC.
Step Action



Step Action

select the pluggable whose facility state you want to change.
5 Select the facility from the Facility Type drop-down list.
6 In the Facility area, select the facility whose state you want to change.
7 Click Edit in the Facility area to open the Edit facility dialog box.
8 Select OOS or IS from the Primary state drop-down list.
CAUTION
If you place a facility out-of-service, you can cause a
loss of traffic.
9 Click OK.
10 If changing the primary state to OOS, click Yes in the warning dialog box.
—end—

Procedure 1-13
Changing the primary state of a circuit pack or
pluggable
Use this procedure to change the primary state of a circuit pack or pluggable
to in-service or out-of-service. You cannot change the primary state of a
pluggable to in-service if the associated circuit pack is out-of-service.
You must change the primary state of any related facilities to out-of-service
before changing the primary state of a circuit pack or pluggable to out-of-
service, see Procedure 1-12, “Changing the primary state of a facility”.
Changing the primary state of a circuit pack automatically changes the

primary state of any provisioned pluggables on that circuit pack to the same
state.
Prerequisites
To perform this procedure, you must use an account with a level 3 or higher
UPC.
Step Action

4 If you are changing the primary state to Then go to
OOS step 5
IS step 6
5 Ensure any related facilities are out-of-service. See Procedure 1-12,

6 Select the circuit pack or pluggable in the Equipment area.
7 Click Edit in the Equipment area to open the Edit Equipment dialog box.
8 Select IS or OOS from the Primary state drop-down list and click OK.
9 If you are changing the primary state to OOS, click Yes in the warning dialog
box.
—end—

Procedure 1-14
Deleting a facility from an equipment
Use this procedure to delete a facility.
CAUTION
If you delete a facility, you can cause a loss of traffic.
Facilities that are auto-created (facilities in brackets in Table 1-12 on page

1-78) when the main facility is created will be auto-deleted when the main
facility is deleted.
Prerequisites
• ensure the end-to-end service to be deleted is not carrying traffic
• ensure the facility to be deleted is out-of-service and is not in maintenance
state
• delete the sub-network connection if provisioned on this facility. Refer to
the “Deleting a sub-network connection” procedure in Configuration -
Control Plane, 323-1851-330.
• delete the connections of the entire path that terminates on this facility.
Refer to the “Deleting path connections” and “Deleting EVPL connections”
procedures in Part 1 of Configuration - Bandwidth and Data Services, 323-
1851-320.
• delete the IISIS circuit or OSPF circuit and then the GCC link if provisioned
on the OTM2 facility to be deleted. Refer to the “Deleting an entry in the
communications settings” procedure in Part 1 of Configuration -
Provisioning and Operating, 323-1851-310.
• ensure that no loopback exists on the facility. Refer to the “Operating/
releasing a loopback” procedure in Part 1 of Configuration - Provisioning
and Operating, 323-1851-310 to release a loopback if it exists.
• ensure the facility to be deleted is not in a protection group


Step Action

select the pluggable whose facilities you want to delete.
6 In the Facility area, select the facility you want to delete.
7 Click Delete in the Facility area.
8 Click Yes in the warning dialog box.
—end—

Procedure 1-15
Deleting a circuit pack or pluggable
Use this procedure to delete a circuit pack or pluggable equipment from the
list of provisioned equipment in the Equipment and Facility Provisioning
application. Deleting a circuit pack automatically deletes any provisioned
pluggables on that circuit pack.
Prerequisites
• delete all facilities on the circuit pack and its associate pluggables, see
Procedure 1-14, “Deleting a facility from an equipment”.
• put the circuit pack or pluggable to be deleted out-of-service, see
Procedure 1-13, “Changing the primary state of a circuit pack or
pluggable”.
Step Action

4 In the Equipment area, select the equipment (circuit pack or pluggable) you
want to delete.
5 Click Delete in the Equipment area.
—end—

Equipment and facility provisioning parameters

Equipment and facility primary and secondary states
The table that follows provides information on equipment and facility primary
states.
Table 1-14
Equipment and facility primary states
Primary State Description

IS In-service; no failure detected
IS-ANR In-service - abnormal; failure exists but entity is still capable of performing
some of its provisioned functions (that is partial failure)
OOS-AU Out-of-service - autonomous; failure detected
OOS-MA Out-of-service - maintenance; no failure detected (OOS for maintenance
for provisioning memory administration)
OOS-AUMA Out-of-service autonomous maintenance; failure detected
OOS-MAANR Out-of-service - maintenance - abnormal; partial failure detected
The table that follows provides information on equipment secondary states.
Table 1-15
Equipment secondary states
Secondary State Description

Active Equipment has connections established to at least one of the facilities it
supports and the connected facilities are in-service
Fault detected Equipment failure detected
Idle No connections established to facilities supported on this equipment, all
connected facilities are out-of-service, or in-service connected facilities are
not on the active traffic path in a protected connection
Mismatched eqp. attribute Mismatched or unknown equipment detected in a provisioned slot
Supporting entity outage Supporting equipment has a failure (applicable to pluggables when
associated circuit pack is missing or has failed or is mismatched)
Unequipped Equipment is missing
Unknown Equipment cannot be identified

The table that follows provides information on facility secondary states.
Table 1-16
Facility secondary states

<null> Active, working state for UPSR/SNCP facility.
Disconnected Facility has no connections established.
Fault detected Facility failure detected
Supporting entity Supporting equipment (SFP/XFP or circuit pack):
outage • has a failure, or
• is missing, or
• is mismatched, or
• has an associated connection which is failed.
Loopback active Loopback (facility, terminal, or EFM remote) active on facility
Maintenance State Maintenance State is enabled. When in Maintenance State, a facility continues to
carry traffic if it can, but does not raise alarms, SNMP traps or Performance
Monitoring Threshold Crossing Alerts (PM TCAs).
Applies to facilities that support maintenance state. See Table 1-18. Maintenance
state is applicable to these facilities only if they are in out-of-service state.
Auto in-service AINS is enabled. Applies to facilities that support AINS. See Table 1-17.
The table that follows provides information on facilities that support AINS.
Table 1-17
Facilities that support Automatic In-Service (AINS)
Equipment Facility type Default value Note

FLEXMOTR OTM2 Disabled
FLEX Enabled
XGE ETH10G Enabled child facility (Note): WAN, STSn
GE ETH Enabled child facility (Note): WAN, STSn
FE ETH100 Enabled child facility (Note): WAN, STSn, VTn
Note: The child facility follows the AINS state of its parent facility.

The table that follows provides information on facilities that support the
maintenance state.
Table 1-18
Facilities that support maintenance state
Equipment Facility type Note

XGE ETH10G child facility (Note): WAN, STSn
GE ETH child facility (Note): WAN, STSn
FE ETH100 child facility (Note): WAN, STSn, VTn
Note: The child facility follows the Maintenance state of its parent facility.
OCn layer facility parameters

The table that follows provides information on OCn layer facility parameters.
Table 1-19
OCn layer facility parameters
Parameters Options Description
Unit facility-shelf-slot-port Displays the facility AID. Read-only.
Primary state See “Equipment and The primary state of the OCn layer facility follows the
facility primary states” parent FLEX facility. Read-only.
on page 1-98
Secondary State See “Facility Displays the facility operational state. Read-only.
secondary states” on
page 1-99
Signal degrade numeric value Displays the signal degrade threshold. Read-only.
threshold
Signal failed numeric value Displays the signal failed threshold. Read-only.
threshold
Port Mode • SONET (default for Displays the port mode of the facility (SONET or SDH).
SONET mode) Read-only.
• SDH (default for
SDH mode)
Customer Defined string of up to 64 Used to identify a provisioned facility. It is the same as

Facility Identifier characters the Common Language Facility Identifier (CLFI). The
provisioned value appears in the facility alarm report if
the SP2, SPAP, SPAP-2 w/2xOSC, or the 2-slot
integrated SP is equipped.

ETH, ETH100, and ETH10G facility parameters

The table that follows provides information on ETH, ETH100, and ETH10G
facility parameters.
Table 1-20
Parameter Options Description
GE ETH
Primary state See “Equipment and Sets the primary state of the facility. Default reflects
facility primary states” on primary state of associated equipment.
page 1-98 Note: IS and OOS are selectable.
Secondary state See “Facility secondary Indicates the operational state of the facility. The
states” on page 1-99 secondary state can be a combination of one or more
states. The Auto in-service state and Maintenance state
are editable.
Control frame • 4: P2P Tunnel (default) Associates a control frame profile index to a specified
profile • 5: EFM + P2P Tunnel LAN port. The predefined profiles identify the control
frame processing behavior for each control frame
protocol.
Note 1: You must disable the auto-negotiation before
setting or editing the control frame profile to 5: EFM +
P2P Tunnel (to enable the EFM).
Note 2: Refer to 6500 Packet-Optical Platform Data
Application Guide, NTRN15BA for more information
about control frame profile.
This parameter can be edited only when the ETH facility
is out-of-service.
Auto negotiation • Enable (default) Controls auto-negotiation with the local Ethernet link
• Disable partner. This parameter can be edited only when the ETH
facility is out-of-service.
Note: EFM only works properly when the
auto-negotiation is disabled.
Auto-negotiation • Unknown Identifies the auto-negotiation status of the Ethernet

status • In progress facility.
• Completed When the negotiation status is in progress, the system

keeps trying to complete the auto-negotiation
• Disabled successfully. Read-only.

Table 1-20
ETH, ETH100, and ETH10G facility parameters (continued)
Pass control • Enable Determines if received Ethernet control frames are

• Disable (default) discarded (disable) or passed through transparently
(enable).
is out-of-service.
Maximum • 1600 (default) Sets the maximum transfer unit (MTU).

Ethernet frame • 9600 This parameter can be edited only when the ETH facility
size is out-of-service.
Inter-Packet • DEFAULT (default) Sets the Inter-Packet Gap, a minimum idle period
Gap • 10 between transmission of Ethernet frames. This
parameter can be edited only when the ETH/ETH100
• 11 facility is out-of-service. When configured as DEFAULT,
• 12 the circuit pack retains the current IPG behavior.
Applicable for 24x10/100BT EPL (NTK548BA), 24x10/
100BT EPL with 8xSFP (NTK548MA), 4xGE EPL
(NTK535LAE5), 4xGE EPL (NTK535LBE5), and 4xGE
EPL (NTK535LJE5).

Table 1-20
Conditioning • Enable (default) Controls Ethernet conditioning.

Type • Disable When Conditioning Type is Enable, the transmit signal of
the ETH port shuts down when any of the following
occurs:
• there are client signal failures received from the far-end
• there is a link down condition on the corresponding
WAN port
• the corresponding WAN port receives client signal
failures
• there are no cross-connects on the corresponding WAN
port
In addition:
• client signal failures received from the far-end cause
ingress frames at the ETH port to be discarded and
egress frames on the WAN ports to be discarded.
• a link down condition on the ETH port triggers
transmission of client signal failures to the WAN port
• client signal failures from the WAN port trigger a Far End
Client Rx Signal Failure alarm
In the case of 1000BT, there is no Ethernet framing.
When Conditioning Type is Disable, the transmit signal of
the ETH port does not shutdown, if any of the conditions
listed above occurs. In addition, an ETH link down
condition does not trigger transmission of client signal
failures to the WAN port and client signal failure from the
WAN do not trigger a "Far End Client Rx Signal Failure"
alarm.
This parameter can be edited only when ETH facility is
out-of-service.

Table 1-20
Pause • Enable Controls the pause frame transmission.

transmission • Disable (default) If auto-negotiation is disabled, the pause transmission
override override attribute has no effect. If auto-negotiation is
enabled, setting pause transmission override to enable
causes the pause frame transmission to be determined
by the pause transmission attribute irrespective of the
flow control attribute and the auto-negotiation status. This
allows pause frame transmission control even if auto-
negotiation is enabled and the link partner does not
support flow control.
is out-of-service.
Pause • Enable (default) Explicitly controls the flow control towards the local
transmission • Disable device. This parameter can be edited only when the ETH
facility is out-of-service. Not applicable if auto-negotiation
is enabled.
Pause reception Enable Displays the pause receive override status which is used
override to override (disable) the negotiated receive pause if auto-
negotiation is enabled. Not applicable if auto-negotiation
is disabled. Read-only.
Pause reception Disable Displays the pause reception status which is used to
control the flow control towards the local device. Not
applicable if auto-negotiation is enabled. Read-only.
Advertised Full Indicates the type of advertised duplex operation by

duplex operation auto-negotiation. Read-only.
Advertised link 1000 Indicates the advertised (current) Ethernet speed

speed measured in Mbit/s. Read-only.
Advertised flow • Asymmetric (default) Sets the advertised Ethernet flow control capabilities.
control • None None to advertise flow control is not supported,
Asymmetric to advertise asymmetric flow control toward
• Symmetric the link partner is supported, Symmetric to advertise
symmetric flow control or asymmetric flow control toward
the local device is supported. This parameter can be
edited only when the ETH facility is out-of-service. Not
applicable if auto-negotiation is disabled.

Table 1-20
Rx idle • 1 seconds Sets hold-off time (in seconds) on Rx Ethernet idle

• 2 seconds condition. “Disabled” indicates that the detection is
disabled.
• 3 seconds
• 4 seconds is out-of-service.
• 5 seconds
• 10 seconds
• 60 seconds
• 120 seconds
• 300 seconds
• Disabled (default)
Negotiated • Full Displays the negotiated duplex mode of the port when
duplex operation • Unknown auto-negotiation is enabled. Read-only.
Negotiated • 1000 Displays the negotiated speed of the port in Mbit/s when
speed • Unknown auto-negotiation is enabled. Read-only.
Negotiated • Disable Displays the negotiated pause transmission status for

pause • Unknown transmissions when auto-negotiation is enabled.
transmission Read-only.
Negotiated • Disable Displays the negotiated pause receive status for

pause reception • Unknown receptions when auto-negotiation is enabled. Read-only.
Link partner • Full Indicates the type of advertised duplex operation of the
advertised • Unknown link partner. Link partner is the peer Ethernet MAC layer
duplex operation at the far end of an Ethernet link. Read-only.
Link partner • 1000 Indicates the advertised (current) Ethernet speed of the
advertised • Unknown link partner in Mbit/s. Read-only.
speed
Link partner • Unknown Indicates the advertised Ethernet flow control capabilities
advertised flow • Asymmetric of the link partner. Read-only.
control
• None
• Symmetric
MAC address • ** ** ** ** ** ** Identifies the MAC address of Ethernet port set at

• Unknown manufacturing time. Read-only.

Table 1-20
Customer string of up to 64 Used to identify a provisioned facility. It is the same as the

Defined Facility characters Common Language Facility Identifier (CLFI). The
Identifier provisioned value appears in the facility alarm report if the
SP2 is equipped.
FLEXMOTR ETH
Primary state See “Equipment and Displays the primary state of the facility, which inherits
facility primary states” on the primary state of the associated FLEX facility.
page 1-98 Read-only.
states. Read-only.
Maximum • 174 Displays the maximum transfer unit (MTU). Depending

Ethernet Frame • 462 on the Latency Optimization setting of the associated
Size FLEX facility. Read-only.
• 1470
Destination • ** ** ** ** ** ** Sets the destination MAC address. Can be any valid

Address • 010075ABCDEF(default) unicast or multicast MAC address.
MAC Address • ** ** ** ** ** ** Identifies the local MAC address. Read-only.

• Unknown
Untagged • Critical-Green (-Yellow)Tx and Rx service class used for the service. PBit and
receive class of • Network-Green (-Yellow) CFI used is dependent of the Tx and Rx class of service
service profile configuration on the ETH10G NNI port which is
• Premium-Green (- hard coded to profile 30.
Yellow)
• Platinum-Green (-Yellow)
• Gold-Green (-Yellow)
• Silver-Green (-Yellow)
• Bronze-Green (-Yellow)
• Standard-Green (-
Yellow)

SP2, SPAP, SPAP-2 w/2xOSC, or the 2-slot integrated
SP is equipped.

Table 1-20
10/100BT ETH100
states. The Auto in-service state is editable. The
Maintenance state is editable.
Control frame • 4: P2P Tunnel (default) Associates a control frame profile index to a specified
profile • 5: EFM + P2P Tunnel LAN port. The predefined profiles identify the control
protocol.
Note: Refer to 6500 Packet-Optical Platform Data
is out-of-service.
• Disable partner. This parameter can be edited only when the
ETH100 facility is out-of-service. This parameter can be
edited only when you select the FE equipment not the
PFE SFP module (equipment type must be IO Panel in
facility area).


Note: This parameter is not supported/shown if a PFE
SFP module is selected in equipment area (it means the
equipment type in facility area must be “IO Panel” to
support/show this parameter).
Pass control Disable Indicates that the received Ethernet control frames are
discarded (disable). Read-only.

Table 1-20
Maximum • 1600 (default) Sets the Maximum Transfer Unit (MTU).

Ethernet frame • 9216 This parameter can be edited only when the ETH100
size facility is out-of-service.
Inter-Packet • DEFAULT (default) Sets the Inter-Packet Gap, a minimum idle period
Gap • 10 between transmission of Ethernet frames. This
parameter can be edited only when the ETH/ETH100
• 11 facility is out-of-service. When configured as DEFAULT,
• 12 the circuit pack retains the current IPG behavior.
Applicable for 24x10/100BT EPL (NTK548BA), 24x10/
100BT EPL with 8xSFP (NTK548MA), 4xGE EPL
(NTK535LAE5), 4xGE EPL (NTK535LBE5), and 4xGE
EPL (NTK535LJE5).

Table 1-20

the ETH100 port shuts down when any of the following
occurs:
WAN port
failures
port
In addition:
ingress frames at the ETH100 port to be discarded and
• a link down condition on the ETH100 port triggers
In the case of 10/100BT, there is no Ethernet framing.
the ETH100 port does not shutdown, if any of the
conditions listed above occurs. In addition, an ETH100
link down condition does not trigger transmission of client
signal failures to the WAN port and client signal failure
from the WAN do not trigger a "Far End Client Rx Signal
Failure" alarm.
This parameter can be edited only when ETH100 facility
is out-of-service.
transmission • Disable device.
This parameter can be edited only when the ETH100
facility is out-of-service. Not applicable if auto-negotiation
is enabled.

Table 1-20
Pause • Enable Controls the pause frame transmission.

transmission • Disable (default) If auto-negotiation is disabled, the pause transmission
override override attribute has no effect. If auto-negotiation is
enabled, setting pause transmission override to enable
causes the pause frame transmission to be determined
by the pause transmission attribute irrespective of the
flow control attribute and the auto-negotiation status. This
allows pause frame transmission control even if auto-
negotiation is enabled and the link partner does not
support flow control.
Rx idle • 1 seconds Sets hold-off time (in seconds) on Rx Ethernet idle

• 2 seconds condition. “Disabled” indicates that the detection is
disabled.
• 3 seconds
• 4 seconds facility is out-of-service.
• 5 seconds
• 10 seconds
• 60 seconds
• 120 seconds
• 300 seconds
• Disabled (default)

Table 1-20
Advertised • Full (default) Sets the type of advertised duplex operation by auto-
duplex operation • Half negotiation.
• Both This parameter can be edited only when the ETH100

Note 1: You must make sure that the device connected
to the port has the same duplex setting.
Note 2: If auto-negotiation is disabled, the Both and Full
values are equivalent and mean Full.
Note 3: If the interface type is 100FX, the only accepted
value is Full.
Note 4: This parameter can be edited only when you
select the FE equipment not the PFE SFP module
(equipment type must be IO Panel in facility area).
Advertised link • 10 Sets the advertised (current) Ethernet speed in Mbit/s.

speed • 100 (default) This parameter can be edited only when the ETH100
• 10/100 facility is out-of-service.
Note 1: You must make sure that the device connected
to the port has the same speed.
Note 2: When the speed is 10/100, speed of 100 is
attempted but fall back to 10 is supported.
Note 3: If auto-negotiation disabled, 10/100 is equivalent
to 100.
Note 4: If the interface type is 100FX, the only accepted
speed is 100 (speed of 10 is denied and speed of 10/100
operates at 100).
Note 5: This parameter can be edited only when you
select the FE equipment not the PFE SFP module
(equipment type must be IO Panel in facility area).

Table 1-20
Advertised flow • Asymmetric (default) Sets the advertised Ethernet flow control capabilities.
control • None None to advertise flow control is not supported,
Asymmetric to advertise asymmetric flow control toward
• Symmetric the link partner is supported, Symmetric to advertise
symmetric flow control or asymmetric flow control toward
the local device is supported.
Not applicable if auto-negotiation is disabled.
duplex operation • Half auto-negotiation is enabled. Read-only.
• Both Note: This parameter is not supported/shown if a PFE

• Unknown

speed • 100 auto-negotiation is enabled. Read-only.
• 10/100 Note: This parameter is not supported/shown if a PFE

Negotiated • Enable Displays the negotiated pause transmission status for

pause • Disable transmissions when auto-negotiation is enabled.
• Unknown
Negotiated • Enable Displays the negotiated pause receive status for

pause reception • Disable receptions when auto-negotiation is enabled. Read-only.
• Unknown Note: This parameter is not supported/shown if a PFE


Table 1-20
advertised • Half link partner. Link partner is the peer Ethernet MAC layer
• Both

advertised • 100 link partner in Mbit/s. Read-only.
speed Note: This parameter is not supported/shown if a PFE
• 10/100
Link partner • Unknown Indicates the advertised Ethernet flow control capabilities
control Note: This parameter is not supported/shown if a PFE
• None
• Symmetric
• Both support/show this parameter).
MAC address ** ** ** ** ** ** Identifies the MAC address of Ethernet port set at

manufacturing time. Read-only.
Equipment type • Faceplate (default on Indicates the equipment type (due to provisionable
ETH100-1 to ETH100-8) support of both pluggable interfaces and 10/100BT
• IO Panel (default on interfaces on a subset of the LAN ports).
ETH100-9 to ETH100- Not-editable (to change the equipment type, the user
24) must delete the ETH100 facility and re-create the
ETH100 facility with the new equipment type).
Note: Ethernet facilities associated with the IO Panel
must be provisioned manually. However, provisioning of
SFP equipment will result in automatically provisioning
the associated Ethernet facility (if it does not already
exist). The IO Panel will be treated as Inventory only (not
Equipment).

SP2 is equipped.

Table 1-20
10GE ETH10G
Secondary State See “Facility secondary Indicates the operational state of the facility. The
states. The Auto in-service state is editable. The
Maintenance state is editable.
Auto negotiation Disable Indicates auto-negotiation with the local Ethernet link
partner. Read-only.
Auto-negotiation Disabled Identifies the auto-negotiation status of the Ethernet

status facility. Read-only.
Pass control Disable Indicates that received Ethernet control frames are
discarded (disable). Read-only.
Maximum • 1600 (default) Sets the maximum Transfer Unit (MTU).

Ethernet frame • 9018 This parameter can be edited only when the ETH10G
size facility is out-of-service.

Table 1-20

the ETH10G port shuts down when any of the following
occurs:
WAN port
failures
port
In addition:
ingress frames at the ETH10G port to be discarded and
• a link down condition on the ETH10G port triggers
the ETH10G port does not shutdown, if any of the
conditions listed above occurs. In addition, an ETH10G
link down condition does not trigger transmission of client
signal failures to the WAN port and client signal failure
from the WAN do not trigger a "Far End Client Rx Signal
Failure" alarm.
This parameter can be edited only when ETH10G facility
is out-of-service.
transmission • Disable device. This parameter can be edited only when the
ETH10G facility is out-of-service.
negotiation is enabled. Read-only.
Pause Disable Indicates the pause frame transmission.

transmission If auto-negotiation is disabled, the pause transmission
override override attribute has no effect. Read-only.

Table 1-20
Rx idle Disabled Indicates hold-off time (in seconds) on Rx Ethernet idle

condition. “Disabled” indicates that the detection is
disabled. Read-only.

Advertised link 10G Indicates the advertised (current) Ethernet speed

Advertised flow Asymmetric Indicates the advertised Ethernet flow control

control capabilities. Asymmetric to advertise asymmetric flow
control toward the link partner is supported. Read-only.
Link partner Unknown Indicates the type of advertised duplex operation of the
advertised link partner. Link partner is the peer Ethernet MAC layer
Link partner Unknown Indicates the advertised (current) Ethernet speed of the
advertised link partner in Mbit/s. Read-only.
speed
Link partner Unknown Indicates the advertised Ethernet flow control capabilities
advertised flow of the link partner. Read-only.
control
Negotiated Unknown Displays the negotiated duplex mode of the port when
duplex operation auto-negotiation is enabled. Read-only.
Negotiated Unknown Displays the negotiated speed of the port in Mbit/s when
speed auto-negotiation is enabled. Read-only.
Negotiated Unknown Displays the negotiated pause transmission status for

pause transmissions when auto-negotiation is enabled.
Negotiated Unknown Displays the negotiated pause receive status for

pause reception receptions when auto-negotiation is enabled. Read-only.

Equipment type ETH Displays the equipment type. Read-only.

Table 1-20

SP2 is equipped.
FLEXMOTR ETH10G
page 1-98 If an OTM2 facility is provisioned on the same line port as
the ETH10G, the primary state of the ETH10G is
controlled through the OTM2.
Note: IS and OOS are selectable.
states. Read-only.
Auto negotiation Disable Controls auto-negotiation with the local Ethernet link
partner. Read-only.
Port conditioning Disable Displays that port conditioning is disabled. Read-only.
Maximum • 1522 Sets the maximum transfer unit (MTU). Received frames
Ethernet frame • 1600 (default) which are larger than the MTU are discarded and counted
size as FRTOOLONGS.
• 9100
• 9216
• 9600
Packet mapping • None Displays the LAN to OTU2 mapping format. Packet
• 10.7G - GFP/OPU2 mapping depends on the OTM2 rate.
(Standard MAC
transparent)
• 11.05G - OPU1e (PCS
transparent)
• 11.09G - OPU2e (PCS
transparent)
Advertised Full Indicates the type of advertised duplex operation by auto-

duplex operation negotiation. Read-only.
Advertised link 10000 Indicates the advertised (current) Ethernet speed


Table 1-20
Advertised flow None Sets the advertised Ethernet flow control capabilities.
control None indicates that the advertise flow control is not
supported. Not applicable if auto-negotiation is disabled.
Read-only.
Pause • Enable Controls pause transmission when auto-negotiation is

transmission • Disable (default) disabled. Not applicable when auto-negotiation is
enabled.
Pause Disable Controls the pause frame transmission. Not applicable if

transmission auto-negotiation is disabled.
override
Pass Control Disable Determines whether the received Ethernet control frames
are passed through transparently (Enable) or removed
from the flow (Disable).

Interface type NNI Identifies the type of interface. Read-only.
Policing Disable (default) Provides rate adaptation between the full speed Ethernet
access ports and the user subscribed bandwidth.
Ether type (in • 8100 (default) Sets the encapsulation scheme (for example stacked
Hex) • 9100 VLAN) used to encapsulate customer frames.
• 88A8
Control frame • 1: Drop All Associates a control frame profile index to a specified
profile • 3: LAG + Drop Other (not LAN port. The predefined profiles identify the control
for GFP mapped frame processing behavior for each control frame
ETH10G) protocol.
• 7: LAG, SONMP+Drop Note: Refer to 6500 Packet-Optical Platform Data

(not for GFP mapped Application Guide, NTRN15BA for more information
ETH10G) about control frame profile.
• 8: SONMP + Drop Other

Table 1-20
Receive class of 30 (predefined) A receive class of service profile indicates how to map the
service profile priority bits and DE bits of the packets received to the
internal per hop behavior (IPHB). It maps the reception
Ethernet priority and CFI to a class of service.
Transmit Class 30 (predefined) A transmit class of service profile indicates how to map
of service profile the internal per hop behavior (IPHB) to the priority bits
and DE bits of the packets transmitted. It maps a
transmission class of service to an Ethernet priority and
CFI.
Untagged • Critical-Green (-Yellow) Class of service in the receive direction.

receive class of • Network-Green (-Yellow)
service
• Premium-Green (-
Yellow)
• Standard-Green (-
Yellow)
Port Bandwidth 0(predefined) Sets the port bandwidth profile to limit the port capacity.
Default is 0.
Queue Group 1 67,70 (predefined) A queue group specifies which scheduler profile, drop
profiles and multipliers to be used for creating a port.
Equipment type ETH Displays the equipment type.
Used As Timing • Yes Indicates whether the facility is chosen as a line timing
Reference • No reference or not. Read-only.
CBR BW numeric value Displays the constant bit rate (CBR) bandwidth remained
Remaining on the port. Maximum line port capacity is 10000.00 when
there is no CBR connection to the port. Read-only.
Latency • MAXIMUM Sets the buffer size on the ETH10G line, where
Optimization • MEDIUM (default) MAXIMUM= minimum buffer capacity, MEDIUM=
medium buffer capacity, and MINIMUM= maximum
• MINIMUM buffer capacity.
DUS Override • Disable (default) When enabled, the provisioned sync status quality level
• Enable will override an incoming DUS sync quality level.

Table 1-20
SSM Transmit • Disable When enabled, the ETH10G facility will transmit SSM
• EEC1 (default for SDH or sync quality level using Ethernet Sync Messaging
SDH-J) Channel (ESMC). When disabled, no ESMC packets will
be sent. Default depends on NE mode.
• EEC2 (default for
SONET)
Tx Actual Power numeric value Displays the measured transmit optical power.
(dBm) Read-only.
Rx Actual Power numeric value Displays the measured receive optical power. Read-only.
(dBm)

SP is equipped.

WAN facility parameters

The table that follows provides information on WAN facility parameters.
Table 1-21
GE WAN
Primary State See “Equipment and facility Indicates the primary state of the WAN facility.
primary states” on page 1-98 Read-only.
states” on page 1-99 secondary state can be a combination of one or
more states. Read-only.
Basic rate • None (default) Displays the basic rate of the WAN facility and is
• None, STS1/VC3, STS3c/ derived from the cross-connections assigned to
VC4, STS12c/VC4-4c, that WAN facility. Read-only.
STS24c/VC4-8c, STS48c/
VC4-16c (when VCAT is
disabled)
• None, STS1/VC3, STS3c/
VC4 (when VCAT is
enabled)
Packet mapping GFP-F Displays the LAN to SONET/SDH/SDH-J mapping

format. Read-only.

Table 1-21
WAN facility parameters (continued)
Virtual • Enable Enables/disables the virtual concatenation mode of

concatenation • Enable; Grouped the port. This parameter can only be edited if no
cross-connects are present on facility.
• Disable (default)
For virtual concatenation support, select Enable
unless network uses dual feed GE sources when
the ‘Enable; Grouped’ option should be selected
(causes all virtual concatenated connections to be
switched together).
• Enable
Enables the virtual concatenation mode of the port
• Enable; Grouped
Enables Group Switching (from dual sources)
• Disable
Disables the virtual concatenation mode of the port
This parameter can be edited only when the
corresponding ETH facility is out-of-service.
Link connectivity Disable Displays the status of the Link Control Monitor
monitor functionality (not supported for GFP-F mapping).
Read-only.
Link capacity Disable Displays the status of the link capacity adjustment
adjustment scheme scheme. Read-only.
Provisioned units • 0 or 1 when VCAT is Displays the number of provisioned bandwidth

disabled (default is 0) units (basic rate units) in the SONET/SDH/SDH-J
• 0 to 21 when VCAT is transmit direction and is derived from the
enabled and rate is STS1/ cross-connections assigned to the WAN facility.
VC3(HO) (default is 0) Read-only.
• 0 to 7 when VCAT is
enabled and rate is STS3C/
VC4 (default is 0)
Actual units • 0 or 1 when VCAT is Displays the actual number of bandwidth units
disabled (default is 0) (basic rate units) carrying traffic in the SONET/
• 0 to 21 when VCAT is SDH/SDH-J transmit direction and is derived from
enabled and rate is STS1/ the cross-connections assigned to the WAN facility
VC3(HO) (default is 0) and SONET/SDH/SDH-J failures. Read-only.
VC4 (default is 0)
• Unknown

Table 1-21
Provisioned • 0 or 1 when VCAT is Displays the number of provisioned bandwidth

reception units disabled units (basic rate units) in the SONET/SDH/SDH-J
• 0 to 21 when VCAT is received direction. Read-only.
enabled and rate is STS1/
VC3(HO)
enabled and rate is STS3c/
VC4
Actual reception • 0 or 1 when VCAT is Displays the number of actual bandwidth units
units disabled (basic rate units) in the SONET/SDH/SDH-J
• 0 to 21 when VCAT is received direction. Since LCAS is not supported in
enabled and rate is STS1/ this release, the actual reception units is either 0 or
VC3(HO) the same as provisioned reception units.
Read-only.
VC4
• Unknown
Conditioning type • GFP CMF (default) Controls the type of conditioning on the WAN port.
• Nil Trace WAN conditioning is triggered by local client
failures on the Ethernet port.
• None
Note: The ‘Unequipped; Nil Trace’ option can be
• Unequipped used when converting a network between using
• Unequipped; Nil Trace Unequipped and Nil Trace as a trigger.
GFP RFI • Enable (default) Controls the GFP remote failure indication (RFI)
• Disable (Used to set the client management frame (CMF) transmission.
default value for GFP RFI) When enabled, it allows GFP RFI CMF
transmission upon WAN link down. Default
• CMFCSF depends on the set up in Nodal Information
• User Defined application.
This is used to set the default value for GFPRFI.

Table 1-21
GFPRFI UPI 3 to 255 This value is transmitted when the WAN link is
Except 128, 129, and 130 down. The GFPRFI UPI is defaulted to the ETH
GFP RFI value.
Note: It is only editable if the GFP RFI parameter
is on User Defined option.
Magic number Disable Displays the status of the magic number used to
distinguish between two peers and detect error
conditions (not supported for GFP-F mapping).
Read-only.
LAN frame Enable Displays whether the LAN frame checksum is

checksum included in the encapsulated frame. For GFP-F,
status is always Enable. Read-only.
Frame checksum •0 Sets whether the GFP frame checksum is included

• 32 (default) in the frame. Checksum is not included if 0
selected, checksum included if 32 or 16 selected.
Payload scrambling Enable Displays the status of the X^43+1 payload

scrambler. Read-only.
Network control None Displays the network control protocol (None if

protocol mapping is GFP-F). Read-only.
Round Trip Delay • 0 to 220000 Displays the estimated time in microseconds for
(microseconds) • Unknown one packet to travel from one device to another and
back again. Dividing the delay by 2x4.897 gives an
approximation of the distance (in km) between the
two end points. This attribute can be unknown if the
delay is not calculated. Read-only.
For the 24x10/100BT EPL circuit pack
(NTK548BAE5), as Round Trip Delay is calculated
through software, it may divert with +/- 10% of the
actual value.
Round trip delay • Enable (default) Displays the status of round trip delay. Round trip
status • Disable delay is the time in microseconds for one packet to
travel from one device to another and back again.
Dividing the delay by 2x4.897 gives an
two end points.

Table 1-21
Current differential •0 Shows the current differential delay (in

delay • Unknown microseconds). A value of 0 is returned when
(microseconds) VCAT=DISABLE, or when there are no egress
connections (from backplane). A value of Unknown
is returned when there is a WAN link down
condition and VCAT=ENABLE and there is at least
one egress cross-connection. Read-only.
Maximum Unknown Shows the maximum differential delay taking into

differential delay account the cross-connect rate (in microseconds).
(microseconds) Read-only.
10GE WAN
Basic rate • None (default) Displays the basic rate of the WAN facility and is
• None, STS192c/VC4-64c derived from the cross-connections assigned to
(when VCAT is disabled) that WAN facility. Read-only.
• None, STS3c/VC4 (when

VCAT is enabled)
Packet mapping GFP-F Displays the LAN to SONET/SDH/SDH-J mapping

format. Read-only.

concatenation • Disable (default) the port. This parameters can only be edited if no
cross-connects present on facility.
corresponding ETH10G facility is out-of-service.
adjustment scheme scheme. Read-only.

Table 1-21
Provisioned units • 0 to 1 when VCAT is Displays the number of provisioned bandwidth

disabled and rate is units (basic rate units) in the SONET/SDH/SDH-J
STS192/VC4-4c-64 transmit direction and is derived from the cross-
(default is 0) connections assigned to the WAN facility.
• 0 to 64 when VCAT is Read-only.
VC4 (default is 0)
Provisioned • 0 to 1 when VCAT is Displays the number of provisioned bandwidth

reception units disabled units (basic rate units) in the SONET/SDH/SDH-J
VC4
Actual units • 0 to 1 when VCAT is Displays the actual number of bandwidth units
enabled and rate is STS3C/ the cross-connections assigned to the WAN facility
VC4 (default is 0) and SONET/SDH/SDH-J failures. Read-only.
• Unknown
Actual reception • 0 to 1 when VCAT is Displays the number of actual bandwidth units
enabled and rate is STS3c/ this release, the actual reception units is either 0 or
VC4 (default is 0) the same as provisioned reception units.
Read-only
• Unknown
Conditioning type • GFP CMF (default) Controls the type of conditioning on the WAN port,
• None WAN conditioning is triggered by local client
• Unequipped

Table 1-21
GFP RFI • Enable Controls the GFP remote failure indication (RFI)
• Disable client management frame (CMF) transmission
upon WAN link down.
• CMFCSF
• Disable - no CMF transmission (UPI = 0)
• User Defined
• Enable - GFP RFI CMF transmission (UPI = 128)
• CMFCSF - Client Signal Fail CMF transmission
(UPI = 2)
• User Defined - user defined value in the UPI code.
Default depends on the set up in Nodal Information
application.
Except 128, 129, and 130 down. The GFPRFI UPI is defaulted to the GFP
RFI value.
LAN frame Enable Displays whether the LAN frame checksum is

Frame Checksum •0 Sets whether the GFP frame checksum is included

selected, checksum included if 32 selected.
Payload Scrambling Enable Displays the status of the X^43+1 payload

Round trip Delay • 0 to 220000 Displays the estimated time in microseconds for
actual value.

Table 1-21
Round trip Delay • Enable Displays the status of round trip delay. Round trip
Status • Disable (default) delay is the time in microseconds for one packet to
travel from one device to another and back again.
Dividing the delay by 2x4.897 gives an
two end points.
Current Differential •0 Shows the current differential delay (in

Delay • Unknown microseconds). A value of 0 is returned when

Differential Delay account the cross-connect rate (in microseconds).
10/100BT WAN
Basic rate • None (default) Displays the SONET/SDH/SDH-J basic rate of the
• None, STS1/VC3, STS3c/ WAN facility and is derived from the cross-
VC4 (when VCAT is connections assigned to that WAN facility.
disabled) Read-only
• None, VT1.5/VC11, VT2/

VC12, STS1/VC3(when
VCAT is enabled)
Packet Mapping GFP-F Displays the LAN to SONET/SDH/SDH-J mapping

format. Read-only.

Table 1-21
Virtual • Enable (default) Enables/disables the virtual concatenation mode of

concatenation • Disable the port. This parameters can only be edited if no
corresponding ETH100 facility is out-of-service.
adjustment scheme scheme (LCAS). Read-only.

disabled (default is 0) units (basic rate units) in the SONET/SDH/SDH-J
• 0 to 61 when VCAT is transmit direction and is derived from the cross-
enabled and rate is VT1.5/ connections assigned to the WAN facility.
VC11 (default is 0) Read-only.
enabled and rate is VT2/
VC12 (default is 0)
VC3(LO) (default is 0)
• Unknown
enabled and rate is VT1.5/ the cross-connections assigned to the WAN facility
VC11 (default is 0) and SONET/SDH/SDH-J failures. Read-only.
VC12 (default is 0)
• Unknown

Table 1-21
Provisioned • 0 or 1 when VCAT is Displays the number of provisioned bandwidth

reception units disabled (default is 0) units (basic rate units) in the SONET/SDH/SDH-J
enabled and rate is VT1.5/
VC11 (default is 0)
VC12 (default is 0)
• Unknown
units disabled (default is 0) (basic rate units) in the SONET/SDH/SDH-J
enabled and rate is VT1.5/ this release, the actual reception units is either 0 or
VC11 (default is 0) the same as provisioned reception units.
Read-only.
VC12 (default is 0)
• Unknown
Conditioning type • GFP CMF (default) Controls the type of conditioning on the WAN port.
• Nil Trace WAN conditioning is triggered by local client
• None
Note: The ‘Unequipped; Nil Trace’ option can be
• Unequipped used when converting a network between using
• Unequipped; Nil Trace Unequipped and Nil Trace as a trigger.

Table 1-21
GFP RFI • Enable (default) Controls the GFP remote failure indication (RFI)
• Disable (Used to set the client management frame (CMF) transmission.
default value for GFP RFI) When enabled, it allows GFP RFI CMF
transmission upon WAN link down. Default
• CMFCSF depends on the set up in Nodal Information
• User Defined application.
This is used to set the default value for GFP RFI.
Except 128, 129, and 130 down. The GFPRFI UPI is defaulted to the ETH
GFP RFI value.
LAN Frame Enable Displays whether the LAN frame checksum is



Round trip delay • 0 to 220000 Displays the estimated time in microseconds for
actual value.
Round trip delay • Enable (default) Controls the support (sending of CMFs) of round
Status • Disable trip delay calculation.

Table 1-21


FLEXMOTR WAN
Primary State See “Equipment and facility Displays the primary state of the facility. Value
primary states” on page 1-98 reflects primary state of associated ETH10G
facility. Read-only.
Packet Mapping GFP-F Displays the WAN to OPU mapping format.

Read-only.
Frame Checksum •0 Sets whether the GFP-F frame checksum (4 Byte

• 32 (default) CRC-32) is appended to each GFP frame.
"32" adds the frame checksum while "0" does not.
LAN frame Disable Displays whether the LAN frame checksum is

status is always disable. Read-only.

Note: Where applicable, the Mapping, Frame checksum, and LAN frame checksum parameters must
always be edited as a group, invalid combinations are rejected.

OTM2 facility parameters

The table that follows provides information on OTM2 facility parameters.
Table 1-22
Parameter Options/ranges Description

Primary State See “Equipment and Sets the primary state of the facility. Default reflects
page 1-98 IS and OOS are selectable.
Secondary State See “Facility secondary Displays the facility operational state.
states” on page 1-99 The Auto in-service state is editable.
Rate • 10.7G Displays the facility rate.
• 11.05G
• 11.09G
Tx Actual Power • Tx optical power Displays the measured line transmit optical power.
(dBm) • Unknown (if circuit Read-only.
pack not present) When the outgoing transmit optical power level for the
monitored port is out of range, the Tx Actual Power
parameter displays "OOR". The corresponding OPT-
OCH/OCH-OPT value in the Site Manager
Performance Monitoring application does not display
"OOR" when out of range; the lowest reading is -45
dBm. Refer to Fault Management - Performance
Monitoring, 323-1851-520 for more information about
OPT-OCH/OCH-OPT values.
Tx SBS Dither • Off Sets the transmit Stimulated Brillouin Scattering (SBS)
• On dither setting. If On, a dither frequency applied to
transmitter to compensate for the non-linear effect of
Stimulated Brillouin Scattering. Normally Off in CPL
interworking systems and On in 1600G interworking
systems.
Tx Chirp • Positive Sets the chirp.
• Negative (default)
Tx FEC Format • Off Sets the transmit Tx FEC format setting.
• RS8 (ITU-T G.709 RS- RS8 and SCFEC are the OTU FEC modes applied to
8) (default) achieve greater margin on a given link.
• Super concatenated Off state allows users to test the product for OTN
FEC (ITU-T G.975 I.4) compliancy.
The OTM2 Tx FEC Format parameter cannot be edited
unless the facility is OOS.

Table 1-22
OTM2 facility parameters (continued)

Rx Actual Power • Rx optical power Displays the measured line receive optical power.
pack not present) When the incoming receive optical power level for the
monitored port is out of range, the Rx Actual Power
parameter displays "OOR". The corresponding OPR-
OCH/OCH-OPR value in the Site Manager
Performance Monitoring application does not display
"OOR" when out of range; the lowest reading is -45
dBm. Refer to Fault Management - Performance
OPR-OCH/OCH-OPR values.
The value may not be accurate if it is outside the normal
operating range.
Rx FEC Format • Off Select the receive Rx FEC format setting.
• RS8 (ITU-T G.709 RS- RS8 and SCFEC are the OTU FEC modes applied to
8) (default) achieve greater margin on a given link.
The OTM2 Rx FEC Format parameter cannot be edited
unless the facility is OOS.
Pre-FEC Signal Fail -1.00 to +1.00 dBQ Sets the threshold level for the Pre-FEC Signal Fail
Threshold (dBQ) (default 0) alarm (applicable only when FEC is On). Can be
provisioned in 0.01 steps. 0 dBQ equates to 1x10^-15
post FEC errors.
This parameter cannot be edited unless the facility is
OOS.
ODU TTI • Yes (default) Displays whether the trail trace identifier (TTI) message
Termination • No is transmitted at the line transmitter.
OTU Signal 1x10^-9 Displays the signal degrade threshold (applicable only
Degrade Threshold when Rx FEC Format is Off). Read-only.
Port Mode • SONET (default for Select the mode of the port. Determines if SONET or
SONET NE mode) SDH terminology is used and whether bit (SONET) or
• SDH (default for SDH block (SDH) errors are used for performance
NE mode) monitoring.
You cannot edit the port mode. To change the port
mode you must delete the OTM2 facility and then re-
add it with the correct port mode.

Table 1-22

Used As Timing • No Indicates whether the facility is used as a timing
Reference • Yes reference. Read-only.

FLEX facility parameters

The table that follows provides information on FLEX facility parameters.
Table 1-23
FLEX facility parameters
Unit FLEX-shelf-slot-port Displays the facility AID. Read-only.
Primary State See “Equipment and facility Sets the primary state of the facility. Default reflects
primary states” on page primary state of associated equipment.
1-98 IS and OOS are selectable.
Secondary State See “Facility secondary Displays the facility operational state. The Auto in-
states” on page 1-99 service state is editable.

Table 1-23
FLEX facility parameters (continued)
Protocol • 1000BASET (Note 1 and Sets the FLEX facility protocol.

Note 2) Note 1: GE clients on FLEX MOTR do not have
• 1000BASEX (Note 1 and auto-negotiation settings but will pass through the
Note 2) client service. If the delay of the devices that connect
to the client ports is low enough so as not to cause
• FC100 auto-negotiation timeouts, auto-negotiation can be
• FC200 enabled on the connecting devices. Otherwise,
auto-negotiation on the connecting devices must be
• FC400 disabled.
• FICON Note 2: For GE clients, maximum transfer unit
• FICONEXPRESS (MTU) is not configurable and 9600 byte jumbo
frames will pass through the client service.
• FICON4G
• GEN8B10B
• GENTRANSP
• ISC3P1G
• ISC3P2G
• ESCON
• OCn/STMn
Protocol Rate Numeric value Displays the protocol rate.

(Mbps) This parameter is editable only when the protocol is
set to GEN8B10B or GENTRANSP. Supported
rates for the GEN8B10B or GENTRANSP protocols
are: 155.52, 200, 622.08, 1000, 1062.5, 1250, 2125,
2488.32, 4250
Mapped Rate • 1244.16 Mbps for OTM0 Displays the rate after mapping. Read-only.
• 2498.77 Mbps for OTM1
Packet Mapping FLEXCBR (read-only) Displays or sets the mapping type.
Latency • MINIMUM Sets the MTU of the ETH facility associated with the
Optimization • MEDIUM (default) FLEX facility.
• MAXIMUM • 1470 bytes for MINIMUM, adds more overhead

(less BW efficient)
• 462 bytes for MEDIUM
• 174 bytes for MAXIMUM, adds less overhead
(more BW efficient)

Table 1-23
FLEX facility parameters (continued)
Conditioning Type • 8B10B Determines type of signal conditioning towards

• K30_7 subtending equipment when line faults or head-end
client faults are detected. Conditioning type support
• LOFEF and behavior is protocol specific.
• NOS • 8B10B – sends a 10B error code. Applicable to all
• AISL protocols except GENTRANSP, and OCn/STMn.
• K30_7 – sends K30.7 error code. Applicable to
1000BASEX and FICONEXPRESS.
• LOFEF – shuts off the Tx laser. Applicable to all
protocols.
• NOS – sends a NOS primitive. Applicable to all FC/
FICON protocols.
• AISL – sends line AIS. Applicable to OCn/STMn
protocols.
Holdoff Timer 0 to 1000 in 100 increments Sets the length of time (in ms) before Tx
conditioning is applied to the client. The default
value for protocols FC100/200/400 and FICON/
FICONEXPRESS/FICON4G is 100. For all other
protocols, it is 0.
All protocols should have the holdoff timer set to 100
ms (or more) when involved in any protection
scheme except O-APS. Holdoff timer of 0 is required
on all FLEX facilities involved in O-APS protection.
Trace string Sets the transmitted trace monitoring value.
Expected Trace string Sets the expected trace monitoring value.
TRCINFO • Yes Sets whether to include the trace information in the

• No (default) response.
AINSTIMELEFT Numeric value Displays the time left on the AINS timer.
Tx Actual Power Numeric value Displays the Tx actual power in dBm.

(dBm)
Rx Actual Power Numeric value Displays the Rx actual power in dBm.

(dBm)
Customer Defined string of up to 64 characters Used to identify a provisioned facility. It is the same
Facility Identifier as the Common Language Facility Identifier (CLFI).
The provisioned value appears in the facility alarm
report if the SP2, SPAP, SPAP-2 w/2xOSC, or the
2-slot integrated SP is equipped.

ADJ facility parameters

The table that follows provides information on ADJ facility parameters.
Table 1-24
ADJ facility parameters
ADJ
Unit ADJ-shelf-slot-port Displays the facility AID. Read-only.
Primary State See “Equipment and Displays the primary state of the facility. Read-only.
facility primary states” on
page 1-98
Adjacency Type TXRX Displays the type of the adjacency. Read-only.
Status • Unverified Displays current status of the adjacency facility.

• Derived • Unverified - The provisioned far end address has been
• Reliable set by the end-user. If an actual far end address exists,
it matches the provisioned far end address and has
• Unreliable been discovered through information received from the
far end shelf but has not been verified by any physical
connectivity.
• Derived - The provisioned far end address has been set
by the system. If an actual far end address exists, it
matches the provisioned far end address and has been
discovered through information received from the far
end shelf but has not been verified by any physical
connectivity.
• Reliable - The actual far end address matches the
provisioned far end address and has been discovered
through physical connectivity. The provisioned far end
address has been set by either the system or the end-
user.
• Unreliable - The actual far end address is detected and
it does not match the provisioned far end address or the
discovery validation has detected a mis-fibering.
Actual Far End string format Displays the actual far end address which is the detected
Address TID, shelf, slot, and port of the far end of the fiber.
Read-only.
Actual Far End See Note 2 Displays the option that each field of the far end address
Address Format represents. Read-only.
Expected Far End TID-shelf-slot-port Sets the provisioned far end address of the fiber
Address (Note 1) connection.

Table 1-24
ADJ facility parameters (continued)
Expected Far End See Note 2 Sets the expected far end line receive and client receive
Address Format addresses format reported by the adjacency.

Note 1: The Expected Far End Address is controlled by the Expected Far End Address Format
selection. If the Expected Far End Address Format is set to ‘NULL’, then the Expected Far End
Address is disabled; Otherwise, it is enabled.
Note 2: The Far End Address Format options are:
• NULL
• TID-SH-SL-PRT
• TID-SH-SL-SBSL-PRT

Synchronization parameters
Table 1-25
Timing reference parameters
Mode Source (Note 1) Description
Internal Timing - No sources available for selection
Line Timing Any equipped OC-n/STM-n/STM1J/STM4J See Note 2, Note 3, and Note 4
port
None Indicates no reference provisioned
External Timing BITSIN-A/ESI-A External synchronization input A

(Note 5 and Note 6) BITSIN-B/ESI-B External synchronization input B
None Indicates an unused source
Mixed Timing BITSIN-A/ESI-A External synchronization input A

(Note 6) BITSIN-B/ESI-B External synchronization input B
Any equipped OC-n/STM-n/STM1J/STM4J See Note 2, Note 3, and Note 4

port
Note 1: Each possible source, except None, can appear only once in the timing reference hierarchy.
Note 2: Only one port on each multi-port circuit pack can be selected as a timing generation and timing
distribution reference.
Note 3: DS3, EC-1, E1, E3, DS1DS3, E1DS3, E1E3, STM1E, GE, 10/100BT, 10GE, L2SS, PDH
gateway, and RPR facilities cannot be set as synchronization source references.
Note 4: DS1 DSM facilities and OC-3 ports which are provisioned as DSM hosts cannot be set as
Note 5: To maximize reliability, the BITSIN/ESI ports require the payload of the incoming signal to be
all 1’s. The BITSIN/ESI hardware may not operate correctly with other payload patterns.
Note 6: It is not applicable to SuperMux, FLEXMOTR, or L2MOTR independent timing groups.

Path connections parameters

The following tables detail the 4xGE EPL, 1x10GE EPL, and 24x10/
100BT EPL circuit pack parameters associated with the Path Connections
Site Manager application.
Table 1-26
Path Connections application parameters for 4xGE EPL, 1x10GE EPL, and 24x10/100BT EPL
circuit packs
Parameter Description
Selectable parameters
Connection ID Enter the connection identifier string used to identify a provisioned path
connection. The path connection ID can contain a maximum of 64 characters,
with the exception of the \, “, and % characters.
For connections created by the SONET/SDH Control Plane, the connection
identifier string is assigned a network wide unique identifier, called a Network
Call Correlation Identification (NCCI).
Note: Support for 64 characters connection IDs is only supported from ONM
Release 6.0 onwards.
Rate Select the rate as defined below:
• 4xGE EPL circuit packs: STS1/VC3, STS3c/VC4, STS12c/VC4-4c, STS24c/
VC4-8c
• 1x10GE EPL circuit packs: STS3c/VC4, STS192c/VC4-64c
• 24x10/100BT EPL circuit packs: STS1/VC3, STS3c/VC4
Type Select the type as defined below:
• 1WAY (Unidirectional)
• 1WAYPR (Unidirectional Path Ring)
Refer to Table 1-27 on page 1-142.
From and To panels Select the Equipment and Facility for the From or To as required. Refer to
Table 1-28 on page 1-142.
Switch Mate Select the Switch Mate when making 2WAYPR or 1WAYPR connections. Refer
to Table 1-27 on page 1-142.

Table 1-27
Path connection types—supported From, To, and Switch Mate instances
Path connection From, Switch Mate To

type
1WAY (Note) GE WAN GE WAN
1WAYPR (Note) GE WAN GE WAN
2WAY GE WAN, 10GE WAN, 10/100 BT WAN GE WAN, 10GE WAN, 10/100 BT WAN
2WAYPR GE WAN GE WAN
Note: Unidirectional (1WAY and 1WAYPR) path connections (Ethernet drop-and-continue) are not
supported on WAN facilities on 10GE EPL circuit packs.
Table 1-28
Equipment and facility parameters for path connections
Rate Equipment Facility/channel Parameter values
4xGE EPL and 4xGE EPL EFM circuit packs (Note 1)
STS1/VC3 PGE-shelf#-slot#-port# WAN-shelf#-slot#-port#-sts# shelf# = 1 to 254

and PGEFC-shelf#-slot#- WAN-shelf#-slot#-port#-J#-K# slot# = 1 to 6 and 9 to 14 for 14-
AU4 port# slot shelf
mapped PGEFC200-shelf#-slot#- slot# = 1-8, 11-18, 21-28, and
VC3 port# 31-38 for 32-slot shelf
port# = 1 to 4
sts# = 1
J# (AU4) = 1
K# (TUG-3) = 1
STS3c/VC4 PGE-shelf#-slot#-port# WAN-shelf#-slot#-port#-sts# shelf# = 1 to 254

PGEFC-shelf#-slot#- WAN-shelf#-slot#-port#-J# slot# = 1 to 6 and 9 to 14 for 14-
port# slot shelf
PGEFC200-shelf#-slot#- slot# = 1-8, 11-18, 21-28, and
port# 31-38 for 32-slot shelf
port# = 1 to 4
sts# = 1
J# (AU4) = 1

Table 1-28
Equipment and facility parameters for path connections (continued)
STS12c/ PGE-shelf#-slot#-port# WAN-shelf#-slot#-port#-sts# shelf# = 1 to 254

VC4-4c PGEFC-shelf#-slot#- WAN-shelf#-slot#-port#-J# slot# = 1 to 6 and 9 to 14 for 14-
port# slot shelf
port# = 1 to 4
sts# = 1
J# (AU4) = 1
STS24c/ PGE-shelf#-slot#-port# WAN-shelf#-slot#-port#-sts# shelf# = 1 to 254

VC4-8c PGEFC-shelf#-slot#- WAN-shelf#-slot#-port#-J# slot# = 1 to 6 and 9 to 14 for 14-
port# slot shelf
port# = 1 to 4
J# (AU4) = 1
STS1-nv/ PGE-shelf#-slot#-port# WAN-shelf#-slot#-port#-sts# shelf# = 1 to 254

AU4 PGEFC-shelf#-slot#- WAN-shelf#-slot#-port#-J#-K# slot# = 1 to 6 and 9 to 14 for 14-
mapped port# slot shelf
VC3
and port# 31-38 for 32-slot shelf
VC3-nv port# = 1 to 4
(n = 1 to 21) sts# = 1 to 21
J# (AU4) = 1 to 7
K# (TUG-3) = 1 to 3
STS3c-nv/ PGE-shelf#-slot#-port# WAN-shelf#-slot#-port#-sts# shelf# = 1 to 254

VC4-nv PGEFC-shelf#-slot#- WAN-shelf#-slot#-port#-J# slot# = 1 to 6 and 9 to 14 for 14-
(n = 1 to 7) port# slot shelf
port# = 1 to 4
sts# = 1, 4, 7, 10, 13, 16, 19
J# (AU4) = 1 to 7

Table 1-28
1x10GE EPL circuit packs
STS192c/ P10GEL-shelf#-slot#- WAN-shelf#-slot#-port#-sts# shelf# = 1 to 254

VC4-64c port# WAN-shelf#-slot#-port#-J# slot# = 1 to 6 and 9 to 14 for 14-
P10GSEL-shelf#-slot#- slot shelf
port# slot# = 1-8, 11-18, 21-28, and
P10GSOEL-shelf#-slot#- 31-38 for 32-slot shelf
port# port# = 1
sts# = 1
J# (AU4) = 1
STS3c-nv/ P10GEL-shelf#-slot#- WAN-shelf#-slot#-port#-sts# shelf# = 1 to 254

VC4-nv port# WAN-shelf#-slot#-port#-J# slot# = 1 to 6 and 9 to 14 for 14-
(n = 1 to 64) P10GSEL-shelf#-slot#- slot shelf
port# slot# = 1-8, 11-18, 21-28, and
port# port# = 1
sts# = 1, 4, 7, ..., 190
J# (AU4) = 1 to 64
24x10/100BT Ethernet Private Line (EPL) circuit packs (Note 2, Note 3, and Note 4)
STS1/VC3 FE-shelf#-slot# WAN-shelf#-slot#-port#-sts# shelf# = 1 to 254

PFE-shelf#-slot#-port# WAN-shelf#-slot#-port#-J#-K# slot# = 1 to 4 and 9 to 12 for 14-
slot shelf
slot# = 1-8, 11-18, 21-28, and
31-38 for 32-slot shelf
port# = 1 to 24 (for FE)
port# = 1 to 8 (for PFE)
sts# = 1
J# (AU4) = 1
K# (TUG-3) = 1

Table 1-28
STS3c/VC4 FE-shelf#-slot# WAN-shelf#-slot#-port#-sts# shelf# = 1 to 254

PFE-shelf#-slot#-port# WAN-shelf#-slot#-port#-J# slot# = 1 to 4 and 9 to 12 for 14-
slot shelf
slot# = 1-8, 11-18, 21-28, and
sts# = 1
J# (AU4) = 1
VT1.5-nv/ FE-shelf#-slot# WAN-shelf#-slot#-port#-sts#- shelf# = 1 to 254

VC11-nv PFE-shelf#-slot#-port# vtg#-vt# slot# = 1 to 4 and 9 to 12 for 14-
(n = 1 to 63) WAN-shelf#-slot#-port#-J#-K#- slot shelf
L#-M# slot# = 1-8, 11-18, 21-28, and
sts# = 1 to 3, vtg# = 1 to 7 or ALL
vt# = 1 to 4
J# (AU4) = 1
K# (TUG-3) = 1 to 3
L# (TUG-2) = 1 to 7 or ALL
M# (TU-11) = 1 to 4

Table 1-28
VT2-nv/ FE-shelf#-slot# WAN-shelf#-slot#-port#-sts#- shelf# = 1 to 254

VC12-nv PFE-shelf#-slot#-port# vtg#-vt# slot# = 1 to 4 and 9 to 12 for 14-
(n = 1 to 46) WAN-shelf#-slot#-port#-J#-K#- slot shelf
L#-M# slot# = 1-8, 11-18, 21-28, and
sts# = 1 to 3
vtg# = 1 to 7 or ALL
vt# = 1 to 3
J# (AU4) = 1 to 2
K# (TUG-3) = 1 to 3,
M# (TU-12) = 1 to 3
STS1-nv/ FE-shelf#-slot# WAN-shelf#-slot#-port#-sts# shelf# = 1 to 254

VC3-nv PFE-shelf#-slot#-port# WAN-shelf#-slot#-port#-J#-K# slot# = 1 to 4 and 9 to 12 for 14-
(n = 1 to 3) slot shelf
slot# = 1-8, 11-18, 21-28, and
sts# = 1 to 3
J# (AU4) = 1 to 8
K# (TUG-3) = 1 to 3

Table 1-28
Note 1: When provisioning path connections on a 4xGE EPL circuit pack, ports 1 and 2 are considered
mate ports and ports 3 and 4 are considered mate ports. The following restrictions apply when provisioning
path connections on the mate ports:
• The virtual concatenation state (enabled or disabled) of the mate ports must be the same. For example, if
virtual concatenation is enabled on port 1 and has a path connection provisioned, you cannot provision a
path connection on port 2 if the virtual concatenation is disabled on port 2.
• If virtual concatenation is disabled:
— if you provision an STS1/VC3 path connection to one port of the mate pair, you can only provision an
STS1/VC3 path connection on the other port of the mate pair.
— if you provision a path connection other than an STS1/VC3 path connection to one port of the mate pair,
you cannot provision an STS1/VC3 path connection on the other port of the mate pair. For example, if
you provision an STS1/VC3 path connection on port 1, you cannot provision an STS3c/VC4, STS12c/
VC4-4c, or STS24c/VC4-8c path connection on port 2. You can provision an STS3c/VC4, STS12c/VC4-
4c, or STS24c/VC4-8c on port 1 and an STS3c/VC4, STS12c/VC4-4c, or STS24c/VC4-8c on port 2.
— Low-order VC3s are mapped into a TU-3 and packed into an AU-4.
Note 2: The 24x10/100BT EPL and NxFE EPL circuit packs support a maximum of 16 STS3c/VC4,
48 STS1/VC3, 336 VT1.5/VC11, and 252 VT2/VC12 connections. The circuit pack’s total bandwidth
capacity is 48 STS1/VC3 connections, but because three STS1/VC3 connections can be provisioned per
port, you can provision the available bandwidth before all the ports are used. The circuit pack supports a
total bandwidth of VT/VC connections that equal 12 STS1/VC3 connections.
The endpoints supported by the 24x10/100BT EPL and NxFE EPL circuit packs depend on the map mode
used for the fast Ethernet (FE) modules as follows:
• AU3_VT1.5 mode (SONET- VT1.5, STS1, STS3c; SDH - VC11, VC3(AU3), VC4)—in this mode VT1.5-nv/
VC11-nv, STS1/HO VC3, STS1-nv/HO VC3-nv, and STS3c/VC4 connections are allowed.
• AU4_VT2 mode (SONET- VT2, STS1, STS3c; SDH - VC12, VC3, VC4)—in this mode VT2-nv/VC12-nv,
STS1/LO VC3, STS1-nv/LO VC3-nv, and STS3c/VC-4 connections are allowed.
For more information on map modes, see Part 1 of Configuration - Provisioning and Operating, 323-1851-
310.

Table 1-28
Note 3: If you provision path connections on a 24x10/100BT circuit pack in AU4_VT2 mode, the LO_VC3
connections (Optics end of an XC is AU4 mapped) are internally allocated in groups of 3xSTS1 connections
(AU4) on the 24x10/100BT circuit pack on the AU4 boundaries. In this case, if VT2 connections or STS1
(with optics end of a XC AU3 mapped) are provisioned along with LO_VC3 connections, some bandwidth
may be stranded since a WAN port cannot have mixed bandwidth. When the 24x10/100BT circuit pack is in
AU4_VT2 mode, a VCAT WAN port is provisioned with either STS1, LO_VC3, or VT2 connections. For
example:
• If ports 1 to 22 of a 24x10/100BT circuit pack are provisioned as LO_VC3 connections, then 45 STS1
connections will be allocated as 15 AU4 blocks. If port 23 is provisioned with two LO_VC3 connections,
then the final AU4 block is allocated as LO_VC3 connection and therefore port 24 must be provisioned as
LO_VC3 connection.
• If port 23 is provisioned with two STS1 or VT2 connections, then the final AU4 block is allocated as a non-
L_VC3 block and the 15th AU4 block is an STS1 connection that is stranded. Port 24 may then be
provisioned with one LO_VC3 (allocated to the 15th AU4 block) or as a single STS1 connection or 21 VT2
connections. In either case two STS1 bandwidth cannot be allocated to port 24.
Note 4: The VT level cross connections can be made only on STS# 1 to 12. Whenever you create cross
connection of full circuit pack bandwidth (i.e. 48 connections), the system fills the STS numbers from 13 for
48 first and the STS numbers 1 to 12 are used for last 12 connections made on the circuit pack. These
connections can be on any port. Hence if you want to add VT connections after deleting STS1s that are
created already, you must delete the STS# 1 to 12 and add VT connections. It means you must delete the
lastly added 12 recent connections to the circuit pack.

EVPL connections parameters

The following tables detail the FLEX MOTR circuit pack parameters
associated with the EVPL Connections Site Manager application.
Table 1-29
EVPL Connections application parameters for FLEX MOTR circuit packs
Connection ID The connection identifier string is used to identify a provisioned EVPL
with the exception of the \, “, and % characters
Rate Select the rate as EVPL. (This is the only connection rate supported in this
release.)
Type Select the connection type as 2WAY (Bidirectional). (This is the only
connection type supported in this release.) Refer to Table 1-30 on page 1-149.
From and To panels Select the Equipment and Facility for the From and To endpoints as
required. Refer to Table 1-31 on page 1-150 for details.
VCID (1-1048575) Select the virtual circuit segment identifier (a value between 1 and 1048575).
The VCID creates the association between a client port FLEX/auto-created
ETH facility and an ETH10G facility on FLEX MOTR circuit packs.
The VCID can be used to uniquely identify a specific customer in the FLEX
MOTR network.
Note: In the Data Services application view for FLEX MOTR circuit packs,
these entities are shown as associations between VCS and its VCEs and
VCEMAPs. The VCS and associated VCEs and VCEMAPs all have the same
VCID value.
SVID (1-4094) Select the service provider VLAN identifier (a value between 1 and 4094).
The SVID is used to uniquely identify the EVPL service on the muxed line port.
The SVID is unique to a port and optional if the VCID is less than 4095 (if the
SVID is not specified, the SVID is equal to the VCID).
Table 1-30
EVPL connection types—supported From and To instances for FLEX MOTR circuit packs
Connection type From To
2WAY auto created ETH (FLEX) and ETH10G auto created ETH (FLEX) and ETH10G

Table 1-31
Equipment and facility parameters for EVPL connections for FLEX MOTR circuit packs
FLEX MOTR circuit packs
EVPL P10GEL-shelf#-slot#-port# ETH10G-shelf#-slot#-port# shelf# = 1 to 254

P10GSEL-shelf#-slot#-port# slot# = 1, 2 for 2-slot shelf
P10GSOEL-shelf#-slot#-port# slot# = 1 to 7 for 7-slot shelf
PXFP-shelf#-slot#-port# slot# = 1 to 14 for 14-slot shelf
(except in slots 7 and 8 of the
14-slot packet-optical shelf)
slot# = 1 to 6 for 6500-7 packet-
optical shelf
slot# = 1-8, 11-18, 21-28, and
port# = 1 and 2
P155622M-shelf#-slot#-port# ETH-shelf#-slot#-port# shelf# = 1 to 254

P155M-shelf#-slot#-port# slot# = 1, 2 for 2-slot shelf
P622M-shelf#-slot#-port# slot# = 1 to 7 for 7-slot shelf
P2G5-shelf#-slot#-port# slot# = 1 to 14 for 14-slot shelf
PCWDMS-shelf#-slot#-port# (except in slots 7 and 8 of the
PGE-shelf#-slot#-port#
slot# = 1 to 6 for 6500-7 packet-
PGEFC-shelf#-slot#-port# optical shelf
PGEFC200-shelf#-slot#-port# slot# = 1-8, 11-18, 21-28, and
PFC400-shelf#-slot#-port# 31-38 for 32-slot shelf
port# = 3 to 10

2-1
Layer 2 circuit packs 2-
This section provides an overview of the 6500 Packet-Optical Platform (6500)

layer 2 circuit packs and their associated procedures. See the following table
for different circuit packs covered in this section.
Table 2-1
Layer 2 circuit packs in this section
Topic
“L2SS VT1.5/LO 4xGE circuit pack (NTK531BAE5)” on page 2-2
“L2SS DS1/E1/DS3/E3 4xGE circuit pack (NTK531MAE5)” on page 2-13
“20G L2SS 16 Port I/O 2xXFP / 8xSFP circuit pack (NTK531HAE5)” on page 2-25
“L2 MOTR 2xXFP/10xSFP circuit pack (NTK531VAE5)” on page 2-41
“eMOTR circuit packs (NTK536AA, NTK536AB, NTK536BE, NTK536FA,
NTK536FB)” on page 2-62
“RPR 10G STS-1/HO 4xGE circuit pack (NTK534BAE5)” on page 2-106
Refer to 6500 Packet-Optical Platform Data Application Guide, NTRN15BA,

for detailed information on data concepts, applications, and engineering rules
supported in this release of 6500.
eMOTR circuit packs use an operating system based on the Service Aware
Operating System (SAOS) for Layer 2 services. Refer to the following
documents for detailed information:
• SAOS-based Packet Services Command Reference, 323-1851-610
• SAOS-based Packet Services Configuration, 323-1851-630
• SAOS-based Packet Services Fault and Performance, 323-1851-650
• SAOS-based Packet Services MIB Reference, 323-1851-690

2-2 Layer 2 circuit packs
L2SS VT1.5/LO 4xGE circuit pack (NTK531BAE5)

Overview
The L2SS VT1.5/LO 4xGE circuit pack (also known as L2SS) uses up to four
SFP optics for the GE interfaces to provide up to five Gbit/s of unidirectional
or 2.5G Gbit/s of bidirectional Layer 2 (L2) aggregation. Services from the
L2SS circuit pack map to SONET/SDH containers and are assigned as
connections to OC-n/STM-n interface circuit packs. They can therefore use
the traffic protection schemes supported by the OC-n/STM-n interface circuit
packs to provide a protected service without the requirement of a redundant
handoff from the subtending equipment.
Figure 2-1 shows the faceplate of a L2SS circuit pack. Figure 2-2 on page 2-3
provides functional block diagram of the L2SS circuit pack.
Figure 2-1
L2SS circuit pack faceplate
Red triangle (Fail)

L2SS 2.5G 4xGE
VT1.5/LO
4 Ports SFP
Fail
Ready
In Use

Rx
2 Tx
Rx
3 Tx

Rx
Hazard
level:

R99
EEEEE99999
S/N NT030MEE9999E
NTUD99EE
Type A

Figure 2-2
L2SS circuit pack block diagram (NTK531BAE5)
PHY SFP 1
XC
PHY SFP 2
Backplane
2.5G SONET/SDH Network

OHP Processor
PHY SFP 3
XC
PHY SFP 4
Processor Power
Module Supply
Legend
The L2SS circuit pack (NTK531BAE5) provides the following functionality.
• operates at the layer 2 (data link layer)
• no direct mapping between LAN and WAN, LAN to WAN association is
achieved by L2 provisioning of virtual circuit segments (VCS)
• LAN facilities can be combined to form link aggregation groups (LAG)
• client interfaces support:


— can be set to UNI or NNI on a per-port basis
— support Ethernet in the first mile (EFM), compliant to IEEE Std 802.3
— auto-negotiation support as per clause 37 of IEEE Std 802.3
— 64 byte to 9100 byte Ethernet frames (jumbo frames support)
— stacked VLANs, tagged/untagged frames
• WAN facilities
— up to 64 WAN facilities per circuit pack
— can be set to UNI or NNI
— mapping of WAN facilities to/from SONET/SDH containers via Framed
GFP
– STS1/HO_VC3/LO_VC3 and VC4 (the support for LO_VC3
cross-connects for this circuit pack and associated facilities
provides for greater interoperability with other products that
support LO_VC3)
– contiguous concatenation (STS3c, STS12c/VC4-4c,
STS24c/VC4-8c, and STS48c/VC4-16c)
– virtual concatenation (VT1.5-nv/VC11-nv where n = 1 to 64,
VT2-nv/VC12-nv where n = 1 to 64,
STS1-nv/HO_VC3-nv/LO_VC3-nv where n = 1 to 24,
STS3c-nv/VC4-nv where n = 1 to 8), LCAS support when VCAT is
enabled
– up to 1344 VT1/1008 VT2 connections are supported.
The total backplane capacity is equivalent to 48xSTS-1s or 16xVC4s.

• traffic management
— metering and marking of frames
— eight classes of service (COS)
— policing/rate limiting for committed information rate (CIR) and
excessive information rate (EIR) at 64 kbit/s granularity
— scheduling and prioritization based in IEEE 802.1p
— LACP support
• L2 connectivity
— point-to-point (P2P) and multipoint-to-multipoint (A2A) connectivity
— forwarding database (FDB) supports up to 32000 static/dynamic MAC
entries per circuit pack
— queue length management support
• packet forwarding
— VLAN switching, swapping, stacking, and stripping (removal of the
VLAN tag)
— port based forwarding
— support of 8100, 88A8, and 9100 Ethertype values
• has two NPUs with 64MB buffers each, for a total of 128MB of memory for
ingress and egress buffers
• Equipment protection (1+1)

6500.
Note 2: For detailed information about L2SS concepts, applications, and
engineering rules, see the 6500 Packet-Optical Platform Data Application
Guide, NTRN15BA.
Note 3: Refer to Table 2-21 on page 2-100 to see a summary comparison
between Layer 2 (L2SS, PDH Gateway, 20G L2SS, eMOTR, and L2
MOTR) circuit packs.

The L2SS circuit pack supports the following cross-connection types:
The L2SS circuit pack supports the following cross-connection rates:
• non-concatenated rates of STS1/LO VC3, STS1/HO VC3, and VC4
• concatenated rates of STS3c, STS12c/VC4-4c, STS24c/VC4-8c, and
STS48c/VC4-16c
• virtual concatenation (LCAS supported with VCAT enabled) at rates of
VT1.5-nv/VC11-nv (n = 1 to 64), VT2-nv/VC12-nv (n = 1 to 64),
STS1-nv/LO VC3-nv (n = 1 to 24), STS1-nv/HO VC3-nv (n = 1 to 24), and
Note the total capacity for cross-connections on the L2SS circuit pack
equivalent to 48 STS1’s or 16 VC4’s.
Supported SFPs
The following table provides a list of the SFPs that are supported on the L2SS
circuit pack.
Table 2-2
Supported SFP modules for the L2SS circuit pack (NTK531BAE5)
Facilities

— ETH — 1000Base-X (1.25Gb/s)

— 1000Base-X (1.25Gb/s)
GE 1000-Base-BX 10-D NTTP59BD

Bidirectional-downstream, 1490 nm Tx, 10 km
SFP
— 1000Base-X (1.25Gb/s)

— 1000Base-T (1.00Gb/s)

Table 2-2
Supported SFP modules for the L2SS circuit pack (NTK531BAE5) (continued)
Facilities

— ETH — 1000Base-X (1.25Gb/s)


— 1000Base-X (1.25Gb/s) x= L, M, N, P, Q,
R, S, T

— ETH — 1000Base-X (1.25Gb/s)

— 1000Base-X (1.25Gb/s)
The L2SS circuit pack supports the following monitored entities:
• PM collection for ETH, WAN, LCAS-enabled WAN, and COS (ETH and
WAN) facilities
• operational measurements for ETH, WAN, LCAS-enabled WAN, LAG
(ETH), COS (ETH, LAG, and WAN), MEP, MIP, and VCE (ETH, and WAN)
facilities

monitoring, refer to Fault Management - Performance Monitoring,
323-1851-520.
Alarms
Equipment alarms


• Equipment OOS with Subtending Facilities IS
Pluggable alarms
Ethernet alarms
• LACP Failed
• Link Down
• Loss Of Signal
• Port Bandwidth Near Limit
• Signal Degrade

WAN alarms
• Config Mismatch -LCAS
• Link Down
• Loopback Traffic Detected
• Signal Degrade
• Rx Partial Loss of Capacity -LCAS
• Rx Total Loss of Capacity -LCAS
• Tx Partial Loss of Capacity -LCAS
• Tx Total Loss of Capacity -LCAS
STS Path alarms

PDH Facility alarms

• AIS
• Loss of Frame
• Loss Of Multiframe
• Loss of Multiframe - VCAT
• Remote Alarm Indication

VT Path Facility alarms

Layer 2 alarms
• Link Aggregation Group Fail
• MAC Database Near Capacity
• MAC Flapping Detected
Common alarms
Equipping rules
The following equipping rules apply to L2SS circuit packs:
• is a single-slot four-port interface.
ATTENTION
— In a 14-slot packet-optical shelf (NTK503SA), this circuit pack supports HO and
LO_VC3 connections when using X-Conn 240G+ STS-1/VC-3 (240/0)
(NTK557ES) or X-Conn 240G+ 80G VT1.5/VC-12 circuit pack (240/80)
(NTK557GS) circuit packs (VT1.5/VC11 and VT2/VC12 connections are not
supported).
— This circuit pack is not supported in 14-slot shelf types when the shelf is
• can be installed in slots 1-8, 11-18, 21-28, and 31-38 in a 32-slot

packet-optical shelf type when the shelf is equipped with 640G+
STS-1/VC-3 (640/0) (NTK610BBE5) cross-connect circuit packs.
ATTENTION
— This circuit pack is not supported in 32-slot packet-optical shelf types when the
shelf is equipped with PKT/OTN cross-connect circuit packs.
— For 32-slot shelf types, a maximum of 16 unprotected L2 circuit packs in total
(L2SS, 20G L2SS, PDH gateway, and RPR circuit packs) can be installed in a
single 32-slot shelf. In this case, a maximum of 16 1+1 protected L2SS, 20G
L2SS, or PDH gateway circuit packs in total (eight pairs) can be installed in a
single 32-slot shelf.


NTK503KA).
this release.
• in a 14-slot shelf type, the 240G+/80G VT1.5/VC-12 (240/80)
cross-connect circuit packs (NTK557GAE5/NTK557GS), and 240G+
STS-1/VC-3 (240/0) circuit packs (NTK557EAE5/NTK557ES), and 640G+
STS-1/VC-3 (640/0) circuit packs (NTKBB610E5) do not support
VT1.5/VC11, VT2/VC12, or LO-VC3 traffic on L2SS VT1.5/LO 4xGE
circuit packs.
• VT1.5/VC11, VT2/VC12 and LO VC3 rates are supported when using the
20G/20G VT1.5/VC-12 (20/20) (NTK557QAE5), 80G/20G VT-1.5/VC-12
(80/20) (NTK557PAE5) and 80G/80G VT1.4/VC-12 (80/80)
(NTK557NAE5) cross-connection circuit packs.
Engineering rules
For more information about L2SS engineering rules, refer to 6500

specifications for the L2SS optical interface circuit packs.
Table 2-3
Technical specifications for L2SS optical interface circuit packs
Parameter L2SS (NTK531BAE5)

25 (+/-3oC) and voltage of 54 Vdc (+/-2.5 V) or in the full operational voltage range in the case of
AC-powered equipment. For practical purposes, the rounded typical power consumption of an
equipment can be used as the equipment heat dissipation when calculating facilities thermal loads (an
estimate of the long term heat release of the item in a system).
Note 5: For optical SFP specifications, see chapter 3 of Pluggable Datasheets and Reference,
323-1851-180.

L2SS DS1/E1/DS3/E3 4xGE circuit pack (NTK531MAE5)

Overview
The L2SS DS1/E1/DS3/E3 4xGE circuit pack (also known as PDH gateway)
uses up to four SFP optics for the GE interfaces to provide up to five Gbit/s of
unidirectional or 2.5G Gbit/s of bidirectional Layer 2 (L2) aggregation.
Additional PDH functionality are also supported by this circuit pack. The PDH
gateway circuit pack provides all the features supported by the L2SS circuit
pack but has the added capability of de-encapsulating/encapsulating PDH
(DS1/DS3/E1/E3) traffic. The PDH gateway circuit pack can terminate up to
128 WAN ports versus 64 on L2SS. The PDH gateway circuit pack is designed
to provide L2 head-end copper access termination (from DS1/DS3/E1/E3
PDH tributaries) for business services within the captive office. In addition,
with multipoint-to-multipoint (A2A) the PDH gateway circuit pack can provide
centralized DCN aggregation of management to the captive office.
Services from the PDH gateway circuit pack map to SONET/SDH containers
and are assigned as connections to OC-n/STM-n interface circuit packs. They
can therefore use the traffic protection schemes supported by the
OC-n/STM-n interface circuit packs to provide a protected service without the
requirement of a redundant handoff from the subtending equipment.
Figure 2-3 on page 2-14 shows the faceplate of a PDH gateway circuit pack.
Figure 2-4 on page 2-15 provides functional block diagram of the PDH
gateway circuit pack.

Figure 2-3
PDH gateway circuit pack faceplate
Red triangle (Fail)

L2SS 2.5G GE
DS1/E1/DS3/E3
4 Ports SFP
Fail
Ready
In Use

Rx
2 Tx
Rx
3 Tx

Rx
Hazard
level:

R99
EEEEE99999
S/N NT030MEE9999E
NTUD99EE
Type A

Figure 2-4
PDH gateway circuit pack block diagram (NTK531MAE5)
PHY SFP 1
XC
PHY SFP 2
Backplane
2.5G SONET/SDH/PDH Network

OHP Processor
PHY SFP 3
XC
PHY SFP 4
Processor Power
Module Supply
Legend

The PDH gateway circuit pack (NTK531MAE5) supports the following:
achieved by L2 provisioning of virtual circuit segments (VCS) and virtual
circuit endpoints (VCE)
• WAN facilities
— up to 128 WAN facilities per circuit pack (up to 2.5G of bandwidth). For
engineering rules concerning how these 128 WAN facilities are
divided, refer to Part 1 of Configuration - Provisioning and Operating,
323-1851-310.
GFP
support LO_VC3)
– virtual concatenation (VT1.5-nv/VC11-nv where n = 1 to 64,
VT2-nv/VC12-nv where n = 1 to 64,
STS1-nv/HO_VC3-nv/LO_VC3-nv where n = 1 to 24,
STS3c-nv/VC4-nv where n = 1 to 8), LCAS support when VCAT is
enabled
– up to 1344 VT1/1008 VT2 connections are supported.


— mapping of WAN facilities to/from PDH containers via Framed GFP
– PDH VCAT disabled: up to 128 DS1 per circuit pack (one DS1 per
WAN facility), up to 128 E1 per circuit pack (one E1 per WAN
facility), up to 48 DS3 per circuit pack (one DS3 per WAN facility),
and up to 48 E3 per circuit pack (one E3 per WAN facility).
– PDH VCAT enabled: up to 16 DS1 (DS1-nv where n = 1 to 16) per
WAN facility (up to 336 DS1 per circuit pack), up to 16 E1 (E1-nv
where n = 1 to 16) per WAN facility (up to 252 E1 per circuit pack),
only one DS3 (DS3-nv where n = 1) per WAN facility (up to 48 DS3
per circuit pack), only one E3 (E3-nv where n = 1) per WAN facility
(up to 48 E3 per circuit pack).
Note: All PDH facilities within WAN facilities (whether they have PDH
VCAT enabled or disabled) are connected via individual VT1.5/VT2/STS-1
or VC11/VC12/VC3 (LO and HO) cross-connections to the far-end PDH
facilities.
excessive information rate (EIR) at 64 kbit/s granularity per COS
— LACP support
• L2 connectivity
VLAN tag)
• Equipment protection (1+1)
• SONMP topology discovery

• has two NPUs with 64MB buffers each, for a total of 128MB of memory for
ingress and egress buffers

6500.
Note 2: For detailed information about PDH gateway concepts,
applications, and engineering rules, see the 6500 Packet-Optical Platform
Data Application Guide, NTRN15BA.
The PDH gateway circuit pack supports the following cross-connection types
The PDH gateway circuit pack supports the following cross-connection rates
• non-concatenated rates of STS1/LO VC3, STS1/HO VC3, and VC4
• contiguous concatenation at STS3c, STS12c/VC4-4c, STS24c/VC4-8c,
and STS48c/VC4-16c
• virtual concatenation (LCAS supported with VCAT enabled) at rates of
VT1.5-nv/VC11-nv (n = 1 to 64), VT2-nv/VC12-nv (n = 1 to 64),
STS1-nv/LO VC3-nv (n = 1 to 24), STS1-nv/HO VC3-nv (n = 1 to 24), and
Note the total capacity for cross-connections on the PDH gateway circuit pack

Supported SFPs
The following table provides a list of the SFPs that are supported on the PDH
gateway circuit pack.
Table 2-4
Supported SFP modules for the PDH gateway circuit pack (NTK531MAE5)
Facilities

— ETH — 1000Base-X (1.25Gb/s)

— 1000Base-X (1.25Gb/s)

SFP
— 1000Base-X (1.25Gb/s)

— 1000Base-T (1.00Gb/s)

— ETH — 1000Base-X (1.25Gb/s)


— 1000Base-X (1.25Gb/s) x= L, M, N, P, Q,
R, S, T

— ETH — 1000Base-X (1.25Gb/s)

— 1000Base-X (1.25Gb/s)
The PDH gateway circuit pack supports the following monitored entities:
• PM collection for STS1, STS3c/VC4, STS12c/VC4-4c, STS24c/VC4-8c,
and STS48c/VC4-16c concatenated payloads
• PM collection for SONET VT Path (VTn)/SDH VC Path (VCm) for
VT1.5/VC11, VT2/VC12, STS1/LO VC3 (VT1.5/LO circuit packs only),
STS1/HO VC3, and VC4 non-concatenated payloads

• PM collection of SONET path (P) for DS1, DS3, DS1DS3, DS1WAN, and
DS3WAN facilities
• PM collection of PDH E1 and E3 Path (P) for E1, E3, E1DS3, E1E3,
E1WAN, and E3WAN facilities
• PM collection of PDH E1 and E3 Line (PPI) for E1 and E3 facilities
• PM collection of PDH E1 and E3 Path (P) for E1, E3, E1DS3, and E1E3
facilities
• PM collection of PDH DS1 and DS3 Line (PPI) and Path (P) for DS1 and
DS3 facilities
• PM collection for ETH, WAN, LCAS-enabled WAN, and COS (ETH and
WAN) facilities
• operational measurements for ETH, WAN, LCAS-enabled WAN, LAG
(ETH), COS (ETH, LAG, and WAN), MEP (ETH, ETH10G, WAN, and
VCE), MIP (VSC), and VCE (ETH and WAN) facilities

323-1851-520.
Alarms
Equipment alarms

Pluggable alarms
Ethernet alarms
• LACP Failed
• Link Down
• Loss Of Signal
• Port Bandwidth Near limit
• Signal Degrade
WAN alarms
• Link Down
• Loopback Traffic detected
• Signal Degrade


STS Path alarms

PDH Facility alarms
• AIS
• Loss of Frame
• Loss of Multiframe - VCAT
• Remote Alarm Indication
VT Path Facility alarms
Layer 2 alarms
Common alarms

Equipping rules
The following equipping rules apply to PDH gateway circuit packs:
• is a single-slot four-port interface.
ATTENTION

ATTENTION

NTK503KA).
this release.
• the LO_VC3 cross-connects are only supported when using a low-order
VT1.5/VC-12 cross-connect, 240G+/80G VT1.5/VC-12 (240/80)
(NTK557GAE5/NTK557GS) cross-connect, or 240G+ STS-1/VC-3
(240/0) (NTK557EAE5/NTK557ES), or 640G+ STS-1/VC-3 (640/0)
(NTK610BBE5) cross-connect circuit pack.
Engineering rules
For more information about PDH gateway engineering rules, refer to 6500
specifications for the PDH gateway optical interface circuit packs.

Table 2-5
Technical specifications for PDH gateway optical interface circuit packs
Parameter PDH gateway (NTK531MAE5)

323-1851-180.

20G L2SS 16 Port I/O 2xXFP / 8xSFP circuit pack (NTK531HAE5)

Overview
The 20G L2SS 16 Port I/O 2xXFP / 8xSFP circuit pack (also known as 20G
L2SS) uses up to eight SFP optics for the GE interfaces and up to two XFP
optics for 10GE LAN interfaces from the circuit pack faceplate to provide up to
20 Gbit/s of unidirectional or 10 Gbit/s of bidirectional Layer 2 (L2)
aggregation. This circuit pack also supports up to 16 GE ports accessed from
an I/O panel (see “Front I/O panel (Multi-Service)” on page 2-28 for more
information on the I/O panel).
Services from the 20G L2SS circuit pack map to SONET/SDH containers and
are assigned as connections to OC-n/STM-n interface circuit packs. They can
therefore use the traffic protection schemes supported by the OC-n/STM-n
interface circuit packs to provide a protected service without the requirement
of a redundant handoff from the subtending equipment.
Figure 2-5 on page 2-26 shows the faceplate of a 20G L2SS circuit pack.
Figure 2-6 on page 2-27 provides functional block diagram of the 20G L2SS
circuit pack.

Figure 2-5
20G L2SS circuit pack faceplate
Red triangle (Fail)

20G L2SS
16 Port I/O
2xXFP / 8xSFP
Fail
Ready
In Use
1

2
3 Tx
Rx
4 Tx
Rx
5 Tx
Rx
6 Tx
Rx
7 Tx
8 Tx
Rx
9 Tx
Rx
10 Tx
Rx
Hazard
level:
R99
EEEEE99999
S/N NT030MEE9999E
NTUD99EE
Type A

Figure 2-6
20G L2SS circuit pack block diagram (NTK531HAE5)
PHY XFP 1
PHY XFP 2
PHY SFP 3
XC PHY SFP 4
10G SONET/SDH Network Ethernet PHY SFP 5

OHP Processor Switch
Backplane
PHY SFP 6
XC
PHY SFP 7
PHY SFP 8
PHY SFP 9
PHY SFP 10
Processor Power
Module Supply
I/O Panel 20 x PHY
Legend
OHP Overhead Processor

PHY Physical Layer Adapter

Front I/O panel (Multi-Service)

The Front I/O panel (Multi-Service) (NTK575YZE5) is an optional device that
can be used in conjunction with 20G L2SS circuit packs to provide extra GE
SFP interfaces for the 20G L2SS circuit packs in this release. The Front I/O
panel (Multi-Service), as shown in Figure 2-7 on page 2-29, is supported in
14-slot shelf front electrical types (not supported in a 2-slot, 6500-7
packet-optical, 7-slot, or 32-slot shelf type).
• Each 14-slot 6500 shelf can support up to four Front I/O panels
(Multi-Service) (NTK575YZE5) and can be equipped in an optical/front
electrical or converged optical/front electrical shelf.
• Each Front I/O panel (Multi-Service) supports two slots in the main shelf.
I/O panel#1 supports slots 1 and 2, I/O panel#2 supports slots 3 and 4, I/O
panel#3 supports slots 9 and 10, and I/O panel#4 supports slots 11 and
12. Front I/O panel (Multi-Service) is not supported for 20G L2SS circuit
packs equipped in slots 5, 6, 13, or 14.
• Each Front I/O panel (Multi-Service) contains four 12xSFP I/O carriers
(NTK575EAE5). The 12xSFP I/O carriers house the SFPs on the Front I/O
panel (Multi-Service) and each 12xSFP I/O carrier can house up to 12 GE
SFPs. However since each 20G L2SS circuit pack must expand with no
more than 16 GE inputs/outputs, you must use two 12xSFP I/O carriers to
expand the number of SFPs available on the 20G L2SS circuit pack where
ports 41-52 from the first 2xSFP I/O carrier and ports 71-74 from the
second 2xSFP I/O carrier are used. Ports 75-82 from the second 12xSFP
I/O carrier (bottom 8 ports of the 12xSFP I/O carrier) are unavailable for
use and must not be equipped with GE SFPs.
• Four 12xSFP I/O carriers on a Front I/O panel (Multi-Service) are used for
two 20G L2SS circuit packs where:
— 16 GE ports on two 12xSFP I/O carriers are used for a 20G L2SS
circuit pack equipped in an odd slot (e.g. slot 1)
— 16 GE ports on other two 12xSFP I/O carriers are used for a 20G L2SS
circuit pack equipped in an even slot (e.g. slot 2)

Figure 2-7
Front I/O panel (Multi-Service) and 12xSFP I/O carriers
Alignment pins on the backplane and an insertion/ejector bar on the I/O

panels aid alignment during installation of the I/O modules.
The Front I/O panel (Multi-Service) supports both unprotected and 1+1
protected configurations.

The 20G L2SS circuit pack (NTK531HAE5) provides the following
functionality.
• up to two pluggable (XFP) 10GE interfaces (ports 1 to 2) and up to eight
pluggable (SFP) FE or GE interfaces (port 3 to 10)
achieved by L2 provisioning of virtual circuit segments (VCS) or EVPL
connections between Tx conditioning UNI and NNI ports or between NNI
ports
• LAN interfaces support:
— auto-detection of SFP modules, which are hot pluggable, unless
facility on corresponding I/O panel port already provisioned
— manual provisioning of SFP and XFP modules
— Tx conditioning UNIs for EPL emulated services
• WAN facilities
— up to 128 WAN facilities per circuit pack
GFP
support LO-VC3)
– virtual concatenation STS1-nv/HO_VC3-nv/LO_VC3-nv, where
n = 1 to 192, STS3c-nv/VC4-nv, where n = 1 to 64), LCAS support
when VCAT is enabled

— LACP support
— Tx conditioning UNIs support policing per port at 10 mbps granularity
• L2 connectivity
VLAN tag)
• equipment protection (1+1)
• SONMP and 802.1ab LLDP topology discovery
• has one NPU with a total of 128MB of memory shared for ingress and
egress buffers
• supports G.8032 ERP. Up to 20 rings per slot and maximum 64 rings per
shelf.
• When port conditioning is enabled on UNI ports, EVPL connections are
supported between such UNI and NNI ports or between NNI ports. When
port conditioning is enabled on UNI ports, it can either run on unprotected
EVPL connection or over G.8032 ERP for Tx conditioning UNI ports
protected using G.8032 ERP.



6500.
Note 2: For detailed information about 20G L2SS concepts, applications,
and engineering rules, see the 6500 Packet-Optical Platform Data
Application Guide, NTRN15BA.
The 20G L2SS circuit pack supports the following cross-connection types
when using the Site Manager Path Connections application:
The 20G L2SS circuit pack only supports the 2WAY (Bidirectional)
cross-connection type when using the Site Manager EVPL Connections
application.

The 20G L2SS circuit pack supports the following cross-connection rates
when Port conditioning is set to:
• Enabled and when using the Site Manager Path Connections
application (to create cross-connection between Tx conditioning UNI
ports)
— non-concatenated rates of STS1/LO VC3, STS1/HO VC3, and VC4
— concatenated rates of STS3c, STS12c/VC4-4c, STS24c/VC4-8c,
STS48c/VC4-16c, and STS192c/VC4-64c
— virtual concatenation (LCAS supported with VCAT enabled) at rates of
STS1-nv/LO VC3-nv (n = 1 to 192), STS1-nv/HO VC3-nv (n = 1 to
192), and STS3c-nv/VC4-nv (n = 1 to 64)
• Enabled (except for LAG UNI ports, which do not support port
conditioning) and when using the Site Manager EVPL Connections
application (to create cross-connection between a Tx conditioning UNI
port and a NNI port, or between two NNI ports)
— EVPL
EVPL cross-connections are not supported for LAG UNI ports.
Note the total capacity for cross-connections on the 20G L2SS circuit pack
Refer to Part 1 of Configuration - Provisioning and Operating, 323-1851-310,

for details on how to retrieve/change the Port conditioning parameter of a
20G L2SS circuit pack port.
L2 provisioning of virtual circuit segments (VCS) using the Site Manager Data
Services applications can also be used to configure a Layer 2 data
connection. Refer to the “Data services segment management provisioning”,
“Data services endpoint management provisioning”, and “Data services
endpoint mapping provisioning” sections in Part 2 of Configuration -
Bandwidth and Data Services, 323-1851-320, for related procedures. For
detailed information about 20G L2SS concepts, applications, and engineering
rules, refer to the 6500 Packet-Optical Platform Data Application Guide,
NTRN15BA.
Supported SFPs/XFPs
Table 2-6 on page 2-34 provides a list of the SFPs that are supported on the
20G L2SS circuit pack. Table 2-7 on page 2-35 provides a list of the XFPs that
are supported on the 20G L2SS circuit pack.

Table 2-6
Supported SFP modules for the 20G L2SS circuit pack (NTK531HA)
Facilities

— ETH — 1000Base-X (1.25Gb/s)

— 1000Base-X (1.25Gb/s)

SFP
— 1000Base-X (1.25Gb/s)

— 1000Base-T (1.00Gb/s)

— ETH — 1000Base-X (1.25Gb/s)


— 1000Base-X (1.25Gb/s) x= L, M, N, P, Q,
R, S, T

— ETH — 1000Base-X (1.25Gb/s)

— 1000Base-X (1.25Gb/s)
PFE GE 100-Base-FX 1310 nm SFP NTTP12ACE6

— ETH100 — 100Base-X (125Mb/s)
GE 100-Base-LX10 1310 nm SFP NTTP12BCE6

— 100Base-X (125Mb/s)

Table 2-7
Supported XFP modules for the 20G L2SS circuit pack (NTK531HA)

and Facilities
P10GEL 10GBASE-SR/SW, 850 nm, 30-300 m, MMF XFP (Note) NTTP81AA

10G-Base-LR/LW (1310nm, SMF, 10km), 0-70C XFP NTTP81BA

— 10.3125 Gb/s 10GBaseR (10GE)

— 10.3125 Gb/s 10GBaseR (10GE)
P10GSEL OC192/STM64 SR-1 / I-64.1 / 10GBase-LR,LW XFP NTTP80BA

OC192/STM64 IR-2 / S-64.2 / 10GBase-ER,EW XFP NTTP80DA

— 10.3125 Gb/s 10GBaseR (10GE)
P10GSOEL OC192/STM64 SR-1/ I-64.1 / 10GBase-LR,LW / OTU2 NTTP84BA

— ETH10G / 10G FC1200 XFP
— 10.3125 Gb/s 10GBaseR (10GE)
Note: MMF stands for multi-mode fiber.
The 20G L2SS circuit pack supports the following monitored entities:
• PM collection for ETH, ETH100, ETH10G, WAN, LCAS-enabled WAN,
and COS (ETH, ETH10G, and WAN) facilities
• operational measurements for ETH, ETH100, ETH10G, WAN,
LCAS-enabled WAN, LAG (ETH, ETH100, and ETH10G), COS (ETH,
ETH10G, WAN, and LAG), RLE (ETH, ETH100, WAN, and LAG), MEP
(ETH, ETH10G, WAN, and VCE), MIP (VSC), and VCE (ETH, ETH100,
and WAN) facilities

323-1851-520.

Alarms
Equipment alarms
• Pluggable I/O Panel Mismatch
• Pluggable I/O Panel Missing
• Pluggable I/O Panel Unknown
• Pluggable I/O Carrier 1 Missing
• Pluggable I/O Carrier 2 Missing
• Pluggable I/O Carrier 1 Fail
• Pluggable I/O Carrier 2 Fail
• Pluggable I/O Carrier 1 Unknown
• Pluggable I/O Carrier 2 Unknown
• Intercard Suspected - Pluggable I/O Carrier 1
• Intercard Suspected - Pluggable I/O Carrier 2
Pluggable alarms


Ethernet alarms
• LACP Failed
• Link Down
• Loss Of Signal
• Local Fault
• Remote Fault
• Remote Port OOS
• Signal Degrade
WAN alarms
• Link Down
• Signal Degrade
STS Path alarms
Layer 2 alarms


• Far End Client Signal Fail
• Remote Port OOS
Equipping rules
The following equipping rules apply to 20G L2SS circuit packs:
• is a single-slot 10-port interface.
• can be installed in slots 1-6 and 9-14 in all 14-slot shelf types with the
following exceptions:
— no SFP I/O panel is supported in packet-optical, optical, metro front
electrical, converged optical, Optical/rear electrical, or converged
optical/rear electrical shelf assembly.
— in optical/front electrical and converged optical/front electrical shelves,
SFP I/O panel is only supported in slots 1-4 and 9-12 (see “Front I/O
panel (Multi-Service)” on page 2-28 for more information on the I/O
panel).
ATTENTION

ATTENTION

NTK503KA).
this release.
• In a 14-slot shelf type, the 20G L2SS circuit pack is not supported when
using the MXC cross-connect circuit pack (NTK557TB).

• the LO_VC3 cross-connects are only supported when using a low-order

VT1.5/VC-12 cross-connect, 240G+/80G VT1.5/VC-12 (240/80)
(NTK557GAE5/NTK557GS) cross-connect, or 240G+ STS-1/VC-3
(240/0) (NTK557EAE5/NTK557ES) cross-connect circuit pack.
• high flow cooling fan modules (NTK507LDE5, NTK507MDE5, NTK507LS,
or NTK507MS) are required when high performance circuit packs such as
20G L2SS circuit packs are equipped in a 14-slot shelf.
Engineering rules
For more information about 20G L2SS engineering rules, refer to 6500
specifications for the 20G L2SS optical interface circuit packs.

Table 2-8
Technical specifications for 20G L2SS optical interface circuit packs
Parameter 20G L2SS (NTK531HAE5)

— 2 W to typical power value and 3 W to power budget for each XFP module with reach less than
IR-2/S-64.2b.
or greater.
323-1851-180.
Note 6: For optical XFP specifications, see chapter 2 of Pluggable Datasheets and Reference,
323-1851-180.

L2 MOTR 2xXFP/10xSFP circuit pack (NTK531VAE5)

Overview
The L2 MOTR 2xXFP/10xSFP circuit pack (also known as L2 MOTR) uses up
to ten SFP optics for the GE/FE interfaces and up to two XFP optics for 10GE
LAN or OTM2 interfaces from the circuit pack faceplate to provide up to 30
Gbit/s of bidirectional Layer 2 (L2) aggregation (or 50 Gbit/s if considering the
20G of M2M connectivity).
Figure 2-8 shows the faceplate of a L2 MOTR circuit pack. Figure 2-9 on page
2-42 provides functional block diagram of the L2 MOTR circuit pack.
Figure 2-8
L2 MOTR circuit pack faceplate
Red triangle (Fail)

2x10G XFP
10xGE SFP
L2 MOTR
Fail
Ready
In Use
1

2
3 Tx
Rx
4 Tx
Rx
5 Tx
Rx
6 Tx
Rx
7 Tx
8 Tx
Rx
9 Tx
Rx
10 Tx
Rx
11 Tx
Rx
12 Tx
Rx
Hazard
level:
R99
EEEEE99999
S/N NT030MEE9999E
NTUD99EE
Type A

Figure 2-9
L2 MOTR circuit pack block diagram (NTK531VAE5)
PHY OTN XFP 1

Mapper
OTN
PHY Mapper XFP 2
PHY SFP 3
PHY SFP 4
Mate
PHY SFP 5
Backplane
PHY SFP 6
PHY SFP 7
Ethernet Switch
PHY SFP 8
PHY SFP 9
PHY SFP 10
Mate
PHY SFP 11
PHY SFP 12
Processor Power
Sync Supply
Module
Legend

The L2 MOTR circuit pack (NTK531VAE5) provides the following functionality.
• pluggable line or client ports via XFP optics (ports 1 and 2):
— up to two 10G XFP-based line or client ports (ports 1 and 2) supporting
10GE LAN, LAG, or OTM2 (10.7G, 11.05G and 11.09G) modes.
Note: Depending on the XFP that is being used in port 1 or 2, the port can
either run 10GE over OTM2 (10.7G - GFP/OPU2, 11.05 - OPU1e or 11.09
- OPU2e) G.709 wrapped line interfaces or run native 10GE. When
running native 10GE (no OTM2 facility configured) and the port is set as a
UNI, it then becomes a client interface, not a line interface.
— offers SR/SW, LR/LW, and ER/EW reach

— offers fixed C-band 100 GHz-compliant DWDM XFP line interfaces
(1528.77 nm to 1564.68 nm)
— offers tunable C-band 50 GHz-compliant DWDM XFP tunable line
— offers multirate 1550 XFP line interfaces (9.95G to 11.1G)
— supports up to 175 km reach (when the OTM2 line port is equipped
with the DWDM XFPs supported by the L2 MOTR circuit packs such
as NTK588xxE5 or NTK589xxE6 or less reach when equipped with
NTK583AAE6, NTK583AB, or NTK587xxE5 XFPs)
— offers multirate long haul CWDM XFP line interfaces
— FEC provisionable to Off, SCFEC and RS8
Note: The RS8 FEC algorithm is also known as ITU-T G.709 RS-8. The
SCFEC FEC algorithm is also known as ITU-T G.975 I.4.
— facility loopbacks on 10GE facility, facility loopbacks on OTM2 facility

• client support (FE, SX, LX, ZX, BX, CWDM, and electrical) via up to 10
SFP optics in ports 3 to 12:
— different SFP types. Up to 10 GbE SFPs (full rate and sub-rate
support) providing ETH and ETH100 client facility types
— facility loopbacks on GE facility

• single circuit pack regeneration solution since L2 MOTR circuit pack

supports two line ports (OTU and ODU are both terminated)
• operates at the layer 2 (data link layer) - 64 byte to 9600 byte Ethernet
frames (jumbo frames support)
• supports E-LINE Ethernet Virtual Private Line (EVPL) service between Tx
conditioning UNI and NNI ports or between NNI port:
— simplified provisioning model (i.e. no VCS/VCE provisioning required
by customer)
— full rate or sub-rate with PAUSE flow control
— signal conditioning (client signal fail via Y.1731 format message)
• E-LINE, E-LAN L2 switched service
— for consistency and simplification L2 provisioning aligns with the L2SS
— 802.1q, 802.1ad
— unicast, multicast and broadcast support
— eight CoS (two strict priority, six weighted round robin)
— P-bits based service priority
— Tx conditioning UNI ports allowing EPL emulation (EVPL) over a
G.8032 ERP protected infrastructure
— forwarding database (FDB) supports up to 32000 dynamic MAC
• LACP support
• SONMP and 802.1ab LLDP topology discovery
• provides an internal buffer pool of 2,097,152 bytes. Consequently, if a
uniform stream of 64 byte frames is being processed, a maximum of
16,384 frames can be simultaneously processed. If a uniform stream of
1522 byte frames is being processed, a maximum of 1365 frames can be
simultaneously processed.
VLAN tag)
• GE port mirroring (e.g. mirroring port on a local L2 MOTR circuit pack
configured as a test access port)

• 802.1ag CCMs, Link Trace, Loopback and defects

• Y.1731 Ethernet AIS generation
• extended service support when in “L2EXTENDED” mode; Increasing
service scalability (1024 VCS, 3072 VCE, 3072 endpoint maps, SVID
range of 1 to 2000)
ATTENTION
When in “L2EXTENDED” mode, 1+1 OTN Protection, SVID swapping
(changing the SVID on NNI ports of the same VCS), Policing, ETH-OAM
Up/Down MEPs and MIPs, and EVPL connection provisioning is not
supported. For more information, refer to Parts 1 and 2 of Configuration -
Bandwidth and Data Services, 323-1851-320 and Parts 1 and 2 of
• protection support
— supports 1+1 OTN line protection on both line ports. The support
includes:
– 1+1 protected configurations using two 10G line ports on different
L2 MOTR circuit packs that require that the two circuit packs be
equipped in consecutive slots (only the GE client ports in the odd
slot of L2 MOTR circuit packs can be used if the clients are
unprotected). Provisioning inter-card protection blocks the
provisioning of M2M ports; port 91 if port 1 is used on each L2
MOTR circuit pack to create 1+1 OTN line protection and port 92 if
port 2 is used on each L2 MOTR circuit pack to create 1+1 OTN
line protection as they are used by the protection mechanism. The
first circuit pack must be in an odd slot and the second circuit pack
must be in the adjacent even slot. For the 2-slot shelf, that is slots
{1,2}. For the 6500-7 packet-optical or 7-slot shelf, that is slots
{1,2}, {3,4}, {5,6}. For the 14-slot shelf, that is slots {1,2}, {3,4},
{5,6}, {7,8}, {9,10}, {11,12}, and {13,14}. For the 32-Slot shelf, that
is slots {1,2}, {3,4}, {5,6}, {7,8}, {11,12}, {13,14}, {15,16}, {17,18},
{21,22}, {23,24}, {25,26}, {27,28}, {31,32}, {33,34}, {35,36},
{37,38}. Also the ports must match (for example, port 1 from slots
1 and 2 are acceptable members of a protection group, however
port 1 from slot 1 and port 2 from slot 2 are not acceptable
members of a protection group).

– 1+1 protected configurations using a intra-card (single-card)

protection where the two 10G line ports are equipped on the same
L2 MOTR circuit pack (provisioning intra-card protection allows the
provisioning of M2M ports (ports 91 and 92)). Port 1 must be the
working port and port 2 must be the protection port. The intra-card
line protection can be configured on any L2 MOTR circuit pack
located in an odd or even slot.
– supports protection exerciser
— supports 1+1 LAG protection
– The 1+1 LAG protected configuration is using two LAG client ports
on different L2 MOTR circuit packs that require that the two circuit
packs be equipped in consecutive slots. The first circuit pack must
be in an odd slot and the second circuit pack must be in the
adjacent even slot. For the 2-slot shelf, that is slots {1,2}. For the
6500-7 packet-optical or 7-slot shelf, that is slots {1,2}, {3,4}, {5,6}.
For the 14-slot shelf, that is slots {1,2}, {3,4}, {5,6}, {7,8}, {9,10},
{11,12}, and {13,14}. For the 32-Slot shelf, that is slots {1,2}, {3,4},
{5,6}, {7,8}, {11,12}, {13,14}, {15,16}, {17,18}, {21,22}, {23,24},
{25,26}, {27,28}, {31,32}, {33,34}, {35,36}, {37,38}. Also the ports
must match (for example, port 1 from slots 1 and 2 are acceptable
members of a protection group, however port 1 from slot 1 and port
2 from slot 2 are not acceptable members of a protection group).
1+1 LAG is designed to operate either with 1+1 OTM or G.8032
ERP protection configured on mate L2 MOTR circuit packs.
VCEs/EVPL connections provisioned on 1+1 LAG protected ports
are only configured on the odd slot circuit packs and get
automatically configured on the even slot card. For this reason, it
is important to note that G.8032 ERP configurations that drop
traffic to a 1+1 LAG must use the same G.8032 ERP LAN port
number on both cards.
— supports G.8032 ERP. Up to 40 rings per slot and maximum 80 rings
per 2-slot shelf, 255 rings per 7-slot, 14-slot, or 32-slot shelf, and 240
rings per 6500-7 packet-optical shelf
— supports 802.1ag triggered G.8032 ERP protection (configurable on a
per ring port basis)
• synchronization support
— can be shelf timed, internally timed using on-board Stratum 3 clock, or
line timed from an OTM2 line port (no sync messaging, must provision
the quality level override). Also supports 10GE line sync with Ethernet
Sync messaging.
— no Shelf X-Conn circuit pack required when internally or line timed

• GCC0 and GCC1 on OTM2 line facility Limit of two total GCC ports shared
amongst two OTM2-configured line ports on a single L2 MOTR circuit
pack.
• backplane access
— up to 20G of traffic to mate card. Backplane access is available in 10G
granularity, as such for slots with 12.5G capacity to mate, 10G can be
utilized by the L2 MOTR. 1+1 OTN protection utilizes 10G of backplane
access capacity (if 1+1 inter-card OTN protection is provisioned, the
M2M ports (91 and 92) are not provisionable and if 1+1 intra-card
protection is provisioned, the M2M ports (91 and 92) can be
provisioned between the L2 MOTR cards).
Note: When using certain 14-slot shelf assemblies (NTK503AA,
NTK503BAE5, NTK503CAE5, NTK503ABE5, NTK503ACE5,
NTK503BCE5, or NTK503CCE5), the maximum mate-to-mate L2 MOTR
bandwidth is 12.5G when using the Low-speed slots (1-4,11-14) and 20G
when using the High-speed slots (5-10).

when deploying a L2 MOTR circuit pack:
equipped with or without cross-connect circuit packs.
• In a 14-slot shelf type, you cannot provision a L2 MOTR circuit pack in slot
7 or 8 if one of these slots already contains a cross-connect circuit pack.
• In a 14-slot shelf type, you cannot provision a cross-connect circuit pack
in slot 7 or 8 if one of these slots already contains a L2 MOTR circuit pack
(or any other broadband circuit pack).
• In a 14-slot shelf type, when the L2 MOTR circuit packs are installed in slot
7 or 8, only Broadband circuit packs or Photonic circuit packs can be
provisioned in the other interface slots (slots 1 to 6 and 9 to14), as
PKT/OTN or MSPP interface circuit packs require a cross-connect circuit
pack. See Part 1 of 6500 Planning, NTRN10EY (Chapter 3) for a full list of
supported Broadband and Photonic circuit packs.
Note 1: For detailed information about L2 MOTR concepts, applications,


The L2 MOTR circuit pack only supports the 2WAY (Bidirectional)
cross-connection type when using the Site Manager EVPL Connections
application.
The L2 MOTR circuit pack only supports the EVPL cross-connection rate
when using the Site Manager EVPL Connections application, and when Port
conditioning is set to Enabled (except for LAG UNI ports, which do not
support port conditioning). Cross-connections are supported between a Tx
conditioning UNI port and a NNI port, or between two NNI ports. EVPL
cross-connections are not supported for LAG UNI ports.
Refer to Part 1 of Configuration - Provisioning and Operating, 323-1851-310,

for details on how to retrieve/change the Port conditioning parameter of a
L2 MOTR circuit pack port.
L2 provisioning of virtual circuit segments (VCS) using the Site Manager Data
Services applications can also be used to configure a Layer 2 data
connection. Refer to the “Data services segment management provisioning”,
“Data services endpoint management provisioning”, and “Data services
endpoint mapping provisioning” sections in Part 2 of Configuration -
Bandwidth and Data Services, 323-1851-320, for related procedures. For
detailed information about L2 MOTR concepts, applications, and engineering
rules, refer to the 6500 Packet-Optical Platform Data Application Guide,
NTRN15BA.

Supported SFPs/XFPs
Table 2-9 provides a list of the SFPs that are supported on the L2 MOTR
circuit pack. Table 2-10 provides a list of the XFPs that are supported on the
L2 MOTR circuit pack.
Table 2-9
Supported SFP modules for the L2 MOTR circuit pack (NTK531VAE5)
Facilities (Note 1)
P2G5 OC-48/STM-16 DWDM SFPs NTK585xx where

— ETH — 1000Base-X (1.25 Gb/s) xx= see Note 2

— ETH — 1000Base-X (1.25Gb/s)

— 1000Base-X (1.25Gb/s)

SFP
— 1000Base-X (1.25Gb/s)

— 1000Base-T (1.00Gb/s)

— ETH — 1000Base-X (1.25Gb/s)


— 1000Base-X (1.25Gb/s) x= L, M, N, P, Q,
R, S, T

— ETH — 1000Base-X (1.25Gb/s)

— 1000Base-X (1.25Gb/s)

Table 2-9
Supported SFP modules for the L2 MOTR circuit pack (NTK531VAE5) (continued)
Facilities (Note 1)
PSFP Multirate 15xx.yy (or 16xx.yy) nm DWDM 1600 NTK586xxE5

— ETH ps/nm SFPs where xx= see
— 1000Base-X (1.25 Gb/s) Note 3
1 GIG, Single Fiber SM, LC Connector, 80km, XCVR-080U49

1550 nm Rx/1490 nm Tx SFP
— 1000Base-X (1.25 Gb/s)

— 1000Base-X (1.25 Gb/s)

Table 2-9
Supported SFP modules for the L2 MOTR circuit pack (NTK531VAE5) (continued)
Facilities (Note 1)
PFE 100-Base-FX 100 Mbit/s 1310 nm multimode 2 NTTP08AC

— ETH100 km
— 100Base-X (125Mb/s)
100-Base-LX FE 1310 nm 10km NTTP08SD

— 100Base-X (125Mb/s)
100-Base-BX 10-U Bidirectional-upstream, 1310 NTTP09BD

nm Tx, 10 km
— 100Base-X (125Mb/s)
100-Base-BX 10-D Bidirectional-downstream, NTTP10BD

1530 nm Tx, 10 km
— 100Base-X (125Mb/s)
10/100-BaseT RJ45 SFP NTTP61BAE6

— 100Base-T (100Mb/s)
— 10Base-T (10 Mb/s)
GE 100-Base-FX 1310 nm SFP NTTP12ACE6

— 100Base-X (125Mb/s)

— 100Base-X (125Mb/s)
Note 1: On the L2 MOTR circuit packs, ports 1 and 2 are the line interface ports (10GE LAN, or OTM2
(at 10.7G, 11.05G or 11.09G)) or client interface ports (10GE LAN) and ports 3 to 12 are the client
interface ports (GE/FE).
Note 3: Refer to Planning - Ordering Information, 323-1851-151, Chapter 3: Table “Multirate
DWDM/CWDM pluggable optics modules (SFP)”, for the complete list of ordering codes.

Table 2-10
Supported XFP modules for the L2 MOTR circuit pack (NTK531VAE5)
Facilities (Note 1)

— ETH10G (ADJ) XFP (Note 2)
— 10.3125 Gb/s 10GBaseR (10GE)
10G-Base-LR/LW (1310nm, SMF, 10km), 0-70C NTTP81BA

XFP
— 10.3125 Gb/s 10GBaseR (10GE)

— 10.3125 Gb/s 10GBaseR (10GE)
P10GSEL OC192/STM64 SR-1 / I-64.1 / 10GBase-LR,LW NTTP80BA

— ETH10G (ADJ) XFP
OC192/STM64 IR-2 / S-64.2 / 10GBase-ER,EW NTTP80DA

XFP

Table 2-10
Supported XFP modules for the L2 MOTR circuit pack (NTK531VAE5) (continued)
Facilities (Note 1)

— OTM2 (ADJ), ETH10G 10GBase-LR,LW
(WAN Note 3) — 10.709 Gb/s OTU2
— 10.3125 Gb/s 10GBaseR (10GE)
9.95G-11.09G multirate, 1550 nm, SMF, 40 km NTTP84AAE6

XFP
— 10.709 Gb/s OTU2
— 10.3125 Gb/s 10GBaseR (10GE)

— 10.709 Gb/s OTU2
— 10.3125 Gb/s 10GBaseR (10GE)
Multirate 15xx.yy nm EML DWDM 1600 ps/nm NTK587Ax to

XFP NTK587Dx,
— 10.709 Gb/s OTU2 where x= see
Note 5
— 10.3125 Gb/s 10GBaseR (10GE)
9.95G-11.09G multirate, 1550 nm, SMF, 80 km NTTP81KAE6

XFP
— 10.709 Gb/s OTU2
— 10.3125 Gb/s 10GBaseR (10GE)

D, E, F, G, or H
— 10.3125 Gb/s 10GBaseR (10GE)

Table 2-10
Supported XFP modules for the L2 MOTR circuit pack (NTK531VAE5) (continued)
Facilities (Note 1)
PXFP Multirate 15xx.yy nm EML DWDM 800 ps/nm NTK587Ex to

— OTM2 (ADJ), ETH10G XFP NTK587Hx,
(WAN Note 3) — 10.709 Gb/s OTU2 where x= see
Note 5
— ETH10G (ADJ) (Note 4) — 11.05 Gb/s OTU1e/11.09 Gb/s OTU2e
— 10.3125 Gb/s 10GBaseR (10GE)
Multirate 15xx.yy nm DWDM 3200 ps/nm XFP NTK588xx,

— 10.709 Gb/s OTU2 where xx= see
Note 6
Multirate 1528.38 nm to 1568.77 nm (1-88) NTK583AAE6

50GHz Tunable DWDM XFP
— 10.709 Gb/s OTU2
— 10.3125 Gb/s 10GBaseR (10GE)
Multirate 1528.38 nm to 1568.77 nm (1-88) NTK583AB

50GHz Tunable Type 2 DWDM XFP
— 10.709 Gb/s OTU2
— 10.3125 Gb/s 10GBaseR (10GE)
Multirate 15xx.yy – 15xx.yy Tunable Dispersion NTK589xxE6

Tolerant DWDM 3200 ps/nm XFP where xx= see
Note 1: On the L2 MOTR circuit packs, ports 1 and 2 are the line interface ports (10GE LAN, or OTM2
(at 10.7G, 11.05G or 11.09G)) or client interface ports (10GE LAN) and ports 3 to 12 are the client
interface ports (GE/FE).
to “10.7G - GFP/OPU2 (Standard MAC transparent)”.
Note 4: The standalone ETH10G facilities are supported on the PXFP variants of NTK583AA/AB and
NTK587Ex to NTK587Hx only. They are not supported on other PXFP variants.
DWDM/CWDM pluggable optics modules (XFP)”, for the complete list of ordering codes.
Note 6: Refer to Planning - Ordering Information, 323-1851-151, Chapter 7: Table “Multirate DWDM
pluggable optics modules (XFP) (manufacture discontinued)”, for the complete list of ordering codes.

The L2 MOTR circuit pack supports the following monitored entities:
• OTM2 line interface
— PM collection for OTU2 layer
— PM collection for ODU2 layer
— PM collection for Physical layer
• Client interfaces
— PM collection for ETH, ETH100, ETH10G, WAN, and LCAS-enabled
WAN facilities
— operational measurements for ETH, ETH100, ETH10G, WAN, LAG
(ETH, ETH100, ETH10G, and WAN), MEP (ETH, ETH10G, WAN, and
VCE), MIP (VSC), VCE (ETH, ETH100, ETH10G, WAN, and LAG),
and RLE (ETH, ETH100, ETH10G, WAN, and LAG) facilities
Note: If you edit the VCE or its attributes, the L2 MOTR circuit pack VCE OM
counter clears.

323-1851-520.
Alarms
Equipment alarms
• Timing Generation Entry to Freerun
• Timing Generation Entry to Holdover

• Timing Generation Failure to Lock
Pluggable alarms
OTM facility alarms

• Far End Protection Line fail
• GCC0 Link Fail
• GCC1 Link Fail
• Lockout Active
• Loss Of Signal
• OTU BDI
• ODU AIS
• ODU LCK
• ODU OCI
• ODU BDI
• OPU AIS
• Protection Exerciser Complete


• Protection Exerciser Fail
• Protection Switch Complete - Revertive
• Pre-FEC Signal Fail
Ethernet alarms
• Local Fault
• LACP Failed
• Link Down
• Loss Of Signal
• Remote Fault
• Remote Port OOS
• Signal Degrade
• Remote Client Circuit Pack Mismatch - Pluggable
• Remote Client Circuit Pack Missing - Pluggable
• Remote Client Circuit Pack Failed - Pluggable
• Remote Client Circuit Pack Unknown - Pluggable
• Remote Client High Received Optical Power

• Remote Client Low Received Optical Power

• Remote Line High Received Optical Power
• Remote Line Low Received Optical Power
• Remote Power Supply 1 Missing
• Remote Power Supply 2 Missing
• TX Manual Provisioning Required
• TX Tuning in Progress
WAN alarms
• Link Down
• Signal Degrade
Photonic alarms
• Adjacency Mismatch
• Duplicate Adjacency Discovered
Layer 2 alarms
• Link Aggregation Group Partial Fail
• Provisioning Mismatch
• Time Out
• Cross-connect error
• CCM error
• Remote CCM error
• MAC Status Defect
Layer 2 1+1 LAG Protection alarms

• Far End Client Signal Fail


• Remote Port OOS
Common alarms
Equipping rules
The following equipping rules apply to L2 MOTR circuit packs:
• can be equipped in any slot (1-14 except slots 7 and 8 if cross-connect
circuit packs are provisioned in slots 7 and 8) of the 14-slot optical,
converged optical, optical/front electrical, converged optical/front
electrical, optical/rear electrical, converged optical/rear electrical shelves.
Can be also equipped in slots 1-6 and 9-14 of 14-slot packet-optical shelf
(slots 7 and 8 of a 14-slot packet-optical shelf (NTK503SA) cannot be
equipped with this circuit pack).
ATTENTION
The L2 MOTR circuit packs are not supported in the Metro front electrical
shelf.
• can be equipped in slots 1-8, 11-18, 21-28, and 31-38 of the 32-slot
packet-optical shelf.
• can be equipped in slots 1 to 7 of the 7-slot optical shelf (NTK503PAE5 or
NTK503KA).
• can be equipped in slots 1 to 6 of the 6500-7 packet-optical shelf
(NTK503RA).
• can be equipped in slots 1 and 2 of the 2-slot shelf.
• 14 L2 MOTR circuit packs per 14-slot shelf (full-filled) are supported
regardless of the type of power input cards used (2x50A, 40A, or 60A).
Engineering rules
For more information about L2 MOTR engineering rules, refer to 6500
specifications for the L2 MOTR optical interface circuit packs.

Table 2-11
Technical specifications for L2 MOTR optical interface circuit packs
Parameter L2 MOTR (NTK531VAE5)

range in the case of AC-powered equipment. These values must be used in sizing feeders and
estimating theoretical maximum power draw.
IR-2/S-64.2b.
or greater.
323-1851-180.
323-1851-180.

Latency

eMOTR circuit packs (NTK536AA, NTK536AB, NTK536BE, NTK536FA,

NTK536FB)
Overview
The eMOTR 4xXFP/8xSFP+, eMOTR 4xXFP/8xSFP+/32xSFP, and eMOTR
Edge 4xXFP/2xSFP+/8xSFP circuit packs (also known as eMOTR) are
high-density, low-cost, multi-port Layer 2 OTR circuit packs and provide
pluggable optics from the circuit pack faceplate for bidirectional Layer 2 (L2)
aggregation. The following variants of eMOTR circuit packs are supported:
• eMOTR 4xXFP/8xSFP+ (NTK536AA and NTK536AB)
These eMOTR variants use up to eight SFP+ optics and up to four XFP
optics. The NTK536AB circuit pack is the enhanced variant of NTK536AA
eMOTR circuit pack that supports line synchronization mode when mating
with 40G OCLD (NTK539PxE5) or Wavelength-Selective 40G OCLD
(NTK539RxE5) circuit packs.
• eMOTR 4xXFP/8xSFP+/32xSFP (NTK536FA, and NTK536FB)
These eMOTR variants use up to eight SFP+ optics, up to 32 SFP optics,
and up to four XFP optics. The NTK536FB circuit pack is the enhanced
variant of NTK536FA eMOTR circuit pack that supports line
synchronization mode when mating with 40G OCLD (NTK539PxE5) or
Wavelength-Selective 40G OCLD (NTK539RxE5) circuit packs.
(NTK539RxE5) circuit packs.
• eMOTR Edge 4xXFP/2xSFP+/8xSFP (NTK536BE)
This eMOTR variant uses up to two SFP+ optics, up to eight SFP optics,
and up to four XFP optics. Unlike other eMOTR variants (NTK536AA,
NTK536AB, NTK536FA, and NTK536FB), the NTK536BE variant
— cannot be mated with 40G OCLD (NTK539PxE5) or
Wavelength-Selective 40G OCLD (NTK539RxE5) circuit packs.
— can be used in an extended temperature environment.
Note: Unless otherwise specified, eMOTR in this document refers to
eMOTR (NTK536AA, NTK536AB, NTK536FA, NTK536FB) and eMOTR
Edge (NTK536BE) variants.

The following figures illustrate circuit packs’ faceplates and block diagrams:
• Figure 2-10 on page 2-64 shows the faceplate of an NTK536AA or
NTK536AB variant of eMOTR circuit packs.
• Figure 2-11 on page 2-65 shows the faceplate of an NTK536FA or
NTK536FB variant of eMOTR circuit packs.
• Figure 2-12 on page 2-66 shows the faceplate of an NTK536BE variant of
eMOTR circuit packs.
• Figure 2-13 on page 2-67 provides the functional block diagram of an
NTK536AA or NTK536AB variant of eMOTR circuit packs.
NTK536FA or NTK536FB variant of eMOTR circuit packs.
NTK536BE variant of eMOTR circuit packs.

Figure 2-10
eMOTR circuit pack faceplate (NTK536AA or NTK536AB variant)
Red triangle (Fail)


Transmit/receive SFP+ or SFP dual LC connector

- Used to communicate Rx Loss of Signal/optical module fail

Figure 2-11
eMOTR circuit pack faceplate (NTK536FA or NTK536FB variant)
Red triangle (Fail)



- Used to communicate Rx Loss of Signal/optical module fail

Figure 2-12
eMOTR circuit pack faceplate (NTK536BE variant)
Red triangle (Fail)



Figure 2-13
eMOTR circuit pack block diagram (NTK536AA or NTK536AB variant)
PHY **SFP+ 1
PHY **SFP+ 2
PHY **SFP+ 3
40G
Left
OTN
Mate PHY **SFP+ 4
Mapper
PHY **SFP+ 5
PHY **SFP+ 6
Backplane
PHY **SFP+ 7
PHY **SFP+ 8
Ethernet Switch
XFP 9
XFP 10
40G OTN
Right OTN Mapper
Mate Mapper
XFP 11
XFP 12
Processor Power
Sync Supply
Module
**means that the port can accommodate either SFP or SFP+ devices.
Legend
OTN Optical transport network

Figure 2-14
eMOTR circuit pack block diagram (NTK536FA or NTK536FB variant)
PHY **SFP+ 1
PHY **SFP+ 2
PHY **SFP+ 3
Left 40G
Mate OTN
Mapper PHY **SFP+ 4
PHY **SFP+ 5
PHY **SFP+ 6
Backplane
PHY **SFP+ 7
PHY **SFP+ 8
Ethernet Switch
XFP 9
OTN XFP 10
Mapper
XFP 11
40G
OTN XFP 12
Right
Mate Mapper
PHY SFP 21
. . .
.. .. ..
PHY
SFP 36
PHY SFP 41
. . .
.. .. ..
PHY SFP 56
Processor Power
Sync Supply
Module
Legend

Figure 2-15
eMOTR circuit pack block diagram (NTK536BE variant)
PHY SFP 1
PHY SFP 2
PHY SFP 3
PHY SFP 4
Mate PHY SFP 5
PHY SFP 6
PHY SFP 7
PHY SFP 8
Backplane
PHY **SFP+ 9
Ethernet Switch
PHY **SFP+ 10
XFP 11
XFP 12
OTN
Mate Mapper
XFP 13
XFP 14
Processor Power
Sync Supply
Module
Legend

The eMOTR circuit packs (NTK536AA, NTK536AB, NTK536BE, NTK536FA,
NTK536FB) provide the following functionality. The following table shows
supported ports/pluggables/facilities/rates for different variants of eMOTR
circuit packs:
Table 2-12
eMOTR ports/pluggables/facilities/rates
Ports Pluggables/facilities/rates
eMOTR eMOTR eMOTR

(NTK536AA/NTK536AB) (NTK536FA/NTK536FB) (NTK536BE)
XFP pluggables
9 to 12 Up to four XFP pluggables Up to four XFP pluggables N/A

supporting: supporting:
• OTU2 (10.7 Gb/s) • OTU2 (10.7 Gb/s)
• OTU2e (11.09 Gb/s) • OTU2e (11.09 Gb/s)
• 10GE LAN (10.3125 Gb/s) • 10GE LAN (10.3125 Gb/s)
11 to 14 N/A N/A Up to four XFP pluggables

supporting:
• OTU2 (10.7 Gb/s)
• OTU2e (11.09 Gb/s)
• 10GE LAN (10.3125 Gb/s)
SFP/SFP+ pluggables
1 to 8 Up to eight SFP/SFP+ Up to eight SFP/SFP+ Up to eight SFP pluggables

pluggables supporting: pluggables supporting: supporting:
• 10GE (10.3125 Gb/s) SFP+ • 10GE (10.3125 Gb/s) SFP+ • 1000Base-X (1.25 Gb/s) SFP
• 1000Base-X (1.25 Gb/s) SFP • 1000Base-X (1.25 Gb/s) • 1000Base-T (1.25 Gb/s) SFP
SFP • 100Base-T (125 Mb/s) SFP
• 100Base-T (125 Mb/s) SFP • 100Base-X (125 Mb/s) SFP
(only on ports 5 to 8) (only applicable to
• 100Base-X (125 Mb/s) SFP NTTP12BCE6 SFP)
(only on ports 5 to 8) (only
applicable to NTTP12BCE6
SFP)

Table 2-12
eMOTR ports/pluggables/facilities/rates
Ports Pluggables/facilities/rates
eMOTR eMOTR eMOTR

(NTK536AA/NTK536AB) (NTK536FA/NTK536FB) (NTK536BE)
9 and 10 N/A N/A Up to two SFP/SFP+

pluggables supporting:
• 10GE (10.3125 Gb/s) SFP+
• 1000Base-T (1.25 Gb/s) SFP
• 1000Base-X (1.25 Gb/s) SFP
• 100Base-T (125 Mb/s) SFP
• 100Base-X (125 Mb/s) SFP
(only applicable to
NTTP12BCE6 SFP)
• 21 to 36 N/A Up to 32 SFP pluggables N/A

• 41 to 56 supporting:
• 100Base-X (125 Mb/s) SFP
(not applicable to
NTTC12BCE6 SFP)
• 1000Base-X (1.25 Gb/s)
SFP

• pluggable XFP optics:

— offers fixed C-band 100 GHz-compliant DWDM XFP interfaces
(1528.77 nm to 1564.68 nm)
— offers tunable C-band 50 GHz-compliant DWDM XFP tunable
— offers multirate 1550 XFP interfaces (9.95G to 11.1G)
— supports up to 175 km reach (when the OTU2 or OTU2e port is
equipped with the DWDM XFPs supported by the eMOTR circuit packs
such as NTK589xxE6 or less reach when equipped with
NTK583AAE6, NTK583AB, or NTK587xxE5 XFPs)
— offers multirate long haul CWDM XFP interfaces
— FEC provisionable to Off and RS8
Note: The RS8 FEC algorithm is also known as ITU-T G.709 RS-8.
— facility loopbacks on 10GE, OTU2, and OTU2e facility (also supported

on OTU3 facility of the mated 40G OCLD or Wavelength-Selective 40G
OCLD circuit pack)
• pluggable SFP+ or SFP optics:
— offers multirate 1310 SFP+ interfaces
— offers multirate DWDM/CWDM SFP interfaces
— offers 850, 1310, 1490, 1550 SFP interfaces
— auto-detection of SFP/SFP+ modules, which are hot pluggable
— manual provisioning of SFP/SFP+ modules
— facility loopbacks on GE and 10GE facilities
Note: Provisioning a loopback will overwrite an existing loopback. It is not
recommended to put one loopback on another.
• NTK536AA and NTK536AB circuit packs can be used interchangeably

and also mated together. NTK536FA and NTK536FB circuit packs can be
also used interchangeably and mated together.
• single circuit pack regeneration solution since eMOTR circuit packs
support four XFP ports (OTU and ODU are both terminated)
• operates at the layer 2 (data link layer) - 64 byte to 9600 byte Ethernet
frames (jumbo frames support)

• supports packet switching services. Some examples are:

— E-LINE, E-LAN, E-Tree L2 switched service
— 802.1q, 802.1ad
— unicast, multicast and broadcast support
— eight CoS
— P-bits based service priority
— forwarding database (FDB) supports up to 32000 dynamic MAC
— Multiprotocol Label Switching (MPLS)
— Ingress resolved CoS configuration at the sub-port level
— Synthetic Loss Measurement (SLM)
— OTN Signal Degrade Detection within MPLS networks
— Egress scheduling enhancements
— Active/standby LAG protection
• operate at the Ethernet (L2) layer to deliver up to 1000 Ethernet P2P or
A2A services.
• LACP support
• 802.1ab LLDP topology discovery
• supports photonic adjacency (ADJ facility), facility AINS, and facility
maintenance state
• supports SPLI
• L1Sync and Ethernet Sync Message Channel (ESMC)
— VLAN steering, push and pop
— support of 88A8 Ethertype values
— Layer 2 control frame tunneling
• Equipment groups (NTK536AA, NTK536AB, NTK536FA, NTK536FB
variants)
These variants of eMOTR circuit packs use equipment groups. By default,
each eMOTR circuit pack inserted in a 6500 shelf is automatically
provisioned in an independent equipment group. Equipment groups can
be composed of up to two eMOTR circuit packs (same type) and up to two
40G OCLD (NTK539PxE5) or Wavelength-Selective 40G OCLD
(NTK539RxE5) circuit packs (quad or half-quad configuration) where

mate-to-mate bandwidth is automatically provisioned between eMOTR

circuit packs and between eMOTR and 40G OCLD or
Wavelength-Selective 40G OCLD circuit packs (for allowable slots, see
Table 2-13 on page 2-75 and Table 2-14 on page 2-76). From a Layer 2
provisioning perspective, the user only provisions traffic on the faceplate
and 10GE backplane ports mated to the 40G OCLD (or
Wavelength-Selective 40G OCLD) circuit packs, no specific Layer 2
provisioning is required to flow traffic between eMOTR circuit packs in the
same equipment group. There is 80 Gbps of traffic capacity between
adjacent eMOTR circuit packs in the same equipment group.
Note: All supported functionalities between NTK536AA and NTK536AB
variants or between NTK536FA and NTK536FB variants of eMOTR circuit
packs are equivalent.
• Equipment groups (NTK536BE variant)

This variant of eMOTR circuit pack also uses equipment groups. By
default, each eMOTR circuit pack inserted in a 6500 shelf is automatically
provisioned in an independent equipment group. Equipment groups can
be composed of up to two eMOTR circuit packs (same type) (for allowable
slots, see Table 2-15 on page 2-76). There is 40 Gbps of traffic capacity
between adjacent eMOTR circuit packs in the same equipment group.
Unlike NTK536AA, NTK536AB, NTK536FA, NTK536FB eMOTR variants,
the NTK536BE eMOTR variant cannot be mated with 40G OCLD circuit
packs.

• Table 2-13 on page 2-75 and Table 2-14 on page 2-76 show allowable
slots for eMOTR circuit packs (NTK536AA, NTK536AB, NTK536FA, and
NTK536FB variants) when mating with 40G OCLD/Wavelength-Selective
40G OCLD circuit packs.
• Table 2-15 on page 2-76 shows allowable slots for a single-slot eMOTR
circuit pack (NTK536AA, NTK536AB, or NTK536BE variant) when mating
with another single-slot eMOTR circuit pack (NTK536AA, NTK536AB, or
NTK536BE variant).
• Table 2-16 on page 2-79 shows allowable slots for a double-slot eMOTR
circuit pack (NTK536FA or NTK536FB variant) when mating with another
double-slot eMOTR circuit pack (NTK536FA or NTK536FB variant).
Table 2-13
Allowable slots for mated single-slot eMOTR circuit packs (NTK536AA or NTK536AB) and 40G
OCLD/Wavelength-Selective 40G OCLD circuit packs
Shelf type 40G OCLD eMOTR eMOTR 40G OCLD

or Wavelength-Selective or Wavelength-Selective
40G OCLD 40G OCLD
Slots
7-slot 1 2 3 4
and 3 4 5 6
6500-7 packet-optical
14-slot 1 2 3 4
3 4 5 6
9 10 11 12
11 12 13 14
32-slot 1 2 3 4
3 4 5 6
5 6 7 8
11 12 13 14
13 14 15 16
15 16 17 18
21 22 23 24
23 24 25 26
25 26 27 28
31 32 33 34
33 34 35 36
35 36 37 38

Table 2-14
Allowable slots for mated double-slot eMOTR circuit packs (NTK536FA or NTK536FB) and 40G
OCLD/Wavelength-Selective 40G OCLD circuit packs
Shelf type 40G OCLD eMOTR eMOTR 40G OCLD

or Wavelength-Selective or Wavelength-Selective
40G OCLD 40G OCLD
Slots
7-slot 1 2/3 4/5 6
and
14-slot 1 2/3 4/5 6
9 10/11 12/13 14
32-slot 1 2/3 4/5 6
13 14/15 16/17 18
21 22/23 24/25 26
33 34/35 36/37 38
Table 2-15
Allowable slots for mated single-slot eMOTR circuit packs (NTK536AA, NTK536AB, or
NTK536BE)
Shelf type eMOTR

Slots
2-slot (only supported in NTK536BE eMOTR 1 2
variant)
7-slot 1 2
and 2 3
6500-7 packet-optical 3 4
4 5
5 6

Table 2-15
Allowable slots for mated single-slot eMOTR circuit packs (NTK536AA, NTK536AB, or NTK536BE)
(continued)
Shelf type eMOTR

Slots
14-slot 1 2
2 3
3 4
4 5
5 6
9 10
10 11
11 12
12 13
13 14

Table 2-15
Allowable slots for mated single-slot eMOTR circuit packs (NTK536AA, NTK536AB, or NTK536BE)
(continued)
Shelf type eMOTR

Slots
32-slot 1 2
2 3
3 4
4 5
5 6
6 7
7 8
11 12
12 13
13 14
14 15
15 16
16 17
17 18
21 22
22 23
23 24
24 25
25 26
26 27
27 28
31 32
32 33
33 34
34 35
35 36
36 37
37 38

Table 2-16
Allowable slots for mated double-slot eMOTR circuit packs (NTK536FA or NTK536FB)
Shelf type eMOTR

Slots
7-slot 1/2 3/4
and 2/3 4/5
6500-7 packet-optical 3/4 5/6
14-slot 1/2 3/4
2/3 4/5
3/4 5/6
9/10 11/12
10/11 12/13
11/12 13/14
32-slot 1/2 3/4
2/3 4/5
3/4 5/6
4/5 6/7
5/6 7/8
11/12 13/14
12/13 14/15
13/14 15/16
14/15 16/17
15/16 17/18
21/22 23/24
22/23 24/25
23/24 25/26
24/25 26/27
25/26 27/28
31/32 33/34
32/33 34/35
33/34 35/36
34/35 36/37
35/36 37/38

• protection support
— supports G.8032 ERP. Up to 96 rings per equipment group
• GCC0 on OTUTTP facility and GCC1 on ODUTTP facility (XFP ports)
• GCC1 on the ODU3-rate ODUTTP on the backplane ports (but not the
ODU2/ODU2E ODUTTPs on the backplane ports)
• GCC0 on the OTU3 of the mated 40G OCLD or Wavelength-Selective 40G
OCLD circuit pack
Note 1: For detailed information about eMOTR concepts, applications,

when deploying an eMOTR circuit pack:
equipped with or without SONET/SDH cross-connect circuit packs.

Supported SFPs/SFP+s/XFPs
Table 2-17 provides a list of the SFPs/SFP+s that are supported on the
eMOTR circuit packs. Table 2-18 provides a list of the XFPs that are supported
on the eMOTR circuit packs.
Table 2-17
Supported SFP/SFP+s modules for the eMOTR circuit packs (NTK536AA, NTK536AB, NTK536FA,
NTK536FB, and NTK536BE)
Pluggable Equipment and Supported SFP/SFP+ modules and rates Part Number
Facilities (Note 1, Note 2, and
Note 3)
P2G5 OC-48/STM-16 DWDM SFPs NTK585xx where

— PTP (ETTP) (auto) — 1000Base-X (1.25 Gb/s) xx= see Note 4

— PTP (ETTP) (auto) — 1000Base-X (1.25Gb/s)

— 1000Base-X (1.25Gb/s)

SFP
— 1000Base-X (1.25Gb/s)

— 1000Base-T (1.00Gb/s)
PGEFC GE/FC100 1.25 Gbit/s 24 dB CWDM SFPs NTK591xB where

— PTP (ETTP) (auto) — 1000Base-X (1.25Gb/s) x= L, M, N, P, Q, R,
S, T

— FC-100/ IBM FICON (1.0625 Gb/s) x= L, M, N, P, Q, R,
S, T)
— 1000Base-X (1.25Gb/s)

— PTP (ETTP) (auto) — 1000Base-X (1.25Gb/s)

— 1000Base-X (1.25Gb/s)

Table 2-17
NTK536FB, and NTK536BE) (continued)
Note 3)
PSFP Multirate 15xx.yy (or 16xx.yy) nm DWDM 1600 NTK586xxE5 where

— PTP (ETTP) (auto) ps/nm SFPs xx= see Note 5
— 1000Base-X (1.25 Gb/s)
GE/FC100/FC200 1000-BaseLX 1310 nm XCT NTTP06CD

Enhanced SFP module
— 1000Base-X (1.25 Gb/s)
GE SX/FC100/FC200 850nm SFP NTTP06AD

— 1000Base-X (1.25 Gb/s)
10/100/1000-BaseT RJ45 SFP NTTP61CA (Note 6)

— 1000Base-T (1.0 Gb/s)
— 100Base-T (100 Mb/s)
10GBASE-LR/FC1200-SM-L,1310nm, SFP+ NTTP30CFE6

— 10.3125 Gb/s 10GBaseR (10GE)

— 1000Base-X (1.25 Gb/s)

— 1000Base-X (1.25 Gb/s)
Multirate 10GE/OTU2/OC192/FC1200, 1310nm, 160-9103-900

10km SFP+
— 10.3125 Gb/s 10GBaseR (10GE)
10GBASE-ER/FC1200, 1550nm, 40km, SFP+ 160-9104-900

— 10.3125 Gb/s 10GBaseR (10GE)
10GBASE-ZR/FC1200, 1550nm, 80km, SFP+ 160-9105-900

— 10.3125 Gb/s 10GBaseR (10GE)
10G, 1270/1330nm Tx/Rx Bidirectional, 40km, 160-9108-900

SFP+
— 10.3125 Gb/s 10GBaseR (10GE)

Table 2-17
Note 3)
Continued for PSFP 10G, 1330/1270nm Tx/Rx Bidirectional, 40km, 160-9109-900

— PTP (ETTP) (auto) SFP+
— 10.3125 Gb/s 10GBaseR (10GE)
10GE/FC1200, 850nm SFP+ 160-9111-900

— 10.3125 Gb/s 10GBaseR (10GE)
Multirate 850nm, MMF SFP+ 160-9116-900

— 10.3125 Gb/s 10GBaseR (10GE)
Multirate 1528.38 nm to 1565.50 nm Tunable, 160-9201-900

50GHz, Type 1 DWDM SFP+
— 10.3125 Gb/s 10GBaseR (10GE)
9.95G-11.09G Multirate,1310nm, SMF, 10km 160-9203-900

SFP+
— 10.3125 Gb/s 10GBaseR (10GE)
9.95G-11.09G Multirate, 1550 nm, SMF, 40 km 160-9204-900

SFP+
— 10.3125 Gb/s 10GBaseR (10GE)
9.95G-11.09G Multirate, 1550 nm, SMF, 80 km 160-9205-900

SFP+
— 10.3125 Gb/s 10GBaseR (10GE)
Multirate LongHaul ITU CWDM SFP+ 160-921x-900,

— 10.3125 Gb/s 10GBaseR (10GE) where x= 1, 2, 3, 4,
5, 6, 7, or 8)
Multi-rate 1310 nm, SMF SFP B-700-1036-001

— 1000Base-X (1.25Gb/s)
— 100Base-X (125Mb/s) (only supported in
NTK536FA and NTK536FB variants)
Note: The SFP B-700-1036-001 with REV “A”
written on the faceplates is not supported in
6500. Only SFP B-700-1036-001 marked REV
“B” can be supported in 6500.

Table 2-17
Note 3)
PFE 100-Base-LX FE 1310 nm 10km NTTP08SD (only

— PTP (ETTP) (auto) — 100Base-X (125Mb/s) supported in
NTK536FA and
NTK536FB
variants)
100-Base-BX 10-U Bidirectional-upstream, 1310 NTTP09BD (only

nm Tx, 10 km supported in
— 100Base-X (125Mb/s) NTK536FA and
NTK536FB
variants)
100-Base-BX 10-D Bidirectional-downstream, NTTP10BD (only

1530 nm Tx, 10 km supported in
— 100Base-X (125Mb/s) NTK536FA and
NTK536FB
variants)

— 100Base-X (125Mb/s)
10/100-BaseT RJ45 SFP NTTP61BAE6

— 100Base-T (100Mb/s)

Table 2-17
Note 3)
Note 1: On the eMOTR circuit packs (except NTK536BE variant), ports 9 to 12 are the 10GE
LAN/OTU2 (10.7G)/OTU2e (11.09G) XFP ports, and ports 1 to 8 are the 10GE SFP+ and GE SFP
ports. On the NTK536BE variant of eMOTR circuit packs, ports 11 to 14 are the 10GE LAN/OTU2
(10.7G)/OTU2e (11.09G) XFP ports, ports 1 to 8 are GE SFP ports and ports 9 and 10 are the GE SFP
or 10GE SFP+ ports. Ports 21 to 36 and 41 to 56 on the NTK536FA or NTK536FB variant are the GE
SFP ports.
Note 3: The facilities in brackets are facilities auto-created on the same port as the main facility or
DWDM/CWDM pluggable optics modules (SFP)”, for the complete list of ordering codes.
Note 6: Special recommendations are applied when NTTP61CA SFP is used in eMOTR circuit packs
equipped in different 6500 shelf types. For details, see “Special considerations when using
10/100/1000-BaseT RJ45 SFP (NTTP61CA)” on page 2-88).

Table 2-18
Supported XFP modules for the eMOTR circuit packs (NTK536AA, NTK536AB, NTK536FA,
NTK536FB, and NTK536BE)

— PTP (ETTP) (auto) XFP (Note 3)
— 10.3125 Gb/s 10GBaseR (10GE)
PXFP Multirate 15xx.yy nm EML DWDM 800 ps/nm NTK587Ex to

— PTP (ETTP) XFP NTK587Hx,
— PTP (OTUTTP, ODUTTP, Note 5
WAN Note 4, ETTP, ADJ) — 11.05 Gb/s OTU1e/11.09 Gb/s OTU2e
— 10.3125 Gb/s 10GBaseR (10GE)
Multirate 1528.38 nm to 1568.77 nm (1-88) NTK583AAE6

50GHz Tunable DWDM XFP
— 10.709 Gb/s OTU2
— 10.3125 Gb/s 10GBaseR (10GE)
Multirate 1528.38 nm to 1568.77 nm (1-88) NTK583AB

50GHz Tunable Type 2 DWDM XFP
— 10.709 Gb/s OTU2
— 10.3125 Gb/s 10GBaseR (10GE)
Multirate LongHaul ITU CWDM XFP NTTP84Jx,

D, E, F, G, or H
— 10.3125 Gb/s 10GBaseR (10GE)
Multirate 15xx.yy – 15xx.yy Tunable Dispersion NTK589xxE6

Tolerant DWDM 3200 ps/nm XFP where xx= see

Table 2-18
P10GSOEL 9.95G-11.09G multirate, 1550 nm, SMF, 40 km NTTP84AAE6

— PTP (ETTP) XFP
— PTP (OTUTTP, ODUTTP, — 10.709 Gb/s OTU2

WAN Note 4, ETTP, ADJ) — 11.05 Gb/s OTU1e/11.09 Gb/s OTU2e
— 10.3125 Gb/s 10GBaseR (10GE)

— 10.709 Gb/s OTU2
— 10.3125 Gb/s 10GBaseR (10GE)
8.5G-10.52G multi-rate, 850nm MMF XFP (Note NTTP86AA

3)
— 10.3125 Gb/s 10GBaseR (10GE)
Multirate 15xx.yy nm EML DWDM 1600 ps/nm NTK587Ax to

XFP NTK587Dx,
Note 5
— 10.3125 Gb/s 10GBaseR (10GE)
9.95G-11.09G multirate, 1550 nm, SMF, 80 km NTTP81KAE6

XFP
— 10.709 Gb/s OTU2
— 10.3125 Gb/s 10GBaseR (10GE)
9.95G-11.09G Multirate XFP, 1310nm, SMF, NTTP84CA

10km
— 10.709 Gb/s OTU2
— 10.3125 Gb/s 10GBaseR (10GE)

D, E, F, G, or H
— 10.3125 Gb/s 10GBaseR (10GE)

Table 2-18
Note 1: On the eMOTR circuit packs (except NTK536BE variant), ports 9 to 12 are the 10GE
LAN/OTU2 (10.7G)/OTU2e (11.09G) XFP ports, and ports 1 to 8 are the 10GE SFP+ and GE SFP
ports. On the NTK536BE variant of eMOTR circuit packs, ports 11 to 14 are the 10GE LAN/OTU2
(10.7G)/OTU2e (11.09G) XFP ports, ports 1 to 8 are GE SFP ports and ports 9 and 10 are the GE SFP
or 10GE SFP+ ports. Ports 21 to 36 and 41 to 56 on the NTK536FA or NTK536FB variant are the GE
SFP ports.
Note 4: The WAN facility is auto-created only if the PTP service type is OTU2.
DWDM/CWDM pluggable optics modules (XFP)”, for the complete list of ordering codes.
Special considerations when using 10/100/1000-BaseT RJ45 SFP

(NTTP61CA)
In an eMOTR Edge variant (NTK536BE), ports 1 to 8 can be used for RJ45
electrical SFPs. Since RJ45 cables occupy more space in the shelf fiber
compared to optical patch cords, use of RJ45 electrical SFPs can result in
congestion in the shelf fiber manager. The following rules are recommended
when equipping RJ45 electrical SFPs in different 6500 shelf types:
• 2-slot shelf type: recommended no more than two electrical SFP ports per
circuit pack. Total number of electrical SFPs per shelf is four. To minimize
congestion use 1.6 mm diameter bend insensitive fiber patchcords on any
optical ports in the shelf.
• 7-slot optical Type 2 shelf type: recommended no more than two ports per
circuit pack. Total number of electrical SFPs per shelf is eight. Optimal
location for circuit pack placements are slots 1/2 and 6/7. To minimize
optical ports in the same half of the shelf (slots 15, 1-3 in the lower half
and slots 4-7 in the upper half).
• 6500-7 packet-optical shelf type: recommended no more than two ports
per circuit pack. Total number of electrical SFPs per shelf is four. Optimal
location for circuit pack placements are slots 1 and 2. To minimize
optical ports in the same half of the shelf (slots 1-4 in the lower half and
slots 4-8 in the upper half).

• 14-slot shelf type: recommended no more than four ports per circuit pack.
Total number of electrical SFPs per shelf half is 12. Optimal locations for
circuit pack placements are slots 1/2 and 13/14. To minimize congestion
use 1.6 mm diameter bend insensitive fiber patchcords on any optical
ports in the pair of slots that share a cable/fiber exit (adjacent odd and
even slots).
Total number of electrical SFPs per shelf quadrant is 12. Optimal locations
for circuit pack placements are slots 1/2, 17/18, 21/22 and 37/38. To
minimize congestion use 1.6 mm diameter bend insensitive fiber
patchcords on any optical ports in the shelf quadrant. Note that use of
brackets with a 50 mm setback further reduces the quadrant’s cable/fiber
exit capacity in front of the brackets by approximately 45%.
In an eMOTR variant (NTK536FA), ports 21 to 28 can be used for electrical
SFPs and the following rules are recommended when equipped in different
6500 shelf types:
• 7-slot optical Type 2 shelf type: recommended no more than four ports per
circuit pack. Total number of electrical SFPs per shelf is eight. Optimal
location for circuit pack placements are slots 1/2 and 6/7. To minimize
optical ports in the shelf.
• 6500-7 packet-optical shelf type: recommended no more than four ports.
Total number of electrical SFPs per shelf is four. Optimal location for circuit
pack placements are slots 1 and 2. To minimize congestion use 1.6 mm
diameter bend insensitive fiber patchcords on any optical ports in the
same half of the shelf (slots 1-4 in the lower half and slots 4-8 in the upper
half).
Total number of electrical SFPs per shelf half is 12. Optimal location for
circuit pack placements are slots 1 and 2. To minimize congestion use 1.6
mm diameter bend insensitive fiber patchcords on any optical ports in the
pair of slots that share a cable/fiber exit (adjacent odd and even slots).
Total number of electrical SFPs per shelf quadrant is 12. Optimal locations
for circuit pack placements are slots 1/2, 17/18, 21/22 and 37/38. To
minimize congestion use 1.6 mm diameter bend insensitive fiber
patchcords on any optical ports in the shelf quadrant. Note that use of
brackets with a 50 mm setback further reduces the quadrant’s cable/fiber
exit capacity in front of the brackets by approximately 45%.

The eMOTR circuit pack supports the following monitored entities (retrieved
using Site Manager):
— PM collection for OTUTTP facilities
— PM collection for ODUTTP facilities
— PM collection for ETTP, ETH100, and WAN facilities
— PM collection for PTP facilities
— operational measurements for ETTP, ETH100, and WAN facilities

323-1851-520.
The eMOTR circuit pack supports the following monitored entities (retrieved
using SAOS CLI or SNMP MIB):
— PM collection of sub-port, QoS flow, port-queue-group, and port
egress-queue (32 x 15-minute PM bins)
— RMON history for port
— RMON usr-history for any MIB addressable entity
For detailed information and procedures associated with SAOS CLI

performance monitoring and SNMP MIB, refer to SAOS-based Packet
Services Fault and Performance, 323-1851-650 and SAOS-based Packet
Services MIB Reference, 323-1851-690.
Alarms
For information on SAOS alarms, refer to SAOS-based Packet Services MIB

Reference, 323-1851-690.
Equipment alarms
• Database Not Saved: CLI Save Config Required


• Secondary SETS Locking to Primary
• Timing Generation Failure to Lock
Pluggable alarms
• Circuit Pack 3rd Party – Pluggable
PTP facility alarms

• Loss Of Signal
• Laser Off Far End failure Triggered
OTUTTP facility alarms

• OTU Loss Of Clock
• OTU Loss Of Frame
• OTU Pre-FEC Signal Fail
• OTU Pre-FEC Signal Degrade
• OTU Loss Of Multiframe
• OTU BDI
• ODU AIS

• GCC0 Link Fail

• Timing Distribution Forced Switch - n Ref
• Timing Distribution Lockout - n Ref
• Timing Distribution Loss Of Reference - n Ref
• Timing Generation Forced Switch - n Ref
• Timing Generation Lockout - n Ref
• Timing Generation Loss Of Reference - n Ref
ODUTTP facility alarms

• ODU AIS
• ODU LCK
• ODU OCI
• ODU BDI
• ODU Signal Degrade
• ODU Pre-FEC Signal Fail
• ODU Loss of Frame
• ODU Loss of Multiframe
• OPU AIS
• OPU Trace Identifier Mismatch
• MSI Mismatch
• Far End Client Signal fail
• GCC1 Link Fail

ETTP Facility alarms

• Loss Of Data Synch
• Loss of Frame
• Local Fault
• Remote Fault
• Service Defect indication
WAN alarms
• Far End Client Signal Failure
Common alarms
SAOS alarms
• AIS HW Session Exhausted
• CFM Rx CCM Rate Exceeded
• CFM Rx FPS Rate Exceeded
• CFM Service Fault
• Class Elements Exhausted
• Config Integrity Fail
• CPU Overload
• Disk Full
• Egress Reflector Enabled
• Link Down
• Memory Low
• No PDU received
• No RPL owner

• Port Signal Degrade

• Port FDB Table Nearly Full
• Port Flapping
• Protection Switch Active
• Provisioning Mismatch
• Q-Resource OverUtilized
• RMEP Limit Exceed
• VLLI Fault
• VS FDB Table Nearly Full
Equipping rules
The following equipping rules apply to eMOTR circuit packs:
• NTK536AA or NTK536AB eMOTR variant is a single-slot 12-port
interface.
• NTK536BE eMOTR variant is a single-slot 14-port interface.
• NTK536FA or NTK536FB eMOTR variant is a double-slot 44-port
interface.
• The following table shows allowable eMOTR slots in different shelf types.
Table 2-19
eMOTR allowable slots
Shelf type eMOTR slots

Single-slot eMOTR variant Double-slot eMOTR
(NTK536BE, NTK536AA, variant (NTK536FA or
NTK536AB) NTK536FB)
• 14-slot converged optical (NTK503ADE5) Slots 1-6 and 9-14 Slots 1-5 and 9-13
• 14-slot converged optical/front electrical
(NTK503BDE5)
• 14-slot converged optical/rear electrical
(NTK503CDE5)
14-slot packet-optical (NTK503SA) Slots 1-6 and 9-14 Slots 1-5 and 9-13
7-slot (NTK503PAE5 and NTK503KA Slots 1 to 7 Slots 1 to 6
variants) (Note 1)
6500-7 packet-optical (NTK503RA) Slots 1 to 6 Slots 1 to 5
2-slot (NTK503MAE5 and NTK503NAE5 Not supported Not supported
variants)

Table 2-19
eMOTR allowable slots (continued)

NTK536AB) NTK536FB)
2-slot Slots 1 and 2 (Note 3) Slot 1
Only NTK503LA variant when equipped
with
• Power Input Card (breakerless) - 2-Wire
D-Sub Input, Max 10A (NTK505TA), or
• AC Power Input Card (100 - 240 Vac)
(NTK505SB), or
• 24 Vdc Power Input Card (breakered) -
2-Wire D-Sub Input (NTK505TR) (Note 2)
and
• SPAP-2 w/2xOSC (NTK555NA or
NTK555NB)
32-slot packet-optical (NTK603AAE5 and Slots 1-8, 11-18, 21-28, and Slots 1-7, 11-17, 21-27, and
NTK603AB variants) 31-38 31-37

Table 2-19
eMOTR allowable slots (continued)

NTK536AB) NTK536FB)
Note 1: To support eMOTR circuit packs on a 7-slot optical Type 2 shelf (NTK503KA) when equipped
with AC power input cards, the shelf requires the minimum of following power setup:
— two working AC power input cards and one protection AC power input card, or
— two AC power input cards and two protection AC power input cards.
To support full-filled eMOTR circuit packs on a 7-slot optical Type 2 shelf (NTK503KA) when equipped
with AC power input cards, the shelf requires three working AC power input cards and one protection
AC power input card.
Note 2: The following considerations apply when equipping an eMOTR circuit pack in an NTK503LA
2-slot shelf equipped with 24 Vdc Power Input Card (breakered) - 2-Wire D-Sub Input (NTK505TR):
— Only one NTK536AA or NTK536AB eMOTR can be equipped (the remaining slot can optionally be
equipped with another lower power circuit pack type as long as the total power budget does not
exceed the limits for the 24 Vdc application).
— If two NTK536BE eMOTRs are equipped, it is not possible to full-fill all the pluggable transceiver
ports in both circuit packs since there is insufficient power in the 24 Vdc application power budget.
For 24 Vdc applications that require equipping two NTK536BE eMOTRs, you must confirm that the
total power budget (including all pluggable transceivers) does not exceed the 24 Vdc application
power budget.
— Use of NTK536FA or NTK535FB eMOTR is not recommended because there is insufficient power
in the 24 Vdc application power budget to equip the eMOTR with many pluggable transceivers.
For additional information, refer to the Power specifications section in Part 3 of Planning, NTRN10EY.
Note 3: The NTK536AA or NTK536AB variant of eMOTR circuit packs cannot be configured in a
2-circuit pack equipment group in a 2-slot shelf type (i.e. cannot be mated with another NTK536AA or
NTK536AB circuit pack in a 2-slot shelf). The NTK536BE variant of eMOTR circuit packs can be
configured in a 2-circuit pack equipment group in a 2-slot shelf type (i.e. can be mated with another
NTK536BE circuit pack in a 2-slot shelf).

ATTENTION
For NTK536FA and NTK536FB variants of eMOTR circuit packs, use only
fiber patch cords that are bend-insensitive in accordance to ITU-T G.657 and
have a 1.6 mm diameter (such as NTTC90xx, NTTC91xx, and NTTC92xx) if
any of the following apply:
— if you plan to connect more than 16 duplex ports per slot.
— if equipping the left or right side of the 14-slot shelf or a quadrant of a 32-slot
with three or more circuit packs such that the total number of fibers will exceed
192 fibers (96 duplex port connections). You must take care when dressing the
fibers in front of the circuit pack in order to minimize layering and twisting that
may result in interference with a shelf front cover if equipped. An extended depth
cover solution will provide additional space in front of the circuit pack.
• requires that the 6500 shelf is equipped with the SP-2 shelf processor
(NTK555EAE5, NTK555CAE5, or NTK555FAE5) or SPAP-2 w/2xOSC
(NTK555NA or NTK555NB), otherwise the eMOTR equipment does not
provision.
• requires high flow cooling fan modules (NTK507LDE5, NTK507MDE5,
NTK507LS, and NTK507MS) when equipped in a 14-slot shelf
• for NTK536FA and NTK536FB variants of eMOTR circuit packs in a
14-slot shelf with front-exhaust fans (NTK507LDE5 or NTK507LS) that is
currently equipped with an air deflector grill (NTK509FA/NTK509FAE6),
the air deflector grill must be removed.
• for NTK536FA and NTK536FB variants of eMOTR circuit packs in a shelf
that is equipped in the same rack as one or more other shelves configured
for front exhaust, refer to “Front exhaust considerations” in the Bay/rack
configurations section in Part 1 of Planning, NTRN10EY.
Engineering rules
For more information about eMOTR engineering rules, refer to 6500

The following table lists the weight, power consumption, and SFP/SFP+/XFP
specifications for the eMOTR optical interface circuit packs.
Table 2-20
Technical specifications for eMOTR optical interface circuit packs
Parameter eMOTR
eMOTR (NTK536AA or eMOTR (NTK536FA or eMOTR
NTK536AB variant) NTK536FB variant) (NTK536BE variant)
Weight (estimated) 1.5 kg (3.2 lb) 2.4 kg (5.3 lb) 1.4 kg (3.1 lb)
Power consumption Typical (W): 115 (Note 1, Typical (W): 151 (Note 1, Typical (W): 74 (Note 1,
Note 3, and Note 4) Note 3, and Note 4) Note 3, and Note 4)
Power Budget (W): 131 Power Budget (W): 178 Power Budget (W): 78
(Note 2, Note 3, and Note (Note 2, Note 3, and Note (Note 2, Note 3, and Note
4) 4) 4)
SFP+ specifications (Note 6)

Table 2-20
Technical specifications for eMOTR optical interface circuit packs (continued)
Parameter eMOTR
eMOTR (NTK536AA or eMOTR (NTK536FA or eMOTR
NTK536AB variant) NTK536FB variant) (NTK536BE variant)
Note 1: The typical power consumption values are based on operation at an ambient temperature of 25
(+/-3oC) and voltage of 54 Vdc (+/-2.5 V) or in the full operational voltage range in the case of AC-powered
equipment. For practical purposes, the rounded typical power consumption of an equipment can be used
as the equipment heat dissipation when calculating facilities thermal loads (an estimate of the long term
heat release of the item in a system).
range in the case of AC-powered equipment. These values must be used in sizing feeders and estimating
theoretical maximum power draw.
Note 3: The power consumption values are derated so that pluggables transceivers must be considered
separately. When estimating the total power for the equipment in a slot or in a system, you must add the
power values for each of the required pluggable devices For pluggable transceiver power values, refer to
Pluggable Datasheets and Reference, 323-1851-180.
Note 4: For this circuit pack that must be equipped with SFPs and XFPs, the power values published in
this table do not include SFPs and XFPs power values. You must add:
IR-2/S-64.2b.
— 3 W to typical power value and 4 W to power budget for each XFP module with IR-2/S-64.2b reach or
greater.
323-1851-180.
Note 6: For optical SFP+ specifications, see chapter 4 of Pluggable Datasheets and Reference,
323-1851-180.
323-1851-180.
Latency

Layer 2 circuit packs summary table

The following table shows a summary table between layer 2 (L2SS, 20G
L2SS, PDH gateway, eMOTR, and L2 MOTR) circuit packs. Refer to 6500
Packet-Optical Platform Data Application Guide, NTRN15BA, for more details.
Table 2-21
Summary comparison between L2SS, 20G L2SS, L2 MOTR, eMOTR circuit packs
Functionality L2 MOTR eMOTR L2SS (NTK531BAE5) 20G L2SS

(NTK531VAE5) (NTK536AA/ and PDH Gateway (NTK531HAE5)
NTK536AB/ (NTK531MAE5)
NTK536BE/
NTK536FA/
NTK536FB)
OTN line rate Yes Yes Not applicable Not applicable
10GE LAN Yes Yes No Yes
GE client provisioning Yes Yes Yes Yes
PAUSE flow control Yes No No Yes
1+1 equipment protection No Not applicable Yes Yes
1+1 inter-card OTN line Yes No Not applicable Not applicable

protection – two cards,
single protection group
1+1 intra-card OTN line Yes No Not applicable Not applicable

protection – two cards,
double protection group
Signal conditioning Yes Yes No Yes
GCC 0 Comms Yes Yes Not applicable Not applicable
GCC 1 Comms Yes Yes Not applicable Not applicable
WAN ports (used for GFP Yes Yes Not applicable Not applicable
encapsulation over OTM2
lines)

Table 2-21
Summary comparison between L2SS, 20G L2SS, L2 MOTR, eMOTR circuit packs (continued)

NTK536BE/
NTK536FA/
NTK536FB)
WAN ports (used for GFP Not applicable Not applicable Yes Yes
encapsulation on the
SONET/SDH/PDH (where
applicable) ports for
bandwidth provisioning to
the shelf central
cross-connect circuit
packs)
Shelf timing Yes No Yes Yes
Line timing Yes Yes (Note) No No
Local timing Yes Yes No No
Ethernet Sync Message No Yes No No

Channel (ESMC)
Point-to-point EVPL (GE Yes Not applicable No Yes

& 10GE)
VLLI Not applicable Yes Not applicable Not applicable
Add/drop with Yes Yes No Yes

pass-through EVPL
E-LINE Yes Yes Yes Yes
E-LAN Yes Yes Yes Yes
Loopback support Yes Yes Yes Yes
Protection exerciser Yes No No No
Single tag classification Yes Yes Yes Yes
Dual tag classification No No Yes Yes
Per VCE per COS policing Yes No Yes Yes
8 COS (2SP + 6 WRR) Yes Yes Yes Yes
Add one tag (UNI-NNI Yes Yes Yes Yes

transition)
Add two tags No No Yes Yes

Table 2-21

NTK536BE/
NTK536FA/
NTK536FB)
NNI-NNI tag swapping Yes Yes Yes Yes
Modify two tags No No Yes Yes
Remove one tag (NNI-UNI Yes Yes Yes Yes

transition)
Remove two tags No No Yes Yes
VCS 235 (standard Not applicable 2000 2000

mode)
1000 (extended
mode)
Services Not applicable 1000 Not applicable Not applicable
VCE 471 (standard Not applicable 4000 4000

mode)
3072 (extended
mode)
Service Endpoints Not applicable 3000 Not applicable Not applicable
VCEMAP 500 (standard Not applicable 8000 8000

mode)
3072 (extended
mode)
Classifiers Not applicable 22000 Not applicable Not applicable
100 FX Yes No No Yes
LAG Yes Yes Yes Yes
D-LAG No Yes No No
LACP Yes Yes Yes Yes
Peer EFM Yes No Yes Yes
Peer SONMP Yes Not applicable Yes Yes
Peer LLDP Yes Yes No Yes

Table 2-21

NTK536BE/
NTK536FA/
NTK536FB)
Control frame profile Yes Yes Yes Yes

support
Provisionable scheduler No No Yes Yes

profiles
G.8032 ERP (revertive) Yes Yes No Yes
G.8032 ERP Yes Yes No Yes

(non-revertive)
G.8032 over LAG ring No Yes No No

spans (where LAG ports
of a G.8032 ring span
must be configured on a
single eMOTR circuit
pack)
ETH OMs & PMs Yes Yes Yes Yes
ETH100 OMs & PMs No No No Yes
WAN OMs & PMs Yes Yes Yes Yes
10GE OMs & PMs Yes Yes Not applicable Yes
OTM2 facility PMs Yes Not applicable Not applicable Not applicable
PTP, OTUTTP and Not applicable Yes Not applicable Not applicable
ODUTTP PMs
Per port per COS OMs & No Yes Yes No

PMs
Per VCE OMs Yes (maximum Not applicable Yes (maximum 100 Yes (maximum
5 VCEs with VCEs with detailed 100 VCEs with
detailed stats) stats) detailed stats)
Per Service Endpoint Not applicable Yes (maximum Not applicable Not applicable
OMs 2000 Service
Endpoints with
detailed stats)
Multiple queue groups No No No Yes

Table 2-21

NTK536BE/
NTK536FA/
NTK536FB)
4K VIDs per port Yes Yes Yes Yes
Extended service (SVID Yes Yes Yes Yes

range [1....4,000])
Extended service (SVID Yes No No No

range [1....2,000])
Provisionable queue sizes Yes No Yes Yes
Provisionable drop No No Yes Yes

profiles
Static MAC addresses 64 500 64 64
32K MAC addresses Yes Yes Yes Yes
SRED Yes No No No
WRED No Yes Yes Yes
802.1ag (CFM) Yes (Note) Yes (Note) Yes Yes (Note)
Note: 20G L2SS and L2 MOTR circuit packs do not support CFM in E-LAN topologies. Therefore, when
interworking with eMOTR circuit packs in E-LAN topologies, do not define remote MEPs on 20G L2SS
or L2 MOTR circuit packs.
Ingress filters Yes Yes Yes Yes
Dual rate three color Yes No No No

marker (RFC 2698)
Differentiated services No Yes Yes Yes

two rate three color
marker (RFC 4115)
Per VCS MTU checking No Yes Yes Yes
WAN alarms Yes Yes Yes Yes
1+1 LAG protection Yes Yes Yes (using LACP 1+1 Yes (using
equipment protection) LACP 1+1
equipment
protection)

Table 2-21

NTK536BE/
NTK536FA/
NTK536FB)
EPL-Emulated services Yes Not applicable No Yes

over G.8032 ERP
EPL-Emulated services in Yes Not applicable No Yes

parallel with G.8032 ERP
VLLI (client port Not applicable Yes Not applicable Not applicable
conditioning) services
over G.8032 ERP
conditioning) services in
parallel with G.8032 ERP
conditioning) services
over single card LAG and
over G.8032 with LAG ring
spans

RPR 10G STS-1/HO 4xGE circuit pack (NTK534BAE5)

Overview
The RPR 10G STS-1/HO 4xGE circuit pack (also known as RPR) uses up to
four SFP optics for the GE interfaces. his circuit pack supports layer 2 services
with layer 2 RPR protection. Services from the RPR circuit pack map to
SONET/SDH containers and are assigned as connections to OC-n/STM-n
interface circuit packs.
Figure 2-16 shows the faceplate of a RPR circuit pack. Figure 2-17 on page
2-107 provides functional block diagram of the RPR circuit pack.
Figure 2-16
RPR circuit pack faceplate
Red triangle (Fail)

RPR 10G GE
STS-1/HO
4 Port SFP
Fail
Ready
In Use

Rx
2 Tx
Rx
3 Tx

Rx
Hazard
level:

R99
EEEEE99999
S/N NT030MEE9999E
NTUD99EE
Type A

Figure 2-17
RPR circuit pack block diagram (NTK534BAE5)
PHY SFP 1
XC
PHY SFP 2
Backplane
10G SONET/SDH RPR Network

OHP Mapper Processor
PHY SFP 3
XC
PHY SFP 4
Processor Power
Module Supply
Legend
RPR Resilient Packet Ring

The RPR circuit pack (NTK534BAE5) provides the following functionality.
• no direct mapping between LAN and RPR, LAN to RPR association is
achieved by L2 provisioning of virtual circuit segments (VCS) or tunnel
segments (TNS)
• SONMP topology discovery
• has two NPUs with 144MB buffers each, for a total of 288MB of memory
for ingress and egress buffers with fixed allocation per CoS. In the current
implementation 166MB are in use, with the unused memory left for future
support for eight different CoS
— stacked VLANs (tagged/untagged frames) on UNI or NNI ports
— OEL2 on NNI ports
• WAN facilities
— up to 4 WAN facilities per circuit pack (10G of bandwidth)
— NNI
GFP
– contiguous concatenation (STS3c/VC4, STS12c/VC4-4c, and
STS48c/VC4-16c)
– virtual concatenation (STS3c-nv/VC4-nv, where n = 1 to 32 and
STS1-nv/HO_VC3-nv, where n=3 to 96)

— five classes of service (COS)
— metering and marking of frames (UNI ports only)
• L2 connectivity
— point-to-point (P2P) and any-to-any (A2A) connectivity on SVLAN and
OEL2 networks
• L2 protection
— two RPRs per circuit pack (two WAN facilities per RPR)
— ring WAN inter-connect topologies
— layer 2 IEEE 802.17-2004 and IEEE 802.17b RPR protection
— ring fairness/ring QoS
Note: For detailed information about RPR concepts, applications, and

engineering rules, see the 6500 Packet-Optical Platform Data Application
Guide, NTRN15BA.
The RPR circuit pack supports the following cross-connection types
The RPR circuit pack supports the following connection rates
• concatenated rates of STS12c/VC4-4c and STS48c/VC4-16c
• virtual concatenation at rates of STS1-nv/HO VC3-nv (n = 3 to 96) and
Supported SFPs
The following table provides a list of the SFPs that are supported on the RPR
circuit pack.

Table 2-22
Supported SFP modules for the RPR 10G STS-1/HO 4xGE circuit pack (NTK534BAE5)
Facilities

— ETH — 1000Base-X (1.25Gb/s)

— 1000Base-X (1.25Gb/s)

SFP
— 1000Base-X (1.25Gb/s)

— 1000Base-T (1.00Gb/s)

— ETH — 1000Base-X (1.25Gb/s)


— 1000Base-X (1.25Gb/s) x= L, M, N, P, Q,
R, S, T

— ETH — 1000Base-X (1.25Gb/s)

— 1000Base-X (1.25Gb/s)
The RPR circuit pack supports the following monitored entities:
• PM collection for ETH, WAN, and COS (ETH, WAN, and RPR rings)
facilities
• operational measurements for ETH, WAN, LAG, RPR rings, COS (ETH,
WAN, and RPR rings), VCE (ETH, LAG, and RPR rings), and TNE (ETH,
LAG, and RPR rings) facilities

323-1851-520.

Alarms
Equipment alarms
Pluggable alarms
Ethernet alarms
• Link Down
• Loss Of Signal
• Signal Degrade
WAN alarms
• Link Down


• Manual Ring Switch Active
• Forced Ring Switch Active
• Ring Failure
• Ringlet Failure
• Signal Degrade
STS Path alarms

Layer 2 alarms
• Link Aggregation Group Partial Fail
• Topology Failure
• Topology Instability
• Isolated Station
• Max Station Exceeded
Common alarms

Equipping rules
The following equipping rules apply to RPR circuit packs:
ATTENTION

ATTENTION

NTK503KA).
this release.
• in a 14-slot shelf type, the RPR 10G STS-1/HO 4xGE circuit pack is not
supported when using the MXC circuit pack.
Engineering rules
For more information about RPR engineering rules, refer to 6500
specifications for the RPR optical interface circuit packs.

Table 2-23
Technical specifications for RPR optical interface circuit packs
Parameter RPR (NTK534BA)

Power consumption Typical (W): 84 (Note 1, Note 3, Note 4, and Note 5)
Power Budget (W): 84 (Note 2, Note 3, Note 4, and Note 5)
Note 5: 50% LAN utilization on all 4 ports.
323-1851-180.

Layer 2 circuit pack provisioning procedures

The following flowcharts provide the various steps/procedures that must be
performed in order to have the eMOTR, L2SS, PDH gateway, 20G L2SS,
RPR, and L2 MOTR circuit packs ready to carry traffic.
eMOTR

L2SS and PDH gateway

20G L2SS

RPR

L2 MOTR

Provisioning rules summary for the L2 MOTR circuit packs

• Port 1 and port 2 can be provisioned as OTM2 (10.7G, 11.05G, 11.09G)
or native ETH10G. When configuring an OTM2 facility, you must also
configure an ETH10G UNI or NNI facility on the same port. Otherwise, no
Ethernet traffic can enter or exit these ports.
• When port 1 or port 2 is provisioned as native ETH10G, the port can be
considered as a client port if the interface type is set to UNI.
• You can provision ETH10G facilities on the mate ports 91 and 92.
• Ports from port 3 to port 12 are the FE or GE ports, which can be either
NNI or UNI.
• Changing the primary state of the OTM2 facility automatically changes the
primary state of the associated ETH10G and/or WAN facility if the
ETH10G and/or WAN facility exists.
Provisioning rules summary for the eMOTR circuit packs

• To provision an eMOTR circuit pack, the shelf must be equipped with the
SP2 or SPAP-2 w/2xOSC shelf processor.
• On the eMOTR circuit packs, ports 9 to 12 are the XFP ports, 10GE LAN,
OTU2 (10.7G), or OTU2e (11.09G), and ports 1 to 8 are the 10GE SFP+
and GE SFP ports. Ports 21 to 36 and 41 to 56 on the NTK536FA variant
are the GE SFP ports.
• PTP facilities are defined as the physical layer of an eMOTR port.
Provisioning a PTP facility with a specified service type automatically
creates a complete set of child facilities down to the ETTP facility. See
Figure 2-18 on page 2-121 for details.
• The primary state of any applicable child OTUTTP/ODUTTP/WAN/ETTP
facilities is managed through the parent PTP facility for faceplate ports. To
delete the PTP facility, there must be no L2 services provisioned on the
associated SAOS port, or the eMOTR circuit pack must be physically
removed. Any applicable child OTUTTP/ODUTTP/WAN/
ETTP facilities are deleted when the parent PTP facility is deleted.
• Backplane ODUTTPs can be auto created as a result of changing the

eMOTR equipment profile or equipment profile 2, or manually created if
they were previously deleted. To delete a backplane ODUTTP, there must
be no L2 services provisioned on the associated SAOS port(s). The state
of the child ETTP and WAN facilities on the eMOTR backplane is managed
through the state of their parent ODU2/ODU2E ODUTTP.

Figure 2-18 shows the facilities supported on faceplate ports of eMOTR circuit
packs.
Figure 2-18
Facilities supported on eMOTR faceplate ports
Figure 2-19 on page 2-122 shows the facilities supported on eMOTR

backplane ports when mated with 40G OCLD/Wavelength-Selective 40G
OCLD.

Figure 2-19
Facilities supported on eMOTR backplane ports and mate 40G OCLDs
The table below provides references to procedures covered in this section.
Table 2-24
Topic
Procedure 2-1, “Provisioning a circuit pack automatically”
Procedure 2-2, “Provisioning a pluggable automatically”
Procedure 2-3, “Routing fiber-optic cables onto the 6500 shelf”
Procedure 2-4, “Connecting or disconnecting fiber-optic cables to or from circuit packs”
Procedure 2-5, “Adding a facility to an equipment”
Procedure 2-6, “Adding a path connection”
Procedure 2-7, “Adding an EVPL connection”
Procedure 2-8, “Adding a resilient packet ring”

Table 2-24
Procedures in this section (continued)
Topic
Procedure 2-9, “Adding east and west protection spans in resilient packet rings”
Procedure 2-10, “Performing profiles provisioning tasks”
Procedure 2-11, “Performing service activation for virtual circuits”
Procedure 2-12, “Provisioning the network element timing mode and references”
Procedure 2-13, “Creating a ring in a G.8032 ERP”
Procedure 2-14, “Creating a ring port in a G.8032 ERP”
Procedure 2-15, “Creating a ringlet in a G.8032 ERP”
Procedure 2-16, “Creating a ringlet port in a G.8032 ERP”
Procedure 2-17, “Changing the L2 MOTR equipment profile”
Procedure 2-18, “Editing facility parameters”
Procedure 2-19, “Creating an equipment group and adding members”
Procedure 2-20, “Changing the eMOTR equipment profile”
Procedure 2-21, “Changing the primary state of a facility”
Procedure 2-22, “Changing the primary state of a circuit pack or pluggable”
Procedure 2-23, “Deleting a facility from an equipment”
Procedure 2-24, “Deleting a circuit pack or pluggable”

Procedure 2-1
When automatic equipping is enabled, a circuit pack is automatically
provisioned when inserted in the shelf, along with any pluggables present.
Facilities may or may not auto-provision, depending on the circuit pack or
pluggable type. See Table 2-25 on page 2-130 for details.

automatic equipping” procedure in Administration and Security,
323-1851-301.
If an eMOTR circuit pack or 20G L2SS is inserted in a 14-slot shelf, the high
flow fan requirement must be met before the circuit pack can be provisioned.
See the “Equipping rules” sections for supported slots for eMOTR, L2SS, PDH
gateway, 20G L2SS, L2 MOTR, and RPR circuit packs. If a circuit pack is
inserted in an unsupported slot, an Autoprovisioning Mismatch alarm is
raised.
CAUTION
packs.
Prerequisites
• To provision equipment for an empty equipment slot, ensure the last
equipment that occupied the slot and its related facilities and
cross-connects have been deleted.
• Ensure the plastic pin protector on the circuit pack has been removed.
Step Action

ground point.


Step Action
2 Insert the circuit pack in the correct slot in the shelf.

If you are logged in to Site Manager when you automatically provision a circuit
pack, the Equipment & Facility Provisioning application will auto-refresh to
display the circuit pack in the list of available equipment. You can also click
the Refresh button to do the manual refresh.
—end—

Procedure 2-2
Provisioning a pluggable automatically
When automatic equipping is enabled, a pluggable is automatically
provisioned when inserted into the circuit pack port. Facilities may or may not
auto-provision, depending on the pluggable type. See Table 2-25 on page
2-130 for details.
On a 20G L2SS circuit pack, by default, the I/O carriers are not provisioned.
Thus the SFPs present on the I/O carriers will not be auto-equipped. You must
edit the equipment parameters Carrier 1 and/or Carrier 2 to be 12portSFP.
Refer to the “Changing the map mode, WAN configuration, and carrier info of
a 20G L2SS circuit pack” in Part 1 of Configuration - Provisioning and
Operating, 323-1851-310. Then the SFPs on the associated I/O carriers will
be auto-equipped.

automatic equipping” procedure in Administration and Security,
323-1851-301.
If a pluggable is inserted in an unsupported circuit pack and automatic

equipping is enabled, an Autoprovisioning Mismatch - Pluggable alarm is
raised.
CAUTION
packs.
Prerequisites
• Ensure the last pluggable that occupied the circuit pack port and its related
facilities and cross-connects have been deleted.
• Ensure the plastic pluggable port protector has been removed.
Step Action

ground point.
2 Insert the pluggable in the correct circuit pack port in the shelf.
—end—

Procedure 2-3
Routing fiber-optic cables onto the 6500 shelf
Refer to the procedure on routing fiber-optical cables onto the 6500 shelf, in
the Installation technical publication specific to the respective 6500 shelf type.
—end—

Procedure 2-4
Connecting or disconnecting fiber-optic cables to or
from circuit packs
Refer to the procedure on connecting or disconnecting fiber-optic cables to or
from circuit packs, in the Installation technical publication specific to the
respective 6500 shelf type.
—end—

Procedure 2-5
Adding a facility to an equipment
Use this procedure to add a facility. See Table 2-25 on page 2-130 for facilities
supported on the Layer 2 circuit packs.
On eMOTR, LAG can only be configured using SAOS-based CLI, not using
the Site Manager. Member ports in a LAG can have different control frame
profiles.
Prerequisites
UPC.
Step Action

2 Select Equipment & Facility Provisioning from the Configuration
drop-down menu to open the Equipment & Facility Provisioning application.
4 In the Equipment area, select the circuit pack or pluggable that will support
the facility.
5 Select the appropriate facility type from the Facility Type drop-down list if the
Facility Type drop-down list is enabled.
6 Click Add in the Facility area to open the Add facility dialog box.
7 If adding WAN or LAG on L2MOTR, 20GL2SS, L2SS, PDH gateway, or RPR
circuit pack, select the required port from the Port drop-down list.
To add facilities to all the remaining unprovisioned ports, select ALL from the
Port drop-down list.
8 Select the required parameters from the drop-down lists. See the following for
facility attribute descriptions:
• “LAG facility parameters” on page 2-218
• “PTP facility parameters” on page 2-232
• “OTUTTP facility parameters” on page 2-233
9 Click OK to add the facility and close the Add facility dialog box.
—end—

Table 2-25
Facilities supported on Layer 2 circuit packs

• L2SS VT1.5/LO • WAN • PGEFC • ETH

4xGE (L2SS) • LAG
NTK531BA • PGE • ETH
• RPR 10G • PGEFC200 • ETH

STS-1/HO 4xGE
(L2RPR)
NTK534BAE5
• L2SS • WAN (DS3WAN, • PGEFC • ETH

DS1/E1/DS3/E3 DS1WAN, E3WAN,
4xGE(L2SS) E1WAN Note 3) • PGE • ETH
NTK531MAE5 • LAG • PGEFC200 • ETH
• 20G L2SS 16 Port • WAN • PGEFC • ETH

I/O 2x XFP/ 8xSFP • LAG
(20GL2SS) • PGE • ETH
NTK531HAE5 • PGEFC200 • ETH
• P10GEL • ETH10G
• P10GSEL • ETH10G
• P10GSOEL • ETH10G
• PFE • ETH100
• L2 MOTR • ETH10G • PGE • ETH

(L2MOTR) • LAG
(Note 4) • PGEFC • ETH
NTK531VAE5 • PGEFC200 • ETH
• PSFP • ETH
• P2G5 • ETH
• PFE • ETH100
• P10GEL • ETH10G (ADJ)
• P10GSEL • ETH10G (ADJ)
• P10GSOEL • OTM2 (ADJ), ETH10G (WAN Note 6)
• PXFP • OTM2 (ADJ), ETH10G (WAN Note 6)

• ETH10G (ADJ) (Note 5)

Table 2-25
Facilities supported on Layer 2 circuit packs (continued)

• eMOTR (EMOTR) • FTTP (auto) • P10GSOEL • PTP (ETTP)

(Note 7) • ODU3 TTP (auto or • PTP (OTUTTP, ODUTTP,
NTK536AA/AB/FA manual) WAN Note 8, ETTP, ADJ)
/FB
• ODU2 TTP (WAN, • PXFP • PTP (ETTP)
ETTP)
• PTP (OTUTTP, ODUTTP,
• ODU2e TTP WAN Note 8, ETTP, ADJ)
(ETTP)
Note 9 • P10GEL • PTP (ETTP) (auto)
• P2G5 • PTP (ETTP) (auto)
• PGE • PTP (ETTP) (auto)
• PGEFC • PTP (ETTP) (auto)
• PGEFC200 • PTP (ETTP) (auto)
• PSFP • PTP (ETTP) (auto)
• PFE • PTP (ETTP) (auto)

Table 2-25

eMOTR • ODU2 TTP (WAN, • P10GSOEL • PTP (ETTP)

4xXFP/2xSFP+/ ETTP) • PTP (OTUTTP, ODUTTP,
8xSFP circuit pack • ODU2e TTP WAN Note 8, ETTP, ADJ)
(EMOTR) (ETTP)
(Note 7) NTK536BE • PXFP • PTP (ETTP)
• PTP (OTUTTP, ODUTTP,
WAN Note 8, ETTP, ADJ)
• PTP (OTUTTP, ODUCTP) when
Service Type is OTU2REGEN or
OTU2EREGEN
• P10GEL • PTP (ETTP) (auto)
• P2G5 • PTP (ETTP) (auto)
• PGE • PTP (ETTP) (auto)
• PGEFC • PTP (ETTP) (auto)
• PGEFC200 • PTP (ETTP) (auto)
• PSFP • PTP (ETTP) (auto)
• PFE • PTP (ETTP) (auto)

Table 2-25

Note 1: For supported pluggable modules on the L2SS, PDH gateway, 20G L2SS, L2 MOTR, eMOTR,
and RPR circuit packs: refer to Table 2-2 on page 2-6, Table 2-4 on page 2-19, Table 2-6 on page 2-34,
Table 2-7 on page 2-35, Table 2-2 on page 2-6, Table 2-10 on page 2-52, Table 2-2 on page 2-6, Table
2-18 on page 2-86, and Table 2-22 on page 2-110.
Note 3: Although PDH gateway circuit packs support PDH facilities (DS3WAN, DS1WAN, E3WAN, and
E1WAN), you cannot manually add these facilities. These facility types are auto-created and appeared
in Facility Type drop-down list only if corresponding cross-connects have been created.
Note 4: On the L2 MOTR circuit packs, ports 1 and 2 are the line interface ports, 10GE LAN or OTM2
(at 10.7G, 11.05G or 11.09G), and ports 3 to 12 are the client interface ports (GE).
Note 5: The standalone ETH10G facilities are supported on the PXFP variants of NTK583AA/AB and
NTK587Ex to NTK587Hx only. They are not supported on other PXFP variants.
to “10.7G - GFP/OPU2 (Standard MAC transparent)”.
Note 7: For more information on the rules related to this circuit pack, see “Provisioning rules summary
for the eMOTR circuit packs” on page 2-120.
Note 8: The WAN facility is auto-created only if the PTP service type is OTU2.
Note 9: The backplane facilities (except FTTP) are created when the eMOTR equipment profile is set
to 4x10G. The virtual port number is 100 if the left equipment profile is 4x10G, or 200 if the right
equipment profile (Equipment Profile 2) is 4x10G. The backplane FTTP facility is created when the PTP
facility is created on the mate 40G OCLD/Wavelength-Selective 40G OCLD. See Figure 2-19 on page
2-122 for more information about the supported facilities.

Procedure 2-6
Use this procedure to add a 2WAY or 2WAYPR path connection to a network
element for L2SS, 20G L2SS, PDH gateway, and RPR circuit packs. To create
an EVPL connection on 20G L2SS and L2 MOTR circuit packs, use
Procedure 2-7, “Adding an EVPL connection”.
Note: This is a generic procedure to enter a path connection using the

circuit packs listed above. For detailed information on each connection
type, recommendations for use of connection types for support of a
particular network configuration, and example networks, refer to "Path
connections management" in Part 1 of Configuration - Bandwidth and
Data Services, 323-1851-320.
This procedure does not apply to unidirectional connections (1WAY and

1WAYPR) for WAN facilities on L2SS, 20G L2SS, PDH gateway, and RPR
circuit packs.
Note: If you encounter a "Backplane bandwidth is fragmented" error

message during this procedure, refer to the “Backplane bandwidth
fragmentation” and “Backplane Bandwidth Query toolset” sections in Part
1 of Configuration - Bandwidth and Data Services, 323-1851-320.
Prerequisites
• ensure that Virtual concatenation is set to Enabled on the WAN port if
you require virtual concatenation. If virtual concatenation is required,
Refer to the "Editing facility parameters" procedure in Part 1 of
Configuration - Provisioning and Operating, 323-1851-310, for information
on how to edit facility parameters.


Step Action

2 Select Cross Connections: Path Connections from the Configuration
menu.
If this is the initial launch of the Path Connections application, no path
the Path Connections application display path connections based on the last
filter criteria.
4 If you Then go to
want to provision a Connection ID step 5
do not want to provision a Connection ID step 7
5 Click once in the Connection ID text field.

Refer to Table 2-51 on page 2-286 for supported options.
7 From the Rate drop-down list, select a signal rate.
Refer to Table 2-51 on page 2-286 for supported connection rates.
8 From the Type drop-down list, select a connection type.
Refer to Table 2-52 on page 2-287 for supported path connection types.
9 Select the required equipment, facility, AU3 or AU4 mapping, and payload
parameters from the drop-down lists for each of the following panels:
• From
• To
• Switch Mate (applicable to 2WAYPR connections only)
path connections and Table 2-52 on page 2-287 for allowable path
connections types between network configurations.
If only AU3 mapping is supported (when the port mode is SONET or an
STS3c/VC4 rate or above is selected), the AU3 and AU4 radio buttons do not
appear in the Add Cross-Connect dialog box.


Step Action
You must add the VT/VC connections in the last STS/J-K of a VCAT Enabled
WAN facility individually.
Note: For a VCAT connection, ensure ALL members of a VCAT group are
uniquely connected to a WAN port and there is no duplicated VCAT member.
For more information about VCAT and VCAT engineering rules refer to 6500
UPSR/SNCP is not supported on L2SS, 20G L2SS, PDH gateway, or RPR
endpoints. When you provision 2WAYPR connections, you must set the WAN
endpoints for L2SS, 20G L2SS, and PDH gateway circuit packs.
RPR WAN ports support only 2WAY connections on unprotected optical links
and BLSR/MS-SPRing protected links. When you use 2-Fiber
BLSR/MS-SPRing protection, you must enable the ENUT parameter for
connections for RPR WAN ports and passthrough connections.
10 If Then go to
the connection you are adding will carry RPR traffic step 11
through a 2-Fiber BLSR/MS-SPRing
otherwise step 12
11 Select the ENUT check box in the From and To panels.

Go to step 18.
12 Click Advanced in the From panel to open the Multi-Channel Selector
dialog box.
13 In the Multi-Channel Selector dialog box, under Available, select the
required channels for the path connections.
To select multiple channels, select the first channel and then:
• Hold down the Ctrl key while individually clicking once on each of the
remaining channels.
• Hold down the Shift key and select the last channel required in the list.
• Select Ctrl+A (the Ctrl and A keys together) to select all channels.
The path connections depend on the order of selection.

Multiple channels are available for L2SS, 20G L2SS, PDH gateway, and
RPR WAN facilities if virtual concatenation is enabled (refer to the equipment
and facility provisioning sections in Part 1 of Configuration - Provisioning and
Operating, 323-1851-310, for information on how to edit facility parameters).
14 Click the arrow pointing to the right (->).
15 Perform step 13 and step 14 for each remaining channel to be in the path
connections.


Step Action
16 When all the channels you require are under the Selected column, click OK.
17 Repeat step 12 to step 16 for the To and Switch Mate (applicable to
2WAYPR, connections only) panels.
When selecting multiple channels, you must select the same number of
channels in each of the From, To, Switch Mate (if applicable), and
Destination Mate (if applicable) panels.
18 If Then go to
the connection type is 2WAY or 2WAYPR and the step 19
From or To facility is a BLSR/MS-SPRing/HERS
otherwise step 20
19 If you want Then

to create a VT/VC access 2-Fiber check the VT Access
BLSR/MS-SPRing connection at the checkbox (see Note)
pass-through node, but you have not selected a and go to step 21
VT/VC rate in step 7 (for example, you selected
an STS/VC4 rate)
otherwise go to step 20
Note: For more information about the VT/VC accessed BLSR/MS-SPRing
feature, refer to the “VT/VC-accessed BLSR/MS-SPRing” section in Section
3 of Part 1 of Configuration - Bandwidth and Data Services, 323-1851-320.
20 Select the End NE A and End NE Z node from the APSIDs in the drop-down
lists in the BLSR/MS-SPRing Endpoints panel.
Note: These fields are available only if ENUT or Extra Traffic are not
selected.
provision additional connections Apply
If you are adding a single path connection, the path connection is added. If
the path connection cannot be added, an error message appears.
Go to step 22.
If you are adding multiple path connections, the Multiple Cross Connect
Add Confirmation dialog box appears. Check that the multiple path
connections are correct, and then click Yes. If the path connections cannot be
added, an error message appears.


Step Action
22 If in step 21 you clicked Then

Apply go to step 4
OK (Apply & Close) the procedure is complete.
When adding an add/drop connection to/from a
BLSR/MS-SPRing/HERS configuration, if you
provision the From endpoint on the add/drop port
and the To endpoint on the
BLSR/MS-SPRing/HERS add/drop port, the From
and To endpoints automatically swap. Click
Refresh to display the updated information.
—end—

Procedure 2-7
Use this procedure to add a 2WAY EVPL connection to a network element for
20G L2SS and L2 MOTR circuit packs. To create a path connection on L2SS,
20G L2SS, PDH gateway, and RPR circuit packs, use Procedure 2-6, “Adding
a path connection”.
Prerequisites
• ensure the equipment and facilities you need for the planned EVPL
connections are provisioned
Step Action

2 Select Cross Connections: EVPL Connections from the Configuration
menu.
If this is the initial launch of the EVPL Connections application, no EVPL
the EVPL Connections application display EVPL connections based on the
last filter criteria.
Refer to Table 2-54 on page 2-299 supported options.
5 Select a signal rate from the Rate drop-down list.
Refer to Table 2-54 on page 2-299 supported EVPL connection rates.
6 Select a connection type from the Type drop-down list.
Refer to Table 2-55 on page 2-300 for supported EVPL connection types.


Step Action
7 Select the required equipment and facility from the drop-down lists for each
of the following panels:
• From
• To
Note: The From and To endpoints must be on the same slot. If ETH10G is
part of a 1+1 OTN line-side protection, the From and To endpoints must be
on the odd slot.
EVPL connections.
8 Type the virtual circuit segment identifier in the VCID (1-1048575) field.
Refer to Table 2-54 on page 2-299 for supported VCID values.
Note: The From and To endpoints must have the same VCID.
9 Type the service provider VLAN identifier in the SVID (1-4094) field.
Refer to Table 2-54 on page 2-299 for supported SVID values.
provision additional connections Apply and go to step 4
—end—

Procedure 2-8
Adding a resilient packet ring
Use this procedure to add a resilient packet ring to an RPR circuit pack in a
network element. See Table 2-41 on page 2-240 for more information on RPR
provisioning parameters.
Prerequisites
• ensure that at least one RPR circuit pack is provisioned.
Step Action

2 Select Data Services: RPR Ring Management from the Configuration
menu to open the RPR Ring Management application.
The Provisioning tab of the RPR Ring Management application displays the
provisioned RPRs. See Table 2-41 on page 2-240 for details on the
provisioning parameters.
3 Click on Add in the ring list area to open the Add Ring dialog box.
4 Select a slot for the RPR circuit pack from the Name drop-down list.
5 Select a port from the Ring Port drop-down list.
6 Select a state from the Primary State drop-down list.
7 Type a name for the ring in the Ring Name field.
8 Type a name for the station in the Station Name field.
9 Select a wait-to-restore period in seconds from the Wait To Restore
drop-down list.
10 Select a fast time in ms from the Fast Timer drop-down list.
11 Select a slow time in ms from the Slow Timer drop-down list.
12 Select a keep alive time in ms from the Keep Alive Timeout drop-down list.
13 Select an attribute discovery message time in ms from the Attribute
Discovery Message drop-down list.
14 Select an attribute from the Even Station Path Control drop-down list.
15 Click OK (Apply & Close).
The Add Ring dialog box closes and the newly added ring appears in the ring
list of the Provisioning tab.
—end—

Procedure 2-9
Adding east and west protection spans in resilient
packet rings
Use this procedure to add spans to resilient packet rings. See Table 2-42 on
page 2-245 for more information on RPR protection parameters. For a closed
ring, you must add both east and west spans.
Prerequisites
• ensure that at least one RPR is provisioned according to Procedure 2-8
on page 2-141
Step Action

2 Select Data Services: RPR Ring Management from the Configuration
menu to open the RPR Ring Management application.
The Provisioning tab of RPR Ring Management application displays the
provisioned RPRs.
3 Select the Protection tab.
The Protection tab of the RPR Ring Management application displays the
provisioned RPR spans for the network element. See Table 2-42 on page
2-245 for details on the protection parameters.
5 Click on Add to open the Add Ring Protection dialog box.
6 Select a ring (RPR port) from the Ring drop-down list.


Adding east and west protection spans in resilient packet rings
Step Action
7 Select a WAN port from the Port drop-down list. You can provision the port
as follows:
• Ring (RPR port) 801 can be associated to WAN ports that have up to
5 Gbps provisioned on them.
• Ring (RPR port) 802 can be associated to WAN ports that have up to
2.5 Gbps provisioned on them.
• The sum of the bandwidth associated to the WAN ports on the RPR
circuit packs cannot exceed 10 Gbps in any slot if a 160 Gbps
cross-connect circuit pack is used or if the circuit pack is equipped in slots
5, 6, 9 or 10 of a 14-slot 6500 shelf with an 80 Gbps cross-connect circuit
pack.
• The sum of the bandwidth associated to the WAN ports on the RPR
circuit pack cannot exceed 5 Gbps if the circuit pack is equipped in slots
1 to 4 or 11 to 14 of a 14-slot 6500 shelf with an 80 Gbps cross-connect
circuit pack.
8 Select a direction from the Direction drop-down list.
9 Select a hold-off time from the Hold off time drop-down list.
10 Click OK (Apply & Close).
The Add Ring Protection dialog box closes and the span appears in the list of
spans in the Protection tab.
—end—

Procedure 2-10
Performing profiles provisioning tasks
Use this procedure to perform the Profiles Provisioning task, which allows you
to create bandwidth profiles. See Table 2-43 on page 2-247 for field definitions
and supported values for the bandwidth profile provisioning fields.
CAUTION
If you click on the New Task button at any time while
performing this procedure, a warning message appears
informing you that the current task is not complete. If you click
on Yes, all parameters change to their default values. In this
case, you must fix any possible provisioning inconsistencies
that may occur without help from the Service Activation Setup
application.
Prerequisites
UPC.
Step Action

2 Select Data Services: Service Activation Setup from the Configuration
menu to open the Service Activation Setup application.
If this is the initial launch of the Service Activation Setup application, no tasks
appear until you select a task from the Task drop-down list. Subsequent
launches of the Service Activation Setup application display tasks based on
the results from the last launch.
3 Select Profiles Provisioning from Task drop-down list.
The left-column window appears showing the Bandwidth Profile
Provisioning step.
The right-column window appears showing the fields applicable to adding a
bandwidth profile.
4 Add the bandwidth profile parameters in the right-column window according
to step 6 to step 14.


Step Action
6 Select a profile index from the Profile index (9-200) drop-down list.
The following seven profiles are predefined profiles with default values and
you cannot use them when creating a new profile: Profile 0 (Not Policed),
Profile 1 (Standard Default); Profile 3 (Silver Default); Profile 4 (Gold Default);
Profile 6 (Premium Default); Profile 7 (Network Default); Profile 8 (Discard
All).
7 Type in a profile name in the Profile name field.
8 Select a CIR units from the Committed Information Rate Units drop-down
list.
9 Type in a CIR in the Committed Information Rate field.
The Committed Information Rate field is read-only if the Committed
Information Rate Units value is set to 0 bps.
10 Type in a CBD in the Committed Burst Duration in ms (for 0 bps, 64 kbps,
1 Mbps, and 10 Mbps CIR units) or Committed Burst Duration in 100s of
µs (for 100 Mbps CIR units) field.
The Committed Burst Duration in ms field is read-only if the Committed
Information Rate Units value is set to 0 bps.
11 Select a value for the EIR units from the Excess Information Rate Units
drop-down list.
12 Type in an EIR in the Excess Information Rate field.
The Excess Information Rate field is read-only if the Excess Information Rate
Units value is set to 0 bps.
13 Type in a EBD in the Excess Burst Duration in ms (for 0 bps, 64 kbps,
1 Mbps, and 10 Mbps EIR units) or Excess Burst Duration in 100s of µs
(for 100 Mbps EIR units) field.
The Excess Burst Duration in ms field is read-only if the Excess Information
Rate Units value is set to 0 bps.
14 Select an OVSR from the Over-subscription Ratio drop-down list.
15 Select a policer from the Policer drop-down list.
16 Click Apply to create the bandwidth profile.


Step Action
17 If Then
your entries in step 4 are valid, the color you have created a bandwidth
of the task circle (Bandwidth Profile profile and completed this
Provisioning) in the left-column window procedure. Proceed to
becomes green Procedure 2-11, “Performing
service activation for virtual
circuits”, to create virtual circuits.
your entries in step 4 are not valid, the you must fix the problem before
task circle (Bandwidth Profile proceeding to Procedure 2-11 to
Provisioning) in the left-column window create virtual circuits.
is crossed and its color becomes red
—end—

Procedure 2-11
Performing service activation for virtual circuits
Use this procedure to perform service activation for virtual circuits, which
include provisioning VCSs, VCEs, and virtual circuit endpoint maps.
Refer to:
• Table 2-44 on page 2-250 for field definitions and supported values for the
VCS provisioning fields.
VCE provisioning fields.
virtual circuit endpoint mapping fields.
CAUTION
If you click on the New Task button at any time while
performing this procedure, a warning message appears
informing you that the current task is not complete. If you click
on Yes, all parameters change to their default values. In this
case, you must fix any possible network element provisioning
inconsistencies that may occur without help from the Service
Activation Setup application.
Prerequisites
UPC.
Step Action

2 Select Data Services: Service Activation Setup from the Configuration
menu to open the Service Activation Setup application.
If this is the initial launch of the Service Activation Setup application, no tasks
appear until you select a task from the Task drop-down list. Subsequent
launches of the Service Activation Setup application display tasks based on
the results from the last launch.


Step Action
3 Select Virtual Circuit Service Activation from the Task drop-down list.
The left-column window appears showing the VCS Provisioning step
highlighted.
The right-column window appears showing the fields applicable to adding a
VCS.
VCS Provisioning
4 Add the VCS parameters in the right-column window according to step 5 to
step 16.
6 Type a virtual circuit segment connection identifier in the Connection ID field.
7 Type in a virtual circuit segment identifier in the VC Segment ID (1-1048575)
field.
8 Click on the Validate button to open the Validate VC Segment ID dialog box.
If the message in this dialog box shows that the entered VC segment ID has
not been used, you can use this VC segment ID by clicking OK to close the
Validate VC Segment ID dialog box and then going to step 9. If the message
in this dialog box shows that the entered VC segment ID is in use, you cannot
use this VC segment ID and you must click OK to close the Validate VC
Segment ID dialog box, enter a different VC segment ID in the VC Segment
ID (1-1048575) field, and return to this step for re-validation.
9 Select a primary state from the Primary state drop-down list.
10 Select a queue group from the Queue group drop-down list.
11 Select a data type from the Data type drop-down list.
12 Select a topology from the Network topology drop-down list.
13 Select one or more classes of service by checking one or more check boxes
in the Class of service field.
14 Select a maximum transfer unit from the Maximum transfer unit drop-down
list.
15 Select the desired ring group that corresponds to the G.8032 ERP ringlet
group ID from the Ring Group ID drop-down list.
16 Click Apply to create the VCS.
17 If your entries in step 4 Then
are valid, the color of the task circle (VCS you have created a VCS. Click
Provisioning) in the left-column window Next to proceed to the VCE
becomes green creation step.
are not valid, the task circle (VCS you must fix the problem before
Provisioning) in the left-column window is proceeding to the VCE creation
crossed and its color becomes red step.


Step Action
VCE Provisioning
Note: You can only create a VCE on a LAG port if that port contains at least
one member. Adding VCEs to a 1+1 protected LAG can only be done on the
odd slot of L2 MOTR circuit packs while other VCEs can be either an
inter-card 1+1 OTM2 protected port or a G.8032 ERP protected port if G.8032
ERP is configured between two adjacent L2 MOTR circuit packs over M2M
port 91. VCEs on the even slot of L2 MOTR circuit packs are automatically
added.
18 Add the VCE parameters in the right-column window according to step 19 to
step 32.
19 Select a circuit pack from the Equipment drop-down list.
20 Select a port from the Port drop-down list.
21 Select a state from the State drop-down list.
22 Select a receive class of service profile from the Receive Class of Service
drop-down list.
23 Select a transmit class of service profile from the Transmit Class of Service
drop-down list.
24 Select whether the operational measurement statistics are to be enabled or
disabled from the Detailed OM Stats drop-down list.
25 If you have selected Then go to
an RPR port (801 or 802) in step 20 step 26
a port other than an RPR port (801 or 802) in step 20 step 29
26 Select a distribution algorithm from the Distribution Algorithm drop-down

list.
27 Select a distribution parameter from the Distribution Parameter drop-down
list.
Note: Distribution Parameter drop-down list is grayed-out if you have
selected Disable for Distribution Algorithm in step 26.
28 Select a distribution protection from the Distribution Protection drop-down
list.
29 Select a bandwidth profile for each class of service in the Bandwidth
Profiles Setup area. Click on the Select button to open the Select Bandwidth
Profile dialog box.
30 Choose the bandwidth profile from the table.


Step Action
31 Click OK to select the bandwidth profile and close the Select Bandwidth
Profile dialog box.
The selected bandwidth profile appears for each class of service in
Bandwidth Profiles Setup area.
32 Click Apply to create the VCE.
33 If Then
your entries in step 18 are you have created a VCE for a VCS.
valid, the color of the task Click Next to proceed to the endpoint map
circle (VCE Provisioning) in creation step.
the left-column window
becomes green
your entries in step 18 are not you must fix the problem before proceeding
valid, the task circle (VCE to the VC Endpoint Map Provisioning step.
Provisioning) in the
left-column window is crossed
and its color becomes red
34 If Then go to
your endpoint is a port on a VC Endpoint Map Provisioning (a port on a
L2SS, 20G L2SS, L2 MOTR, L2SS, 20G L2SS, L2 MOTR, or PDH
or PDH Gateway circuit pack Gateway circuit pack)
your endpoint is a port on a VC Endpoint Map Provisioning (a port on a
RPR circuit pack RPR circuit pack)
VC Endpoint Map Provisioning (a port on a L2SS, 20G L2SS, L2 MOTR, or PDH Gateway circuit
pack)
35 Add the endpoint map parameters in the right-column window according to
step 36 to step 56.
36 Type a mapping ID in the Mapping ID (0-4098) field.
Note: Tx direction and “Rx direction->Tags to match -> Inner local tag” are
not supported on L2 MOTR circuit packs.
Tx direction in step 37 (only applies to UNI ports) step 39
Rx direction in step 37 (only applies to UNI ports) step 47
TXADDRXDEL direction in step 37 (only applies step 53
to NNI ports)


Step Action
39 Select whether you want to match the outer or both outer and inner VLAN
tags from the Tags to match drop-down list.
40 Select whether you want to delete the remote VLAN tags from the Remote
tags to delete drop-down list.
41 Depending on the selection you made in step 39, select the appropriate radio
button in the Outer remote tag and Inner remote tag areas (the items that
are not applicable are grayed out).
42 If you have selected radio button Specific tag (0-4095) in step 41, then a
specific tag value between the range of 0 to 4095 must be entered.
43 Select the appropriate radio button in the Outer local tag or Inner local tag
areas (the items that are not applicable are grayed out).
45 In Outer local tag area, select the following parameters if the item is not
grayed out.
• outer local tag action from the Action drop-down list.
• outer local priority source from the Priority source drop-down list.
• outer local priority from the Priority drop-down list.
• outer local Ether Type from the etherType drop-down list.
46 In Inner local tag area, select the following parameters if the item is not
grayed out.
• inner local tag action from the Action drop-down list.
• inner local priority source from the Priority source drop-down list.
• inner local priority from the Priority drop-down list.
• inner local Ether Type from the etherType drop-down list.
Go to step 56.
47 Select Allow or Filter from the Access drop-down list.
To use the Filter option, you must have previously provisioned an endpoint
map with the outer local tag set to All unprovisioned tagged Frames.
48 Select whether you want to match the outer or both outer and inner VLAN
tags from the Tags to match drop-down list.
49 Depending on the selection you made in step 48, select the appropriate radio
button in the Outer local tag and Inner local tag areas (the items that are
not applicable are grayed out).
51 Select the receive priority source in the Rx priority source drop-down list.


Step Action
52 Choose the priority bits by checking one or more check box items in Priority
Bits area. This step is optional. If you have chosen All untagged frames
(4096) for the local tag, you must uncheck all check box items for priority bits
as priority bits are not supported when the local customer tag is 4096.
Note: For 20G L2SS and L2 MOTR circuit packs, you must check all check
boxes in Priority Bits area.
Go to step 56.
53 Select an Ether Type value from the etherType drop-down list.
54 Select the appropriate radio button in the Outer local tag area (the items that
56 Click Apply to create the virtual circuit endpoint map.
57 If Then
your entries in step 35 are valid, the color of you have created an endpoint
the task circle (VC Endpoint Map map. Go to step 58.
Provisioning) in the left-column window
becomes green
your entries in step 35 are not valid, the task you must fix the problem
circle (VC Endpoint Map Provisioning) in the before proceeding to step 58.
left-column window is crossed and its color
becomes red
58 If Then
you only added one VCE in the VCS you must create another
Provisioning section of this procedure VCE for the VCS by clicking
Add more VCEs. Go to
step 18 to add another VCE.
you want to create more than one endpoint click on Add more maps
map (only possible for a UNI VCE) and go to step 35
you have added both VCEs (UNI or NNI) for you have completed this
the VCS and all endpoint maps have been procedure
created


Step Action
VC Endpoint Map Provisioning (a port on a RPR circuit pack)

59 Add the endpoint map parameters in the right-column window according to
step 60 to step 70.
60 Type a mapping ID in the Mapping ID (0-4098) field.
Tx direction in step 61 (only applies to UNI ports) step 63
Rx direction in step 61 (only applies to UNI ports) step 65
TXADDRXDEL direction in step 61 (only applies step 68
to NNI ports)
63 Select the appropriate radio button in the Outer remote tag area (the items
that are not applicable are grayed out).
64 In Outer local tag area, select the following parameters if the item is not
grayed out.
• outer local tag action from the Action drop-down list.
• outer local priority source from the Priority source drop-down list.
• outer local priority from the Priority drop-down list.
• outer local Ether Type from the etherType drop-down list.
Go to step 70.
65 Select Allow or Filter from the Access drop-down list.
To use the Filter option, you must have previously provisioned an endpoint
map with the outer local tag set to All untagged and tagged frames.
66 Select the appropriate radio button in the Outer local tag area.
67 Choose the priority bits by checking one or more check box items in Priority
Bits area. This step is optional. If you have chosen All untagged frames
(4096) for the local tag, you must uncheck all check box items for priority bits
as priority bits are not supported when the local customer tag is 4096.
Go to step 70.
68 Select an Ether Type value from the etherType drop-down list.
69 Select the appropriate radio button in the Outer local tag area (the items that
70 Click Apply to create the virtual circuit endpoint map.


Step Action
71 If Then
your entries in step 59 are valid, the color of you have created an endpoint
the task circle (VC Endpoint Map map. Go to step 72.
Provisioning) in the left-column window
becomes green
your entries in step 59 are not valid, the task you must fix the problem
circle (VC Endpoint Map Provisioning) in the before proceeding to step 72
left-column window is crossed and its color
becomes red
72 If Then
you only added one VCE in the VCS you must create another
Provisioning section of this procedure VCE for the VCS by clicking
Add more VCEs. Go to
step 18 to add another VCE.
you want to create more than one endpoint click on Add more maps
map (only possible for a UNI VCE) and go to step 59
you have added both VCEs (UNI or NNI) for you have completed this
the VCS and all endpoint maps have been procedure
created
—end—

Procedure 2-12
Provisioning the network element timing mode and
references
Use this procedure to provision the timing generation (timing mode and
references) for the network element. The timing mode can be set to:
• internal timing—the shelf timing is derived from an internal clock on the
cross-connect circuit pack
• line timing—the shelf timing is derived from received OTM2/ETH10G/
ETTP/OTUTTP signal
• external timing—the shelf timing is derived from the BITSIN/ESI ports
• mixed timing—the shelf timing is derived from OTM2/ETH10G/
ETTP/OTUTTP ports or BITSIN/ESI ports
For line timing, external timing, and mixed timing, a hierarchy of up to four
reference sources can be provisioned. The timing generation selects the
source in the hierarchy with the highest derived quality level for the shelf
timing. If there is more than one source at the highest derived quality level, the
timing generation selects the highest priority source in the hierarchy from
references with the same derived quality level (first is the highest priority and
fourth is the lowest priority). To provision a timing source from an
OTM2/ETH10G/ETTP/OTUTTP port, the reference source must be logically
equipped.
If a reference source is selected as the active source, the reference source

cannot be deprovisioned (Source changed to None). To deprovision the active
source, you first must either perform a manual switch to another source or a
If a reference source is not selected as the active source, it can be

deprovisioned (Source changed to None). It is recommended that you perform
a lockout of the reference source before deprovisioning it.
The internal timing source is provided by a SONET/SDH-compliant Stratum

3/G.813 Option 1 free running clock (±4.6 ppm) produced within the network
element. Sources of line timing are OTM2/ETH10G/ETTP/OTUTTP facilities.


Prerequisites
• use an account with a level 3 UPC or higher
• have a network synchronization plan for the network element
Step Action

2 Select Synchronization from the Configuration drop-down menu to open
the Synchronization application.
4 If you want to provision Then go to
the timing mode and references of an independent timing step 5
group
otherwise step 6
5 Select the required Timing Group Name for the independent timing group for
which you wish to change the mode.
6 Select the Timing Generation tab.
7 Click Edit to open the Synchronization Edit dialog box.
8 Select Timing Mode & References from the Type drop-down list.
9 From the network synchronization plan, determine the timing mode required.
Select the required Timing mode radio button to set the timing mode for the
network element.
CAUTION
Risk of timing loops
To avoid timing loops, verify the clock source setting of
each network element in the network. An incorrect
clock source setting can cause a service outage.
In case of provisioning an independent timing group, you have the options of

only Line Timing and Internal Timing, and external or mixed timing modes
are not supported. In case of selecting Line Timing, you can choose up to
two references for this timing group. You must note that:
• all references must be chosen from valid facilities which are on the
equipment contained within the independent timing group
• at most, one reference per circuit pack
In general, the Timing mode radio buttons are disabled if both cross-connect
circuit packs are missing.


Step Action
Except when changing the timing mode from line timing or external timing to
mixed timing, you must remove all references from the hierarchy (set the
references to None, see step 10) before changing the timing mode.
10 From the network synchronization plan, determine the references to be
provisioned. For each timing generation reference to be provisioned, select
the timing reference from the appropriate source drop-down list, leave all
other possible references as None. See Table 2-40 on page 2-239.
• Only one port of each multi-port circuit pack can be used as a timing
reference source.
• The available options from the source drop-down lists are dependent on
the selected timing mode. Only logically equipped sources are available
for selection.
• You cannot remove the active reference source from the hierarchy. To
remove the active source from the timing generation hierarchy, you first
must either perform a manual switch away from the active source or a
• If a reference source is not selected as the active source, it can be
removed from the timing generation hierarchy. It is recommended that
you perform a lockout of the reference source before removing it from the
timing generation hierarchy.
• E1, E3, DS3, EC-1, DS1DS3, E1DS3, E1E3, STM1E, GE, 10GE,
10/100BT, L2SS, PDH gateway, and RPR facilities cannot be set as
• DS1 DSM facilities and OC-3 ports which are provisioned as DSM hosts
cannot be set as line synchronization source references.
11 Click OK.
12 Click Yes in the confirmation dialog box.
13 If the Synchronization Protection application is open, click Refresh in the
Synchronization Protection application to update the application with the
changes you have made to the hierarchy.
—end—

Procedure 2-13
Creating a ring in a G.8032 ERP
Use this procedure to create a ring in a G.8032 ERP on a network element.
See Table 2-47 on page 2-268 for field definitions and supported values.
This procedure uses the “Ring Provisioning” tab in the G.8032 ERP
Management application.
CAUTION
While creating a ring, make sure you are using consistent
Ring ID-Ringlet Port at each node of the network. Failure
to do so will create Time Out alarm during node upgrade.
Prerequisites
UPC.
Step Action

2 Select Data Services: G.8032 ERP Management from the Configuration
menu to open the G.8032 ERP Management application.
The Ring Provisioning tab appears in the foreground.
If this is the initial launch of the G.8032 ERP Management application, no
rings appear until you perform a Retrieve. Subsequent launches of the
G.8032 ERP Management application display rings based on the results from
the last launch.
3 Click Add in the Filter area to open the Add Ring dialog box.
4 Select an equipment from the Equipment drop-down list.
5 Type a ring identifier in the Ring ID (1-255) field.
6 Click on the Validate button to open the Validate Ring ID dialog box. If the
message in this dialog box shows that the entered ring ID has not been used,
you can use this ring ID by clicking OK to close the Ring ID dialog box and
then going to step 7. If the message in this dialog box shows that the entered
ring ID is in use, you cannot use this ring ID and you must click OK to close
the Validate Ring ID dialog box, enter a different Ring ID in the Ring ID
(1-255) field, and return to this step for re-validation.
7 Select a guard time from the Guard Time drop-down list.
8 Select a wait to restore time from the Wait To Restore drop-down list.


Creating a ring in a G.8032 ERP
Step Action
9 If you Then click

want to add more rings Apply and go to step 4
do not want to add more rings OK (Apply & Close)
—end—

Procedure 2-14
Creating a ring port in a G.8032 ERP
Use this procedure to create a ring port in a G.8032 ERP.
This procedure uses the “Ring Provisioning” tab in the G.8032 ERP
Prerequisites
Before you perform this procedure, you must
• ensure that the ring is created. See Procedure 2-13, “Creating a ring in a
G.8032 ERP”.
• use an account with a level 3 UPC or higher.
Step Action

rings appear until you perform a Retrieve. Subsequent launches of the
G.8032 ERP Management application display rings based on the results from
the last launch.
3 Click Retrieve to populate the Filter area with the provisioned rings.
4 Select the required ring in the rings list of the Filter area.
You can hide the details area by clicking on the arrow next to the Details label.
If the details area is not visible, click on the arrow next to the details label.
5 Click Add in the Ring Port Provisioning tab in the Details area to open the Add
Ring Port dialog box.
6 Select a facility from the Facility drop-down list.
7 Select a hold off time from the Hold Off Time drop-down list.
8 Select a maintenance end point from the MEP drop-down list.
9 If you Then click
want to add more ring ports Apply and go to step 6
do not want to add more ring ports OK (Apply & Close)
—end—

Procedure 2-15
Creating a ringlet in a G.8032 ERP
Use this procedure to create a ringlet in a G.8032 ERP on a network element.
See Table 2-49 on page 2-277 for field definitions and supported values. A
ringlet and its associated ringlet ports have the same ring ID and the same
group ID.
This procedure uses the “Ringlet Provisioning” tab in the G.8032 ERP
Prerequisites
UPC.
Step Action

3 Select the Ringlet Provisioning tab.
ringlets appear until you perform a Retrieve. Subsequent launches of the
G.8032 ERP Management application display ringlets based on the results
from the last launch.
4 Click Add in the Filter area to open the Add Ringlet dialog box.
5 Select an equipment from the Equipment drop-down list.
6 Select a ring from the Ring drop-down list.
7 Select a group ID from the Group ID drop-down list.
8 Type an APS VID in the APS VID (1-4094) field.
9 Select an APS type from the APS Type drop-down list.
10 Select a RPL port from the RPL Port drop-down list.
11 If you Then click
want to add more ringlets Apply and go to step 5
do not want to add more ringlets OK (Apply & Close)
—end—

Procedure 2-16
Creating a ringlet port in a G.8032 ERP
Use this procedure to create a ringlet port in a G.8032 ERP.
A ringlet and its associated ringlet ports have the same ring ID and the same
group ID. This procedure uses the “Ringlet Provisioning” tab in the G.8032
ERP Management application.
Prerequisites
Before you perform this procedure, you must
• ensure that the ringlet is created. See Procedure 2-15, “Creating a ringlet
in a G.8032 ERP”.
• use an account with a level 3 UPC or higher.
Step Action

3 Select the Ringlet Provisioning tab.
ringlets appear until you perform a Retrieve. Subsequent launches of the
G.8032 ERP Management application display ringlets based on the results
from the last launch.
4 Click Retrieve to populate the Filter area with the provisioned ringlets.
5 Select the required ringlet in the ringlets list of the Filter area.
You can hide the details area by clicking on the arrow next to the Details label.
If the details area is not visible, click on the arrow next to the details label.
6 Click Add in the Ringlet Port Provisioning tab in the Details area to open the
Add Ringlet Port dialog box.
7 Select a facility from the Facility drop-down list.
8 Select an APS role from the APS Role drop-down list.
9 If you Then click
want to add more ringlet ports Apply and go to step 7
do not want to add more ringlet ports OK (Apply & Close)
—end—

Procedure 2-17
Changing the L2 MOTR equipment profile
Use this procedure to change the L2 MOTR equipment profile from
L2STANDARD (default) to L2EXTENDED or L2STANDARD_EXT_OM, which
determines the supported L2 services.
Note 1: To change the L2 MOTR equipment profile, make sure none of

the following is provisioned on the L2 MOTR circuit pack:
VCS/VCE/VCEMAPs, 1+1 OTN protection, 1+1 LAG protection, mate to
mate ports, ETH-OAM connected to a service.
Note 2: Changing the L2 MOTR equipment profile between
L2STANDARD/L2STANDARD_EXT_OM and L2EXTENDED will result in
a cold restart of the L2 MOTR circuit pack. Changing the L2 MOTR
equipment profile between L2STANDARD and L2STANDARD_EXT_OM
will result in a warm restart of the L2 MOTR circuit pack.
Prerequisites
• ensure none of the following is provisioned on the L2 MOTR circuit pack:
— VCS/VCE/VCEMAPs
— 1+1 OTN protection
— 1+1 LAG protection
— mate to mate ports
— ETH-OAM connected to a service
Step Action

4 In the Equipment area, select the L2MOTR equipment that you want to
change the equipment profile.


Changing the L2 MOTR equipment profile
Step Action
5 Ensure there are no VCS/VCE/VCEMAPs, 1+1 OTN protection, 1+1 LAG

protection, mate to mate ports, or ETH-OAM connected to a service
provisioned on the L2 MOTR circuit pack.
7 Select the required equipment profile from the Equipment Profile drop-down
list.
8 Click OK.
—end—

Procedure 2-18
Editing facility parameters
Use this procedure to edit the facility parameters for a facility. LAG on eMOTR
is configured with SAOS-based CLI.
Prerequisites
UPC.
Step Action

select the circuit pack or pluggable whose facilities you want to edit.
5 Select the appropriate facility from the Facility Type drop-down list if more
than one facility type is supported. See Table 2-25 on page 2-130 for facilities
supported on interface circuit packs and pluggable ports.
6 In the Facility area, select the facility you want to edit.
7 Click Edit in the Facility area to open the Edit Facility dialog box.
8 Select the required parameters from the drop-down lists.
For multiple facilities, selecting <no change> from the drop-down lists leaves
the parameter unchanged for the selected facilities.
See the following for facility attribute descriptions (note that read-only
parameters are greyed out or not displayed):
• “LAG facility parameters” on page 2-218
• “PTP facility parameters” on page 2-232
• “OTUTTP facility parameters” on page 2-233
• “ETTP facility parameters” on page 2-235
• “ODUTTP facility parameters” on page 2-237
9 Click OK.
—end—

Procedure 2-19
Creating an equipment group and adding members
Use this procedure to create an equipment group and add an equipment
group member. This procedure is applicable to eMOTR and 40G
OCLD/Wavelength-Selective 40G OCLD only.
By default, each eMOTR inserted in the 6500 NE is automatically provisioned

in an independent equipment group (EQPTGRP-shelf-slot). You cannot add a
member to an auto-created equipment group.
Manually created equipment groups (EQPTGRP-shelf-groupID) can have a

maximum two member eMOTR circuit packs. Mate-to-mate bandwidth is
automatically provisioned between eMOTR circuit packs. The two member
eMOTR circuit packs must be of the same type (both single slot or dual slot)
and equipped in adjacent slots. The Equipment Profile2 of the left eMOTR and
the Equipment Profile of the right eMOTR must be None.
When adding the second eMOTR to an equipment group, the second eMOTR
cannot have saved or active L2 configurations on any of its ETTP ports, that
is, the L2 Saved Config and L2 Active Config ETTP parameters must be No.
The existing eMOTR in the equipment group cannot have saved or active L2
configurations on any of its in-service ETTP ports.
On a 14-slot shelf, two single slot eMOTR circuit packs in slots 6/7, 7/8, or 8/9
cannot be added to the same equipment group. Two dual slot eMOTR circuit
packs in slots 5/7, or 7/9 cannot be added to the same equipment group.
On the 2-slot shelf (NTK503LA variant), two single slot eMOTR circuit packs
in the same equipment group is not supported.
Manually created equipment groups can have two adjacent eMOTR circuit
packs in the middle and one 40G OCLD/Wavelength-Selective 40G OCLD
circuit pack to the left and one 40G OCLD/Wavelength-Selective 40G OCLD
circuit pack to the right. The eMOTR is mated when PTP facility is created on
the mate 40G OCLD/Wavelength-Selective 40G OCLD, The two mate 40G
OCLD/Wavelength-Selective 40G OCLD circuit packs can have different
product engineering codes (PEC). The Equipment Profile of the left eMOTR
and the Equipment Profile 2 of the right eMOTR must be 4x10G.


The eMOTR circuit packs must be added to the equipment group first. There
must be no existing facilities on the 40G OCLD/Wavelength-Selective 40G
OCLD circuit packs before they can be added to the equipment group. When
adding the 40G OCLD/Wavelength-Selective 40G OCLD into the equipment
group, all in-use facilities on eMOTR must be OOS. If line timing is provisioned
on the eMOTR, both eMOTRs in the equipment group must be the
NTK536AB/NTK536FB variants, or the request will be blocked.
The supported slots for a four-card equipment group involving single slot
eMOTR circuit packs are x to x+3, where x = 1 to 3 in a 6500-7 packet-optical
shelf; x = 1 to 4 in a 7-slot shelf; x = 1 to 3 and 9 to 11 in a 14-slot shelf; x= 1,
3, 5, 11, 13, 15, 21, 23, 25, 31, 33, 35 in a 32-slot shelf.
The supported slots for a four-card equipment group involving dual slot
eMOTR circuit packs are {x, x+1, x+3, x+5}, where x = 1 in a 6500-7
packet-optical shelf; x = 1 in a 7-slot shelf; x = 1 and 9 in a 14-slot shelf; x= 1,
13, 21, and 33 in a 32-slot shelf.
Two-card equipment groups (OCLD-single eMOTR or single eMOTR-OCLD)

are supported in the same shelf types with the same slot assignment as
four-card equipment groups. For example, a four-card configuration is
supported in slots 1 to 4 (OCLD-eMOTR-eMOTR-OCLD) of 6500-7
packet-optical, 7-slot, 14-slot, and 32-slot shelves, meaning a two-card
configuration can be defined in slots 1 and 2 (OCLD-eMOTR) or in slots 3 and
4 (eMOTR-OCLD).
The four-card slots can be configured as two independent two-card

configurations, or the two unused slots can be used for other services. A
two-card equipment group can be expanded to a four-card configuration by
the addition of an eMOTR-OCLD or OCLD-eMOTR pair to the provisioned
equipment group. A four-card configuration can be reduced to a two-card
configuration by deleting an eMOTR-OCLD or OCLD-eMOTR pair from the
provisioned equipment group.
The two-card configuration (OCLD-single eMOTR) is also supported in the

2-slot shelf (NTK503LA w/ SPAP-2 w/2xOSC), where the OCLD is in slot 1
and the eMOTR is in slot 2.
If the OCLD is to the left of the eMOTR, the Equipment Profile of the eMOTR
must be 4x10G. If the OCLD is to the right of the eMOTR, the Equipment
Profile 2 of the eMOTR must be 4x10G.


If the network element is managed using OneControl, refer to the “Managing

eMOTR equipment group changes” section in OneControl Service
Management Guide, 450-3201-302, for more information.
Step Action

2 Select Equipment Group from the Configuration drop-down menu to open
the Equipment Group application.
4 Click Add to open the Add Equipment Group dialog.
5 Select a group ID (101 to 138) in the Id drop-down list.
6 Enter a description (a string of up to 32 characters, optional) in the Label field.
7 Click OK.
8 To add a member to an equipment group, select a manually created
equipment group (EQPTGRP-shelf-groupID) in the equipment group list.
9 Click Add Equipment.
10 In the Add Equipment to Group dialog, select the required eMOTR or
40GOCLD equipment in the Equipment drop-down list and click OK.
—end—

Procedure 2-20
Changing the eMOTR equipment profile
Use this procedure to change the eMOTR equipment profile to 4x10G or
None.
You cannot change Equipment Profile to None if there is an OCLD in the

equipment group on the left of eMOTR or Equipment Profile 2 to None if there
is an OCLD in the equipment group on the right of eMOTR. If two eMOTRs are
mated in the equipment group, you cannot change the Equipment Profile of
the right eMOTR or the Equipment Profile 2 of the left eMOTR to 4x10G.
Prerequisites
• ensure any facilities that exist on the virtual backplane ports of the eMOTR
are OOS and disconnected if you are changing the eMOTR equipment
profile from 4x10G to None
Step Action

4 In the Equipment area, select the eMOTR equipment for which you want to
change the equipment profile.
6 Select the required left equipment profile from the Equipment Profile
drop-down list.
7 Select the required right equipment profile from the Equipment Profile 2
drop-down list.
8 Click OK.
—end—

Procedure 2-21
Use this procedure to change the primary state of a facility.
CAUTION
If you place a facility out-of-service, you can cause a loss of
traffic.
The primary state of an ETH10G and the associated WAN facility

auto-created when the ETH10G packet mapping is set to “10.7G - GFP/OPU2
(Standard MAC transparent)” on the L2MOTR circuit pack is automatically
inherited from the same primary state as the OTM2 facility on the same port
if the OTM2 facility exists.
The primary state of a WAN facility in a L2 MOTR, 20G L2SS, L2SS, PDH
gateway, or RPR circuit pack is automatically inherited from the same primary
state as the L2 MOTR, 20G L2SS, L2SS, PDH gateway, or L2RPR equipment
at the creation. The primary state of a WAN facility in a L2 MOTR, 20G L2SS,
L2SS, PDH gateway, or RPR circuit pack is independent of the ETH facilities
or GE SFP state since WAN facilities in a 20G L2SS, L2SS, PDH gateway or
RPR circuit pack have no specific association to GE SFPs in that 20G L2SS,
L2SS, PDH gateway, or RPR circuit pack.
The primary state of a PDH facility (DS3WAN,DS1WAN, E3WAN, or E1WAN)

in a PDH gateway circuit pack is automatically inherited from the same
primary state as the associated WAN facilities (the WAN facilities that were
used to add the cross-connect in order to create the PDH facility).
The conditioning actions at the far end LAN link of taking the ETH facility
out-of-service depend on the setting of the Conditioning Type parameter. The
far end ETH facility (if on a 6500 network element) will turn off the laser if the
near end ETH facility is taken out-of-service (if Conditioning Type is set to
Enable on the near end ETH facility). See Table 2-29 on page 2-180.
On the eMOTR circuit packs, the primary state of all child facilities is managed
through the parent PTP facility for faceplate ports. The state of the child ETTP
and WAN facilities on the eMOTR backplane (for mating with 40G
OCLD/Wavelength-Selective 40G OCLD) is managed through the state of
their parent ODU2/ODU2E ODUTTP.


Prerequisites
UPC.
Step Action

select the circuit pack or pluggable whose facility state you want to change.
6 In the Facility area, select the facility whose state you want to change.
For circuit packs that support multiple facilities, you can select multiple
facilities as follows:
some but not all hold down the Ctrl key while clicking on each required
facilities facility
all facilities select the first facility in the list and hold down the
Shift key while clicking once on the last facility in the
list.
or
select any facility in the list and then Ctrl+A (Ctrl and
A keys together) to select all facilities.
7 Click Edit in the Facility area to open the Edit facility dialog box.
8 Select OOS or IS from the Primary state drop-down list.
For multiple facilities, selecting <no change> from the drop-down lists leaves
the primary state unchanged for the selected facilities.
9 Click OK.
If changing the primary state to OOS, a Warning dialog appears.
This command may cause a LOSS IN TRAFFIC.
Are you sure you want to continue?
—end—

Procedure 2-22
Changing the primary state of a circuit pack or
pluggable
Use this procedure to change the primary state of a circuit pack or pluggable
to in-service or out-of-service.
You cannot change the primary state of a pluggable to in-service if the

associated circuit pack is out-of-service.
You must change the primary state of any related facilities to out-of-service
before changing the primary state of a circuit pack or pluggable to
out-of-service, see Procedure 2-21, “Changing the primary state of a facility”.
The exceptions are facilities on L2SS/20GL2SS working and PDH gateway
working circuit packs with 1+1 equipment protection where you can change
the primary state of the circuit pack without changing the corresponding
facilities to out-of-service (an Equipment OOS with subtending facilities IS
alarm is raised in this condition).
Changing the primary state of a circuit pack automatically changes the

primary state of any provisioned pluggables on that circuit pack to the same
state.
Prerequisites
UPC.
Step Action

4 If you are changing the primary state to Then go to
OOS step 5
IS step 7


Changing the primary state of a circuit pack or pluggable
Step Action
5 If you intend to change the primary state of a Then

20G L2SS/L2SS working or PDH gateway the related facilities can be
working circuit pack in a 1+1 equipment IS. Go to step 7.
protection
otherwise the related facilities must be
put OOS. Go to step 6.
6 Ensure any related facilities are out-of-service. See Procedure 2-21,

7 Select the circuit pack or pluggable in the Equipment area.
9 Select IS or OOS from the Primary state drop-down list.
10 Click OK.
11 If you are changing the primary state to OOS, click Yes in the warning dialog
box.
—end—

Procedure 2-23
Use this procedure to delete a facility.
CAUTION
If you delete a facility, you can cause a loss of traffic.
Facilities that are auto-created (facilities in brackets in Table 2-25 on page

2-130) when the main facility is created will be auto-deleted when the main
facility is deleted.
Note also that deleting:

• an ETH, ETH100, or ETH10G facility in a 20G L2SS, L2SS, PDH gateway,
or RPR circuit pack does not affect WAN facilities on that 20G L2SS,
L2SS, PDH gateway, or RPR circuit pack.
• an ETH, ETH100, or ETH10G facility already part of a LAG or a LAG
containing at least one ETH, ETH100, or ETH10G facility in a L2 MOTR,
20G L2SS, L2SS, PDH gateway, or RPR circuit pack will be rejected by the
system. You must first remove the ETH, ETH100, or ETH10G facility from
its LAG before you can delete that ETH, ETH100, or ETH10G facility or the
LAG facility.
You cannot manually delete PDH facilities (DS3WAN, DS1WAN, E3WAN, and
E1WAN). These facility types are created automatically and appeared in
Facility Type drop-down list only if corresponding cross-connects have been
created. You must delete the corresponding cross-connect in order to delete
the PDH facilities.
Deleting the PTP facility on eMOTR also deletes all the auto-created child
facilities. The PTP facility can only be deleted if:
• The PTP facility state has been changed to OOS.
• No dependent SAOS configuration exists. The L2 Active Config and L2
Saved Config parameters of the ETTP port must indicate No. If both
eMOTR members in an equipment group are missing or mismatched, you
can delete the PTP facility even if a dependent SAOS configuration exists.
• No loopback, GCC comms, or timing reference is provisioned on a child
facility.
• All of its auto-created child facilities can be deleted.


Deleting a backplane ODU3TTP on eMOTR also deletes all the auto-created

child facilities. The ODUTTP facility can only be deleted if:
• The ODUTTP facility state has been changed to OOS.
• No dependent SAOS configuration exists. The L2 Active Config and L2
Saved Config parameters of the ETTP port must indicate No.
• No loopback, GCC comms, or timing reference is provisioned on the
facility or a child facility.
The eMOTR backplane FTTP is deleted when the PTP on the mate 40G
OCLD/Wavelength-Selective 40G OCLD is deleted.
Prerequisites
• ensure the end-to-end service to be deleted is not carrying traffic
• ensure the facility to be deleted is out-of-service and is not in maintenance
state
• delete the sub-network connection if provisioned on this facility. Refer to
the “Deleting a sub-network connection” procedure in Configuration -
Control Plane, 323-1851-330.
• delete the connections of the entire path that terminates on this facility.
procedures in Part 1 of Configuration - Bandwidth and Data Services,
323-1851-320.
• delete the IISIS circuit or OSPF circuit and then the GCC link if provisioned
on the facility to be deleted or on the child OTUTTP or ODUTTP of a PTP
facility to be deleted. Refer to the “Deleting an entry in the communications
settings” procedure in Part 1 of Configuration - Provisioning and
Operating, 323-1851-310.
• delete the timing reference if it is provisioned on the facility or a child
OTUTTP or ETTP of a PTP facility to be deleted, refer to the “Provisioning
the network element timing mode and references” procedure in Part 2 of
Configuration - Provisioning and Operating, 323-1851-310
• ensure that no loopback exists on the facility or a child OTUTTP or ETTP
of a PTP facility to be deleted. Refer to the “Operating/releasing a
loopback” procedure in Part 1 of Configuration - Provisioning and
Operating, 323-1851-310 to release a loopback if it exists.
• delete all the VCEs against the facility to be deleted in the L2MOTR, 20G
L2SS, L2SS, PDH gateway, or RPR circuit pack


• delete all the TNEs against the facility to be deleted in the RPR circuit pack
• ensure that the WAN facility to be deleted is not part of an RPR ring in the
RPR circuit pack. For more information about RPR rings, refer to the “Data
services resilient packet ring management” chapter in Part 2 of
Configuration - Bandwidth and Data Services, 323-1851-320
Step Action

select the circuit pack or pluggable whose facilities you want to delete.
5 Select the appropriate facility from the Facility Type drop-down list if more
than one facility type is supported.
7 In the Facility area, select the facility you want to delete.
For circuit packs that support multiple facilities, you can select multiple
facilities as follows:
some but not all facilities hold down the Ctrl key while clicking on each
required facility
all facilities select the first facility in the list and hold down
the Shift key while clicking once on the last
facility in the list.
or
select any facility in the list and then Ctrl+A
(Ctrl and A keys together) to select all facilities
8 Click Delete in the Facility area.

—end—

Procedure 2-24
Deleting a circuit pack or pluggable
Use this procedure to delete a circuit pack or pluggable equipment from the
list of provisioned equipment in the Equipment and Facility Provisioning
application. Deleting a circuit pack automatically deletes any provisioned
pluggables on that circuit pack.
Prerequisites
• delete all connections provisioned through the equipment,
procedures in Part 1 of Configuration - Bandwidth and Data Services,
323-1851-320.
• delete all facilities on the circuit pack and all facilities on its associate
pluggables, see Procedure 2-23, “Deleting a facility from an equipment”.
• deprovision all timing references on the L2MOTR or eMOTR circuit pack
to be deleted and make sure that it does not have any other circuit packs
within its timing group. Refer to the “Provisioning the network element
timing mode and references” procedure in Part 2 of Configuration -
Provisioning and Operating, 323-1851-310.
• put the circuit pack or pluggable to be deleted out-of-service, see
Procedure 2-22, “Changing the primary state of a circuit pack or
pluggable”.
Step Action

4 In the Equipment area, select the equipment (circuit pack or pluggable) you
want to delete.
5 Click Delete in the Equipment area.
—end—

Equipment and facility provisioning parameters

Equipment and facility primary and secondary states
The table that follows provides information on equipment and facility primary
states.
Table 2-26
Equipment and facility primary states
Primary State Description
IS In-service; no failure detected
IS-ANR In-service - abnormal; failure exists but entity is still capable of performing
some of its provisioned functions (that is partial failure)
OOS-AU Out-of-service - autonomous; failure detected
OOS-MA Out-of-service - maintenance; no failure detected (OOS for maintenance

for provisioning memory administration)
OOS-AUMA Out-of-service - autonomous - maintenance; failure detected
OOS-MAANR Out-of-service - maintenance - abnormal; partial failure detected
The table that follows provides information on equipment secondary states.
Table 2-27
Equipment secondary states
Active Equipment has connections established to at least one of the facilities it

supports and the connected facilities are in-service
Fault detected Equipment failure detected
Idle No connections established to facilities supported on this equipment, all

connected facilities are out-of-service, or in-service connected facilities are
not on the active traffic path in a protected connection
Mismatched eqp. attribute Mismatched or unknown equipment detected in a provisioned slot
Supporting entity outage Supporting equipment has a failure (applicable to pluggables when
associated circuit pack is missing or has failed or is mismatched)
Unequipped Equipment is missing
Unknown Equipment cannot be identified

The table that follows provides information on facility secondary states.
Table 2-28
Facility secondary states
<null> Active, working state for UPSR/SNCP facility.
Disconnected Facility has no connections established.
Disabled Applies to 20G L2SS, L2SS, PDH gateway, or RPR circuit packs (ETH, WAN or
LAG facilities) and eMOTR circuit packs (ETTP facility). The 20G L2SS, L2SS and
PDH gateway facility’s secondary state is set to Disabled when it has no
associated tunnel segment endpoint or virtual circuit endpoint created. The
eMOTR ETTP facility secondary state is set to Disabled when there is no SAOS
provisioning at the port.
Fault detected Facility failure detected
Supporting entity Supporting equipment (pluggable or circuit pack) or facility:

outage • has a failure, or
• is missing, or
• is mismatched, or
• has an associated connection which is failed.
The 20G L2SS, L2SS, PDH gateway, or RPR LAG facility's secondary state is also
set to Supporting entity outage when one or more of the LAG's member ports are
out of service.
Loopback active Loopback (facility, terminal, or EFM remote) active on facility
Supported entity Applies to 20G L2SS, L2SS LAG facilities when the LAG facilities have no
absent members.
UAS Applies to RPR backplane WAN facility’s secondary state when the WAN facility is
not associated to an RPR ring.
MT Maintenance State is enabled. When in Maintenance State, a facility continues to

carry traffic if it can, but does not raise alarms, SNMP traps or Performance
Monitoring Threshold Crossing Alerts (PM TCAs).
Applies to ETH facilities on L2 MOTR and PTP, OTUTTP, ODUTTP, ETTP, and
WAN facilities on eMOTR.
AINS Auto in-service is enabled.

Applies to ETH facilities on L2 MOTR and PTP, OTUTTP, ODUTTP, ETTP, and
WAN facilities on eMOTR.
Note: The secondary state can be a combination of all applicable states.


The table that follows provides information on ETH, ETH100, and ETH10G
facility parameters.
Table 2-29
L2SS ETH (for 20G L2SS, L2SS and PDH gateway circuit packs) and ETH100 for 20G L2SS
states. Read-only.
• The facility’s secondary state is set to Disabled when it
has no associated tunnel segment endpoint or virtual
circuit endpoint created.
• The facility’s secondary state is set to Supporting entity
outage when the supporting SFP or the equipment is
missing/mismatched/failed.
• The facility’s secondary state is set to Fault detected
when a facility failure detected.
• The facility’s secondary state is set to Loopback active
when an EFM remote loopback is active on the facility.
Link aggregation A LAG facility (if Displays if the facility belongs to any link aggregation
group applicable) group (LAG). LAG represents a combination of LANs on
a circuit pack. Therefore, the combined LANs on the
circuit pack can be collectively treated as a single high
capacity bandwidth link.
• Disable partner. If Auto negotiation is enabled, it is automatically
triggered when any of the following occur:
• the facility is put in-service.
• after a recovery from an Ethernet link failure (loss of
signal, loss of 8B18B synchronization).
• the link partner re-initiates auto-negotiation.
Note 1: On ETH100 facility, auto-negotiation is read-only
and is always disabled.
Note 2: EFM only works properly when the
auto-negotiation is disabled.

Table 2-29


On ETH100 facility, auto-negotiation status is always
Disabled.
Interface type • UNI Identifies the type of interface.

• NNI Not-editable (to change the interface type, the user must
delete the ETH/ETH100 facility and re-create the
ETH/ETH100 facility with the new interface type)
Maximum • 9216 for ETH on L2SS Displays the Maximum Transfer Unit (MTU) and is
Ethernet frame and PDH gateway (see controlled by setting the MTU parameter for a virtual
size Note) circuit segment (VCS). Read-only.
• 1522, 1594, Note: The actual limit for Maximum Ethernet frame size
1600 (default for is set by the VCS Maximum Transfer Unit (MTU) which
ETH100), 9100, 9216 can be set to either 1600 or 9100. Refer to Part 2 of
(default for ETH) on Configuration - Bandwidth and Data Services,
20GL2SS 323-1851-320 for more information on MTU and VCS.
Pause • Disable Explicitly controls the flow control towards the local
transmission • Enable device.
Pause • Disable (default) Controls the pause frame transmission. Not applicable if
transmission • Enable auto-negotiation is disabled.
override Setting pause transmission override to enable causes the
pause frame transmission to be determined by the pause
transmission attribute irrespective of the flow control
attribute. This allows pause frame transmission control
even if the link partner does not support flow control.

Advertised link • 1000 for ETH Indicates the advertised (current) Ethernet speed in
speed • 100 for ETH100 Mbit/s. Read-only.

Table 2-29
Advertised flow • Asymmetric if Port Indicates the advertised Ethernet flow control
control conditioning is Enabled capabilities. None indicates that the advertised flow
• None if Port conditioning control is not supported, Asymmetric to advertise
is Disabled asymmetric flow control toward the link partner. Not
applicable if auto-negotiation is disabled. Read-only.
Link partner • 1000 for ETH Indicates the advertised (current) Ethernet speed of the
advertised • 100 for ETH100 link partner in Mbit/s. Read-only.
speed
• Unknown
Link partner • Unknown Indicates the advertised (current) flow control capability
control
• None
• Symmetric
• Both
Negotiated • 1000 for ETH Displays the negotiated speed of the port in Mbit/s when
speed • 100 for ETH100 auto-negotiation is enabled. Read-only.
• Unknown



SNMP index 0 to 2^32-1 Contains the index value of the equivalent MIB object
instance in the SNMP interfaces MIB. Only inventory
entities that have a valid SNMP index will report the
SNMP index attribute. Read-only.
about SNMP index.

Table 2-29
Control frame See Table 2-32 on page Associates a control frame profile index to a specified
profile 2-227 LAN port. The predefined profiles identify the control
protocol.
Customer Ethernet p-bits Indicates from where the ETH facility must look for the
priority mode priority. The customer priority mode is not supported
when the interface type is NNI. Read-only.
• 88A8
Policing • Enable Provides rate adaptation between the full speed Ethernet
• Disable access ports and the user subscribed bandwidth. If the
interface type is UNI, the default is Enable. If the interface
type is NNI, the default is Disable.
Bandwidth 0 to 100 Shows the amount of utilized bandwidth on a given ETH

utilized (%) facility. Read-only.
Applicable to L2SS and PDH gateway ETH only.
Bandwidth 1 to port speed Shows the amount of available bandwidth on a given

available (kbps) ETH facility. This attribute is mainly used to find out
whether the addition of a given VCE to a given port is
possible. Read-only.
Bandwidth 0 to 100 (default is 80) Sets the threshold setting (as a percentage of total
utilization available port bandwidth) above which a standing AO will
threshold (%) be raised against the applicable port. The percentage
bandwidth utilization attribute allows the network
operator to determine the percentage utilization of a
given port.
When the value is set to 0, the standing AO warning for
bandwidth threshold exceeded will not be raised.

Table 2-29
Port Bandwidth • 0:Not Policed Displays the port bandwidth. Displays 0 if not policed.
• 1:Standard Default Only displayed for 20GL2SS ETH/ETH100.
• 3:Silver Default
• 4:Gold Default
• 6:Premium Default
• 7:Network Default
• 8:Discard All
Queue Group 1 1, 2, 67, 68, 69, 70 A queue group specifies which scheduler profile, drop
(predefined) profiles and multipliers to be used for creating a port.
3-66 (user-defined) Typically one queue group will be used for P2P traffic, a
second queue group will be used for A2A traffic.
Queue Group 2 1, 2, 67, 68, 69, 70 Queue group 2. Applicable to 20G L2SS ETH/ETH100
(predefined) only.
3-66 (user-defined)
Receive class of 1, 2, 26, 27, 28, 29, 30, 31 A receive class of service profile indicates how to map the
service profile (predefined) priority bits and DE bits of the packets received to the
3-25 (user-defined) internal per hop behavior (IPHB) or discard (the discard
option is only available to L2SS and PDH gateway circuit
packs). It maps the reception Ethernet priority and CFI to
a class of service.
Transmit Class 1, 2, 26, 27, 28, 29, 30 A transmit class of service profile indicates how to map
of service profile (predefined) the internal per hop behavior (IPHB) to the priority bits
3-25 (user-defined) and DE bits of the packets transmitted or discard (the
discard option is only available to L2SS and PDH
gateway circuit packs). It maps a transmission class of
service to an Ethernet priority and CFI.

service
• Premium-Green
(-Yellow)
• Standard-Green
(-Yellow)

Table 2-29
Port conditioning • Disable (default) Sets whether port conditioning is disabled or enabled. If
• Enable port conditioning is enabled, L2 or EVPL provisioning can
be used. If port conditioning is disabled, only L2
provisioning can be used.
Applicable to 20G L2SS only.
Conditioning • Enable (default) Sets the conditioning type. Only applicable if port
type • Disable conditioning is enabled.
Conditioning • Disable (default) Sets the state of the conditioning heartbeat. Only
heartbeat • Enable applicable if port conditioning is enabled.
• TXonly • Disable (default) – Do not send ETH-CCM messages

and never condition due to a heartbeat timeout.
• Enable – Send ETH-CCM messages but do not
condition due to a heartbeat timeout until the remote
has been detected. Detection is considered to be the
reception of one ETH-CCM, ETH-AIS, or ETH-LCK
message.
• TXonly – Send ETH-OAM frames (ETH-CCM, ETH-AIS,
ETH-LCK) but do not raise alarms or condition the client
based on any receive condition including line port failed.
Conditioning HB • 1 second Sets the conditioning heartbeat interval. Only applicable

interval • 100 msecond if port conditioning is enabled.
Conditioning MD 0 to 7 (default 0) Sets the conditioning MD level. Only applicable if port

level conditioning is enabled. MD should be set to a value
higher than the MDs used for Ethernet OAM (if used).
Conditioning • Explicit Sets the conditioning network signal. Only applicable if

network signal • CFM port conditioning is enabled.
• Type Length and Value If Conditioning heartbeat is Disabled, this parameter

(TLV) must be Explicit.
CFM is for VLLI interworking with eMOTR. 20G L2SS and
L2 MOTR circuit packs do not support CFM in E-LAN
topologies. Therefore, when interworking with eMOTR
circuit packs in E-LAN topologies, do not define remote
MEPs on 20G L2SS or L2 MOTR circuit packs.
If service is A2A and conditioning heartbeat is not
Disabled, this parameter must be TLV or CFM.

Table 2-29
Basic rate • 10 to 100 for ETH100 Sets the rate of the port. Only applicable if port
(default 100) conditioning is enabled.
• 10 to 1000 for ETH
(default 1000)

SP2 is equipped.
RPR ETH
Unit ETH-shelf-slot-port Displays the facility AID. Read-only.
Secondary state See “Facility secondary Indicates the operational state of the ETH facility. The
states. Read-only.
• The ETH facility’s secondary state is set to Disabled
when it has no associated tunnel segment endpoint or
virtual circuit endpoint created.
• The ETH facility’s secondary state is set to Supporting
entity outage when the supporting SFP or the RPR
equipment is missing/mismatched/failed.
• The ETH facility’s secondary state is set to Fault
detected when a facility failure detected.
Link aggregation A LAG facility (if Displays if the ETH facility belongs to any link
group applicable) aggregation group (LAG). LAG represents a combination
of LANs on a RPR circuit pack. Therefore, the combined
LANs on the RPR circuit pack can be collectively treated
as a single high capacity bandwidth link.
• Disable partner. If Auto-negotiation is enabled, it is automatically
• the ETH facility is put in-service.

Table 2-29
Auto-negotiation • Unknown (default) Identifies the auto-negotiation status of the Ethernet


Maximum For UNI: Sets the Maximum transfer unit (MTU).

Ethernet frame • 1522 (default) This parameter can be edited only when the ETH facility
size is out-of-service.
• 9100
For NNI: Note: The VCS Maximum Transfer Unit (MTU) size does
not apply to the RPR circuit packs.
• 1600 (default)
• 9216
Pause Disable Explicitly controls the flow control towards the local
transmission device. Read-only.

Advertised link 1000 Indicates the advertised (current) Ethernet speed in

speed Mbit/s. Read-only.
Advertised flow • Asymmetric Sets the advertised Ethernet flow control capabilities.
control • None (default) None indicates that the advertised flow control is not
• Symmetric supported, Asymmetric to advertise asymmetric flow
control toward the link partner is supported, Symmetric to
advertise symmetric flow control or asymmetric flow
control toward the local device is supported. Not
applicable if auto-negotiation is disabled.
is out-of-service.
duplex operation at the far end of an Ethernet link. The unknown value is
displayed when auto-negotiation is disabled.
Read-only.

Table 2-29
advertised • Unknown link partner in Mbit/s. The unknown value is displayed
speed when auto-negotiation is disabled.
Read-only.
advertised flow • Asymmetric of the link partner. The unknown value is displayed when
control auto-negotiation is disabled. Read-only.
• None
• Symmetric
• Both
duplex operation • Unknown auto-negotiation is enabled. The unknown value is
displayed when auto-negotiation is disabled. Read-only.
speed • Unknown auto-negotiation is enabled. The unknown value is
displayed when auto-negotiation is disabled. Read-only.

pause • Unknown transmissions when auto-negotiation is enabled. The
transmission unknown value is displayed when auto-negotiation is

pause reception • Unknown receptions when auto-negotiation is enabled. The
unknown value is displayed when auto-negotiation is

about SNMP index.

• NNI Not-editable (to change the interface type, the user must
delete the RPR ETH facility and re-create the RPR ETH
facility with the new interface type)

Table 2-29
protocol.
• 88A8 This parameter can be edited only when the ETH facility
is out-of-service.
Customer Ethernet p-bits identifies from where the ETH facility must look for the
priority mode priority. The customer priority mode is not supported
when the interface type is NNI.
Read-only.
Policing • Enable (default if the Sets rate adaptation between the full speed Ethernet
interface type is UNI) access ports and the user subscribed bandwidth.
• Disable If the interface type is NNI, the only possible value is
Disable. If the interface type is UNI, the possible values
are Enable or Disable.
3-25 (user-defined) internal per hop behavior (IPHB) or discard. It maps the
reception Ethernet priority and CFI to a class of service.
This parameter is not applicable to RPR ETH-UNI.
Transmit class of 1, 2, 26, 27, 28, 29, 30 A transmit class of service profile indicates how to map
service profile (predefined) the internal per hop behavior (IPHB) to the priority bits
3-25 (user-defined) and DE bits of the packets transmitted or discard. It maps
a transmission class of service to an Ethernet priority and
CFI.
This parameter is not applicable to RPR ETH, UNI or
NNI.

Table 2-29
Untagged • Critical-Green (-Yellow)Class of service in the receive direction. The color in the
receive class of • Network-Green (-Yellow) class of service is ignored by the RPR.
service
• Premium-Green
(-Yellow)
• Standard-Green
(-Yellow)

SP2 is equipped.
L2 MOTR ETH and ETH100
Secondary state • See “Facility secondary Indicates the operational state of the facility. The
states.
For ETH facilities, the Test state, Auto In-Service state,
and Maintenance state are editable.
Link LAG AID Displays the link aggregation group this facility belongs
Aggregation to. Read-only.
Group
• Disable partner. If Auto-negotiation is enabled, it is automatically
• the ETH facility is put in-service.
Note: On ETH100 facility, auto-negotiation is read-only
and is always disabled.

Table 2-29

status • In progress facility. Read-only.

• Disabled successfully.
On ETH100 facility, auto-negotiation status is always
Disabled.

• NNI To change the interface type, you must delete the ETH
facility and re-create the ETH facility with the new
interface type.
Maximum • 1522 Sets the Maximum Transfer Unit (MTU). Received

Ethernet frame • 1600 (default) frames which are larger than the MTU are discarded and
size counted as frtoolongs.
• 9100
• 9216
• 9600
Pause • enable Controls pause transmission when auto-negotiation is

transmission • disable disabled. Not applicable when auto-negotiation is
enabled.
Default is disable when port conditioning is disabled,
enable when port conditioning is enable. Must be enable
if the basic rate is less than the advertised link speed.
Pause reception disable Displays the pause reception status which is used to
Advertised full Indicates the type of advertised duplex operation by

Advertised link • 1000 for ETH Indicates the advertised (current) Ethernet speed in
speed • 10 or 100 (default) for Mbit/s. Editable for ETH100 on the 10/100BaseT SFP
ETH100 only.
Advertised flow • Asymmetric Sets the advertised Ethernet flow control capabilities.
control • None None indicates that the advertised flow control is not
Default is None when port conditioning is disabled,
Asymmetric when port conditioning is enable.

Table 2-29
Link partner • 1000 for ETH Indicates the advertised (current) Ethernet speed of the
advertised • 100 for ETH100 link partner in Mbit/s. Read-only.
speed
• Unknown
control
• None
• Symmetric
• Both
Negotiated • 1000 for ETH Displays the negotiated speed of the port in Mbit/s when
speed • 100 for ETH100 auto-negotiation is enabled. Read-only.
• Unknown



about SNMP index.

Table 2-29
Conditioning • CFM Sets the conditioning network signal. Only applicable if

network signal • Explicit port conditioning is enabled.
• Type Length and Value CFM is for VLLI interworking with eMOTR. 20G L2SS and
(TLV) L2 MOTR circuit packs do not support CFM in E-LAN
If Conditioning heartbeat is Disabled, this parameter
must be Explicit.
Disabled, this parameter must be TLV or CFM.
heartbeat • Enable applicable if port conditioning is enabled and conditioning
network signal is not CFM.
• TXonly
• Disable (default) – Do not send ETH-CCM messages
message.

interval • 100 msecond if port conditioning is enabled and conditioning network
signal is not CFM.

level conditioning is enabled and conditioning network signal is
not CFM.
MD should be set to a value higher than the MDs used for
Ethernet OAM (if used).

Table 2-29
Control frame • 1: Drop all (for ETH only) Associates a control frame profile index to a specified
profile • 2: EFM + Drop Other (for LAN port. The predefined profiles identify the control
EVPL and L2 UNI) frame processing behavior for each control frame
protocol.
• 3: LAG + Drop Other (for
all) Note: Refer to 6500 Packet-Optical Platform Data
• 4: P2P Tunnel
(for EVPL and L2 UNI)
• 5: EFM + P2P Tunnel (for
EVPL and L2 UNI)
• 6: LAG + P2P Tunnel (for
EVPL and L2 UNI)
• 7: LAG, SONMP+Drop
(for all)
(for all)
• 10: SONMP + A2A
Tunnel (for EVPL and L2
UNI)
• 11: LAG, LLDP, LACP +
Drop (for all)
• 12: LLDP + Drop Other
(for all)
• 13: LLDP + A2A Tunnel
(for all)
Hex) • 9100 VLAN) used to encapsulate customer frames. For UNI
ports, the value comes from the L2MOTR equipment
• 88A8 level Ether Type setting.
Enable only when port conditioning is enable.
Inter-Packet • 11 Sets the Inter-Packet Gap, a minimum idle period

Gap • 12 (default) between transmission of Ethernet frames.
Port Bandwidth 0 to 8 (predefined) Sets the port bandwidth profile to limit the port capacity.
9-200 (user-defined) Default is 0. 0 only when port conditioning is enable.

Table 2-29
3-66 (user-defined) 70 only when port conditioning is enable.
3-25 (user-defined) internal per hop behavior (IPHB). It maps the reception
Default 31 when port conditioning is enable. Circuit pack
default when port conditioning is disabled.
3-25 (user-defined) and DE bits of the packets transmitted. It maps a
CFI.
L2MOTR only supports profile 30.

receive class of • Network-Green (-Yellow) Default Premium-Green when port conditioning is
service enable. Default 0 when port conditioning is disabled.
• Premium-Green
(-Yellow)
• Standard-Green
(-Yellow)
override to override (disable) the negotiated receive pause if
auto-negotiation is enabled. Not applicable if
auto-negotiation is disabled. Read-only.

Table 2-29
Basic rate • 10 to 1000 in 10 Mb/s Sets the maximum rate of EVPL service in Mb/s. Default
increments for ETH is 1000 for ETH, 100 for ETH100. Only editable when port
• 10 to 100 in 10 Mb/s conditioning is enable.
increments for ETH100

SP is equipped.
20G L2SS ETH10G (for 20G L2SS circuit packs)
Unit ETH10G-shelf-slot-port Displays the facility AID. Read-only.
Secondary state • See “Facility secondary Indicates the operational state of the ETH10G facility.
states” on page 2-179 The secondary state can be a combination of one or more
states. Read-only.
• The facility’s secondary state is set to Disabled when it
has no associated tunnel segment endpoint or virtual
circuit endpoint created.
• The facility’s secondary state is set to Supporting entity
outage when the supporting SFP or the 20G L2SS
• The facility’s secondary state is set to Fault detected
when a facility failure detected.
• The facility’s secondary state is set to Loopback active
when an EFM remote loopback is active on the facility.
Link aggregation A LAG facility (if Displays if the ETH10G facility belongs to any link
group applicable) aggregation group (LAG).
Auto negotiation Disable Indicates auto-negotiation with the local Ethernet link
partner. Read-only.

Table 2-29
Auto-negotiation Disabled Identifies the auto-negotiation status of the Ethernet

status facility. Read-only.
Interface type • UNI Identifies the type of interface. Not-editable (to change
• NNI the interface type, the user must delete the facility and
re-create the facility with the new interface type)
Maximum • 1522 Displays the Maximum Transfer Unit (MTU) and is

Ethernet frame • 1594 controlled by setting the MTU parameter for a virtual
size circuit segment (VCS).
• 1600
Note: The actual limit for 20G L2SS ETH10G Maximum
• 9100
Ethernet frame size is set by the VCS Maximum Transfer
• 9216 (Default, see Note) Unit (MTU). Refer to Part 2 of Configuration - Bandwidth
and Data Services, 323-1851-320 for more information
on MTU and VCS.
Pause • Disable Explicitly controls the flow control towards the local
transmission • Enable device. Read-only.


Advertised flow • Asymmetric if Port Indicates the advertised Ethernet flow control
control conditioning is Enabled capabilities. None indicates that the advertised flow
• None if Port conditioning control is not supported, Asymmetric to advertise
is Disabled asymmetric flow control toward the link partner. Not
applicable if auto-negotiation is disabled. Read-only.

Table 2-29
advertised • Unknown link partner in Mbit/s. Read-only.
speed
control
• None
• Symmetric
• Both
speed • Unknown auto-negotiation is enabled. Read-only.


protocol.
Customer Ethernet p-bits Indicates from where the ETH10G facility must look for
priority mode the priority. The customer priority mode is not supported
when the interface type is NNI.
Read-only.
• 88A8
• Disable access ports and the user subscribed bandwidth. Default
is Enable for UNI and Disable for NNI.

Table 2-29
Port Bandwidth 0:Not Policed Displays the port bandwidth. Displays 0 if not policed.
3-66 (user-defined) Typically one queue group will be used for P2P traffic, a
second queue group will be used for A2A traffic.
Queue Group 2 1, 2, 67, 68, 69, 70 Queue group 2.

(predefined)
3-66 (user-defined)
CFI.

service
• Premium-Green
(-Yellow)
• Standard-Green
(-Yellow)

Table 2-29
• TXonly • Disable (default) – Do not send ETH-CCM messages

message.

interval • 100 msecond if port conditioning is enabled.

Conditioning • Explicit Sets the conditioning network signal. Only applicable if

network signal • Implicit port conditioning is enabled.
must be Explicit.
Disabled, this parameter must be Implicit.
Basic rate 10 to 10000 (default Sets the rate of the port. Only applicable if port
10000) conditioning is enabled.

SP2 is equipped.
L2 MOTR ETH10G
Unit ETH10G-shelf-slot-port Displays the facility AID. Read-only.

For the ETH10G facility on the L2MOTR CP equipment,
the available ports are 91 and 92.

Table 2-29
Secondary state • See “Facility secondary Indicates the operational state of the facility. The
states. Read-only.
Link LAG AID Displays the link aggregation group this facility belongs
Aggregation to. Read-only.
Group
Auto negotiation Disable Controls auto-negotiation with the local Ethernet link
partner.
Tx Wavelength 1528.38 (0) to 1568.77 at Sets the required line transmit wavelength.
(nm) 50 GHz spacing Tx Wavelength cannot be edited unless the facility is
(default 0) OOS, except when changing from 0 to a valid
wavelength, which can be IS. Editing to 0 is supported.
Provisionable on tunable pluggables only.
The number in brackets is the channel ID.
Applicable to the ETH10G facility on the PXFP variants of
NTK583AA/AB and NTK587Ex to NTK587Hx only.
Maximum • 1522 Sets the Maximum Transfer Unit (MTU). Received

Ethernet frame • 1600 (default) frames which are larger than the MTU are discarded and
size counted as FRTOOLONGS.
• 9100
• 9216
• 9600
Packet mapping • None Displays the LAN to OTU2 mapping format. Packet
• 10.7G - GFP/OPU2 mapping depends on the OTM2 rate.
(Standard MAC
transparent)
• 11.05G - OPU1e (PCS
transparent)
• 11.09G - OPU2e (PCS
transparent)



Table 2-29
Advertised flow None Sets the advertised Ethernet flow control capabilities.
control None indicates that the advertised flow control is not
Pause • Enable Controls pause transmission when auto-negotiation is

transmission • Disable disabled. Not applicable when auto-negotiation is
enabled.
Default is Disable when port conditioning is disabled,
Enable when port conditioning is enable. Must be Enable
if the basic rate is less than the advertised link speed.
override to override (disable) the negotiated receive pause if
auto-negotiation is enabled. Not applicable if
auto-negotiation is disabled. Read-only.


• NNI To change the interface type, you must delete the facility
and re-create the facility with the new interface type.
Enable only when port conditioning is enable.

Table 2-29
Hex) • 9100 VLAN) used to encapsulate customer frames. For UNI
ports, the value comes from the L2MOTR equipment
• 88A8 level Ether Type setting.
Control frame • 1: Drop all (for L2 NNI) Associates a control frame profile index to a specified
profile • 3: LAG + Drop Other (for LAN port. The predefined profiles identify the control
ETH10G on L2MOTR frame processing behavior for each control frame
CP equipment, UNI or protocol.
NNI) Note: Refer to 6500 Packet-Optical Platform Data
• 4: P2P Tunnel Application Guide, NTRN15BA for more information
(for EVPL and L2 UNI) about control frame profile.
• 6: LAG + P2P Tunnel (for
ETH10G on L2MOTR
CP equipment, UNI)
• 7: LAG, SONMP+Drop
(for L2 NNI and UNI)
(for L2 NNI and UNI)
• 10: SONMP + A2A
Tunnel (for L2 UNI)
• 11: LAG, LLDP, LACP +
Drop (for all)
• 12: LLDP + Drop Other
(for all)
• 13: LLDP + A2A Tunnel
(for all)
about SNMP index.
Default 31 when port conditioning is enable. Circuit pack
default when port conditioning is disabled.

Table 2-29
SSMTRANSMIT • EEC1 When enabled, the ETH10G facility will transmit SSM
• EEC2 sync quality level using Ethernet Sync Messaging
Channel (ESMC). EEC1 is SDH/SDH-J format and EEC2
• Disable (default) is SONET format.
When disabled, no ESMC packets will be sent. Only
displayed for ports 1 and 2, not 91 and 92
CFI.
L2MOTR only supports profile 30.

receive class of • Network-Green (-Yellow) Default Premium-Green when port conditioning is
service enable. Default 0 when port conditioning is disabled.
• Premium-Green
(-Yellow)
• Standard-Green
(-Yellow)
Inter-Packet • 11 Sets the Inter-Packet Gap, a minimum idle period

Gap • 12 (default) between transmission of Ethernet frames.
3-66 (user-defined) 70 only when port conditioning is enable.
Port Bandwidth 0 to 8 (predefined) Sets the port bandwidth profile to limit the port capacity.
9-200 (user-defined) Default is 0. 0 only when port conditioning is enable.

Table 2-29
Conditioning • CFM Sets the conditioning network signal. Only applicable if

network signal • Explicit port conditioning is enabled.
• Implicit CFM is for VLLI interworking with eMOTR. 20G L2SS and
L2 MOTR circuit packs do not support CFM in E-LAN
must be Explicit.
Disabled, this parameter must be Implicit.
heartbeat • Enable applicable if port conditioning is enabled and conditioning
network signal is not CFM.
• TXonly
• Disable (default) – Do not send ETH-CCM messages
message.

interval • 100 msecond if port conditioning is enabled and conditioning network
signal is not CFM.
Conditioning MD • 0 to 7 (default 0) Sets the conditioning MD level. Only applicable if port

level conditioning is enabled and conditioning network signal is
not CFM.
MD should be set to a value higher than the MDs used for
Ethernet OAM (if used).
Basic rate 10 to 10000 in 10 Mb/s Sets the maximum rate of EVPL service in Mb/s. Default
increments is 10000. Only editable when port conditioning is enable.

Table 2-29
TMGREF •Y Indicates whether the facility is chosen as a line timing

•N reference or not.

SP is equipped.

The table that follows provides information on WAN facility parameters.
Table 2-30
L2SS WAN (for 20G L2SS, L2SS and PDH gateway circuit packs)
Unit WAN-shelf-slot-port Displays the facility AID. Read-only.

Available ports:
• 101 to 164 for L2SS
101 to 228 for PDH gateway and 20G L2SS
• All
Primary state See “Equipment and facility Sets the primary state of the facility. Default reflects
2-178 Note: IS and OOS are selectable.

Table 2-30
Secondary state See “Facility secondary Indicates the operational state of the WAN facility.
states” on page 2-179 The secondary state can be a combination of one
or more states. Read-only.
• The WAN facility’s secondary state is set to
Disconnected when it has no associated
cross-connections.
Disabled when it has no associated tunnel
segment endpoint or virtual circuit endpoint
created.
Supporting entity outage when an associated
cross-connection is failed (SONET/SDH/SDH-J
path alarm or Virtual Concatenation (VCAT)
alarm) and VCAT=DISABLE, or
VCAT=ENABLE/LCAS=DISABLE.
Supporting entity outage when the
20G L2SS/L2SS equipment is
missing/mismatched/failed.
• The backplane WAN facility’s secondary state is
set to Fault detected when a facility failure
detected.
PDH type • DS1 Sets the PDH type of WAN facility.

• DS3 Note: This parameter is only applicable to L2SS
• E1 DS1/E1/DS3/E3 4xGE circuit pack (also known as
PDH gateway circuit pack).
• E3
• Non-PDH
Basic Rate • None (default) Displays the basic rate of the WAN facility and is
• None, STS1/VC3, derived from the cross-connections assigned to
STS3c/VC4, that WAN facility. Read-only.
STS12c/VC4-4c, Note 1: 20G L2SS does not support VT
STS24c/VC4-8c, cross-connections.
STS48c/VC4-16c (when Note 2: The STS192c/VC4-64c rate is only
VCAT is disabled), applicable to 20G L2SS.
STS192c/VC4-64c
• None, VT1.5/VC11,
VT2/VC12, STS1/VC3,
STS3c/VC4 (when VCAT is
enabled)

Table 2-30

concatenation • Disable (default) the port. This parameter can only be edited if the
WAN facility is out-of-service and no
Note: If you edit the VCAT to enabled, it does not
automatically edit the LCAS to enabled. You must
manually set the LCAS mode to enabled if the
LCAS is in disabled mode.
Link capacity • Enable Enables/disables the link capacity adjustment

adjustment scheme • Disable (default) scheme (LCAS). LCAS is a signaling protocol for
virtual concatenation (VCAT) that allows hitless
virtual concatenation group (VCG) member
addition or deletion.
Note: If LCAS is enabled, you cannot edit the
VCAT to disabled. You must first disable the LCAS
before you can disable the VCAT.

• NNI Not-editable (to change the interface type, the user
must delete the WAN facility and re-create the
WAN facility with the new interface type)
Packet mapping GFP-F Displays the WAN to SONET/SDH/SDH-J mapping

format. Read-only.

disabled units (basic rate units) in the SONET/SDH/SDH-J
enabled and rate is cross-connections assigned to the WAN facility.
VT1.5/VC11 or VT2/VC12 Read-only.

enabled and rate is
STS1/VC3
enabled and rate is
STS3c/VC4

Table 2-30
disabled (basic rate units) carrying traffic in the
• 0 to 64 when VCAT is SONET/SDH/SDH-J transmit direction and is
enabled and rate is derived from the cross-connections assigned to the
VT1.5/VC11 or VT2/VC12 WAN facility and SONET/SDH/SDH-J failures.
Read-only.
enabled and rate is
STS1/VC3
enabled and rate is
STS3c/VC4
• Unknown
enabled and rate is
VT1.5/VC11 or VT2/VC12
enabled and rate is
STS1/VC3
enabled and rate is
STS3c/VC4
• Unknown

This parameter can only be edited if the WAN
facility is out-of-service



Table 2-30
Round trip delay Unknown Displays the estimated time in microseconds for
(microseconds) one packet to travel from one device to another and
SNMP index 0 to 2^32-1 Contains the index value of the equivalent MIB
object instance in the SNMP interfaces MIB. Only
inventory entities that have a valid SNMP index will
report the SNMP index attribute. Read-only.
Application Guide, NTRN15BA for more
information about SNMP index.
Control frame profile See Table 2-32 on page Associates a control frame profile index to a
2-227 specified WAN. The predefined profiles identify the
control frame processing behavior for each control
frame protocol.
information about control frame profile. This
parameter can only be edited if the WAN facility is
out-of-service.
Customer priority Ethernet p-bits (default) Indicates from where the WAN facility must look for
mode the priority. The customer priority mode is not
supported when the interface type is UNI.
Read-only.
WAN capacity HICAP Indicates the capacity of the WAN facility.

Read-only.
Applicable to 20G L2SS WAN only.
Ether type (in Hex) • 8100 (default) Sets the encapsulation scheme (for example
• 9100 stacked VLAN) used to encapsulate customer
frames.
• 88A8
Policing Enable Provides rate adaptation between the full speed

Ethernet access ports and the user subscribed
bandwidth. The only possible value for UNI and
NNI interface types is Enable.
Read-only.

Table 2-30
Bandwidth utilized 0 to 100 Shows the amount of utilized bandwidth on a given

(%) WAN facility. Read-only.
Applicable to L2SS and PDH gateway WAN only.
Bandwidth available 1 to port speed Shows the amount of available bandwidth on a

(kbps) given WAN facility. This attribute is mainly used to
find out whether the addition of a given VCE to a
given port is possible. Read-only.
Bandwidth utilization 0 to 100 (default is 80) Sets the threshold setting (as a percentage of total
threshold (%) available port bandwidth) above which a standing
AO will be raised against the applicable port. The
percentage bandwidth utilization attribute allows
the network operator to determine the percentage
utilization of a given port.
When the value is set to 0, the standing AO
warning for bandwidth threshold exceeded will not
be raised.


PDHVLI • Disable (default) Shows the PDH VCAT LCAS Interworking

• Enable (PDHVLI) byte control. PDHVLI parameter controls
the VCAT overhead byte transmission.
• Disable – the VLI byte is used as payload
• Enable – the VLI byte is set to all zeros as per ITU
G.8040 (09/2005)
Can be enabled only for PDH WANs (DS1, DS3,
E1, or E3) when VCAT is disabled. This parameter
can only be edited if the WAN facility is
out-of-service.

Table 2-30
Queue Group 1 1, 2, 67, 68, 69, 70 A queue group specifies which scheduler profile,
(predefined) drop profiles and multipliers to be used for creating
3-66 (user-defined) a port. Typically one queue group will be used for
P2P traffic, a second queue group will be used for
A2A traffic.
Queue Group 2 1, 2, 67, 68, 69, 70 Queue group 2. Applicable to 20G L2SS WAN
(predefined) only.
3-66 (user-defined)
Receive class of 1, 2, 26, 27, 28, 29, 30, 31 A receive class of service profile indicates how to
service profile (predefined) map the priority bits and DE bits of the packets
3-25 (user-defined) received to the internal per hop behavior (IPHB) or
discard (the discard option is only available to
L2SS and PDH gateway circuit packs). It maps the
reception Ethernet priority and CFI to a class of
service.
Transmit Class of 1, 2, 26, 27, 28, 29, 30 A transmit class of service profile indicates how to
service profile (predefined) map the internal per hop behavior (IPHB) to the
3-25 (user-defined) priority bits and DE bits of the packets transmitted
or discard (the discard option is only available to
L2SS and PDH gateway circuit packs). It maps a
transmission class of service to an Ethernet priority
and CFI.
Untagged receive • Critical-Green (-Yellow) Class of service in the receive direction.

class of service • Network-Green (-Yellow)
• Premium-Green (-Yellow)
• Standard-Green (-Yellow)
MAC Option • None (default) Sets the option for MAC address provisioning.
• Auto
• Manual
MAC Address ** ** ** ** ** ** Displays the MAC address of the port. Editable only
when the MAC option is set to Manual.

Table 2-30
RPR WAN

Available ports:
• 101 to 104
• All
Primary State See “Equipment and facility Sets the primary state of the facility. Default reflects
2-178 Note: IS and OOS are selectable.
Secondary State See “Facility secondary Indicates the operational state of the WAN facility.
states” on page 2-179 The secondary state can be a combination of one
or more states. Read-only.
Disconnected when it has no associated
cross-connections.
Disabled when it has no associated tunnel
segment endpoint or virtual circuit endpoint
created.
Supporting entity outage when an associated
cross-connection is failed (SONET/SDH/SDH-J
path alarm or Virtual Concatenation (VCAT)
alarm) and VCAT=DISABLE, or
VCAT=ENABLE/LCAS=DISABLE.
Supporting entity outage when the RPR
set to Fault detected when a facility failure
detected.
set to UAS when the WAN facility is not
associated to an RPR ring.

Table 2-30
Basic Rate • None (default) Displays the basic rate of the WAN facility and is
• None, STS1/VC3, derived from the cross-connections assigned to
STS3c/VC4, that WAN facility. Read-only.
STS12c/VC4-4c, and
STS48c/VC4-16c (when
VCAT is disabled)
• None, STS1/VC3, and
STS3c/VC4 (when VCAT is
enabled)
Packet Mapping GFP-F Displays the WAN to SONET/SDH/SDH-J mapping

format. Read-only.

Concatenation • Disable (default) the port.
This parameter can only be edited if the WAN
facility is out-of-service and no cross-connects are
present on the WAN facility.
Link Capacity Disable Displays the status of the link capacity adjustment
Adjustment Scheme scheme. Read-only.
Provisioned Units • 0 or 1 when VCAT is Displays the number of provisioned bandwidth

disabled units (basic rate units) in the SONET/SDH/SDH-J
enabled and rate is cross-connections assigned to the WAN facility.
STS3c/VC4 Read-only.
enabled and rate is
STS1/VC3 (HO)
Frame Checksum 0 Displays whether the GFP frame checksum is

included in the frame.
The only possible value in this release is 0 which
indicates that the checksum is not included.
Read-only.
LAN Frame Disable Displays whether the LAN frame checksum is

Checksum included in the encapsulated frame. For GFP-F,
Payload Scrambling Enable Displays the status of the X^43+1 payload


Table 2-30
SNMP Index 0 to 2^32-1 Contains the index value of the equivalent MIB
object instance in the SNMP interfaces MIB. Only
inventory entities that have a valid SNMP index will
report the SNMP index attribute. Read-only.
information about SNMP index.
Interface Type NNI Identifies the type of interface. Only NNI is

supported in this release. Read-only.
Ether Type (in Hex) • 8100 (default) Sets the encapsulation scheme (for example
• 9100 stacked VLAN) used to encapsulate customer
frames. This parameter can be edited only when
• 88A8 the WAN facility is out-of-service and the WAN port
is not associated to an RPR ring.
Policing Disable Provides rate adaptation between the full speed

Ethernet access ports and the user subscribed
bandwidth. The only possible value in this release
is Disable. Read-only.
discard. It maps the reception Ethernet priority and
CFI to a class of service.
3-25 (user-defined) priority bits and DE bits of the packets transmitted
or discard. It maps a transmission class of service
to an Ethernet priority and CFI.
Untagged receive • Critical-Green (-Yellow) Class of service in the receive direction. The color
class of service • Network-Green (-Yellow) in the class of service is ignored by the RPR.

Table 2-30
L2MOTR WAN
Primary State See “Equipment and facility Displays the primary state of the facility. Value
primary states” on page reflects primary state of associated ETH10G
2-178 facility. Read-only.
Packet Mapping GFP-F Displays the WAN to OPU2 mapping format.

Read-only.
Frame Checksum •0 Sets whether the GFP-F frame checksum (4 Byte

• 32 (default) CRC-32) is appended to each GFP-F frame.
"32" adds the frame checksum while "0" does not.


eMOTR WAN
Unit WAN-shelf-slot-port-2P1 Displays the AID for the facility. Read-only.

WAN-shelf-slot-port-3P1-2P
n (n=1 to 4)
Primary State See “Equipment and facility Displays the primary state of the WAN facility,
primary states” on page which follows the primary state of its parent PTP
2-178 facility. Read-only.
more states. The Auto In-Service state and
Maintenance state follows the parent PTP facility.
Read-only.
Supporting • ODUTTP-shelf-slot-port- Displays the supporting termination point.

Termination Point 2P1 Read-only.
• ODUTTP-shelf-slot-port-3P
1-2Pn (n=1 to 4)

Table 2-30
Packet mapping GFP-F Displays the type of GFP mapping used.

Read-only.
Ethernet Preamble • Keep Sets whether the 8 byte Ethernet MAC preamble is
• Discard kept or discarded during GFP-F mapping. This
parameter is determined by the ETH10G packet
mapping. Discard for standard mappings.
Read-only.
FCS Errored • Keep (default) Sets whether the LAN FCS errored frames are kept
Frames • Discard or discarded at the client ingress.
When set to Discard, FCS errored frames (either
GFP or MAC FCS errors) are not discarded at the
client egress. The only location FCS errored
frames are discarded is at the ETH10G client Rx.
Additionally, the discarded frames are added to the
DFR-EPM count and the Ethernet in Frames
Discard: Total OM count, which do not normally
include FCS errored frames.
Round trip delay Disable Controls the support (sending of CMFs) of round
status trip delay calculation. Read-only.
Conditioning type None Indicates the type of conditioning to apply on client

failure. Read-only.
Frame checksum 0 Indicates that the GFP frame checksum is not

included in the frame. Read-only.
User Payload 00 to FF Displays the User Payload Identifier to be

Indicator transmitted in the client data frames, depending on
Transmitted (In mapping. Read-only.
HEX) (Note 2)
User Payload 00 to FF Displays the expected User Payload Identifier to be

Indicator Expected received in the client data frames, which follows the
(In HEX) User Payload Indicator Transmitted value.
Read-only.

Table 2-30
Transparent • G7041CMF Displays if ordered set transparency is supported.

Ordered Sets • G7041CDF Applicable to GFP-F mapping only. G7041CMF if
ETH10G mapping is 10.7G - GFP/OPU2 (Standard
MAC transparent). G7041CDF if ETH10G mapping
is 10.7G - GFP/OPU2+7 (Preamble/ Ordered Set/
MAC transparent). Read-only.
DIRECTION RX Indicates the direction of the WAN facility.

Read-only.
Note 1: Where applicable, the Mapping, Frame checksum, and LAN frame checksum parameters must
always be edited as a group, invalid combinations are rejected.
Note 2: This parameter has the following values as per G.7041:
• 10.7G - GFP/OPU2 (Standard MAC transparent) – 01, not provisionable
• 10.7G - GFP/OPU2+7 (Preamble/ Ordered Set/ MAC transparent) – 13 for data, not provisionable
LAG facility parameters

The table that follows provides information on LAG facility parameters.
Table 2-31
LAG facility parameters (see Note)
L2MOTR, 20G L2SS, L2SS and PDH gateway LAG
Unit LAG-shelf-slot-port Displays the facility AID.

Available ports:
For L2SS and PDH circuit packs: 401 to 404
For 20G L2SS: 401 to 408
For L2 MOTR: 403 to 412
Secondary state See “Facility secondary Indicates the operational state of the LAG facility. The
states. Read-only.
Description Up to 20 characters Sets the LAG label.

Table 2-31
LAG facility parameters (see Note) (continued)
Operational mode • BMAX Operational Mode BMAX means that all member
• PMAX ports in the LAG will be used for traffic-carrying
purposes and the committed bandwidth of the LAG
can be as much as the sum of the port members
bandwidth. LAG on 20G L2SS and L2MOTR only
supports BMAX.
Operational Mode PMAX means that both member
ports in the LAG will be used for traffic-carrying
purposes but the committed bandwidth of the LAG is
limited to the bandwidth of one port member.
about operational mode.
Maximum Ethernet • 1522 Displays the Maximum Transfer Unit (MTU) and is
frame size • 1594 1600 (Default for controlled by setting the MTU parameter for a virtual
L2MOTR) circuit segment (VCS).
• 9100 Applicable to 20G L2SS and L2MOTR LAG only.
• 9216 (Default for Note: Refer to Part 2 of Configuration - Bandwidth

20GL2SS) and Data Services, 323-1851-320 for more
information on MTU and VCS.
Load distribution MAC Determines which traffic goes through which LAG
algorithm member ports.
A distribution algorithm of MAC hashing distributes
traffic by taking the result of XORing the last 6 bits of
both SA and DA outer MAC addresses and MODing
it with the # of active links. Read-only.
about load distribution algorithm.

• NNI Not-editable (to change the interface type, the user
must delete the L2MOTR, 20G L2SS, L2SS or PDH
gateway LAG facility and re-create the LAG facility
with the new interface type)

Table 2-31
about SNMP index.
Control frame See Table 2-32 on page Associates a index to a specified LAG. The
profile 2-227 predefined profiles identify the control frame
processing behavior for each control frame protocol.
Customer priority Ethernet p-bits Indicates from where the ETH facility must look for
mode the priority. The customer priority mode is not
supported when the interface type is NNI. Read-only.
Ether type (in Hex) • 8100 (default) Sets the encapsulation scheme (for example stacked
• 9100 VLAN) used to encapsulate customer frames.
• 88A8
Policing • Enable Provides rate adaptation between the full speed

• Disable Ethernet access ports and the user subscribed
bandwidth.
Bandwidth utilized 0 to 100 Shows the amount of utilized bandwidth on a given

(%) LAG facility. Read-only.
Applicable to L2SS and PDH gateway LAG only.
Bandwidth 1 to port speed Shows the amount of available bandwidth on a given

available (kbps) LAG facility. This attribute is mainly used to find out
whether the addition of a given VCE to a given port is
possible. Read-only.

Table 2-31
Bandwidth 0 to 100 (default is 80) Sets the threshold setting (as a percentage of total
utilization threshold available port bandwidth) above which a standing AO
(%) will be raised against the applicable port. The
percentage bandwidth utilization attribute allows the
network operator to determine the percentage
utilization of a given port.
When the value is set to 0, the standing AO warning
for bandwidth threshold exceeded will not be raised.
LACP • Disable (default) Enables or disables the LACP.

• Enable LACP can only be enabled/disabled using the LAG
LACP parameter for the L2MOTR and 20GL2SS.
LACP is controlled by the SWMODE of the
equipment protection group for L2SS and PDH
gateway circuit packs.
LACP poll time • Slow (default) Polling frequency of the LACP. Slow is every 30
• Fast seconds. Fast is every 1 second.
If you are using more than 500 VCEs, you must set
the LACP poll time to slow at both the near end and
the remote end.
Queue Group 1 1, 2, 67, 68, 69, 70 A queue group specifies which scheduler profile,
(predefined) drop profiles and multipliers to be used for creating a
3-66 (user-defined) port. Typically one queue group will be used for P2P
traffic, a second queue group will be used for A2A
traffic.
Queue Group 2 1, 2, 67, 68, 69, 70 Queue group 2. Applicable to 20G L2SS LAG only.
(predefined)
3-66 (user-defined)
discard (the discard option is only available to L2SS
and PDH gateway circuit packs). It maps the
reception Ethernet priority and CFI to a class of
service.

Table 2-31
3-25 (user-defined) priority bits and DE bits of the packets transmitted or
discard (the discard option is only available to L2SS
and PDH gateway circuit packs). It maps a
transmission class of service to an Ethernet priority
and CFI.
Untagged receive • Critical-Green (-Yellow) Class of service in the receive direction.

class of service • Network-Green (-Yellow)
MAC Option • None (default) Sets the option for MAC address provisioning.
• Auto
• Manual
MAC Address ** ** ** ** ** ** Displays the MAC address of the port. Editable only
when the MAC option is set to Manual.
Port conditioning • Disable (default) Sets whether port conditioning is disabled or

• Enable enabled. Applicable to L2MOTR and 20G L2SS only.
Note: Port conditioning attributes are not supported
on LAG facilities in this release.
Conditioning type • Enable (default) Sets the conditioning type. Only applicable if port
• Disable conditioning is enabled.

Table 2-31
• TXonly • Disable (default) – Do not send ETH-CCM

messages and never condition due to a heartbeat
timeout.
condition due to a heartbeat timeout until the
remote has been detected. Detection is considered
to be the reception of one ETH-CCM, ETH-AIS, or
ETH-LCK message.
• TXonly – Send ETH-OAM frames (ETH-CCM,
ETH-AIS, ETH-LCK) but do not raise alarms or
condition the client based on any receive condition
including line port failed.
Conditioning HB • 1 second Sets the conditioning heartbeat interval. Only

interval • 100 msecond applicable if port conditioning is enabled.

Conditioning • Explicit (default) Sets the conditioning network signal. Only applicable
network signal • Type Length and Value if port conditioning is enabled.
(TLV) If Conditioning heartbeat is Disabled, this parameter
must be Explicit.
Disabled, this parameter must be TLV.
Rate of member • 10 to 100 for ETH100 Sets the rate of the members. The value will be
members (default 100) copied to the member ports Rate attribute. Only
• 10 to 1000 for ETH applicable if port conditioning is enabled.
members (default 1000)
• 10 to 10000 for ETH10G
members (default 10000)
RPR LAG
Unit LAG-shelf-slot-port Displays the facility AID.

Available ports: 401 to 404

Table 2-31
Secondary state See “Facility secondary Indicates the operational state of the LAG facility. The
states. Read-only.
Description Up to 20 characters Sets the LAG label.
Operational mode BMAX Operational Mode BMAX means that both member
ports in the LAG will be used for traffic-carrying
purposes and the committed bandwidth of the LAG
can be as much as the sum of the port members
bandwidth.
The only possible value in this release is BMAX and
no other values are shown in the drop-down menu.
The drop-down menu is only enabled if equipment is
OOS.
about operational mode.
Load distribution • MAC Sets which traffic goes through which LAG member
algorithm • OEL2UID ports.
A distribution algorithm of MAC hashing distributes
traffic by taking the result of XORing the last 6 bits of
both SA and DA outer MAC addresses and MODing
it with the # of active links.
A distribution algorithm of OEL2UID hashing
distributes OEL2 traffic by taking the result of XORing
the last 6 bits of both SA and DA IP addresses and
MODing it with the # of active links.
On the other hand, a distribution algorithm of
OEL2UID hashing distributes SVLAN traffic by taking
the result of XORing the last 6 bits of both SA and DA
outer MAC addresses and MODing it with the # of
active links (same as MAC Hashing).
about load distribution algorithm.

• NNI (default) Not-editable (to change the interface type, the user
must delete the RPR LAG facility and re-create the
LAG facility with the new interface type)

Table 2-31
about SNMP index.
profile 2-228 LAG. The predefined profiles identify the control
protocol.
Ether type (in Hex) • 8100 (default) Sets the encapsulation scheme (for example stacked
• 9100 VLAN) used to encapsulate customer frames.
• 88A8 This parameter can be edited only when the LAG

Policing • Enable Sets rate adaptation between the full speed Ethernet
• Disable (default) access ports and the user subscribed bandwidth.
For RPR circuit packs and for a LAG facility that have
LAN 1&2 or LAN 3&4 and interface type is UNI, both
Enable and Disable are supported. For RPR circuit
packs and when the interface type is NNI or when the
LAG is composed of any other LAN ports
combinations, only Disable is supported for policing.
This parameter can be edited only when the LAG
Note: If you disable policing on the ETH LAN/LAG
facilities on an RPR circuit pack, the bandwidth
profiles assigned to the VCEMAP are ignored.
discard. It maps the reception Ethernet priority and
CFI to a class of service.

Table 2-31
3-25 (user-defined) priority bits and DE bits of the packets transmitted or
discard. It maps a transmission class of service to an
Ethernet priority and CFI.
Untagged receive • Critical-Green (-Yellow)Class of service in the receive direction. The color in
class of service • Network-Green (-Yellow) the class of service is ignored by the RPR.
Maximum Ethernet For UNI: Sets the Maximum Transfer Unit (MTU).
frame size • 1522 (default) Note: The actual limit for RPR ETH Maximum
• 9100 Ethernet frame size is set by the VCS Maximum
Transfer Unit (MTU) which can be set to either 1600
For NNI:
or 9100. Refer to Part 2 of Configuration - Bandwidth
• 1600 (default) and Data Services, 323-1851-320 for more
• 9216 information on MTU and VCS.
This parameter can be edited only when the LAG
Note: Link Aggregation Group (LAG) represents a combination of LANs on the L2 MOTR, 20G L2SS,
L2SS, PDH gateway, or RPR circuit pack. Therefore, the combined LANs on the L2 MOTR, 20G L2SS,
L2SS, PDH gateway, or RPR circuit pack can be collectively treated as a single high capacity bandwidth
link.

Table 2-32
Control frame profile summary/applicability (L2MOTR, 20G L2SS, L2SS and PDH gateway circuit
packs)
Control Frame Profile Port applicability Interface type applicability

(Note 1 and Note 2)
ETH ETH10G WAN LAG UNI NNI

ETH100 (Note 3) (Note 4)
(Note 3)
1: Drop All Yes Yes Yes No Yes Yes
2: EFM + Drop Other (Note 5) Yes No No No Yes No
3: LAG + Drop Other Yes Yes No Yes Yes Yes
4: P2P Tunnel Yes Yes Yes No Yes No
5: EFM + P2P Tunnel (Note 5) Yes No No No Yes No
6: LAG + P2P Tunnel Yes Yes No Yes Yes No
7: LAG, SONMP+Drop (Note 5) Yes Yes No Yes Yes Yes
8: SONMP + Drop Other (Note 5) Yes Yes Yes No Yes Yes
9: A2A Tunnel Yes Yes Yes No Yes No
10: SONMP + A2A Tunnel (Note 5) Yes Yes Yes No Yes No
11: LAG, LLDP, LACP+Drop (Note Yes Yes No Yes Yes Yes
5 and Note 6)
12: LLDP + Drop Other (Note 5 Yes Yes Yes No Yes Yes
and Note 6)
13: LLDP + A2A Tunnel (Note 5 Yes Yes Yes No Yes No

and Note 6)
Note 1: Refer to 6500 Packet-Optical Platform Data Application Guide, NTRN15BA for more information
Note 2: To support a certain control frame profile for a specific port/interface type, both values for port and
interface type must show “Yes”.
Note 3: ETH10G/ETH100 is only applicable to 20G L2SS and L2 MOTR circuit packs.
Note 4: Not applicable to the L2 MOTR WAN.
Note 5: When a 20G L2SS, L2SS or PDH gateway circuit pack is part of a protection group, you cannot
set the control frame profile to PEER EFMOAM, SONMP, or LLDP (20G L2SS only).
Note 6: Control frame profiles 11, 12, and 13 are supported on the L2 MOTR and 20G L2SS circuit packs
only.

Table 2-33
Control frame profile summary/applicability (RPR circuit packs)
Control Frame Profile Port applicability Interface type applicability

(Note 1 and Note 2)
ETH WAN LAG UNI NNI

(Note 3) (Note 3)
1: Drop All No No No Yes Yes
2: EFM + Drop Other No No No Yes No
3: LAG + Drop Other Yes No Yes Yes Yes
4: P2P Tunnel Yes Yes No Yes No
5: EFM + P2P Tunnel No No No Yes No
6: LAG + P2P Tunnel Yes No Yes Yes No
7: LAG, SONMP+Drop Yes No Yes Yes Yes
8: SONMP + Drop Other Yes No No Yes Yes
9: A2A Tunnel Yes Yes No Yes Yes for ETH

No for WAN
10: SONMP + A2A Tunnel Yes No No Yes No
Note 1: Refer to 6500 Packet-Optical Platform Data Application Guide, NTRN15BA for more
information about control frame profile.
Note 2: To support a certain control frame profile for a port/interface type, both values for port and
interface type must show “Yes”.
Note 3: RPR WAN UNI ports are not supported in this release.


The table that follows provides information on OTM2 facility parameters.
Table 2-34
Unit OTM2-shelf-slot-port Displays the facility AID. Read-only.
Secondary State See “Facility secondary Displays the facility operational state. Read-only
states” on page 2-179
Rate • 10.7G Displays the facility rate.

• 11.05G
• 11.09G
Optical System Up to 8 alphanumeric Sets the optical system identifier used by other
Identifier characters and applications for network topology building blocks to
underscore “_” build an optical network model including DWDM
transmit/receive elements.
Setting the optical system identifier in this dialog
overrides the default setting provisioned in the Node
Information application which is used when OTM2
facilities are auto-provisioned.
Tx Path Identifier 1 to 254 Sets the transmit path identifier which allows two
different transmitters with identical wavelengths in the
same network element to be identified uniquely in an
optical system.
Setting the transmit path identifier in this dialog
overrides the default setting provisioned in the Node
Information application which is used when OTM2
facilities are auto-provisioned.

Table 2-34
Tx Actual Power • Tx optical power Displays the measured line transmit optical power.
pack not present) When the outgoing transmit optical power level for the
monitored port is out of range, the Tx Actual Power
parameter displays "OOR". The corresponding
OPT-OCH/OCH-OPT value in the Site Manager
Performance Monitoring application does not
display "OOR" when out of range; the lowest reading
is -45 dBm. Refer to Fault Management - Performance
OPT-OCH/OCH-OPT values.
Tx Wavelength (nm) 1528.77 (93) to Sets the required line transmit wavelength.
1565.09 (88), at 50 GHz Tx Wavelength cannot be edited unless the facility is
spacing (default 0) OOS.
The number in brackets is the channel ID. Tx
wavelength may auto-provision.
Tx FEC Format • Off Sets the transmit Tx FEC format setting.

• RS8 (ITU-T G.709 RS8 and SCFEC are the OTU FEC modes applied to
RS-8) achieve greater margin on a given link.
(default) The OTM2 Tx FEC Format parameter cannot be
edited unless the facility is OOS.
Rx Actual Power • Rx optical power Displays the measured line receive optical power.
pack not present) When the incoming receive optical power level for the
monitored port is out of range, the Rx Actual Power
parameter displays "OOR". The corresponding
OPR-OCH/OCH-OPR value in the Site Manager
Performance Monitoring application does not
display "OOR" when out of range; the lowest reading
is -45 dBm. Refer to Fault Management - Performance
OPR-OCH/OCH-OPR values.
The value may not be accurate if it is outside the
normal operating range.

Table 2-34
Rx FEC Format • Off Select the receive Rx FEC format setting.

• RS8 (ITU-T G.709 RS8 and SCFEC are the OTU FEC modes applied to
RS-8) achieve greater margin on a given link.
(default) The OTM2 Rx FEC Format parameter cannot be
edited unless the facility is OOS.
Pre-FEC Signal Fail -1.00 to +1.00 dBQ Sets the threshold level for the Pre-FEC Signal Fail
Threshold (dBQ) (default 0) alarm (applicable only when FEC is On). Can be
provisioned in 0.01 steps. 0 dBQ equates to 1x10^-15
post FEC errors.
This parameter cannot be edited unless the facility is
OOS.
ODU TTI • Yes (default) Displays whether the trail trace identifier (TTI)
Termination • No message is transmitted at the line transmitter.
Port Mode • SONET (default for Select the mode of the port. Determines if SONET or
SONET NE mode) SDH terminology is used and whether bit (SONET) or
• SDH (default for SDH block (SDH) errors are used for performance
NE mode) monitoring.
You cannot edit the port mode. To change the port
mode you must delete the OTM2 facility and then
re-add it with the correct port mode.

Reference • Yes reference.


PTP facility parameters

The table that follows provides information on PTP facility parameters.
Table 2-35
PTP facility parameters
Secondary State See “Facility secondary Displays the facility operational state. The Auto
states” on page 2-179 In-Service state and Maintenance state are editable.
Auto In-Service hh-mm Displays the time left for the auto in-service timer.
Time Left (hh-mm) Read-only.

Facility Identifier characters the Common Language Facility Identifier (CLFI).
Service Type • OTUk (k=2, 2e) Sets the service type. Default depends on pluggable
• ETH100M and fixed optics. Defined at creation time. Not editable
• ETH1G Note: B-700-1036-001 on eMOTR is

auto-provisioned with the ETH1G service type. To
• ETH10G
provision the ETH100M service type, you must delete
and re-provision the PTP facility with the ETH100M
service type.
Conditioning Type • Laser off Displays the conditioning type. Read-only. None for
• None service type OTU2 or OTU2e, and Laser off for
service type ETH1G or ETH10G.
Tx Path Identifier 1 to 254 Sets the transmit path identifier which allows two
different transmitters with identical wavelengths in the
same network element to be identified uniquely in an
optical system.
Applicable only to DWDM capable pluggables when
service type is OTU2 and OTU2e.

Table 2-35
PTP facility parameters (continued)
Rx Actual Power • Rx optical power Displays the actual receive optical input power.
(dBm) • Unknown (if circuit pack Read-only.
not present)
Tx Actual Power • Tx optical power Displays the actual transmit optical output power.
(dBm) • Unknown (if circuit pack Read-only.
not present)
Tx Wavelength (nm) pluggable dependent Sets the transmit wavelength in nm. Tx Wavelength
cannot be edited unless the facility is OOS, except
when changing from 0 to a valid wavelength, which
can be IS. Editable on tunable DWDM pluggables
only.
OTUTTP facility parameters

The table that follows provides information on OTUTTP facility parameters.
Table 2-36
OTUTTP facility parameters
Unit OTUTTP-shelf-slot-port Displays the facility AID. Read-only.
Primary State See “Equipment and Displays the primary state of the facility, which follows
facility primary states” on the primary state of its parent PTP facility. Read-only.
page 2-178
Secondary State See “Facility secondary Displays the facility operational state. The Auto
states” on page 2-179 In-Service state and Maintenance state follows the
parent PTP facility. Read-only.
Supporting PTP-shelf-slot-port Displays the supporting termination point. Read-only.

Termination Point
Number of trib slots 1 Displays the number of tributary slots comprising the
TTP. Read-only.
Basic rate • OTU2 Displays the OTU rate, depending on the PTP service
• OTU2e type. Read-only.
Pre-FEC Signal Fail -1.00 to 1.00 (default 0) Sets the threshold level for the Pre-FEC Signal Fail
Threshold (dBQ) alarm (applicable only when FEC is On). Can be
provisioned in 0.01 increments.
Facility must be OOS to edit this parameter.

Table 2-36
OTUTTP facility parameters (continued)
Pre-FEC Signal -1.00 to 2.00 (default 0.5) Sets the threshold level for the Pre-FEC Signal
Degrade Threshold Degrade alarm (applicable only when FEC is On).
(dBQ) Can be provisioned in 0.01 increments.
Pre-FEC Signal Fail numeric value Displays the threshold level in BER for the Pre-FEC
Threshold (BER) Signal Fail alarm (applicable only when FEC is On).
Read-only.
Pre-FEC Signal numeric value Displays the threshold level in BER for the Pre-FEC
Degrade Threshold Signal Degrade alarm (applicable only when FEC is
(BER) On). Read-only.
OTU Signal Degrade 1x10^-6 Displays the OTU signal degrade threshold
Threshold (applicable only when FEC Mode is Off). Read-only.
Forward Error RS8 (default) or Off Displays the FEC on RX. FEC on RX is set internally
Correction on RX to be the same as FEC on TX. Cannot be provisioned
independently. Read-only.
Forward Error RS8 (default) or Off Sets the FEC on TX. Facility must be OOS to edit this
Correction on TX parameter.

Facility Identifier characters the Common Language Facility Identifier (CLFI).


ETTP facility parameters

The table that follows provides information on ETTP facility parameters.
Table 2-37
ETTP facility parameters
Unit • ETTP-shelf-slot-port Displays the facility AID. Read-only.

• ETTP-shelf-slot-port-2P1 2P1 in the second AID option indicates tributary port rate
• ETTP-shelf-slot-port-id1- and tributary port number and is applicable to the
id2 mapped ETTP facility only.
id1=3P1, id2=2Pn, n=1 to 4 for eMOTR backplane ports
Primary State See “Equipment and Sets the primary state of the facility, which follows the
facility primary states” on primary state of its parent PTP facility for faceplate ports
page 2-178 or its parent ODU2/ODU2e TTP facility for backplane
ports. Read-only.
states. The Auto In-Service state and Maintenance state
follows the parent PTP facility. Read-only.
Interface Type • I-NNI (default on ports Indicates the service type. The eMOTR backplane ports
9-12 and backplane) support the I-NNI interface type only.
• E-NNI
• UNI (default ports 1-8,
21-36, 41-56)
Supporting • PTP-shelf-slot-port Displays the supporting termination point. Read-only.

Termination • ODUTTP-shelf-slot-port- PTP for non-mapped ETTPs, ODUTTP for 11.09G -
Point 2P1 OPU2e (PCS transparent) mapped ETTPs, and WAN for
• ODUTTP-shelf-slot-port- GFP mapped ETTPs.
id1-id2
• WAN-shelf-slot-port-2P1
• WAN-shelf-slot-port-id1-
id2
Basic rate • ETH100M Displays the rate of the interface, depending on the PTP
• ETH1G service type for faceplate ports. ETH10G for backplane
ports. Read-only.
• ETH10G

Table 2-37
ETTP facility parameters (continued)
Packet Mapping See description Sets the Ethernet mapping into OTN. Facility must be
OOS to edit this parameter.
• 10.7G - GFP/OPU2 (Standard MAC transparent)
This packet mapping provides mapping of 10GE LAN
PHY (10G-BASE-R) signal to 10.709G OTU2 signal,
using GFP-F, asynchronous, standard WAN.
• 10.7G - GFP/OPU2+7 (Preamble/ Ordered Set/ MAC
transparent)
PHY (10G-BASE-R) signal to 10.709G OTU2 signal,
using GFP-F, asynchronous, Preamble, Ordered Set
transparent, and MAC transparent WAN.
• 11.09G - OPU2e (PCS transparent)
PHY (10G-BASE-R) to a proportionally wrapped
11.096G OTU2e signal, synchronous, CBR10G.
• None
Port TERMINATED Indicates that the MAC and PHY layers are terminated.
Conditioning Read-only.
L2 Active Config • Yes Indicates whether there is an active L2 configuration on

• No the port. Read-only.
L2 Saved Config • Yes Indicates whether there is a saved L2 configuration on

• No the port. Read-only.


Defined Facility characters Common Language Facility Identifier (CLFI).
Identifier
Note: Auto-negotiation on eMOTR ETTP is configured with SAOS-based CLI only.

FTTP facility parameters

The table that follows provides information on FTTP facility parameters.
Table 2-38
FTTP facility parameters
Unit FTTP-shelf-slot-port Displays the facility AID.
Supporting • OTUTTP-shelf-slot-port Displays the supporting termination point. Read-only.

Termination Point • null
ODUTTP facility parameters

The table that follows provides information on ODUTTP facility parameters.
Table 2-39
ODUTTP facility parameters
Unit ODUTTP-shelf-slot-port-2 Displays the facility AID.

P1 id1=3P1, id2=2Pn, n=1 to 4 for eMOTR backplane ports
ODUTTP-shelf-slot-port-[id
1[-id2]]
Primary State See “Equipment and Sets the primary state of the facility, which follows the
facility primary states” on primary state of its parent PTP facility or parent
page 2-178 ODU3TTP for backplane ports. The primary state of the
backplane ODU3TTP can be independently changed.
states. The Auto In-Service state and Maintenance state
follows the parent PTP facility. Read-only.
Supporting • OTUTTP-shelf-slot-port Displays the supporting termination point. Read-only.

Termination • FTTP-shelf-slot-port
Point
• ODUTTP-shelf-slot-port-
3P1
Signal Degrade 1x10^-6 Displays the signal degrade threshold.

Threshold
Basic rate • ODU2 Displays the rate of the facility. Not editable
• ODU2e
• ODU3

Table 2-39
ODUTTP facility parameters (continued)
Number of trib 16 or - Displays the number of tributary slots comprising the

slots TTP, depending on the rate. Applicable only to the
ODU3TTP on the eMOTR backplane port. Read-only.
Owner PARENT Displays the entity which created the facility. Read-only.
USER
Tributary slot ODU1 or - Displays the tributary slot size. Applicable only to the
size ODU3TTP on the eMOTR backplane port. Read-only.
Protection Type NOT_PROTECTED Displays the type of protection the facility has. Read-only.
Expected 2 byte string in hex format Displays the expected payload type, depending on the
payload type mapping. See Figure 2-18 on page 2-121 for details.
Received 2 byte string in hex format Displays the received payload type. Read-only.
payload type
Conditioning • OPUK_AIS Displays the conditioning type for non-OTN client faults.
type • OPUK_CSF
• OPUK_CSF&OPUK_AIS
(default)
• ODUK_AIS
Client Type ETH Indicates if the ODU is a server layer for an OTN or
OTN non-OTN client layer. Read-only.

Defined Facility characters Common Language Facility Identifier (CLFI).
Identifier

Synchronization parameters
Table 2-40
Timing reference parameters
Mode Source (Note 1) Description
Internal Timing - No sources available for selection
Line Timing • ETH10G and OTM2 line ports on L2 See Note 2, Note 3, and Note 4
MOTR
• ETTP or OTUTTP faceplate ports on
eMOTR
External Timing BITSIN-A/ESI-A External synchronization input A

(see Note 5 and Note 6)
BITSIN-B/ESI-B External synchronization input B
None Indicates an unused source
Mixed Timing BITSIN-A/ESI-A External synchronization input A

(Note 6) BITSIN-B/ESI-B External synchronization input B
Any equipped OC-n/STM-n/STM1J/ See Note 2, Note 3, and Note 4

STM4J port
Note 1: Each possible source, except None, can appear only once in the timing reference hierarchy.
Note 2: Only one port on each multi-port circuit pack can be selected as a timing generation and timing
distribution reference.
Note 3: DS3, EC-1, E1, E3, DS1DS3, E1DS3, E1E3, STM1E, GE, 10/100BT, 10GE, L2SS, PDH gateway,
and RPR facilities cannot be set as synchronization source references.
Note 4: DS1 DSM facilities and OC-3 ports which are provisioned as DSM hosts cannot be set as
Note 5: To maximize reliability, the BITSIN/ESI ports require the payload of the incoming signal to be all 1’s.
The BITSIN/ESI hardware may not operate correctly with other payload patterns.
Note 6: It is not applicable to SuperMux, FLEXMOTR, or L2MOTR independent timing groups.

RPR Ring provisioning parameters

Table 2-41 details the parameters associated with provisioning and managing
RPRs.
Table 2-41
RPR Ring provisioning parameters
Shelf 1 to 254 Displays the shelf number. Read-only.
Name RPR-[1 to 254]-[1 to 6, 9 to 14 The name of the RPR port in the format
for 14-slot shelf and 1 to 8, 11 to RPR-shelf-slot-rprid. RPR ports are virtual ports
18, 21 to 28, and 31 to 38 for that interconnect the two physical WAN ports at
32-slot shelf]-[801, 802] the RPR station.
Primary State • IS The primary state of the RPR port is defined in

• OOS the Add Ring and Edit Ring dialogs as IS (In
Service) and OOS (Out of Service). IS is the
default.
The primary states appear in the RPR
provisioning list as:
IS-ANR (In Service - Abnormal)
OOS-MA (Out Of Service - Maintenance)
OOS-AU (Out Of Service - Autonomous)
OOS-AUMA (Out Of Service - Autonomous
Maintenance)
OOS-MAANR (Out Of Service - Maintenance
Abnormal)
Secondary State Supporting Entity Outage The secondary state of the RPR port. Read-only.
Supported Entity Absent
Faulted
Disabled
Ring Name Up to 64 characters The descriptive name of the ring.
Station Name Up to 64 characters The descriptive name of the RPR station.
Ring Operational • JUMBO The summary of the operational modes for the
Mode • WRAP RPR station as discovered by the topology
discovery protocol. All stations in the ring must
• OPEN support the same mode or the ring is considered
• UNKNOWN an open ring. Read-only.

Table 2-41
RPR Ring provisioning parameters (continued)
Ring Status • Inconsistent The current status of the RPR station as follows:
• Exceeded Maximum Stations • “Inconsistent” means there is a topological
• UNKNOWN inconsistency.
• “Exceeded Maximum Stations” means there
are more than the maximum number of stations
in the RPR.
This parameter supports alarm generation.
Read-only.
Number of Stations 1 to 255 The number of stations in the RPR. When the
operational state of the RPR is down, the value
is 1. This release supports a maximum of
• 12 stations per RPR when traffic is engineered
for potential congestion in the RPR.
• 28 stations per RPR when traffic is engineered
for no potential congestion in the RPR.
Read-only.
Wrap DISABLE Displays whether the RPR station is configured

Configuration with wrap protection mode. The only value
possible is Disable. Read-only.
Reversion Mode Y Displays whether the protection reversion mode

is enabled for the RPR station.
Wait To Restore 0, 1, 2, 3, 4, 5, 10, or 30 Specifies the Layer 2 wait-to-restore time for the
RPR station, which is the length of time in
seconds to remain in the protection state after
the removal of the cause of an automatic
protection. The default is 10.
Fast Timer 1, 2, 5, 10, or 20 Specifies the duration of the Layer 2 fast timer
for protection messages in ms. The default value
is 10 ms. This parameter applies to the RPR
station.
Slow Timer 50, 100, 500, 1000, 5000, or Specifies the duration of the Layer 2 slow timer
10000 for protection messages in ms. The default value
is 1000 ms. This parameter applies to the RPR
station.
Keep Alive Timeout 0 to 200, increments of 10 Specifies the time to declare a keepalive timeout
for the RPR station. The default value is 20 ms.

Table 2-41
Attribute Discovery 50, 100, 500, 1000, 5000, or Specifies the message transmission timer period
Message 10000 for the attribute discovery feature in ms. The
default is 1000 ms. This parameter applies to
each RPR station.
Support for more •Y Displays whether the RPR station supports more
than 2.5G •N than 2.5 Gbps of bandwidth per ringlet. This
parameter is set to Y (yes) only on RPR 801 on
each RPR circuit pack. Read-only.
Aggressive N Displays whether the fairness rate adjustment

Fairness for the RPR station is aggressive or
conservative. The only possible value is N (no).
Read-only.
Jumbo Preferred Y Displays whether Jumbo frames in a MAC entity

that supports jumbo frames are preferred. This
parameter applies to the station. Read-only.
MAC Operational DROPBADFCS Displays the summary of the MAC operational

Mode modes for the RPR station. Frames with bad
frame check sequences (FCSs) are dropped.
Read-only.
Spatially Aware ENABLE Displays whether the spatially aware sublayer

(SAS) is enabled for the RPR station. The SAS
is only activated when all stations on the RPR
have SAS enabled. An RPR station that does not
support SAS cannot have SAS enabled. In this
release, the only possible value is Enable.
Read-only.
Spatially Aware • TRUE Displays whether the SAS for the RPR station is
Active • FALSE active (TRUE) or inactive (FALSE). If the circuit
pack is not available (for example, it has failed or
• UNKNOWN it is provisioned but not actually present),
UNKNOWN appears.
Spatial awareness is only active if all other
stations in the RPR ring have the Spatially
Aware parameter enabled. Read-only.
PTQ size 0 to 42949667295 Displays the size in bytes of the primary transit
queue per ringlet this RPR station’s MAC entity
supports. Read-only.

Table 2-41
STQ size 0 to 42949667295 Displays the size in bytes of the secondary

transit queue per ringlet this RPR station’s MAC
entity supports. Read-only.
SNMP Index 32-bit value Displays the SNMP index number, which is the
index of the equivalent entity instance in the MIB
group for the SNMP interface for the RPR
station. Read-only.
Even Station Path • AUTO Specifies the value of the tie-break path to create
Control • EAST the bidirectional traffic on the ring.
• WEST
West Rate If VCAT is enabled: Displays the basic rate assigned to the west
• NONE span WAN of the RPR facility. It is derived from
the cross-connections assigned to that west
• STS1 span WAN port. Read-only.
• STS3C
If VCAT is disabled:
• NONE
• STS12C
• STS48C
east rate If VCAT is enabled: Displays the basic rate assigned to the east span
• NONE WAN of the RPR facility. It is derived from the
cross-connections assigned to that east span
• STS1 WAN port. Read-only.
• STS3C
• NONE
• STS12C
• STS48C
West Provisioned If VCAT is enabled: Displays the number of provisioned bandwidth

Units • 0 to 96 when west rate is units of the west span WAN of the RPR facility in
STS1 the SONET/SDH transmit direction. It is derived
from the cross-connections assigned to that
• 0 to 32 when west rate is west span WAN port. Read-only.
STS3C
•0
•1

Table 2-41
East Provisioned If VCAT is enabled: Displays the number of provisioned bandwidth

Units • 0 to 96 when east rate is STS1 units of the east span WAN of the RPR facility in
the SONET/SDH transmit direction. It is derived
• 0 to 32 when east rate is from the cross-connections assigned to that east
STS3C span WAN port. Read-only.
•0
•1
West Actual Units If VCAT is enabled: Displays the number of provisioned bandwidth
• 0 to 96 when west rate is units of west span WAN of the RPR facility that
STS1 is actually carrying traffic in the SONET/SDH
transmit direction. It is derived from the
• 0 to 32 when west rate is cross-connections and the SONET/SDH
STS3C failures. Read-only.
• UNKNOWN when there is no
west span WAN associated to
the RPR facility
•0
•1
• UNKNOWN
East Actual Units If VCAT is enabled: Displays the number of provisioned bandwidth
• 0 to 96 when east rate is STS1 units of east span WAN of the RPR facility that is
actually carrying traffic in the SONET/SDH
• 0 to 32 when east rate is transmit direction. It is derived from the
STS3C cross-connections and the SONET/SDH
• UNKNOWN when there is no failures. Read-only.
east span WAN associated to
the RPR facility
•0
•1
• UNKNOWN
Additional fields on the Add Ring dialog
Ring Port • 801 The identifier for the RPR port (rprid).
• 802

RPR Protection parameters

The following table details the parameters associated with provisioning
protection for spans in RPRs.
Table 2-42
RRP Ring protection (span) parameters
Unit RPR-[1 to 254]-[1 to 6, 9 to 14 The name the RPR port in the format:
for 14-slot shelf and 1 to 8, 11 to RPR-shelf-slot-rprid.
18, 21 to 28, and 31 to 38 for
32-slot shelf]-[801, 802]
Port WAN-[1 to 254]-[1 to 6, 9 to 14 The WAN port associated to the RPR port in the
for 14-slot shelf and 1 to 8, 11 to format WAN-shelf-slot-port.
18, 21 to 28, and 31 to 38 for
32-slot shelf]-[101 to 104]
Direction • East The physical direction of the RPR span.

• West

Table 2-42
RRP Ring protection (span) parameters (continued)
Hold off Time 0, 10, 20, ... to 200 The time in ms allowed for the physical layer to
perform its own protection mechanism before
the RPR layer 2 protection activates. This
parameter applies to each span of a station. The
default is 0 ms.
Additional fields on the Add Ring Protection dialog
Ring RPR-[1 to 254]-[1 to 6, 9 to 14 The name of the RPR port in the format:
for 14-slot shelf and 1 to 8, 11 to RPR-shelf-slot-rprid.
18, 21 to 28, and 31 to 38 for The port can be provisioned as follows:
32-slot shelf]-[801, 802]
• Ring (RPR port) 801 can be associated to WAN
ports that have up to 5 Gbps provisioned on
them.
• Ring (RPR port) 802 can be associated to WAN
ports that have up to 2.5 Gbps provisioned on
them.
• The sum of the bandwidth associated to the
WAN ports on the RPR circuit packs cannot
exceed 10 Gbps in any slot if a 160 Gbps
cross-connect circuit pack is used; or if the
circuit pack is equipped in slots 5, 6, 9 or 101 to
6, 9 to 14 for 14-slot shelf and 1 to 8, 11 to 18,
21 to 28, and 31 to 38 for 32-slot shelf with an
80 Gbps cross-connect circuit pack.
• The sum of the bandwidth associated to the
WAN ports on the RPR circuit pack cannot
exceed 5 Gbps if the circuit pack is equipped in
slots 1 to 4 or 11 to 14 with an 80 Gbps
cross-connect circuit pack.

Profiles Provisioning task

The Profile Provisioning task in the Service Activation Setup application
contains the bandwidth profile provisioning step. The following table lists the
bandwidth profile provisioning parameters.
Table 2-43
Profile Provisioning tasks (Bandwidth Profile provisioning)
Profile index 9 to 200 Sets the profile index number.

(9-200)
Profile name An alphanumeric character(s) Sets the name of the profile. This attribute has a
limit of 20 alphanumeric characters. You can also
use special characters, except %, \, and “.
Committed • 0bps (default) Sets CIR units. CIR units is the number of units in
Information Rate • 64kbps which CIR is specified.
Units
• 1Mbps
• 10Mbps
• 100Mbps
Committed • 0 for 0bps CIR units Sets CIR multiplier. CIR defines the committed
Information Rate • 0 to 32 for 64 kbps CIR units rate of information that the network delivers.
(10 is the default) The CIR is read-only if the CIR units value is 0bps.
• 0 to 99 for 1 Mbps CIR units
(10 is the default)
• 0 or 10 to 100 for 10 and 100
Mbps CIR units (10 is the
default)
Committed Burst • 0 for 0bps CIR units Sets the committed burst duration (CBD). CBD is
Duration in ms for • 0 to 1200 for 64 kbps CIR also known as time committed (TC). CBD defines
0 bps, 64 kbps, units (10 is the default) the amount of time traffic is allowed to burst over
1 Mbps, and the CIR.
10 Mbps CIR units • 0 to 100 for 1 Mbps CIR units The CBD is read-only if CIR units is 0bps.
(10 is the default)
or
• 0 to 100 for 10 and 100 Mbps
Committed Burst CIR units (10 is the default)
Duration in 100s of
µs for 100 Mbps
CIR units

Table 2-43
Profile Provisioning tasks (Bandwidth Profile provisioning) (continued)
Excess Information • 0bps (default) Sets the EIR units. EIR units is the number of units
Rate Units • 64kbps in which EIR is specified.
• 1Mbps
• 10Mbps
• 100Mbps
Excess Information • 0 for 0bps EIR units Sets the EIR multiplier. The EIR defines the
Rate • 0 to 32 for 64 kbps EIR units sustainable rate of information in excess of CIR
(10 is the default) that the network delivers if there is available
bandwidth.
• 0 to 99 for 1 Mbps EIR units
(10 is the default) EIR is read-only if the EIR units value is 0bps.
• 0 or 10 to 100 for 10 and 100

Mbps EIR units (10 is the
default)
Excess Burst • 0 for 0bps EIR units Sets the excess burst duration. EBD is also
Duration in ms for • 0 to 1200 for 64 kbps EIR known as time excessed (TE). Excess burst
0 bps, 64 kbps, units (10 is the default) duration (EBD) defines the amount of time traffic
1 Mbps, and is allowed to burst over the EIR.
10 Mbps EIR units • 0 to 100 for 1 Mbps EIR units EBD is read-only if the EIR units value is 0 bps.
(10 is the default)
or
• 0 to 100 for 10 and 100 Mbps
Excess Burst EIR units (10 is the default)
Duration in 100s of
µs for 100 Mbps
EIR units
Over-subscription 1 (default) to 50 Sets the over-subscription ratio (OVSR). The

Ratio OVSR is the ratio between the cumulative CIR for
all flows destined for a particular egress port,
compared to the port speed. The oversubscription
ratio operates on a per-bandwidth profile basis.

Table 2-43
Profile Provisioning tasks (Bandwidth Profile provisioning) (continued)
Policer • RFC4115 (default) Sets the policer. The policer specifies the
• RFC2697 algorithm to classify the incoming traffic.
• RFC2698 If the policer is RFC4115, the CIR is the

bandwidth always reserved for green packets and
the EIR is the bandwidth reserved for excess
green packets or yellow packets. Only this type of
policer is allowed on the bandwidth profiles
specified on the VCEs. RFC4115 policer is not
supported on L2 MOTR circuit packs.
If the policer is RFC2698, the CIR + EIR is the
bandwidth reserved for green packets or yellow
packets. With this policer, the CIR bandwidth may
be used by yellow packets (which never happens
with policer RFC4115). The profiles with policer
RFC2698 can only be used on Port Bandwidth
attribute of the ETH and ETH10G facilities of the
20G L2SS circuit packs. For L2 MOTR circuit
packs, the profiles with policer RFC2698 can only
be used on Bandwidth attribute of the VCE and it
will be ignored if set on ETH or ETH10G facilities
of the L2 MOTR circuit packs.
Note: You must not use RFC2697 for policer
attribute since RFC2697 is not supported for
policer in this release.

Virtual Circuit Service Activation task

The Virtual Circuit Service Activation task in the Service Activation Setup
application contains three steps:
• VCS Provisioning step
Table 2-44 lists the VCS provisioning parameters.
• VCE Provisioning step
Table 2-45 on page 2-253 lists the VCE provisioning parameters.
• VC Endpoint Map Provisioning step
Table 2-46 on page 2-260 lists the endpoint map provisioning parameters.
Operating System (SAOS) for Layer 2 services. Refer to SAOS-based Packet
Services Configuration, 323-1851-630 for detailed information.
Table 2-44
Virtual Circuit Service Activation task (VCS parameters)
Connection ID Up to 48 alphanumeric ASCII Enters the virtual circuit segment connection

characters identifier. The connection ID string is used to
identify a provisioned virtual circuit segment.
This release supports a virtual circuit segment
connection identifier for L2 MOTR circuit packs.
However if you want to use the virtual circuit
segment connection identifier for other Layer 2
circuit packs, you must contact your Ciena
representative.
Note 1: Up to 256 connection IDs are supported
per each 6500 node.
Note 2: The same connection ID can be used
for multiple virtual circuit segments (uniqueness
is not validated by the system and each duplicate
connection ID entry takes counts towards the
256 connection ID limit).
Shelf 1 to 254 Sets the shelf number.
VC Segment ID 1 to 1048575 Sets the virtual circuit segment identifier. You

(1-1048575) use the VC segment ID to create the association
between the VCS and its VCEs. The VCS and
associated VCEs all have the same VC segment
ID value, which uniquely identifies a specific
customer flow in the L2SS, PDH gateway,
20G L2SS, L2 MOTR, or RPR network.

Table 2-44
Virtual Circuit Service Activation task (VCS parameters) (continued)
Ring Group ID • 1 to 256 Selects the ring group identifier. The ring group
• All ID indicates which G.8032 ERP ringlet group the
VCS belongs to. The ring group ID value is set to
zero if VCS is not associated to any G.8032 ERP
group.
For more information about G.8032 ERP and
group ID, refer to “Data services G.8032 ERP
management provisioning” Part 3 of the
Configuration - Bandwidth and Data Services,
323-1851-320.
Primary State • IS (default) Sets the primary state of the VCS.

• OOS
Queue group • 1 or 2 for 20G L2SS circuit Sets the queue group. The queue group attribute
packs (1 is the default) on a VCS defines which queue group the VCEs
• 1 for L2 MOTR, L2SS, and of the VCS are using on each of the ports.
PDH Gateway circuit packs Only 20G L2SS circuit packs support two queue
Not supported for RPR groups and the rest of L2SS circuit packs (L2SS
and PDH Gateway) and L2 MOTR circuit packs
only support one queue group (that means when
a port or VCE is created on a L2SS circuit pack
other than 20G L2SS circuit pack or on a L2
MOTR circuit pack, the value of queue group is
ignored and queue group 1 is used).
Data type • Customer Data (default) Sets the VCS data type. The data type defines
• Customer Management the customer data or service provider
management flows.
• Management
Network topology • Point to Point (default) Sets the VCS network topology, which defines
• Any to Any the network connectivity model for the VCS.
For G.8032 ERP protected connections (Ring
Group used is not 0), Any to Any network
topology must be used on the VCS.

Table 2-44
Virtual Circuit Service Activation task (VCS parameters) (continued)
Class of service • Critical Sets the VCS class of service. For L2SS,
• Network 20G L2SS, and PDH Gateway circuit packs, the
CoS is an indicator for a traffic flow in the service
• Premium provider network. The CoS influences traffic flow
• Platinum packet delay and discard eligibility. For
• Gold L2 MOTR circuit packs, this parameter has no
meaning and is ignored.
• Silver
You can create up to eight classes of service for
• Bronze each VCS.
• Standard (default)
Maximum transfer • 1600 (default) Sets the maximum transfer unit, which defines
unit • 9100 the largest packet size that the VCS can
transport within the service provider network.
RPR and L2 MOTR circuit packs do not use the
Maximum transfer unit parameters. For RPR and
L2 MOTR circuit packs, the maximum Ethernet
transfer unit parameter for the ETH (LAN) and
ETH10G (LAN L2 MOTR only) facility defines
the largest packet size.
Ring Group ID 1 to 256 Sets the ring group identifier. The ring group ID
indicates which G.8032 ERP group the VCS
belongs to. The ring group ID value is set to zero
if VCS is not associated to any G.8032 ERP
group.
For more information about G.8032 ERP and
group ID, refer to Part 3 of Configuration -
Bandwidth and Data Services, 323-1851-320
(chapter 25; “Data services G.8032 ERP
management provisioning”).

Table 2-45
Virtual Circuit Service Activation task (VCE parameters)
Shelf 1 to 254 Displays the shelf number.

Read-only.
Virtual circuit ID 1 to 1048575 Displays the virtual circuit ID for VCS

display.
The virtual circuit ID creates the
association between the VCS and its
VCEs. The VCS and associated
VCEs all have the same virtual
circuit ID value, which uniquely
identifies a specific customer flow in
the L2SS, PDH gateway, 20G L2SS,
L2 MOTR, or RPR network.
Read-only.
Equipment • L2SS-[1 to 254]-[1 to 6, 9 to 14 for 14-slot Sets the L2SS, PDH gateway, 20G
shelf and 1 to 8, 11 to 18, 21 to 28, and 31 L2SS, L2 MOTR, or RPR circuit
to 38 for 32-slot shelf] pack according to the equipment slot
• 20GL2SS-[1 to 254]-[1 to 6, 9 to 14 for in the format:
14-slot shelf and 1 to 8, 11 to 18, 21 to 28, • L2SS-shelf-slot for L2SS and PDH
and 31 to 38 for 32-slot shelf] gateway circuit packs
• L2MOTR-[1 to 254]-[1 to 6 for 6500-7 • 20GL2SS-shelf-slot for 20G L2SS
packet-optical shelf, 1 to 14 for 14-slot circuit packs
shelf, 1 to 8, 11 to 18, 21 to 28, and 31 to • L2MOTR-shelf-slot for L2 MOTR
38 for 32-slot shelf, 1 to 7 for 7-slot shelf, circuit packs
and 1 to 2 for 2-slot shelf]
• L2RPR-shelf-slot for RPR circuit
• L2RPR-[1 to 254]-[1 to 6, 9 to 14 for 14-slot packs
shelf and 1 to 8, 11 to 18, 21 to 28, and 31
to 38 for 32-slot shelf]

Table 2-45
Virtual Circuit Service Activation task (VCE parameters) (continued)
Port • ETH (LAN) ports (L2SS, RPR, and PDH Sets the port number of the selected
gateway): slot in the format:
ETH-[1 to 254]-[1 to 6, 9 to 14 for 14-slot facility-shelf-slot-port
to 38 for 32-slot shelf]-[1 to 4]
• ETH or ETH100 (LAN) ports (20G L2SS):
ETH or ETH100-[1 to 254]-[1 to 6, 9 to 14
for 14-slot shelf and 1 to 8, 11 to 18, 21 to
28, and 31 to 38 for 32-slot shelf]-[3 to 10],
[41 to 52], or [71 to 74]
• ETH or ETH100 (LAN) ports (L2 MOTR):
ETH or ETH100-[1 to 254]-[1 to 6 for
6500-7 packet-optical shelf, 1 to 14 for
14-slot shelf, 1 to 8, 11 to 18, 21 to 28, and
31 to 38 for 32-slot shelf, 1 to 7 for 7-slot
shelf, and 1 to 2 for 2-slot shelf]-[3 to 12]
• ETH10G (LAN) ports (20G L2SS):
ETH10G-[1 to 254]-[1 to 6, 9 to 14 for
14-slot shelf and 1 to 8, 11 to 18, 21 to 28,
and 31 to 38 for 32-slot shelf]-[1 or 2]
• ETH10G (LAN) ports (L2 MOTR):
ETH10G-[1 to 254]-[1 to 6 for 6500-7
packet-optical shelf, 1 to 14 for 14-slot
shelf, 1 to 8, 11 to 18, 21 to 28, and 31 to
38 for 32-slot shelf, 1 to 7 for 7-slot shelf,
and 1 to 2 for 2-slot shelf]-[1 or 2]
• WAN ports (L2SS):
WAN-[1 to 254]-[1 to 6, 9 to 14 for 14-slot

Table 2-45
Port (continued) • WAN ports (20G L2SS, and PDH gateway): Sets the port number of the selected
WAN-[1 to 254]-[1 to 6, 9 to 14 for 14-slot slot in the format:
shelf and 1 to 8, 11 to 18, 21 to 28, and 31 facility-shelf-slot-port
• WAN ports (RPR):
WAN-[1 to 254]-[1 to 6, 9 to 14 for 14-slot
• LAG ports (L2SS and RPR):
LAG-[1 to 254]-[1 to 6, 9 to 14 for 14-slot
• LAG ports (PDH gateway):
• LAG ports (20G L2SS):
• LAG ports (L2 MOTR):
LAG-[1 to 254]-[1 to 6 for 6500-7
shelf, 1 to 8, 11 to 18, 21 to 28, and 31 to
38 for 32-slot shelf, 1 to 7 for 7-slot shelf,
and 1 to 2 for
• RPR ports (RPR):
RPR-[1 to 254]-[1 to 6, 9 to 14 for 14-slot
to 38 for 32-slot shelf]-[801 or 802]
Interface type • NNI Displays the interface type for the

• UNI VCE. Read-only.
State • IS (default) Sets the primary state of the VCE.

• OOS

Table 2-45
Receive Class of • 0: Use Port (default for L2SS, PDH Sets the receive class of service.
Service gateway, L2 MOTR, and 20G L2SS circuit The receive class of service
packs and also RPR circuit packs on an specifies a profile which maps the
NNI port) pbits and CFI in the incoming
• 1: Pbits+CFI Mapping packets for this service into a class
of service and a color.
• 2: Pbits+CFI(0) Mapping
For the 20G L2SS and L2 MOTR
• 26: Pbits+CFI Ind Cust-S circuit packs, profiles with mappings
• 27: Pbits+CFI Ind Cust-O to Discard are not valid.
• 28: Pbits+CFI 5CoS-0xff For RPR circuit packs on an NNI
• 29: Pbits+CFI 5Cos 1Clr (default for RPR port, the only acceptable value is 0:
circuit packs on a UNI port) Use Port.
• 30: Pbits+CFI 8CoS 2Clr For RPR circuit packs on a UNI port,
the only acceptable mappings of the
• 31: All Premium Green profile are 1 (standard), 4, 5 (silver),
• User-provisioned profiles 6, 7 (gold), 10, 11 (premium), 14 and
Note: Profiles with numbers 1000 or above 15 (critical), also the RX values for
the same pbit (RX2 and RX3, ...,
will also be available on retrievals. Profiles
RX14 and RX15) must be the same
with numbers 1000 or above represent the
COS. For example If RX2=5, then
old settings for Customer CoS to Provider
RX3 must be either 4 or 5 (both
CoS mappings. silver COS). The mappings must be
only to classes of service specified
in the VCS class of service field for
the RPR circuit pack on a UNI port.
For L2 MOTR circuit packs, the only
acceptable value is 0: Use Port.
Transmit Class of • 0: Use Port (default) Sets the transmit class of service.
Service • 1: Pbits+CFI Mapping The transmit class of service
specifies a profile which maps the
• 2: Pbits+CFI(0) Mapping class of service and color into a pbit
• 26: Pbits+CFI Ind Cust-S and CFI when a tag is added to the
• 27: Pbits+CFI Ind Cust-O packet or when the packet priority is
modified with option COS Profile.
• 28: Pbits+CFI 5CoS-0xff
For 20G L2SS circuit packs, profiles
• 29: Pbits+CFI 5Cos 1Clr with mappings to Discard are not
• 30: Pbits+CFI 8CoS 2Clr valid.
• User-provisioned profiles For RPR circuit packs, the only
For L2 MOTR circuit packs, the only

Table 2-45
Detailed OM Stats • Enabled Specifies whether the operational

• Disabled (default) measurements are enabled or
disabled for the virtual circuit
endpoints. Only 100 endpoints can
have OM statistics enabled
(including both VCEs and TNEs)
except for L2 MOTR circuit packs
where only 5 endpoints with detailed
OM stats enabled are supported.
Distribution • Disable (default) Sets the user overriding distribution

Algorithm • Preferred Member algorithm as either disabled or
preferred member on the RPR ring.
This parameter only applies to RPR
ports (801 and 802) on the RPR
circuit packs.
Note: You must put the Distribution
Algorithm parameter to Disable
before making any changes to the
WAN or any other layer 1 data. After
the changes are made to WAN or
any other layer 1 data, you can then
set the Distribution Algorithm
parameter to Preferred Member if
needed.
For more information about
Distribution Algorithm, refer to the
6500 Packet-Optical Platform Data

Table 2-45
Distribution • WAN ports (RPR circuit packs only) Sets the port number of the
parameter • WAN-[1 to 254]-[1 to 6, 9 to 14 for 14-slot preferred member where the traffic
shelf and 1 to 8, 11 to 18, 21 to 28, and is routed on the RPR ring.
31 to 38 for 32-slot shelf]-[101 to 104] The preferred member on RPR is
the primary path that traffic will
follow on the ring. The format is:
facility-shelf-slot-port
circuit packs.
When the Distribution Algorithm is
disable, this parameter is grayed
out.
Distribution • Enable (default) Specifies whether the preferred

Protection • Disable member has protection enabled or
disabled for the RPR ring.
When set to disable, the VCE is not
protected if the primary path fails.
When set to enable, the VCE under
a failure is routed to the secondary
path on the ring.
circuit packs.
This parameter is only settable to
disable when the Distribution
Algorithm is set to Preferred
Member.

Table 2-45
Bandwidth Profiles Index: Profile name Sets the bandwidth profile for a class
Setup (Critical of service in the VCE.
Profile, Network RPR ports (801 and 802) and NNI
Profile, Premium Ethernet ports on RPR circuit packs
Profile, Platinum cannot have bandwidth profiles and
Profile, Gold the profiles are therefore grayed out.
Profile, Silver Also, UNI Ethernet ports on RPR
Profile, Bronze circuit packs do not support Network
Profile, Standard profile, Platinum profile, and Bronze
Profile) profile.
For L2 MOTR circuit packs in
“L2EXTENDED” mode, the only
supported bandwidth profile is
“0:Not Policed”.

Read-only

Table 2-46
Virtual Circuit Service Activation task (VCE endpoint map parameters)
Virtual circuit VCE-[1 to 254]-[1 to 6, 9 to 14 for Displays the name of the endpoint map. This
endpoint 14-slot shelf and 1 to 8, 11 to 18, attribute appears in the following format:
21 to 28, and 31 to 38 for 32-slot VCE-shelf-slot-port-virtual circuit ID. Read-only.
shelf]-port-[1 to 1048575] for all
circuit packs except L2 MOTR
circuit pack
VCE-[1 to 254]-[1 to 6 for 6500-7
packet-optical shelf, 1 to 14 for
14-slot shelf, 1 to 8, 11 to 18, 21 to
28, and 31 to 38 for 32-slot shelf,
1 to 7 for 7-slot shelf, and 1 to 2 for
2-slot shelf]-port-[1 to 1048575] for
L2 MOTR circuit pack
where port is
• [1 to 4] for ETH (LAN) ports
(L2SS, RPR, and PDH gateway)
• [3 to 10], [41 to 52], or
[71 to 74] for ETH or ETH100
(LAN) ports (20G L2SS)
• [3 to 12] for ETH (LAN) or
ETH100 ports (L2 MOTR)
• [1 or 2] for ETH10G (LAN) ports
(20G L2SS and L2 MOTR)
• [101 to 164] for WAN ports
(L2SS)
• [101 to 228] for WAN ports (PDH
gateway and 20G L2SS)
• [101 to 104] for WAN ports (RPR)
• [401 to 404] for LAG ports
(L2SS and RPR)
(PDH gateway)
(20G L2SS)
(L2 MOTR)
• [801 or 802] for RPR ports (RPR)
Mapping ID 0 to 4098 Sets the mapping ID of the endpoint map.

(0-4098)

Table 2-46
Virtual Circuit Service Activation task (VCE endpoint map parameters) (continued)
Direction For UNI ports Sets the direction to which the endpoint map
• Rx (default) applies. The direction should be Rx for ingress
and Tx for egress endpoint maps.
• Tx
Note: When a tag is added to the frame (all
For NNI ports TxADDRXDEL maps and Tx maps with an Action
• TXADDRXDEL to Add), the packets will have the EtherType
No TX mapping is allowed for L2 specified by the map.
MOTR circuit packs.
Access Rx Sets whether the endpoint map is allowed or

• Allow (default) filtered.
• Filter Filtering is not supported in the Tx and

TXADDRXDEL directions.
Tx and TXADDRXDEL
• Allow
etherType TXADDRXDEL only Sets Ether Type value. The Ether Type specifies
• 0 : Use Port the Ether Type to be used when a tag is added to
the packet (a tag is always added in the NNI
• 0X8100 ports; a tag is added on the UNI ports if there is
• 0X9100 an action to add a tag).
• 0X88A8 When etherType is 0, it means you must use the
For L2 MOTR circuit packs, only “0 etherType configured on the port.
: Use Port” value is supported for
ether Type.
Tags To Match Tx and Rx only Sets if single (outer) or double (outer and inner)
• Outer VLAN tags classification should be used.
• Outer and inner Not supported for RPR. Only supports single
(outer) for L2 MOTR.
Remote Tags To Tx only Sets the number of remote tags to delete when
Delete • None (default) creating a VCEMAP from the Endpoint
Management application. This is for the Tx
• Outer direction only.
Not supported for RPR and L2 MOTR.

Table 2-46
Outer Remote Tag Tx only Sets the outer remote VLAN ID expected from
• All untagged frames the far-end equipment. This is for the Tx direction
only.
• All unprovisioned tagged frames
(L2SS/20G L2SS/PDH only) You can set a specific tag by selecting the
Specific tag radio button and selecting an unused
• Specific tag (0-4095 for ID (0- 4095) or select one of the other radio
L2SS/20G L2SS/PDH) buttons:
For RPR the only valid value is: • All untagged frames (L2SS/20G L2SS/PDH
• All untagged and tagged frames only)
• All untagged and tagged frames (RPR only)
(L2SS/20G L2SS/PDH only)
If the outer remote tag is All untagged, All tagged
and untagged, or All tagged, then Tags to Match
must be set to outer.
Inner Remote Tag Tx only Sets the inner remote VLAN ID expected from
• All untagged frames the far-end equipment (L2SS, 20G L2SS, and
PDH Gateway circuit packs only). This is for the
• All unprovisioned tagged frames Tx direction only.
(L2SS/PDH only)
You can set a specific tag by selecting the
• Specific tag (0-4095) Specific tag radio button and selecting unused ID
Not valid for RPR and L2 MOTR (0-4095) or select one of the radio buttons:
• All untagged frames
• All unprovisioned tagged frames (L2SS/PDH
only). 20G L2SS circuit pack does not support
“All unprovisioned tagged frames”.

Table 2-46
Outer Local Tag Rx Sets the outer local VLAN ID you are mapping.
• All untagged frames You can set a specific tag by selecting the
• All unprovisioned tagged frames Specific tag radio button and selecting unused ID
(L2SS/20G L2SS/PDH/L2 MOTR (0-4095) or select one of the radio buttons:
only) • All untagged frames
• All tagged and untagged frames • All tagged and untagged frames (RPR only)
(RPR only) • All unprovisioned tagged frames (L2SS/20G
• Specific tag (0-4095) L2SS/PDH only/L2 MOTR)
If the Outer remote tag is all untagged, all tagged
Tx and untagged, or all tagged, then tags to match
must be set to outer
• Specific Tag (0-4095)
Only valid if inner local customer tag action is
Not supported for L2 MOTR add.
Set a specific tag by selecting an ID (0-4095).
TXADDRXDEL
• Specific Tag (0-4095)
L2 MOTR only supports 1 to 4094
when L2 MOTR is in
“STANDARD” mode and 1 to 2000
when L2 MOTR is in
“L2EXTENDED” mode
Outer Local Tag Tx only Sets the outer local tag action to be taken.
Action • Nothing • If the outer tag action is set to Nothing, the inner
• Add local tag action cannot be set to add (it can be
set to Nothing or Modify priority) if allowed.
• Modify priority
• The Add action adds a tag with the VLAN ID
RPR only supports “Add” specified in the attribute Outer local tag. The
priority that should be used in the tag is
described by the attribute priority source.
• The Modify priority action modifies the priority
of the outer most tag based on the action
described by the attribute priority source. The
VLAN ID is not modified.

Table 2-46
Outer Local Tag Tx only Sets the outer local priority source.
Priority Source • Remote outer tag This attribute is only used when the Outer local
• Remote inner tag tag action is set to Add or Modify priority. It is not
used if the Outer local tag action is set to Nothing.
• Explicit
• Remote outer tag. You can copy the priority
• Use class of service profile including CFI/DE from the received outer
RPR only supports "Remote outer customer frame before any tags have been
customer priority source” deleted as defined by the parameter "Remote
Tags to Delete".
• Remote inner tag. You can copy the priority
including CFI/DE from the received inner
customer frame before any tags have been
deleted as defined by the parameter "Remote
Tags to Delete".
• Explicit sets the total value of pbit+cfi (0-15)
allowing the user to select the CFI. (3 bits for
pbit + 1 bit for CFI).
• Use class of service profile sets the priority in
the outer tag to a value that is dependent on the
class of service of the frame using the transmit
class of service profile that is configured at the
VCE to map the class of service to Pbit/CFI
value.
Outer Local Tag Tx only Sets the outer local explicit priority.
Priority • 0-15 The menu goes from 0 to 15, allowing the user to
Not supported for RPR select the CFI. (3 bits for pbit + 1 bit for CFI)
This attribute is only used when the Outer Local
Priority Source is set to Explicit. In this case it
specifies the priority to be set in the frame’s outer
tag.
Outer Local only for Tx direction Sets the outer local etherType tag. The
etherType Tag • 0 : Use Port etherType specifies the Ether Type to be used
when a tag is added to the packet (a tag is always
• 0X8100 added in the NNI ports; a tag is added on the UNI
• 0X9100 ports if there is an action to add a tag). When
• 0X88A8 etherType is 0, it means you must use the
etherType configured on the port.
This attribute is only used when the Outer local
tag action is set to Add. It is not used if the Outer
local tag action is set to Nothing or Modify
priority.

Table 2-46
Inner Local Tag Rx Sets the inner local VLAN ID you are mapping.
• All untagged frames Only valid if tags to match is inner and outer.
• All unprovisioned tagged frames You can set a specific tag by selecting the
(L2SS/20G L2SS/PDH only) Specific tag radio button and selecting an unused
• Specific tag (0-4095) ID (0-4095) or select one of the radio buttons:
• All untagged frames
Tx Only valid if inner local customer tag action is

“Add”
• Specific tag (0-4095)
You can set a specific tag by selecting an ID
(0-4095)
Not supported for RPR.
Inner Local Tag Tx only: Sets the inner local tag action to be taken.
Action • Nothing • If the outer tag action is set to Nothing or Modify
• Add priority, the inner local tag action cannot be set
to add (it can be set to Nothing or Modify
• Modify priority priority) if allowed.
Not supported by RPR • Add action adds a tag with the VLAN ID
specified in the attribute Inner local tag. The
priority that should be used in the tag is
described by the attribute priority source.
• Modify priority action modifies the priority of the
inner most tag based on the action described by
the attribute priority source. The VLAN ID is not
modified.

Table 2-46
Inner Local Priority Tx only Sets the inner local priority source.
Source • Remote outer tag This attribute is only used when the inner local
• Remote inner tag tag action is set to Add or Modify priority. It is not
used if the inner local tag action is set to Nothing.
• Explicit
• Remote outer tag. You can copy the priority
• Use class of service profile including CFI/DE from the received outer
Not supported for RPR customer frame before any tags have been
Tags to Delete".
• Remote inner tag. You can copy the priority
including CFI/DE from the received inner
customer frame before any tags have been
Tags to Delete".
• Explicit sets the priority in the outer tag to the
specific value. The value ranges from 0 to 15
(3 bits for pbit concatenated with 1 CFI bit)
• Use class of service profile sets the priority in
the inner tag to a value that is dependent on the
class of service of the frame using the receive
class of service profile that is configured at the
VCE to map the class of service to Pbit/CFI
value.
Inner Local Priority Tx only Sets the inner local explicit priority.
• 0-15 This attribute is only used when the inner local
Not supported for RPR priority source is set to Explicit. In this case it
specifies the priority to be set in the frame’s inner
tag.

Table 2-46
Inner Local Tx only Sets the inner local etherType tag. The
etherType Tag • 0 : Use Port etherType specifies the Ether Type to be used
when the Tx VCEMAP has an Inner Local Tag
• 0X8100 Action of Add. When etherType is 0, it means you
• 0X9100 must use the etherType configured on the port.
• 0X88A8 This attribute is only used when the inner local
Not supported for RPR tag action is set to Add. It is not used if the inner
local tag action is set to Nothing or Modify
priority.
Rx Priority Source Rx only Identifies if the pbits used to classify the traffic
• Outer local tag flow will be from the inner or outer VLAN tag.
• Inner local tag RPR supports only outer local tag.
Priority Bits Rx Only The priorities to be allowed into a specific

Bit mask of priorities endpoint for a given customer VLAN.
If tags to match is outer and inner, all priorities for
a given priority must be selected.
For 20G L2SS and L2 MOTR circuit packs, you
must check all check boxes in Priority Bits area.

Ring parameters in a G.8032 ERP

Table 2-47 details the parameters associated with ring provisioning in a
G.8032 ERP. The fields appear as displayed on the Ring Provisioning tab.
However, the definitions also apply to the corresponding fields on the Add
Ring and Edit Ring dialogs.
Table 2-47
Filter criteria and ring parameters in a G.8032 ERP
Slot • 1 to 6 or 9 to 14 for 14-slot Select the slot number of the 20G L2SS or
shelf and 1-8, 11-18, L2 MOTR circuit pack.
21-28, and 31-38 for
32-slot shelf (20G L2SS)
• 1 to 6 for 6500-7
packet-optical shelf, 1 to 14
for
14-slot shelf, 1-8, 11-18,
21-28, 31-38 for 32-slot
shelf, 1 to 7 for 7-slot shelf,
and 1 to 2 for 2-slot shelf
(L2 MOTR)
Ring ID • 1 to 255 Selects the ring ID for the ring.

• All The ring ID creates the association between the
ring and its ringlets.
Only the last five entered ring IDs plus the All
option appear in the drop-down list.
Equipment 20GL2SS-[1 to 254]-[1 to 6, Selects a G.8032 ERP-capable circuit pack

9 to 14 for 14-slot shelf and 1 (20G L2SS or L2 MOTR). The first available
to 8, 11 to 18, 21 to 28, and 20G L2SS or L2 MOTR circuit pack with a
31 to 38 for 32-slot shelf] provisioned port is shown in the format:
(20G L2SS) 20GL2SS-shelf-slot, or
L2MOTR-[1 to 254]-[1 to 6 L2MOTR-shelf-slot
for 6500-7 packet-optical
shelf, 1 to 14 for 14-slot
shelf,
1-8, 11-18, 21-28, 31-38 for
32-slot shelf, 1 to 7 for 7-slot
shelf, and 1 to 2 for 2-slot
shelf] (L2 MOTR)

Table 2-47
Filter criteria and ring parameters in a G.8032 ERP (continued)
Name • RNS-[1 to 254]-[1 to 6 and Displays the name of the ring. This attribute has
9 to 14 for 14-slot shelf and the following format:
1-8, 11-18, 21-28, and RNS-shelf-slot-ring ID. Read-only.
31-38 for 32-slot shelf]-[1 to
255] (20G L2SS)
• RNS-[1 to 254]-[1 to 6 for
shelf, 1-8, 11-18, 21-28,
31-38 for 32-slot shelf, 1 to
7 for 7-slot shelf, and 1 to 2
for 2-slot shelf]-[1 to 255]
(L2 MOTR)
Guard Time 10 to 2000 (milliseconds) in Selects the guard time for the ring. The guard time
(milliseconds) 10 ms increments is used by the nodes adjacent to a failure as the
length of time (in milliseconds) that the nodes will
ignore any R-APS message after noticing the
cause of the failure has been removed. The guard
time is part of the mechanism to avoid protection
oscillation.
Without the guard time attribute, after a ring span
recovers from a failure and adjacent nodes detect
the recovery and take action, outdated failure
indication messages might be received on nodes
that just recovered. This results in channel block
removal on the recovered ring span while the ring
is still in a wait-to-restore state (that is, the RPL
owner would not be blocked). In such a case, there
would be no channel block set around the ring,
creating a loop and generating a broadcast storm.
The guard time must be minimally two times the
round trip delay of R-APS messages.

Table 2-47
Filter criteria and ring parameters in a G.8032 ERP (continued)
Wait To Restore • 10 to 720 (seconds) in 10 Selects the wait to restore time for the ring. The
Time (seconds) seconds increments wait to restore time is used by the RPL owners as
• Infinite the time in seconds between receiving
R-APS(RIM) and installing the RPL block and
transmitting R-APS(OK). Wait to restore time is
part of the mechanism to avoid protection
oscillation.
• If you select a value for the wait to restore time,
then the node becomes revertive.
• If you select “Infinite” for the wait to restore time,
then the node becomes non-revertive. To make
a ring non-revertive, this setting must be at the
node with the RPL owner. For proper operation of
a non-revertive ring, the wait to restore time on all
nodes on the ring be infinite.
Editing between revertive and non-revertive can
be done in-service.
This release supports infinite wait to restore time
(non-revertive) for L2 MOTR circuit packs.
However if you want to use infinite wait to restore
time (non-revertive) for other Layer 2 circuit
packs, you must contact your Ciena
representative.
Ring • RNS-[1 to 254]-[1 to 6 and Displays the ring. This attribute has the following
9 to 14 for 14-slot shelf and format:
1-8, 11-18, 21-28, and RNS-shelf-slot-ring ID.
255] (20G L2SS)
• RNS-[1 to 254]-[1 to 6 for
shelf,
1-8, 11-18, 21-28, 31-38 for
32-slot shelf, 1 to 7 for
7-slot shelf, and 1 to 2 for
(L2 MOTR)

Ring port parameters in a G.8032 ERP

Table 2-48 details the parameters associated with ring port provisioning in a
G.8032 ERP. The fields appear as displayed on the Ring Port Provisioning tab.
Ring Port and Edit Ring Port dialogs.
Table 2-48
Ring port parameters in a G.8032 ERP
Slot • 20G L2SS circuit packs Select the slot number of the 20G L2SS or
— 1 to 6 or 9 to 14 for 14-slot L2 MOTR circuit pack.
shelf
— 1-8, 11-18, 21-28, and
• L2 MOTR circuit packs
— 1 to 2 for 2-slot shelf
— 1 to 6 for 6500-7
packet-optical shelf
— 1-8, 11-18, 21-28, and
Port • 3 to 10, 41 to 52, or 71 to 74 for Select the port number of the selected slot.
ETH or ETH100 (LAN) ports
(20G L2SS)
• 3 to 12 for ETH or ETH100
(LAN) ports (L2 MOTR)
• 1 or 2 for ETH10G (LAN) ports
• 101 to 228 for WAN ports
(20G L2SS)
• 401 to 408 for LAG ports (20G
L2SS)
• 403 to 412 for LAG ports
(L2 MOTR)
• All

Table 2-48
Ring port parameters in a G.8032 ERP (continued)

Equipment 20GL2SS-[1 to 254]-[1 to 6, 9 to Selects a G.8032 ERP-capable circuit pack

14 for 14-slot shelf and 1 to 8, (20G L2SS or L2 MOTR). The first available
11 to 18, 21 to 28, and 31 to 38 20G L2SS or L2 MOTR circuit pack with a
for 32-slot shelf] provisioned port is shown in the format:
L2MOTR-[1 to 254]-[1 to 6 for L2MOTR-shelf-slot
6500-7 packet-optical shelf, 1 to
14 for 14-slot shelf,
1-8, 11-18, 21-28, 31-38 for
32-slot shelf,
1 to 7 for 7-slot shelf, 1 to 2 for
2-slot shelf] (L2 MOTR)

Table 2-48
Facility • WAN ports (20G L2SS): Sets the facility of the circuit pack to associate a
WAN-[1 to 254]-[1 to 6, 9 to 14 ring to a port.
for 14-slot shelf and The format is:
1 to 8, 11 to 18, 21 to 28, and
31 to 38 for 32-slot shelf]-[101 facility-shelf-slot-port
to 228]
LAG-[1 to 254]-[1 to 6, 9 to 14
for 14-slot shelf and
1 to 8, 11 to 18, 21 to 28, and
31 to 38 for 32-slot shelf]-[401
to 408]
LAG-[1 to 254]-[1 to 6 for
6500-7 packet-optical shelf, 1
to 14 for 14-slot shelf,
1-8, 11-18, 21-28, 31-38 for
shelf]-[403 to 412]
• ETH or ETH100 (LAN) ports
(20G L2SS):
ETH or ETH100-[1 to 254]-[1
to 6, 9 to 14 for 14-slot shelf
and
1 to 8, 11 to 18, 21 to 28, and
31 to 38 for 32-slot shelf]-[3 to
10], [41 to 52], or [71 to 74]

Table 2-48
Facility • ETH or ETH100 (LAN) ports Sets the facility of the circuit pack to associate a
(continued) (L2 MOTR): ring to a port.
ETH or ETH100-[1 to 254]-[1 The format is: facility-shelf-slot-port
to 6 for 6500-7 packet-optical
and
1-8, 11-18, 21-28, 31-38 for
32-slot shelf,
1 to 7 for 7-slot shelf,
1 to 2 for 2-slot shelf]-[3 to 12]
• ETH10G (LAN) ports
(20G L2SS):
ETH10G-[1 to 254]-[1 to 6, 9
to 14 for 14-slot shelf and
1 to 8, 11 to 18, 21 to 28, and
31 to 38 for 32-slot shelf]-[1 or
2]
(L2 MOTR):
ETH10G-[1 to 254]-[1 to 6 for
to 14 for 14-slot shelf, and
1-8, 11-18, 21-28, 31-38 for
32-slot shelf,
1 to 2 for 2-slot shelf]-[1 or 2]
Ring • RNS-[1 to 254]-[1 to 6 and 9 to Sets the ring. All rings provisioned on the
14 for 14-slot shelf and selected Equipment will be available in the
1-8, 11-18, 21-28, and 31-38 drop-down list. This attribute has the following
for 32-slot shelf]-[1 to 255] format:
(20G L2SS) RNS-shelf-slot-ring ID.
• RNS-[1 to 254]-[1 to 6 for
1-8, 11-18, 21-28, 31-38 for
32-slot shelf,
255]
(L2 MOTR)

Table 2-48
Name • RNE-[1 to 254]-[1 to 6 and 9 to Displays the name of the ring port. This attribute
14 for 14-slot shelf and has the following format:
1-8, 11-18, 21-28, and 31-38 RNE-shelf-slot-port-ring ID. Read-only.
for 32-slot shelf]-[Port][1 to
255]
(20G L2SS)
• RNE-[1 to 254]-[1 to 6 for
1-8, 11-18, 21-28, 31-38 for
32-slot shelf,
1 to 2 for 2-slot shelf]-[Port][1
to 255]
(L2 MOTR)
where [Port] is:
• 3 to 10, 41 to 52, or 71 to 74 for
ETH or ETH100 (LAN) ports
(20G L2SS)
• 3 to 12 for ETH or ETH100
(LAN) ports (L2 MOTR)
• 101 to 228 for WAN ports
(20G L2SS)
(20G L2SS)
(L2 MOTR)
Hold Off Time 0 to 10000 (milliseconds) in Sets the hold off time. The hold off time is used
100 ms increments by the nodes that detect a failure as the length of
time (in milliseconds) between noticing a failure
and reporting the failure. This field is useful if
there is another protection mechanism in place.
The hold off time gives this other protection
mechanism a chance to correct the failure.

Table 2-48
MEP • MEP-[1 to 254]-[1 to 6 for Sets a pre-provisioned “Down” or “Port”

6500-7 packet-optical shelf, 1 maintenance end point (MEP). This attribute has
to 14 for 14-slot shelf, the following format:
1-8, 11-18, 21-28, 31-38 for MEP-shelf-slot-MD ID-MA ID-MEP ID.
32-slot shelf, If no “Down” or “Port” MEP is pre-provisioned,
1 to 7 for 7-slot shelf, only the “NONE” option can be selected.
7]-[1 to 1048575]-[1 to 8191] This parameter is used to trigger G.8032
protection based on loss of 802.1ag CCM
• NONE-[1 to 254] messages. You must note that if the MEP is
alarmed (down), the ring port will be considered
as down as well and the G.8032 ring will remain
in protected state until the MEP goes up. Ensure
the MEP is UP before linking to the G.8032 ring
port to simplify the G.8032 configuration.
This parameter is only applicable to L2 MOTR
circuit packs.

Ringlet parameters in a G.8032 ERP

Table 2-49 details the parameters associated with ringlet provisioning in a
G.8032 ERP. The fields appear as displayed on the Ringlet Provisioning tab.
Ringlet and Edit Ringlet dialogs.
Table 2-49
Filter criteria and ringlet parameters in a G.8032 ERP
Slot • 1 to 6 or 9 to 14 for 14-slot Select the slot number of the 20G L2SS or
shelf and L2 MOTR circuit pack.
1-8, 11-18, 21-28, and
31-38 for 32-slot shelf (20G
L2SS)
• 1 to 6 for 6500-7
packet-optical shelf, 1 to 14
for
14-slot shelf, 1-8, 11-18,
21-28, 31-38 for 32-slot
and 1 to 2 for 2-slot shelf
(L2 MOTR)

Group ID • 1 to 256 Selects the group ID for the ringlet.

• All A group represents a collection of services that will
be treated the same way by the G.8032 ERP
control protocol. The group ID, in conjunction with
the ring ID, is used to identify the ringlet.
Only the last five entered group IDs plus the All

Table 2-49
Filter criteria and ringlet parameters in a G.8032 ERP (continued)
Equipment 20GL2SS-[1 to 254]-[1 to 6, Selects a G.8032 ERP-capable circuit pack

9 to 14 for 14-slot shelf and 1 (20G L2SS or L2 MOTR). The first available
to 8, 11 to 18, 21 to 28, and 20G L2SS or L2 MOTR circuit pack with a
31 to 38 for 32-slot shelf] provisioned port is shown in the format:
L2MOTR-[1 to 254]-[1 to 6 L2MOTR-shelf-slot
for 6500-7 packet-optical
shelf,
1-8, 11-18, 21-28, 31-38 for
shelf] (L2 MOTR)
Ring • RNS-[1 to 254]-[1 to 6 and Sets the ring. All rings provisioned on the selected
9 to 14 for 14-slot shelf and Equipment will be available in the drop-down list.
1-8, 11-18, 21-28, and This attribute has the following format:
31-38 for 32-slot shelf]-[1 to RNS-shelf-slot-ring ID.
255] (20G L2SS)
• RNS-[1 to 254]-[1 to 6 for
shelf,
1-8, 11-18, 21-28, 31-38 for
(L2 MOTR)
Name • RLS-[1 to 254]-[1 to 6 and 9 Displays the name of the ringlet. This attribute has
to 14 for 14-slot shelf and the following format:
1-8, 11-18, 21-28, and RLS-shelf-slot-ring ID-group ID. Read-only.
255]-[1 to 256] (20G L2SS)
• RLS-[1 to 254]-[1 to 6 for
shelf, 1-8, 11-18, 21-28,
31-38 for 32-slot shelf, 1 to
7 for 7-slot shelf, and 1 to 2
for 2-slot shelf]-[1 to 255]-[1
to 256] (L2 MOTR)

Table 2-49
APS VID 1 to 4094 Selects the APS VID of the ringlet.

This is the VID that will be used by the R-APS
messages on the ringlet. APS VID must be a VID
not used by any service (VCS, TNS) on the ring
ports of the ring. It must also be a VID not used as
an APS VID by any other ringlet on the same ring
(the combination Ring ID and APS VID must be
unique on the port).
APS Type • Major Ring Selects the APS type of the ringlet.
• Sub Ring APS type indicates whether or not the ringlet is an
enclosed loop. A major-ring is a ringlet with
enclosed loop topology. A sub-ring is a ringlet with
an open topology.
State • Initializing Displays the state of the ringlet.

• Idle Initializing: indicates that the node is either being
• Protected added, newly added to the G.8032 ERP, or the
node is coming out of a cold state.
• Pending
Idle: indicates that the node perceives the G.8032
• Unknown ERP to be in a closed state.
Protected: indicates that the node perceives the
G.8032 ERP to be in an open state.
Pending: indicates that the node is attempting to
close the G.8032 ERP.
Unknown: unable to retrieve the information from
the node at this time.
Note that State is operational information that is
not updated automatically. The Refresh button
must be used to see the current view.
RPL Port • None Selects the RPL port of the ring.

• a reference to one of the One of the ports on the ringlet will be provisioned
two ring ports on the node as the RPL port. The RPL port will block all traffic
for services (VCSs) assigned to the ringlet. This is
to prevent traffic from looping around the ring. In
the event of a failure, this block will be lifted to
provide a backup path for the traffic.

Table 2-49
Ringlet • RLS-[1 to 254]-[1 to 6 and 9 Displays the ringlet. This attribute has the
to 14 for 14-slot shelf and following format:
1-8, 11-18, 21-28, and RLS-shelf-slot-ring ID-group ID.
255]-[1 to 256] (20G L2SS)
• RLS-[1 to 254]-[1 to 6 for
shelf,
1-8, 11-18, 21-28, 31-38 for
2-slot shelf]-[1 to 255]-[1 to
256] (L2 MOTR)

Ringlet port parameters in a G.8032 ERP

Table 2-50 details the parameters associated with ringlet port provisioning in
a G.8032 ERP. The fields appear as displayed on the Ringlet Port Provisioning
tab. However, the definitions also apply to the corresponding fields on the Add
Ringlet Port and Edit Ringlet Port dialogs.
Table 2-50
Ringlet port parameters in a G.8032 ERP

Read-only.
Slot • 20G L2SS circuit packs Select the slot number of the
— 1 to 6 or 9 to 14 for 14-slot shelf 20G L2SS or
L2 MOTR circuit pack.
— 1-8, 11-18, 21-28, and 31-38 for
32-slot shelf
• L2 MOTR circuit packs
— 1 to 6 for 6500-7 packet-optical shelf
— 1-8, 11-18, 21-28, and 31-38 for
32-slot shelf
Port • 3 to 10, 41 to 52, or 71 to 74 for ETH or Select the port number of the
ETH100 (LAN) ports (20G L2SS) selected slot.
• 3 to 12 for ETH or ETH100 (LAN) ports
(L2 MOTR)
• 101 to 228 for WAN ports (20G L2SS)
• 401 to 408 for LAG ports (20G L2SS)
• 403 to 412 for LAG ports (L2 MOTR)
• All

• All The ring ID creates the association
between the ring and its ringlets.
Only the last five entered ring IDs
plus the All option appear in the
drop-down list.

Table 2-50
Ringlet port parameters in a G.8032 ERP (continued)
Group ID • 1 to 256 Selects the group ID for the ringlet.

• All A group represents a collection of
services that will be treated the same
way by the G.8032 ERP control
protocol. The group ID, in
conjunction with the ring ID, is used
to identify the ringlet.
Only the last five entered group IDs
plus the All option appear in the
drop-down list.
Equipment 20GL2SS-[1 to 254]-[1 to 6, 9 to 14 for Selects a G.8032 ERP-capable

14-slot shelf and circuit pack (20G L2SS or L2 MOTR).
1 to 8, 11 to 18, 21 to 28, and 31 to 38 for The first available 20G L2SS or
32-slot shelf] L2 MOTR circuit pack with a
L2MOTR-[1 to 254]-[1 to 6 for 6500-7 provisioned port is shown in the
packet-optical shelf, 1 to 14 for 14-slot format:
shelf, 1-8, 11-18, 21-28, 31-38 for 32-slot 20GL2SS-shelf-slot, or
shelf, 1 to 7 for 7-slot shelf, and L2MOTR-shelf-slot
1 to 2 for 2-slot shelf]

Table 2-50
Facility • WAN ports (20G L2SS): Sets the facility of the circuit pack to
WAN-[1 to 254]-[1 to 6, 9 to 14 for 14-slot associate a ring to a port.
shelf and The format is:
1 to 8, 11 to 18, 21 to 28, and 31 to 38 for
32-slot shelf]-[101 to 228] facility-shelf-slot-port

shelf and
1 to 8, 11 to 18, 21 to 28, and 31 to 38 for
LAG-[1 to 254]-[1 to 6 for 6500-7
shelf, 1-8, 11-18, 21-28, 31-38 for 32-slot
shelf, 1 to 7 for 7-slot shelf, 1 to 2 for
• ETH or ETH100 (LAN) ports (20G L2SS):
ETH or ETH100-[1 to 254]-[1 to 6, 9 to 14
for 14-slot shelf and
1 to 8, 11 to 18, 21 to 28, and 31 to 38 for
32-slot shelf]-[3 to 10], [41 to 52], or [71 to
74]
• ETH or ETH100 (LAN) ports (L2 MOTR):
ETH or ETH100-[1 to 254]-[1 to 6 for
6500-7 packet-optical shelf, 1 to 14 for
14-slot shelf,
1-8, 11-18, 21-28, 31-38 for 32-slot shelf,
(20G L2SS):
ETH10G-[1 to 6]-[1 to 6, 9 to 14 for 14-slot
shelf and
1 to 8, 11 to 18, 21 to 28, and 31 to 38 for
32-slot shelf]-[1 or 2]
(L2 MOTR):
ETH10G-[1 to 254]-[1 to 6 for 6500-7
shelf,
1-8, 11-18, 21-28, 31-38 for 32-slot shelf,
1 to 2 for 2-slot shelf]-[1 or 2]

Table 2-50
Ring • RNS-[1 to 254]-[1 to 6 and 9 to 14 for Sets the ring. This attribute has the
14-slot shelf and following format:
1-8, 11-18, 21-28, and 31-38 for 32-slot RNS-shelf-slot-ring ID.
shelf]-[1 to 255] (20G L2SS)
• RNS-[1 to 254]-[1 to 6 for 6500-7
shelf,
1-8, 11-18, 21-28, 31-38 for 32-slot shelf,
(L2 MOTR)
Name • RLE-[1 to 254]-[1 to 6 and 9 to 14 for Displays the name of the ringlet. This
14-slot shelf and attribute has the following format:
1-8, 11-18, 21-28, and 31-38 for 32-slot RLE-shelf-slot-port-ring ID-group ID.
shelf]-[Port]-[1 to 255]-[1 to 256] Read-only.
(20G L2SS)
• RLE-[1 to 254]-[1 to 6 for 6500-7
shelf,
1-8, 11-18, 21-28, 31-38 for 32-slot shelf,
1 to 2 for 2-slot shelf]-[Port]-[1 to 255]-[1
to 256]
(L2 MOTR)
where [Port] is:
• 3 to 10, 41 to 52, or 71 to 74 for ETH or
ETH100 (LAN) ports (20G L2SS)
• 3 to 12 for ETH or ETH100 (LAN) ports
(L2 MOTR)
• 101 to 228 for WAN ports (20G L2SS)
• 401 to 408 for LAG ports (20G L2SS)
• 403 to 412 for LAG ports (L2 MOTR)

Table 2-50
APS Role • Tandem Selects the APS role for the ringlet
• Termination port.
This attribute indicates the port role
on the ringlet topology. On a
major-ring ringlet, all ports must have
a tandem role. On a sub-ring ringlet,
the ports adjacent to the open link
must have a termination role and the
other ports must have a tandem role.
Blocked • Blocked Displays whether or not there is a

• NotBlocked block in place for this port.
Note that the Blocked parameter is
operational information that is not
updated automatically. The Refresh
button must be used to see the
current view.
VCE Availability • True Displays whether or not there is a

• False VCE associated to the Group ID. It is
an indication of incorrect
provisioning. It is an important
indication because the control data
may be working fine but the customer
data may not.
Note that the VCE Availability
parameter is operational information
that is not updated automatically.
The Refresh button must be used to
see the current view.
Ringlet Port • RLE-[1 to 254]-[1 to 6 and 9 to 14 for Displays the ringlet port. This
14-slot shelf and attribute has the following format:
1-8, 11-18, 21-28, and 31-38 for 32-slot RLE-shelf-slot-port-ring ID-group ID.
shelf]-[Port]-[1 to 255]-[1 to 256]
(20G L2SS)
• RLE-[1 to 254]-[1 to 6 for 6500-7
shelf,
1-8, 11-18, 21-28, 31-38 for 32-slot shelf,
1 to 2 for 2-slot shelf]-[Port]-[1 to 255]-[1
to 256]
(L2 MOTR)

Path connections parameters

The following tables detail the L2SS, PDH gateway, 20G L2SS, and RPR
circuit pack parameters associated with the Path Connections Site Manager
application.
Table 2-51
Path Connections application parameters for L2SS, PDH gateway, 20G L2SS, and RPR circuit
pack
Connection ID Enter the connection identifier string is used to identify a provisioned path
For connections created by the SONET/SDH Control Plane, the connection
identifier string is assigned a network wide unique identifier, called a Network
Call Correlation Identification (NCCI).
Note: Support for 64 characters connection IDs is only supported from ONM
Release 6.0 onwards.
Rate Select the rate as defined below:
• L2SS, PDH gateway, and 20G L2SS circuit packs: STS1/VC3, STS3c/VC4,
STS12c/VC4-4c, STS24c/VC4-8c, STS48c/VC4-16c
• RPR circuit packs: STS12c/VC4-4c, STS48c/VC4-16c
Type Select the type as defined below:
Refer to Table 2-52 on page 2-287.
From panel Select the Equipment, Facility, and channels for the From connection
endpoints. Refer to Table 2-52 on page 2-287.
ENUT (From panel) For RPR connections, you must enable enhanced non-preemptible unprotected
traffic (ENUT) for the source. You must use ENUT path connections when you
add, drop, or pass through RPR traffic in 2-Fiber BLSR/MS-SPRings.
VT Access Select this checkbox if the path connection is a VT/VC-assigned
BLSR/MS-SPRing connection.
AU3 and/or AU4 For connection rates at VC11, VC12 or VC3 on SDH/SDH-J ports, select the
mapping radio connection mapping as AU3 or AU4 to determine the High Order container.
buttons
Timeslot numbers Each signal type requires that you assign a timeslot number to each parameter
(VT/STS/VC) in that signal type. Enter a time slot number for the STS/VC. For VT1.5 and VT2,
enter a timeslot number for STS, VT Group, and VT. For VC11 and VC12, enter
a timeslot number for AU4 (J), TUG-3 (K), TUG-2 (L), and TU-12/TU-11 (M).
Site Manager automatically populates the available VT/STS/VC parameter
fields when you select the Rate and Type.

Table 2-51
Path Connections application parameters for L2SS, PDH gateway, 20G L2SS, and RPR circuit
pack (continued)
To panel Select the Equipment, Facility, and channels for the To connection endpoints.
Refer to Table 2-52.
ENUT (To panel) For RPR connections, you must enable ENUT for the destination.
Switch Mate panel Select the switch mate when creating 2WAYPR connections. Refer to Table
2-52.
BLSR/MS-SPRing/ Select the starting endpoint (End NE A) and finishing endpoint (End NE Z) of
HERS Endpoints the path for BLSR/MS-SPRing/HERS connections.
panel
Table 2-52
Path connection types for path connections for L2SS, PDH gateway, 20G L2SS, and RPR circuit
packs—supported From and To, Switch Mate instances
Path connection type From, Switch Mate To
2WAY GE WAN GE WAN
2WAYPR Note GE WAN
Note: Layer 2 circuit packs (L2SS, PDH gateway, 20G L2SS, or RPR) cannot be used as From or
Switch Mate endpoints.

Table 2-53
Equipment and facility parameters for path connections for L2SS, PDH gateway, 20G L2SS, and
RPR circuit packs
L2SS circuit packs
STS1/AU3- L2SS-shelf#-slot# WAN-shelf#-slot#-port#- shelf# = 1 to 254

mapped VC3 sts# slot# = 1 to 6 and 9 to 14 for
and WAN-shelf#-slot#-port#- 14-slot shelf
AU4-mapped J#-K# slot# = 1-8, 11-18, 21-28, and
VC3 31-38 for 32-slot shelf
port# = 101 to 164
sts# = 1
J# (AU4) = 1
K# (TUG-3) = 1
STS3c/VC4 L2SS-shelf#-slot# WAN-shelf#-slot#-port#- shelf# = 1 to 254

sts# slot# = 1 to 6 and 9 to 14 for
WAN-shelf#-slot#-port#-J# 14-slot shelf
slot# = 1-8, 11-18, 21-28, and
port# = 101 to 164
sts# = 1
J# (AU4) = 1
STS12c/ L2SS-shelf#-slot# WAN-shelf#-slot#-port#- shelf# = 1 to 254

VC4-4c sts# slot# = 1 to 6 and 9 to 14 for
slot# = 1-8, 11-18, 21-28, and
port# = 101 to 164
sts# = 1
J# (AU4) = 1

slot# = 1-8, 11-18, 21-28, and
port# = 101 to 164
sts# = 1
J# (AU4) = 1

Table 2-53
RPR circuit packs (continued)

slot# = 1-8, 11-18, 21-28, and
port# = 101 to 164
sts# = 1
J# = 1
VT1.5-nv/ L2SS-shelf#-slot# WAN-shelf#-slot#-port#- shelf# = 1 to 254

VC11-nv sts#- slot# = 1 to 6 and 9 to 14 for
(n = 1 to 64) vtg#-vt# 14-slot shelf (except the 14-slot
WAN-shelf#-slot#-port#- packet-optical shelf)
J#-K#- slot# = 1-8, 11-18, 21-28, and
L#-M# 31-38 for 32-slot shelf
port# = 101 to 164
sts# = 1 to 3
vt# = 1 to 4
J# (AU4) = 1
K# (TUG-3) = 1 to 3
M# (TU-11) = 1 to 4

Table 2-53
VT2-nv/ L2SS-shelf#-slot# WAN-shelf#-slot#-port#- shelf# = 1 to 254

(n = 1 to 64) vtg#-vt# 14-slot shelf (except the 14-slot
WAN-shelf#-slot#-port#- packet-optical shelf)
J#-K#- slot# = 1-8, 11-18, 21-28, and
L#-M# 31-38 for 32-slot shelf
port# = 101 to 164
sts# = 1 to 4
vt# = 1 to 3
J# (AU4) = 1 to 2
K# (TUG-3) = 1 to 3
M# (TU-12) = 1 to 3
STS1-nv/ L2SS-shelf#-slot# WAN-shelf#-slot#-port#- shelf# = 1 to 254

AU3 mapped sts# slot# = 1 to 6 and 9 to 14 for
VC3-nv WAN-shelf#-slot#-port#- 14-slot shelf
AU4 mapped J#-K# slot# = 1-8, 11-18, 21-28, and
VC3-nv 31-38 for 32-slot shelf
(n = 1 to 24) port# = 101 to 164
sts# = 1 to 24
J# (AU4) = 1 to 8
K# (TUG-3) = 1 to 3
STS3c-nv/ L2SS-shelf#-slot# WAN-shelf#-slot#-port#- shelf# = 1 to 254

VC4-nv sts# slot# = 1 to 6 and 9 to 14 for
(n = 1 to 8) WAN-shelf#-slot#-port#-J# 14-slot shelf
slot# = 1-8, 11-18, 21-28, and
port# = 101 to 164
sts# = 1, 4, 7, 10, 13, 16, 19, 22
J# (AU4) = 1 to 8

Table 2-53
PDH gateway circuit packs (Note)
VT1.5/VC11 L2SS-shelf#-slot# DS1WAN-shelf#-slot#- shelf# = 1 to 254

port#- slot# = 1 to 6 and 9 to 14 for
channel# 14-slot shelf (X-CONN 240G+/
80G cross-connect required for
slot# = 1-8, 11-18, 21-28, and
port# = 101 to 228
channel#=1 to 16
VT2/VC12 L2SS-shelf#-slot# E1WAN-shelf#-slot#- shelf# = 1 to 254

channel# 14-slot shelf (X-CONN 240G+/
80G cross-connect required for
slot# = 1-8, 11-18, 21-28, and
port# = 101 to 228
channel# = 1 to 16
STS1/VC3 L2SS-shelf#-slot# DS3WAN-shelf#-slot#- shelf# = 1 to 254

channel# 14-slot shelf
slot# = 1-8, 11-18, 21-28, and
port# = 101 to 228
channel# = 1
L2SS-shelf#-slot# E3WAN-shelf#-slot#- shelf# = 1 to 254

channel# 14-slot shelf
slot# = 1-8, 11-18, 21-28, and
port# = 101 to 228
channel# = 1

Table 2-53
STS1/AU3- L2SS-shelf#-slot# WAN-shelf#-slot#-port#- shelf# = 1 to 254

mapped VC3 sts# slot# = 1 to 6 and 9 to 14 for
port# = 101 to 228
sts# = 1
J# (AU4) = 1
K# (TUG-3) = 1
STS3c/VC4 L2SS-shelf#-slot# WAN-shelf#-slot#-port#- shelf# = 1 to 254

slot# = 1-8, 11-18, 21-28, and
port# = 101 to 228
sts# = 1
J# (AU4) = 1

slot# = 1-8, 11-18, 21-28, and
port# = 101 to 228
sts# = 1
J# (AU4) = 1

slot# = 1-8, 11-18, 21-28, and
port# = 101 to 228
sts# = 1
J# (AU4) = 1

Table 2-53

slot# = 1-8, 11-18, 21-28, and
port# = 101 to 228
sts# = 1
J# = 1
VT1.5-nv/ L2SS-shelf#-slot# WAN-shelf#-slot#-port#- shelf# = 1 to 254

(n = 1 to 64) vtg#-vt# 14-slot shelf (X-CONN 240G+/
WAN-shelf#-slot#-port#- 80G cross-connect required for
J#-K#- 14-slot packet-optical shelf)
L#-M# slot# = 1-8, 11-18, 21-28, and
port# = 101 to 228
sts# = 1 to 3
vt# = 1 to 4
J# (AU4) = 1
K# (TUG-3) = 1 to 3
M# (TU-11) = 1 to 4

Table 2-53
VT2-nv/ L2SS-shelf#-slot# WAN-shelf#-slot#-port#- shelf# = 1 to 254

(n = 1 to 64) vtg#-vt# 14-slot shelf (X-CONN 240G+/
WAN-shelf#-slot#-port#- 80G cross-connect required for
J#-K#- 14-slot packet-optical shelf)
L#-M# slot# = 1-8, 11-18, 21-28, and
port# = 101 to 228
sts# = 1 to 4, vtg# = 1 to 7 or ALL
vt# = 1 to 3
J# (AU4) = 1 to 2
K# (TUG-3) = 1 to 3
L# (TUG-2) = = 1 to 7 or ALL
M# (TU-12) = 1 to 3
STS1-nv/ L2SS-shelf#-slot# WAN-shelf#-slot#-port#- shelf# = 1 to 254

AU3-mapped sts# slot# = 1 to 6 and 9 to 14 for
and J#-K# slot# = 1-8, 11-18, 21-28, and
AU4-mapped 31-38 for 32-slot shelf
(n = 1 to 24) sts# = 1 to 24
J# (AU4) = 1 to 8
K# (TUG-3) = 1 to 3
STS3c-nv/ L2SS-shelf#-slot# WAN-shelf#-slot#-port#- shelf# = 1 to 254

slot# = 1-8, 11-18, 21-28, and
port# = 101 to 228
sts# = 1, 4, 7, 10, 13, 16, 19, 22
J# (AU4) = 1 to 32
K# (TUG-3) =1 to 3

Table 2-53
20G L2SS circuit packs
STS1/AU3- 20GL2SS-shelf#- WAN-shelf#-slot#-port#- shelf# = 1 to 254

mapped VC3 slot# vsts# slot# = 1 to 6 and 9 to 14 for
port# = 101 to 228
sts# = 1
J# (AU4) = 1
K# (TUG-3) = 1
STS3c/VC4 20GL2SS-shelf#- WAN-shelf#-slot#-port#- shelf# = 1 to 254

slot# sts# slot# = 1 to 6 and 9 to 14 for
slot# = 1-8, 11-18, 21-28, and
port# = 101 to 228
sts# = 1
J# (AU4) = 1
STS12c/ 20GL2SS-shelf#- WAN-shelf#-slot#-port#- shelf# = 1 to 254

VC4-4c slot# sts# slot# = 1 to 6 and 9 to 14 for
slot# = 1-8, 11-18, 21-28, and
port# = 101 to 228
sts# = 1
J# (AU4) = 1

slot# = 1-8, 11-18, 21-28, and
port# = 101 to 228
sts# = 1
J# (AU4) = 1

Table 2-53

slot# = 1-8, 11-18, 21-28, and
port# = 101 to 228
sts# = 1
J# = 1

slot# = 1-8, 11-18, 21-28, and
port# = 101 to 228
sts# = 1
J# = 1
STS1-nv/ 20GL2SS-shelf#- WAN-shelf#-slot#-port#- shelf# = 1 to 254

AU3 mapped slot# sts# slot# = 1 to 6 and 9 to 14 for
and J#-K# slot# = 1-8, 11-18, 21-28, and
AU4 mapped 31-38 for 32-slot shelf
(n = 1 to 24) sts# = 1 to 24
J# (AU4) = 1 to 8
K# (TUG-3) = 1 to 3
STS3c-nv/ 20GL2SS-shelf#- WAN-shelf#-slot#-port#- shelf# = 1 to 254

VC4-nv slot# sts# slot# = 1 to 6 and 9 to 14 for
slot# = 1-8, 11-18, 21-28, and
port# = 101 to 228
sts# = 1, 4, 7, 10, 13, 16, 19, 22
J# (AU4) = 1 to 8

Table 2-53
RPR circuit packs
STS1-nv/ L2RPR-shelf#-slot# WAN-shelf#-slot#-port#- shelf# = 1 to 254

AU3 mapped sts# slot# = 1 to 6 and 9 to 14 for
and J#-K# slot# = 1-8, 11-18, 21-28, and
AU4 mapped 31-38 for 32-slot shelf
(n =1 to 96) sts# = 1 to 192
J# (AU4) = 1 to 64
K# (TUG-3) = 1 to 3
STS3c-nv/ L2RPR-shelf#-slot# WAN-shelf#-slot#-port#- shelf# = 1 to 254

slot# = 1-8, 11-18, 21-28, and
port# = 101 to 104
sts# = 1
sts# = 1, 4, 7, 10, ..., 190
J# (AU4) = 1 to 64
STS3c/VC4 L2RPR-shelf#-slot# WAN-shelf#-slot#-port#- shelf# = 1 to 254

slot# = 1-8, 11-18, 21-28, and
port# = 101 to 104
sts# = 1
J# (AU4) = 1

Table 2-53
STS12c/ L2RPR-shelf#-slot# WAN-shelf#-slot#-port#- shelf# = 1 to 254

slot# = 1-8, 11-18, 21-28, and
port# = 101 to 104
sts# = 1
J# (AU4) = 1
STS48c/ L2RPR-shelf#-slot# WAN-shelf#-slot#-port#- shelf# = 1 to 254

slot# = 1-8, 11-18, 21-28, and
port# = 101 to 104
sts# = 1
J# = 1
Note: The PDH gateway circuit pack supports a map mode that controls the number and type of PDH
channels that can be provisioned per pack. For more information on the map modes, refer to Part 1 of
When you set the map mode to DS1E1DS3E3, you can provision up to 36 combined DS3 and E3 PDH
channels, including DS1 and E1 channels.
When you set the map mode DS3E3, you can provision up to 48 combined DS3 and E3 PDH channels (but
not DS1 or E3 PDH channels).
EVPL connections parameters

The following tables detail the 20G L2SS and L2 MOTR circuit pack
parameters associated with the EVPL Connections Site Manager
application.

Table 2-54
EVPL Connections application parameters for 20G L2SS and L2 MOTR circuit packs
Connection ID The connection identifier string is used to identify a provisioned EVPL
Rate Select the rate as EVPL. (This is the only connection rate supported in this
release.)
Type Represents the type of provisioned EVPL connection. The only supported
connection type in this release of 6500 is 2WAY (Bidirectional) (see Table 2-55
on page 2-300).
From and To panels Select the Equipment and Facility for the From and To endpoints as required.
Refer to Table 2-55 on page 2-300 and Table 2-56 on page 2-301.
VCID (1-1048575) Select the virtual circuit segment identifier (a value between 1 and 1048575).
The VCID creates the association between:
• LAG (NNI line port), WAN, ETH, ETH100, and ETH10G ports on 20G L2SS
circuit packs
• LAG (NNI line port), ETH, ETH100, and ETH10G ports on L2 MOTR circuit
packs
The VCID can be used to uniquely identify a specific customer in the 20G L2SS
and L2 MOTR network.
Note: In the Data Services application view for 20G L2SS and L2 MOTR circuit
packs, these entities are shown as associations between VCS and its VCEs and
VCEMAPs. The VCS and associated VCEs and VCEMAPs all have the same
VCID value.
SVID (1-4094) Select the service provider VLAN identifier (a value between 1 and 4094).
The SVID is used to uniquely identify the EVPL service on the muxed line port.
The SVID is unique to a port and optional if the VCID is less than 4095 (if the
SVID is not specified, the SVID is equal to the VCID).

Table 2-55
EVPL connection types for 20G L2SS and L2 MOTR circuit packs—supported From and To
instances
Connection type From To
2WAY LAG (NNI line port), WAN, ETH, LAG (NNI line port), WAN, ETH,
ETH100, and ETH10G for ETH100, and ETH10G for 20G L2SS
20G L2SS circuit packs circuit packs
ETH, ETH100, ETH10G for ETH, ETH100, ETH10G for L2 MOTR
L2 MOTR circuit packs circuit packs
Note: EVPL connections are only supported between a Tx conditioning UNI port and a NNI port,
or between two NNI ports.

Table 2-56
Equipment and facility parameters for EVPL connections for L2 MOTR circuit packs
20G L2SS circuit packs
EVPL 20GL2SS-shelf#-slot# WAN-shelf#-slot#-port# shelf# = 1 to 254

slot# = 1 to 6 and 9 to 14 for
14-slot shelf
slot# = 1-8, 11-18, 21-28, and
port# = 101 to 164
PGE-shelf#-slot#-port# ETH-shelf#-slot#-port# shelf# = 1 to 254

PGEFC-shelf#-slot#- slot# = 1 to 6 and 9 to 14 for
port# 14-slot shelf
port# = 3 to 12
PFE-shelf#-slot#-port# ETH100-shelf#-slot#-port# shelf# = 1 to 254

slot# = 1 to 6 and 9 to 14 for
14-slot shelf
slot# = 1-8, 11-18, 21-28, and
port# = 1 and 2
P10GEL-shelf#-slot#- ETH10G-shelf#-slot#-port# shelf# = 1 to 254

port# slot# = 1 to 6 and 9 to 14 for
P10GSEL-shelf#-slot#- 14-slot shelf
port# slot# = 1-8, 11-18, 21-28, and
port# port# = 1 and 2

Table 2-56
Equipment and facility parameters for EVPL connections for L2 MOTR circuit packs (continued)
L2 MOTR circuit packs
EVPL PGE-shelf#-slot#-port# ETH-shelf#-slot#-port# shelf# = 1 to 254

PGEFC-shelf#-slot#- slot# = 1, 2 for 2-slot shelf
port# slot# = 1 to 7 for 7-slot shelf
PGEFC200-shelf#-slot#- slot# = 1 to 14 for 14-slot shelf
port# (except in slots 7 and 8 of the
slot# = 1-8, 11-18, 21-28, and
port# = 3 to 12
PFE-shelf#-slot#-port# ETH100-shelf#-slot#-port# shelf# = 1 to 254

slot# = 1, 2 for 2-slot shelf
slot# = 1 to 7 for 7-slot shelf
(except in slots 7 and 8 of the
slot# = 1-8, 11-18, 21-28, and
port# = 3 to 12
P10GEL-shelf#-slot#- ETH10G-shelf#-slot#-port# shelf# = 1 to 254

port# slot# = 1, 2 for 2-slot shelf
P10GSEL-shelf#-slot#- slot# = 1 to 7 for 7-slot shelf
port#
P10GSOEL-shelf#-slot#- (except in slots 7 and 8 of the
port# 14-slot packet-optical shelf)
PXFP-shelf#-slot#-port# slot# = 1-8, 11-18, 21-28, and
port# = 1 and 2

6500 Packet-Optical Platform
Data and Layer 2 Circuit Packs
Copyright© 2010-2019 Ciena® Corporation. All rights reserved.
Release 12.6
Publication: 323-1851-102.7
Document status: Standard
Issue 1
Document release date: September 2019
CONTACT CIENA
For additional information, office locations, and phone numbers, please visit the Ciena
web site at www.ciena.com

323-1851-102.7 (6500 R12.6 Data Layer2 CPS) Issue1

Uploaded by

Copyright:

Available Formats

323-1851-102.7 (6500 R12.6 Data Layer2 CPS) Issue1

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

323-1851-102.7 (6500 R12.6 Data Layer2 CPS) Issue1

Uploaded by

Copyright:

Available Formats

6500 Packet-Optical Platform

Data and Layer 2 Circuit Packs

323-1851-102.7 - Standard Issue 1

6500 Packet-Optical Platform Data and Layer 2 Circuit Packs

6500 Packet-Optical Platform Data and Layer 2 Circuit Packs

6500 Packet-Optical Platform Data and Layer 2 Circuit Packs

New in this release and documentation roadmap xi

6500 Packet-Optical Platform Data and Layer 2 Circuit Packs

Technical specifications 1-35

6500 Packet-Optical Platform Data and Layer 2 Circuit Packs

Layer 2 circuit packs 2-1

6500 Packet-Optical Platform Data and Layer 2 Circuit Packs

6500 Packet-Optical Platform Data and Layer 2 Circuit Packs

2-20 Changing the eMOTR equipment profile 2-169

6500 Packet-Optical Platform Data and Layer 2 Circuit Packs

6500 Packet-Optical Platform Data and Layer 2 Circuit Packs

New in this release and documentation

This Technical Publication supports 6500 Packet-Optical Platform (6500)

6500 Packet-Optical Platform technical publications

6500 Packet-Optical Platform Data and Layer 2 Circuit Packs

6500 D-Series and S-Series roadmap

Planning a Network Installing, Managing and Maintaining and Circuit Pack-Based

Documentation Installation - Administration Fault Management - Common Equipment

SAOS-based Command Fault and MIB

6500 Packet-Optical Platform Data and Layer 2 Circuit Packs

6500 T-Series roadmap

Planning a Network Installing, Managing and Maintaining and

T-Series Administration Fault Management -

SAOS-based Command Fault and MIB

6500 Packet-Optical Platform Data and Layer 2 Circuit Packs

6500 Packet-Optical Platform Data and Layer 2 Circuit Packs

Data circuit packs (Ethernet Private Line

This section provides an overview of the 6500 Packet-Optical Platform (6500)

Refer to 6500 Packet-Optical Platform Data Application Guide, NTRN15BA,

6500 Packet-Optical Platform Data and Layer 2 Circuit Packs

4xGE EPL circuit packs (NTK535LAE5 and NTK535LBE5)

GE LAN/ETH port 1 WAN port 1 STS/VC containers

6500 Packet-Optical Platform Data and Layer 2 Circuit Packs

Red triangle (Fail)

Blue diamond (In Use)

Rx Red/yellow bi-color circle (Fail/LOS)

Transmit/receive SFP dual LC connector

6500 Packet-Optical Platform Data and Layer 2 Circuit Packs

6500 Packet-Optical Platform Data and Layer 2 Circuit Packs

6500 Packet-Optical Platform Data and Layer 2 Circuit Packs

6500 Packet-Optical Platform Data and Layer 2 Circuit Packs

WAN signals can be mapped to non-concatenated, concatenated and virtual

6500 Packet-Optical Platform Data and Layer 2 Circuit Packs

PGE GE 1000-Base-ZX 1550 nm SFP NTTP07FF

GE 1000-Base-BX 10-U Bidirectional-upstream, NTTP58BD

GE 1000-Base-BX 10-D Bidirectional- NTTP59BD

1000-BaseT RJ45 SFP NTTP61AAE6

PGEFC GE/FC100 1000-BaseSX 850 nm SFP NTTP01AF

GE/FC100 1000-BaseLX 1310 nm SFPs NTTP01CF and

GE/FC100 1.25 Gbit/s 24 dB CWDM SFPs NTK591xB where

GE/FC100 1.25 Gbit/s 32 dB CWDM SFPs NTK591xH where

PGEFC200 GE/FC100/FC200 1000-BaseSX 850 nm SFP NTTP06AF

GE/FC100/FC200 1000-BaseLX 1310 nm SFP NTTP06CF

For detailed information and procedures associated with performance