Ciena OME 6130 R5.0 Planning Issue3

613

Planning Guide

Release 5.0

What’s inside...

IntroductionFeature overviewConfigurations, upgrades, and interworkingHardware descriptionUser interface descriptionOAM&P descriptionTechnical specificationsOrdering information and system engineering rulesTechnical assistanceAppendix A: Data communications planning

NT6QMay Copy

0 Multiservice Optical Platform

Ciena® Confidential and Proprietary

92ME - Issue 3 Standard2012right© 2011-2012 Ciena® Corporation. All rights reserved.

LEGAL NOTICES

THIS DOCUMENT CONTAINS CONFIDENTIAL AND TRADE SECRET INFORMATION OF CIENA CORPORATIONAND ITS RECEIPT OR POSSESSION DOES NOT CONVEY ANY RIGHTS TO REPRODUCE OR DISCLOSE ITSCONTENTS, 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 CIENACORPORATION IS STRICTLY FORBIDDEN.

EVERY EFFORT HAS BEEN MADE TO ENSURE THAT THE INFORMATION IN THIS DOCUMENT IS COMPLETEAND ACCURATE AT THE TIME OF PUBLISHING; HOWEVER, THE INFORMATION CONTAINED IN THISDOCUMENT IS SUBJECT TO CHANGE.

While the information in this document is believed to be accurate and reliable, except as otherwise expressly agreed toin 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 changewithout notice.

Copyright© 2011-2012 Ciena® Corporation.

All Rights Reserved

The material contained in this document is also protected by copyright laws of the United States of America and othercountries. It may not be reproduced or distributed in any form by any means, altered in any fashion, or stored in a database or retrieval system, without express written permission of the Ciena Corporation.

SecurityCiena® cannot be responsible for unauthorized use of equipment and will not make allowance or credit forunauthorized use or access.

Contacting Ciena

For additional office locations and phone numbers, please visit the Ciena web site at www.ciena.com.

Corporate Headquarters 410-694-5700 or 800-921-1144 www.ciena.com

Customer Technical Support/Warranty

In North America1-800-CIENA24 (243-6224) 410-865-4961

In Europe, Middle East, and Africa

800-CIENA-24-7 (800-2436-2247) +44-207-012-5508

In Asia-Pacific800-CIENA-24-7 (800-2436-2247) +81-3-6367-3989+91-124-4340-600

In Caribbean and Latin America

800-CIENA-24-7 (800-2436-2247) 410-865-4944 (USA)

Sales and General Information 410-694-5700 E-mail: [email protected]

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-124-434-0500 E-mail: [email protected]

In Latin America 011-5255-1719-0220 (Mexico City) E-mail: [email protected]

Training877-CIENA-TD (243-6283) or 410-865-8996

E-mail: [email protected]

6130 Multiservice Optical Platform Planning GuideRelease 5.0 NT6Q92ME Standard Issue 3Copyright© 2011-2012 Ciena® Corporation May 2012

IMPORTANT: PLEASE READ THIS LICENSE AGREEMENT ("AGREEMENT") CAREFULLY BEFOREINSTALLING OR USING CIENA CORPORATION ("Ciena") SOFTWARE, HARDWARE OR DOCUMENTATION(COLLECTIVELY, THE "EQUIPMENT").

BY INSTALLING OR USING THE EQUIPMENT, YOU ACKNOWLEDGE THAT YOU HAVE READ THISAGREEMENT AND AGREE TO BE BOUND BY ITS TERMS AND CONDITIONS.

1. Right to Use License; Restrictions. Subject to these terms, and the payment of all applicable license fees, Cienagrants to you, as end user, a non-exclusive license to use the Ciena software (the "Software") in object code formsolely in connection with, and as embedded within, the Equipment,. You shall have the right to use the Software solelyfor your own internal use and benefit. You may make one copy of the Software and documentation solely for backupand archival purpose, however you must reproduce and affix all copyright and other proprietary rights notices thatappear in or on the original. You may not, without Ciena's prior written consent, (i) sublicense, assign, sell, rent, lend,lease, transfer or otherwise distribute the Software; (ii) grant any rights in the Software or documentation not expresslyauthorized herein; (iii) modify the Software nor provide any third person the means to do the same; (iv) createderivative works, translate, disassemble, recompile, reverse engineer or attempt to obtain the source code of theSoftware in any way; or (v) alter, destroy, or otherwise remove any proprietary notices or labels on or embedded withinthe Software or documentation. You acknowledge that this license is subject to Section 365 of the U.S. BankruptcyCode and requires Ciena's consent to any assignment related to a bankruptcy proceeding. Sole title to the Softwareand documentation, to any derivative works, and to any associated patents and copyrights, remains with Ciena or itslicensors. Ciena reserves to itself and its licensors all rights in the Software and documentation not expressly grantedto you. You shall preserve intact any notice of copyright, trademark, logo, legend or other notice of ownership from anyoriginal or copies of the Software or documentation.

2. Audit: Upon Ciena's reasonable request, but not more frequently than annually without reasonable cause, youshall permit Ciena to audit the use of the Software at such times as may be mutually agreed upon to ensurecompliance with this Agreement.

3. Confidentiality. You agree that you will receive confidential or proprietary information ("Confidential Information")in connection with the purchase, deployment and use of the Equipment. You will not disclose Confidential Informationto any third party without prior written consent of Ciena, will use it only for purposes for which it was disclosed, use yourbest efforts to prevent and protect the contents of the Software from unauthorized disclosure or use, and must treat itwith the same degree of care as you do your own similar information, but with no less than reasonable care. Youacknowledge that the design and structure of the Software constitute trade secrets and/or copyrighted materials ofCiena and agree that the Equipment is Confidential Information for purposes of this Agreement.

4. 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 and52-227-19 or DFARS Section 52.227-7013(C)(1)(ii), as applicable. The Equipment and any accompanying technicaldata (collectively "Materials") are commercial within the meaning of applicable Federal acquisition regulations. TheseMaterials were developed fully at private expense. U.S. Government use of the Materials is restricted by thisAgreement, and all other U.S. Government use is prohibited. In accordance with FAR 12.212 and DFAR Supplement227.7202, software delivered to you is commercial computer software and the use of that software is further restrictedby this Agreement.

5. Term of License. This license is effective until terminated. Customer may terminate this license at any time bygiving written notice to Ciena [or] and destroying or erasing all copies of Software including any documentation. Cienamay terminate this Agreement and your license to the Software immediately by giving you written notice of terminationin the event that either (i) you breach any term or condition of this Agreement or (ii) you are wound up other thanvoluntarily for the purposes of amalgamation or reorganization, have a receiver appointed or enter into liquidation orbankruptcy or analogous process in your home country. Termination shall be without prejudice to any other rights orremedies Ciena may have. In the event of any termination you will have no right to keep or use the Software or anycopy of the Software for any purpose and you shall destroy and erase all copies of such Software in its possession orcontrol, and forward written certification to Ciena that all such copies of Software have been destroyed or erased.


6. Compliance with laws. You agree to comply with all applicable laws, including all import regulations, and to obtainall required licenses and permits related to installation and use of Equipment. Software, including technical data, issubject to U.S. export control laws, including the U.S. Export Administration Act and its associated regulations, andmay be subject to export or import regulations in other countries. Customer agrees to comply strictly with all suchregulations and acknowledges that it has the responsibility to obtain licenses to export, re-export, or import Software.

7. Limitation of Liability. ANY LIABILITY OF Ciena SHALL BE LIMITED IN THE AGGREGATE TO THE AMOUNTSPAID BY YOU FOR THE SOFTWARE. THIS LIMITATION APPLIES TO ALL CAUSES OF ACTION, INCLUDINGWITHOUT LIMITATION BREACH OF CONTRACT, BREACH OF WARRANTY, NEGLIGENCE, STRICT LIABILITY,MISREPRESENTATION AND OTHER TORTS. THE LIMITATIONS OF LIABILITY DESCRIBED IN THIS SECTIONALSO APPLY TO ANY THIRD-PARTY SUPPLIER OF Ciena. NEITHER Ciena NOR ANY OF ITS THIRD-PARTYSUPPLIERS 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 INFORMEDOF THE POSSIBILITY OF SUCH DAMAGES IN ADVANCE

8. General. Ciena may assign this Agreement to any Ciena affiliate or to a purchaser of the intellectual property rightsin the Software, but otherwise neither this Agreement nor any rights hereunder may be assigned nor duties delegatedby either party, and any attempt to do so will be void. This Agreement shall be governed by the laws of the State ofMaryland (without regard to the conflict of laws provisions) and shall be enforceable in the courts of Maryland. TheU.N. Convention on Contracts for the International Sale of Goods shall not apply hereto. This Agreement constitutesthe complete and exclusive statement of agreement between the parties relating to the license for the Software andsupersedes all proposals, communications, purchase orders, and prior agreements, verbal or written, between theparties. If any portion hereof is found to be void or unenforceable, the remaining provisions shall remain in full forceand effect.


v

Publication history 0

May 2012Issue 3 of the 6130 Release 5.0 Planning Guide. Updated to include 2xGE Extended Temp Circuit Pack, NT6Q20BAE5.

April 2012Issue 2 of the 6130 Release 5.0 Planning Guide.

November 2011Issue 1 of the 6130 Release 5.0 Planning Guide.


vi Publication history


vii

Contents 0

About this document xv

Introduction 1-16130 applications 1-36130 service interfaces 1-4

Small form-factor pluggable interfaces 1-6Point-to-point optical broadband services 1-6TDM switching 1-7Layer 2 switching 1-7

6130 Input/Output (I/O) Modules 1-8Network management 1-8Key features and benefits 1-9

Feature overview 2-1Physical description 2-11Interface circuit packs 2-12System Line-up and Test (SLAT) 2-15Configurations 2-16Connection management 2-17

Service mapping 2-17Traffic protection 2-19Equipment Protection 2-19Synchronization 2-20Alarms and events 2-20Performance monitoring 2-21Loopbacks 2-21Data management 2-22Security and administration 2-22Autodiscovery 2-23Data communication network 2-236130 management 2-24

Local Craft Access Terminal 2-24Site manager 2-24TL1 user interfaces 2-24SNMP traps 2-24

Interworking with Ciena portfolio 2-25Interoperating with non-Ciena portfolio 2-25


viii Contents

Configurations, upgrades, and interworking 3-11+1 MSP/APS 3-1SNCP/UPSR 3-2MS-SPRing/BLSR 3-2Unprotected configuration 3-3Tributary Equipment Protection 3-3Network reconfiguration 3-4Upgrade support 3-4

Software 3-4Hardware 3-4

6130 interworking with other products 3-5Interworking with MS-SPRing/BLSR configurations 3-6Interoperability with non-Ciena portfolio 3-6

Hardware description 4-1Hardware architecture 4-2Chassis 4-4Slot numbers 4-7Power supply unit 4-7

DC PSU 150W single feed 4-8AC PSU 150W 4-8

Fan module 4-9ESD interface 4-9

OAM circuit pack 4-10Aggregate circuit packs 4-11

2x155/622M aggregate circuit pack 4-121x155/622M aggregate circuit pack 4-141x2.5G aggregate circuit pack 4-161x2.5G+4x155M/2x622M aggregate circuit pack 4-19

Tributary interface circuit pack 4-22Transmux circuit pack 4-238xGE EoPDH L2 circuit pack 4-248xETH circuit pack 4-274x10/100BT+4x100FX L1 circuit pack 4-292xGE+8x10/100BT L1 1.2G circuit pack 4-322xGE circuit pack 4-35L2PA circuit packs 4-3728xE1/DS1 circuit pack 4-4463xE1/DS1 circuit pack 4-4528xE1/DS1(W/P) circuit pack 4-463xE3/DS3 circuit pack 4-483xE3/DS3(W/P) circuit pack 4-492x155M circuit pack 4-502x622M/8x155M circuit pack 4-51

I/O Modules 4-5528xE1/DS1 1+1 I/O Module 4-5584xE1/DS1 1:N I/O Module 4-563xE3/DS3 1+1 I/O Module 4-57

Filler faceplate 4-58


Contents ix

E1 75 ohm termination panel 4-58Cable routing 4-586130 Shelf assembly kit 4-59

User interface description 5-16130 Node Manager (WUI) 5-16100 Site Manager 5-2TL1 interface 5-3SNMP traps 5-4

OAM&P description 6-1SDH and SONET Configurations 6-2System Line-up and Test (SLAT) 6-3

Commissioning process 6-3Testing process 6-5

Network element management 6-5Equipment management 6-5Facility management 6-7

Managing facilities 6-7Loopbacks 6-9Synchronization management 6-11

Timing generation 6-11Timing distribution 6-14Synchronization operating modes 6-14Synchronization status messages 6-15Viewing and management 6-16Synchronization protection 6-17

Connection management 6-17Hair-pinning 6-24Connection management application 6-24

Equipment protection 6-25Aggregate Card Protection 6-26Tributary Card Protection 6-26

Traffic protection 6-27Traffic Protection application 6-29

1+1 MSP/APS traffic protection 6-30Provisioning MSP/APS protected connections 6-301+1 MSP/APS protection switch criteria 6-32

SNCP/UPSR Traffic Protection 6-33Provisioning SNCP/UPSR connections 6-33SNCP/UPSR protection switch types 6-33

2-Fiber MS-SPRing/BLSR traffic protection 6-34Provisioning MS-SPRing/BLSR protected configurations 6-35Cross-connect provisioning for MS-SPRing/BLSR 6-35MS-SPRing/BLSR protection switch types 6-37

Traffic protection exerciser 6-37Unprotected connections 6-38

Provisioning unprotected connections 6-38Data communications 6-39


x Contents

Interfaces 6-39DCC Transparency 6-43OAM comms management 6-44OAM comms routing 6-44

Alarm and event management 6-456130 local alarm indications 6-45Alarm management / surveillance 6-45Alarm Reporting Control 6-47PDH / DSn alarm monitoring 6-49

Performance monitoring 6-51PM functions 6-51STM/ OCn PM parameters 6-52PDH / DSn performance monitoring 6-52PDH / DSn PM parameters 6-5310/100/1000BT, 100FX and GE PM parameters 6-53WAN PM parameters 6-58PM time intervals 6-61PM enable/disable 6-61PM inhibition 6-61

Security and administration 6-61Local account user authentication 6-62RADIUS Centralized authentication 6-62Security levels 6-64Login sessions 6-65Local password management 6-65Lockout users 6-66Database changes log / audit trail 6-67Network element name 6-68Date and time setting 6-68

Auto discovery 6-69Backing up and restoring the network element database 6-69Installing and upgrading network element 6-70

Deliver release 6-71Check upgrade 6-71Load upgrade 6-71Invoke upgrade 6-71Commit upgrade 6-71

Technical specifications 7-1Physical specifications 7-2Power specifications 7-5Connector pinouts 7-8

DC power connector 7-9OAM circuit pack connector pinouts 7-9

E1/DS1 cable pinouts and assemblies 7-12Cable details 7-1228xE1/DS1 connector pinouts 7-1463xE1/DS1connector pinouts 7-23E1/DS1 Cable routing 7-36


Contents xi

Optical specifications 7-37STM-1/4/16/OC-3/12/48, 100Base and GE SFP optical specifications 7-38

Electrical specifications 7-54Environmental specifications 7-57

Operating environment specifications 7-57Electromagnetic specifications 7-58Safety specifications 7-59

General commercial and regulatory 7-59Laser emission 7-59

Power and grounding specifications 7-60DC input voltage range 7-60

Ordering information and system engineering rules 8-16130 network element configuration rules 8-2

Chassis layout 8-2Bay equipping rules 8-5Shelf equipping rules 8-5Site engineering recommendations 8-16

List of parts 8-186130 chassis and components 8-186130 shelf assembly kit 8-20Tributary circuit packs & I/O Modules 8-21Small form-factor pluggable (SFP) modules 8-23Electrical interface hardware 8-29E1/DS1 cable assemblies 8-30E3/DS3 cable assemblies 8-33STM-1e cable assemblies 8-34Ethernet service cable assemblies 8-35Optical fiber patch cords 8-36OAM cable assemblies 8-39Power and earthing cable assemblies 8-41Software load 8-42Right to use licenses 8-43Site Manager for 6100 8-43Engineering and support services 8-446130 documentation 8-44Change application procedures 8-46

RoHS compliant equipment 8-47Ordering procedures 8-47

List of procedures8-1 Ordering 6130 chassis, circuit packs, and software 8-488-2 Ordering cables, documentation, and services 8-65

Technical assistance 9-1Technical support and information 9-2Ciena web site 9-2CE mark 9-2Field return information 9-3


xii Contents

Appendix A: Data communications planning 10-1Introduction 10-2OAM&P Ports 10-3

M1/F1 port 10-3LAN port (LAN-1-6) 10-3

Network Interface 10-4STM-1/4/16/OC-3/12/48 Data Communication Channel 10-7

Data link layer protocols 10-7STM-1/4/16/OC-3/12/48 DCC operation mode 10-8Overhead transparency 10-10STM-1/4/16/OC-3/12/48 DCC implementation rules 10-11

IP communication 10-12Static routing 10-13Dynamic routing - OSPF 10-14Dynamic routing - Integrated IS-IS 10-15Routing protocol configuration 10-16Proxy ARP 10-16

OSI data communications 10-17CLNP 10-18Configure OSI connection 10-18Configure GRE tunnel 10-19Configure IP routing 10-23

Application protocols 10-23ftp 10-24telnet 10-24

Diagnostic commands 10-24arp 10-24ifconfig 10-24ping 10-24route 10-24tcpdump 10-24

Firewall considerations 10-25Engineering guidelines 10-25

DCN performance 10-27Supported DCN design examples 10-28

DCN example 1 - Using static routing with direct LAN connections to 6130 network elements. 10-30

DCN example 2 - Using single 6130 GNE with static routing to external DCN. OSPF is used in between 6130 network elements. 10-34

DCN example 3 - Using single 6130 GNE with OSPF to external DCN. OSPF is used in between 6130 network elements. 10-38

DCN example 4 - Using OSPF with dual 6130 GNEs to external OSPF backbone. 10-42

6100DCN example 5 - Using single OM4000/3000 GNE with GRE tunnels through OM4000/3000 network to reach remote 6130 network elements in linear spurs off OM4000/3000 NE. 10-47

DCN example 6 - Using single OM4000/3000 GNE with GRE tunnels through OM4000/3000 network to reach remote 6130 network elements in SNCP/UPSR ring with an OM4000/3000 network element. 10-53


Contents xiii

DCN example 7 - Using dual OM4000/3000 GNEs with GRE tunnels through OM4000/3000 network to reach remote 6130 network elements in SNCP/UPSR ring with generic SONET/SDH network elements. 10-59

DCN example 8 - Using single 6130 GNE with iISIS through OM4000/3000 network to reach remote 6130 network elements in SNCP/UPSR rings with OM4000/3000 network elements. Proxy ARP used at 6130 GNE for access to remote 6130 NEs. 10-65

DCN example 9 - Using single 6500 GNE with iISIS through 6500 network to reach remote 6130 network elements. 10-72

DCN example 10 - Using single 6500 GNE with iISIS to reach remote 6130 network elements in a SNCP/UPSR ring configuration with generic SDH/SONET equipment. 10-78

DCN example 11 - Using VC12 management channels through OM4000 network to reach remote 6130 network elements in SNCP ring with OM4000 and legacy OSI network elements. Transparent DCC used to provided resilient OSI communications. 10-84

DCN example 12 - Using E1 and VC12 management channels to reach remote 6130 network elements in SNCP ring with OM4000 and legacy OSI network element. Transparent DCC used to provided resilient OSI communications. 10-90

IP networks, addressing, and masks 10-95Dotted decimal notation for IP addresses 10-96Circuitless IP interface 10-98ARP 10-98

IP routing protocols 10-99OSPF 10-99Route preference 10-105Static and default routes 10-105


xiv Contents


xv

About this document 0

This planning guide describes the applications and functionality provided by the software and hardware of 6130 Multiservice Optical Platform (6130) Release 5.0.

This planning guide covers the following topics:

• Introduction

• Features overview

• Configurations and interworking

• Hardware description

• User interface description

• Operations, administration, maintenance and provisioning (OAM&P) description

• Technical specifications

• Ordering information and system engineering rules

• Technical assistance

• Appendix A: Data communications planning

Supported software releaseThis document supports the software release for 6130 Release 5.0.

AudienceThe following members of your company are the intended audience of this Ciena technical publication:

• Planners

• Provisioners

• Network administrators

• Transmission standards engineers

• Maintenance personnel


xvi About this document

6130 Multiservice Optical Platform (6130) Technical Publications Library

This roadmap identifies the 6130 library structure and the use of application guides and technical publications.


About this document xvii

ReferencesThis document refers to the following 6130 technical publications:

• Documentation Roadmap, 323-1855-090

• TL1 Reference, 323-1855-190

• Local Craft Access User Guide, 323-1855-195

• Installation, Commissioning and Testing Procedures, 323-1855-201

• Provisioning and Protection Switching Procedures, 323-1855-310

• Bandwidth and Data Services Procedures, 323-1855-320

• Trouble Clearing and Module Replacement Procedures, 323-1855-543

This document refers to the following 6130 supporting documentation:

• Site Manager for 6100 Rel 4.0 Fundamentals, NT6Q91AD

• Data Communications Network Planning Guide, NTR710AM

• Network Interworking Guide, NTCA68CA

• 6100 Data Application Guide, NTRN15CA


xviii About this document


1-1

Introduction 1-

The 6130 is a compact-MSPP (Multi-Service Provisioning Platform) offering very cost effective transport of Ethernet and TDM services over SDH and SONET networks. The 6130 is designed for use in customer sites and in collector networks where multi-service capability is required and compact footprint is paramount.

The 6130 Release 5.0 is a global platform and is software provisionable for either SDH or SONET mode. Figure 1-1 and Figure 1-2 displays the 6130 network element.

Figure 1-16130 network element (without I/O modules)


1-2 Introduction

Figure 1-26130 network element (with I/O modules)

The 6130 provides dramatic cost savings over currently deployed solutions and offers deployment flexibility at multiple levels, including:

• Service flexibility: Full mix of services including 10/100Base-T Ethernet (Layer 1 and Layer 2), 100Base-FX (Layer 1 and Layer 2), Gigabit Ethernet (Layer 1 and Layer 2), E1/DS1, E3/DS3, STM-1o/e, STM-4o, OC-3 and OC-12.

• Reach flexibility: Small Form-Factor Pluggable (SFPs) optics are used, allowing each shelf to be configured for the distance and wavelength required.

• Protection flexibility: Can be deployed with or without line protection. 1+1 MSP/APS, SNCP/UPSR and MS-SPRing/BLSR network protection protocols are supported. 1+1 and 1:N (N=3) tributary protection is supported for the 28xE1/DS1 (1+1 and 1:3) and 3xE3/DS3 (1+1) tributaries.

• Interoperability flexibility: Can be networked either with 6110, 6130 or 6150 network elements, or subtended from other Ciena optical products, such as OM3000, OM4000 or 6500.

• Management flexibility: The 6130 is fully integrated into Ciena’s Optical Network Manager with OMEA. The 6130 can also be managed from an HTTP web-based craft user interface running on the network element. In addition, SNMP alarm traps are supported, enabling 6130 fault management from SNMP management systems. The 6130 can also be managed with 6100 Site Manager.


Introduction 1-3

• Data communications flexibility: The 6130 can be managed over either OSI or IP DCN networks. Path DCC capabilities are also provided for extending management reach over third-party networks.

The 6130 is a carrier grade platform that builds upon the solid reputation for dependability of Ciena's widely deployed optical networking products.

The various protection options offered by the 6130 further enhance the dependability of service transport. For access head end applications, service traffic can either be connected via sub-network connection protection (SNCP)/unidirectional path-switched ring (UPSR), via protected point-to-point 1+1 connections or MS-SPRing/BLSR configuration.

6130 applicationsThe 6130 offers significant value across a range of network applications. The principal 6130 applications are:

• Feeder for Metro Optical networks: The 6130 can be subtended from Ciena’s larger Optical platforms to collect 10/100Base-T (10/100BT) Ethernet, 100Base-FX (100FX) Ethernet, Gigabit Ethernet (GE), E1/DS1, E3/DS3, STM-1o/e, STM-4o, OC-3 and OC-12 traffic from the Access Edge. Its compact footprint and low price make it well suited for smaller customer locations. The 6130 can be subtended either in a SNCP/UPSR, 1+1 MSP/APS or MS-SPRing/BLSR configuration. The capability to manage 6130 using path DCC bytes also allows it to be managed remotely over leased STM-1/4/16/OC-3/12/48 circuits. The Regenerator Section/Section and Multiplexer Section/Line overhead tunnel capability provides further flexibility in managing other SDH/SONET equipment within the same ring.

• Private Enterprise Networks: The 6130 can be deployed in smaller private networks providing transport of 10/100BT, 100FX, GE, E1/DS1, E3/DS3, STM-1o/e, STM-4o, OC-3 and OC-12 services between sites. A light weight management solution is available for such applications consisting of a web-based craft interface running on the 6130 for NE provisioning and SNMP north bound interface for reporting alarms to a generic SNMP alarm browser.

• Wireless Backhaul: The 6130 is also well suited for wireless backhaul applications where both space and cost are paramount. The 6130 can be used as a cost-effective backhaul of today’s E1/DS1s and will support the 3G/4G network transition to Ethernet.


1-4 Introduction

6130 service interfaces6130 offers transport and aggregation of asynchronous private lines, SDH/SONET, and Ethernet. The 6130 shelf has four (4) universal tributary slots and supports a full mix of tributary interfaces. The 6130 supports four basic categories of interface:

• Layer 1 Ethernet services: 10/100Base-T (10/100BT) Ethernet, 100Base-FX (100FX) Ethernet and Gigabit Ethernet (GE).

— The tributary slots can be equipped with the 8xETH, 4x10/100BT+4x100FX L1, 4x10/100BT+4x100FX L1 622M, 2xGE and 2xGE+8x10/100BT L1 1.2G Ethernet circuit packs.

– The 8xETH Ethernet circuit pack supports 8 10/100BT Ethernet Private Line (EPL) ports.

– The 4x10/100BT+4x100FX L1 and 4x10/100BT+4x100FX L1 622M Ethernet circuit pack supports 4 10/100BT and 4 100FX EPL ports.

– The 2xGE circuit pack supports 2 GE EPL ports.

– The 2xGE+8x10/100BT L1 1.2G Ethernet Circuit pack supports 8 10/100BT and 2 GE EPL ports with 1.2G WAN bandwidth (uplink).

• Layer 2

— Packet Aggregation (L2PA) services: 10/100Base-T (10/100BT) Ethernet, 100Base-FX (100FX) Ethernet and Gigabit Ethernet (GE)

— EoPDH services: 100/1000 BT and 1000 Base SX/LX/ZX

— The tributary slots can be equipped with the L2PA622M, the L2PA1G2 Ethernet and the 8xGE EoPDH L2 circuit pack.

– The L2PA622M circuit pack (name on circuit pack faceplate label is 2xGE/FX+8x10/100BT L2 622M) supports 2 GE or 2 100FX ports and 8 10/100BT L2 ports with 622M WAN bandwidth (uplink).

– The L2PA1G2 circuit pack (name on circuit pack faceplate label is 2xGE/FX+8x10/100BT L2 1G2) supports 2 GE or 2 100FX ports and 8 10/100BT L2 ports with 1.2G WAN bandwidth (uplink).

– The 8xGE EoPDH L2 circuit pack supports 4 x 100/1000 BT and 4 x 1000 Base SX/LX/ZX with 622M WAN bandwidth (uplink)

— The Layer 2 Packet Aggregation (L2PA) circuit packs have the capabilities to help aggregate and switch Ethernet services. L2PA provides a strong Ethernet services and infrastructure solution for IP, Ethernet Private LANs, Ethernet VPNs, Ethernet Virtual Private Lines, Triple Play Services, and Internet access solutions.

— The EoPDH circuit pack offers Ethernet Virtual Private Lines and Ethernet Virtual Private LANs.


Introduction 1-5

— Ethernet Ring Protection (ERP) is supported with the L2PA and EoPDH circuit packs. The ERP Standard (G.8032) is also referred to as E-SPRing and it provides sub 50ms protection mechanism for the Ethernet traffic.

— Transparent IGMP snooping (V1, V2 and V3) is supported with the L2PA circuit pack as per RFC 4541.

— Inter-card and intra-card WAN-to-WAN connections is supported.

• PDH

— The tributary slots can be equipped with the 28xE1/DS1, 63XE1/DS1, 3xE3/DS3, 28xE1/DS1(W/P), 3xE3/DS3(W/P) and Transmux circuit packs.

– The Transmux supports 6 x DS3/E3 ports.

– The 28xE1/DS1 circuit pack supports 28 E1/DS1 ports.


– The 28xE1/DS1(W/P) circuit pack supports 1+1 and 1:3 tributary protection. I/O modules are required with the 28xE1/DS1(W/P) circuit pack. See 6130 Input/Output (I/O) Modules on page 1-8 for details on the I/O modules.


– The 3xE3/DS3(W/P) circuit pack supports 1+1 E3/DS3 tributary protection. I/O modules are required with the 3xE3/DS3(W/P) circuit pack. See 6130 Input/Output (I/O) Modules on page 1-8 for details on the I/O modules.

• SDH/SONET

— The tributary slots can be equipped with the 2x155M and 2x622M/8x155M circuit packs.

– The 2x155M circuit pack supports 2 STM-1 optical / electrical (o/e) or OC-3 optical ports.

– The 2x622M/8x155M circuit pack supports 2 STM-4/OC-12 ports, 8 STM-1/OC-3 ports or 1 STM-4/OC-12 and 4 STM-1/OC-3 ports with SFP optical interfaces. Please refer to 2x622M/8x155M circuit pack modes of operation on page 4-51 for additional details.

— The 1x2.5G+4x155M/2x622M aggregate card have integrated 155M or 622M tributary ports.

– The 1x2.5G+4x155M/2x622M aggregate card supports 4 STM-1/OC-3 or 2 STM-4/OC-12 tributary ports with SFP optical interfaces. Please refer to 1x2.5G+4x155M/2x622M aggregate circuit pack on page 4-19 for details on the modes of operation of the 1x2.5G+4x155M/2x622M aggregate card.


1-6 Introduction

Small form-factor pluggable interfacesThe 6130 uses small form-factor pluggable (SFP) interfaces to deliver optical rate and reach flexibility on a per port basis for the line interface. The 6130 also supports electrical SFP for the STM-1e and 1000Base-T interface.

The 6130 offers the following SFP interface types: SR-0, SR-1/I-16, IR-1/S-1.1/S-4.1/S-16.1, LR-1/L-1.1/L-4.1/L-16.1, LR-2/L-1.2/L-4.2/L-16.2, CWDM, DWDM, STM-1e, 100Base-LX10, 100Base-BX10-U, 100Base-BX10-D, GE SX, GE LX, 1000Base-BX10-U, 1000Base-BX10-D, 1000Base-ZX and 1000-Base-T electrical.

Ciena has been collaborating closely with leading SFP vendors to improve the reliability, robustness and manageability of SFPs. The use of such carrier-grade SFP technology enables service providers to enjoy the flexibility of provisioning the interfaces per the requirements of the specific application.

SFPs also reduce the cost of sparing by enabling an upgrade of the optical line interfaces as they become readily available.

Figure 1-3Pluggable optical modules summary

Point-to-point optical broadband servicesThe 6130 uses GFP, VCAT and LCAS standards for the mapping and transport of Ethernet services.

GFP provides an efficient mechanism for Ethernet transport over a SDH/SONET core network via efficiently mapping varying client signals into SDH/SONET VC-12/VT2, VC-11/VT1.5, VC-3/STS and VC-4/STS-3c frames. GFP mapping enables efficient network resource utilization with low overhead requirements, and limited over-provisioning with VCAT. End-to-end framing provides demarcation for the Ethernet signal, and enables consistent SDH/SONET based PMs through the network. Since the Ethernet is mapped into SDH/SONET frames, the existing core network can transport the Ethernet frames transparently.

Small-form factor pluggable (SFP)

155/622 Mbit/s- Carrier grade- Service tolerance: - Reach (SR/IR/LR) - Rate (OC-3/STM-1, OC-12/STM-4 future) - GE (future) - CWDM with wavelength per pluggable slot- Operational simplification- Expenditure matched with reach requirements- CAPEX savings through reduced sparing


Introduction 1-7

The 6130 also supports Virtual Concatenation (ITU-T G.707 compliant) with support at the VC-11-nv, VC-12-nv, VC-3-nv and VC-4-nv SDH rates as well as VT1.5-nv, VT-2-nv, STS-1-nv and STS-3c-nv SONET rates.

Along with VCAT the 6130 also supports value added capabilities such as soft protection via Link Capacity Adjustment Scheme (LCAS - G.7042). LCAS has been specifically developed to overcome static link provisioning. It enables service providers to efficiently offer dynamically-allocated bandwidth as well as hitless throttling of the capacity of a VCAT link (or Virtual Concatenated Group) by adding or removing VCs or VTs/STSs as required.

LCAS provides a soft protection and load-sharing mechanism to automatically decrease the link capacity if a VC or VT/STS path experiences a failure and automatically increases the link capacity when the network fault is repaired. This capability provides an extra level of network and service resiliency by facilitating the support of SLAs through graceful service degradation when necessary. In particular, during network and service restoration LCAS can support hitless bandwidth expansion and contraction thereby reducing service interruptions in the event of network failure and easing network operations and maintenance actions.

TDM switchingIn the 6130 architecture, traffic is switched between working and protection line interfaces via the switch matrix in the aggregate circuit pack(s).

All ingress service traffic is mapped into VC-11/VT1.5, VC-12/VT2, VC-3/STS-1, VC-4/STS-3c or VC-4-4c/STS-12c containers and directed towards the switch matrix which is configured to switch the incoming traffic to the appropriate line interface. The switch matrix allows any input channel to be connected to any output channel. Hairpinning is also supported between client ports.

Layer 2 switchingThe 6130 supports the Layer 2 Packet Aggregation (L2PA) and the EoPDH circuit pack to help aggregate and switch Ethernet services. Designed for carrier grade reliability, manageability, broadband data rates, and service flexibility, the L2PA circuit packs provides a strong Ethernet services and infrastructure solution for IP, Ethernet Private LANs, Ethernet VPNs, Ethernet Virtual Private Lines, Triple Play Services, and Internet access solutions.In addition to the L2PA circuit packs, the EoPDH circuit packs supports Ethernet Virtual Private Lines and Ethernet Virtual Private LANs.

Ethernet Ring Protection (ERP) is supported with the L2PA and EoPDH circuit packs. The ERP Standard (G.8032) is also referred to as E-SPRing and it provides sub 50ms protection mechanism for the Ethernet traffic.


1-8 Introduction

Transparent IGMP snooping (V1, V2 and V3) is supported with the L2PA circuit pack as per RFC 4541.

With the L2PA and EoPDH circuit pack, Ciena continues its technology direction to support Ethernet over GFP for transport over SDH/SONET as demonstrated in our 6500, OM3000, OM4000, and 5000 product lines.

The L2PA also supports virtual and contiguous concatenation as well as LCAS (for VCAT) in order to ensure that packet traffic is most efficiently, reliably, and deterministically carried over the transport network. The L2PA circuit pack supports stacked VLAN switching, stacking, and MAC Switching for large scale and availability. The L2PA circuit pack supports both Ethernet UNI (User-to-Network interfaces) such as VLAN and raw Ethernet as well as Ethernet NNI (Network-to-Network Interfaces) with stacked VLAN and includes point-to-point, point-to-multipoint, and any-to-any logical topologies.

For detailed information on Optical Ethernet services, 6130 L2PA concepts, applications, and engineering rules, see 6100 Data Application Guide, NTRN15CA.

6130 Input/Output (I/O) ModulesThe 6130 offers 1+1 and 1:3 protection for E1/DS1 tributaries and 1+1 protection for E3/DS3 tributaries.

I/O modules are required with the 28xE1/DS1(W/P) & 3xE3/DS3(W/P) circuit packs. The following E1/DS1 and E3/DS3 tributary protection (I/O) modules are supported:

— The I/O 28xE1/DS1 1+1 module supports 1+1 E1/DS1 tributary equipment protection.

— The I/O 84xE1/DS1 1:N module supports 1:N E1/DS1 tributary equipment protection.

— The I/O 3xE3/DS3 1+1 module supports 1+1 E3/DS3 tributary equipment protection.

Network managementThe 6130 is managed as an integral part of Ciena's market proven end-to-end optical portfolio management capabilities. This framework supports a sophisticated and highly customizable desktop providing centralized topology view and fault management, centralized launch pad for a full suite of management applications, easy to use nodal managers and seamless network element reach-through for Ciena's complete optical networks portfolio. These network management capabilities are supported by 6100 Site Manager, the Optical Network Manager (formerly known as Preside) and Optical Manager Element Adapter (OMEA), in alignment with Ciena overall optical networks portfolio.


Introduction 1-9

The 6130 local craft access terminal, which is an HTTP/HTTPS web-based graphical interface running on the network element, provides complete nodal management that can be integrated into a centralized network wide view through the Optical Network Manager.

Key features and benefits The 6130 multi-services access platform provides customers with the flexibility, scalability and management capabilities they need in a compact cost effective package. The key benefits to customers of deploying the 6130 can be summarized as follows:

• support of a broad set of services (Ethernet, PDH/Async and SDH/SONET)

— integrated L2 packet aggregation (L2PA) and switching

— ELINE and ELAN L2 services (EoPDH)

— switching granularity and flexibility for service grooming and connection management, such as unconstrained VC-11/VT1.5 and VC-12/VT2 level switching

• cost-efficient service deployment through

— low cost entry configuration for E1/DS1 and E3/DS3 services

— in-service expansion to support new services

— dynamically pluggable optical and electrical SFP interfaces (lowers sparing costs)

— flexible, complete and easy to use network and service management leading to simplified operations for rolling out and maintaining services


1-10 Introduction


2-1

Feature overview 2-

This chapter provides an overview of the 6130 Release 5.0 supported features. The 6130 Release 5.0 network element can be commissioned in SDH or SONET mode and supports optical interfaces (STM-1/STM-4/STM-16/OC-3/OC-12/OC-48), electrical STM-1e interface as well as transport of 10/100Base-T (10/100BT) Ethernet, 100Base-FX (100FX) Ethernet, Gigabit Ethernet (GE) and PDH/DSn services.

Table 2-1 lists the features available in the 6130. For more information about these features, refer to the appropriate reference in this planning guide. The following sections in this chapter give a brief description of the main features.

Table 2-1Summary of features for current releases

Topic R1.0 R2.0 R3.0 R4.0 R5.0 Reference

Modes of operation

SDH Yes Yes Yes Yes Yes SDH and SONET Configurations on page 6-2SONET No Yes Yes Yes Yes

Equipment redundancy for Aggregate circuit packs

Non-redundant Yes Yes Yes Yes Yes Equipment protection on page 6-25

Redundant (1+1 equipment protection)

No Yes Yes Yes Yes


2-2 Feature overview

6130 hardware

Chassis Yes Yes Yes Yes Yes Chassis on page 4-4

2x155/622M Aggregate circuit pack Yes Yes Yes Yes YesAggregate circuit packs on page 4-11

Note: The 1x2.5G Aggregate circuit pack is supported in Rel.4.1. (Refer to NT6Q64BE R4.1 Addendum)

1x155/622M Aggregate circuit pack No Yes Yes Yes Yes

1x2.5G Aggregate circuit pack No Yes Yes Yes No

1x2.5G+4x155M/2x622M No No No Yes Yes

Single feed DC power supply unit Yes Yes Yes Yes YesPower supply unit on page 4-7Single feed AC power supply unit No No Yes Yes Yes

Fan module Yes Yes Yes Yes Yes Fan module on page 4-9

OAM unit Yes Yes Yes Yes Yes OAM circuit pack on page 4-10

Filler faceplate Yes Yes Yes Yes Yes Filler faceplate on page 4-58

75 ohm termination panel Yes Yes Yes Yes Yes E1 75 ohm termination panel on page 4-58

Table 2-1 (continued)Summary of features for current releases



Feature overview 2-3

Tributary interface circuit packs

Transmux No No No No Yes

Tributary interface circuit pack on page 4-22

8xGE EoPDH L2 (with NT6Q48xx 1x2.5G+4x155M/2x622M Agg. Card)

No No No No Yes

8xETH Yes Yes Yes Yes Yes

4x10/100BT+4x100FX L1 No Yes Yes Yes Yes

4x10/100BT+4x100FX L1 622M No No No Yes Yes

2xGE Yes Yes Yes Yes Yes

2xGE+8x10/100BT L1 1.2G No No Yes Yes Yes

L2PA622M No Yes Yes Yes Yes

L2PA1G2 No No Yes Yes Yes

28xE1/DS1 Yes Yes Yes Yes Yes

63xE1/DS1 (R4.0 supports only E1) No No No Yes Yes

28xE1/DS1(W/P) No No Yes Yes Yes

3xE3/DS3 Yes Yes Yes Yes Yes

3xE3/DS3(W/P) No No Yes Yes Yes

2x155M Yes Yes Yes Yes Yes

2x622M/8x155M No No Yes Yes Yes

I/O Modules

I/O 28xE1/DS1 1+1 No No Yes Yes YesI/O Modules on page 4-55I/O 84xE1/DS1 1:N No No Yes Yes Yes

I/O 3xE3/DS3 1+1 No No Yes Yes Yes





SFP modules

STM-1/OC-3 SR-0 1310 nm Yes Yes Yes Yes Yes

Small form-factor pluggable (SFP) modules on page 8-23

STM-1/4/OC-3/12 IR-1/S-1.1/S-4.1 1310 nm

Yes Yes Yes Yes Yes

STM-1/4/OC-3/12 LR-1/L-1.1/L-4.1 1310 nm

Yes Yes Yes Yes Yes

STM-1/4/OC-3/12 LR-2/L-1.2/L-4.2 1550 nm

Yes Yes Yes Yes Yes

STM-1/4/16/OC-3/12/48 CWDM Yes Yes Yes Yes Yes

STM-1e Yes Yes Yes Yes Yes

STM-16/OC-48 SR-1/I-16 1310 nm No Yes Yes Yes Yes

STM-16/OC-48 IR-1/S-16.1 1310 nm No Yes Yes Yes Yes

STM-16/OC-48 LR-1/L-16.1 1310 nm No Yes Yes Yes Yes

STM-16/OC-48 LR-2/L-16.2 1550 nm No Yes Yes Yes Yes

STM-16/OC-48 DWDM No No Yes Yes Yes

100Base-LX10 No Yes Yes Yes Yes

100Base-BX10-U, 100Base-BX10-D Yes Yes Yes Yes Yes

GE SX, LX Yes Yes Yes Yes Yes

GE ZX No No No No Yes

1000Base-BX10-U,1000Base-BX10-D

No Yes Yes Yes Yes

1000BaseT No No No No Yes

GE electrical 1000-BaseT No No Yes Yes Yes





Configurations

1+1 MSP Yes Yes Yes Yes Yes1+1 MSP/APS on page 3-11+1 APS No Yes Yes Yes Yes

SNCP Yes Yes Yes Yes YesSNCP/UPSR on page 3-2UPSR No Yes Yes Yes Yes

MS-SPRing/BLSR (STM-16/OC-48 ports on 1x2.5G+4x155M/2x622M Aggregate card only)

No No No Yes Yes MS-SPRing/BLSR on page 3-2

Unprotected Yes Yes Yes Yes Yes Unprotected configuration on page 3-3

Line rate upgrades

STM-1/OC-3 to STM-4/OC-12 line rate upgrades

No No No Yes Yes Aggregate circuit packs on page 4-11

STM-4/OC-12 to STM-16/OC-48 line rate upgrades

No No No Yes Yes

Equipment and facility management

Equipment management Yes Yes Yes Yes Yes Equipment management on page 6-5

Facility Management Yes Yes Yes Yes Yes Facility management on page 6-7

Connection management

VC11, VC12, VC3 and VC4 cross-connects

Yes Yes Yes Yes Yes

Connection management on page 6-17

VT1.5, VT2, STS-1 and STS-3c cross-connects

No Yes Yes Yes Yes

VC4-4c/STS-12c cross-connects No No Yes Yes Yes





Service Mapping

100/1000BT Ethernet GFP-F to E1, E3, DS1 or DS3

No No No No Yes

Generic Framing Procedure on page 6-20

Gigabit Ethernet GFP-F to E1, E3, DS1 or DS3

No No No No Yes

10/100BT Ethernet GFP-F to VC11, VC12, VC3, VC4

Yes Yes Yes Yes Yes

10/100BT Ethernet GFP-F to VC11-nv, VC12-nv, VC3-nv (virtual concatenation)

Yes Yes Yes Yes Yes

10/100BT Ethernet GFP-F to VT1.5, STS-1, STS-3c

No Yes Yes Yes Yes

10/100BT Ethernet GFP-F to VT1.5-nv, STS-1-nv (virtual concatenation)

No Yes Yes Yes Yes

100FX Ethernet GFP-F to VC11/VT1.5, VC12, VC3/STS-1

No Yes Yes Yes Yes

100FX Ethernet GFP-F to VC11/VT1.5-nv, VC12-nv, VC3/STS-1-nv (virtual concatenation)

No Yes Yes Yes Yes

Gigabit Ethernet GFP-F to VC11, VC12, VC3, VC4

Yes Yes Yes Yes Yes

Gigabit Ethernet GFP-F to VC11-nv, VC12-nv, VC3-nv, VC4-nv (virtual concatenation)

Yes Yes Yes Yes Yes

Gigabit Ethernet GFP-F to VT1.5, STS-1, STS-3c

No Yes Yes Yes Yes

Gigabit Ethernet GFP-F to VT1.5-nv, STS-1-nv, STS-3c-nv (virtual concatenation)

No Yes Yes Yes Yes





E1 to VC12 Yes Yes Yes Yes Yes

Connection management application on page 6-24

DS1 to VC11 Yes Yes Yes Yes Yes

E3 to VC3 Yes Yes Yes Yes Yes

DS3 to VC3 Yes Yes Yes Yes Yes

E1 to VT2 No Yes Yes Yes Yes

DS1 to VT1.5 No Yes Yes Yes Yes

E3 to STS-1 No Yes Yes Yes Yes

DS3 to STS-1 No Yes Yes Yes Yes

Traffic protection

1+1 MSP - STM-1/4 Yes Yes Yes Yes Yes 1+1 MSP/APS traffic protection on page 6-30

1+1 MSP/APS - STM-16/OC-3/12/48 No Yes Yes Yes Yes

SNCP Yes Yes Yes Yes Yes SNCP/UPSR Traffic Protection on page 6-33

UPSR No Yes Yes Yes Yes

MS-SPRing/BLSR No No No Yes Yes 2-Fiber MS-SPRing/BLSR traffic protection on page 6-34

Unprotected - STM-1/4 Yes Yes Yes Yes Yes Unprotected connections on page 6-38Unprotected - STM-16/OC-3/12/48 No Yes Yes Yes Yes

Equipment Protection

1+1 E1/DS1 protection No No Yes Yes YesEquipment protection on page 6-251:3 E1/DS1 protection No No Yes Yes Yes

1+1 E3/DS3 protection No No Yes Yes Yes





Synchronization

Internal, BITS, line, port Yes Yes Yes Yes Yes

Synchronization management on page 6-11

Timing generation hierarchy Yes Yes Yes Yes Yes

Timing distribution hierarchy Yes Yes Yes Yes Yes

SDH SSM generation/termination Yes Yes Yes Yes Yes

SONET SSM generation/termination No Yes Yes Yes Yes

2 MHz and 2 Mbits/s ESI/ESO with SSM

Yes Yes Yes Yes Yes

DS1 ESI/ESO with SSM No Yes Yes Yes Yes

Alarms and events

LEDs indication of shelf and circuit pack status

Yes Yes Yes Yes Yes

Alarm and event management on page 6-45

Alarm and event reporting Yes Yes Yes Yes Yes

Alarm reporting control Yes Yes Yes Yes Yes

RS, MS, HO path, LO path alarms Yes Yes Yes Yes Yes

Section, Line, STS-1, VT alarms No Yes Yes Yes Yes

STM-1/4, E1/DS1, E3/DS3 alarms Yes Yes Yes Yes Yes

STM-16/OC-3/12/48 alarms No Yes Yes Yes Yes

Ethernet and VCG (WAN) alarms Yes Yes Yes Yes Yes

Performance monitoring

SDH RS, MS and path Yes Yes Yes Yes Yes

Performance monitoring on page 6-51

SONET Section, Line and path No Yes Yes Yes Yes

Transceiver (physical PM for SFPs) Yes Yes Yes Yes Yes

Ethernet and VCG (WAN) Yes Yes Yes Yes Yes

E1/DS1/E3/DS3 PM parameters Yes Yes Yes Yes Yes

System lineup and testing

SLAT (commissioning tool) Yes Yes Yes Yes Yes System Line-up and Test (SLAT) on page 6-3





Loopbacks

Facility and Terminal Loopbacks(STM-1/4, E1, DS1, E3, DS3, GE)

Yes Yes Yes Yes Yes

Loopbacks on page 6-9

Facility and Terminal Loopbacks(STM-16/OC-3/12/48)

No Yes Yes Yes Yes

Terminal Loopback (10/100BT Ethernet)

Yes Yes Yes Yes Yes

Terminal Loopback (100FX Ethernet) No Yes Yes Yes Yes

Facility loopback (10/100BT, 100FX) No No Yes Yes Yes

NIU Loopback No No No No Yes

Data management

NE data backup and restore Yes Yes Yes Yes Yes Backing up and restoring the network element database on page 6-69

Security and administration

Local user account/password management

Yes Yes Yes Yes Yes

Security and administration on page 6-61

8 character password Yes Yes Yes Yes Yes

Inactivity timeout No No No Yes Yes

Account lockout after configured number of unsuccessful login attempts

No No No Yes Yes

Up to 100 named user accounts No No Yes Yes Yes

RADIUS Centralized Authentication No Yes Yes Yes Yes

Network element naming, date and time

Yes Yes Yes Yes Yes

Database changes log / audit trail No No Yes Yes Yes

Secure Shell (SSH) No No No No Yes

Autodiscovery

Autodiscovery of topology adjacency No Yes Yes Yes Yes Auto discovery on page 6-69





Data communication network

LAN, DCC physical interfaces Yes Yes Yes Yes Yes

Data communications on page 6-39 and Appendix A: Data communications planning on page 10-1

IP addressing Yes Yes Yes Yes Yes

OSI addressing Yes Yes Yes Yes Yes

IP over OSI GRE tunnel (auto or static)

Yes Yes Yes Yes Yes

PPP/LAPD over DCC Yes Yes Yes Yes Yes

OSPF and iISIS routing Yes Yes Yes Yes Yes

Route Redistribution No No No Yes Yes

Proxy ARP Yes Yes Yes Yes Yes

F1 user channel access Yes Yes Yes Yes Yes

OAM via Path DCC (F2/F3 bytes) Yes Yes Yes Yes Yes

E1/VC12 management channel Yes Yes Yes Yes Yes

Overhead tunnel (RS, MS, E1, E2, F1 bytes)

Yes Yes Yes Yes Yes

6130 management

Web User Interface - HTTP Yes Yes Yes Yes YesUser interface description on page 5-1Web User Interface - HTTPS No No No Yes Yes

SNMP v1 and v2 trap monitoring Yes Yes Yes Yes Yes

6100 Site Manager No No Yes Yes Yes

TL-1 Interface Yes Yes Yes Yes Yes

Interworking

Ciena portfolio Yes Yes Yes Yes Yes Interworking with Ciena portfolio on page 2-25

non-Ciena portfolio Yes Yes Yes Yes Yes Interoperating with non-Ciena portfolio on page 2-25

Software upgrades

Network element upgrade Yes Yes Yes Yes Yes Installing and upgrading network element on page 6-70





Physical descriptionThe 6130 platform consists of a chassis which fits in a standard 19 in., 21 in., or 23 in. rack. The chassis is equipped with the following circuit packs:

• aggregate circuit pack(s)

– non-redundant configuration: one 2x155/622M aggregate circuit pack required

– redundant configuration: two 1x155/622M aggregate circuit packs or two 1x2.5G aggregate circuit packs or two 1x2.5G+4x155M/2x622M aggregate circuit packs required.

• up to 4 service interfaces:

– Transmux

– 8xGE EoPDH L2

– 8xETH circuit pack

– 4x10/100BT+4x100FX L1 circuit pack

– 4x10/100BT+4x100FX L1 622M circuit pack

– 2xGE circuit pack

– 2xGE+8x10/100BT L1 1.2G circuit pack

– L2PA622M circuit pack

– L2PA1G2 circuit pack

– 28xE1/DS1 circuit pack

– 63xE1/DS1circuit pack

– 28xE1/DS1(W/P) circuit pack


– 3xE3/DS3(W/P) circuit pack

– 2x155M circuit pack

– 2x622M/8x155M circuit pack

• two single feed AC or DC power supply unit

• OAM circuit pack

• fan module

• filler faceplate



Figure 2-1 provides an overview of the 6130 chassis layout.

Figure 2-16130 chassis layout

For more information, refer to “Hardware description” on page 4-1 and “6130 network element configuration rules” on page 8-2.

Interface circuit packsThe 6130 Release 5.0 supports the following configurations for the aggregate circuit pack(s):

• non-redundant configuration:

— STM-1/OC-3 or STM-4/OC-12 line interfaces:

– one 2x155/622M aggregate circuit pack is required per shelf

– two STM-1/OC-3 or STM-4/OC-12 line interfaces are supported per circuit pack

• redundant configurations (1+1 equipment protection):

— STM-1/OC-3 or STM-4/OC-12 line interfaces:

– two 1x155/622M aggregate circuit packs are required per shelf

– one STM-1/4/OC-3/12 line interface is supported per circuit pack

PSU (2) OAM I/O slots (2) Aggregate slots (2) Fan

Tributary slots (4)



— STM-4/16/OC-12/48 line interfaces:

– two 1x2.5G aggregate circuit packs are required per shelf


— STM-4/16/OC-12/48 line interfaces and STM-1/4/OC-3/12 tributary interfaces on the aggregate circuit pack:

– two 1x2.5G+4x155M/2x622M aggregate circuit packs are required per shelf


– four STM-1/OC-3 or two STM-4/OC-12 tributary interfaces per circuit pack.

The 6130 also supports four tributary slots that can be equipped with the following circuit packs:

• Transmux

• 8xGE EoPDH L2

• 8xETH circuit pack

• 4x10/100BT+4x100FX L1 circuit pack

• 4x10/100BT+4x100FX L1 622M circuit pack

• 2xGE circuit pack

• 2xGE+8x10/100BT L1 1.2G

• L2PA622M circuit pack

• L2PA1G2 circuit pack

• 28xE1/DS1 circuit pack

• 63xE1/DS1circuit pack

• 28xE1/DS1(W/P) circuit pack



• 2x155M circuit pack

• 2x622M/8x155M circuit pack

Attention: When the tributary slots are not equipped with a circuit pack, a filler panel must be installed.



Table 2-2 provides a summary of the tributary circuit packs supported in 6130 Release 5.0.

Table 2-26130 tributary circuit pack summary

Circuit pack Port density/ circuit pack

Notes

Transmux 6 • unframed E3• G.832 framed E3• unframed DS3• ASYNC DS3• ASYNC M13 DS3

8xGE EoPDH L2 8 • GFP-F mapped (ITU-T G.7041 compliant)

8xETH 8 • GFP-F mapped (ITU-T G.7041 compliant)

4x10/100BT+4x100FX L1

8 • GFP-F mapped (ITU-T G.7041 compliant)

4x10/100BT+4x100FX L1 622M


2xGE 2 • GFP-F mapped (ITU-T G.7041 compliant)

2xGE+8x10/100BT L1 1.2G


L2PA622M 10 • GFP-F mapped (ITU-T G.7041 compliant)

L2PA1G2 10 • GFP-F mapped (ITU-T G.7041 compliant)

28xE1/DS1 28 • unframed E1• CRC4 framed E1• unframed DS1• ESF DS1

63XE1/DS1 63 • unframed E1• CRC4 framed E1

28xE1/DS1(W/P) 28 • unframed E1• CRC4 framed E1• unframed DS1• ESF DS1• 1+1 and/or 1:N protection

3xE3/DS3 3 • unframed E3• G.832 framed E3• unframed DS3• ASYNC framed DS3



For more information about the tributary circuit packs, refer to Tributary interface circuit pack on page 4-22. For more information about slot equipping rules, refer to Chassis layout on page 8-2.

System Line-up and Test (SLAT)This release supports the ability to configure the system when it is being commissioned for the first time. The user is given an option to initialize the system with a configuration compatible with the NE.

The 6130 Release 5.0 supports SDH and SONET modes of operation and the user is given the choice of initializing the NE in either mode of operation during SLAT.

When the 2x155/622M aggregate circuit pack is used, the node capability is provisioned to either STM-1/OC-3 or STM-4/OC-12 during initial commissioning and cannot be edited.

When the 1x155/622M aggregate circuit packs is used, the node capability is provisioned to either STM-1/OC-3 or STM-4/OC-12 during initial commissioning. It is supported to upgrade the line rate without having to re-commission the shelf.

When the 1x2.5G or 1x2.5G+4x155M/2x622M aggregate circuit packs are used, the node capability is provisioned to either STM-4/OC-12 or STM-16/OC-48 during initial commissioning. It is supported to upgrade the line rate without having to re-commission the shelf.

For more information, refer to System Line-up and Test (SLAT) on page 6-3

3xE3/DS3(W/P) 3 • unframed E3• G.832 framed E3• unframed DS3• ASYNC framed DS3• 1+1 protection

2x155M 2 • STM-1/OC-3 optical and electrical SFPs supported

2x622M/8x155M 8 (see Note) • STM-1/4/OC-3/12 optical SFPs supported. STM-1 electrical SFPs supported

Note: Please refer to 2x622M/8x155M circuit pack modes of operation on page 4-51 for details on supported modes of operation.

Table 2-2 (continued)6130 tributary circuit pack summary

Circuit pack Port density/ circuit pack

Notes



Configurations6130 currently supports the following configurations for the line interfaces.

1+1 MSP/APS protection6130 supports 1+1 Multiplex Section Protection (MSP)/Automatic Protection Switching (APS) configurations. For more information, refer to 1+1 MSP/APS on page 3-1.

SNCP/UPSR6130 supports Sub-network connection protection (SNCP)/Unidirectional path switched ring (UPSR) ring configurations.

In a SNCP/UPSR configuration, traffic is transmitted simultaneously on two separate ports. The traffic is transmitted via different routes through the network to the destination node which selects one of the two paths based on the quality of the received signal. For example, in a ring configuration, the traffic can be transmitted simultaneously on the working fiber in the clockwise direction and on the protection fiber in the counter-clockwise direction.

For more information, refer to SNCP/UPSR on page 3-2.

MS-SPRing/BLSR protection6130 supports Multiplex Section - Shared Protection Ring (MS-SPRing)/Bidirectional Line Switched Ring (BLSR) configurations. For more information, refer to MS-SPRing/BLSR on page 3-2.

Unprotected6130 supports unprotected configurations. For more information, refer to Unprotected configuration on page 3-3.



Connection management6130 supports nodal port-to-port connection management. 6130 supports the ability to provision bidirectional and unidirectional connections at VC11/VT1.5, VC12/VT2, VC3/STS-1, VC4/STS-3c and VC4-4c/STS-12c rates.

6130 Release 5.0 supports various bandwidth management models that include the following;

• bidirectional connections

• unidirectional connections

• port to port (hair-pinning)

• drop and continue

Attention: Only bidirectional connection type is supported for WAN ports corresponding to the 10/100BT Ethernet, 100FX Ethernet and Gigabit Ethernet ports.

For more information, refer to Connection management on page 6-17.

Service mappingAll services (Ethernet, E1, DS1, E3, and DS3) are mapped to appropriate SDH/SONET containers and tributaries. Eth

The 6130 uses Generic Framing Procedure (GFP) as its standards based SDH/SONET mapping for Ethernet services. GFP is an ITU standard (G.7041) which describes a flexible mapping technique for transparent transport of multiple protocols in SDH. GFP-Framed (GFP-F) is used for mapping Ethernet to SDH/SONET tributaries and containers. In Release 5.0, mapping Ethernet to PDH is supported.



Table 2-3 provides a summary of the service mappings supported in this release.

For more information, refer to Connection management on page 6-17.

Table 2-36130 service mapping

Services Circuit Pack Mapping/connection level supported

100/1000BT Ethernet

Gigabit Ethernet

• 8xGE EoPDH L2 • GFP-F to E1, E3

• GFP-F to DS1, DS3

10/100BT Ethernet • 8xETH • GFP-F to VC12, VC3, VC4

• GFP-F to VT1.5, STS-1, STS-3c

10/100BT Ethernet100FX Ethernet

• 4x10/100BT+4x100FX L1

• 4x10/100BT+4x100FX L1 622M

• GFP-F to VC12, VC3, VC4


Gigabit Ethernet • 2xGE • GFP-F to VC3, and VC-4

• GFP-F to STS-1, and STS-3c

Gigabit Ethernet 10/100BT Ethernet

• 2xGE+8x10/100BT L1 1.2G

• GFP-F to VC11, VC12, VC3, and VC4

• GFP-F to VT1.5, STS-1, and STS-3c

10/100BT Ethernet100FX Ethernet Gigabit Ethernet

• L2PA622M • GFP-F to VC11, VC12, VC3, VC-4


10/100BT Ethernet100FX Ethernet Gigabit Ethernet

• L2PA1G2 • GFP-F to VC11, VC12, VC3, VC4


E1/DS1 • 28xE1/DS1

• 63XE1/DS1

• 28xE1/DS1(W/P)

• VC12/VT2, VC11/VT1.5

E3/DS3 • 3xE3/DS3

• 3xE3/DS3(W/P)

• VC3/STS-1

• Transmux • AU4/STS-1



Traffic protection6130 supports 1+1 MSP/APS and SNCP/UPSR traffic protection. The system monitors the traffic facilities for performance degradation and failure and performs protection switching when these conditions are present. Table 2-4 provides a summary of the protection schemes supported in this release.

Equipment Protection6130 supports equipment protection for the 1x155/622M, 1x2.5G and 1x2.5G+2x622M/4x155M aggregate cards. Equipment protection is also supported for E1/DS1 services and E3/DS3 services with the 28xE1/DS1(W/P), 3xE3/DS3(W/P) and Transmux circuit packs.

For more information, refer to Equipment protection on page 6-25.

Table 2-4Traffic protection summary

Protection scheme Supported interfaces or circuit packs

1+1 MSP/APS • STM-1/4/16/OC-3/12/48 interfaces

SNCP/UPSR • STM-1/4/16/OC-3/12/48 interfaces

MS-SPRing/BLSR • STM-16/OC-48 interfaces of the 1x2.5G+4x155M/2x622M aggregate cards only

Unprotected (default for all supported interfaces)

• STM-1/4/16/OC-3/12/48 interfaces





• 2xGE+8x10/100BT L1 1.2G circuit pack




• 63xE1/DS1






SynchronizationSynchronization is a network level application that ensures all nodes across a network can trace back to the same clock source. Within a single node, synchronization prevents buffer overflow or underflow which avoids bit errors.

For more information, refer to Synchronization management on page 6-11.

Alarms and eventsThe 6130 provides several mechanisms to identify and localize faults and events.

• light-emitting diodes (LEDs) on the faceplate of a circuit pack indicate the status of the functionality supported on the equipment

— circuit pack failed on all circuit packs

— loss of signal on interface circuit packs

— power LED on the OAM circuit pack provides the power status

• visual alarms interface on the OAM circuit pack provides a summary of active alarms at the shelf level

The 6130 stores active alarms and events which can be viewed from the local craft access terminal.

The following alarm reporting control features are supported: profile based path alarm control, alarm filter, and facility alarm reporting. The user has the option to enable or disable alarm reporting to the management system, on a per alarm type and per port basis.

For more information, refer to Alarm and event management on page 6-45.



Performance monitoringPerformance monitoring (PM) refers to the continuous collection, analysis and reporting of the performance data of a monitored entity. This monitoring allows early detection of service degradations and facilitates preventive maintenance without interruption of service. PMs can also be used to facilitate trouble and fault isolation. Performance monitoring is performed on all in-service optical and electrical interface ports.

This release supports the following PMs:

• regenerator section (RS)/section near-end PMs

• multiplex section (MS)/line near-end and far-end PMs

• High Order (HO)/STS near-end and far-end path PMs

• Low Order (LO)/VT near-end and far-end path PMs

• physical layer PMs for all SFP interfaces

• Ethernet (client facing) and WAN (GFP-F mapped - line facing) PMs

• PDH/DSn line PMs and near-end path PMs

The 6130 allows the user to retrieve:

• current PM values (15 minute and 1-Day values in progress)

• recent history (32 previous 15 minute and previous day values stored on the network element)

The 6130 supports threshold crossing alerts (TCA) to advise the user when a PM parameter threshold has been exceeded. The user can enable or disable the TCAs for the RS/section, MS/line, and SDH/SONET path parameters and when enabled, the PM thresholds are user-provisionable.

For more information, refer to Performance monitoring on page 6-51.

LoopbacksThe 6130 supports facility loopbacks on the STM-1/4/16/OC-3/12/48, PDH/DSn, 10/100BT, 100FX and GE ports, and terminal loopbacks on all ports. The loopbacks provide a quick and reliable way to sectionalize connections during testing and troubleshooting.

Attention: Only terminal loopbacks are supported on the 10/100BT and 100FX ports of the 8xETH and 4x10/100BT+4x100FX circuit packs. Loopbacks are not supported on the Ethernet ports of the EoPDH.

For more information, refer to Loopbacks on page 6-9.



Data managementThe 6130 is responsible for the resilience of its provisioning data and ensures that a copy is preserved on flash. If the 6130 network element is equipped with two aggregate circuit packs (redundant configuration), then each piece of provisioning data exists on the two aggregate circuit packs. The active aggregate circuit pack contains a master copy of the configuration data and the inactive aggregate circuit pack contains a copy of the configuration data.

The 6130 provides the capability to backup and/or restore the provisioning data to/from an external storage device.

For more information, refer to Backing up and restoring the network element database on page 6-69.

Security and administrationThe 6130 provides the following security and administration capabilities managed from the Local Craft Access Terminal:

• Network element security

— RADIUS client for centralized authentication

— local user authentication

— local password management

— security levels

— login sessions

— Database changes log / audit trail

— Secure Shell (SSH)

• Network element administration

— network element naming

— date and time setting

For more information, refer to Security and administration on page 6-61.



AutodiscoveryAutodiscovery is used by the network management to build the network topology for end-to-end connection management. The network element transmits autodiscovery tags from the interface circuit packs using the internal DCN. Messages received from other network elements containing autodiscovery tags are stored and reported to the network management application. This process allows the network management application to build the topology.

When using OSPF on the DCC circuits, topology autodiscovery does not function across the DCC circuits using OSPF. Autodiscovery does function across DCC circuits using iISIS.

For more information, refer to Auto discovery on page 6-69.

Data communication network6130 uses an IP-based data communications infrastructure for network element management and for interworking with IP-based network elements. 6130 also supports IP over OSI via GRE for interworking with OSI-based network elements. iISIS is supported as the internal DCN routing protocol and can be enabled on the DCC interfaces.

The 6130 supports the following types of management interfaces:

• LAN port for interface to a data communications network (DCN). Proxy ARP is supported on the LAN port.

• M1/F1 port for modem and user data channel access.

• RS/section, MS/line and Path (F2, F3 and F2-F3) DCC for OAM&P access to remote network elements

• management channel via VC12 circuit or E1 channel

• overhead tunnel provisioning for DCC transparency (for interoperability with other vendors’ equipment)

For more information, refer to Data communications on page 6-39. For more information on DCN planning, refer to Appendix A: Data communications planning on page 10-1.



6130 managementLocal Craft Access Terminal

The 6130 supports a comprehensive suite of OAM&P functionality which can be managed through a web-based local craft access user interface. The local craft user interface is a graphical, nodal management tool that is inherent on the network element software load and can be launched via a web browser.

The local craft access user interface is launched from a web browser which can be running on Windows, UNIX or Solaris workstations ensuring field technicians and NOC operators are operating with the same view.

For more information, refer to User interface description on page 5-1.

Site managerThe 6130 supports a comprehensive suite of OAM&P functionality which can be managed through the Site Manager craft user interface. The Site Manager craft user interface is a graphical, nodal management tool that is available on a CD.

The Site Manager craft user interface is platform independent, running natively on Windows, UNIX and Solaris workstations ensuring field technicians and network operations centre (NOC) operators are operating with the same view. For more information, refer to 6100 Site Manager on page 5-2.

TL1 user interfacesTransaction Language 1 (TL1) is an industry recognized common language protocol that allows an operating system to communicate with different vendor equipment.

6130 provides a TL1 command line interface (CLI). The TL1 CLI is a standard command line interface. The 6130 TL1 interface conforms to standards GR-831, GR-833, and GR-199 for syntax, information structure, and transactions.

For more information, refer to TL1 interface on page 5-3.

SNMP trapsThe 6130 system events can be monitored through SNMP traps raised by the NE, based on the MIB tables.

SNMP Get for Ethernet PMs is supported, refer to technical publication 323-1855-201.

For more information, refer to SNMP traps on page 5-4.



Interworking with Ciena portfolio The 6130 interworks with the following products:

• Ciena Optical Network Manager (ONM)

• Ciena products through STM-1/4/16/OC-3/12/48 interfaces

6130 Release 5.0 operates with the following network management software:

• Optical Solution Release (OSR) Rel. 17 (for Rel.4.1)

– Optical Manager Element Adapter (OMEA) Release 10.0

In this release, the 6130 interworks with:

• 6110, 6150, Optical Metro 3000/4000-series, the TransportNode TN-1C/1X, and the 6500 products through STM-1/4/16/OC-3/12/48 interfaces.

For more information, refer to 6130 interworking with other products on page 3-5.

Interoperating with non-Ciena portfolioThe 6130 is a standards compliant product that can operate with subtending products that support standard compliant STM-1/4/16/OC-3/12/48 interfaces. You must note that multi-vendor mid span meet applications depend on the configuration and MSP/APS mode of interest.




3-1

Configurations, upgrades, and interworking 3-

This chapter describes how the 6130 Release 5.0 fits in a network and interworks with other Ciena products. This chapter also describes the upgrade considerations for 6130. Table 3-1 lists the topics in this chapter.

For an overview of the 6130 applications supported by this release, refer to 6130 applications on page 1-3.

1+1 MSP/APS1+1 Multiplex Section Protection (MSP)/Automatic Protection Switching (APS) configuration is a line level traffic protection scheme and consists of a point-point configuration with two optical fiber pairs carrying the traffic (one for working and the other for protection). The 1+1 MSP protection is also supported for STM-1e interface. Traffic is carried on both working and protection STM-1/4/16/OC-3/12/48 lines and the receiving interfaces determine which line to select based on signal quality or user-initiated actions.

Table 3-1Topics in this chapter

Topic Page

1+1 MSP/APS 3-1

SNCP/UPSR 3-2

MS-SPRing/BLSR 3-2

Unprotected configuration 3-3

Tributary Equipment Protection 3-3

Network reconfiguration 3-4

Upgrade support 3-4

6130 interworking with other products 3-5


3-2 Configurations, upgrades, and interworking

The 6130 supports 1+1 MSP/APS protection switching on the STM-1/4/16/OC-3/12/48 line interfaces.

For more information about 1+1 MSP/APS protection configuration rules, refer to Shelf equipping rules on page 8-5. For more information about the 1+1 MSP/APS protection scheme, refer to 1+1 MSP/APS traffic protection on page 6-30.

SNCP/UPSRA Sub-network connection protection (SNCP)/unidirectional path-switched ring (UPSR) is a path level traffic protection scheme. In SNCP/UPSR configuration, the destination node selects one of the two paths based on the quality of the received signal.

The 6130 supports SNCP/UPSR protection switching on the STM-1/4/16/OC-3/12/48 line interfaces on the network element.

For more information about SNCP/UPSR protection configuration rules, refer to Shelf equipping rules on page 8-5. For more information about the SNCP/UPSR protection scheme, refer to SNCP/UPSR Traffic Protection on page 6-33.

MS-SPRing/BLSRA 2-Fiber Multiplex Section - Shared Protection Ring (MS-SPRing)/ Bi-directional Line Switched Ring (BLSR) is a line level traffic protection scheme. A 2-Fiber MS-SPRing/BLSR is a ring network of nodes interconnected by a pair of optical fibers. Each optical fiber carries both working and protection channels, the bandwidth being divided into two equal halves, one half for working and the other half for protection. The user assigns traffic to the working channels in either direction around the ring. The protection channels travel around the ring in the opposite direction to the working channels that they protect.

The 6130 supports MS-SPRing/BLSR protection on a per-port basis provisionable through Site Manager or Node Manager (WUI) on the STM-16/OC-48 interfaces. The east and west pair of interfaces can be provisioned on the STM-16/OC-48 ports of the 1x2.5G+4x155M/2x622M aggregate card. A maximum of 16 nodes per MS-SPRing/BLSR configuration is supported.

For more information about MS-SPRing/BLSR protection configuration rules, refer to Shelf equipping rules on page 8-5. For more information about the MS-SPRing/BLSR protection scheme, refer to 2-Fiber MS-SPRing/BLSR traffic protection on page 6-34.


Configurations, upgrades, and interworking 3-3

Unprotected configuration6130 unprotected configuration on the STM-1/4/16/OC-3/12/48 line interface ports has a single pair of optical fibers interconnecting network elements. The unprotected configuration is supported for STM-1e interface. Unprotected connection configuration is also supported on all tributary circuit packs available in this release:

• 8xGE EoPDH L2

• Transmux






• L2PA622M circuit pack (name on circuit pack faceplate label is 2xGE/FX+8x10/100BT L2 622M)

• L2PA1G2 circuit pack (name on circuit pack faceplate label is 2xGE/FX+8x10/100BT L2 1G2)


• 63xE1/DS1






For more information about the unprotected protection scheme, refer to Unprotected connections on page 6-38.

Tributary Equipment Protection6130 supports 1+1 & 1:N (N=3) tributary protection for E3/DS3 and E1/DS1 services. 1+1, 1:N (N=3) tributary protection is supported for the following tributary circuit packs:

• 3xE3/DS3(W/P): 1+1

• 28xE1/DS1(W/P): 1+1 & 1:N (N=3)

• Transmux: 1+1



I/O modules are required with the 3xE3/DS3(W/P), 28xE1/DS1(W/P) and Transmux circuit packs. The following I/O modules are supported:

• 28xE1/DS1 1+1 I/O module

• 84xE1/DS1 1:N I/O module


For more information about the unprotected protection scheme, refer to Equipment protection on page 6-25.

Network reconfigurationThe network reconfiguration procedures are present in the Installation, Commissioning and Testing Procedures, 323-1855-201 and the following network reconfiguration procedures are described:

• Adding an 6130 NE to a STM-n SNCP ring configuration

• Deleting an 6130 NE from a STM-n SNCP ring configuration

Refer to the Network reconfiguration chapter in 323-1855-201 for more details on the standard supported procedures. 6130 also supports non-standard network reconfigurations. Contact your Ciena representative for more information.

Upgrade supportThis section provides information when planning upgrades on the 6130.

SoftwareThe 6130 supports the following in-service software upgrades:

• 6130 Release 3.0/3.0.1/4.0 (GA) to 6130 Release 5.0(GA)

• Shelf with 1x2.5G aggregate cards can be upgraded from 6130 Release 3.0/3.0.1/4.0 (GA) to 6130 Release 4.1(GA). Refer to NT6Q64BE R4.1 Addendum for more details.

Attention: Upgrades must be performed following a specific procedure. Refer to the upgrade change application procedure (CAP), NT6Q93MG, for more details and detailed upgrade procedures. Refer to Ordering information and system engineering rules on page 8-1 for ordering information.

HardwareNo hardware upgrades are required when upgrading to Release 5.0 unless you require the new functionality provided by new circuit packs.


Configurations, upgrades, and interworking 3-5

6130 interworking with other products6130 is compliant with SDH/SONET standards and therefore enables interworking with other SDH/SONET compliant network elements.

As shown in Table 3-2, 6130 Release 5.0 operates with the following network management software.

In order to be able to launch the Node Manager (WUI) from the Optical Network Manager (ONM AP) platform, a file needs to be installed on the ONM AP server. Refer to the Optical Manager Element Adapter Technical Publication Library, Installation and Configuration Guide, 450-3121-201 for more information.

Table 3-2Network management software that operates with 6130 Release 5.0

Product Releases Functionality

Optical Network Manager (ONM)Application Platform (AP)

AP 11.0 Patch A

• NE discovery

• Graphical network browser

• Fault management

• Craft reach through to NE Node Manager (WUI)

Optical Solution Release (OSR)

17.0 • OMEA 10.0

• OSP 10.0

• NSV 10.0

Optical Manager Element Adaptor (OMEA)

10

(for Rel.4.1)

• NE discovery

• Fault management

• Craft reach through to NE Node Manager (WUI)

• Connection services with OSP 8.0 / NSV 5.0

• PM data collection, storage an display

• Backup and restore

• Software delivery

• Autodiscovery of topology

6100 Site Manager 4.0 • Navigation Tree

• Login/Logout

• Alarms and Alarm Banner

• Shelf Level View

• Terminal session to the TL1 interface

• Launch of the 6130 WUI



As shown in Table 3-3, 6130 Release 5.0 interworks with Ciena products through STM-1/4/16/OC-3/12/48 interfaces or Ethernet/PDH/DSn interfaces. For more information on 6130 interworking rules and guidelines, refer to the Network Interworking Guide, NTCA68CA.

Interworking with MS-SPRing/BLSR configurationsInterworking is supported with MS-SPRing/BLSR configurations between the following products:

• 6130 and 6500 NEs that are part of the same MS-SPRing/BLSR ring

• 6130 and TN-16x NEs that are part of the same MS-SPRing/BLSR ring

• 6130 and 6150 NEs that are part of the same MS-SPRing/BLSR ring

Interoperability with non-Ciena portfolioSee Interoperating with non-Ciena portfolio on page 2-25 for more details.

Table 3-3Ciena products that interwork with 6130 Release 5.0

Product Release

6110 2.1 and higher

6130 1.0 and higher

6150 1.0 and higher

6500 3.0 and higher

Optical Metro 3100 4 & higher

Optical Metro 3400 11.1 & higher


Optical Metro 4100 4.9 & higher



5000 10.1 & higher

TN-1C 7 & higher

TN-1X 9 & higher

TN-16X 9 & higher

HDX/HDXc 3.3 & higher

OSPF interop with 6500 5 and higher


4-1

Hardware description 4-

This chapter provides an overview of the 6130 hardware. This chapter describes the 6130 chassis, modules and circuit packs, as listed in Table 4-1.


Topic Page

Hardware architecture 4-2

Chassis 4-4

Slot numbers 4-7

Power supply unit 4-7

Fan module 4-9

OAM circuit pack 4-10

Aggregate circuit packs 4-11

Tributary interface circuit pack 4-22

I/O Modules 4-55

Filler faceplate 4-58

E1 75 ohm termination panel 4-58

Cable routing 4-58

6130 Shelf assembly kit 4-59


4-2 Hardware description

Hardware architectureThe 6130 platform, as shown in Figure 4-2 and 4-3, consists of a chassis which can be equipped with the following circuit packs:

• one or two aggregate circuit pack(s)

• tributary interface circuit packs:

– 8xGE EoPDH L2

– Transmux

– 8xETH circuit pack

– 4x10/100BT+4x100FX L1 circuit pack

– 4x10/100BT+4x100FX L1 622M circuit pack

– 2xGE circuit pack

– 2xGE+8x10/100BT L1 1.2G circuit pack

– L2PA622M circuit pack (name on circuit pack faceplate label is 2xGE/FX+8x10/100BT L2 622M)

– L2PA1G2 circuit pack (name on circuit pack faceplate label is 2xGE/FX+8x10/100BT L2 1G2)



– 28xE1/DS1(W/P) circuit pack (requires I/O modules)


– 3xE3/DS3(W/P) circuit pack (requires I/O modules)

– 2x155M circuit pack

– 2x622M/8x155M circuit pack

• I/O modules:

– 28xE1/DS1 1+1 I/O

– 84xE1/DS1 1:N I/O

– 3xE3/DS3 1+1 I/O

• two AC or DC power supply unit


• fan module


Hardware description 4-3

Figure 4-16130 chassis dimensions (with I/O modules)

4U(without

176 mm(6.9 in.)

445 mm(17.5 in.)

295 mm (11.6 in.)

depth including cable routing brackets

231 mm (9.1 in.)depth (shelf only)

5U(with I/O

199 mm(7.9 in.)

modules)

I/O modules)



ChassisFigure 4-2 provides an overview of the 6130 chassis layout without I/O modules installed.

Figure 4-26130 chassis layout without I/O modules

Figure 4-3 provides an overview of the 6130 chassis layout with I/O modules installed.

PSU (2) OAM I/O slots Aggregate slots (2) Fan

ESD connectorTributary slots (4)



Figure 4-36130 chassis layout with I/O modules

Table 4-2 provide the PEC for the 6130 system kit.

Table 4-3 lists the components of the 6130 system kits.

Table 4-26130 system kit

System kit PEC Notes

6130 DC system kit (includes chassis, Fan, OAM card and two DC PSUs)

NT6Q60AA

NT6Q60AAE5

6130 DC system kit (includes chassis, Fan, OAM Rev2 card and two DC PSUs)

NT6Q60ABE5

6130 System; Chassis, OAM Rev2 & fan NT6Q60AME5 1

6130 DC System Ext Temp; Chassis, dual PSU, std OAM & fan

NT6Q60BAE5

Note 1: The NT6Q60AME5 kit does not include PSU units. Order this kit plus AC PSU for applications that require AC power.

I/O Modules



Table 4-36130 system kit description

Refer to Ordering information and system engineering rules on page 8-1 for more information.

System kit PEC Included PEC Description

6130 DC system kit

NT6Q60AAE5 NT6Q01AAE5 6130 Chassis (no Circuit Packs)

NT6Q43AAE5 6130 Standard OAM Circuit Pack

NT6Q40AAE5 (qty=2) 6130 DC Power Supply Unit 150W

NT6Q70ADE6 (qty=2) 6130 Top IO Filler Panel

NT6Q42AAE5 6130 Fan Tray with Filter

6130 DC system kit (OAM Rev. 2)

NT6Q60ABE5 NT6Q01AAE5 6130 Chassis (no Circuit Packs)

NT6Q43ABE5 6130 Standard OAM Circuit Pack

NT6Q40AAE5 (qty=2) 6130 DC Power Supply Unit 150W



6130 DC system kit

NT6Q60AA NT6Q01AA 6130 Chassis (no Circuit Packs)

NT6Q43AA 6130 Standard OAM Circuit Pack

NT6Q40AA (qty=2) 6130 DC Power Supply Unit 150W


NT6Q42AA 6130 Fan Tray with Filter

6130 system kit (without PSU)

NT6Q60AME5 (see Note)

NT6Q01AAE5 6130 Chassis (no Circuit Packs)

NT6Q43ABE5 6130 Standard OAM Circuit Pack



6130 DC System Ext Temp

NT6Q60BAE5 NT6Q01AAE5 6130 Chassis (no Circuit Packs)

NT6Q43BAE5 6130 Standard OAM Ext Temp Circuit Pack

NT6Q40BAE5 6130 DC Power Supply, Ext Temp 225W

NT6Q70AHE6 6130 Top Right IO Filler Panel

NT6Q70AIE6 6130 Top Left IO Filler Panel

NT6Q42BAE5 6130 Fan Tray, Ext Temp (with Filter)

Note: The NT6Q60AME5 kit does not include PSU units. Order this kit plus AC PSUs for applications that require AC power.



Slot numbersFigure 4-4 shows the slot numbers for the 6130 chassis.

Figure 4-46130 slot numbers

Power supply unitThe 6130 supports AC and DC PSUs. Table 4-4 describes the different versions available.

Table 4-4PSU

PSU PEC code Notes

DC Power Supply Unit 150W NT6Q40AA

DC Power Supply Unit 150W NT6Q40AAE5 1

DC Power Supply, Ext Temp 225W

NT6Q40BAE5 2

AC Power Supply Unit 150W NT6Q41AAE5

Note 1: DC PSU units come equipped with the base chassis as described in Table 4-2 on page 4-5 but can also be ordered separately for sparing.

Note 2: DC PSU units come equipped with the Ext Temp chassis as described in Table 4-2 on page 4-5 but can also be ordered separately for sparing.



DC PSU 150W single feedThe 6130 supports a power supply unit with single -48 V dc power feed. The chassis is equipped in normal operation with two DC PSU circuit packs for redundancy.

The DC power supply unit, as shown in Figure 4-5, is located at the left of the chassis and provides the following functionality:

• operates over the range -40 V to -57.5 V dc

• 150 W or 225 W capacity

• single power input

• local safety ground point

• monitors voltage on input power feed and the value displayed on the user interface can be used as general guidance

• low and high voltage thresholds for voltage alarms to the user interface

Refer to Ordering information and system engineering rules on page 8-1 for the PEC information. Two DC PSUs come equipped with the 6130 DC system kit, but can also be ordered separately for sparing.

Figure 4-56130 DC power supply unit

AC PSU 150WThe 6130 supports a power supply unit with a 90-264V AC power feed. The AC power supply unit, is located at the left of the base chassis and provides the following functionality:

• operates over the range 90 Vac to 264 Vac at 47/63 Hz

• 150 W capacity

• single power input

PSU (2)



• standard temperature support only

• Universal AC power socket (IEC C14)

Refer to Ordering information and system engineering rules on page 8-1 for the PEC.

Fan moduleThe 6130 chassis is equipped with a fan module that is located on the right side of the chassis, as shown in Figure 4-2 on page 4-4. Four fans are integrated within the module and are continuously being monitored for failures.

The air filter is field replaceable and it can be ordered separately for sparing or replacement.

ESD interfaceThe ESD interface is located below the fan module and is used to connect an antistatic wrist strap required when handling circuit packs to avoid damage as a result of electrostatic discharge. Figure 4-6 on page 4-9 shows the location of the ESD interface below the fan module of the 6130.

Figure 4-66130 fan module

Refer to Ordering information and system engineering rules on page 8-1 for the PEC information. The fan module comes equipped with the chassis, but can also be ordered separately for sparing.

ESD



OAM circuit packThe OAM circuit pack provides a Craft port which allows for local craft Web User Interface (WUI) access and LAN port which allows for remote access to the network element via the data communications network. The OAM circuit pack is equipped with six ports:

• Craft

• LAN

• external synchronization input (ESI)

• alarm output

• alarm input

• M1/F1

Figure 4-7 shows the OAM circuit pack. Table 4-5 provides a description of the OAM interfaces.

Figure 4-7OAM circuit pack

Table 4-5OAM port descriptions

Port Physical interface Description

Craft • RJ-45 connector • 10/100Base-T connectivity between the local craft PC and the 6130. Ethernet shielded twisted pair (STP) cables must be used to connect to the Craft port.

LAN • RJ-45 connector • Central office LAN provides switched 10/100Base-T connectivity between the carrier’s DCN and the 6130. Ethernet shielded twisted pair (STP) cables must be used to connect to the LAN port.



Refer to Connector pinouts on page 7-8 for details on the connector pinouts for the OAM ports.

Aggregate circuit packsThe aggregate circuit packs are the main circuit packs of the 6130 NE and they provide the following functionality:

— Shelf control: refer to OAM&P description on page 6-1 for more details

— Synchronization: refer to Synchronization management on page 6-11 for more details

— Cross-connect matrix: refer to Connection management on page 6-17 for more details

— Line interfaces: STM-1/4/16/OC-3/12/48 interfaces

Four types of aggregate circuit packs are available in 6130 Rel 5.0 and the following shelf configurations are supported:

• non-redundant configuration with STM-1/4/OC-3/12 line interfaces:

— one 2x155/622M aggregate circuit pack is required in slot 6

ESI • RJ-45 connector • Two external synchronization inputs for timing generation references which enable the 6130 to be timed from an external timing reference of G.813 Option 1/stratum 3 (ST3) or better quality. Both clock and data formats are supported.

• External synchronization outputs for timing distribution references which enable other network elements to be timed from the 6130.

Alarm output • RJ-45 connector • Alarm output port enables the customer to monitor the shelf level alarms (Critical, Major and minor) onto external equipment, such as lights or sirens.

• These contacts are normally open.

Alarm input • RJ-45 connector • Seven telemetry inputs enable the customer to connect external environmental monitoring equipment to the 6130 (for example, door open indicator, fire alarm, and flood alarm).

• The alarm inputs are operating as follows:open circuit = no alarmclosed circuit = alarm

M1/F1 • RJ-45 connector • Remote dial-in access through modem to the 6130.

• F1 user byte access (for clear channel access)

Table 4-5 (continued)OAM port descriptions

Port Physical interface Description



• redundant configuration with STM-1/4/OC-3/12 line interfaces:

— two 1x155/622M aggregate circuit packs are required in slots 6 and 7 (1+1 equipment protection)

• redundant configuration with STM-4/16/OC-12/48 line interfaces:

— two 1x2.5G aggregate circuit packs are required in slots 6 and 7 (1+1 equipment protection)

• redundant configuration with STM-4/16/OC-12/48 line interfaces and STM-1/4/OC-3/12 tributary interfaces on the aggregate card:

— two 1x2.5G+4x155M/2x622M aggregate circuit packs are required in slots 6 and 7 (1+1 equipment protection)

Attention: Only the configurations listed previously are supported for the aggregate circuit packs. Other configurations (e.g. mix of 155/622M and 2.5G aggregate circuit packs in same shelf, etc.) are not supported.

6130 Release 5.0 supports the aggregate circuit packs listed in Table 4-6.

2x155/622M aggregate circuit packThe 2x155/622M aggregate circuit pack must be installed in the slot 6 when the 6130 NE is configured in non-redundant mode. Figure 4-8 shows the faceplate of a 2x155/622M aggregate circuit pack.

The 2x155/622M aggregate circuit pack supports the following interfaces:

— two STM-1/OC-3 or two STM-4/OC-12 interfaces: see below for more details

The STM-1/OC-3 or STM-4/OC-12 rate for the line interfaces is provisioned by the user during the commissioning of the 6130 network element and cannot be changed. The two line interfaces of the 2x155/622M aggregate circuit pack are operating with the same rate.

Table 4-6Aggregate circuit packs

Aggregate circuit pack Page

2x155/622M aggregate circuit pack 4-12

1x155/622M aggregate circuit pack 4-14

1x2.5G aggregate circuit pack 4-16

1x2.5G+4x155M/2x622M aggregate circuit pack 4-19



The 2x155/622M aggregate circuit pack supports pluggable optical transceivers for the two STM-1/4/OC-3/12 line interfaces. The STM-1/OC-3 and STM-4/OC-12 optical interfaces use small form-factor pluggable (SFP) interfaces to deliver optical rate and reach flexibility on a per port basis. The STM-1/4/OC-3/12 optical interfaces use SFP modules for short reach, intermediate reach and long reach, and CWDM access applications. Figure 4-8 shows the STM-1/4/OC-3/12 optical interface ports on the right side of the 2x155/622M aggregate circuit pack.

The PECs for the 2x155/622M aggregate circuit pack are listed in Table 4-7.

Table 4-72x155/622M aggregate circuit pack

2x155/622M aggregate circuit pack PEC code Notes

2x155/622M aggregate (circuit pack only) NT6Q45AA 1

2x155/622M aggregate circuit pack with Release 1.0 software

NT6Q66AA 2


NT6Q66ABE5 3


NT6Q66ACE5 4


NT6Q66ADE5 5


NT6Q66AEE5 6

Note 1: The NT6Q45AA PEC cannot be ordered.

Note 2: The NT6Q66AA PEC includes one NT6Q45AA 2x155/622M aggregate circuit pack and one NT6Q87AA 6130 Release 1.0 software.

Note 3: The NT6Q66ABE5 PEC includes one NT6Q45AA 2x155/622M aggregate circuit pack and one NT6Q87AB 6130 Release 2.0 software.

Note 4: he NT6Q66ACE5 PEC includes one NT6Q45AA 2x155/622M aggregate circuit pack and one NT6Q87AC 6130 Release 3.0 software.

Note 5: The NT6Q66ADE5 PEC includes one NT6Q45AA 2x155/622M aggregate circuit pack and one NT6Q87AE 6130 Release 4.0 software.

Note 6: The NT6Q66AEE5 PEC includes one NT6Q45AA 2x155/622M aggregate circuit pack and one NT6Q87AG 6130 Release 5.0 software.



Figure 4-82x155/622M aggregate circuit pack

STM-1/4/OC-3/12 functionality overviewThe STM-1/4/OC-3/12 interfaces provide the following functionality:

• supports STM-1 or STM-4 (SDH) or OC-3 or OC-12 (SONET) services

• auto-detection of SFP modules, which are hot pluggable

• auto provisioning of STM-1/OC-3 or STM-4/OC-12 specific SFPs

• supports optical SFPs at the STM-1/4/OC-3/12 rates

• terminates RS/section and MS/line overhead

— terminates RS/section and MS/line overhead bytes in Rx direction

— inserts RS/section and MS/line overhead bytes in Tx direction

• RS/section DCC selectable (default is Off)

• MS/line DCC selectable (default is Off)

• supports RS/section DCC or MS/line DCC transparency for pass through functionality on overhead tunnels

• supports RS/section, MS/line, path and tributary unit (TU) PMs

• monitors transceiver values, such as optical received and transmit powers

• selectable automatic laser shutdown controlled by software

• supports unprotected, 1+1 MSP/APS, and SNCP/UPSR traffic protection schemes

• line timing synchronization support (provides the handover between the line timing and the shelf)

Refer to Optical specifications on page 7-37 for specifications of the SFPs and the sections in OAM&P description on page 6-1 for more details on functionality supported.

1x155/622M aggregate circuit packTwo 1x155/622M aggregate circuit packs must be installed in slots 6 and 7 when the 6130 NE is configured in redundant mode with STM-1/4/OC-3/12 interfaces.

Figure 4-9 shows the faceplate of a 1x155/622M aggregate circuit pack.



The 1x155/622M aggregate circuit pack supports the following interface:

— one STM-1/OC-3 or STM-4/OC-12 interface: see below for more details

The STM-1/OC-3 or STM-4/OC-12 rate for the line interface is provisioned by the user during the commissioning of the 6130 network element. Line rate upgrades are supported after initial commissioning of the shelf. The line interface of both 1x155/622M aggregate circuit packs are operating at same rate (i.e. it is not possible to have one line port configures at STM-1/OC-3 line rate and the other line port configured at the STM-4/OC-12 line rate).

The 1x155/622M aggregate circuit pack supports pluggable optical transceivers for the STM-1/4/OC-3/12 line interface. The STM-1/OC-3 and STM-4/OC-12 optical interfaces use small form-factor pluggable (SFP) interfaces to deliver optical rate and reach flexibility on a per port basis. The STM-1/4/OC-3/12 optical interfaces use SFP modules for short reach, intermediate reach and long reach, and CWDM access applications. Figure 4-9 shows the STM-1/4/OC-3/12 optical interface port on the right side of the 1x155/622M aggregate circuit pack.

The PECs for the 1x155/622M aggregate circuit pack are listed in Table 4-8.

Table 4-81x155/622M aggregate circuit pack

1x155/622M aggregate circuit pack PEC code Notes

1x155/622M aggregate (circuit pack only) NT6Q46AAE5 1


NT6Q67AAE5 2


NT6Q67ACE5 3


NT6Q67ADE5 4


NT6Q67AEE5 5

Note 1: The NT6Q46AAE5 PEC cannot be ordered.

Note 2: The NT6Q67AAE5 PEC includes one NT6Q46AAE5 1x155/622M aggregate circuit pack and one NT6Q87AB 6130 Release 2.0 software.

Note 3: The NT6Q67ACE5 PEC includes one NT6Q46AAE5 1x155/622M aggregate circuit pack and one NT6Q87AC 6130 Release 3.0 software.

Note 4: The NT6Q67ADE5 PEC includes one NT6Q46AAE5 1x155/622M aggregate circuit pack and one NT6Q87AE 6130 Release 4.0 software.

Note 5: The NT6Q67AEE5 PEC includes one NT6Q46AAE5 1x155/622M aggregate circuit pack and one NT6Q87AG 6130 Release 5.0 software.



Figure 4-91x155/622M aggregate circuit pack

STM-1/4/OC-3/12 functionality overviewThe STM-1/4/OC-3/12 interface provide the following functionality:

• supports STM-1 or STM-4 (SDH) or OC-3 or OC-12 (SONET) services

• line rate upgrades are supported (i.e. from STM-1/OC-3 to STM-4/OC-12)


• auto provisioning of STM-1/OC-3 or STM-4/OC-12 specific SFPs

• supports optical SFPs at the STM-1/4/OC-3/12 rates













1x2.5G aggregate circuit packTwo 1x2.5G aggregate circuit packs must be installed in slots 6 and 7 when the 6130 NE is configured in redundant mode with STM-4/16/OC-12/48 interfaces. Please refer to R4.1 Addendum (NT6Q64BE) for additional information.

Agg



Figure 4-10 shows the faceplate of a 1x2.5G aggregate circuit pack.

The 1x2.5G aggregate circuit pack supports the following interface:

— one STM-4/OC-12 or STM-16/OC-48 interface: see below for more details

The STM-4/OC-12 or STM-16/OC-48 rate for the line interface is provisioned by the user during the commissioning of the 6130 network element. Line rate upgrades are supported after initial commissioning of the shelf. The line interface of both 1x2.5G aggregate circuit packs are operating at same rate (i.e. it is not possible to have one line port configured at STM-4/OC-12 line rate and the other line port configured at the STM-16/OC-48 line rate).

The 1x2.5G aggregate circuit pack supports pluggable optical transceivers for the STM-4/16/OC-12/48 line interface. The STM-4/16/OC-12/48 optical interfaces use small form-factor pluggable (SFP) interfaces to deliver optical rate and reach flexibility on a per port basis. The STM-4/16/OC-12/48 optical interfaces use SFP modules for short reach, intermediate reach and long reach, and CWDM access applications. Figure 4-10 shows the STM-4/16/OC-12/48 optical interface port on the right side of the 1x2.5G aggregate circuit pack.

The PECs for the 1x2.5G aggregate circuit pack are listed in Table 4-9.

Table 4-91x2.5G aggregate circuit pack

1x2.5G aggregate circuit pack PEC code Notes

1x2.5G aggregate (circuit pack only) NT6Q47AAE5 1

1x2.5G aggregate circuit pack with Release 2.0 software

NT6Q68AAE5 2


NT6Q68ACE5 3


NT6Q68ADE5 4



Figure 4-101x2.5G aggregate circuit pack

STM-4/16/OC-12/48 functionality overviewThe STM-16/OC-48 interface provide the following functionality:

• supports STM-4/OC-12 or STM-16/OC-48 services


• auto provisioning of STM-4/16/OC-12/48 specific SFPs

• supports optical SFPs at the STM-4/16/OC-12/48 rate

• supports DWDM SFPs at the STM-16/OC-48 rate






1x2.5G aggregate circuit pack, no DCC with Release 4.0 software

NT6Q68MDE5 6


NT6Q68AEE5 5


Note 2: The NT6Q68AAE5 PEC includes one NT6Q47AAE5 1x2.5G aggregate circuit pack and one NT6Q87AB 6130 Release 2.0 software.

Note 3: The NT6Q68ACE5 PEC includes one NT6Q47AAE5 1x2.5G aggregate circuit pack and one NT6Q87AC 6130 Release 3.0 software.

Note 4: The NT6Q68ADE5 PEC includes one NT6Q47AAE5 1x2.5G aggregate circuit pack and one NT6Q87AE 6130 Release 4.0 software.

Note 5: The NT6Q68AEE5 PEC includes one NT6Q47AAE5 1x2.5G aggregate circuit pack and one NT6Q87AF 6130 Release 4.1 software.

Note 6: The NT6Q68ADE5 PEC includes one NT6Q47AME5 1x2.5G aggregate circuit pack, no DCC and one NT6Q87AE 6130 Release 4.0 software.

Table 4-91x2.5G aggregate circuit pack

1x2.5G aggregate circuit pack PEC code Notes

1x2G5Agg










1x2.5G+4x155M/2x622M aggregate circuit packTwo 1x2.5G+4x155M/2x622M aggregate circuit packs must be installed in slots 6 and 7 when the 6130 NE is configured in redundant mode with STM-4/16/OC-12/48 interfaces.

Figure 4-11 shows the faceplate of a 1x2.5G+4x155M/2x622M aggregate circuit pack.

The 1x2.5G+4x155M/2x622M aggregate circuit pack supports up to five optical ports. One line port and up to four tributary ports are supported. The line port can be configured as STM-4/OC-12 or STM-16/OC-48 line rate and the tributary ports can be configured as either 2xSTM-4/OC-12 ports or 4xSTM-1/OC-3 ports depending on the rate of the line port.

— When the line port is configured at STM-4/OC-12 line rate, the tributary ports of the 1x2.5G+4x155M/2x622M aggregate card are automatically configured as 4 STM-1/OC-3 ports.

— When the line port is configured at STM-16/OC-48 line rate, the tributary ports of the 1x2.5G+4x155M/2x622M aggregate card can be configured as either 4 STM-1/OC-3 ports or 2 STM-4/OC-12 ports.

The STM-4/OC-12 or STM-16/OC-48 rate for the line port is provisioned by the user during the commissioning of the 6130 network element. Line rate upgrades are supported after initial commissioning of the shelf. The line interface of both 1x2.5G+4x155M/2x622M aggregate circuit packs are operating at same rate (i.e. it is not possible to have one line port configured at STM-4/OC-12 line rate and the other line port configured at the STM-16/OC-48 line rate).



The 1x2.5G+4x155M/2x622M aggregate circuit pack supports pluggable optical transceivers for the STM-1/4/16/OC-3/12/48 interfaces. The STM-1/4/16/OC-3/12/48 optical interfaces use small form-factor pluggable (SFP) interfaces to deliver optical rate and reach flexibility on a per port basis. The STM-1/4/16/OC-3/12/48 optical interfaces use SFP modules for short reach, intermediate reach and long reach, and CWDM access applications. The STM-16/OC-48 optical interfaces also support DWDM SFP modules. Figure 4-11 shows the STM-1/4/16/OC-3/12/48 optical interface ports on the 1x2.5G+4x155M/2x622M aggregate circuit pack.

The PECs for the 1x2.5G+4x155M/2x622M aggregate circuit pack are listed in Table 4-10.

Figure 4-111x2.5G+4x155M/2x622M aggregate circuit pack

Table 4-101x2.5G+4x155M/2x622M aggregate circuit pack

1x2.5G+4x155M/2x622M aggregate circuit pack PEC code Notes

1x2.5G+4x155M/2x622M aggregate (circuit pack only)

NT6Q48AAE5 1

1x2.5G+4x155M/2x622M aggregate circuit pack with Release 4.0 software

NT6Q69ADE5 2

1x2.5G+4x155M/2x622M aggregate circuit pack with Release 5.0 software

NT6Q69AEE5 3

1x2.5G+4x155M/2x622M aggregate, EXT TEMP circuit pack with Release 5.0 software

NT6Q69BAE5 4


Note 2: The NT6Q69ADE5 PEC includes one NT6Q48AAE5 1x2.5G+4x155M/2x622M aggregate circuit pack and one NT6Q87AE 6130 Release 4.0 software.

Note 3: The NT6Q69AEE5 PEC includes one NT6Q48AAE5 1x2.5G+4x155M/2x622M aggregate circuit pack and one NT6Q87AG 6130 Release 5.0 software.

Note 4: The NT6Q69BAE5 PEC includes one NT6Q48BAE5 1x2.5G+4x155M/2x622M Ext Temp aggregate circuit pack and one NT6Q87AG 6130 Release 5.0 software.



STM-1/4/16/OC-3/12/48 functionality overviewThe STM-1/4/16/OC-3/12/48 interfaces provide the following functionality:

• supports STM-4/OC-12 (port 1) or STM-16/OC-48 (port 1) line interface

• supports 4 STM-1/OC-3 (ports 2, 3, 4, 5) or 2 STM-4/OC-12 (ports 2 and 4) tributary interfaces when line port 1 is configured at STM-16/OC-48 line rate.

• supports 2 STM-1/OC-3 (ports 4, 5) and 1 STM-4/OC-12 (ports 2) tributary interfaces when line port 1 is configured at STM-16/OC-48 line rate.

• supports 4 STM-1/OC-3 (ports 2, 3, 4, 5) tributary interfaces when line port 1 is configured at STM-4/OC-12 line rate.


• auto provisioning of STM-1/4/16/OC-3/12/48 specific SFPs

• supports optical SFPs at the STM-1/4/16/OC-3/12/48 rate

• supports DWDM SFPs at the STM-16/OC-48 rate







Table 4-11Configurations

Config. Agg. Line port Trib. port Numb. of ports (two aggs.)

2.5G 622M 155M

1 Slot 6 1x622M 4x155M 2 8

Slot 7 1x622M 4x155M

2 Slot 6 1x2.5G 2x622M 2 4

Slot 7 1x2.5G 2x622M

3 Slot 6 1x2.5G 4x155M 2 8

Slot 7 1x2.5G 4x155M

4 Slot 6 1x2.5G 1x622M + 2x155M

2 2 4

Slot 7 1x2.5G 1x622M + 2x155M







• supports MS-SPRing/BLSR on the STM-16/OC-48 line interfaces



Tributary interface circuit packThis section provides an overview of the tributary interface circuit packs. The circuit packs can be equipped in the tributary slots 4, 5, 8, and 9 of the chassis (see Figure 4-2 on page 4-4).

6130 Release 4.0 supports the tributary circuit packs listed in Table 4-12.

Table 4-12Tributary circuit packs

Tributary circuit pack Page

Transmux circuit pack 4-23

8xGE EoPDH L2 circuit pack 4-24

8xETH circuit pack 4-27

4x10/100BT+4x100FX L1 circuit pack 4-29

2xGE+8x10/100BT L1 1.2G circuit pack 4-32

2xGE circuit pack 4-35

L2PA circuit packs 4-37

28xE1/DS1 circuit pack 4-44


28xE1/DS1(W/P) circuit pack 4-46


3xE3/DS3(W/P) circuit pack 4-49

2x155M circuit pack 4-50

2x622M/8x155M circuit pack 4-51



Transmux circuit packIntroduced in this release, the Transmux circuit pack can be installed in the tributary slots on the 6130 chassis to offer E3/DS3. Figure 4-12 shows the faceplate of a Transmux circuit pack.

The PEC for the Transmux circuit pack is listed in Table 4-13.

Figure 4-12Transmux

Transmux functionality overviewThe Transmux circuit pack has 6 x DS3/E3 ports that are SMB male connectors.

• Unprotected (Supported on Tributary slot 4, 5, 8 and 9)

• 1+1 Equipment protection is supported with the 3xE3/DS3 1+1 I/O Module. The I/O module must be in I/O slot 4 when Transmux is in Tributary slot 4 and 5. The I/O module must be in I/O slot 5 when Transmux is in Tributary slot 8 and 9.

— working slots: 4, 8

— protection slot: 5, 9

• Can be independently configured DS3 or E3

• Can be independently configured as channelized or unchannelized for DS3

— If unchannelized DS3, mapped to STS-1 directly

— If channelized, 28 DS1s mapped to VT1.5 which will be multiplexed to form STS-1/AU4 through M13 mechanism

• supported cross-connect rates:

— DS1 to DS1 (on same Transmux or another DS1 card)

— DS1 to VT-1.5 (SONET)

— DS3 to STS-1 (SONET)

Table 4-13Transmux circuit pack

Circuit pack PEC code

Transmux circuit pack NT6Q12NAE5



— DS1 to TU11 (in SDH/AU4 mode)

• supports E3/DS3 line and path PMs

• Physical and electrical specifications of the ports are compliant to ITU-T G.703.

Jitter and wander specifications are compliant to ITU-T G.823/G.824,

Refer to Ordering information and system engineering rules on page 8-1 for the associated PEC and the sections in OAM&P description on page 6-1 for more details on functionality supported.

8xGE EoPDH L2 circuit packThese circuit packs support Layer 2 Packet Aggregation capabilities to help aggregate and switch Ethernet services. Designed for carrier grade reliability, manageability, broadband data rates, and service flexibility, the 8xGE EoPDH L2 circuit pack provides a strong Ethernet services and infrastructure solution for E-Lan, E-Line and Internet access solutions.

The Ethernet Ring Protection (ERP - G.8032) is supported in Release 5.0.

The 8xGE EoPDH L2 supports virtual and contiguous concatenation as well as LCAS (for VCAT) in order to ensure that packet traffic is most efficiently, reliably, and deterministically carried over the transport network. The 8xGE EoPDH L2 circuit pack supports stacked VLAN switching, stacking, and MAC Switching for large scale and availability. E-Line services supports point-to-point and E-Lan for point-to-point and multipoint to multipoint.

The 2 slot 8xGE EoPDH L2 circuit pack can be installed in the tributary slots on the 6130 chassis to offer 4 1000 Base SX/LX/ZX (SPF) and 4 100/1000 BT Ethernet services. Figure 4-13 shows the faceplate of a 8xGE EoPDH L2 circuit pack. The 100/1000 BT Ethernet ports can be configured independently by the user.

The GE optical interfaces use small form-factor pluggable (SFP) interfaces to deliver optical rate and reach flexibility on a per port basis. The GE optical interfaces use SFP modules for short reach (SX), intermediate reach (LX) and long reach (ZX) applications.

The PEC for the 8xGE EoPDH L2 circuit pack is listed in Table 4-14.

Table 4-148xGE EoPDH L2 circuit pack

8xGE EoPDH L2 circuit pack PEC code

8xGE EoPDH L2 circuit pack NT6Q23AAE5



Figure 4-138xGE EoPDH circuit pack

8xGE EoPDH L2 functionality overview

The 8xGE EoPDH L2 circuit pack supports the transport of up to eight (8) GE interfaces:

• supports up to four (4) GE ports (SFP) (Ports 5, 6, 7 and 8

• supports up to four (4) 100/1000 BT (RJ45) (Ports 1, 2, 3 and 4)

• EoS mapping in SDH mode containers via Framed GFP (G.7041) at following levels:

— VC-12-nv, n= 1 to 63

— VC-11-nv, n= 1 to 63

— VC-3-nv, n= 1 to 12

— VC-4-nv, n= 1 to 4

• EoPDH mapping in SDH mode via Framed GFP (G.7041) at following levels:

— VC-12-E1-nv, n= 1 to 16

— VC-3-E3-nv, n= 1 to 8

— VC-3-DS3-nv, n= 1 to 8

• EoS mapping in SONET mode via Framed GFP (G.7041) at following levels:

— VT-1.5-nv, n= 1 to 63

— Vt-2-nv, n= 1 to 63

— STS-3c-nv, n= 1 to 4

• EoPDH mapping in SONET mode via Framed GFP (G.7041) at following levels:

— VC-1.5-DS1-nv, n= 1 to 12

— STS-1-DS3-nv, n= 1 to 8

— STS-1-E3-nv, n= 1 to 8

• Maximum Differential Delay: 64ms

• PDH signals supports the following frame formats:

8xETH



— E1: PCM31CRC Multiframe format

— E3: G.832 Frame format

— DS1: Extended SuperFrame (ESF) format

— DS3: M23 Frame format

• The total WAN bandwidth available for connections on the 8xGE EoPDH L2 circuit pack STM-4 (622Mb/s). The bandwidth is shared between the 8 ports of the circuit pack. Up to 128 VCGs is supported.

• The maximum bandwidth 100 Mb/s for the 100BT ports

• supports provisionable Ethernet auto-negotiation (Enable or Disable) with the local Ethernet link partner as per clause 37 of IEEE 802.3-2000

• supports full duplex for Ethernet interfaces

• 64 byte to 9600 byte Ethernet frame support

• supports provisionable Link Capacity Adjustment Scheme (LCAS) (Enabled or Disabled) as per G.7042 and G7043

• supports removal of channels with MND (members non-deskewable) (Enable or Disable)

• supports GFP FCS (Frame Check Sequence) (Enable or Disable)

• DCN supported over broadcast ethernet interface

• Ethernet and WAN PMs

Attention: GE, 100/1000BT services can be forwarded by the Layer 2 Ethernet switch to the GFP mapper where the Ethernet frames are mapped to SDH/SONET containers and are assigned as WAN associations to the STM-1/4/16/OC-3/12/48 interfaces. They can therefore use the traffic protection schemes supported by the STM-1/4/16/OC-3/12/48 interfaces to provide a protected GE, 100/1000BT Ethernet service without the requirement of a redundant handoff from the subtending Ethernet equipment.

Ethernet shielded twisted pair (STP) cables must be used to connect to 100/1000BT Ethernet ports on the 8xGE EoPDH L2 circuit pack.




8xETH circuit packThe 8xETH circuit pack can be installed in the tributary slots on the 6130 chassis to offer 10/100BT Ethernet services. Figure 4-13 shows the faceplate of a 8xETH circuit pack.

The PEC for the 8xETH circuit pack are listed in Table 4-14.

Figure 4-148xETH circuit pack

8xETH functionality overviewThe 8xETH circuit pack consists of two entities (client facing and line facing):

• client facing interfaces referred to as 10/100BT Ethernet ports

• line facing (mapped for transport via SDH/SONET containers) interfaces referred to as WAN ports

The 8xETH circuit pack supports the following:

• supports the transport of up to eight (8) 10/100BT services ports

• mapping of 10/100BT Ethernet to/from SDH/SONET containers via Framed GFP at following levels:

— VC12/VT1.5, VC3/STS-1 and VC4/STS-3c operating granularity

— contiguous concatenation at STS-3c

— virtual concatenation (VC12/VT1.5-nv, where n=1 to 63 and VC3/STS1-nv, where n = 1 to 3)


• the total WAN bandwidth available for connections on the 8xETH circuit pack is STM-1/STS-3c (155 Mb/s). The bandwidth is shared between the 8 10/100BT ports of the circuit pack

Table 4-158xETH circuit pack

8xETH circuit pack PEC code

8xETH circuit pack NT6Q13AB,

NT6Q13ACE5 (Rev2)

NT6Q13BAE5 (Ext Temp)

8xETH



• The maximum bandwidth is 10 Mb/s for the 10BT ports and 100 Mb/s for the 100BT ports

• supports provisionable Ethernet link integrity (Enabled or Disabled)

Attention: For Ethernet point to point connections, when one or both end points is/are terminated on the 8xETH and/or 4x10/100BT+4x100FX L1 circuit packs, the “IgnoreRDI in LFE” WAN configuration parameter must be configured to “Disable” on both WAN ports when the following conditions are met:

- Link Integrity on the corresponding ETH ports is set to “Enabled” and - The connection rate on the WAN ports is VC4/STS-3c or VC3/STS-1 and- The Ethernet point to point connection is over a 1+1 MSP/APS Unidirectional configuration or UPSR/SNCP configuration

For all other configurations, the “IgnoreRDI in LFE” WAN configuration parameter must be configured to “Disable” (i.e. Disable is the default value)


• supports half or full duplex mode


• supports provisionable Ethernet maximum transfer unit (MTU) between 64 and 9600 (default) bytes

• supports Ethernet flow control capabilities

— Advertise None (advertises that flow control is not supported)

— Advertise Asymmetric (advertises asymmetric flow control toward the link partner)

— Advertise Symmetric (advertises that pause frames can be sent towards link partner and can be received from link partner)

— Advertise Both (advertises that Asymmetric and Symmetric flow control is supported)

— Manual Disable, Manual Tx-Rx, Manual Tx-Only or Manual Rx-Only

— If auto-negotiation is disabled, then only the following values can be provisioned for flow control: Manual Disable, Manual Tx-Rx, Manual Tx-Only or Manual Rx-Only

• supports provisionable Link Capacity Adjustment Scheme (LCAS) (Enabled or Disabled) as per G.7042/Y.1305




Attention: 10/100BT Ethernet services map to SDH/SONET containers and are assigned as WAN associations to the STM-1/4/16/OC-3/12/48 interfaces. They can therefore use the traffic protection schemes supported by the STM-1/4/16/OC-3/12/48 interfaces to provide a protected 10/100BT Ethernet service without the requirement of a redundant handoff from the subtending Ethernet equipment.

Ethernet shielded twisted pair (STP) cables must be used to connect to 10/100BT Ethernet ports on the 8xETH circuit pack.


4x10/100BT+4x100FX L1 circuit packThe 4x10/100BT+4x100FX L1 circuit pack and 4x10/100BT+4x100FX L1 622M circuit pack can be installed in the tributary slots on the 6130 chassis to offer 10/100BT Ethernet and 100Base-FX (100FX) Ethernet services. Figure 4-15 shows the faceplate of a 4x10/100BT+4x100FX L1 circuit pack.

The PECs for the 4x10/100BT+4x100FX L1 circuit pack are listed in Table 4-16.

Figure 4-154x10/100BT+4x100FX L1 circuit pack

Table 4-164x10/100BT+4x100FX L1 circuit pack

4x10/100BT+4x100FX L1 circuit pack PEC code

4x10/100BT+4x100FX L1 circuit pack NT6Q13MAE5, NT6Q13MBE5

4x10/100BT+4x100FX L1 622M circuit pack NT6Q14BAE5

4X10/100BT+4x100FXL1



4x10/100BT+4x100FX L1 and 4x10/100BT+4x100FX L1 622M functionality overviewThe 4x10/100BT+4x100FX L1 and 4x10/100BT+4x100FX L1 622M circuit pack consists of two entities (client facing and line facing):

• client facing interfaces referred to as 10/100BT and 100FX Ethernet ports


The 4x10/100BT+4x100FX L1 and 4x10/100BT+4x100FX L1 622M circuit pack supports the following:

• supports the transport of up to four (4) 10/100BT (Ports 1 to 4) plus up to four (4) 100Base-FX (100FX) (Ports 5 to 8) services ports

• mapping of 10/100BT and 100FX Ethernet to/from SDH/SONET containers via Framed GFP at following levels:

— VC12/VT1.5, VC3/STS-1 and VC4/STS-3c operating granularity


— virtual concatenation (VC12/VT1.5-nv, where n=1 to 63 and VC3/STS1-nv, where n = 1 to 3)


• the total WAN bandwidth available for connections on the 4x10/100BT+4x100FX L1 circuit pack is 155 Mb/s. The bandwidth is shared between the 4 10/100BT and 4 100FX ports of the circuit pack

• the total WAN bandwidth available for connections on the 4x10/100BT+4x100FX L1 622M circuit pack is 622 Mb/s. The bandwidth is shared between the 4 10/100BT and 4 100FX ports of the circuit pack

• The maximum bandwidth is 10 Mb/s for the 10BT ports and 100 Mb/s for the 100BT and 100FX ports


Attention: For Ethernet point to point connections, when one or both end points is/are terminated on the 8xETH and/or 4x10/100BT+4x100FX L1 circuit packs, the “IgnoreRDI in LFE” WAN configuration parameter must be configured to “Disable” on both WAN ports when the following conditions are met:

- Link Integrity on the corresponding ETH ports is set to “Enabled” and - The connection rate on the WAN ports is VC4/STS-3c or VC3/STS-1 and- The Ethernet point to point connection is over a 1+1 MSP/APS Unidirectional configuration or UPSR/SNCP configuration

For all other configurations, the “IgnoreRDI in LFE” WAN configuration parameter must be configured to “Disable” (i.e. Disable is the default value)



• for the 10/100BT interfaces, supports provisionable Ethernet auto-negotiation (Enable or Disable) with the local Ethernet link partner as per clause 37 of IEEE 802.3-2000

• supports half or full duplex mode for the 10/100BT interfaces

• auto-negotiation is not supported for the 100FX interfaces

• supports full duplex mode for the 100FX interfaces












Attention: 10/100BT Ethernet and 100FX Ethernet services map to SDH/SONET containers and are assigned as WAN associations to the STM-1/4/16/OC-3/12/48 interfaces. They can therefore use the traffic protection schemes supported by the STM-1/4/16/OC-3/12/48 interfaces to provide protected 10/100BT Ethernet and 100FX Ethernet services without the requirement of a redundant handoff from the subtending Ethernet equipment.

Ethernet shielded twisted pair (STP) cables must be used to connect to 10/100BT Ethernet ports on the 4x10/100BT+4x100FX L1 circuit pack.




2xGE+8x10/100BT L1 1.2G circuit packThe 2xGE+8x10/100BT L1 1.2G circuit pack can be installed in the tributary slots on the 6130 chassis to offer Gigabit Ethernet and 10/100Base-T Ethernet services. Figure 4-16 shows the faceplate of a 2xGE+8x10/100BT L1 1.2G circuit pack.

The 2xGE+8x10/100BT L1 1.2G circuit pack supports pluggable transceivers for the two GE interfaces. The GE optical interfaces use small form-factor pluggable (SFP) interfaces to deliver optical rate and reach flexibility on a per port basis. The GE optical interfaces use SFP modules for short reach (SX), intermediate reach (LX) and bidirectional (BX) applications. The GE interfaces also support the 1000Base-T electrical SFP module. Figure 4-16 shows the GE SFP ports on the 2xGE+8x10/100BT L1 1.2G circuit pack.

The PEC for the 2xGE+8x10/100BT L1 1.2G circuit pack is listed in Table 4-17.

Figure 4-162xGE+8x10/100BT L1 1.2G circuit pack

2xGE+8x10/100BT L1 1.2G functionality overviewThe 2xGE+8x10/100BT L1 1.2G circuit pack consists of two entities (client facing and line facing):

• client facing interfaces referred to as Gigabit Ethernet (GE) and 10/100Base-T (10/100BT) ports


The 2xGE+8x10/100BT L1 1.2G circuit pack supports up to ten (10) client facing interfaces:

• supports up to two (2) GE ports (SFP) (Ports 9 and 10)

• supports up to eight (8) 10/100BT ports (RJ45) (Ports 1 to 8)

Table 4-172xGE+8x10/100BT L1 1.2G circuit pack

2xGE+8x10/100BT L1 1.2G circuit pack PEC code

2xGE+8x10/100BT L1 1.2G circuit pack NT6Q22AAE5

2xGE+8x10/100BT L1 1G2



The 2xGE+8x10/100BT L1 1.2G circuit pack supports up to ten (10) WAN ports where the Ethernet frames are mapped to/from SDH/SONET containers with Framed GFP protocol:

• For the two WAN ports corresponding to the GE ports (Ports 9 and 10), the following VCG mappings are supported:

— VC11/VT1.5, VC12, VC3/STS-1, VC4/STS-3c operating granularity


— virtual concatenation:

– VC11/VT1.5-nv, where n = 1 to 63

– VC12-nv, where n = 1 to 63

– VC3/STS1-nv, where n = 1 to 24

– VC4/STS-3c-nv, where n = 1 to 8

• For the eight WAN ports corresponding to the 10/100BT ports (Ports 1 to 8), the following VCG mappings are supported:







– VC4/STS-3c-nv, where n = 1


• the total WAN bandwidth available for connections on the 2xGE+8x10/100BT L1 1.2G circuit pack is 8 x STM-1/STS-3c (1.2 Gb/s). The bandwidth is shared between the two GE ports and the eight 10/100BT of the circuit pack. If shelf uses the 1x2.5G aggregate circuit pack in redundant mode, the 2.5G bandwidth can be shared amongst the tributary slots 4, 5, 8, and 9. If shelf uses the 1x2.5G+4x155M/2x622M aggregate circuit pack in redundant mode, the 5G bandwidth can be shared amongst the tributary slots 4, 5, 8, and 9. Refer to “Connection management” on page 2-17 for further details on available bandwidths.

• The maximum bandwidth is 10 Mb/s for the 10BT ports, 100 Mb/s for the 100BT ports and 1000 Mb/s for the GE ports.


• supports provisionable Ethernet auto-negotiation (Enable or Disable) with the local Ethernet link partner as per clause 37 of IEEE 802.3-2000.



• supports half or full duplex mode for the 10/100BT interfaces when auto-negotiation is disabled

• supports full duplex mode only for the 10/100BT interfaces when auto-negotiation is enabled

• supports full duplex mode for the GE interfaces












Attention: Gigabit Ethernet and 10/100BT Ethernet services map to SDH/SONET containers and are assigned as WAN associations to the STM-1/4/16/OC-3/12/48 interfaces. They can therefore use the traffic protection schemes supported by the STM-1/4/16/OC-3/12/48 interfaces to provide a protected GE or 10/100BT service without the requirement of a redundant handoff from the subtending GE or 10/100BT equipment.

Ethernet shielded twisted pair (STP) cables must be used to connect to 10/100BT Ethernet ports on the 2xGE+8x10/100BT L1 1.2G circuit pack.

Refer to Optical specifications on page 7-37 for specifications of the SFPs. Refer to Ordering information and system engineering rules on page 8-1 for the associated PEC and the sections in OAM&P description on page 6-1 for more details on functionality supported.



2xGE circuit packThe 2xGE circuit pack can be installed in the tributary slots on the 6130 chassis to offer Gigabit Ethernet services. Figure 4-17 shows the faceplate of a 2xGE circuit pack.

The 2xGE circuit pack supports pluggable optical transceivers for the two GE interfaces. The GE optical interfaces use small form-factor pluggable (SFP) interfaces to deliver optical rate and reach flexibility on a per port basis. The GE optical interfaces use SFP modules for short reach (SX) and intermediate reach (LX) applications. The GE interfaces also support the 1000Base-T electrical SFP module. Figure 4-17 shows the GE optical interface ports on the 2xGE circuit pack.

The PEC for the 2xGE circuit pack is listed in Table 4-18.

Figure 4-172xGE circuit pack

2xGE functionality overviewThe 2xGE circuit pack consists of two entities (client facing and line facing):

• client facing interfaces referred to as Gigabit Ethernet ports


The 2xGE circuit pack supports the following:

• supports the transport of up to two (2) Gigabit Ethernet services ports

• mapping of Gigabit Ethernet to/from SDH/SONET containers via Framed GFP at following levels:

— VC3/STS-1 and VC4/STS-3c operating granularity


— virtual concatenation (VC3/STS1-nv, where n = 1 to 12 and VC4/STS-3c-nv, where n = 1 to 4)

Table 4-182xGE circuit pack

2xGE circuit pack PEC code

2xGE circuit pack NT6Q20AA, NT6Q20ABE5

2xGE circuit pack NT6Q20BAE5 (Ext Temp)




• the total WAN bandwidth available for connections on the 2xGE circuit pack is 4 x STM-1/STS-3c (622 Mb/s). The bandwidth is shared between the two GE ports of the circuit pack



• supports full duplex mode












Attention: Gigabit Ethernet services map to SDH/SONET containers and are assigned as WAN associations to the STM-1/4/16/OC-3/12/48 interfaces. They can therefore use the traffic protection schemes supported by the STM-1/4/16/OC-3/12/48 interfaces to provide a protected Gigabit Ethernet service without the requirement of a redundant handoff from the subtending Gigabit Ethernet equipment.




L2PA circuit packs There are 2 versions of the L2PA circuit pack. There is one version with 622M capacity, L2PA622M (name on circuit pack faceplate label is 2xGE/FX+8x10/100BT L2 622M) and a second version with 1.2G capacity, L2PA1G2 (name on circuit pack faceplate label is 2xGE/FX+8x10/100BT L2 1G2).

These circuit packs support Layer 2 Packet Aggregation (L2PA) capabilities to help aggregate and switch Ethernet services. Designed for carrier grade reliability, manageability, broadband data rates, and service flexibility, the L2PA circuit pack provides a strong Ethernet services and infrastructure solution for IP, Ethernet Private LANs, Ethernet VPNs, Ethernet Virtual Private Lines, Triple Play Services, and Internet access solutions.

The Ethernet Ring Protection (ERP - G.8032) and IGMP Snooping features are introduced in 6130 Release 4.0 with the L2PA circuit pack.

The L2PA supports virtual and contiguous concatenation as well as LCAS (for VCAT) in order to ensure that packet traffic is most efficiently, reliably, and deterministically carried over the transport network. The L2PA circuit pack supports stacked VLAN switching, stacking, and MAC Switching for large scale and availability. The L2PA circuit pack supports both Ethernet UNI (User-to-Network interfaces) such as VLAN and raw Ethernet as well as Ethernet NNI (Network-to-Network Interfaces) with stacked VLAN and includes point-to-point, point-to-multipoint, and any-to-any logical topologies.

The L2PA622M or L2PA1G2 circuit packs (L2PA) can be installed in the tributary slots on the 6130 chassis to offer Gigabit Ethernet (GE), 100Base-FX (100FX) and 10/100Base-T (10/100BT) services. Figure 4-18 shows the faceplate of a L2PA622M circuit pack. Figure 4-19 shows the faceplate of a L2PA1G2 circuit pack.

The L2PA circuit packs supports pluggable optical transceivers for the two GE and/or 100FX interfaces. The two SFP ports can be configured independently by the user to GE and/or 100FX. The two SFP ports can operate at the same rate or at different rates.

The GE or 100FX optical interfaces use small form-factor pluggable (SFP) interfaces to deliver optical rate and reach flexibility on a per port basis. The GE optical interfaces use SFP modules for short reach (SX), intermediate reach (LX) and bidirectional (BX) applications. The GE interfaces also support the 1000Base-T electrical SFP module. The 100FX optical interfaces use SFP modules for short reach (FX), intermediate reach (LX) and bidirectional (BX) applications. Figure 4-18 shows the GE or 100FX optical interface ports on the L2PA622M circuit pack. Figure 4-19 shows the GE or 100FX optical interface ports on the L2PA1G2 circuit pack.



The PEC for the L2PA circuit packs are listed in Table 4-19.

Figure 4-18L2PA622M circuit pack

Figure 4-19L2PA1G2 circuit pack

L2PA functionality overview

The L2PA circuit packs consists of two entities (client facing and line facing):

• client facing interfaces referred to as Gigabit Ethernet (GE), 100Base-FX (100FX) and 10/100Base-T (10/100BT) ports


Table 4-19L2PA circuit packs

L2PA circuit packs PEC code Notes

L2PA622M circuit pack NT6Q21AAE5, NT6Q21ABE5

1

L2PA1G2 circuit pack NT6Q21GAE5, NT6Q21GBE5 (Rev2)

2

Note 1: Due to power limitations, up to two L2PA622M circuit packs can be equipped in the 6130 NE with the 150W PSU. Please refer to Shelf equipping rules Step 19 on page 8-15 for details on power limitations.

Note 2: Due to power limitations, up to three L2PA1G2 circuit packs can be equipped in the 6130 NE with the 150W PSU. Please refer to Shelf equipping rules Step 19 on page 8-15 for details on power limitations.

2xGE/FX+8x10/100BT L2 622M

2xGE/FX+8x10/100BT L2 1G2



The L2PA622M and L2PA1G2 circuit packs supports up to ten (10) client facing interfaces:

• supports up to two (2) GE and/or 100FX ports (SFP) (ports 9 and 10)

• supports up to eight (8) 10/100BT ports (RJ45) (ports 1 to 8)

The L2PA622M circuit pack supports up to eight (8) WAN ports and the L2PA1G2 circuit pack supports up to ten (10) WAN ports where the Ethernet frames are mapped to/from SDH/SONET containers with Framed GFP protocol:

• supports up to two (2) GE WAN ports (ports 9 and 10)

• the L2PA622M circuit pack supports up to six (6) FE WAN ports (ports 1 to 6)

• the L2PA1G2 circuit pack supports up to eight (8) FE WAN ports (ports 1 to 8)

• For the two GE WAN ports (ports 9 and 10), the following VCG mappings are supported:

— VC11/VT1.5, VC12, VC3/STS-1 and VC4/STS-3c operating granularity





– VC3/STS1-nv, where n = 1 to 12 for the L2PA622M and n = 1 to 24 for the L2PA1G2

– VC4/STS-3c-nv, where n = 1 to 4 for the L2PA622M and n = 1 to 8 for the L2PA1G2

• For the FE WAN ports (ports 1 to 8), the following VCG mappings are supported:









Attention: The traffic rate is limited to 100 Mb/s for FE WAN ports. If connections are provisioned to have more than 100 Mb/s VCG capacity and the traffic rate on the WAN ports (ingress from STM/OC ports) exceeds 100 Mb/s, then the packets exceeding 100 Mb/s are dropped.


• the total WAN bandwidth available for connections on the L2PA622M circuit pack is 4 x STM-1/STS-3c (622 Mb/s). The bandwidth is shared between the eight WAN ports of the circuit pack

• the total WAN bandwidth available for connections on the L2PA1G2 circuit pack is 8 x STM-1/STS-3c (1.2 Gb/s). The bandwidth is shared between the ten WAN ports of the circuit pack. If shelf uses the 1x2.5G aggregate circuit pack in redundant mode, the 2.5G bandwidth can be shared amongst the tributary slots 4, 5, 8, and 9. If shelf uses the 1x2.5G+4x155M/2x622M aggregate circuit pack in redundant mode, the 5G bandwidth can be shared amongst the tributary slots 4, 5, 8, and 9. Refer to “Connection management” on page 2-17 for further details on available bandwidths.

• for the 10/100BT and GE interfaces, supports provisionable Ethernet auto-negotiation (Enable or Disable) with the local Ethernet link partner as per clause 37 of IEEE 802.3-2000

• auto-negotiation is not supported for the 100FX interfaces

• supports full duplex mode for the 100FX and GE interfaces

• supports half or full duplex mode for the 10/100BT interfaces














Integrated Layer 2 Ethernet switch functionality overview

The Layer 2 Ethernet switch integrated in the L2PA622M and L2PA1G2 circuit pack provides the following functionality:

• MAC and VLAN switching and forwarding

– Maximum number of MAC addresses in lookup table: 16000

– Maximum number of VLANs that can be provisioned: 2000

• Flexible QoS with per client port and WAN port

• Ethernet Services:

– Ethernet UNI

– Q-in-Q encapsulation

– Ethernet Private Line

– Ethernet Virtual Private Line

– Transparent IGMP snooping (V1, V2 and V3) as per RFC 4541

• Classification based on:

– Port

– MAC SA/DA

– VLAN ID (inner and outer)

– P-bits (inner and outer)

– DSCP (Differentiated Services Code Point) or TOS (Type of Service)

– IP PT (Packet Type)

– TCP/UDP SP/DP

– IP SA/DA

• Classification based marking:

– DSCP, TOS

– VLAN tag (outer)

– P-bits (outer)

• Over-ride switching decision based on classification

• Hardware based ACLs (Access Control List):

– Maximum number of ACL that can be provisioned: 100

– L2 – SA/DA MAC, CVLAN (TPID, VID, Pbit), SVLAN (TPID, VID, Pbit)

– L3/L4 – IP SA/DA, PT, SP/DP, TOS/DSCP



• Traffic Management:

– per-port ingress rate limiting - 64 kbps incr.

– per-port egress rate limiting - 64 kbps incr.

– 8 Classes of Service

– Traffic class rate limiting

— Scheduling:

– SP (Strict Policing)

– SP + WRR (Weighted Round-Robin)

– SP + WFQ (Weighted Fair Queuing)

— CoS mappings:

– P-bit to P-bit + CoS

– DSCP to P-bit + CoS

– IP pres. to P-bit + CoS

— Queue admission – tail drop, WRED (Weighted Random Early Detection)

— Dual drop precedence per CoS

— Metering

— Policing

• Ethernet Ring Protection (ERP):

— the ERP Standard (G.8032) is also referred to as E-SPRing

— protection mechanism for Ethernet traffic:

– below 50ms switching for all ringlets when there is a single failure (e.g. LOS) in the Ethernet ring

– up to 250 VLANs can be switched within 50ms

– number of ring nodes is not limited

— supported in 802.1q or Q-in-Q mode for the L2PA circuit pack

— ringlets are supported to achieve spatial re-use and bandwidth efficiency:

– up to 8 ringlets are supported per L2PA circuit pack

– up to 8 ringlets are supported per NNI port

– only 1 ringlet is supported per UNI port

— VLAN mapping:

– multiple VLANs can be mapped to a ringlet

– a VLAN can be mapped to no more than 1 ringlet. A VLAN cannot be mapped to 2 or more ringlets.



— ERP control frames:

– ERP control frames are sent for each ringlet. Each ringlet is operating independently and has its own control frames.

– the user can view the state of each ringlet and each port

– the VLAN used for the ERP control frames cannot be used to carry Customer data

— ERP and STP can be used in the same VLAN but with no overlap for the ports on which they operate. A port cannot use ERP and STP at the same time.

• Spanning Tree Protocol (STP) support:

— STP (Spanning Tree Protocol)

— RSTP (Rapid STP)

— MSTP (Multiple STP)

• Link Aggregation Group (LAG):

— 802.3ad LA (Ling Aggregation) on up to 6 FE ports (for L2PA622M) or up to 8 FE ports (for L2PA1G2)

— 802.3ad LA on up to 2 GE or 100FX ports

— LA hashing based on:

– 3 LSB (Least Significant Bit) of IPv4 SA/DA

– MAC SA/DA

— LACP (Link Aggregation Control Protocol) tunneling

• Security:

— Access control list

— Port mirroring for lawful intercept

— Packet storm control

• IGMP Snooping:

— Implementation as per RFC 4541

— transparent IGMP snooping V1, V2 and V3 is supported

— IGMP snooping can be enabled on a per VLAN basis

— dynamic detection of multicast routers on a per port and per VLAN basis when IGMP Query, DVMRP or PIM messages are received

— manual configuration is supported for the multicast routers

— manual configuration is supported for the IGMP Group membership interval, maximum response time and multicast router expiry time on a per VLAN basis



— IGMP Membership reports are forwarded to the ports where the multicast routers are connected

— non-IGMP multicast frames within the range 224.0.0.1 to 224.0.0.255 are forwarded to all ports of the VLAN (except ingress port)

— can be used on ports and VLANs where STP or ERP protocols are enabled

Attention: GE, 100FX and 10/100BT services can be forwarded by the Layer 2 Ethernet switch to the GFP mapper where the Ethernet frames are mapped to SDH/SONET containers and are assigned as WAN associations to the STM-1/4/16/OC-3/12/48 interfaces. They can therefore use the traffic protection schemes supported by the STM-1/4/16/OC-3/12/48 interfaces to provide protected GE, 100FX and 10/100BT services without the requirement of a redundant handoff from the subtending equipment.

Ethernet shielded twisted pair (STP) cables must be used to connect to 10/100BT Ethernet ports on the L2PA622M and L2PA1G2 circuit packs.

For detailed information on the 6130 L2PA concepts, applications, and engineering rules, see 6100 Data Application Guide, NTRN15CA.


28xE1/DS1 circuit packThe 28xE1/DS1 circuit pack can be installed in the tributary slots of the 6130 chassis. Figure 4-20 shows the faceplate of a 28xE1/DS1 circuit pack.

The PEC for the 28xE1/DS1 circuit pack is listed in Table 4-20.

Table 4-2028xE1/DS1 circuit pack

28xE1/DS1 circuit pack PEC code

28xE1/DS1 circuit pack NT6Q10AANT6Q10AB (Rev2)

NT6Q10ABE5 (Rev2)

NT6Q10BA (Ext Temp)




Figure 4-2028xE1/DS1 circuit pack faceplate

28xE1/DS1 functionality overviewThe 28xE1/DS1 circuit pack supports the following:

• supports up to 28 E1/DS1 services (120/100 ohm balanced)

• mapping of E1/DS1 signals to VC12/VT2/VC11/VT1.5 containers

• support for framed E1 (CRC4) / DS1 (ESF) or unframed signals monitoring

• the NT6Q10AB or NT6Q10BA supports super frame when provisioned in a shelf using 1x155/622M or 1x2.5G+4x155M/2x622M agg. card

• supports E1/DS1 line PMs

• supports NE synchronization on any of 1, 4, 7, 10, 13, 16, 19, 22, 25 or 28 E1/DS1 ports

• can be configured to carry either E1 traffic or DS1 traffic on all 28 ports of the circuit pack, independent of the NE mode (SDH or SONET). A mix of E1 and DS1 traffic services is not supported.

Refer to the sections in OAM&P description on page 6-1 for more details on functionality supported.

63xE1/DS1 circuit packThe 63xE1/DS1 circuit pack can be installed in any service slot of the 6130 chassis. Figure 4-21 shows the faceplate of a 63xE1/DS1 circuit pack.

Attention: DS1 service is supported in Release 5.0. DS1 is not supported in Release 4.0 and below.



63xE1/DS1circuit pack PEC code Notes

63xE1/DS1 NT6Q11AAE5 Standard temperature



Figure 4-2163xE1/DS1circuit pack faceplate

63xE1/DS1functionality overviewThe 63xE1/DS1 circuit pack supports the following:

• supports up to 63 E1/DS1 services (120 ohms balanced and 75 ohms unbalanced)

— the 63xE1/DS1 circuit pack can be configured to operate with 120 ohms (default) or 75 ohms impedance on all 63 E1 ports of the circuit pack. A mix of 120 ohms and 75 ohms impedance is not supported on the same circuit pack.


• support for framed E1 (CRC4) / DS1 (ESF) or clear channel (unframed) signal monitoring

• support Super Frame for DS1 when provisioned in a shelf using the 1x155/622M or 1x2.5G+4x155M/2x622M agg. card.

• supports E1 line PMs and path PMs

• NE synchronization on any E1/DS1 ports


28xE1/DS1(W/P) circuit packThe 28xE1/DS1(W/P) circuit pack can be installed in the tributary slots of the 6130 chassis. Figure 4-22 shows the faceplate of a 28xE1/DS1(W/P) circuit pack.

The PEC for the 28xE1/DS1(W/P) circuit pack is listed in Table 4-22.

I/O modules are required with the 28xE1/DS1(W/P) circuit pack. See I/O Modules on page 4-55 for more details.

Table 4-2228xE1/DS1(W/P) circuit pack

28xE1/DS1(W/P) circuit pack PEC code

28xE1/DS1(W/P) circuit pack NT6Q10MAE5



Figure 4-2228xE1/DS1(W/P) circuit pack faceplate

28xE1/DS1(W/P) functionality overviewThe 28xE1/DS1(W/P) circuit pack supports the following:

• supports up to 28 E1/DS1 services (120/100 ohm balanced)

• 1+1 Equipment protection is supported with the 28xE1/DS1 1+1 I/O module (one protection circuit pack for one working circuit packs). The 28xE1/DS1(W/P) circuit pack is supported in the working and protection slots (i.e. same PEC for working and protection circuit packs):



• 1:N (N=3) Equipment protection is supported with the 84xE1/DS1 1:N I/O module (one protection circuit pack for up to three working circuit packs in 1:3 mode). The 28xE1/DS1(W/P) circuit pack is supported in the working and protection slots (i.e. same PEC for working and protection circuit packs):

— working slots: 4, 5, 8

— protection slot: 9

• Unprotected mode is supported for the 28xE1/DS1(W/P) circuit pack. Any tributary slot not part of a protection group is completely independent to accept any other circuit pack

— in unprotected mode, with the 28xE1/DS1 1+1 I/O module in I/O slot 4: slot 5 can be used for any other circuit pack.


— in unprotected mode, with the 84xE1/DS1 1:N I/O module. Working slots 4 and/or 5 and/or 8 can be equipped with the 28xE1/DS1(W/P) circuit pack: the unused slots (slots 4 and/or 5 and/or 8) and protection slot 9 can be used for any other circuit pack


• support for framed E1 (CRC4) / DS1 (ESF) or unframed signals monitoring

• supports E1/DS1 line PMs

• supports NE synchronization on any of 1, 4, 7, 10, 13 E1/DS1 ports



• can be configured to carry either E1 traffic or DS1 traffic on all 28 ports of the circuit pack, independent of the NE mode (SDH or SONET). A mix of E1 and DS1 traffic services is not supported on the same circuit pack.


3xE3/DS3 circuit packThe 3xE3/DS3 circuit pack can be installed in the tributary slots of the 6130 chassis. Figure 4-23 shows the faceplate of a 3xE3/DS3 circuit pack.



3xE3/DS3 functionality overviewThe 3xE3/DS3 circuit pack supports the following:

• supports up to 3 E3/DS3 services (75 ohm)

• mapping of E3/DS3 signals to VC3/STS1 containers

• support for framed E3 (G.832) / DS3 (ASYNC M13) or unframed signals monitoring


• each port can be independently configured to carry E3 or DS3 traffic. A mix of E3 and DS3 services is supported.



3xE3/DS3 circuit pack PEC code

3xE3/DS3 circuit pack NT6Q12AA, NT6Q12ABE5, NT6Q12ACE5


3XE3DS3



3xE3/DS3(W/P) circuit packThe 3xE3/DS3(W/P) circuit pack can be installed in the tributary slots of the 6130 chassis. Figure 4-24 shows the faceplate of a 3xE3/DS3(W/P) circuit pack.

The PEC for the 3xE3/DS3(W/P) circuit pack is listed in Table 4-24.

I/O modules are required with the 3xE3/DS3(W/P) circuit pack. See 3xE3/DS3 1+1 I/O Module on page 4-57 for more details.

Figure 4-243xE3/DS3(W/P) circuit pack faceplate

3xE3/DS3(W/P) functionality overviewThe 3xE3/DS3(W/P) circuit pack supports the following:

• supports up to 3 E3/DS3 services (75 ohm)

• mapping of E3/DS3 signals to VC3/STS1 containers

• 1+1 Equipment protection is supported. The 3xE3/DS3(W/P) circuit pack is supported in the working and protection slots (i.e. same PEC for working and protection circuit packs):



• Unprotected mode is supported for the 3xE3/DS3(W/P) circuit pack. Any tributary slot not part of a protection group is completely independent to accept any other circuit pack.



• support for framed E3 (G.832) / DS3 (ASYNC M13) or unframed signals monitoring


Table 4-243xE3/DS3(W/P) circuit pack

3xE3/DS3(W/P) circuit pack PEC code

3xE3/DS3(W/P) circuit pack NT6Q12MAE5



• each port can be independently configured to carry E3 or DS3 traffic. A mix of E3 and DS3 services is supported.


2x155M circuit packThe 2x155M circuit pack can be installed in the tributary slots of the 6130 chassis. Figure 4-25 shows the faceplate of a 2x155M circuit pack.

The 2x155M circuit pack supports pluggable optical and electrical transceivers for the two STM-1/OC-3 line interfaces. The STM-1/OC-3 optical and electrical interfaces use small form-factor pluggable (SFP) interfaces to deliver optical and electrical rate and reach flexibility on a per port basis. The STM-1/OC-3 optical interfaces use SFP modules for short reach, intermediate reach and long reach, and CWDM access applications. The STM-1/OC-3 electrical interfaces use SFP modules for intra office applications. Figure 4-25 shows the STM-1/OC-3 interface ports on the center of the 2x155M circuit pack.

The PEC for the 2x155M circuit pack is listed in Table 4-25.

Figure 4-252x155M circuit pack faceplate

2x155M functionality overviewThe 2x155M circuit pack supports the following:

• supports up to 2 STM-1/OC-3 optical (o) or electrical (e) services


• auto provisioning of STM-1/OC-3 specific optical and electrical SFPs

• supports single fiber working (SFW) SFPs at the STM-1/OC-3 rate



Table 4-252x155M circuit pack

2x155M circuit pack PEC code

2x155M circuit pack NT6Q17AA, NT6Q17ABE5, NT6Q17ACE5













2x622M/8x155M circuit packThe 2x622M/8x155M circuit pack can be installed in the tributary slots of the 6130 chassis. Figure 4-26 shows the faceplate of a 2x622M/8x155M circuit pack.

2x622M/8x155M circuit pack modes of operationThe 2x622M/8x155M circuit pack, when equipped in a shelf with two 1x2.5G or 1x2.5G+4x155M/2x622M aggregate cards, can be configured to supports one of the following modes of operation:

• one STM-16/OC-48 interface (when circuit pack is in slot 5 or 9)

– port 1 for STM-16/OC-48, other ports are disabled

Attention: The 2x622M/8x155M circuit pack only supports the STM-16/OC-48 rate when running Release 5.0 and only when using the 1x2.5G+4x155M/2x622M aggregate circuit pack.

• two STM-4/OC-12 interfaces

– ports 1 and 5 used for STM-4/OC-12, other ports are disabled

• one STM-4/OC-12 interface and four STM-1 interfaces

– port 1 used for STM-4/OC-12, ports 5-8 used for STM-1/OC-3, other ports are disabled

– ports 1-4 used for STM-1/OC-3, port 5 used for STM-4/OC-12, other ports are disabled



• eight STM-1/OC-3 interfaces

– ports 1 to 8 used for STM-1/OC-3

The 2x622M/8x155M circuit pack, when equipped in a shelf with two 1x2.5G aggregate cards, can be configured to supports one of the following modes of operation:

• two STM-4/OC-12 interfaces

– ports 1 and 5 used for STM-4/OC-12, other ports are disabled

• one STM-4/OC-12 interface and four STM-1 interfaces

– port 1 used for STM-4/OC-12, ports 5-8 used for STM-1/OC-3, other ports are disabled

– ports 1-4 used for STM-1/OC-3, port 5 used for STM-4/OC-12, other ports are disabled

• eight STM-1/OC-3 interfaces

– ports 1 to 8 used for STM-1/OC-3

The 2x622M/8x155M circuit pack, when equipped in a shelf with the 1x155/622M aggregate cards, can be configured to supports 1 of the following modes of operation:

• one STM-4/OC-12 interface

– port 1 used for STM-4/OC-12, other ports are disabled

• four STM-1/OC-3 interfaces

– ports 1-4 used for STM-1/OC-3, other ports are disabled

The 2x622M/8x155M circuit pack is not supported with the non redundant 2x155/622M aggregate circuit packs.

The 2x622M/8x155M circuit pack supports pluggable optical transceivers for the STM-1/4/OC-3/12 line interfaces and pluggable electrical transceivers for the STM-1 line interfaces. The STM-1/4/OC-3/12 optical interfaces use small form-factor pluggable (SFP) interfaces to deliver optical rate and reach flexibility on a per port basis. The STM-1/OC-3 or STM-4/OC-12 optical interfaces use SFP modules for short reach, intermediate reach, long reach, and CWDM access applications. The STM-1 electrical interfaces use SFP modules for intra office applications.



The PEC for the 2x622M/8x155M circuit pack is listed in Table 4-26.

Figure 4-262x622M/8x155M circuit pack faceplate

2x622M/8x155M functionality overviewThe 2x622M/8x155M circuit pack supports the following:

• supports up to 8 STM-1/OC-3 optical (o) or electrical (e) services or up to 2 STM-4/OC-12 optical services or a combination of STM-1/OC-3 and STM-4/OC-12 services as described in 2x622M/8x155M circuit pack modes of operation on page 4-51.


• auto provisioning of STM-1/4/OC-3/12 specific optical and electrical SFPs

• supports single fiber working (SFW) SFPs at the STM-1/OC-3 rate

Table 4-262x622M/8x155M circuit pack

2x622M/8x155M circuit pack PEC code

2x622M/8x155M circuit pack NT6Q18AAE5 (See Notes 1, 2, 3, 4, 5)

2x622M/8x155M Rev2 circuit pack NT6Q18ABE5 (See Notes 3, 4)

Note 1: Due to power limitation, a maximum of 3 2x622M/8x155M (NT6Q18AAE5) circuit packs can be equipped in a 6130 shelf equipped with the 1x2.5G aggregate cards. Please refer to Shelf equipping rules Step 19 on page 8-15 for details on power limitations.

Note 2: Due to power limitation, a maximum of 2 2x622M/8x155M (NT6Q18AAE5) circuit packs can be equipped in a 6130 shelf equipped with the 1x2.5G+4x155M/2x622M aggregate cards. Please refer to Shelf equipping rules Step 19 on page 8-15 for details on power limitations

Note 3: A maximum of 16 STM-1/OC-3 ports or 4 STM-4/OC-12 ports or any other combination of STM-1/OC-3 and STM-4/OC-12 ports (totaling 2.5Gb/s worth of bandwidth) can be simultaneously active on a shelf equipped with redundant 1x2.5G aggregate cards.

Note 4: A maximum of 8 STM-1/OC-3 ports or 2 STM-4/OC-12 ports or any other combination of STM-1/OC-3 and STM-4/OC-12 ports (totaling 1.2Gb/s worth of bandwidth) can be simultaneously active on a shelf equipped with redundant 1x155/622M aggregate cards.

Note 5: For NEBS Radiated Emissions compliancy, in 6130 deployments which include one or more DS-1 I/O cards (NT6Q44AAE5), only one (1) NT6Q18AAE5 circuit pack per 6130 shelf is supported and it must be installed in tributary slot #5.



• supports electrical SFPs for STM-1 interface only















I/O ModulesI/O modules for the 6130 shelves provide input and output of electrical signals for traffic. The I/O panels are removable and replaceable.

28xE1/DS1 1+1 I/O ModuleThe 28xE1/DS1 1+1 I/O Module provides the electrical interfaces for the 28xE1/DS1(W/P) circuit packs. Each I/O panel supports 28 E1/DS1 inputs/outputs. The I/O panels can be installed in one of the two I/O slots located on the top section of the 6130 chassis.

Attention: Refer to 28xE1/DS1(W/P) circuit pack on page 4-46 for additional details on the 28xE1/DS1(W/P) circuit pack.

Figure 4-27 shows the faceplate of the 28xE1/DS1 1+1 I/O module.

The PEC for the 28xE1/DS1 1+1 I/O Module is listed in Table 4-27.

Figure 4-2728xE1/DS1 1+1 I/O Module faceplate

Slot population rules for the 28xE1/DS1 1+1 I/O moduleThe following slot population rules must be observed with the 28xE1/DS1 1+1 I/O module.

• 28xE1/DS1 1+1 I/O module equipped in I/O slot 4

– 28xE1/DS1(W/P) circuit pack equipped in tributary slots 4 and 5.



Table 4-2728xE1/DS1 1+1 I/O Module

28xE1/DS1 1+1 I/O Module PEC code

28xE1/DS1 1+1 I/O Module NT6Q44AAE5



84xE1/DS1 1:N I/O ModuleThe 84xE1/DS1 1:N I/O Module provides the electrical interfaces for the 28xE1/DS1(W/P) circuit packs. Each I/O panel supports 84 E1/DS1 inputs/outputs. The I/O panels can be installed in the I/O slots located on the top section of the 6130 chassis.




Figure 4-2884xE1/DS1 1:N I/O Module faceplate

Slot population rules for the 84xE1/DS1 1:N I/O moduleThe following slot population rules must be observed with the 84xE1/DS1 1:N I/O module. The 84xE1/DS1 1:N I/O module occupies both I/O slots (I/O slots 4 and 8).

• 84xE1/DS1 1:N I/O module in I/O slots 4 and 8

– Working cards: 28xE1/DS1(W/P) circuit pack equipped in tributary slots 4, 5 and/or 8.

– Protection card: 28xE1/DS1(W/P) circuit pack equipped in tributary slot 9.



84xE1/DS1 1+1 I/O Module NT6Q44CAE5



3xE3/DS3 1+1 I/O ModuleThe 3xE3/DS3 1+1 I/O Module provides the electrical interfaces for the 3xE3/DS3(W/P) circuit packs. Each I/O panel supports 3 E3/DS3 inputs/outputs. The I/O panels can be installed in one of the two I/O slots located on the top section of the 6130 chassis.




Figure 4-293xE3/DS3 1+1 I/O module faceplate

Slot population rules for the 3xE3/DS3 1+1 I/O moduleThe following slot population rules must be observed with the 3xE3/DS3 1+1 I/O module.







3xE3/DS3 1+1 I/O Module NT6Q44BAE5



Filler faceplateThe filler faceplate is required to cover the unused tributary slots 4, 5, 8 and 9. If only one Aggregate circuit pack is used in slot 6 for the shelf, then slot 7 must be equipped with a filler faceplate. If no additional tributary circuit packs are required a filler faceplate must be used to cover the empty slots to ensure proper airflow through the chassis and to ensure EMI compliance. Figure 4-2 on page 4-4 displays the chassis with a filler faceplate installed over the slot 7.

Refer to Ordering information and system engineering rules on page 8-1 for the associated PEC. The filler faceplate must be ordered separately.

E1 75 ohm termination panelThe conversion from 120 ohm to 75 ohm E1 service interfaces can be achieved for the 28xE1/DS1 circuit pack.

The conversion is achieved by connecting the Telco connectors of the 28xE1/DS1 circuit pack to a 1U high 16-channel termination panel. The termination panel is equipped with 32 BNC connectors (16 connectors for RX ports and 16 connectors for TX ports). This 75 ohm termination panel can only be used for E1 services.

Attention: The 75 ohm termination panel is labeled from 1-16 by default, but includes an additional overlay label which can be installed by the user when connecting the ports 17-28 of the 28xE1/DS1 circuit pack.

A 64-pin to 64-pin male connector cable must be used to connect to the termination panel. For more information regarding the 75 ohm termination panel and the cable pinout information, refer to E1/DS1 cable pinouts and assemblies on page 7-12

Cable routingThe cable routing brackets which are installed at either side of the 6130 shelf allows for the management of the power cables, OAM cables, optical fibers and the Ethernet/PDH/DSn service cables. The cable routing brackets are placed over the mounting brackets during the installation of the 6130 shelf. Figure 4-30 shows the mounting and cable routing brackets for 6130 without I/O modules.

For more information on the installation of the cable routing brackets, refer to Installation, Commissioning and Testing Procedures, 323-1855-201. The cable routing brackets come as part of the 6130 shelf assembly kit. Refer to Ordering information and system engineering rules on page 8-1 for ordering details of the 6130 shelf assembly kit.



Figure 4-306130 mounting and cable routing brackets (without I/O modules)

6130 Shelf assembly kitIt is recommended to order one 6130 shelf assembly kit for each NE. The PEC for the 6130 shelf assembly kit is listed in Table 4-30.

The 6130 shelf assembly kit contains the following components:

• cable routing brackets

• rack mounting screws

• 21” and 23” flange

• cage nuts

• earthing cable

Attention: The 19” shelf mounting brackets are included in the 6130 system kits so they do not need to be ordered separately.

Table 4-306130 Shelf assembly kit

6130 Shelf assembly kit PEC code

6130 Shelf assembly kit NT6Q70CA, NT6Q70CAE6

6130 - 19” Mounting Kit - brackets, screws & cage nuts

NT6Q70CBE6



Refer to Ordering information and system engineering rules on page 8-1 for ordering details of the 6130 shelf assembly kit.


5-1

User interface description 5-

This chapter provides an overview of the user interfaces available for the 6130 Release 5.0. Table 5-1 lists the topics in this chapter.

6130 Node Manager (WUI)The 6130 Node Manager is a Web User Interface (WUI) and it is a graphical, nodal management tool that is available inherently on the network element software. The Node Manager (WUI) is launched via an HTTP/HTTPS web-browser that runs on any computing platform. Table 5-2 provides a list of minimum requirements for various web browsers. The Node Manager provides full access to the 6130 network element across TCP/IP and to other 6130 network element visible across DCC or locally across the network element's Craft port.


Topic Page

6130 Node Manager (WUI) 5-1

6100 Site Manager 5-2

TL1 interface 5-3

SNMP traps 5-4


5-2 User interface description

The Node Manager (WUI) provides support for the following functions:

• fault and alarm management

• equipment and facility management

• PM viewing and threshold setting

• synchronization management

• upgrades and software download

• backup and restore

• protection status and control

• nodal security management

• nodal connection management

• DCN communications management

Refer to Chapter 6, OAM&P description for more information about the operations, administration, maintenance and provisioning (OAM&P) capabilities supported by the 6130 Release 5.0.

For more information on the Node Manager (WUI) and the supported applications, refer to the Local Craft Access User Guide, 323-1855-195.

6100 Site ManagerThe 6100 Site Manager craft user interface supports a comprehensive suite of OAM&P functionality for the 6130. The Site Manager craft user interface is a graphical, nodal management tool that is available on a CD.

The Site Manager craft user interface is platform independent, running natively on Windows, UNIX and Solaris workstations ensuring field technicians and network operations centre (NOC) operators are operating with the same view.

Table 5-26130 Node Manager (WUI) requirements

Web browser Supported version OS platform

Microsoft Internet Explorer

6.x • Win2K

• WinXp

Mozilla 1.6 and 1.7 • Red Hat Linux

• HP-UX

• Solaris 9.0

FireFox 1.0 • Red Hat Linux 7.x


User interface description 5-3

The 6100 Site Manager provides full access to the 6130 network element across TCP/IP and to other 6130 network element visible across DCC or locally across the network element's Craft port.

The 6100 Site Manager provides support for the following functions for the 6130 NEs:

• login / logout of NEs

• navigation tree

• alarm banner

• active alarms

• shelf level view

• launch of WUI

• terminal session to the NE TL1 interface

• MS-SPRing/BLSR configuration management

Refer to Chapter 6, OAM&P description for more information about the operations, administration, maintenance and provisioning (OAM&P) capabilities supported by the 6130 Release 5.0.

For more information on the 6100 Site Manager and the supported applications, refer to the Site Manager for 6100 Rel 4.0 Fundamentals, NT6Q91AD.

TL1 interfaceTransaction Language 1 (TL1) allows you to manage SDH/SONET optical equipment for 6130. TL1 is a common language protocol for messages exchanged between network elements and OMEA. TL1 is based on Telcordia specifications. TL1 message sets allow you to perform the following functions:

• connection provisioning

• alarm and network surveillance

• performance monitoring

• network security and administration

• inventory retrieval

• network element discovery and management

• topology adjacency discovery

• database backup and restore

• software upgrade and release management

The 6130 TL1 interface conforms to standards, GR-831, GR-833 and GR-199 for syntax, information structure and transactions.


5-4 User interface description

SNMP trapsThe 6130 supports autonomous forwarding of system events through SNMP traps for consolidated alarm reporting. The SNMP traps are sent to an SNMP manager, where they can be used to alert a system operator.

Up to eight SNMP trap managers can be provisioned for each 6130 network element. For each trap destination, the IP address and the SNMP version (v1 or v2) are provisioned.

For more information on how to provision the SNMP trap destinations, refer to Provisioning and Protection Switching Procedures, 323-1855-310.


6-1

OAM&P description 6-

This chapter provides the operations, administration, maintenance and provisioning (OAM&P) description for the 6130 network element. Table 6-1 lists the topics in this chapter.


Topic Page

SDH and SONET Configurations 6-2

System Line-up and Test (SLAT) 6-3

Network element management 6-5

Equipment management 6-5

Facility management 6-7

Loopbacks 6-9

Synchronization management 6-11

Connection management 6-17

Equipment protection 6-25

Traffic protection 6-27

1+1 MSP/APS traffic protection 6-30

SNCP/UPSR Traffic Protection 6-33

2-Fiber MS-SPRing/BLSR traffic protection 6-34

Traffic protection exerciser 6-37

Unprotected connections 6-38

Data communications 6-39

Alarm and event management 6-45

Performance monitoring 6-51


6-2 OAM&P description

SDH and SONET Configurations6130 Release 5.0 is a global platform that can be deployed in both SDH and SONET environments. The network element (NE) mode determines the overall function of the network element in either a SDH or SONET environment.

The user uses the Initialize Node Parameters page from the Node Manager (WUI) to set the NE mode to either SDH or SONET during initial commissioning.

Attention: You cannot change the mode from SDH to SONET or vice versa while in-service. To change the mode of the network element, you must first use the “Restore factory default” application to delete all configuration, events, and PM data. Power cycle the network element and then use the Initialize Node Parameters page to enter the required commissioning information and NE mode or to restore from a saved configuration.

The NE mode defines the defaults for some provisioning items as detailed in Table 6-2. Some of these provisioning items can be overridden after the user sets the NE mode.

Attention: All other provisioning items are independent of the NE mode (for example, OAM comms and security).

Security and administration 6-61

Auto discovery 6-69

Backing up and restoring the network element database 6-69

Installing and upgrading network element 6-70

Table 6-1 (continued)Topics in this chapter


OAM&P description 6-3

System Line-up and Test (SLAT)System Line-up and Test (SLAT) is a two part process consisting of commissioning an 6130 network element and system testing. Commissioning brings a newly installed 6130 network element to an in-service state ready to carry traffic. System testing consists of performing a traffic continuity and performance test of the network.

Commissioning processThe commissioning process starts after completion of the installation of the 6130 chassis into a 19”, 21” or 23” rack, circuit packs in the aggregate and tributary slots, service cables and optical fibers routed but not connected, and power cables connected but power switched off.

The commissioning process can be broken down into the following phases:

• network element powering up

In this phase, the user verifies the network element equipment and the power supply, and then powers up the shelf.

Table 6-2NE mode - differences between SONET and SDH

Provisioning item SONET mode SDH mode

Cannot be overridden by user

Port mode Optical ports support OC-n interfaces

Optical ports support STM-n interfaces

Linear protection mode Supports 1+1 APS linear (Telcordia GR-253)

Supports 1+1 MSP linear (ITU-T G.841)

Ring protection terminology Uses UPSR or BLSR Uses SNCP or MS-SPRing

ESI/ESO mode Supports DS1 (1.5 Mbit/s) interfaces

Supports 2 MHz and E1 (2 Mbit/s) interfaces

SSM format Optical and ESI/ESO ports use SONET quality levels

Optical and ESI/ESO ports use SDH quality levels

PMs Supports bit based PMs Supports block based PMs

Connection terminology Uses VT and STS Uses VC

Can be overridden by user

E1/DS1 service E1 or DS1 for all ports on the 28xE1/DS1 and 28xE1/DS1(W/P) circuit packs

E1 or DS1 for all ports on the 28xE1/DS1 and 28xE1/DS1(W/P) circuit packs

E3/DS3 service E3 or DS3 service for each port E3 or DS3 service for each port



• network element commissioning

In this phase, the user logs in to the 6130 network element by connecting to the Craft port on the OAM circuit pack. The user uses the Initialize Node Parameters WUI page to either restore a saved configuration onto the new network element or manually enter the network element commissioning data and DCN parameters.

The NE mode (SDH or SONET) is entered during commissioning.

Supported node redundancy modes:

— non-redundant mode:

– If the node redundancy mode is provisioned to non-redundant, then the 6130 NE must be equipped with one 2x155/622M aggregate circuit pack (NT6Q45AA).

— redundant mode:

– If the node redundancy mode is provisioned to redundant, then the 6130 NE must be equipped with two 1x155/622M aggregate circuit packs (NT6Q46AAE5) or two 1x2.5G aggregate circuit packs (NT6Q47AAE5) or two 1x2.5G+4x155M/2x622M aggregate circuit pack (NT6Q48AAE5).

Supported node capacity values:

— STM-4/16/OC-12/48:

– If the 6130 NE is equipped with two 1x2.5G aggregate circuit packs (NT6Q47AAE5), then the line rate is STM-4/OC-12 or STM-16/OC-48.

– If the 6130 NE is equipped with two 1x2.5G+4x155M/2x622M aggregate circuit packs (NT6Q48AAE5), then the line rate is STM-4/OC-12 or STM-16/OC-48 and the tributary ports on the aggregate card are configurable as either 4x STM-1/OC-3 or 2x STM-4/OC-12 or 1x STM-4/OC-12 + 2x STM-1/OC-3.

Attention: When the line rate of the 1x2.5G+4x155M/2x622M aggregate circuit packs (NT6Q48AAE5) is STM-4/OC-12, the tributary ports on the aggregate card are configured as 4x STM-1/OC-3 ports.

When the line rate of the 1x2.5G+4x155M/2x622M aggregate circuit packs (NT6Q48AAE5) is STM-16/OC-48, the tributary ports on the aggregate card are configurable to either 4x STM-1/OC-3 ports or 2x STM-4/OC-12 ports.

— STM-1/OC-3 or STM-4/OC-12:



– If the 6130 NE is equipped with one 2x155/622M aggregate circuit pack (NT6Q45AA) or two 1x155/622M aggregate circuit packs (NT6Q46AAE5), then the node capability is provisioned to either STM-1/OC-3 or STM-4/OC-12 during initial commissioning from the Initialize Node Parameters WUI application. The two SFP interfaces of the aggregate circuit pack(s) are operating at the rate of the node capability value.

Attention: You cannot change the node capability from STM-1/OC-3 to STM-4/OC-12 or vice versa on the 2x155/622M aggregate circuit pack while in-service. To change the node capability of the network element, you must first use the “Restore factory default” application to delete all configuration, events, and PM data. Power cycle the network element and then use the Initialize Node Parameters WUI page to enter the required commissioning information and node capability or to restore from a saved configuration.

Testing processThe testing process occurs after the user has completed the powering up and commissioning of the 6130 network element. The testing process consists of a system level test as follows:

• system testing

The user performs system testing after all the network elements for a system are physically connected into a linear or ring configuration. In this phase, the user sets up and verifies the system configuration, connects the test equipment, establishes a loopback, provisions a traffic connection, and performs a traffic continuity and performance test on the system.

Refer to Installation, Commissioning and Testing Procedures, 323-1855-201, for detailed installation, commissioning, and system testing procedures.

Network element managementNE information page is an application that allows you to retrieve general information for the network element. You can display and/or edit different network element parameters (name, IP provisioning, contact, location).

Equipment managementIn 6130, equipment is a logical entity and is the software representation of a circuit pack. The user provisioned data about a circuit pack is stored in the corresponding equipment object and the equipment object is not deleted from the node inventory list when a circuit pack is removed. The equipment entities for the 6130 platform are as follows:

• chassis

• 2x155/622M aggregate circuit pack




• 1x2.5G aggregate circuit pack

• 1x2.5G+4x155/2x622M aggregate circuit pack

• Transmux circuit pack

• 8xGE EoPDH L2













• 84xE1/DS1 1:N I/O module




• power supply unit


• fan module

• SFP modules

The 6130 supports automatic detection of new circuit packs in the tributary slots. After insertion of a circuit pack in a previously unprovisioned tributary slot, the system autoprovisions the circuit pack with default values and places the circuit pack in-service. The circuit packs are immediately visible in the OAM&P management system through applications such as Node inventory and Node slot view. Similarly, the SFP modules inserted into the STM-1/4/16/OC-3/12/48,100FX and GE ports are automatically detected and are auto-provisioned in-service. The SFP status and details are presented in the Node inventory application.



Before you can delete the equipment from the inventory, you must physically remove the module from its slot. For more information, refer to Provisioning and Protection Switching Procedures, 323-1855-310.

Facility managementA facility represents an equipment’s OAM&P capabilities that allows the user to provision, inspect, and control that interface. For the 6130, a facility represents an optical, electrical or service interfaces, such as:

• STM-1/4/16/OC-3/12/48 interfaces on the aggregate circuit pack(s)

• STM-1/OC-3 interfaces on the 2x155M circuit pack

• STM-1/4/OC-3/12 interfaces on the 2x622M/8x155M circuit pack

• STM-1/4/16/OC-3/12/48 interfaces on the 2x622M/8x155M Rev2 circuit pack

• 10/100BT Ethernet interface ports on the 8xETH circuit pack, 4x10/100BT+4x100FX L1 circuit pack, 2xGE+8x10/100BT L1 circuit pack, L2PA622M circuit pack and L2PA1G2 circuit pack.

• 100Base-FX (100FX) Ethernet interface ports on the 4x10/100BT+4x100FX L1 circuit pack, L2PA622M circuit pack and L2PA1G2 circuit pack

• GE optical interfaces on the 2xGE circuit pack, 2xGE+8x10/100BT L1 circuit pack, L2PA622M circuit pack, L2PA1G2 circuit pack and 8xGE EoPDH L2 circuit pack.

• 100/1000BT Ethernet interface ports on the 8xGE EoPDH L2

• WAN ports associated to 10/100BT, 100FX and GE interface ports

• E1/DS1 interface ports on the 28xE1/DS1 and 28xE1/DS1(W/P) circuit packs

• E1/DS1 interface ports on the 63xE1/DS1circuit packs

• E3/DS3 interface ports on the 3xE3/DS3, 3xE3/DS3(W/P) and Transmux circuit packs

For a complete list of editable and retrievable facility parameters, refer to Provisioning and Protection Switching Procedures, 323-1855-310.

Managing facilitiesFacility provisioning is a nodal function that allows you to query and edit facility attributes on a specific interface.

The user manages facilities from the corresponding application menu in the Provisioning main menu:

• STM/OCn

• Ethernet



• WAN

• E1/E3/DS1/DS3

By default, the facility is Admin down. When a cross-connect is provisioned with a PDH/DSn facility, its Admin status is automatically changed to Admin Up. When you change a facility from Admin Up to the Admin Down state, the following occurs:

• STM/OCn facility

— traffic will not be carried on the port

— Tx laser is shut off

— alarms present on the port are cleared

— alarm conditions are not declared

— performance monitoring is terminated

— DCC will be disabled

• E1/E3/DS1/DS3 facility





• 10/100/1000BT Ethernet facility


— Client Signal Fail will be sent on the WAN facility




• 100FX and GE facility


— Tx laser is shut off

— Client Signal Fail will be sent on the WAN facility






Attention: For the 8xETH circuit pack, 4x10/100BT+4x100FX L1 circuit pack 2xGE circuit pack and 2xGE+8x10/100BT L1 circuit pack, the WAN state follows the state of the associated 10/100BT, 100FX or GE port. If a 10/100BT, 100FX or GE facility is placed in admin down state, the corresponding WAN state will automatically be placed to admin down.

LoopbacksThe 6130 supports loopbacks on STM-1/4/16/OC-3/12/48, 10/100BT, 100FX, GE, E1/DS1 and E3/DS3 ports:

• Facility - the received signal is looped back towards the transmitter port immediately on entering the interface port.

• Terminal - the signal is looped back towards the cross-connect on the aggregate circuit pack just before reaching the interface transmitter.

Figure 6-1 provides an overview of terminal and facility loopbacks.

Figure 6-1Facility and terminal loopbacks

In Release 5.0, Network Interface Unit (NIU) loopback on E1/DS1 is supported on shelves equipped with the 2x155/622M, 1x155/622M or 1x2.5G+4x155M/2x622M aggregate circuit pack. Upon receiving a loop-up or loop-down code, a terminal/facility loopback will be created. DS1/E1 NIU loopback is in accordance to ANSI T1.403-1999 standard. NIU loopback is supported on the HDE chassis for the following interfaces:

– 28xE1/DS1 Circuit Pack- Rev2 (NT6Q10MAE5)

– 28xE1/DS1 Circuit Pack Ext Temp (NT6Q10BAE5)

– 63xE1/DS1 Circuit Pack (unprotected) (NT6Q11AAE5)

Facility loopback

RxAIS

STM-1/OC-3 optical interface portsE1/DS1 and E3/DS3 services

Tx

Terminal loopback

Rx

Tx

STM-1/4/16/OC-3/12/48 interface portsE1, DS1, E3, DS3, 10/100BT, 100FX and GE services



Table 6-3 on page 6-10 summarizes the type of loopbacks types, the code and framing type.

Table 6-4 on page 6-10 summarizes the supported loopback types for the different ports and the appropriate AIS alarm conditioning.

The user performs loopbacks on an STM-1/4/16/OC-3/12/48, 10/100BT, 100FX, GE, E1/DS1 and E3/DS3 ports from the Maintenance application in the main menu of the local craft access terminal. A facility and a terminal loopback cannot be performed on the same interface port at the same time.

For complete procedures, refer to Provisioning and Protection Switching Procedures, 323-1855-310.

Table 6-3NIU Loopback

DS1 Loop type/Equip. Location

Loop-up code Loop-down code In/Out-Band

Unframed CSU/Terminal 10000 100 In-Band

SF CSU/Terminal 10000 100 In-Band

ESF CSU/Terminal 10000 100 In-Band

Line/Facility 0000 1110 1111 1111 0011 1000 1111 1111 Out of Band

CSU/Terminal 0010 0000 1111 1111 0010 0100 1111 1111 Out of Band

Note 1: CSU: Channel Service Unit

Note 2: Unframed CSU/Terminal NIU Loopback is not supported on the 63xE1/DS1circuit pack.

Table 6-4Loopbacks and AIS alarm conditioning

Port type Facility loopback AIS injection on facility loopback

Terminal loopback

AIS injection on terminal loopback

STM-n/OC-n Yes Yes Yes No

E1/DS1 Yes Yes Yes Yes

E3/DS3 Yes No Yes Yes

10/100BT & 100FX Yes (Note 1) No Yes No

GE (Note 2) Yes No Yes No

Note 1: Facility loopback is supported on the 10/100BT and 100FX ports of the 2xGE+8x10/100BT L1 1.2G, L2PA622M and L2PA1G2 circuit packs. Facility loopback is not supported on the 10/100BT and 100FX ports of the 8xETH and 4x10/100BT+4x100FX circuit pack.

Note 2: Loopback is not supported on the 8xGE EoPDH L2 circuit pack.



Synchronization managementSynchronization is a network level application that ensures all nodes across a network can trace back to the same clock source. Within a single node, synchronization prevents buffer overflow or underflow which avoids bit errors.

Synchronization provisioning on the 6130 is nodal based. However synchronization must be planned at a network level to avoid hierarchy violations and timing loops that cause excessive jitter and can result in traffic loss.

A network level synchronization plan must take into consideration the requirements for synchronization sources to be used for timing generation and timing distribution. A detailed plan must be available to define how to provision the synchronization parameters on the 6130 network element at each site.

Timing generationTiming generation is the ability of the 6130 to extract and use the synchronization reference from any of the defined synchronization inputs. The 6130 generates shelf timing signals based on external, line or internal (freerun or holdover) references. The 6130 supports a timing generation hierarchy for two timing references.

The 6130 is capable of generating a 4.6 ppm quality clock internally. This clock is the default synchronization reference. The 6130 supports synchronizing to a reference clock signal derived from the following sources (provisioned by the user as defined by the network synchronization plan):

• internal timing

When the internal clock is provisioned as a timing reference, the network element goes to internal freerun mode rather than holdover mode, when the internal clock becomes the active timing reference. See Figure 6-2 on page 6-13 example (a).



• external timing

As shown in Figure 6-2 on page 6-13 example (b), from the external synchronization input (ESI) port on the OAM circuit pack, the 6130 supports external timing reference inputs. The supported BITS signals are detailed in Table 6-5 on page 6-12:

The following needs to be considered when using an external source to provide the timing reference for the 6130:

— the external timing source and its quality

— the signal format of the external timing source (E1 or 2.048 MHz for SDH, DS1 ESF for SONET)

— the connector type/impedance of the ESI port (120/100 ohm balanced or 75 ohm unbalanced)

• line timing

Line timing is a clock derived from an STM-1/4/16/OC-3/12/48 interface or an E1/DS1 port. See Figure 6-2 on page 6-13 example (c).

When using line timing to provide the timing reference for the 6130, you may consider one of the following sources:

— one or two STM-1/4/16/OC-3/12/48 ports on the aggregate circuit pack

— one or two STM-1/OC-3 ports on the 2x155M circuit pack

— one or two STM-1/4/OC-3/12 ports on the 2x622M/8x155M circuit pack

— one or two STM-1/4/16/OC-3/12/48 ports on the 2x622M/8x155M Rev2 circuit pack

— any of 1, 4, 7, 10, 13, 16, 19, 22, 25 or 28 E1/DS1 ports of the 28 x E1/DS1 circuit pack

— any E1/DS1 port of the 63xE1/DS1circuit pack.

— any of 1, 4, 7, 10, 13 E1/DS1 ports of the 28 x E1/DS1(W/P) circuit pack

Table 6-5Supported BITS signals

BITS-1-2-1 BITS-1-2-2 NE mode

In Out In Out

2 MHz 2 MHz E1 (2 Mb/s) E1 (2 Mb/s) SDH

DS1 DS1 DS1 DS1 SONET



The 6130 can identify a faulty synchronization source and switch to the next highest quality source as defined in the input hierarchy. When all synchronization sources (external or line) are unavailable (caused by faulty sources or lockouts), the 6130 falls into holdover mode. In the holdover mode, the internal clock operates at a fixed frequency according to the last known frequency reference for a minimum of 24 hours followed by freerun mode (internal stratum 3 [ST3]/G.813 Option 1 compliant 4.6ppm clock). See Figure 6-2 on page 6-13 example (a).

Refer to Viewing and management on page 6-16 for information about the Synchronization application in the Configuration main menu of the local craft access terminal for the 6130.

Figure 6-2Flow of synchronization timing signals



Timing distributionTiming distribution is the ability of the 6130 to provide a synchronization reference to external devices. The 6130 supports the following timing distribution reference signals:

• CLKOUT and DATAOUT ports on the ESI port located on the faceplate of the OAM circuit pack

• one or two STM-1/4/16/OC-3/12/48 line ports on the aggregate circuit pack

• up to four STM-1/4/OC-3/12 tributary ports on the 1x2.5G+4x155M/2x622M aggregate circuit pack

• one or two STM-1/OC-3 ports on the 2x155M circuit pack

• up to eight STM-1/4/16/OC-3/12/48 ports on the 2x622M/8x155M circuit pack

The following items need to be considered when using the 6130 as a timing source.

• the signal format of the external timing source (E1 or 2.048 MHz for SDH, DS1 for SONET)

• the connector type/impedance of the ESI port (120/100 ohm balanced or 75 ohm unbalanced)

• the reference sources to be used for timing distribution and the hierarchy

Synchronization operating modesThe 6130 synchronization operating modes describe the state that the synchronization hardware is operating in. These modes are not provisionable by the user and consists of the following:

• freerun

• locked

• holdover

Freerun modeIn freerun mode, the system clock is not locked to a timing reference and runs at its natural frequency. The synchronization hardware on the aggregate circuit pack provides timing references quality as specified in internal G.813 Option 1/stratum 3 (ST3) (4.6 ppm). The 6130 is in this mode if the user has provisioned the shelf timing as internal or the holdover period has expired in which case a warning condition is raised to advise the user.

Locked modeIn locked mode, the system clock is locked to a timing reference. The 6130 is in this mode when a timing reference is active and working during trouble free operations.



Holdover modeThe synchronization hardware enters holdover mode automatically if the target mode is locked but all timing references have become unavailable. The system clock in the synchronization hardware holds within a certain frequency range of the last locked-in timing reference in which case a warning condition is raised to advise the user.

When a timing reference becomes available again, the synchronization hardware automatically transitions to locked mode. The synchronization hardware remains in holdover mode for a minimum of 24 hours. After holdover mode, the synchronization hardware enters the freerun mode.

Synchronization status messagesSynchronization status messages (SSM) indicate the quality of the timing signals currently available to a network element. The timing sources that can be provisioned in a network element include external timing (ESI), line timing (timing derived from STM-1/4/16/OC-3/12/48 interfaces or E1/DS1 signals), and the internal clock of the network element.

A network element can select the best of the two timing signals provided by the timing sources provisioned by the user. The selection is based on the quality values carried in the SSMs if the quality mode is enabled, otherwise, the selection is based on the priority level set by the user. As the timing passes from one network element to the next, each network element sends SSMs. If the quality of the timing changes, the SSMs inform the next network element of the change.

If a timing reference is not to be used for synchronization, the SSM will contain a do not use for synchronization (DNU) message. See Table 6-6 on page 6-15 for an overview of SSM designations supported by 6130 in SDH mode and see Table 6-7 on page 6-16 for the SSM designations in SONET mode.

Table 6-6Synchronization status messages in SDH mode

Description Designation Quality Level

S1 bits (5-8)

Traceable to Primary Reference Clock PRC 2 0010

Traceable to Transit Clock SSU-A 4 0100

Traceable to Local Clock SSU-B 8 1000

Traceable to SDH Equipment Clock SEC 11 1011

Do Not Use for Synchronization DNU 15 1111



Attention: If the incoming quality level is not recognized by the 6130, the quality level is displayed as invalid. To use a timing source with an invalid quality level as a timing reference, the user must override the invalid quality level.

The incoming quality level can not be overwritten if the timing source is an STM-1/4/16/OC-3/12/48 interface port.

Quality level overridesA user can specify or override the SSM quality level of an incoming or outgoing timing source.

The user can specify the incoming quality level if the timing source comes from equipment that does not support SSM (for example, legacy BITS equipment). To avoid timing loops do not override the quality level of an incoming timing source if SSM is supported.

The outgoing override can be used when a remote network element expects a particular SSM value.

Viewing and managementThe network element provides all required synchronization source information from the local craft access terminal. The Synchronization application in the Configuration main menu allows users to view and provision synchronization parameters for an 6130 network element.

Table 6-7Synchronization status messages in SONET mode

Description Designation Quality Level

S1 bits (5-8)

Stratum 1 Traceable PRS 1 0001

Synchronized - Traceability Unknown STU 2 0000

Stratum 2 Traceable ST2 3 0111

Transit Node Clock Traceable TNC 4 0100

Stratum 3E Traceable ST3E 5 1101

Stratum 3 Traceable ST3 6 1010

SONET Minimum Clock Traceable SMC 7 1100

Don’t Use for Synchronization DUS 9 1111



For complete procedures, refer to Provisioning and Protection Switching Procedures, 323-1855-310.

Synchronization protectionSynchronization protection deals with the protection of the timing references. The 6130 supports the protection of the timing reference used for timing generation. The timing generation reference for the system is selected from the pool of provisioned reference sources.

From the local craft access terminal, the Timing Manager application in the Protection main menu displays the protection status of the provisioned synchronization hierarchies for the network element. The application shows the source state, current quality level, and any active synchronization protection switches on the sources for each hierarchy. Synchronization protection switches include the following:

• automatic switch

• manual switch

• forced switch

• lockout

For more information synchronization protection, refer to Provisioning and Protection Switching Procedures, 323-1855-310.

Connection managementIn the 6130 architecture, traffic is switched between interface ports on the circuit packs through the cross-connect matrix located on the aggregate circuit packs.

6130 supports the following connection management capabilities:

• fully non-blocking cross-connects at VC11/VT1.5, VC12/VT2, VC3/STS-1, VC4/STS-3c and VC4-4c/STS-12c granularity

Attention: In SDH mode, only Low Order VC3/TU3/AU4 mapping (LO_VC3) is supported. The interworking with other products is not supported with High Order VC3 (HO_VC3) connections.

STS-3c, VC-4-4c/STS-12c connections are not supported in MS-SPRing/BLSR configurations.

• contiguous concatenated connections for VC4/STS-3c and VC4-4c/STS-12c rates



• virtual concatenated connections for VC11/VC12/VT1.5-nv, where n = 1 to 63 or VC3/STS-1-nv, where n = 1 to 3 for the 10/100BT and 100FX ports

• virtual concatenated connections for VC3/STS-1-nv, where n = 1 to 12 and VC4/STS-3c-nv, where n = 1 to 4 for the GE ports of the 2xGE circuit pack

• virtual concatenated connections for VC11/12/VT1.5-nv, where n = 1 to 63 or VC3/STS-1-nv, where n = 1 to 24 or VC4/STS-3c-nv, where n = 1 to 8 for the GE ports of the 2xGE+8x10/100BT L1 1.2G circuit pack

• maximum WAN bandwidth for Ethernet tributary circuit packs:

— the total WAN bandwidth available for connections on the 8xETH circuit pack or 4x10/100BT+4x100FX L1 circuit pack is STM-1/STS-3c (155 Mb/s). The bandwidth is shared between the 10/100BT and/or 100FX ports of the circuit pack

— the total WAN bandwidth available for connections on the 4x10/100BT+4x100FX L1 622M circuit pack is 4xSTM-1/STS-3c (622 Mb/s). The bandwidth is shared between the 10/100BT and/or 100FX ports of the circuit pack

— the total WAN bandwidth available for connections on the 2xGE circuit pack is 4 x STM-1/STS-3c (622 Mb/s). The bandwidth is shared between the two GE ports of the circuit pack

— the total WAN bandwidth available for connections on the 2xGE+8x10/100BT L1 1.2G circuit pack is 8 x STM-1/STS-3c (1.2Gb/s). The bandwidth is shared between the 10 ports of the circuit pack.

— the total WAN bandwidth available for connections on the L2PA622M circuit pack is 4 x STM-1/STS-3c (622 Mb/s). The bandwidth is shared between the eight WAN ports of the circuit pack

— the total WAN bandwidth available for connections on the L2PA1G2 circuit pack is 8 x STM-1/STS-3c (1.2Gb/s). The bandwidth is shared between the ten WAN ports of the circuit pack

— the total WAN bandwidth available for connections on the 8xGE EoPDH L2 circuit pack is STM-4 (622 Mb/s). The bandwidth is shared between the 128 WAN ports of the circuit pack

• If the 6130 NE is equipped with one 2x155/622M aggregate circuit pack or two 1x155/622M aggregate circuit packs and the NE is commissioned with the node capacity parameter set to STM-4/OC-12 rate, then the total bandwidth available for connections on the NE is 16 x STM-1/STS-3c (2.5 Gb/s).

— half of the bandwidth (8 x STM-1/STS-3c or 1.25 Gb/s) is dedicated to the two STM-4/OC-12 interfaces of the aggregate circuit pack(s)



— half of the bandwidth (8 x STM-1/STS-3c or 1.25 Gb/s) is shared between the four tributary circuit packs. Each tributary slot can use a maximum of (4x STM-1/STS-3c or 622 Mb/s)

— the granularity of the bandwidth distribution among the tributary circuit pack is STM-1/STS-3c. That is, the 8 x STM-1/STS-3c are distributed to the tributary circuit packs with a granularity of STM-1/STS-3c.

– For example, if slot 4 is using one STM-1/STS-3c, slot 5 is using four STM-1/STS-3c and slot 8 is using two STM-1/STS-3c, then the remaining bandwidth available for slot 9 is limited to one STM-1/STS-3c

– For example, if slot 4 is using 4 STM-1/STS-3c and slot 5 is using four STM-1/STS-3c then there is no remaining bandwidth available for slots 8 and 9.

• If the 6130 NE is equipped with two 1x2.5G aggregate circuit packs, then the total bandwidth available for connections on the NE is 48 x STM-1/STS-3c (7.5 Gb/s).

— two third of the bandwidth (32 x STM-1/STS-3c or 5 Gb/s) is dedicated to the two STM-16/OC-48 interfaces of the aggregate circuit packs

— one third of the bandwidth (16 x STM-1/STS-3c or 2.5 Gb/s) is shared between the four tributary circuit packs. Each tributary slot can use a maximum of (8x STM-1/STS-3c or 1.2 Gb/s).

— the granularity of the bandwidth distribution among the tributary circuit pack is STM-1/STS-3c. That is, the 16 x STM-1/STS-3c are distributed to the tributary circuit packs with a granularity of STM-1/STS-3c.

– For example, each tributary slot can use 4 x STM-1/STS-3c (622 Mb/s) worth of bandwidth

– For example, 2 tributary slots can each use 8 x STM-1/STS-3c (1.2 Gb/s) worth of bandwidth. In this case, there is no bandwidth left for the other 2 tributary slots.

• If the 6130 NE is equipped with two 1x2.5G+4x155M/2x622M aggregate circuit packs, then the total bandwidth available for connections on the NE is 96x STM-1/STS-3c (15 Gb/s).

— 32 x STM-1/STS-3c or 5 Gb/s is dedicated to the two STM-4/16/OC-12/48 line interfaces of the aggregate circuit packs

— 48 x STM-1/STS-3c or 7.5 Gb/s is dedicated to the four tributary circuit packs in slots. Slot 4&8 have 1.25G each and slot 5&9 have 2.5G each. Slot 4&8 can each use a maximum of (8x STM-1/STS-3c or 1.25Gb/s worth of bandwidth). Slot 5&9 can each use a maximum of (16x STM-1/STS-3c or 2.5 Gb/s worth of bandwidth).

— 16 x STM-1/STS-3c or 2.5 Gb/s is dedicated to the 4x155M/2x622M tributary ports of the 1x2.5G+4x155M/2x622M aggregate cards.



• PDH/DSn signals mapping:

— E1 to VC12/VT-2

— DS1 to VC11/VT-1.5

— E3 to VC3/STS-1

— DS3 to VC3/STS-1

• bandwidth management models:

— bidirectional connection type

— unidirectional connection type

— hair-pinning

— drop and continue

— dual-cast (bridge)

Attention: Only bidirectional connection type is supported for WAN ports corresponding to the 10/100/1000BT, 100FX and GE ports.

All services (Ethernet, E1/DS1 and E3/DS3) are mapped to the appropriate VC/VT/STS containers. The 6130 uses Generic Framing Procedure (GFP) as its standards based SDH/SONET mapping for Ethernet services.

Generic Framing ProcedureGFP is an ITU standard (G.7041) which describes a flexible mapping technique for transparent transport of multiple protocols in SDH and SONET. GFP provides an efficient mechanism for Ethernet data services to be transported over an SDH/SONET network via efficiently mapping varying client signals into VC/VT/STS containers with a virtual concatenation group (VCG). 6130 supports:

• Framed-mapped GFP (GFP-F), which maps one frame or packet of client signal in one GFP frame. GFP-F processes client signal data streams on a protocol data unit (PDU) basis and maps these streams into GFP-F frames one packet at a time. GFP-F is recommended for Ethernet services as it provides flow control capability and performance monitoring.

In GFP-F, idle frames are inserted as necessary to fill the transport payload. Multiple GFP-F frames can be aggregated in a single SDH/SONET payload.



Table 6-8 provides a summary of the service mappings and interconnection type supported in 6130 Release 5.0.

Table 6-86130 service mapping

Service Mapping Interconnection type

STM-1/OC-3

• VC11/VT1.5, VC12/VT2, VC3/STS-1, VC4/STS-3c

• non-concatenated at VC11/VT1.5, VC12/VT2, VC3/STS-1, VC4 level

• contiguous concatenation at STS-3c

STM-4/OC-12

• VC11/VT1.5, VC12/VT2, VC3/STS-1, VC4/STS-3c, VC4-4c/STS-12c

• non-concatenated at VC11/VT1.5, VC12/VT2, VC3/STS-1, VC4

• contiguous concatenation at STS-3c, VC4-4c/STS-12c

STM-16/OC-48

• VC11/VT1.5, VC12/VT2, VC3/STS-1, VC4/STS-3c, VC4-4c/STS-12c

• non-concatenated at VC11/VT1.5, VC12/VT2, VC3/STS-1, VC4

• contiguous concatenation at STS-3c, VC4-4c/STS-12c

10/100BT • SDH mode:

— GFP-F to VC11, VC12, VC3 and VC4

— GFP-F to VC11, VC12-nv (n=1 to 63), VC3-nv (n=1 to 3) and VC4

• SONET mode:

— GFP-F to VT1.5, STS-1, STS-3c

— GFP-F to VT1.5-nv (n=1 to 63), STS-1 (n=1 to 3) and STS-3c

• SDH mode:

— non-concatenated at VC11, VC12, VC3 and VC4 level

— virtual concatenation at VC11, VC12-nv (n=1 to 63) and VC3-nv (n=1 to 3)

• SONET mode:

— non-concatenated at VT1.5, STS-1, STS-3c level

— virtual concatenation at VT1.5-nv (n=1 to 63) and STS-1 (n=1 to 3)

100FX • SDH mode:

— GFP-F to VC11, VC12, VC3 and VC4

— GFP-F to VC11, VC12-nv (n=1 to 63), VC3-nv (n=1 to 3) and VC4

• SONET mode:

— GFP-F to VT1.5, STS-1, STS-3c

— GFP-F to VT1.5-nv (n=1 to 63), STS-1 (n=1 to 3) and STS-3c

• SDH mode:

— non-concatenated at VC11, VC12, VC3 and VC4 level

— virtual concatenation at VC-11, VC12-nv (n=1 to 63) and VC3-nv (n=1 to 3)

• SONET mode:

— non-concatenated at VT1.5, STS-1, STS-3c level

— virtual concatenation at VT1.5-nv (n=1 to 63) and STS-1 (n=1 to 3)



GE ports on the 2XGE circuit pack

• SDH mode:

— GFP-F to VC3, and VC4

— GFP-F to VC3-nv (n=1 to 12) and VC4-nv (n=1 to 4)

• SONET mode:

— GFP-F to STS-1 and STS-3c

— GFP-F to STS-1 (n=1 to 12) and STS-3c (n=1 to 4)

• SDH mode:

— non-concatenated at VC3, and VC4 level

— virtual concatenation at VC3-nv (n=1 to 12) and VC4-nv (n=1 to 4)

• SONET mode:

— non-concatenated at STS-1, and STS-3c level

— virtual concatenation at STS-1 (n=1 to 12) and STS-3c (n=1 to 4)

GE ports on the 2XGE+8x10/100BT L1 1.2G circuit pack

• SDH mode:

— GFP-F to VC3, and VC4

— GFP-F to VC3-nv (n=1 to 24) and VC4-nv (n=1 to 8)

• SONET mode:

— GFP-F to STS-1 and STS-3c

— GFP-F to STS-1 (n=1 to 24) and STS-3c (n=1 to 8)

• SDH mode:

— non-concatenated at VC3, and VC4 level

— virtual concatenation at VC3-nv (n=1 to 24) and VC4-nv (n=1 to 8)

• SONET mode:

— non-concatenated at STS-1, and STS-3c level

— virtual concatenation at STS-1 (n=1 to 24) and STS-3c (n=1 to 8)

E1 • VC12/TU12/AU4 (SDH mode)

• VT2/STS1 (SONET mode)

• non-concatenated at VC12/VT2 level

Table 6-8 (continued)6130 service mapping




10/100BT, 100FX, GE and PDH services are mapped to SDH/SONET containers and assigned as SDH/SONET level connections to STM-1/4/16/OC-3/12/48 interfaces. The traffic protection schemes supported by the STM-1/4/16/OC-3/12/48 interfaces can therefore be used to provide a protected Ethernet, E1/DS1 or E3/DS3 service without the requirement of a redundant handoff from the subtending 10/100BT, 100FX, GE, E1/DS1 or E3/DS3 equipment. See Traffic protection on page 6-27 for more information.

DS1 • VC11/TU11/AU4 (SDH mode)

• VT1.5/STS-1 (SONET mode)

• non-concatenated at VC11/VT1.5 level

E3/DS3 • VC3/TU3/AU4 (SDH mode)

• STS-1 (SONET mode)

• non-concatenated at VC3/STS-1 level

100/1000BT and 1000 Base SX/LX/ZX on the 8xGE EoPDH L2 circuit pack

• EoS in SDH mode, GFP-F to:

— VC-12-nv, n= 1 to 63

— VC-11-nv, n= 1 to 63

— VC-3-nv, n= 1 to 12

— VC-4-nv, n= 1 to 4

• EoPDH in SDH mode, GFP-F to:

— VC-12-E1-nv, n= 1 to 16

— VC-3-E3-nv, n= 1 to 8

— VC-3-DS3-nv, n= 1 to 8

• EoS in SONET mode, GFP-F to:

— VT-1.5-nv, n= 1 to 63

— Vt-2-nv, n= 1 to 63

— STS-3c-nv, n= 1 to 4

• EoPDH in SONET mode, GFP-F to:

— VC-12-nv, n= 1 to 63

— VC-11-nv, n= 1 to 63

— VC-3-nv, n= 1 to 12

— VC-4-nv, n= 1 to 4

• Virtual concatenation

Table 6-8 (continued)6130 service mapping




Hair-pinningThe 6130 provides the ability to provision hairpin connections for PDH services.

• E1-to-E1

• DS1-to-DS1

• E3-to-E3

• DS3-to-DS3

Connection management application6130 connection management is based on a nodal, port-to-port connection management philosophy that takes protection schemes into account to rearrange connections at the physical level to implement traffic protection. See Traffic protection on page 6-27 for more details.

The Cross-connect application in the local craft access terminal allows the user to perform the following:

• filter, and display nodal connections

• provision nodal connections from any E1/E3/DS1/DS3 interface port to any available timeslot of an STM-1/4/16/OC-3/12/48 interface or of another E1/E3/DS1/DS3 interface port on the same 6130 network element. Each cross-connect can have a Circuit Identifier which allows the user to label the cross-connect.

Attention: The systems blocks any cross-connects that are illegal. For example, if a low-order VC12/VT1.5 cross-connect is provisioned, the system blocks the addition of VC3/VC4/STS cross-connects for the corresponding timeslot.

• delete a nodal connection (supports multiple deletes)

The WAN application in the Facilities menu of the local craft access terminal allows the user to perform the following:

• provision VC/VT/STS associations within a WAN from any 10/100/1000BT, 100FX or GE interface port to any available timeslot of an STM-1/4/16/OC-3/12/48 interface on the same 6130 network element.

• if VCAT is enabled for a WAN facility, then bulk connections can be added by the user (i.e. provisioning of multiple contiguous connections in a single command)

• delete a VC/VT/STS association within a WAN (supports multiple deletes)

• click on hyperlink to Cross-connect application to filter, display or delete nodal connections.



SDH payload instance numberingIn the local craft access terminal, SDH payload instances are displayed using J, K, L, and M format where:

• J is the AU-4 payload number (1 to 16 for STM-16 line rate, 1 to 4 for STM-4 line rate and fixed at 1 for STM-1 line rate)

• K is the TUG-3 payload number (1 to 3)

• L is the TUG-2 payload number (1 to 7)

• M is the TU-12 payload number (1 to 3) or TU-11 payload number (1 to 4)

For example, a format of J = 3, K = 2, L = 6, M = 2 identifies:

• AU-4 number 3

• TUG-3 number 2

• TUG-2 number 6

• TU-12/TU-11 payload number 2

SONET payload instance numberingIn the local craft access terminal, SONET payload instances are displayed using STS #, VT Group, and VT # format where:

• STS # is the STS-1 payload number (1 to 48 for OC-48 line rate, 1 to 12 for OC-12 line rate and 1 to 3 for OC-3 line rate)

• VT Group is the VTG payload number (1 to 7)

• VT # is the VT2 payload number (1 to 3) or VT1.5 payload number (1 to 4)

For example, a format of K = 2, L = 6, M=2 identifies:

• STS-1 number 2

• VTG number 6

• VT2/VT1.5 payload number 2

For detailed procedures and associated rules, refer to Provisioning and Protection Switching Procedures, 323-1855-310.

Equipment protectionEquipment protection detects an equipment failure that causes a loss of service, and restores the failed services to a redundant piece of equipment. Equipment protection manages core functions and services in a network element that are normally traffic affecting. This section provides a definition of 6130 equipment protection, including information about the protection scheme and mode for aggregate card and for tributary cards.



Aggregate Card ProtectionAggregate card protection is provided for the following aggregate circuit packs:

• 1x155/622M aggregate circuit packs (NT6Q46AAE5)

• 1x2.5G aggregate circuit packs (NT6Q47AAE5)

• 1x2.5G+4x155M/2x622M aggregate circuit pack (NT6Q48AAE5)

Performance degradation and/or equipment failure triggers equipment protection. The protection switch can be the result of the following:

• hardware or software failure on the circuit pack

• removal of the circuit pack from the network element

• force switch command (user initiated)

The 6130 supports the following equipment protection scheme and mode when the node redundancy mode is provisioned to redundant:

• 1+1 non-revertive for aggregate circuit packs with the following shelf configurations:

– 6130 NE equipped with two 1x155/622M aggregate circuit packs (NT6Q46AAE5)

– 6130 NE equipped with two 1x2.5G aggregate circuit packs (NT6Q47AAE5)

– 6130 NE equipped with two 1x2.5G+4x155M/2x622M aggregate circuit packs (NT6Q48AAE5)

In non-revertive mode, when the condition that caused the equipment protection switch clears, the working unit does not become active automatically.

Tributary Card ProtectionEquipment protection is supported for the 28xE1/DS1(W/P) and 3xE3/DS3(W/P) tributary circuit packs. Refer to Tributary interface circuit pack on page 4-22 and I/O Modules on page 4-55 for more information.

The following equipment protection schemes are supported:

• 1+1 E1/DS1 tributary equipment protection

– 6130 NE equipped with two 28xE1/DS1(W/P) circuit packs and one 28xE1/DS1 1+1 I/O module.

– 6130 NE equipped with four 28xE1/DS1(W/P) circuit packs and two 28xE1/DS1 1+1 I/O module.

Attention: Revertive and non-revertive modes are supported.



• 1:N (N=3) E1/DS1 tributary equipment protection

– 6130 NE equipped with two (in 1:1 mode) 28xE1/DS1(W/P) circuit packs and one 84xE1/DS1 1:N I/O module.

– 6130 NE equipped with three (in 1:2 mode) 28xE1/DS1(W/P) circuit packs and one 84xE1/DS1 1:N I/O module.

– 6130 NE equipped with four (in 1:3 mode) 28xE1/DS1(W/P) circuit packs and one 84xE1/DS1 1:N I/O module.

Attention: In 1:N mode, priority among the working cards is user configurable. Revertive and non-revertive modes are supported.

• 1+1 E3/DS3 tributary equipment protection

– 6130 NE equipped with two 3xE3/DS3(W/P) circuit packs and one 3xE3/DS3 1+1 I/O module.

– 6130 NE equipped with four 3xE3/DS3(W/P) circuit packs and two 3xE3/DS3 1+1 I/O module.

– 6130 NE equipped with two Transmux circuit packs and one I/O module.

Attention: Revertive and non-revertive modes are supported.

Protection switching under 50ms will be triggered under the following conditions:

• Fault on the circuit pack

• Admin down or up operation on the circuit pack

• Removal of the active circuit pack

• User initiated switching commands

Refer to Shelf equipping rules on page 8-5 for more information.

Traffic protectionTraffic protection is a mechanism to enhance the dependability of a transport service. The 6130 provides a variety of protection mechanisms which can be deployed to tailor the resilience of the platform to that required by the customer. The system monitors the traffic facilities for performance degradation and failure and performs protection switching when these conditions are present. The following traffic protection configurations are currently available:



• 1+1 Multiplex Section Protection (MSP)/Automatic Protection Switching (APS)

• Sub-Network Connection Protection (SNCP)/Unidirectional Path Switch Ring (UPSR)

• 2 Fiber Multiplex Section-Shared Protection Ring (MS-SPRing) / Bidirectional Line-Switched Ring (BLSR)

• unprotected

Table 6-9 provides an overview of the supported traffic protection schemes.

The 6130 can be provisioned to support a mix of 1+1 MSP/APS, SNCP/UPSR and MS-SPRing/BLSR protection and unprotected configurations on the STM-1/4/16/OC3/12/48 interfaces on a network element. Refer to Shelf equipping rules on page 8-5 for more information.

Table 6-9Traffic protection summary

Protection scheme

Interfaces Notes

1+1 MSP/APS STM-1/4/16/OC-3/12/48 interfaces

When MSP/APS is provisioned, SNCP/UPSR connections are not supported on this protection group.

SNCP/UPSR STM-1/4/16/OC-3/12/48 interfaces

STM-1/4/16/OC-3/12/48 interfaces must be provisioned in Unprotected mode.

MS-SPRing/BLSR STM-16/OC-48 STM-16/OC-48 ports of 1x2.5G+4x155M/2x622M aggregate card only

Unprotected STM-1/4/16/OC-3/12/48 interfaces10/100/1000BT services100FX servicesGE servicesE1/DS1 servicesE3/DS3 services

A mix of unprotected and SNCP/UPSR connections can be provisioned on the STM-1/4/16/OC-3/12/48 interfaces.



Traffic Protection applicationThe user performs provisioning of traffic protection by selecting the MSP/APS groups or MS-SPRing/BLSR application in the Configuration main menu of the local craft access terminal.

The MSP/APS groups protection provisioning application displays the protection provisioning data and allows the user to perform the following actions:

• view the protection switch scheme and protection switch mode for the STM-1/4/16/OC-3/12/48 interfaces

• change the protection scheme from 1+1 MSP/APS to unprotected for the STM-1/4/16/OC-3/12/48 interfaces. This operation can be performed only when no connection is provisioned on the 1+1 MSP/APS protection group.

• change the protection scheme from unprotected to 1+1 MSP/APS for the STM-1/4/16/OC-3/12/48 interfaces. This operation can be performed only when no connection is provisioned on the ports that will be used in 1+1 MSP/APS protection group.

• change the protection switching mode from unidirectional (1WAY) to bidirectional (2WAY) and vice versa for the STM-1/4/16/OC-3/12/48 interfaces of the 1+1 MSP/APS protection group

The user performs user-initiated protection switch requests for 1+1 MSP/APS protection groups by selecting the MSP/APS groups application in the Protection main menu of the local craft access terminal. The protection application displays the protection status data and allows the user to perform the following actions:

• operate or release a user-initiated switch request on the 1+1 MSP/APS group for the STM-1/4/16/OC-3/12/48 interfaces

The SNCP/UPSR protection configuration is provisioned upon creation of the nodal cross-connect or the VC/VT/STS association for Ethernet services. For more details on the local craft access terminal applications used to provision SNCP/UPSR traffic protection, refer to Connection management application on page 6-24

The user performs user-initiated protection switch requests for SNCP/UPSR connections by selecting the Connections application in the Protection main menu of the local craft access terminal. The protection application displays the protection status data and allows the user to perform the following actions:

• operate or release a user-initiated switch request on the SNCP/UPSR connections provisioned for the STM-1/4/16/OC-3/12/48 interfaces

The 2-Fiber MS-SPRing /BLSR protection provisioning application displays the protection provisioning data and allows the user to perform the following actions:



• view the protection switch scheme and protection switch mode for the STM-16/OC-48 interfaces of the MS-SPRing /BLSR protection groups

• change the protection scheme from unprotected to MS-SPRing /BLSR for the STM-16/OC-48 interfaces. This operation can be performed only when no connection is provisioned on the ports that will be used in MS-SPRing /BLSR protection group.

• change the protection scheme from MS-SPRing/BLSR to unprotected for the STM-16/OC-48 interfaces of the 1x2.5G+4x155M/2x622M aggregate card. This operation can be performed only when no connection is provisioned on the MS-SPRing/BLSR protection group.

The user performs user-initiated protection switch requests for MS-SPRing /BLSR protection groups by selecting the MS-SPRing / BLSR application in the Protection main menu of the Node Manager (WUI). The protection application displays the protection status data and allows the user to perform the following actions:

• operate or release a user-initiated switch request on the MS-SPRing/BLSR group for the STM-16/OC-48 interfaces

Attention: The default traffic protection mode on the 6130 network element is unprotected.

1+1 MSP/APS traffic protection1+1 MSP/APS traffic protection is supported for the STM-1/4/16/OC-3/12/48 interfaces to provide line traffic protection. 1+1 MSP/APS traffic protection uses the 1+1 MSP/APS protocol to handshake between adjacent network elements to determine when a protection switch should occur. All of the paths/payloads within the line are protected together.

Provisioning MSP/APS protected connectionsThe user performs protection group provisioning from the MSP/APS groups application in the Configuration main menu of the local craft access terminal. The user creates the 1+1 MSP/APS protection group for the STM-1/4/16/OC-3/12/48 interfaces located on the aggregate circuit pack or the 2x155M and 2x622M/8x155M tributary circuit packs.

The working and protection ports of the 1+1 MSP/APS traffic protection group must be provisioned on the same slot (i.e. slot 6 ports 1 and 2) for the STM-1/4/OC-3/12 interfaces of the 2x155/622M aggregate circuit pack.



The working and protection ports of the 1+1 MSP/APS traffic protection group must be provisioned on different slots for the STM-1/4/16/OC-3/12/48 interfaces of the 1x155/622M aggregate circuit packs or 1x2.5G aggregate circuit packs. A mix between ports on a tributary slots (Slots 4, 5, 8, 9) and/or ports on aggregate slots (Slots 6 & 7) is supported.

The working and protection ports of the 1+1 MSP/APS traffic protection groups can be provisioned on the same slot or on different slots for the STM-1/4/16/OC-3/12/48 interfaces of the 2x155M, 2x622M/8x155M tributary circuit packs and 1x2.5G+4x155M/2x622M aggregate cards. A mix between ports on a tributary slots (Slots 4, 5, 8, 9) and/or ports on aggregate slots (Slots 6 & 7) is supported

Example 1: Working and protection ports on same slotThe user can provision a 1+1 MSP/APS traffic protection group with the STM-1/OC-3 slot 4 port 1 as the working port and the STM-1/OC-3 slot 4 port 2 as the protection port.

Example 2: Working and protection ports on different slotsThe user can provision a 1+1 MSP/APS traffic protection group with the STM-1/OC-3 slot 4 port 1 as the working port and the STM-1/OC-3 slot 5 port 1 as the protection port.

Example 3: Working and protection ports on different slotsThe user can provision a 1+1 MSP/APS traffic protection group with the STM-4/OC-12 slot 4 port 1 as the working port and the STM-4/OC-12 aggregate slot 6 port 1 as the protection port.

The user provisions the Protection switching mode as either 2WAY (bidirectional where both transmit and receive directions switch together) or 1WAY (unidirectional where only the transmit or receive directions switched based on the fault or user initiated action). The Admin reversion mode can be set to either revertive or non-revertive. By default, the non-revertive mode is set. When revertive mode is selected, the user must also specify the WTR Time period for the MSP/APS group.

The user provisions the Route Diversity for the 1+1 MSP/APS traffic protection group. The route diversity can be set to enable or disable for the STM-1/4/16/OC-3/12/48 ports. By default, the route diversity is set to enable in SDH mode. By default, the route diversity is set to disable in SONET mode

For detailed procedures for 1+1 MSP/APS protection, refer to Provisioning and Protection Switching Procedures, 323-1855-310.



1+1 MSP/APS protection switch criteria1+1 MSP/APS protection switch request can occur automatically by the system or by user initiated actions. All user-initiated 1+1 MSP/APS switching commands are signaled via MSP/APS channels (K1 and K2 bytes).

Table 6-11 summarizes the hierarchy of protection commands.

For a complete procedures, see Provisioning and Protection Switching Procedures, 323-1855-310.

Table 6-111+1 MSP/APS protection - command hierarchy

Switch request Priority

Lockout of protection 1 (highest)

Auto switch (Signal Fail) on protection 2

Forced switch 3

Auto switch (Signal Fail) on working 4

Auto switch (Signal Degrade) (Working or protection) 5

Manual switch to protection 6

Manual switch to working 7

Wait-to-Restore 8 (lowest)



SNCP/UPSR Traffic ProtectionSNCP/UPSR traffic protection is defined as a 1 + 1 dedicated path protection scheme where the transmit end is permanently bridged to both the working and protection paths of the SNCP/UPSR connection. At the receive end of the SNCP or UPSR connection, a protection switch is performed by selecting one of the signals based on the path status. No 1+1 MSP/APS protocol is required as SNCP/UPSR is defined as a unidirectional protection scheme.

Provisioning SNCP/UPSR connectionsThe user performs SNCP/UPSR connection provisioning from the Cross-connect application in the Configuration main menu of the local craft access terminal. The user selects the source and destination port interfaces for the SNCP/UPSR connection and specifies the appropriate protection requirements for each end-point of the end-to-end connection.

The working and protection paths of the SNCP/UPSR connections can be provisioned on any timeslots, any ports and any slots for the STM-1/4/16/OC-3/12/48 interfaces. There is no fix mapping between the working and protection paths of the SNCP/UPSR connections.

Example 1: Working and protection paths on same slotThe user can provision a SNCP/UPSR connection with the TU12/VT2-1-6-1-1-1-1-1 as the working path and the TU12/VT2-1-6-2-1-1-1-1 as the protection path.

Example 2: Working and protection paths on different slotsThe user can provision a SNCP/UPSR connection with the TU12/VT2-1-6-1-1-1-1-1 as the working path and the TU12/VT2-1-7-1-1-1-1-1 as the protection path.

When protection is provisioned for the source or destination end-points of the SNCP/UPSR connection, the user must also provision the revertive mode and the WTR Time period when applicable.

Attention: The 6130 supports nodal provisioning. When provisioning an end-to-end circuit, you must provision the cross connections at the end points and at any pass-through nodes that make up the end-to-end circuit.

For detailed procedures for SNCP/UPSR protection, refer to Provisioning and Protection Switching Procedures, 323-1855-310.

SNCP/UPSR protection switch typesSNCP/UPSR protection switch requests can occur automatically by the system or by user initiated actions.



Table 6-12 summarizes the hierarchy of protection commands.

For a complete description and procedures, see Provisioning and Protection Switching Procedures, 323-1855-310.

2-Fiber MS-SPRing/BLSR traffic protectionA 2-Fiber Multiplex Section Shared Protection Ring (MS-SPRing) / Bidirectional Line-Switched Ring (BLSR) is a ring network of nodes interconnected by a pair of optical fibers. MS-SPRing/BLSR traffic protection provides 100% restoration of restorable traffic for single failures by reserving 50% of the ring’s capacity for protection. As a result, a 2-Fiber STM-16/OC-48 ring effectively has a span capacity of STM-8/STS-24.

For a 2-Fiber MS-SPRing/BLSR operating at the STM-16/OC-48 level, time slot numbers 1 through 8 (SDH) or 1 through 24 (SONET) at the multiplex input are reserved for working channels. Time slot number ‘X’ of the first fiber is protected using time slot number ‘X+8’ (SDH) or ‘X+24’ (SONET) of the second fiber in the opposite direction, where X is an integer between 1 and 8 (SDH) or between 1 and 24 (SONET).

In a MS-SPRing/BLSR, switching nodes communicate to each other through K-bytes. All of the VC-4s/STS-1s within the line are protected together.

A maximum of 16 NEs is supported for each MS-SPRing/BLSR ring configuration. The traffic protection switch time is less than 50 ms for rings of up to 1200 km of fiber (ring circumference).

Table 6-12:SNCP/UPSR protection - command hierarchy


Lockout of protection 1 (Highest)

Forced switch 2

Auto switch (P-AIS, P-LOP, P-UNEQ) 3

Auto switch (P-SF) 4

Auto switch (P-SD) 5

Manual switch on protection path 6

Manual switch on working path 7

Wait-to-Restore 8 (lowest)



Provisioning MS-SPRing/BLSR protected configurationsThe user performs protection group provisioning from the MS-SPRing/BLSR application in the Configuration main menu of the Node Manager (WUI). The user creates the MS-SPRing/BLSR protection group for the STM-16/OC-48 interfaces located on the 1x2.5G+4x155M/2x622M aggregate cards.

East and west ports provisioningThere is no fix mapping between the two ports (east and west) of a MS-SPRing/BLSR traffic protection group. The east and west ports of a protection group must have the same rate and they are provisioned with the following rules:

• STM-16/OC-48 interfaces on the 1x2.5G+4x155M/2x622M aggregate cards:

— protection group members: slot 6 port 1 and slot 7 port 1

— one MS-SPRing/BLSR configuration is supported on the 6130 with STM-16/OC-48 interfaces

Attention: MS-SPRing/BLSR is only supported on the STM-16/OC-48 interfaces of the 1x2.5G+4x155M/2x622M aggregate cards.

Ring map provisioningThe Ring map contains an ordered list of up to 16 APS IDs, ranging in value from 0 to 15 (APS ID0;APS ID1;APS ID2;…;APS ID15). Although ordered, the list does not have to be in sequential order of 0 to 15.

Node ID, Ring ID and WTR Time provisioningEach NE in the ring must have a unique Node ID number (i.e. APS ID) from 0 to 15. The user also provisions the Ring ID identifier of the MS-SPRing/BLSR configuration. The reversion mode for the MS-SPRing/BLSR configuration is always revertive and the Ring WTR time period is user configurable from 1 to 12 minutes (default value is 5 minutes).

For detailed procedures for MS-SPRing/BLSR protection, refer to Provisioning and Protection Switching Procedures, 323-1855-310.

Cross-connect provisioning for MS-SPRing/BLSRThe user performs cross-connect provisioning from the Cross-connect application in the Configuration main menu of the Node Manager (WUI). The user provisions a 2WAY connection type at the end points and any pass through nodes if applicable. For dual feed applications on MS-SPRing/BLSR configurations, use the 1WAY connection type to create drop-and-continue connections.



For MS-SPRing/BLSR connections only, the MS-SPRing/BLSR end points must be identified. The MS-SPRing/BLSR end points are the APS IDs of the connection end points.

The 6130 supports nodal provisioning. When provisioning an end-to-end circuit, you must provision the traffic protection and cross-connects at the end points and at any pass through nodes that make up the end-to-end circuit.

The following rates are supported for add/drop cross-connects:

• VC-11/VT1.5, VC-12/VT2, VC-3/STS-1 and VC-4

The following rate is supported for pass-through cross-connects:

• STS-1, VC-4

Attention: STS-3c, VC-4-4c/STS-12c cross-connects are not supported in MS-SPRing/BLSR configurations.

VC/STS MS-SPRing/BLSR with LO VC/VT assignment6130 supports low order (LO) VC/VT assignment on MS-SPRing/BLSR configurations. Payload connectivity in the MS-SPRing/BLSR configurations is at the STS-1, VC-4 level where the STS-1, VC-4 managed connection can contain LO VC/VT payloads. Individual LO VC/VT payload overheads are not monitored.

In LO VC/VT assigned MS-SPRing/BLSR configurations, users must provision STS-1 or VC-4 connections at pass-through nodes for the LO VC/VT traffic. This gives a number of distinct advantages to the user:

• less connections for the user to manage

• less, therefore quicker, connection retrievals on pass-through nodes

• interoperability support with STS-1 or VC4 based products

LO VC/VT assigned end-to-end connections must have the following characteristics:

• for any given end-to-end LO VC/VT connection, add and drop nodes must be provisioned with LO VC/VT connections and pass-through nodes must be provisioned with STS-1 or VC4 connections for the LO VC/VT traffic

• if one LO VC/VT connection is provisioned within an STS-1 or VC4, then the entire STS-1 or VC-4 must be LO VC/VT assigned

• all LO VC/VT assigned end-to-end connections within an STS-1 or VC-4 channel must terminate (add/drop) at the same node



Attention: Extra traffic is not supported with 6130 Release 5.0.

Enhanced non-preemptible unprotected traffic (ENUT) feature is not supported with 6130 Rel 5.0.

For detailed procedures for MS-SPRing/BLSR co5.0nnection provisioning, see Bandwidth and Data Services Procedures, 323-1855-320.

MS-SPRing/BLSR protection switch typesMS-SPRing/BLSR protection switch requests can occur automatically by the system or by user initiated actions. All user-initiated MS-SPRing/BLSR switching commands are signaled on the APS channels (K1 and K2 bytes). Table 6-13 summarizes the hierarchy of protection commands.

For detailed procedures, see Provisioning and Protection Switching Procedures, 323-1855-310.

Traffic protection exerciserThe traffic protection exerciser allows you to verify the protection functionality without affecting the traffic. By running the protection exerciser, you can detect silent protection-related failures before the failures become service-affecting. The traffic protection exerciser is supported only for MS-SPRing/BLSR configurations.

The traffic protection exerciser is a routine that tests the integrity of the protection switching bytes (K-bytes) communication between an optical interface pair of a MS-SPRing/BLSR configuration. If the two ends fail to exchange the K-bytes, the test fails and alarms are raised.

Table 6-13MS-SPRing/BLSR protection - command hierarchy


Lockout of protection - span 1 (highest)

Forced switch 2

Auto switch (Signal Fail) 3

Auto switch (Signal Degrade) 4

Manual switch 5

Wait-to-Restore 6

Exerciser 7

Reverse Request 8 (lowest)



The exerciser can be initiated manually by the user from the MS-SPRing/BLSR WUI application from the Protection menu. The exerciser is the lowest priority user command and does not run if:

• a higher priority request or command is in effect

• alarms are present on the interface circuit packs

The exerciser runs only on a pair of interface circuit packs that meet all the following conditions:

• The interface circuit packs must be in a MS-SPRing/BLSR configuration. The interface circuit packs must also have a valid MS-SPRing/BLSR configuration and no active protection switch.

• The interface circuit packs must be in-service

Unprotected connectionsUnprotected configurations consists of end-to-end paths that do not have an alternate path. In the case of the a fault on the unprotected path, traffic is lost.

Attention: Unprotected is the default traffic protection configuration for the port interfaces in 6130.

Provisioning unprotected connectionsAs unprotected is the default traffic protection configuration, unless the user has already provisioned the STM-1/4/16/OC-3/12/48 interfaces for 1+1 MSP/APS or MS-SPRing/BLSR protection scheme, the user can simply provision cross-connects.

The user performs cross-connect provisioning from the Cross-connect application in the Configuration main menu of local craft access terminal for E1/DS1, E3/DS3 and STM-1/4/16/OC-3/12/48 services. For the Ethernet circuit packs (Layer 1 and Layer 2), the VCG associations are provisioned from the WAN application in the Facilities menu.

Attention: The 6130 supports nodal provisioning. When provisioning an end-to-end circuit, you must provision the cross connections at the end points and at any pass-through nodes that make up the end-to-end circuit.

For a complete procedures for provisioning unprotected connections, see Provisioning and Protection Switching Procedures, 323-1855-310.



Data communicationsThe 6130 supports data communication features to provide the capabilities for local and remote management of the 6130 network element and for interworking with other network elements to provide a cohesive network management solution. The 6130 OAM interfaces provided are as follows:

• STM-1/4/16/OC-3/12/48 interfaces using RS/Section DCC (D1-D3 bytes), RS/Section F1 byte, MS/Line DCC (D4-D12 bytes), or HO/STS Path (F2, F3 and F2-F3 bytes) for OAM&P access to remote network elements

• LAN port for interface to a data communications network (DCN).

• Craft port for interface to a local craft terminal PC.

• M1/F1 port for modem access or for user byte access

• Management channel via physical E1 port

• Management channel via VC12 payload

InterfacesThe interfaces/protocols are configured from various applications available from the local craft access terminal. For DCN provisioning procedures, see Provisioning and Protection Switching Procedures, 323-1855-310.

LAN interfaceThe LAN interface provides a mechanism to connect the 6130 network element to the office DCN for connectivity to a management system for remote management of the 6130 network and subtending network elements. The LAN interface consists of a 10/100Base-T RJ-45 port located on the front of the OAM circuit pack.

The LAN port can be enabled or disabled with the default being enabled.

Proxy ARP is supported on the LAN interface when the 6130 NE is used as a gateway NE for other 6130 NEs or 6110 NEs. The gateway 6130 NE responds to ARP requests for the subtending NEs when Proxy ARP is enabled. The subtending NEs need to be added as Proxy ARP neighbors at the gateway 6130 NE.

The LAN interface can be configured from the Network interface application available from the Configuration/DCN menu item in the local craft access terminal. For a detailed procedures, see Provisioning and Protection Switching Procedures, 323-1855-310. To know how to provision the IP address for the LAN port, refer to Installation, Commissioning and Testing Procedures, 323-1855-201.



Craft interfaceThe Craft interface provides a mechanism to connect a local craft terminal PC directly to the 6130 network element for local access to the network element. The Craft interface consists of a 10/100Base-T RJ-45 port located on the front of the OAM circuit pack.

The Craft port is always enabled and its IP address is 192.168.1.254

The Craft port is running a DHCP server to assign an IP address (192.168.1.253) to the host computer when it is connected to this port. The DHCP server is always enabled on the Craft port.

M1/F1 interfaceThe M1/F1 interface provides a mechanism to connect a PC or a modem to the 6130 network element for user byte clear channel access or remote management. The RS-232 serial port is exposed as a RJ-45 connector located on the front of the OAM circuit pack.

The M1/F1 interface can be provisioned for two applications:

• point-to-point protocol (ppp) - modem connectivity to the network element through the RS-232 serial port based on IP over PPP

• user data channel (udc) - F1 byte user data channel used as synchronous mode at 64 kbps. The F1 byte user data channel is supported for one STM-1/4/16/OC-3/12/48 interface on any of the STM-n/OC-n circuit packs.

The serial port can be configured from the Serial Port application available from the Configuration/DCN menu item in the local craft access terminal. For more details, refer to Provisioning and Protection Switching Procedures, 323-1855-310.

E1/VC12 management channelThe 6130 supports up to two management channels that can be provisioned over an E1 or VC12 channel. The management channel provides a means to connect to isolated clusters over an E1 or VC12 channel.

An E1 management channel allows management data to be transmitted and received over the first E1 port of the 28xE1/DS1, 28xE1/DS1(W/P) or 63xE1/DS1circuit pack to manage remote network element.

Attention: Only the first E1 port of the 28xE1/DS1, 28xE1/DS1(W/P) or 63xE1/DS1 circuit pack can be used for the E1 management channel.



A VC12 management channel allows for management data to be transmitted and received over one VC12 channel on the STM-1/4/16 interfaces to manage remote network element.

Attention: In this release, the management channel is supported only over E1 or VC12 channels in SDH mode.

The E1/VC12 management channel can be configured from the Management channel application available from the Configuration/DCN menu item in the local craft access terminal. For more details, refer to Provisioning and Protection Switching Procedures, 323-1855-310.

DCC interfaceThe DCC interfaces provide a mechanism for 6130 network elements and subtending network elements to communicate and exchange OAM messages using the RS/Section, MS/Line or HO/STS Path overhead bytes. The embedded communication channel (ECC) for the STM-1/4/16/OC-3/12/48 interfaces can be configured to use any of the following byte groups:

• D1-D3 bytes of the Regenerator Section/Section overhead

• F1 byte of the Regenerator Section/Section overhead

• D4-D12 bytes of the Multiplex Section/Line overhead

• F2, F3 or F2-F3 bytes of the HO/STS path overhead

The 6130 supports both IP and OSI based DCC interfaces and can operate as a single point of entry for access to remote or subtending network elements using IP or OSI based DCC interfaces. In this release, one IP or OSI based DCC interface can be provisioned for each STM-1/4/16/OC-3/12/48 interface on the 6130 network element.

The generic routing encapsulation (GRE) protocol is used for OSI based DCC interfaces. The GRE tunnels can be provisioned statically or dynamically (auto-GRE tunneling).

Table 6-14 describes the maximum number of RS/Section and MS/Line DCC interfaces supported on the STM-1/4/16/OC-3/12/48 interfaces for each 6130 NE equipped with the 2x155/622M, 1x155/622M or 1x2.5G aggregate cards.



Table 6-15 describes the maximum number of RS/Section and MS/Line DCC interfaces supported on the STM-1/4/16/OC-3/12/48 interfaces for each 6130 NE equipped with the 1x2.5G+4x155M/2x622M aggregate cards.

Table 6-14Maximum number of RS/Section and MS/Line DCC interfaces per 6130 NE equipped with the 2x155/622M, 1x155/622M or 1x2.5G aggregate cards

If the number of MS/Line DCC interface(s) is:

Then, the number of RS/Section DCC interfaces available is:

None 18

1 17

2 15

3 12

4 9

5 6

6 3

7 none

Table 6-15Maximum number of RS/Section and MS/Line DCC interfaces per 6130 NE equipped with the 1x2.5G+4x155M/2x622M aggregate cards





none 42 15 27

1 41 16 26

2 40 17 25

3 39 18 24

4 38 19 23

5 37 20 22

6 36 21 21

7 35 22 19

8 34 23 16

9 33 24 13

10 32 25 10



Each STM-1/4/16/OC-3/12/48 interface is capable of supporting one DCC interface. The default setting for the DCC interface is set to off. The DCC interfaces can be configured from the Network Interface application available from the DCN menu item in the local craft access terminal. For more details on how to provision the DCC interfaces, refer to Provisioning and Protection Switching Procedures, 323-1855-310. For more information on DCN planning, refer to Appendix A: Data communications planning on page 10-1.

DCC TransparencyThe 6130 supports DCC transparency via overhead tunnel provisioning. This feature allows two STM-1/4/16/OC-3/12/48 interfaces to be connected together so the network element appears transparent to subtending network elements (NEs connected to the 6130 via the STM-1/4/16/OC-3/12/48 interfaces).

The overhead tunnel allows DCC bytes to be forwarded transparently between the two STM-1/4/16/OC-3/12/48 interfaces. This feature offers advantages such as, allowing interoperability with other vendor’s equipment that do not support a standard-based OSI stack.

The user can select the bytes on which the overhead tunnel should be passing through. The available values are:

• E1

• E2

• F1

• DCC_R

• DCC_M

11 31 26 7

12 30 27 4

13 29 28 1

14 28

Table 6-15 (continued)Maximum number of RS/Section and MS/Line DCC interfaces per 6130 NE equipped with the 1x2.5G+4x155M/2x622M aggregate cards







The DCC transparency can be configured from the Overhead Tunnel application available from the Configuration main menu item in the local craft access terminal. For more details on how to provision the DCC interfaces, refer to Provisioning and Protection Switching Procedures, 323-1855-310.

OAM comms managementThe 6130 uses an IP-based comms infrastructure for network element management and interworking with IP-based DCC network elements. However, 6130 also supports OSI-based DCC for interworking with OSI-based network elements.

For more information about provisioning the communication parameters, see Provisioning and Protection Switching Procedures, 323-1855-310.

OAM comms routingSupport of IP-based and OSI-based DCC requires support of several routing protocols. 6130 supports the following routing protocols:

• Integrated ISIS (iISIS)

iISIS can be used as the internal DCN routing protocol and is available on all DCC interfaces. iISIS is not available on the LAN, Craft and RS232 ports.

The iISIS settings for the 6130 NE can be provisioned using the iISIS application available from the Configuration/DCN menu item in the local craft access terminal. The iISIS settings for the embedded channel interfaces can be configured using the Network interface application also available from the Configuration/DCN menu. For more details on how to provision iISIS, refer to Provisioning and Protection Switching Procedures, 323-1855-310. For more information on DCN planning, refer to Appendix A: Data communications planning on page 10-1.

• OSPF

The OSPF feature enables monitoring neighboring network elements and retrieving routing information for In Band Communication (IBC). The OSPF feature can be enabled or disabled for the embedded communication channel interfaces or for the LAN access to the public DCN.

The OSPF area can be provisioned using the OSPF application available from the Configuration/DCN menu item in the local craft access terminal. The OSPF settings for the embedded channel interface or the LAN port can be configured using the Network interface application also available from the Configuration/DCN menu. For more details on how to provision



OSPF, refer to Provisioning and Protection Switching Procedures, 323-1855-310. For more information on DCN planning, refer to Appendix A: Data communications planning on page 10-1.

Alarm and event managementActive alarms are indicated on the 6130 equipment and are visible from the local craft access terminal. Alarm history and events are stored on the 6130 network element. Login sessions using craft user interface, and Optical Network Manager provide details of network element alarms.

The severity of an alarm is indicated by the following designations: Critical, Major, minor, warning. Critical alarms have the highest priority and are reported before Major, minor or warning alarms. Major alarms are reported before minor alarms and minor alarms are reported before warnings.

6130 local alarm indicationsTrouble conditions present on the 6130 network element are indicated locally by light-emitting diodes (LEDs) on the front of the faceplate of the circuit packs, or the SFP interfaces.

For more information about the local alarm indications, refer to Trouble Clearing and Module Replacement Procedures, 323-1855-543.

Alarm management / surveillanceThe local craft access terminal provides the user with the ability to view and manage alarms and events for the 6130 as follows:

• view summary of active alarms

• view active alarms

• view suppressed alarms

• view/provision alarm filters

• view event history

• view/provision alarm severities

• alarm reporting control

— view/provision STM/OC port profiles

— view/provision path alarm profiles

— enable/disable facility alarm reporting

• view/provision environmental alarms input



Viewing summary of active alarmsThe WUI provides the user with an alarm banner which summarizes the active alarms on the network element. The alarm banner is continuously displayed in the WUI to provide the user with an accurate of the current state of the system while navigating through the different menus of the WUI. The alarm banner has auto refresh enabled by default and is time-stamped, and it can be disabled.

For more information about the alarm banner, refer to Local Craft Access User Guide, 323-1855-195.

Viewing active alarmsThe network element user interface provides the user with a list of active alarms on the 6130 shelf by selecting the Active alarms application in the Faults menu of the local craft access terminal. The current active alarms list is set to auto refresh by default, and it can be disabled.

For more information about the active alarm and alarm clearing procedures, refer to Local Craft Access User Guide, 323-1855-195 and Trouble Clearing and Module Replacement Procedures, 323-1855-543.

Viewing/provisioning alarm filtersThe Alarm Filters application in the Faults menu of the local craft access terminal provides the ability for users to create alarm filter rules whereby selected alarms on chosen entities are not displayed in the active alarm list. The application gives the user the ability to view, add or delete an alarm filter rule.

An alarm filter rule can be created for an object type against only one object instance, where a selected alarm or all alarms are filtered out. When an alarm filter is created, any active alarm which matches the filter rule are no longer displayed in the active alarm list, and the filtered alarm is displayed in the suppressed alarm list. An alarm filter can be deleted at any time.

For more information about the alarm filter and detailed procedures on managing alarm filters, refer to Local Craft Access User Guide, 323-1855-195 and Trouble Clearing and Module Replacement Procedures, 323-1855-543.

Viewing suppressed alarmsThe Suppressed alarms application in the Faults menu of the WUI allows the user to view any alarms that have been suppressed by the Alarm Filter or by the Alarm Reporting Control feature.

For more information about the suppressed alarms and alarm clearing procedures, refer to Local Craft Access User Guide, 323-1855-195 and Trouble Clearing and Module Replacement Procedures, 323-1855-543.



Viewing event historyThe user views the events on an 6130 shelf by selecting the Event history application in the Faults menu of local craft access terminal. The Events history application supports the viewing of historical (current and cleared) alarms and events for the 6130 network element.

The 6130 network element stores a minimum of 7500 events in non-volatile storage.

For more information about the event history and alarm clearing procedures, refer to Local Craft Access User Guide, 323-1855-195 and Trouble Clearing and Module Replacement Procedures, 323-1855-543.

Viewing/provisioning alarm severitiesThe Alarm severity application in the Faults menu of the local craft access terminal provides the ability for users to view or edit the severity of an alarm for the 6130 network element. The severity changes are applied to the alarm type, but is not provisionable on an entity basis.

For more information about the alarm severities and detailed procedures on managing alarm severities, refer to Local Craft Access User Guide, 323-1855-195 and Trouble Clearing and Module Replacement Procedures, 323-1855-543.

Alarm Reporting ControlThe ARC feature provides a toolset to control the declaration of alarms from the network element to the EMS/NMS applications. There are three components of this feature:

• port profiles

• path alarm profiles

• facility alarm reporting

Viewing/editing port profilesThe STM/OC Port Profile application in the Profiles menu of the local craft access terminal provides the ability for users to define the appropriate port profiles for the STM/OC interfaces. The following are the two default port profiles:

• internal-NNI - use within an EMS domain

• external-NNI - use between management domains



The port profile is a global setting and allows the user to assign the appropriate path alarm profile to each of the eight individual connection types:

• terminating and unprotected TU/VT

• terminating and protected TU/VT

• passthrough and unprotected TU/VT

• passthrough and protected TU/VT

• terminating and unprotected AU/STS

• terminating and protected AU/STS

• passthrough and unprotected AU/STS

• passthrough and protected AU/STS

The provisioned path alarm profile is automatically assigned to any cross-connect that is created using the STM/OC interface.

For detailed procedures on managing port profiles, refer to Trouble Clearing and Module Replacement Procedures, 323-1855-543.

Viewing/provisioning path alarm profilesThe Path Alarm Profiles application in the Profiles menu of the local craft access terminal provides the ability for users to view the eight default path alarm profiles, or create/edit/delete a user defined path alarm profile. The path alarm profile is then assigned and applied to the eight connection types according to the STM/OC Port Profile.

The path alarm profile specifies the consequent actions upon TIM, PLM and UNEQ conditions. The path alarm profile also specifies the path level alarms that should be masked. The eight default path alarm profiles can not be deleted and their defined actions can not be modified, while the user can create or delete the user defined path profiles and edit the defined actions.

Once a connection is created with the path alarm profile assigned according to the STM/OC Port Profile, the path alarm profile can be manually changed at the AU/STS/TU/VT levels.

For detailed procedures on managing path alarm profiles, refer to Trouble Clearing and Module Replacement Procedures, 323-1855-543.

Enable/disable facility alarm reportingUser can enable or disable all alarm reporting associated to the following facilities / alarm object instances:

• STM-n / OC-n

• AU / TU

• STS / VT



• 10/100/1000BT

• 100FX

• GE

• PDH / DSn

Once the alarm reporting is disabled for the facility / alarm object instance, any active alarm will be suppressed and listed in the suppressed alarms application.

Viewing/provisioning environmental alarmsThe 6130 network element has 7 parallel telemetry input points. The input points allow remote monitoring of other equipment in the office in which the network element is located. For example, the input points can monitor room temperature alarms or office door open alarms. Specific external alarm must be set up during provisioning and are assigned to a specific contact pin. The alarm input points are connected to the ALM.IN RJ-45 connector on the front of the OAM circuit pack.

The Environmental alarm input application in the Configuration menu of the local craft access terminal supports the provisioning of alarm for an alarm input point.

The 6130 also supports the capability of displaying the network element summary alarms onto an external device. The Critical, Major, and Minor alarms can be reported to an external control device by connecting to the ALM.OUT RJ-45 connector on the front of the OAM circuit pack.

For more information on environmental alarms, refer to Local Craft Access User Guide, 323-1855-195 and detailed procedures, refer to Trouble Clearing and Module Replacement Procedures, 323-1855-543.

PDH / DSn alarm monitoringAlarm monitoring support is limited for framed E1/DS1 ports of the 28xE1/DS1 and 28xE1/DS1(W/P) circuit packs. The level of alarm monitoring depends on the E1/DS1 PDH path monitoring mode assigned to the unframed/framed E1/DS1 PDH ports.

Below are the three provisionable modes of operations for E1/DS1 PDH path monitoring for the 28xE1/DS1 and 28xE1/DS1(W/P) circuit packs:

• no monitoring mode (NMM)

Alarm and performance monitoring is disabled for all E1/DS1 ports of this circuit pack and is the default mode.



• alarm monitoring mode (AMM)

Path alarms are monitored in a round-robin basis. Under normal operating condition, each E1/DS1 port of this circuit pack is polled at least 2-3 times in a 2.5 seconds interval.

• alarm and performance monitoring (APMM)

Only the nominated framed E1/DS1 port is monitored for path alarms and performance.

The path alarm monitoring modes of operation are not applicable to framed E3/DS3 ports or framed E1 ports of the 63xE1/DS1circuit pack. Each unframed/framed E3/DS3 port has full alarm and performance monitoring support. Each unframed/framed E1 port of the 63xE1/DS1circuit pack has full line alarm and performance monitoring support. All framed E1 ports of the 63xE1/DS1circuit pack are monitored for path alarms and performance monitoring.

Table 6-16 on page 6-50 summarizes the PDH/DSn alarms for the different circuit packs.

For detailed procedures, refer to Provisioning and Protection Switching Procedures, 323-1855-310.

Table 6-16PDH / DSn alarm monitoring

Card type Line alarm Path alarm (near-end) Path alarm (far-end)

28xE1/DS1 (see Note1) LOS AIS, LOF, LOM RAI

63XE1/DS1 LOS AIS, LOF, LOM RAI

28xE1/DS1(W/P) (see Note1) LOS AIS, LOF, LOM RAI

3xE3/DS3 (see Note2) LOS AIS, LOF, LOM RAI

3xE3/DS3(W/P) (see Note2) LOS AIS, LOF, LOM RAI

Transmux (6 x E3/DS3) (see Note2)

LOS AIS, LOGF, LOM RAI

Note 1: The underlined path alarms have limited monitoring support and the non-underlined path alarms have full monitoring support

Note 2: All line and path alarms have full monitoring support



Performance monitoringPerformance monitoring (PM) refers to the continuous collection, analysis, and reporting of the performance data of a monitored entity. This monitoring allows early detection of service degradations and facilitates preventive maintenance without interruption of service. PMs can also be used to facilitate trouble/fault isolation.

The 6130 monitors the following entities for PM collection:

• STM/OCn performance monitoring parameters

• 10/100/1000BT Ethernet performance monitoring parameters

• 100FX Ethernet performance monitoring parameters

• Gigabit Ethernet performance monitoring parameters

• WAN performance monitoring parameters

• E1/E3/DS1/DS3 performance monitoring parameters

The 6130 craft user interface Performance application allows the user to retrieve:

• current PM values (15 minute and 1-Day values in progress)

• recent history (32 previous 15 minute and previous day values stored on the network element)

PM functionsPM functions include:

• count binning

• thresholding

Count binningEach monitored entity generates a set of PM parameter counts based on raw data from hardware and other systems. These counts can be retrieved or reset through user commands.

ThresholdingPerformance thresholds are values associated with specific performance error statistics. Aside from the physical PMs, each SDH performance parameter has two thresholds which can be applied to either the current 15 minute or day counts. When a PM parameter value exceeds its threshold settings, the system generates a threshold crossing alert (TCA). TCAs are cleared when the PM counts have been reset or the particular timed accumulation bin has terminated.

PM thresholds management for the STM-1/4/16/OC-3/12/48 interfaces is available from the STM/OCn application in the Facility menu of the local craft access terminal.



STM/ OCn PM parametersSTM/OCn PM parameters are accumulated for the STM-1/4/16/OC-3/12/48 interfaces on the circuit packs. Table 6-17 provides a summary of the supported STM/OCn PM parameters.

PDH / DSn performance monitoringPath performance monitoring for E1/DS1 port is limited for the 28xE1/DS1 and 28xE1/DS1(W/P) circuit pack and dependant on the PDH/DSn path monitoring mode assigned to the unframed/framed E1/DS1 PDH ports as described in the PDH / DSn alarm monitoring on page 6-49.

Path performance parameters are monitored for the 28xE1/DS1 and 28xE1/DS1(W/P) circuit packs when the path monitoring mode for the selected framed E1/DS1 port is set to Alarm and Performance Monitoring. Path performance parameters are also counted for unframed E1/DS1 ports only based on AIS condition.

Path performance monitoring is fully supported on all E1 ports of the 63xE1/DS1circuit pack.

Path performance monitoring is fully supported on all E3/DS3 ports.

Line performance monitoring is fully supported on all PDH/DSn ports.

Table 6-17SDH / SONET PM parameters summary

Facility PM parameter

Regenerator Section (RS) / Section

SDH: ES, SES, UAS, SEP, EB, BBE, ESR, SESR, BBER, SEPI SONET: CV, ES, SES, SEFS

Multiplex section (MS) / Line

SDH: ES, SES, UAS, SEP, EB, BBE, ESR, SESR, BBER, SEPI, ES-FE, SES-FE, BBE-FE, UAS-FE, SEP-FESONET: CV, ES, SES, UAS, FC, CV-FE, ES-FE, SES-FE, UAS-FE

Path (HO AU / STS) SDH: ES, SES, UAS, SEP, EB, BBE, PPJE, NPJE, ESR, SESR, BBER, SEPI, ES-FE, SES-FE, BBE-FE, UAS-FE, SEP-FESONET: CV, ES, SES, UAS, FC, PPJE, NPJE, CV-FE, ES-FE, SES-FE, UAS-FE

Tributary Unit (LO TU / VT)

SDH: ES, SES, UAS, SEP, EB, BBE, ESR, SESR, BBER, SEPI, ES-FE, SES-FE, BBE-FE, UAS-FE, SEP-FESONET: CV, ES, SES, UAS, FC, CV-FE, ES-FE, SES-FE, UAS-FE

Transceiver (physical)

Received Power, Transmit Power, Laser Bias, Laser Voltage, Laser Temperature



PDH / DSn PM parametersPM parameters are accumulated for the E1/E3/DS1/DS3 facilities on the:






• Transmux circuit pack

Table 6-18 provides a summary of the supported PDH PM parameters.

10/100/1000BT, 100FX and GE PM parametersEthernet PM parameters are accumulated for the 10/100/1000BT, 100FX and GE interfaces. Table 6-19 provides a summary of the supported 10/100/1000BT, 100FX and GE PM parameters.

Table 6-18PDH / DSn PM parameters summary

Facility PM parameter Location

E1 Line: CV-L, ES-L, SES-LPath: EB-P, BBE-P, ES-P, SES-P, UAS-P (see Note 1)

Near end

DS1 Line: CV-L, ES-L, SES-LPath: CV-P, ES-P, SES-P, UAS-P, SAS-P, AISS-P (see Note 1)

Near end

E3 Line: CV-L, ES-L, SES-LPath: ES-P, SES-P, UAS-P

Near end

DS3 Line: CV-L, ES-L, SES-LPath: CV-P, ES-P, SES-P, UAS-P, SAS-P, AISS-P

Near end

Note 1: Limited path PM support for E1/DS1 facilities of the 28xE1/DS1 and 28xE1/DS(W/P) circuit packs.



Table 6-1910/100BT, 100FX and GE PM parameters summary


100/1000BT ports of the following circuit pack:

— 8xGE EoPDH L2

• Packets RX/TX 64 Bytes

• Packets RX/TX 65-127 Bytes






• Unacceptable Frame Type

• Frames Received

• Octets Received

• Frames Transmitted

• Octets Transmitted

• FCS Errors RX

• Frames Too Short RX

• Pause Frames Received

• Broadcast Frames Received

• Broadcast Frames Transmitted

• Multicast Frames Received

• Multicast Frames Transmitted

• Frame Fragment TX

• Frame Fragment RX

• Frame Jabber TX

• Frame Jabber RX

• Discarded Rx packets

• Discarded Tx Packets

• Service Lookup Failure

• Ingress Other Discards

• MTU Discards

• Packets RX/TX > 1522 (Jumbo Frames)

• FrameErrorLength RX

• FrameErrorLength TX



10/100BT and /or 100FX ports of the following circuit packs:

Note 2: 8xETH

— 4x10/100BT+4x100FX L1

— 4x10/100BT+4x100FX L1 622M

• Alignment Errors



• Collisions

• ES

• Ethernet Interval Valid

• FCS Error Bytes

• FCS Error Frames

• Frame Too Long Errors

• Frame Too Short Errors

• Frames Aborted Due To Excessive Collisions

• Frames Dropped Rx

• Frames Dropped Tx

• Frames Received


• Frames With Deferred Transmissions

• Idle Seconds

• Late Collisions



• Multiple Collision Frames

• Octets Received



• Pause Frames Transmitted

• SES

• Single Collision Frames

• UAS

Table 6-19 (continued)10/100BT, 100FX and GE PM parameters summary




10/100BT and/or GE ports of the following circuit packs:

— 2xGE

— 2xGE+8x10/100BT L1

• ES

• Ethernet Interval Valid

• FCS Error Bytes

• FCS Error Frames

• Frame Too Long Errors

• Frame Too Short Errors

• Frames Dropped Rx

• Frames Dropped Tx

• Frames Received


• Idle Seconds

• Octets Received



• Pause Frames Transmitted

• SES

• UAS

10/100BT, 100FX and GE ports of the following circuit pack:

— L2PA622M

— L2PA1G2

• Alignment Errors• Broadcast Frames Received• Broadcast Frames Transmitted• Collisions• Ethernet Interval Valid• ES• FCS Error Bytes• FCS Error Frames• Frames Received• Frames Transmitted• Frame Too Long Errors• Frame Too Short Errors• Frames Aborted Due To Excessive Collisions• Idle Seconds• Late Collisions• Multicast Frames Received• Multicast Frames Transmitted• Multiple Collision Frames





< continued > • Octets Received• Octets Transmitted• Pause Frames Received• Pause Frames Transmitted• Rx Overflow• SES• Single Collision Frames• UAS• Unacceptable Frame Type• Unicast Frames RX• Unicast Frames TX• Packets RX/TX 64 Bytes• Packets RX/TX 65-127 Bytes• Packets RX/TX 128-255 Bytes• Packets RX/TX 256-511 Bytes• Packets RX/TX 512-1023 Bytes• Packets RX/TX 1024-1518 Bytes• Packets RX/TX 1519-1522 Bytes• Packets RX/TX 1523-2047 Bytes• Packets RX/TX 2048-4095 Bytes• Packets RX/TX 4096-9216 Bytes• STP BPDU's RX• STP BPDU's TX• RSTP BPDU's RX• RSTP BPDU's TX• MSTP BPDU's RX• MSTP BPDU's TX• CoS Queue 1 Enqueue Discards• CoS Queue 2 Enqueue Discards• CoS Queue 3 Enqueue Discards• CoS Queue 4 Enqueue Discards• CoS Queue 5 Enqueue Discards• CoS Queue 6 Enqueue Discards• CoS Queue 7 Enqueue Discards• CoS Queue 8 Enqueue Discards





WAN PM parametersWAN PM parameters are accumulated for the WAN interfaces on the 8xETH circuit pack, 4x10/100BT+4x100FX L1 circuit pack, 2xGE circuit pack, 2xGE+8x10/100BT L1 circuit pack, L2PA622M and L2PA1G2 circuit pack. Table 6-20 provides a summary of the supported VCG PM parameters.

Table 6-20WAN PM parameters summary


100/1000BT ports of the following circuit pack:

8xGE EoPDH L2

• Idle Seconds

• ES

• SES

• UAS

• Valid Frames Transmitted

• Valid Frames Received

• Valid Bytes Transmitted

• Valid Bytes Received

• Core Header Single Error Corrections

• Type Header Single Error Corrections

• Core Header CRC Errors

• Type Header CRC Errors

• Payload FCS Errors

• VCG Interval Valid

WAN ports of the following circuit packs:

- 4x10/100BT+4x100FX L1

- 4x10/100BT+4x100FX L1 622M

- 8xETH

- 2xGE+8x10/100BT L1 1G2

- 2xGE



• ES

• Idle Seconds


• SES



• UAS








WAN ports of the following circuit packs:

- L2PA1G2

- L2PA622M





• ES

• Idle Seconds




• SES



• UAS

• Unacceptable Frame Type

Table 6-20 (continued)WAN PM parameters summary




< continued> • Unicast Frames RX

• Unicast Frames TX






• Packets RX/TX 64 Bytes










• STP BPDU's RX

• STP BPDU's TX

• RSTP BPDU's RX

• RSTP BPDU's TX

• MSTP BPDU's RX

• MSTP BPDU's TX

• CoS Queue 1 Enqueue Discards








Table 6-20 (continued)WAN PM parameters summary




PM time intervalsFor PM parameters, the following PM counts are stored and can be retrieved:

• current 15-minute interval

• last 32 15-minute intervals

• current day

• previous day

PM enable/disable The 15-minutes and 1-Day Threshold Cross Alerts for the STM-1/4/16/OC-3/12/48/PDH/DSn facilities are disabled by default. The system does not generate TCAs if the port/facility is in the admin down state.

PM inhibitionThe system inhibits the collection of PMs when the associated facility is in the the admin down state and for some parameters during various trouble conditions.

For more details on performance layer parameters, refer to Trouble Clearing and Module Replacement Procedures, 323-1855-543.

Security and administration The 6130 provides the following security and administration capabilities managed from local craft access terminal:

• Network element security

— local user authentication

— RADIUS centralized authentication

— security levels

— login sessions

— local password management

— lockout users

— database changes log / audit trail

— Secure Shell configuration

• Network element administration

— network element naming

— date and time setting

For details of the procedures associated with security and administration, refer to Provisioning and Protection Switching Procedures, 323-1855-310.



Local account user authenticationLocal account user authentication uses a user ID and password and is the default method on 6130 network elements. A user ID and password is managed individually at each network element. Up to 100 user IDs can be created locally on the 6130 network element.

Attention: Local account user authentication is the default authentication mode for network elements.

This method of user authentication is not available for network elements when RADIUS centralized authentication is enabled.

RADIUS Centralized authentication6130 supports a Remote Access Dial-In User authentication Service (RADIUS) as a centralized authentication solution. The RADIUS protocol is an IETF Draft Standard (RFC 2865) widely used to support remote access protocols (for example, PPP, telnet, and rlogin). The RADIUS protocol is a UDP-based client-server protocol. 6130 provides support for three messages from this protocol:

• Access-Request - message sent from the network element to the authentication server providing user information (user ID, password)

• Access-Reject - message sent from the authentication server to the network element refusing access to the user

• Access-Accept - message sent from the authentication server to the network processor allowing access to the user

The 6130 operates as a RADIUS client, responsible for passing user information to RADIUS servers, and then acting on the response. This remote authentication feature is user provisionable, allowing system administrators to enable or disable RADIUS. When RADIUS is enabled, the RADIUS server processes all user authentications (local account user authentication is not available). When RADIUS servers are not available or down, users can log in with local account user authentication.

Attention: The 6130 uses the following parameters which must be configured on the RADIUS server:

— Vendor ID (Ciena): 562

— Vendor type (6130) 226

— Attribute values of 1 to 5 correspond to the UPC levels of 6130 users

Network elements with RADIUS centralized authentication interoperate seamlessly with network elements that do not support RADIUS centralized authentication or have not enabled it.



The login/retry strategy is as follows:

• The RADIUS client on the network element sends up to three requests to the primary server, followed by up to three requests to the secondary server.

• The provisioned timeout value specifies the maximum amount of time allowed to send and wait for responses for each server.

Users can provision on the 6130:

• a primary RADIUS server’s IP address and port number

• a secondary RADIUS server’s IP address and port number

• the primary and secondary server shared secret

• timeout period for each RADIUS server

• state of the RADIUS feature (enabled/disabled)

Database save and restore operations include the centralized authentication provisioning data on the 6130. The centralized authentication provisioning data on the 6130 survives circuit pack restarts and replacements.

The 6130 raises the following alarms if it receives no response within the timeout period:

• a Primary or Secondary RADIUS Server Unavailable alarm if the 6130 receives no response from either the primary or secondary RADIUS server

• an All RADIUS Servers Are Unavailable alarm (major, non-traffic affecting) if the network element receives no response from both the primary or secondary RADIUS server

The alarm clears when the connection with the server(s) recovers or when the user deprovisions the RADIUS server or disables the RADIUS feature.



Security levels6130 network elements support multiple security access levels. This feature reduces accidental or intrusive interruption of service. There are 4 user access classes that allow a range of task execution capabilities.

The 6130 has a default ADMIN level account named ADMIN with ADMIN password. Ciena recommends that the default passwords be changed. See “Local password management” on page 6-65 for more information.

There is no restriction on the number of user account per user access class, as long as the total number of local user accounts does not exceed 100.

Table 6-21User access classes for 6130

User Access Classes Privileges

USER (Level 1) The USER has read-only access to all the management information including configuration, faults and performance

OPERATOR (Level 2) The OPERATOR can perform the following operations in addition to the USER operations:

• configure interfaces and cross-connects

• perform protection switches

• reset the performance statistics

• perform loopbacks

OPERATOR2 (Level 3) The OPERATOR2 can perform the following operations in addition to the OPERATOR operations:

• configure node name, contact and location

• configure Router ID and Ethernet IP / mask

• configure DCN parameters

• perform maintenance operations such as software upgrade, configuration backup and restore, etc.

ADMIN (Level 4) The ADMIN can perform the following operations in addition to the OPERATOR2 operations:

• create and delete Userid’s for the local authentication mechanism on the network element

• change the password of other Userid’s for the local authentication mechanism

• configure the RADIUS parameters



Login sessionsTo manage an 6130 network element and issue commands, the user must be logged in on that node which creates a login session. The maximum number of login sessions to a network element is ten.

Multiple login sessionsSeveral user accounts can be active at the same time as long as the maximum number of ten login sessions is not exceeded. When several sessions are active, commands can be sent to the network element simultaneously from each active session.

Local password managementThe user performs local password management from the Security menu of the local craft access terminal.

Password restrictionsFor the 6130 network element, a valid password must be used in order to activate a login session. The password is a confidential code to qualify the authorized system user’s access to the account specified by the user name. The password must be exactly 8 characters in length. The 6130 uses a security based on the Linux operating systems password encryption scheme.

Table 6-22User ID and password details

User ID • is unique

• can be alphabetic/numeric/alphanumeric

• supports special characters except space

• supports up to 32 characters

• is case sensitive

Password • is unique

• must be exactly eight characters long

• can be alphabetic/numeric/alphanumeric

• supports special characters except space

• is case sensitive

• and the user ID cannot be identical



Lockout usersThe users with Admin privilege level can disable a user account by setting the ‘User lockout’ parameter. When the user is locked out during an active session, the authentication information stored in the cache is used for the session till the user logs out. The next time the user tries to log into the network element, access is denied.

User-Lockout can be done to prevent password guessing or unauthorized access to network element.

The following parameters are configurable from the Security / Lockout users menu of the Web User Interface:

• Max Invalid Login attempts: The maximum invalid login attempts, after which the user would get locked out.

• Lockout Time: Time duration during which the locked out users cannot connect to the network element.

For more information about the lockout users procedures, refer to Local Craft Access User Guide, 323-1855-195 and Provisioning and Protection Switching Procedures, 323-1855-310.



Database changes log / audit trailThe database changes log, by default, records all changes made in the network element configuration by different users. The Database Changes application is available from the Maintenance menu. The database changes log display includes the following information:

• date and time of the modification

• type of change (e.g. add, delete, change)

• name of object modified

• identification of user who performed the change

The Database changes application displays the following changes:

• changes made in user security profiles and attributes

• changes made in the network element’s security configuration

• changes made in attributes associated with the network element configuration

• changes made in attributes associated with a connection or port

The 6130 network element archives these database change logs in a non-volatile circular buffer accessible through the Maintenance menu in WUI. The circular buffer has a capacity of 800 to 1000 logs per node (estimated 1 week’s activity).

For more information about the database changes procedures, refer to Local Craft Access User Guide, 323-1855-195 and Provisioning and Protection Switching Procedures, 323-1855-310.

The Event history application in the Faults menu displays the following historical events:

• all user login and logouts

• invalid user authentication attempts (and alerts caused by invalid authentication attempts)

• all alarms and events (current and cleared)

The 6130 network element stores a minimum of 7500 historical events in non-volatile storage.

For more information about the event history and alarm clearing procedures, refer to Local Craft Access User Guide, 323-1855-195 and Trouble Clearing and Module Replacement Procedures, 323-1855-543.



Network element nameThe user can edit the network element name assigned during the commissioning phase from the NE Information application in the System main menu on the local craft access terminal.

The network element name can be alphabetic/numerical/alphanumeric consisting of 1-18 characters. Special characters can also be used, except space. Quotes are added automatically in the TL1 interface for the network element name (TID).

Date and time settingThe user can edit the network element date and time settings provisioned during the commissioning phase from the System Time application on the local craft access terminal. This application provides the following time of day synchronization features:

• Date and time setting

• Time zone setting

• Time server setting

Date and time settingThe network element date and time can be provisioned using the Set Time application in the System Time menu.

Time zone settingThe time zone of the 6130 network element can be provisioned to correspond to the local settings using the Set time zone application in the System Time menu. A second timezone can be provisioned for display on the WUI as well.

Time server settingThe 6130 network element can be provisioned to synchronize its time off of NTP servers:

• up to 5 NTP servers can be provisioned (no servers set as default)

• synchronization frequency of the network element can be provisioned in units of seconds (default is 1024 seconds)

• the synchronization to NTP server feature can be enabled or disabled by user (default is disabled).

When NTP server synchronization is enabled, the network element time is automatically adjusted after a restart of the network element or shelf power failures. If no NTP server is available, the network element time is based on an internal clock.



Attention: When managing the 6130 network element using OMEA, the first two NTP servers will automatically be provisioned by the OMEA server. If additional time servers are desired, these should be provisioned against other than the first two sources.

The user can provision TOD synchronization from the Set time server application in the System Time menu of the local craft access terminal.

For a complete description of the security and network element administration features and procedures, refer to Provisioning and Protection Switching Procedures, 323-1855-310.

Auto discoveryAuto discovery is used by the network management to build the network topology for end-to-end connection management. The network element transmits auto discovery tags from the interface circuit packs using the internal DCN. Messages received from other network elements containing auto discovery tags are stored and reported to the network management application. This process allows the network management application to build the topology.

When using OSPF on the DCC circuits, topology auto discovery does not function across the DCC circuits using OSPF. Auto discovery does function across DCC circuits using iISIS.

For detailed procedures for provisioning the topology adjacency parameters, refer to Provisioning and Protection Switching Procedures, 323-1855-310.

Backing up and restoring the network element database The 6130 is responsible for the resilience of its provisioning data and ensures that a copy is preserved on flash. A primary and backup copy of the configuration and provisioning data is stored on the flash disk on the aggregate circuit pack. This ensures that in the event of a failure, the system can still recover on its own.

If the 6130 network element is equipped with two aggregate circuit packs (redundant configuration), then each piece of provisioning data exists on the two aggregate circuit packs. The active aggregate circuit pack contains a master copy of the configuration data and the inactive aggregate circuit pack contains a copy of the configuration data.

The user manages database backups from the Backup configuration and Restore configuration applications in the Maintenance/Configuration Management menu of the local craft access terminal. The applications allow



the user to manage backup copies of the network element database for each network element within a network and restore the network element database to an operational state following a system initialization.

Backup and restore operations can be performed remotely or locally from a machine (server or PC). The remote operation uses FTP to move configuration data between network elements and external backup repositories via a DCN. A FTP server is required in order to perform remote backup and restore operations onto the 6130 network element. The local operation uses HTTP to move configuration between the network element and an external backup repository (laptop or desktop) locally connected to the Craft port.

Refer to Installation, Commissioning and Testing Procedures, 323-1855-201, for more information.

Installing and upgrading network elementThe 6130 Release 5.0 network element software, firmware and documentation (on-line help) is factory installed on the aggregate circuit pack(s) and is also available on a CD in the event the network element software needs to be re-installed on the aggregate circuit pack(s). Refer to Software load on page 8-42 for the 6130 Release 5.0 software load on CD product code (PEC).

Attention: Re-installing the Release 5.0 software may require the user to contact Ciena. Refer to Technical assistance on page 9-1 for information on how to contact Ciena for technical assistance.

Upgrade from Rel 3.0 to Rel 5.0 requires a FTP server to act as the source of the new software, firmware and documentation files. Refer to Change Application Procedure NT6Q93ME for details in performing the upgrade.

The upgrade is performed in a 5-step application from the Unified Upgrade application in the Maintenance/Upgrade operations menu in the WUI:

• Deliver release

• Check upgrade

• Load upgrade

• Invoke upgrade

• Commit upgrade



Deliver releaseThe deliver release feature allows the user to transfer a software load to the network element. The software load can be delivered to the network element via the DCN from a remote machine running a FTP server.

The deliver release process consists of the following steps:

• Verifies that there is sufficient memory space on 6130 shelf to store the new software release.

• Transfers the software from the remote server to the 6130 shelf file system.

Check upgradeThe check upgrade is used to verify the downloaded software. The check upgrade process consists of the following steps:

• Verifies the validity of the downloaded software through checksum.

• Verifies that downloaded software version is not the same as the current running software version.

• Verifies that the downloaded software is a software for the 6130 network element.

Load upgradeDuring the load upgrade process, the network element proceeds to move the software load into a persistent storage area.

Invoke upgradeThe invoke upgrade process initiates the execution of the downloaded software load. In the event of un-successful execution of the invoke command, the NE continues to execute using the existing software load. Once the invoke command is successful, a restart of the NE will execute the new software load. After a successful invoke operation, the NE can be reverted back to the previous software load using the Cancel operation.

Commit upgradeThe commit upgrade process makes the downloaded software load the currently active software release. Subsequent restarts of the network element following a commit upgrade will not revert the system back to the previous software release. Once the new software load is committed on the NE, the NE can not be reverted back to the previous software load.

Network element software upgrade is performed following a detailed Change Application Procedure (CAP). For more details, Change application procedures on page 8-46 for the PEC code of the Software Upgrade CAP.




7-1

Technical specifications 7-

This chapter provides technical specifications, as listed in Table 7-1, for the 6130 network element.


Topic Page

Physical specifications 7-2

Power specifications 7-5

Connector pinouts 7-8

E1/DS1 cable pinouts and assemblies 7-12

Optical specifications 7-37

Electrical specifications 7-54

Environmental specifications 7-57

Electromagnetic specifications 7-58

Safety specifications 7-59

Power and grounding specifications 7-60


7-2 Technical specifications

Physical specifications Table 7-2 lists the following physical specifications for 6130 network elements.

Table 7-2Physical specifications for 6130 platform

Equipment Physical specification Notes

Circuit packs

2x155/622M aggregate 2 ports/circuit pack (2 ports/shelf)

Refer to 6130 network element configuration rules on page 8-2.

When 2 or more of the L2PA622M and/or L2PA1G2 and/or 2x622M/8x155M (NT6Q18AAE5) circuit packs are used in the same 6130 shelf, the total power requirement of the shelf may exceed the 6130 PSU capacity.

Please refer to Shelf equipping rules on page 8-5, step 19 to determine shelf power requirements.

1x155/622M aggregate 1 port/circuit pack (2 ports/shelf)

1x2.5G aggregate 1 port/circuit pack (2 ports/shelf)

1x2.5G+4x155M/2x622M aggregate

5 ports/circuit pack

(10 ports/shelf)

8xGE EoPDH L2 8 port/circuit pack

(maximum of 16 ports/shelf)

8xETH 8 ports/circuit pack (maximum of 32 ports/shelf)

Transmux 6 ports/circuit pack

(maximum of 24 ports/shelf)

4x10/100BT+4x100FX L1 8 ports/circuit pack (maximum of 32 ports/shelf)

4x10/100BT+4x100FX L1 622M

8 ports/circuit pack (maximum of 32 ports/shelf)

2xGE 2 ports/circuit pack (maximum of 8 ports/shelf)

2xGE+8x10/100BT L1 10 ports/circuit pack (maximum of 40 ports/shelf)

L2PA622M (name on circuit pack faceplate label is 2xGE/FX+8x10/100BT L2 622M)


L2PA1G2 (name on circuit pack faceplate label is 2xGE/FX+8x10/100BT L2 1G2)


3xE3/DS3 3 ports/circuit pack (maximum of 12 ports/shelf)


Technical specifications 7-3

3xE3/DS3(W/P) 3 ports/circuit pack with the 3xE3/DS3 1+1 I/O module (maximum of 6 ports/shelf in unprotected mode)

Refer to 6130 network element configuration rules on page 8-2.

When 2 or more of the L2PA622M and/or L2PA1G2 and/or 2x622M/8x155M (NT6Q18AAE5) circuit packs are used in the same 6130 shelf, the total power requirement of the shelf may exceed the 6130 PSU capacity.

Please refer to Shelf equipping rules on page 8-5, step 19 to determine shelf power requirements.

28xE1/DS1 28 ports/circuit pack (maximum of 112 ports/shelf)

63xE1/DS1 63 ports/circuit pack(maximum of 252 ports/shelf)

28xE1/DS1(W/P) 28 ports/circuit pack with the 28xE1/DS1 1+1 I/O module ( maximum of 56 ports per shelf)

28 ports/circuit pack with the 84xE1/DS1 1:N I/O module(maximum of 84 ports/shelf)

2x155M 2 ports/circuit pack (maximum of 8 ports/shelf)

2x622M/8x155M 8 ports/circuit pack (maximum of 16 ports/shelf)

2x622M/8x155M Rev2 8 ports/circuit pack (maximum of 32 ports/shelf)

6130 chassis

Height 4U (176.0 mm / 6.9 in.) without PDH protection I/O modules.

Refer to:

• Figure 7-1 on page 7-4 for an overview of the 6130 chassis

• 6130 network element configuration rules on page 8-2 for more information about physical specifications

5U (199.0 mm / 7.9 in.) with PDH protection I/O modules.

Width 445.0 mm / 17.5 in.

Depth 231.0 mm / 9.1 in. (shelf only) 295.0 mm / 11.6 in. (including cable routing brackets)

Weight Minimum Configuration:

( 6.5 kg / 14.3 lb. )

Maximum Configuration:

(13.7 kg / 30.14 lb. )

Table 7-2 (continued)Physical specifications for 6130 platform

Equipment Physical specification Notes



Figure 7-16130 chassis - physical specifications

PSU (2) OAM I/O slots Aggregate slots (2) Fan

ESD connectorTributary slots (4)



Power specificationsThe 6130 equipped with the DC PSU (standard temp) operates from -40 V dc to -57.5 V dc measured at the input terminals of the network element. The DC PSU (Ext. Temp.) operates from -40 V dc to -72 V dc measured at the input terminals of the network element. The following tables list the estimated power consumption for the different modules:

• Table 7-3 lists the estimated power requirement for the common equipment at -54 V dc

• Table 7-4 lists the estimated power requirement for each interface circuit pack -54 V dc

• Table 7-5 lists the estimated power requirement for each small form-factor pluggable (SFP) module at -54 V dc

• Table 7-6 lists the recommended feeders for the chassis

Table 7-3Power consumption for common equipment at -54 V dc

Common equipment Typical (W)

2x155/622M aggregate circuit pack 18


1x2.5G aggregate circuit pack 28

1x2.5G+4x155M/2x622M aggregate circuit pack 34

1x2.5G+4x155M/2x622M (Ext. Temp.) aggregate circuit pack

30

Single feed DC Power Supply Unit 20

OAM circuit pack 6

OAM circuit pack (Ext. Temp.) 7

Fan module (standard temp.) 12

Chassis 0

Note: Power consumption for the circuit packs with SFP interfaces, includes the SFP power consumption.



Table 7-4Power consumption for each tributary circuit pack and I/O module at -54 V dc

Tributary Circuit pack Typical (W)

8xETH 7

8xGE EoPDH 55

4x10/100BT+4X100FX L1 10.5

4x10/100BT+4X100FX L1 622M 12.5

2xGE 8

2xGE (Ext Temp) 15

2xGE+8x10/100BT L1 15

L2PA622M 28

L2PA1G2 25

28xE1/DS1 7

28xE1/DS1 (Ext. Temp.) 10

63XE1/DS1 9

28xE1/DS1(W/P) 6

3xE3/DS3 7

3xE3/DS3(W/P) 5

Transmux 15

2x155M 8

2x622M/8x155M 25

2x622M/8x155M Rev.2 (Low Power) 16

I/O 3xE3/DS3 1+1 2

I/O 28xE1/DS1 1+1 2

I/O 84xE1/DS1 1:N 3

Note: Power consumption for the circuit packs with SFP interfaces, includes the SFP power consumption.



Refer to Table 8-25 on page 8-41 for a list of power cables assemblies available and the Installation, Commissioning and Testing Procedures, 323-1855-201 for details on installing and connecting power to an 6130 shelf.

Table 7-5Power consumption for each SFP at -54 V dc

SFP modules Typical (W)

Optical SFP 0.7

Electrical SFP 0.7

Note: Power consumption of the SFP modules is included in the power consumption of the circuit packs listed in Table 7-4 on page 7-6

Table 7-6Recommended feeders

Configuration Feeders per shelf

6130 chassis with DC PSUs (150W)

A feed (6 A) and redundant B feed (6 A)

6130 DC PSU Ext Temp 225W

A feed (7.5 A) and redundant B feed (7.5 A)



Connector pinoutsTable 7-7 lists the connectors and the respective tables providing the details of their pin assignments and front views.

Table 7-7Connector pin assignment details

Connector Details

DC power connector Table 7-8

OAM circuit pack connector pinouts

Alarm input connector - pin assignment (NT6Q71AB alarm cable included in the NT6Q59AB kit)

Table 7-9

Alarm output connector - pin assignment (NT6Q71AB alarm cable included in the NT6Q59AB kit)

Table 7-10

M1/F1 connector - pin assignment (NT6Q71AG/NT6Q71AF)

Table 7-11

ESI connector - pin assignment (NT6Q71AC/NT6Q71AE)

Table 7-12

LAN, Craft and 10/100BT port connector - pin assignment (NTTC09C/Dx)

Table 7-13

28xE1/DS1 connector pinouts

E1 connector - pin assignment (NT6Q73BA/CA/DA/EA, NT6Q72BA/CA/DA/EA)

Figure 7-5

DS1 connector - pin assignment (NT6Q73QA/TA, NT6Q72QA/TA)

Figure 7-6

E1 connector (port 17-28) - pin assignment (NT6Q73BA/CA/DA/EA, NT6Q72BA/CA/DA/EA)

Figure 7-7

DS1 connector (port 17-28) - pin assignment (NT6Q73QA/TA, NT6Q72QA/TA)

Figure 7-8

E1 connector (120 Ohms) of the 63xE1/DS1Circuit Pack- pin assignment (NTTC41Bx)

Table 7-14

E1 connector (75 Ohms) of the 63xE1/DS1Circuit Pack - pin assignment (NTTC41Ax)

Table 7-15



DC power connectorThe following table describes the Pin for the DC power connector.

OAM circuit pack connector pinoutsFigure 7-1 on page 7-4 shows the interfaces available on the OAM circuit pack. Table 7-9 to Table 7-13 provide the details on the RJ-45 OAM ports.

Table 7-8DC power connector - pin assignment (in NT6Q59CA, NT6Q59DA, NT6Q59PA and NT6Q59QA)

Pin Connector

1 RET

2 GND

3 -48V

Table 7-9Alarm input connector - pin assignment (NT6Q71AB alarm cable included in the NT6Q59AB kit)

Pin Description

1 ALARMIN_1

2 ALARMIN_2

3 ALARMIN_3

4 ALARMIN_4

5 ALARMIN_5

6 ALARMIN_6

7 ALARMIN_7

8 COMMON

Note: The alarm inputs are operating as follows:open circuit = no alarmclosed circuit = alarm

2 3 4 5 6 7 81



Table 7-10Alarm output connector - pin assignment (NT6Q71AB alarm cable included in the NT6Q59AB kit)

Pin Description Usage

1 ALARMOUT_4_RET Unused

2 ALARMOUT_4

3 ALARMOUT_3_RET Minor

4 ALARMOUT_3

5 ALARMOUT_2_RET Major

6 ALARMOUT_2

7 ALARMOUT_1_RET Critical

8 ALARMOUT_1

Note 1: Those contacts are normally open.

Note 2: For each alarm output, a relay is present between the signal pin and the return pin. The maximum voltage is 30 VDC for the monitoring equipment connected to the output.

Table 7-11M1/F1 connector - pin assignment (NT6Q71AG/NT6Q71AF)

Pin Signal (M1) Signal (F1)

1 DSR

2 CD

3 DTR

4 GND GND

5 RD RD

6 TD TD

7 CTS

8 RTS

2 3 4 5 6 7 81

2 3 4 5 6 7 81



Table 7-12ESI connector - pin assignment (NT6Q71AC/NT6Q71AE)

Pin Signal

1 CLKIN+ (SDH)DATAIN+ (SONET)

2 CLKIN- (SDH)DATAIN- (SONET)

3 DATAIN+

4 CLKOUT- (SDH)DATAOUT- (SONET)

5 CLKOUT+ (SDH)DATAOUT+ (SONET)

6 DATAIN-

7 DATAOUT+

8 DATAOUT-

Note 1: BITS-1-2-1 (IN) uses pins 1 & 2 and BITS-1-2-2 (IN) uses pins 3 & 6

Note 2: BITS-1-2-1 (OUT) uses pins 4 & 5 and BITS-1-2-2 (OUT) uses pins 7 & 8

Table 7-13LAN, Craft and 10/100BT port connector - pin assignment (NTTC09C/Dx)

Pin Signal

MDI-X MDI

1 RX+ TX+

2 RX- TX-

3 TX+ RX+

4

5

6 TX- RX-

7

8

Note 1: The Ethernet cables connecting to the LAN and Craft ports of the OAM circuit pack must be shielded twisted pair. The Ethernet cables connecting to the 10/100BT ports on the 8xETH, 4x10/100BT+4x100FX and L2PA622M circuit packs must be shielded twisted pair. Refer to Ethernet service cable assemblies on page 8-35 for ordering information.

Note 2: The LAN, Craft and 10/100BT Ethernet ports are wired as MDI/MDI-X, and auto-detect the type of cable connected to it (straight or crossover).

2 3 4 5 6 7 81



E1/DS1 cable pinouts and assembliesCable details

The 28xE1/DS1 circuit pack, 28xE1/DS1(W/P) circuit pack with the 28xE1/DS1 1+1 I/O or 84xE1/DS1 1:N I/O module supports 64-pin Telco connectors to offer the E1/DS1 services. By default, the ports are 120/100 ohm balanced E1/DS1 electrical ports. A termination panel can be used to convert the 120 ohm balanced E1 ports to 75 ohm unbalanced E1 ports.

The 63xE1/DS1circuit pack supports 160-pin connectors to offer the E1/DS1 services. The ports are software configurable to 120 ohm balanced E1 ports or 75 ohm unbalanced E1 ports. The ports can also be configured as DS1 ports.

The following sections detail the pinouts and port mappings for the 75/120/100 ohm cable assemblies and for the 75 ohm termination panel. The E1/DS1 cables come with right or left routing.

These cable assemblies can be ordered from Ciena (see E1/DS1 cable assemblies on page 8-30) or produced locally to the specifications provided:

• Figure 7-5 on page 7-15 provides the 120 ohm cable connector pin assignment, which applies to the E1 connector (ports 1 -16) on the 28xE1/DS1 circuit pack, 28xE1/DS1 1+1 I/O module and 84xE1/DS1 1:N I/O module.

• Figure 7-6 on page 7-17 provides the 100 ohm cable connector pin assignment, which applies to the DS1 connector (ports 1-16) on the 28xE1/DS1 circuit pack, 28xE1/DS1 1+1 I/O module and 84xE1/DS1 1:N I/O module.

• Figure 7-7 on page 7-19 provides the 120 ohm E1 cable connector pin assignment for the E1 connector (ports 17-28) on the 28xE1/DS1 circuit pack,28xE1/DS1 1+1 I/O module and 84xE1/DS1 1:N I/O module.

• Figure 7-8 on page 7-21 provides the 100 ohm DS1 cable connector pin assignment for the DS1 connector (ports 17-28) on the 28xE1/DS1 circuit pack, 28xE1/DS1 1+1 I/O module and 84xE1/DS1 1:N I/O module.

• Table 7-14 on page 7-23 provides the 120 ohm E1/DS1 cable connector pin assignment for the E1/DS1 connector on the 63xE1/DS1Circuit Pack.

• Table 7-15 on page 7-28 provides the 75 ohm E1 cable connector pin assignment for the E1 connector on the 63xE1/DS1Circuit Pack.

• on page 7-30 provides E1/DS1 Port mapping for the E1/DS1 connector on 63xE1/DS1circuit pack vs. the Cable labeling.

• Figure 7-10 on page 7-31 shows the 75 ohm BNC termination panel for 16 channels. Using the termination panel, the 120 ohm balanced E1 services can be converted to 75 ohm unbalanced.



• Table 7-17 on page 7-32 lists the physical specifications for the 75 ohm BNC termination panel.

• Table 7-18 on page 7-32 lists the cable specifications for connecting E1 ports.

• Table 7-19 on page 7-33 lists the cable specifications for connecting the DS1 ports.

• Table 7-20 on page 7-34 lists the connector specifications for the shield connector required for the right or left routing E1 and DS1 cables.

• Figure 7-11 on page 7-35 shows the 120 ohm twisted pair E1 cable bundle.

• Figure 7-12 on page 7-35 shows the 64-pin 100 degree right routing cable connector.

• Figure 7-13 on page 7-35 shows the 64-pin 100 degree left routing cable connector.

Attention: The color codes and pinout provided apply to the suggested E1/DS1 cables. Color codes and pinout may vary by manufacturer.



28xE1/DS1 connector pinoutsFigure 7-2, 7-3 and 7-4 shows the faceplate of the 28xE1/DS1 circuit pack, the 84xE1/DS1 1:N I/O module and the 28xE1/DS1 1+1 I/O module. The 64-pin Telco connector and pinouts on these E1/DS1 I/O modules and circuit pack are common.

The 64-pin Telco connector and pinout used for ports 1 to 16 of the E1/DS1 circuit pack and I/O modules is presented in Figure 7-5 for E1 services and Figure 7-6 for DS1 services. The 64-pin Telco connector and pinout used for ports 17 to 28 of the E1/DS1 circuit pack and I/O modules and is presented in Figure 7-7 for E1 services and Figure 7-8 for DS1 services.


Figure 7-384xE1/DS1 1:N I/O module faceplate

Figure 7-428xE1/DS1 1+1 I/O module faceplate



Figure 7-5E1 connector - pin assignment (NT6Q73BA/CA/DA/EA, NT6Q72BA/CA/DA/EA)

Pin Signal Group Color Pin Signal Group Color(White/)

Pair

1 TX1+ 1 Orange 33 TX1- 1 Orange P1

2 RX1+ 1 Green 34 RX1- 1 Green P2

3 TX2+ 1 Blue 35 TX2- 1 Blue P3

4 RX2+ 1 Brown 36 RX2- 1 Brown P4



7 TX4+ 2 Blue 39 TX4- 2 Blue P7




11 TX6+ 3 Blue 43 TX6- 3 Blue P11




15 TX8+ 4 Blue 47 TX8- 4 Blue P15




19 TX10+ 5 Blue 51 TX10- 5 Blue P19




23 TX12+ 6 Blue 55 TX12- 6 Blue P23




20 19 18 17 16 15 14 13 12 11 10 9 8

7 6

5 4

3 2

1 29

30 28 27 26 25

22 23

24 21

32 31

39 38 37 36 35 33

34 40

50 49 48 43

45 47 46

44 41

42 60 59 58 57

52 54

55 56

53 51

61 63

64 62



27 TX14+ 7 Blue 59 TX14- 7 Blue P27




31 TX16+ 8 Blue 63 TX16- 8 Blue P31


Note: E1 connector (port 1 -16) on 28xE1/DS1 circuit pack, 28xE1/DS1 1+1 I/O module and 84xE1/DS1 1:N I/O module must have a shielded connector. Refer to Table 7-20 on page 7-34 for details on the shielded connector specifications.

Figure 7-5 (continued)E1 connector - pin assignment (NT6Q73BA/CA/DA/EA, NT6Q72BA/CA/DA/EA)



Figure 7-6DS1 connector - pin assignment (NT6Q73QA/TA, NT6Q72QA/TA)

Pin Signal VTG Color Pin Signal VTG Color Pair

1 TX1(tip) 1 White (WH/BU)

33 TX1(ring) 1 Blue (WH/BU)

P1

2 RX1(tip) 1 White (WH/OR)

34 RX1(ring) 1 Orange (WH/OR)

P2

3 TX2(tip) 1 White (WH/GN)

35 TX2(ring) 1 Green (WH/GN)

P3

4 RX2(tip) 1 White (WH/BR)

36 RX2(ring) 1 Brown (WH/BR)

P4

5 TX3(tip) 1 White (WH/GR)

37 TX3(ring) 1 Gray (WH/GR)

P5

6 RX3(tip) 1 Red (RD/BU)

38 RX3(ring) 1 Blue (RD/BU)

P6

7 TX4(tip) 1 Red (RD/OR)

39 TX4(ring) 1 Orange (RD/OR)

P7

8 RX4(tip) 1 Red (RD/GN)

40 RX4(ring) 1 Green (RD/GN)

P8

9 TX5(tip) 2 Red (RD/BR)

41 TX5(ring) 2 Brown (RD/BR)

P9

10 RX5(tip) 2 Red (RD/GR)

42 RX5ring) 2 Gray (RD/GR)

P10

11 TX6(tip) 2 Black (BK/BU)

43 TX6(ring) 2 Blue (BK/BU)

P11

12 RX6(tip) 2 Black (BK/OR)

44 RX6(ring) 2 Orange (BK/OR)

P12

13 TX7(tip) 2 Black (BR/GN)

45 TX7(ring) 2 Green (BK/GN)

P13

14 RX7(tip) 2 Black (BK/BR)

46 RX7(ring) 2 Brown (BK/BR)

P14

15 TX8(tip) 2 Black (BK/GR)

47 TX8(ring) 2 Gray (BK/GR)

P15

16 RX8(tip) 2 Yellow (YL/BU)

48 RX8(ring) 2 Blue (YL/BU)

P16

17 TX9(tip) 3 Yellow (YL/OR)

49 TX9(ring) 3 Orange (YL/OR)

P17

20 19 18 17 16 15 14 13 12 11 10 9 8

7 6

5 4

3 2

1 29

30 28 27 26 25

22 23

24 21

32 31

39 38 37 36 35 33

34 40

50 49 48 43

45 47 46

44 41

42 60 59 58 57

52 54

55 56

53 51

61 63

64 62



18 RX9(tip) 3 Yellow (YL/GN)

50 RX9(ring) 3 Green (YL/GN)

P18

19 TX10(tip)

3 Yellow (YL/BR)

51 TX10(ring) 3 Brown (YL/BR)

P19

20 RX10(tip)

3 Yellow (YL/GR)

52 RX10(ring) 3 Gray (YL/GR)

P20

21 TX11(tip)

3 Purple (PU/BU)

53 TX11(ring) 3 Blue (PU/BU)

P21

22 RX11(tip)

3 Purple (PU/OR)

54 RX11(ring) 3 Orange (PU/OR)

P22

23 TX12(tip)

3 Purple (PU/GN)

55 TX12(ring) 3 Green (PU/GN)

P23

24 RX13(tip)

3 Purple (PU/BR)

56 RX13(ring) 3 Brown (PU/BR)

P24

25 TX13(tip)

4 Purple (PU/GR)

57 TX13(ring) 4 Gray (PU/GR)

P25

26 RX13(tip)

4 Wh/Blue (WH-BU/BU)

58 RX13(ring) 4 Blue (WH-BU/BU)

P26

27 TX14(tip)

4 Wh/Blue (WH-BU/OR)

59 TX14(ring) 4 Orange (WH-BU/OR)

P27

28 RX14(tip)

4 Wh/Blue (WH-BU/GN)

60 RX14(ring) 4 Green (WH-BU/GN)

P28

29 TX15(tip)

4 Wh/Blue (WH-BU/BR)

61 TX15(ring) 4 Brown (WH-BU/BR)

P29

30 RX15(tip)

4 Wh/Blue (WH-BU/GR)

62 RX15(ring) 4 Gray (WH-BU/GR)

P30

31 TX16(tip)

4 Wh/Or (WH-OR/BU)

63 TX16(ring) 4 Blue (WH-OR/BU)

P31

32 RX16(tip)

4 Wh/OR (WH-OR/OR)

64 RX16(ring) 4 Orange (WH-OR/OR)

P32

Note: DS1 connectors (port 1-16) on the 28xE1/DS1 circuit pack, 28xE1/DS1 1+1 I/O module and 84xE1/DS1 1:N I/O module must have a shielded connector. Refer to Table 7-20 on page 7-34 for details on the shielded connector specifications.

Figure 7-6 (continued)DS1 connector - pin assignment (NT6Q73QA/TA, NT6Q72QA/TA)



Figure 7-7E1 connector (port 17-28) - pin assignment (NT6Q73BA/CA/DA/EA, NT6Q72BA/CA/DA/EA)

Pin Signal Group Color Pin Signal Group Color(White/)

Pair



3 TX18+ 1 Blue 35 TX18- 1 Blue P3




7 TX20+ 2 Blue 39 TX20- 2 Blue P7




11 TX22+ 3 Blue 43 TX22- 3 Blue P11




15 TX24+ 4 Blue 47 TX24- 4 Blue P15




19 TX26+ 5 Blue 51 TX26- 5 Blue P19




23 TX28+ 6 Blue 55 TX28- 6 Blue P23


25 NC 57 NC P25

26 NC 58 NC P26

20 19 18 17 16 15 14 13 12 11 10 9 8

7 6

5 4

3 2

1 29

30 28 27 26 25

22 23

24 21

32 31

39 38 37 36 35 33

34 40

50 49 48 43

45 47 46

44 41

42 60 59 58 57

52 54

55 56

53 51

61 63

64 62



27 NC 59 NC P27

28 NC 60 NC P28

29 NC 61 NC P29

30 NC 62 NC P30

31 NC 63 NC P31

32 NC 64 NC P32

Note: E1 connectors (port 17-28) on the 28xE1/DS1 circuit pack,28xE1/DS1 1+1 I/O module and 84xE1/DS1 1:N I/O module must have a shielded connector. Refer to Table 7-20 on page 7-34 for details on the shielded connector specifications.

Figure 7-7 (continued)E1 connector (port 17-28) - pin assignment (NT6Q73BA/CA/DA/EA, NT6Q72BA/CA/DA/EA)



Figure 7-8DS1 connector (port 17-28) - pin assignment (NT6Q73QA/TA, NT6Q72QA/TA)

Pin Signal VTG Color Pin Signal VTG Color Pair

1 TX17(tip) 1 White (WH/BU)

33 TX17(ring) 1 Blue (WH/BU)

P1

2 RX17(tip) 1 White (WH/OR)

34 RX17(ring) 1 Orange (WH/OR)

P2

3 TX18(tip) 1 White (WH/GN)

35 TX18(ring) 1 Green (WH/GN)

P3

4 RX18(tip) 1 White (WH/BR)

36 RX18(ring) 1 Brown (WH/BR)

P4

5 TX19(tip) 1 White (WH/GR)

37 TX19(ring) 1 Gray (WH/GR)

P5

6 RX19(tip) 1 Red (RD/BU)

38 RX19(ring) 1 Blue (RD/BU)

P6

7 TX20(tip) 1 Red (RD/OR)

39 TX20(ring) 1 Orange (RD/OR)

P7

8 RX20(tip) 1 Red (RD/GN)

40 RX20(ring) 1 Green (RD/GN)

P8

9 TX21(tip) 2 Red (RD/BR)

41 TX21(ring) 2 Brown (RD/BR)

P9

10 RX21(tip) 2 Red (RD/GR)

42 RX21(ring) 2 Gray (RD/GR)

P10

11 TX22(tip) 2 Black (BK/BU)

43 TX22(ring) 2 Blue (BK/BU)

P11

12 RX22(tip) 2 Black (BK/OR)

44 RX22(ring) 2 Orange (BK/OR)

P12

13 TX23(tip) 2 Black (BR/GN)

45 TX23(ring) 2 Green (BK/GN)

P13

14 RX23(tip) 2 Black (BK/BR)

46 RX23(ring) 2 Brown (BK/BR)

P14

15 TX24(tip) 2 Black (BK/GR)

47 TX24(ring) 2 Gray (BK/GR)

P15

16 RX24(tip) 2 Yellow (YL/BU)

48 RX24(ring) 2 Blue (YL/BU)

P16

20 19 18 17 16 15 14 13 12 11 10 9 8

7 6

5 4

3 2

1 29

30 28 27 26 25

22 23

24 21

32 31

39 38 37 36 35 33

34 40

50 49 48 43

45 47 46

44 41

42 60 59 58 57

52 54

55 56

53 51

61 63

64 62



17 TX25(tip) 3 Yellow (YL/OR)

49 TX25(ring) 3 Orange (YL/OR)

P17

18 RX25(tip) 3 Yellow (YL/GN)

50 RX25(ring) 3 Green (YL/GN)

P18

19 TX26(tip) 3 Yellow (YL/BR)

51 TX26(ring) 3 Brown (YL/BR)

P19

20 RX26(tip) 3 Yellow (YL/GR)

52 RX26(ring) 3 Gray (YL/GR)

P20

21 TX27(tip) 3 Purple (PU/BU)

53 TX27(ring) 3 Blue (PU/BU)

P21

22 RX27(tip) 3 Purple (PU/OR)

54 RX27(ring) 3 Orange (PU/OR)

P22

23 TX28(tip) 3 Purple (PU/GN)

55 TX28(ring) 3 Green (PU/GN)

P23

24 RX28(tip) 3 Purple (PU/BR)

56 RX28(ring) 3 Brown (PU/BR)

P24

25 NC 57 NC P25

26 NC 58 NC P26

27 NC 59 NC P27

28 NC 60 NC P28

29 NC 61 NC P29

30 NC 62 NC P30

31 NC 63 NC P31

32 NC 64 NC P32

Note: DS1 connectors (port 17-28) on the 28xE1/DS1 circuit pack, 28xE1/DS1 1+1 I/O module and 84xE1/DS1 1:N I/O module must have a shielded connector. Refer to Table 7-20 on page 7-34 for details on the shielded connector specifications.

Figure 7-8 (continued)DS1 connector (port 17-28) - pin assignment (NT6Q73QA/TA, NT6Q72QA/TA)



63xE1/DS1connector pinoutsFigure 7-9 on page 7-23 shows the faceplate of the 63xE1/DS1circuit pack. The first 160-pin Telco connector is used for ports 1 to 32 of the circuit pack. The second 160-pin Telco connector is used for ports 33 to 63 of the circuit pack. The pinout information is presented in Table 7-14 for 120 Ohms E1 services and Table 7-15 for 75 Ohms E1 services. contains the mapping between the port numbers of the circuit pack and the ports numbers of the cables.

Attention: Each connector of the E1 cable assemblies for the 63xE1/DS1circuit pack has 2 cables attached to the connector. One cable for the Rx signals and a second cable for the Tx signals.

Figure 7-963xE1/DS1circuit pack faceplate

Table 7-14E1 connector (120 Ohms) of the 63xE1/DS1Circuit Pack- pin assignment (NTTC41Bx)

Port# Cable Pin Signal Group Color Pin Signal Group Color

-

Rx

1 NC - - 80 NC - -

- 2 NC - - 79 NC - -

- 3 NC - - 78 NC - -

- 4 NC - - 77 NC - -

32

Rx

5 RX32+

8

Blue/White 76 RX32-

8

Blue

31 6 RX31+ Brown/white 75 RX31- Brown

30 7 RX30+ Orange/white 74 RX30- Orange

29 8 RX29+ Green/white 73 RX29- Green



28

Rx

9 RX28+

7

Blue/White 72 RX28-

7

Blue




24

Rx

13 RX24+

6

Blue/White 68 RX24-

6

Blue




20

Rx

17 RX20+

5

Blue/White 64 RX20-

5

Blue




16

Rx

21 RX16+

4

Blue/White 60 RX16-

4

Blue




12

Rx

25 RX12+

3

Blue/White 56 RX12-

3

Blue




Table 7-14 (continued)E1 connector (120 Ohms) of the 63xE1/DS1Circuit Pack- pin assignment (NTTC41Bx)




8

Rx

29 RX8+

2

Blue/White 52 RX8-

2

Blue




4

Rx

33 RX4+

1

Blue/White 48 RX4-

1

Blue




-

Rx

37 NC - - 44 NC - -

- 38 NC - - 43 NC - -

- 39 NC - - 42 NC - -

- 40 NC - - 41 NC - -

The remainder of this table applies to the Tx cable

-

Tx

81 NC - - 160 NC - -

- 82 NC - - 159 NC - -

- 83 NC - - 158 NC - -

- 84 NC - - 157 NC - -

32

Tx

85 TX32-

8

Blue 156 TX32+

8

Blue/White

31 86 TX31- Brown 155 TX31+ Brown/white

30 87 TX30- Orange 154 TX30+ Orange/white

29 88 TX29- Green 153 TX29+ Green/white





28

Tx

89 TX28-

7

Blue 152 TX28+

7

Blue/White




24

Tx

93 TX24-

6

Blue 148 TX24+

6

Blue/White




20

Tx

97 TX20-

5

Blue 144 TX20+

5

Blue/White




16

Tx

101 TX16-

4

Blue 140 TX16+

4

Blue/White




12

Tx

105 TX12-

3

Blue 136 TX12+

3

Blue/White








8

Tx

109 TX8-

2

Blue 132 TX8+

2

Blue/White




4

Tx

113 TX4-

1

Blue 128 TX4+

1

Blue/White




-

Tx

117 NC - - 124 NC - -

- 118 NC - - 123 NC - -

- 119 NC - - 122 NC - -

- 120 NC - - 121 NC - -





Table 7-15E1 connector (75 Ohms) of the 63xE1/DS1Circuit Pack - pin assignment (NTTC41Ax)

Rx Cable Tx Cable

Port# Conductor Pin Signal Pin Signal Pin Signal Pin Signal

- - 1 NC 80 NC 81 NC 160 NC

- - 2 NC 79 NC 82 NC 159 NC

- - 3 NC 78 NC 83 NC 158 NC

- - 4 NC 77 NC 84 NC 157 NC

32 32 5 SIG-RX32 76 GND 85 GND 156 SIG-TX32


































- - 37 NC 44 NC 117 NC 124 NC

- - 38 NC 43 NC 118 NC 123 NC

- - 39 NC 42 NC 119 NC 122 NC

- - 40 NC 41 NC 120 NC 121 NC

Table 7-15 (continued)E1 connector (75 Ohms) of the 63xE1/DS1Circuit Pack - pin assignment (NTTC41Ax)

Rx Cable Tx Cable

Port# Conductor Pin Signal Pin Signal Pin Signal Pin Signal



Table 7-16E1 Port mapping - E1 connector on 63xE1/DS1circuit pack vs. Cable labeling

Port number on connector 1 of the 63xE1/DS1circuit pack

Port number on the NTTC41Ax and NTTC41Bx cables



1 1 33 1

2 2 34 2

3 3 35 3

4 4 36 4

5 5 37 5

6 6 38 6

7 7 39 7

8 8 40 8

9 9 41 9

10 10 42 10

11 11 43 11

12 12 44 12

13 13 45 13

14 14 46 14

15 15 47 15

16 16 48 16

17 17 49 17

18 18 50 18

19 19 51 19

20 20 52 20

21 21 53 21

22 22 54 22



Figure 7-1075 ohm termination panel - 16 channel

23 23 55 23

24 24 56 24

25 25 57 25

26 26 58 26

27 27 59 27

28 28 60 28

29 29 61 29

30 30 62 30

31 31 63 31

32 32 32

Table 7-16 (continued)E1 Port mapping - E1 connector on 63xE1/DS1circuit pack vs. Cable labeling







Attention: The 75 ohm termination panel is labeled from 1-16 by default, but includes an additional overlay label which can be installed by the user when connecting the ports 17-28 of the 28xE1/DS1 circuit pack, 28xE1/DS1 1+1 I/O module or 84xE1/DS1 1:N I/O module.

Table 7-18 lists the E1 cable specifications and Table 7-19 lists the DS1 cable specifications for connecting E1 and DS1 ports respectively, on the 28xE1/DS1 circuit pack, 28xE1/DS1 1+1 I/O module or 84xE1/DS1 1:N I/O module.

Table 7-17Physical specifications for 75 ohm BNC termination panel

Feature Physical specification Notes

Data rate 2.048 Mbps

75 ohm connector Dual coax female BNC

120 ohm connector(for interconnection with 6130 shelf)

64-pin Telco See Figure 7-5 on page 7-15 for pinout information on 64-pin connector.

Power supply none required

Link-to-data isolation 500 volts AC/DC

Temperature range 0-50oC

Height 1U (44.0 mm / 1.9 in.)

Width 483.0 mm / 19 in.

Depth 89.0 mm / 3.5 in.

Table 7-18Cable specifications for connecting E1 ports

Feature Physical specification

Conductor 26 AWG solid tin plated copper

Insulation Solid polyolefin

Pairs Two conductors twisted into pairs with varying lay length

Pair groups Four twisted pairs are cabled together

Jacket Four pair groups are jacketed with PVC and each group is numbered

Cable Groups 8 four pair groups are cabled together



Colour Code • Pair 1: Orange-White/Orange

• Pair 2: Blue-White/Blue

• Pair 3: Green-White/Green

• Pair 4: Brown-White/Brown

Shield Overall Aluminum/Mylar foil shield with aluminum side facing out. 26 AWG tinned copper drain wire over the foil with a 34 AWG tin plated copper braid, 65% coverage.

Jacket Gray PVC jacket. Overall dimension 15,6 mm Nom.

Electrical Characteristics

Impedance 120+/- Ohms Nom.

Capacitance 13.3 pF/ft Nominal

Velocity of propagation 65% Nominal

Near End Cross Talk (NEXT) pair to pair

53 dB at 20 MHz

Dielectric Strength

Conductor to Conductor 2.5 KV DC

Core to Sheath 2.3 KV DC

Table 7-19Cable specifications for connecting DS1 ports


Conductor 24 AWG solid tin plated copper

Insulation Solid polyolefin or solid Polyethylene

Pairs Two conductors twisted into pairs with varying lay length

Pair groups 32 twisted pairs are cabled together

Jacket 32 pair groups are jacketed with PVC

Colour Code Refer to Figure 7-6 on page 7-17 for colour coding information

Shield 24 AWG tinned copper drain wire over the foil with a 34 AWG tin plated copper braid, 65% coverage.

Jacket Gray PVC jacket. Overall dimension 14.0 mm Nom.

Table 7-18 (continued)Cable specifications for connecting E1 ports




Electrical Characteristics

Impedance 100 +/- 15 Ohms Nom.

Capacitance 13.3 pF/ft Nominal

Velocity of propagation 65% Nominal

Near End Cross Talk (NEXT) pair to pair

53 dB at 20 MHz

Dielectric Strength

Conductor to Conductor 2.5 KV DC

Core to Sheath 2.3 KV DC

Table 7-20Connector specifications for right/left routing E1/DS1 cables for the 28xE1/DS1 circuit pack


Connector

Connector type 64 POS Male AMP Champ (0.085) or equivalent ‘key telephone’ connector

Latching hardware 4-40 screws - 2 places

Component Minimum 30uin Au over 50uin Ni plating on contacts

Hood

Hood exit Angled exit recommended at 100 degrees. Close proximity of connector positions on 6130 faceplate prevents the user of many low profile right/left angle exit hoods. (See Figure 7-12 on page 7-35 for the right routing cable connector and Figure 7-13 on page 7-35 for the left routing cable connector)

Depth 60 mm maximum connector hood and cable depth from connector mating face

Component Metal plated plastic (100% coverage) or fully metal shielded connector hood

Terminations Shielded hood terminated to cable shield and to both hood mounting screws via the cable drain wires (both mounting screws must attach to the drain wire through Y’d arrangement, or two drain wires) and interference contact to exposed braid at the exit of the cable from hood.

Table 7-19 (continued)Cable specifications for connecting DS1 ports




Figure 7-11E1 cable bundle specification

Figure 7-1264-pin E1/DS1 100 degree right routing cable connector

Figure 7-1364-pin E1/DS1 100 degree left routing cable connector



E1/DS1 Cable routingRight routing E1 or DS1 cables must be used for the following applications:



• 28xE1/DS1 1+1 I/O module equipped in the 6130 I/O slot 8

• 84xE1/DS1 1:N I/O module - for the 3 E1/DS1 connectors to the right of the I/O module:

– Slot 5 - ports 1-16



Left routing E1 or DS1 cables must be used for the following applications:

• 28xE1/DS1 1+1 I/O module equipped in the 6130 I/O slot 4

• 84xE1/DS1 1:N I/O module - for the 3 E1/DS1 connectors to the left of the I/O module:




The cable connectors for the right / left routing cables must comply to the specifications provided in Table 7-20.



Optical specificationsThe following sections provide details of the optical specifications. All the optical SFPs for the 6130 are equipped with LC type connectors.

The following assumptions were made when calculating the dispersion and attenuation limited distances quoted in the optical specifications:

• NSDF fiber plant is being used

• dispersion and attenuation coefficient are as listed in Table 7-21.

Table 7-21Optical specifications - assumed dispersion and attenuation coefficient

Wavelength

1310 nm 1550 nm + C-band

Dispersion coefficient (ps/nm/km)

6.0 17.0

Attenuation coefficient (dB/km)

0.35 0.25

ATTENTIONThe dispersion and attenuation limited distances quoted in the optical specifications are based on the dispersion and attenuation coefficients detailed in Table 7-21 and are for guidance only and must be verified by a full link budget calculation. The actual limiting distance is the lower of the dispersion limited or attenuation limited distances.



STM-1/4/16/OC-3/12/48, 100Base and GE SFP optical specifications

Table 7-22 lists the optical specifications for the STM-1/OC-3 optical SFPs.

Table 7-22Optical specifications for STM-1/OC-3 SFPs

Classification SR0 IR1/S1.1 LR1/L1.1 LR2/L1.2

PEC NTTP02AD NTTP02CD NTTP02ED NTTP02FD/NTTP02FF

Transmitter

Transmitter type LED FP laser DFB laser DFB laser

Nominal wavelength 1270 nm to 1380 nm

1310 nm 1310 nm 1550 nm

Transmit output power (max) -14 dBm -8 dBm 0 dBm 0 dBm

Transmit output power (min.) -20 dBm -15 dBm -5 dBm -5 dBm

Spectral width 200 nm (FWHM)

7.7 nm (RMS)

1 nm (-20 dB)

1 nm (-20 dB)

Minimum side mode suppression ratio

- - 30 dB 30 dB

Minimum extinction ratio 10 dB 8.2 dB 10 dB 10 dB

Power monitor accuracy(see Note 2)

+/- 2 dB +/- 2 dB +/- 2 dB +/- 2 dB

Receiver

Receiver type PIN photodiode APD APD APD

Wavelength range 1100 nm to 1600 nm

1261 nm to 1580 nm

1261 nm to 1580 nm

1260 nm to 1580 nm

Nominal wavelength 1310 nm 1310 nm 1310 nm 1550 nm

Receiver sensitivity -30 dBm -28 dBm -34 dBm -34 dBm

Receiver overload -14 dBm -8 dBm -10 dBm -10 dBm

Path penalty - 1 dB 1 dB 1 dB

Maximum receive reflectance - - - -25 dB

Power monitor accuracy (see Note 2, Note 4)

+/- 2 dB +/- 2 dB +/- 2 dB +/- 2 dB




Optical path

Attenuation range 0 dB to 10 dB

0 dB to 12 dB 10 dB to 28 dB 10 dB to 28 dB

Nominal reach (see Note 3) 2 km 15 km 40 km 80 km

Maximum dispersion - 96 ps/nm - -

Minimum optical return loss - - - 20 dB

Dispersion limited distance (see Note 5)

- 16 km - -

Attenuation limited distance (see Note 5)

2 km 34.3 km 80 km 112 km

Note 1: All parameter values in the above table achieve an optical system BER better than 1x10-10 when used over G.652 specified SMF-28 fiber. The exception is SR0 where the values are for use over 62.5 μm core, 500 MHz-km modal bandwidth MMF as specified in ANSI T1.416.01-1999.

Note 2: Power monitor accuracy figures are for normal operating range (minimum to maximum transmit power, receiver sensitivity to overload).

Note 3: Nominal reach figures are for classification purposes only as defined in the appropriate standards.

Note 4: Received power lower / higher threshold crossed alarms are not supported for the NTTP02CD, NTTP02ED, NTTP02FD SFPs.

Note 5: The dispersion and attenuation limited distances are based on the dispersion and attenuation coefficients detailed in Table 7-21 on page 7-37 and are for guidance only and must be verified by a full link budget calculation. The actual limiting distance is the lower of the dispersion limited or attenuation limited distances.


Classification LR1/L4.1 LR2/L4.2

PEC NTTP05EF NTTP05FF

Transmitter

Transmitter type DFB laser DFB laser

Nominal wavelength 1310 nm 1550 nm

Transmit output power (max) +2 dBm +2 dBm

Transmit output power (min.) -3 dBm -3 dBm

Table 7-22 (continued)Optical specifications for STM-1/OC-3 SFPs

Classification SR0 IR1/S1.1 LR1/L1.1 LR2/L1.2




Spectral width 1 nm (-20 dB) 1 nm (-20 dB)

Minimum side mode suppression ratio 30 dB 30 dB

Minimum extinction ratio 10 dB 10 dB

Power monitor accuracy (see Note 2) +/- 2 dB +/- 2 dB

Receiver

Receiver type APD APD

Wavelength range 1260 nm to 1580 nm 1260 nm to 1580 nm

Nominal wavelength 1310 nm 1550 nm

Receiver sensitivity -28 dBm -28 dBm

Receiver overload -8 dBm -8 dBm

Path penalty 1 dB 1 dB

Maximum receive reflectance -14 dB -27 dB

Power monitor accuracy (see Note 2, Note 4) +/- 2 dB +/- 2 dB

Optical path

Attenuation range 10 dB to 24 dB 10 dB to 24 dB

Nominal reach (see Note 3) 40 km 80 km

Minimum optical return loss 20 dB 24 dB

Dispersion limited distance (see Note 5) - -

Attenuation limited distance (see Note 5) 68.6 km 96 km

Note 1: All parameter values in the above table achieve an optical system BER better than 1x10-10 when used over G.652 specified SMF-28 fiber.



Note 4: Received power lower / higher threshold crossed alarms are not supported for the NTTP05EF, NTTP05FF SFPs.



Classification LR1/L4.1 LR2/L4.2




Classification SR1/I16.1 IR1/S16.1 LR1/L16.1 LR2/L16.2

PEC NTTP03BF NTTP03CF NTTP03EF NTTP03FF

Transmitter

Transmitter type FP laser DFB laser DFB laser DFB laser


Transmit output power (max) -3 dBm 0 dBm +3 dBm +3 dBm

Transmit output power (min.) -10 dBm -5 dBm -2 dBm -2 dBm

Spectral width 4 nm (RMS) 1 nm (-20 dB) 1 nm (-20 dB) 1 nm (-20 dB)


- 30 dB 30 dB 30 dB

Minimum extinction ratio 8.2 dB 8.2 dB 8.2 dB 8.2 dB

Power monitor accuracy (see Note 2) +/- 2 dB +/- 2 dB +/- 2 dB +/- 2 dB

Receiver

Receiver type PINphotodiode

PINphotodiode

APD APD


1260 nm to 1360 nm

1280 nm to 1335 nm

1500 nm to 1580 nm


Receiver sensitivity -18 dBm -18 dBm -27 dBm -28 dBm

Receiver overload -3 dBm 0 dBm -9 dBm -9 dBm

Path penalty 1 dB 1 dB 1 dB 1 dB

Maximum receive reflectance -27 dB -27 dB -27 dB -27 dB

Power monitor accuracy (see Note 2, Note 4)

+/- 2 dB +/- 2 dB +/- 2 dB +/- 2 dB

Optical path

Attenuation range 0 dB to 7 dB 0 dB to 12 dB 12 dB to 24 dB 12 dB to 24 dB

Nominal reach (see Note 3) 2 km 15 km 40 km 80 km

Maximum dispersion 12 ps/nm - - 1600 ps/nm

Minimum optical return loss 24 dB 24 dB 24 dB 24 dB




2 km - - 94 km


20 km 34.3 km 68.6 km 96 km




Note 4: Received power lower / higher threshold crossed alarms are not supported for the NTTP03BF, NTTP03CF, NTTP03EF and NTTP03FF SFPs.



Classification SR1/I16.1 IR1/S16.1 LR1/L16.1 LR2/L16.2



Table 7-25 lists the optical specifications for the STM-1/4/OC-3/12 optical SFP.

Table 7-25Optical specifications for STM-1/4/OC-3/12 SFPs

Classification IR1/S1.1_S4.1

PEC NTTP04CF, NTTP04CDE6

Transmitter

Transmitter type FP laser

Nominal wavelength 1310 nm

Transmit output power (max) -8 dBm

Transmit output power (min.) -15 dBm

Spectral width 2.5 nm (RMS)

Minimum extinction ratio 8.2 dB

Power monitor accuracy (see Note 2) +/- 2 dB

Receiver

Receiver type APD


Nominal wavelength 1310 nm

Receiver sensitivity -28 dBm

Receiver overload -8 dBm

Path penalty 1 dB

Power monitor accuracy (see Note 2, Note 4) +/- 2 dB

Optical path


Nominal reach (see Note 3) 15 km

Maximum dispersion 74 ps/nm



Dispersion limited distance (see Note 5) 12.3 km

Attenuation limited distance (see Note 5) 34.3 km




Note 4: Received power lower / higher threshold crossed alarms are not supported for the NTTP04CF SFP.


Table 7-25 (continued)Optical specifications for STM-1/4/OC-3/12 SFPs

Classification IR1/S1.1_S4.1



Table 7-26 lists the optical specifications for the STM-1/4/16/OC-3/12/48 CWDM optical SFPs.

Table 7-26Optical specifications for STM-1/4/16/OC-3/12/48 SFPs

Classification 2.5G NRZ CWDM(S-C8L1-1Dx)

PEC NTK590xH(see Note 7)

Transmitter

Transmitter type DFB laser

Nominal wavelength 1471 nm to 1611 nm @ 20 nm +/-6.5 nm

Transmit output power (max) +5 dBm

Transmit output power (min.) 0 dBm

Spectral width 1 nm (-20 dB)

Minimum side mode suppression ratio 30 dB



Receiver

Receiver type APD


Nominal wavelength 1471 nm to 1611 nm @ 20 nm

Receiver sensitivity (see Note 4) -28 dBm

Receiver overload (see Note 4) -9 dBm

Path penalty 2.5 dB

Maximum receive reflectance -27 dB




Optical path

Attenuation range 14 dB to 25.5 dB

Nominal reach (see Note 3) See Note 5


Minimum optical return loss 24 dB

Dispersion limited distance (see Note 6) See Note 5

Attenuation limited distance (see Note 6) See Note 5

Note 1: All parameter values in the table achieve an optical system BER better than 1x10-10 when used over G.652 specified SMF-28 fiber except for the CWDM value which is for an optical system BER better than 1x10-12.



Note 4: Received power lower / higher threshold crossed alarms are not supported for the NTK590xH SFPs.

Note 5: CWDM reach is consistent with Appendix II of ITU-T G.695 (refer to G.695 Table II.2 for parameter values and G.695 Table II.1 for attenuation values). Dispersion limits are based on 21.1 ps/nm-km.


Note 7: Refer to Ordering information and system engineering rules on page 8-1 for a list of supported wavelengths and PECs.

Table 7-26 (continued)Optical specifications for STM-1/4/16/OC-3/12/48 SFPs

Classification 2.5G NRZ CWDM(S-C8L1-1Dx)



Table 7-27 lists the optical specifications for the STM-16/OC-48 DWDM optical SFPs.

Table 7-27Optical specifications for OC-48/STM-16 DWDM SFPs

Parameter Value

PEC NTK585xx See Small form-factor pluggable (SFP) modules on page 8-23

Transmitter

Transmitter type Direct mod.

Wavelength range 1528.77 nm to 1564.68 nm (see Note 1)

Central wavelength accuracy +/- 0.10 nm

Transmit output power (max) +4.0 dBm

Transmit output power (min) +0.0 dBm

Spectral width 1 nm



Power monitor accuracy +/- 2 dB

Chirp polarity Non-chirp

Receiver

Receiver type APD

Wavelength range 1528.77 nm to 1564.68 nm

Receiver sensitivity at OSNR >= 27 dB (see Note 4) -28 dBm (see Note 2)

Receiver overload -8 dBm

Path penalty 2 dB (see Note 3)


Power monitor accuracy +/- 2 dB



Optical path

Attenuation range at OSNR >= 27 dB (see Note 4) 12 dB to 26 dB

Nominal reach (see Note 5) 120 km


Dispersion limited distance (see Note 6) 120 km

Attenuation limited distance (see Note 6) 100 km

Note 1: Refer to Small form-factor pluggable (SFP) modules on page 8-23 for list of supported wavelengths and PECs.

Note 2: The sensitivity level is the minimum optical power for which the interface meets a bit-error-rate of 10-12.

Note 3: At the dispersion maximum.

Note 4: Quoted OSNRs are as measured using 0.1 nm resolution bandwidth.



Table 7-27 (continued)Optical specifications for OC-48/STM-16 DWDM SFPs

Parameter Value



Table 7-28 lists the optical specifications for the 100Base SFPs.

Table 7-28Optical specifications for 100Base SFPs

Classification 100BaseLX10 100Base BX10-U(see Note 3)

100BaseBX10-D(see Note 3)

PEC NTTP08SD NTTP09BD NTTP10BD

Transmitter

Transmitter type FP laser FP laser FP laser

Nominal wavelength 1310 nm 1310 nm 1530 nm

Transmit output power (max) -8 dBm -8 dBm -8 dBm

Transmit output power (min.) -15 dBm -14 dBm -14 dBm

Spectral width 7.7 nm (RMS) 7.7 nm (RMS) 4.4 nm (RMS)

Minimum extinction ratio 5 dB 6.6 dB 6.6 dB

Receiver

Receiver type PIN photodiode PIN photodiode PIN photodiode


1480 nm to 1580 nm

1260 nm to 1360 nm

Nominal wavelength 1310 nm 1530 nm 1310 nm

Receiver sensitivity (see Note 4) -28 dBm -28.2 dBm -28.2 dBm

Receiver overload (see Note 4) - 8 dBm - 8 dBm - 8 dBm

Path penalty 4.5 dB 4.5 dB 4.5 dB

Maximum receive reflectance -12 dB -12 dB -12 dB

Optical path

Reach 10 km (see Note 2)

10 km (see Note 2)

10 km (see Note 2)

Note 1: All parameter values in the above table achieve an optical system BER better than 1x10-12.

Note 2: 0.5 m to 10 km over G.652 SMF.

Note 3: Used for a bidirectional link over a single fiber with an upstream SFP fitted at one end of the link and an downstream SFP fitted at the other end of the link. The upstream SFP transmits at 1310 nm and receives at 1530 nm, the downstream SFP transmits at 1530 nm and receives at 1310 nm.

Note 4: Received power lower / higher threshold crossed alarms are not supported for the NTTP08SD SFP.



Table 7-29 and lists the optical specifications for the GE optical SFPs.

Table 7-29Optical specifications for GE SFP

Classification CWDM

PEC NTK591xB

Transmitter

Transmitter type DFB laser

Nominal wavelength 1471 nm to

1611 nm @

20 nm +/-6.5nm

Transmit output power (max) +5 dBm

Transmit output power (min) 0 dBm

Spectral width 1 nm(-20 dB)


Minimum extinction ratio 9 dB

Receiver

Receiver type PIN photodiode


Nominal wavelength 1260 nm to

1620 nm @20 nm

Receiver sensitivity -24 dBm

Receiver overload 0 dBm

Path penalty 2 dB


Optical path


Nominal reach (see Note 2)

See Note 6


Dispersion limited distance (see Note 5) See Note 6

Attenuation limited distance (see Note 5) See Note 6





Note 3: 2 m to 220 m over 62.5 μm core, 160 MHz-km MMF; 2 m to 550 m over 50 μm core, 500 MHz-km MMF.

Note 4: 2 m to 10 km over 10 μm core SMF; 2 m to 550 m over MMF.


Note 6: CWDM reach is consistent with Appendix II of ITU-T G.695 (refer to G.695 Table II.2 for parameter values and G.695 Table II.1 for attenuation values). Dispersion limits are based on 21.1 ps/nm-km.

Table 7-29 (continued)Optical specifications for GE SFP

Classification CWDM



Table 7-30Optical specifications for GE SFPs

Classification SX (see Note 2)

LX ZX 1000BaseBX10-U(see Note 11)


PEC NTTP01AFNTTP06AF

NTTP01CF NTTP07FF NTTP58BD NTTP59BD

Transmitter

Transmitter type VCSEL FP laser DFB laser FP laser FP laser

Nominal Wavelength 850 nm 1310 nm 1550 nm 1310 nm 1490 nm

Transmit output power (max)

<0 dBm (see Note 3)

-3 dBm +5 dBm -3 dBm -3 dBm

Transmit output power (min.)

-9.5 dBm -9.5 dBm 0 dBm -9 dBm -9 dBm

Spectral width 0.85 nm (RMS)

4 nm (RMS) 1 nm (-20 dB) See Note 9 See Note 9


- - 30 dB - -

Minimum extinction ratio

9 dB 9 dB 9 dB 6 dB 6 dB

Receiver

Receiver type PINphotodiode

PIN photodiode

PIN photodiode

PIN photodiode

PINphotodiode


1270 nm to 1355 nm

1540 nm to 1570 nm

1480 nm to 1500 nm

1260 nm to 1360 nm

Nominal wavelength 850 nm 1310 nm 1550 nm 1490 nm 1310 nm

Receiver sensitivity (see Note 4)

-17 dBm -20 dBm -24 dBm -19.5 dBm -19.5 dBm

Receiver overload (see Note 4)

0 dBm -3 dBm 0 dBm -3 dBm -3 dBm

Path penalty - - 2 dB -3.3 dB -3.3 dB

Maximum receive reflectance

-12 dB -12 dB -12 dB -12 dB -12 dB



Optical path

Attenuation range - - 5 dB to 22 dB 0 dB to10.5dB

0 dB to10.5dB

Nominal reach (see Note 5)

2 m to 550 m(see Note 6)

10 km(see Note 7)

80 km

Note 12

10 km(see Note 10)

10 km(see Note 10)

Maximum dispersion - - ~1280 ps/nm - -


see Note 6 see Note 7 ~ 75 km

Note 12

see Note 10 see Note 10


see Note 6 see Note 7 ~ 88 km

Note 12

see Note 10 see Note 10


Note 2: Parameter values for SX SFP are characterized for 62.5 um 160 MHz-km MMF.

Note 3: The maximum transmit power is the lesser of Class 1 safety limits (CDRH and EN 60825) or the receiver overload.

Note 4: Received power lower / higher threshold crossed alarms are not supported for the NTTP01CF SFP.


Note 6: 2 m to 220 nm over 62.5 um core, 160 MHz-km MMF; 2 m to 550 m over 50 um core, 500 MHz-km MMF.

Note 7: 2 m to 10 km over 10 um core SMF; 2 m to 550 m over MMF.


Note 9: As per IEEE 802.3ah-2004, Table 59-4.

Note 10: 0.5 m to 10 km over G.652 SMF.

Note 11: Used for a bidirectional link over a single fiber with an upstream SFP fitted at one end of the link and a downstream SFP fitted at the other end of the link. The upstream SFP transmits at 1310 nm and receives at 1490 nm, the downstream SFP transmits at 1490 nm and receives at 1310 nm.

Note 12: When used over NDSF SMF (link engineering is required for links using the ZX SFP).

Table 7-30 (continued)Optical specifications for GE SFPs

Classification SX (see Note 2)

LX ZX 1000BaseBX10-U(see Note 11)




Electrical specificationsTable 7-31 to Table 7-38 lists the electrical specifications for the E1, E3, DS3, DS1, STM-1e and GE electrical 1000 Base-T interfaces.

Table 7-31E1 electrical specifications

Parameter Value

Line rate 2048 kbit/s +/- 50 ppm

Line code HDB3

Framing application CRC4

Impedance 75 ohm or 120 ohm (see Note 1)

Output voltage (nominal) 75 ohm: 2.37 V (mark), 0 ± 0.237 V (space)120 ohm: 3.00 V (mark), 0 ± 0.300 V (space)

Minimum output return loss 6 dB (51 kHz to 102 kHz), 8 dB (102 kHz to 3072 kHz)

Cable loss to input 0 dB to 6 dB at 1024 kHz

Minimum input return loss 12 dB (51 kHz to 102 kHz), 18 dB (102 kHz to 2048 kHz), 14 dB (2048 kHz to 3072 kHz)

Note 1: A termination panel must be used for 75 ohm E1 applications.

Table 7-32E3 electrical specifications (3xE3/DS3)

Parameter Value


Line code HDB3

Framing application G.832

Impedance 75 ohm

Output voltage (nominal) 75 ohm: 1.0 V (mark), 0 ± 0.1 V (space)

Cable loss to input 0 dB to 12 dB at 17184 kHz

Minimum input return loss 12 dB (860 kHz to 1720 kHz), 18 dB (1720 kHz to 34368 kHz), 14 dB (34368 kHz to 51550 kHz)

Table 7-33E3 electrical specifications (Transmux)

Parameter Value

Line rate 34.368 Mbps +/- 20 PPM

Line code HDB3

Framing application Clear channel



Impedance 75 ohm

Output voltage (Nominal) As per G.703

Minimum output return loss As per G.703

Cable distances 12 dB

Minimum input return loss As per G.703

Table 7-34DS1 electrical specifications

Parameter Value


Line code B8ZS, AMI

Framing application Extended Super Frame (ESF)

Impedance 100 ohm ± 5%

Pulse amplitude 2.4 V to 3.6 V

Power level In a band not wider than 3 kHz, the power level is less than 19 dBm.

Cable distances Maximum 200 m (655 ft)

Line build-out (LBO) ranges

Using NT6Q72QA/TA or NT6Q73QA/TA cables:0 to 133 ft (40.5 m), 133 ft (40.5 m) to 266 ft (81.1 m), 266 ft (81.1 m) to 399ft (121.6 m), 399 ft (121.6 m) to 533 ft (162.5 m), 533 ft (162.5 m) to 655 ft (200 m)

Table 7-35DS3 electrical specifications (3xE3/DS3)

Parameter Value


Line code B3ZS

Framing application ASYNC

Impedance 75 ohm ± 5%, unbalanced

Pulse amplitude 0.36 V to 0.85 V peak

Power level -4.7 dBm to +3.6 dBm

Cable distances Maximum 450 ft (137.1 m)

Line build-out (LBO) ranges

Using 735A cables (recommended) (NTTC03xx):0 to 255 ft (77.7 m), 255 ft (77.7 m) to 450 ft (137.1 m)

Table 7-33 (continued)E3 electrical specifications (Transmux)

Parameter Value



Table 7-38GE electrical 1000-BaseT specifications (NTTP61AAE6)

Table 7-36DS3 electrical specifications (Transmux)

Parameter Value

Line rate 44.736 Mbps +/- 20 PPM

Line code B3ZS

Framing application Clear channel and Channelized

Impedance 75 ohm

Output voltage (Nominal) As per G.703

Minimum output return loss As per G.703

Cable distances Maximum 350 ft of RG-59 cable or about 450 ft of AT&T 734A cable

Minimum input return loss As per G.703

Table 7-37STM-1e electrical specifications (NTTP60AE)

Parameter Value


Line code CMI

Impedance 75 ohm

Peak output voltage 1.00 V ± 0.1 V

Minimum output return loss 15 dB (8 MHz to 240 MHz)

Cable loss to input 0 dB to 12.7 dB at 78 MHz

Minimum input return loss 15 dB (8 MHz to 240 MHz)

Parameter Value

Symbol Rate 125 MBaud

Bits/symbol 8

Line rate 1000 Mb/s

Line code 4D-PAM5 (Pulse Amplitude Modulated 5-level symbol on each of 4 twisted pairs)

Nominal Reach 100 m

Tx/Rx Characteristics Per IEEE 802.3 clauses 40.6 and 40.8

Link Characteristics Per IEEE 802.3 clauses 40.7 (100 Ohm balanced Cat5 cable)



Environmental specificationsThe following section outlines the environmental specifications including:

• operating environment specifications

• storage and transportation specifications

Operating environment specificationsTable 7-39 outlines the 6130 operating environment specifications.

Table 7-39Operating environmental specifications for 6130 system

Attribute Condition Test method and specification

Normal operating temperature

0oC to 50oC • Telcordia GR-63 CORE (NEBS)

• ETSI EN 300 019-2-3 Class 3.1 (E)

Short term operating temperature

-5oC to 55oC

(not more than 96 consecutive hours and a total of not more than 15 days in a year)

• Telcordia GR-63 CORE (NEBS)

Normal operating humidity

5% to 90% RH

(for Telecordia GR-63-CORE, this also meets the short term relative humidity specification)


• ETSI EN 300 019-2-3 Class 3.1 (E)

Operational vibration 0.1 g from 5 to 100 Hz and return to 5 Hz at a rate of 0.1 octave/minute


Storage temperature -40oC to 70oC • ETSI EN 300 019-1-1 Class 1.2


Handling shock Packaged and unpackaged criteria (by weight) per specification


• ETSI EN 300 019-2-2 Class 2.2 and Class 2.3

Transportation vibration

Sinusoidal, random, and non-stationary per respective specifications


• ETSI EN 300 019-2-2 Class 2.3

Extended operating temperature

-40oC to 65oC (Ext. temp. equipment only)

No specification. This option of the product has been designed to withstand the specified temperature range at the shelf inlet.



Electromagnetic specificationsTable 7-40 lists the electromagnetic compatibility of the 6130 network element.

Table 7-40Electromagnetic specifications for 6130

Electromagnetic topic Attribute Test method and specification

Electromagnetic interference Radiated emissions: “Class A”

E-field: 10 kHz to 40 GHz

H-field: 10 Hz to 30 MHz

• ICES-003 (Industry Canada), Iss.3

• EN 300 386 V1.3.3

• EN 55022:1998+A1:2000+A2:2003

• FCC Part 15 Subpart B

• Telcordia GR-1089-CORE, Iss.3

Conducted emissions

10 Hz to 100 MHz

power and signal cables

• EN 300 386 V1.3.3

• EN 55022:1998+A1:2000+A2:2003


• ETS 300 132-2 V2.1.2

• Bellcore GR-499-CORE, Iss.2

RF Immunity Radiated RFI

E-field: 10 kHz to 10 GHz

10V/m

• EN 300 386 V1.3.3


• EN 55024:1998+A1:2001+A2:2003

Conducted RFI

10 Hz to 80 MHz

power and signal cables

3 Vrms (voltage)

89 dBµArms (current)

56 dBrnc (voice-band)

• EN 300 386 V1.3.3

• EN 55024:1998+A1:2001+A2:2003

• ETS 300 132-2 V2.1.2


• Bellcore GR-499-CORE, Iss.2

Operational Condition: no effect occurs when the system is exposed to the RF levels described in the specifications above.

Direct and indirect electrostatic discharge (ESD)

Direct and indirect ESD

air discharge up to 15 kV

contact discharge up to 8 kV

• EN 300 386 V1.3.3


• Telcordia GR-78-CORE

• EN 55024:1998+A1:2001+A2:2003

Operational Condition: no effect occurs when the system is exposed to the RF levels described in the specifications above.



Safety specificationsThe following section outlines the safety specifications, including:

• general commercial and regulatory

• laser emissions

General commercial and regulatoryThe 6130 complies with the safety requirements of the following specifications:

• IEC/EN 60950-1:2001+A11:2004


Laser emissionThe 6130 meets the requirements of the following specifications:

• IEC/EN 60825-1:1994+A11:1996+A2:2001+A1:2002

• IEC/EN 60825-2:2004

• FDA 21 CFR 1040.10

The 6130 is a class 1 laser product/optical fiber communications system.

Electrical fast transient (EFT) power and signal cables

4 kV - ground

1 kV - power

0.5 kV - signal

• EN 300 386 V1.3.3


• EN 55024:1998+A1:2001+A2:2003

Operational Condition: No effect occurs when the system is exposed to the EFT levels described in the specifications above.

Surge (lightning) signal cables

1.5 kV, 2/10 µs pulse

0.5 kV, 1.2/50 µs pulse

• EN 300 386 V1.3.3


• EN 55024:1998+A1:2001+A2:2003

Operational Condition: the system will continue to operate as intended immediately after exposure to the surge levels described in the specifications above.

Table 7-40 (continued)Electromagnetic specifications for 6130

Electromagnetic topic Attribute Test method and specification



Power and grounding specificationsThe following section outlines the power and grounding specifications

DC input voltage rangeThe operational input voltage range for the 6130 is -40 V dc to -57.5 V dc with DC feed (150W PSU). The 6130 is not damaged when an input voltage of correct polarity, with a value between zero and -40 V dc (minimum voltage), is applied for any period of time. The system is not damaged by a reversed polarity voltage supply, for example, zero to +57.5 V dc (the system does not function with a reversed polarity supply).

The operational input voltage range for the 6130 is -40 V dc to -72 V dc with DC feed (225W PSU). The 6130 is not damaged when an input voltage of correct polarity, with a value between zero and -40 V dc (minimum voltage), is applied for any period of time. The system is not damaged by a reversed polarity voltage supply, for example, zero to +72 V dc (the system does not function with a reversed polarity supply).

The 6130 automatically recovers when the input voltage returns to a value exceeding the minimum voltage within an acceptable period of time and without any manual intervention.

The 6130 meets the specifications listed in Table 7-41.

Table 7-41Power, grounding, and noise references

Topic References

Power • ANSI T1.315-2001, Voltage Levels for DC Powered Equipment Used in the Telecommunications Environment, 2001.

• ETS 300 132-2, Equipment Engineering (EE); Power supply interface at the input to telecommunications equipment; Part 2: Operated by direct current (dc)

• DS8171, Issue 2, 60 Hz and -48 V dc Power for DC Powered Telecommunication Equipment, Bell Canada



Grounding • ITU-T K.27, Bonding Configurations and Earthing Inside a Telecommunication Building), May 1996

• TR-NWT-000295, Bellcore Technical Reference, Isolated Ground Planes: Definition and Application to Telephone Central Offices. July 1992

• ETSI EN 300 253, Equipment Engineering (EE); Earthing and bonding of telecommunication equipment in telecommunication centres, January 1995

• NFPA70, (US National Electrical Code)

• CSA 22.1, (Canadian Electrical Code)

• Telecordia: GR-1089-CORE, Electromagnetic Compatibility and Electrical Safety, Issue 2, Revision 1, February 1999, Section 9

Noise • ANSI T1.315-2001, Voltage Levels for DC Powered Equipment Used in the Telecommunications Environment, November 2001

• DS8171, Issue 2, 600 Hz and -48 V dc Power for DC Powered Telecommunication Equipment, Bell Canada

• ETS 300 132-2, Equipment Engineering (EE); Power supply interface at the input to telecommunications equipment; Part 2: Operated by direct current (dc), September 1996

• Telecordia: GR-63-CORE, Network Equipment Building System (NEBS) Requirements (Bellcore, October 1995), Section 4.6

Table 7-41 (continued)Power, grounding, and noise references

Topic References




8-1

Ordering information and system engineering rules 8-

This chapter provides the ordering information and engineering rules for the 6130 network element. Table 8-1 lists the topics in this chapter.


Topic Page

6130 network element configuration rules

Chassis layout 8-2

Bay equipping rules 8-5

Shelf equipping rules 8-5

Site engineering recommendations 8-16

List of parts

6130 chassis and components 8-18

6130 shelf assembly kit 8-20

Tributary circuit packs & I/O Modules 8-21

Small form-factor pluggable (SFP) modules 8-23

Electrical interface hardware 8-29

E1/DS1 cable assemblies 8-30

E3/DS3 cable assemblies 8-33

STM-1e cable assemblies 8-34

Ethernet service cable assemblies 8-35

Optical fiber patch cords 8-36

OAM cable assemblies 8-39


8-2 Ordering information and system engineering rules

6130 network element configuration rulesThis section documents the 6130 network element configuration rules, including slot numbering, bay equipping rules, shelf equipping rules, and site engineering recommendations.

Chassis layoutTable 8-2 lists the circuit packs or components that can be inserted into the 6130 chassis and the corresponding slot numbers. Figure 8-1 shows the 6130 chassis layout.

Power and earthing cable assemblies 8-41

Software load 8-42

Right to use licenses 8-43

Site Manager for 6100 8-43

Engineering and support services 8-44

6130 documentation 8-44

Change application procedures 8-46

RoHS compliant equipment 8-47

Ordering procedures

Ordering 6130 chassis, circuit packs, and software 8-48

Ordering cables, documentation, and services 8-65

Table 8-2Chassis components

Circuit pack or component Slot number Note

2x155/622M aggregate circuit pack Slot 6 1, 2, 6

1x155/622M aggregate circuit pack Slots 6, 7 1, 2, 6

1x2.5G aggregate circuit pack Slots 6, 7 1, 2, 6

1x2.5G+4x155M/2x622M aggregate circuit pack

Slots 6, 7 1, 2, 6

8xETH circuit pack Slots 4, 5, 8, 9 2

Table 8-1 (continued)Topics in this chapter

Topic Page


Ordering information and system engineering rules 8-3

4x10/100BT+4x100FX L1 circuit pack Slots 4, 5, 8, 9 2, 6

4x10/100BT+4x100FX L1 622M circuit pack

Slots 4, 5, 8, 9 2, 6

8xGE EoPDH L2 circuit pack Slot 4, 8 2, 6, 13

2xGE circuit pack Slots 4, 5, 8, 9 2, 6

2xGE+8x10/100BT L1 1.2G circuit pack Slots 4, 5, 8, 9 2, 6

L2PA622M circuit pack (name on circuit pack faceplate label is 2xGE/FX+8x10/100BT L2 622M)

Slots 4, 5, 8, 9 2, 6, 7

L2PA1G2 circuit pack (name on circuit pack faceplate label is 2xGE/FX+8x10/100BT L2 1G2)

Slots 4, 5, 8, 9 2, 6, 8

28xE1/DS1 circuit pack Slots 4, 5, 8, 9 2

63xE1/DS1circuit pack Slots 4, 5, 8, 9 2

28xE1/DS1(W/P) circuit pack Slots 4, 5, 8, 9 2, 3

Transmux circuit pack Slots 4, 5, 8, 9 2

3xE3/DS3 circuit pack Slots 4, 5, 8, 9 2

3xE3/DS3(W/P) circuit pack Slots 4, 5, 8, 9 2, 4

2x155M circuit pack Slots 4, 5, 8, 9 2, 6

2x622M/8x155M circuit pack Slots 4, 5, 8, 9 2, 6, 9, 10, 11, 12

2x622M/8x155M Rev2 (Low Power) circuit pack

Slots 4, 5, 8, 9 2, 6, 10, 11

Power supply unit(DC)

Slots 1, 3 2, 5

OAM circuit pack Slot 2 2

Fan module Slot 10 2

SFP interfaces Slots 4, 5, 6, 7, 8, 9 2, 6

28xE1/DS1 1+1 I/O module I/O slots 4, 8 2, 3

Table 8-2 (continued)Chassis components




84xE1/DS1 1:N I/O module I/O slots 4 + 8 2, 3

3xE3/DS3 1+1 I/O module I/O slots 4, 8 2, 4

Note 1: Refer to Shelf equipping rules on page 8-5 for list of supported configurations (line rate and equipment redundancy) with the aggregate circuit packs.

Note 2: This is a field replaceable unit.

Note 3: The 28xE1/DS1(W/P) circuit pack requires the use of the 28xE1/DS1 1+1 I/O module or the 84xE1/DS1 1:N I/O module. Refer to I/O Modules on page 4-55 for the slot population rules of the 28xE1/DS1(W/P) circuit pack and associated I/O modules.

Note 4: The 3xE3/DS3(W/P) circuit pack requires the use of the 3xE3/DS3 1+1 I/O module. Refer to I/O Modules on page 4-55 for the slot population rules of the 3xE3/DS3(W/P) circuit pack and associated I/O module.

Note 5: Two PSU circuit packs are equipped in the shelf in normal operation for equipment redundancy and DC power feed redundancy.

Note 6: SFP modules must be ordered separately.

Note 7: Up to two L2PA622M circuit packs can be equipped per 6130 NE (with 150W PSU.

Note 8: Up to three L2PA1G2 circuit packs can be equipped per 6130 NE (with 150 PSU and 1x2.5G agg. card).

Note 9: Up to three 2x622M/8x155M (NT6Q18AAE5) circuit packs can be equipped per 6130 NE equipped with the 1x2.5G aggregate cards and 150W PSU. Up to two 2x622M/8x155M (NT6Q18AAE5) circuit packs can be equipped per 6130 NE equipped with the 1x2.5G+4x155M/2x622M aggregate cards and 150W PSU


Note 11: A maximum of 8 STM-1/OC-3 ports or 2 STM-4/OC-12 ports or any other combination of STM-1/OC-3 and STM-4/OC-12 ports (totaling 1.2Gb/s worth of bandwidth) can be simultaneously active on a shelf equipped with redundant 1x155/622M aggregate cards.


Note 13: The 225W PSU is required when 8xGE EoPDH L2 card is equipped in the shelf.

Table 8-2 (continued)Chassis components




Figure 8-16130 chassis layout

Bay equipping rulesThis section provides equipping rules for 6130 installation in a bay. The 6130 shelf can be mounted in a variety of telecommunications equipment bays, including 19”, 21”, and 23” standard bays.

Refer to Table 8-3 for 6130 equipment rack space requirements.

Shelf equipping rulesThis section lists the equipping rules for the 6130 shelf.

For more information on the 6130 chassis, refer to Chassis on page 4-4.

Table 8-36130 equipment rack space requirements

Equipment Rack units required

6130 shelf 4U

6130 shelf with PDH protection I/O modules 5U

75 ohm BNC Termination Panel (NT6Q71EA) 1U



Engineering rules1 Each shelf at an 6130 site is a stand-alone network element.2 Each shelf requires one or two aggregate circuit pack(s) depending on the

node redundancy mode for this application. Four types of aggregate circuit packs are available in 6130 Rel 5.0 and the following shelf configurations are supported:— non-redundant configuration with STM-1/4/OC-3/12 interfaces:

– one 2x155/622M aggregate circuit pack is required in slot 6

– one filler panel in slot 7

— redundant configuration with STM-1/4/OC-3/12 interfaces:

– two 1x155/622M aggregate circuit packs are required in slots 6 and 7 (1+1 equipment protection)

— redundant configuration with STM-4/16/OC-12/48 interfaces:

– two 1x2.5G aggregate circuit packs are required in slots 6 and 7 (1+1 equipment protection)

— redundant configuration with STM-4/16/OC-12/48 line interfaces and STM-1/4/OC-3/12 tributary interfaces on the aggregate cards:

– two 1x2.5G+4x155M/2x622M aggregate circuit packs are required in slots 6 and 7 (1+1 equipment protection)

Attention: Only the configurations listed previously are supported for the aggregate circuit packs. Other configurations (e.g. mix of 155/622M and 2.5G aggregate circuit packs in same shelf, etc.) are not supported.

The SFPs interfaces must be ordered separately.

3 The node capability is provisioned to either STM-1/OC-3 or STM-4/OC-12 or STM-16/OC-48 line rate during initial commissioning from the Initialize Node Parameters WUI application. The two SFP interfaces of the aggregate circuit pack(s) line ports are operating at the rate of the node capability value. The appropriate SFPs (i.e. STM-1/OC-3 or STM-4/OC-12 or STM-16/OC-48 rate) must be selected for the aggregate circuit pack(s).— the 1x155/622M aggregate cards support in service line rate upgrades

(STM-1/OC-3 to STM-4/OC-12).

— the 1x2.5G aggregate cards support in service line rate upgrades (STM-4/OC-12 to STM16/OC-48).

— the 1x2.5G+4x155M/2x622M aggregate cards support in service line rate upgrades (STM-4/OC-12 to STM-16/OC-48).



Attention: In service line rate upgrades are not supported with the 2x155/622M aggregate circuit pack.

4 Each shelf requires the following components:— two power supply units (one in slot 1 and one in slot 3)

— one OAM circuit pack in slot 2

— one filler panel for each slots 4, 5, 8 and 9 (if no tributary circuit packs are used)

— one filler panel for each I/O slots 4, 8 (if no I/O modules are used)

— one fan module in slot 10

5 Each shelf is capable of supporting up to four tributary circuit packs (slots 4, 5, 8 and 9).

Attention: When 2 or more of the L2PA622M and/or L2PA1G2 and/or 2x622M/8x155M (NT6Q18AAE5) circuit packs are used in the same 6130 shelf, the total power requirement of the shelf may exceed the 6130 150W PSU capacity. Please refer to Shelf equipping rules on page 8-5, step 19 to determine shelf power requirements.

Attention: For NEBS Radiated Emissions compliancy, in 6130 deployments which include one or more DS-1 I/O cards (NT6Q44AAE5), only one (1) NT6Q18AAE5 circuit pack per 6130 shelf is supported and it must be installed in tributary slot #5.

6 Each shelf is capable of supporting up to two I/O modules (I/O slots 4 and 8)

7 No fiber slack storage is provided for fibers terminating on the 6130 shelf. Cable relief off the shelf can be handled using the routing brackets provided with the 6130 Assembly Kit.

8 You can only replace (spare) a circuit pack with a circuit pack with the same product engineering code (PEC).

9 1+1 MSP/APS, SNCP/UPSR, and unprotected traffic protection schemes are available. The STM-1/4/16/OC-3/12/48 interfaces must be provisioned in a MSP/APS group for 1+1 MSP/APS protection, or in unprotected mode for SNCP/UPSR or unprotected configuration.

10 MS-SPRing/BLSR traffic protection is available. The equipping rules for MS-SPRing/BLSR ring protection scheme are as follows:a. MS-SPRing/BLSR protection is supported only on the STM-16/OC-48

ports of the 1x2.5G+4x155/2x622M aggregate cards.b. The protection switch mode is revertive, bidirectional.



11 Only the 8xETH, 4x10/100BT+4x100FX L1, 2xGE, 2xGE+8x10/100BT L1 1.2G, L2PA622M, L2PA1G2, 28xE1/DS1, 63XE1/DS1, 28xE1/DS1(W/P), 3xE3/DS3, 3xE3/DS3(W/P), 2x155M 2x622M/8x155M, 8xGE EoPDH L2 (Slot 4&5, 8&9) and Transmux circuit packs can be inserted in the tributary slots (slots 4, 5, 8, 9).

Attention: When the tributary slots are not equipped with a circuit pack, a filler panel must be installed.

12 Only the 28xE1/DS1 1+1 I/O, 84xE1/DS1 1:N I/O and 3xE3/DS3 1+1 I/O modules can be inserted in the I/O module slots (I/O slots 4, 8).

Attention: When the I/O slots are not equipped with a I/O module, a filler panel must be installed.

13 If the node redundancy mode is provisioned to redundant, then some circuit packs are not supported. Table 8-4 lists the PEC codes that are supported for the non-redundant and redundant configurations.



Table 8-4PEC codes supported for non-redundant and redundant configurations

Description PEC supported for non-redundant configuration (see Note 1)

PEC supported for redundant configuration

2x155/622M aggregate circuit pack

1x155/622M aggregate circuit pack (see notes 2, 5)

1x2.5G aggregate circuit pack (see notes 3, 5)

1x2.5G+4x155M/2x622M aggregate circuit pack (see notes 4, 5)

6130 System Kits NT6Q60AA,NT6Q60AAE5, NT6Q60ABE5, NT6Q60AME5


NT6Q60ABE5, NT6Q60AME5, NT6Q60BAE5 (Ext Temp)

OAM circuit pack NT6Q43AA, NT6Q43AAE5, NT6Q43ABE5

NT6Q43BAE5

NT6Q43ABE5, NT6Q43BAE5

8xETH circuit pack NT6Q13AB, NT6Q13ABE5, NT6Q13ACE5


NT6Q13ACE5

8xGE EoPDH L2 NA NT6Q23AAE5

Transmux NT6Q12NAE5 NT6Q12NAE5 NA NT6Q12NAE5

2xGE circuit pack NT6Q20AA, NT6Q20AAE5, NT6Q20ABE5


NT6Q20ABE5, NT6Q20BAE5 (Ext Temp)

28xE1/DS1 circuit pack

NT6Q10AA, NT6Q10AAE5, NT6Q10ABNT6Q10ABE5


NT6Q10ABE5



3xE3/DS3 circuit pack

NT6Q12AA, NT6Q12AAE5, NT6Q12ABE5NT6Q12ACE5


NT6Q12ABE5, NT6Q12ACE5

2x155M circuit pack NT6Q17AA, NT6Q17AAE5, NT6Q17ACE5

NT6Q17ACE5

2x155/622M Aggregate circuit pack

NT6Q45AA, NT6Q45AAE5

N/A

1x155/622M Aggregate circuit pack

N/A NT6Q46AAE5 N/A N/A

1x2.5G Aggregate circuit pack

N/A N/A NT6Q47AAE5 N/A

1x2.5G+4x155M/2x622M Aggregate circuit pack

N/A N/A N/A NT6Q48AAE5

L2PA1G2 circuit pack

Not Supported (see Note 6) NT6Q21GAE5, NT6Q21GBE5

2xGE+8x10/100BT L1 1.2G

Not Supported (see Note 6) NT6Q22AAE5

2x622M/8x155M Not Supported NT6Q18AAE5, NT6Q18ABE5 (see Note 7)

NT6Q18AAE5, NT6Q18ABE5

4x10/100BT+4x100FX L1 circuit packs

NT6Q13MAE5, NT6Q13MBE5

Table 8-4 (continued)PEC codes supported for non-redundant and redundant configurations









4x10/100BT+4x100FX L1 622M circuit packs


L2PA622M circuit pack

NT6Q21AAE5, NT6Q21ABE5

28xE1/DS1(W/P) NT6Q10MAE5

63XE1/DS1 NT6Q11AAE5

3xE3/DS3(W/P) NT6Q12MAE5

28xE1/DS1 1+1 I/O Module

NT6Q44AAE5

84xE1/DS1 1:N I/O Module

NT6Q44CAE5

3xE3/DS3 1+1 I/O Module

NT6Q44BAE5

DC PSU circuit pack NT6Q40AA, NT6Q40AAE5 NT6Q40BAE5 (Ext Temp)










14 The STM-1/4/16/OC-3/12/48, 100FX and GE interfaces use small form-factor pluggable (SFP) modules. Each active port requires a SFP module, which are ordered separately. Dust covers for the SFP positions are included with the circuit packs, therefore, dust covers do not need to be ordered for unequipped ports. — A maximum of 2 SFP modules are required for each 2x155M, 2xGE,

2xGE+8x10/100BT L1 1.2G, L2PA622M, L2PA1G2 circuit pack

— a maximum of one SFP module is required for each 1x155/622M, 1x2.5G aggregate cards.

— A maximum of 4 SFP modules are required for each 4x10/100BT+4x100FX L1 and 8xGE EoPDH L2 circuit pack.

— A maximum of 5 SFP modules are required for each 1x2.5G+4x155M/2x622M aggregate card.

— A maximum of 8 SFP modules are required for each 2x622M/8x155M circuit pack.

AC PSU circuit pack NT6Q41AAE5

Fan circuit pack NT6Q42AA, NT6Q42AAE5, NT6Q42ABE5 (Hinged), NT6Q42BAE5 (Ext Temp)

Note 1: The shelf is equipped with one 2x155/622M aggregate circuit pack for the non-redundant configuration.

Note 2: The shelf is equipped with two 1x155/622M aggregate circuit packs for the redundant configuration.

Note 3: The shelf is equipped with two 1x2.5G aggregate circuit packs for the redundant configuration.

Note 4: The shelf is equipped with two 1x2.5G+4x155M/2x622M aggregate Standard or Extended Temperature circuit packs for the redundant configuration.

Note 5: The alarm “Circuit pack below baseline” will be raised when a circuit pack that is not supported is inserted in an 6130 shelf equipped with redundant aggregate circuit packs. In this case, the circuit pack below baseline will not carry traffic.

Note 6: The alarm “Circuit pack below baseline” will not be raised when the L2PA1G2 circuit pack or 2xGE+8x10/100BT L1 1.2G circuit pack is inserted in an 6130 shelf equipped with either the 2x155/622M or 1x155/622M aggregate circuit pack.

Note 7: In redundant configuration with the 1x155/622M aggregate cards, only ports number 1, 2, 3 & 4 of the 2x622M/8x155M circuit pack are available to carry traffic.










15 Table 8-5 lists the SFP PEC codes that are supported for the circuit packs.

Table 8-5SFP PEC codes supported for circuit packs

Interface circuit pack SFP Line rate SFP PEC codes supported

8xGE EoPDH L2 (refer to Note 2) GE NTTP06AF, NTTP01CF, NTTP58BD, NTTP59BD, NTTP61AAE6, NTTP01AFE6

2x155/622M Aggregate circuit pack and 1x155/622M Aggregate circuit pack

STM-1/OC-3 NTTP02AD, NTTP02CD, NTTP02ED, NTTP02FD, NTTP02FF, NTTP04CF, NTK590xH

STM-4/OC-12 NTTP04CF, NTTP05EF, NTTP05FF, NTK590xH

1x2.5G Aggregate circuit pack STM-4/OC-12 NTTP04CDE6, NTK590xH

STM-16/OC-48 NTTP03BF, NTTP03CF, NTTP03EF, NTTP03FF, NTK585xx, NTK590xH

1x2.5G+4x155M/2x622M Aggregate circuit pack (Standard Temperature)

STM-1/OC-3 NTTP02AD, NTTP02CD, NTTP02ED, NTTP02FD, NTTP02FF, NTTP04CDE6, NTTP04CF, NTK590xH

STM-4/OC-12 NTTP04CDE6, NTTP04CF, NTTP05EF, NTTP05FF, NTK590xH

STM-16/OC-48 NTTP03BF, NTTP03CF, NTTP03EF, NTTP03FF, NTK585xx, NTK590xH

1x2.5G+4x155M/2x622M Aggregate circuit pack (Extended Temperature) (see Note 3)

STM-1/OC-3 NTTP02AD, NTTP02CD, NTTP02ED, NTTP02FD, NTTP04CDE6

STM-4/OC-12 NTTP04CDE6, NTTP05EF

STM-16/OC-48 NA

2x155M tributary circuit pack STM-1/OC-3 NTTP02AD, NTTP02CD, NTTP02ED, NTTP02FD, NTTP02FF, NTTP04CDE6, NTTP09BD, NTTP10BD, NTTP60AE (see Note 1)

2x622M/8x155M tributary circuit pack STM-1/OC-3 NTTP02AD, NTTP02CD, NTTP02ED, NTTP02FD, NTTP02FF, NTTP04CDE6, NTTP04CF, NTK590xH, NTTP60AE (see Note 1)

STM-4/OC-12 NTTP04CDE6, NTTP04CF, NTTP05EF, NTTP05FF, NTK590xH



16 The 28xE1/DS1 circuit pack, the 28xE1/DS1 1+1 I/O module and the 84xE1/DS1 1:N I/O module require the appropriate I/O interface cabling. The default impedance for the E1/DS1 interfaces is 120/100 ohm. The E1/DS1 interface uses a 64-pin Telco connector. Conversion for E1 services to 75 ohm unbalanced interface can be achieved using the 75 ohm BNC termination panel.

17 In a rack mount installation, it is recommended to install the 75 ohm BNC termination panel directly below the 6130 shelf. If more than one termination panel is required (for converting impedance of ports on the 28xE1/DS1 circuit pack, 28xE1/DS1 1+1 I/O module and the 84xE1/DS1 1:N I/O module), stack the termination panels below the 6130 shelf.

4x10/100BT+4x100FX L1 and 4x10/100BT+4x100FX L1 622M Ext Temp circuit pack

100FX NTTP02AD, NTTP08SD, NTTP09BD, NTTP10BD

(These SFP supports Ext Temp conditions)

2xGE circuit pack GE NTTP01AF, NTTP01AFE6, NTTP01CF, NTTP06AF, NTTP58BD, NTTP59BD, NTTP61AAE6

2xGE Ext Temp circuit pack GE NTTP01AFE6, NTTP01CFE6, NTTP06AFE6, NTTP58BD, NTTP59BD, NTTP61AAE6, NTTP07FF, NTTP07FFE6

L2PA622M circuit pack 100FX NTTP02AD, NTTP08SD, NTTP09BD, NTTP10BD

GE NTTP01AF, NTTP01AFE6, NTTP01CF, NTTP06AF, NTTP58BD, NTTP59BD, NTTP61AAE6, NTTP07FF, NTK591xB

L2PA1G2 circuit pack 100FX NTTP02AD, NTTP08SD, NTTP09BD, NTTP10BD

GE NTTP01AF, NTTP01AFE6, NTTP01CF, NTTP06AF, NTTP58BD, NTTP59BD, NTTP61AAE6, NTTP07FF, NTK591xB

2xGE+8x10/100BT L1 1.2G circuit pack GE NTTP01AF, NTTP01CF, NTTP06AF, NTTP58BD, NTTP59BD, NTTP61AAE6

Note 1: The NTTP60AE electrical SFP is supported only for the STM-1 interface.

Note 2: The SFP support is independent of the RoHS compliancy. E6 suffix can be disregarded for compatibility purposes.

Note 3: This card also supports the Standard Temperature SFPs if the shelf is used in Standard Temperature conditions.

Table 8-5 (continued)SFP PEC codes supported for circuit packs

Interface circuit pack SFP Line rate SFP PEC codes supported



18 The 63xE1/DS1circuit pack requires the appropriate I/O interface cabling. The impedance for the E1/DS1 interfaces of the 63xE1/DS1circuit pack is configurable from the facility WUI application to either 75 or 120 Ohms (75 Ohms and 120 Ohms cables are available). The E1/DS1 interfaces of the 63xE1/DS1circuit pack use two 160-pin Telco connectors.

19 The 6130 shelf power requirements (including aggregate circuit packs, tributary circuit packs, I/O modules, OAM module and Fan unit) must not exceed 150W when the 6130 150W PSU is used or 225W when the 6130 225W PSU is used. For each 6130 shelf, determine if the total power requirement exceeds the capability of the PSU by adding the power consumption of all circuit packs and component equipped in the shelf. If the total power calculated for the shelf exceeds the capability of the PSU, then one or more tributary circuit pack(s) will need to be moved to another 6130 shelf at this site. Use to calculate the shelf power requirements.

Table 8-66130 shelf power requirements

Shelf Component Power (W) consumption

Qty Total

8xGE EoPDH L2 55

Transmux 15



1x2.5G aggregate circuit pack 28

1x2.5G+4x155M/2x622M aggregate circuit pack

34

1x2G5+4x155M/2x622MAgg (Ext Temp) circuit pack

30

OAM circuit pack (Std Temp) 6

OAM circuit pack (Ext Temp) 7

Fan module (Std Temp) 12

Fan module (Ext Temp) 12

8xETH circuit pack 7

8x10/100BT L1 Circuit Pack Ext Temp 9

4x10/100BT+4X100FX L1 circuit pack 10.5

4x10/100BT+4X100FX L1 622M circuit pack

12.5

2xGE circuit pack 8



Site engineering recommendationsConsider the following site engineering recommendations when planning a network deployment.

1 Breaker interface panels or fuse panels should be installed at the top of the bay.

2xGE (Ext Temp) circuit pack 15

2xGE+8x10/100BT L1 circuit pack 15

L2PA622M circuit pack 28

L2PA1G2 circuit pack 25

28xE1/DS1 circuit pack 7

28xE1/DS1 Circuit Pack (Ext Temp) circuit pack

10

63xE1/DS1circuit pack 9

28xE1/DS1(W/P) circuit pack 6

3xE3/DS3 circuit pack 7

3xE3/DS3 Circuit Pack (Ext Temp) circuit pack

7

3xE3/DS3(W/P) circuit pack 5

2x155M circuit pack 8

2x622M/8x155M circuit pack 25

2x622M/8x155M Rev2 circuit pack 16

I/O 3xE3/DS3 1+1 circuit pack 2

I/O 28xE1/DS1 1+1 circuit pack 2

I/O 84xE1/DS1 1:N circuit pack 3

Total:

Note 1: The PSU circuit pack is not listed in the table because the power consumption of the PSU circuit packs is excluded from the 150W or 225W maximum capacity. The 150W or 225W maximum capacity is calculated by adding the power consumption of the aggregate circuit packs, tributary circuit packs, I/O modules, OAM module and Fan unit.

Table 8-6 (continued)6130 shelf power requirements

Shelf Component Power (W) consumption

Qty Total



2 Recommendation is to use 2x6 Amp breakers or fuses for the dual DC power feeds for each 6130 chassis equipped with the 150W PSUs.

3 Recommendation is to use 2x7.5 Amp breakers or fuses for the dual DC power feeds for each 6130 chassis equipped with the 225W PSUs.

4 Recommendation is to leave 1U space between 6130 shelves when installed in the same rack to provide added air flow through the equipment.

5 Optical fiber cables should be routed on the right side of the bay.6 No fiber slack storage is provided for fibers terminating on the 6130 shelf.

Use external fiber management drawers to store excess fiber cable.7 Right routing E1 or DS1 cables must be used for the following applications:

— 28xE1/DS1 circuit pack

— 63xE1/DS1circuit pack

— 28xE1/DS1 1+1 I/O module equipped in the 6130 I/O slot 8

— 84xE1/DS1 1:N I/O module - for the 3 E1/DS1 connectors to the right:




8 Left routing E1 or DS1 cables must be used for the following applications:— 28xE1/DS1 1+1 I/O module equipped in the 6130 I/O slot 4

— 84xE1/DS1 1:N I/O module - for the 3 E1/DS1 connectors to the left:




9 E3/DS3 electrical interface cable should be routed on the right side of the bay for the 3xE3/DS3 circuit pack and for the 3xE3/DS3 1+1 I/O module installed in I/O slot 8.

10 E3/DS3 electrical interface cable should be routed on the left side of the bay for the 3xE3/DS3 1+1 I/O module installed in I/O slot 4.

11 The Ethernet cables should be routed on the right side of the bay for the 8xETH, 4x10/100BT+4x100FX L1, 4x10/100BT+4x100FX L1 622M, 2xGE+8x10/100BT L1 1.2G, L2PA622M, L2PA1G2 and 8xGE EoPDH L2 circuit packs.

12 Install power cables on the left side of the 6130 bay.13 Install OAM cables (for Alarm Input, Alarm Output, M1/F1 and ESI ports)

on the left side of the 6130 bay. The Ethernet cables should be routed on the left side of the bay for the LAN port of the OAM circuit pack for DCN access.



List of partsThis section provides the orderable codes available for the 6130 product. Use these tables with the ordering procedures (Procedure 8-1 on page 8-48 through Procedure 8-2 on page 8-65) to make sure that a complete and accurate bill of material is created.

6130 chassis and componentsTable 8-8 lists the ordering codes for the chassis and components. For rules on equipping the 6130 chassis, refer to Shelf equipping rules on page 8-5.

Table 8-86130 chassis and components

Description Order code Notes

6130 System Kit

6130 DC System; Chassis, Dual DC PSU, OAM circuit pack, Fan, two top I/O Fillers and 19” flange

NT6Q60ABE5 1

6130 System; Chassis, OAM circuit pack, Fan, two top I/O Fillers and 19” flange

NT6Q60AME5 2

6130 DC System Ext Temp; Chassis, OAM circuit pack, Fan, two top I/O Fillers and 19” flange

NT6Q60BAE5 12

Aggregate circuit pack Kit

2x155/622M Aggregate circuit pack with Rel 1.0 software NT6Q66AA 3

2x155/622M Aggregate circuit pack with Rel 2.0 software NT6Q66ABE5 3

1x155/622M Aggregate circuit pack with Rel 2.0 software NT6Q67AAE5 3

1x2.5G Aggregate circuit pack with Rel 2.0 software NT6Q68AAE5 3

2x155/622M Aggregate circuit pack with Rel 3.0 software NT6Q66ACE5 3

1x155/622M Aggregate circuit pack with Rel 3.0 software NT6Q67ACE5 3

1x2.5G Aggregate circuit pack with Rel 3.0 software NT6Q68ACE5 3

2x155/622M Aggregate circuit pack with Rel 4.0 software NT6Q66ADE5 3

1x155/622M Aggregate circuit pack with Rel 4.0 software NT6Q67ADE5 3

1x2.5G Aggregate circuit pack with Rel 4.0 software NT6Q68ADE5 3

1x2.5G Aggregate, no DCC circuit pack with Rel 4.0 software NT6Q68MDE5 3

1x2.5G+4x155M/2x622M Aggregate circuit pack with Rel.4.0 software

NT6Q69ADE5 3

2X622M Aggregate circuit pack with R4.1 software NT6Q66AEE5 3

1x622M Aggregate circuit pack with R5.0 software NT6Q67AEE5 3



1x2488M Aggregate circuit pack with R4.1 software NT6Q68AEE5 3

1x2488M Aggregate, no DCC circuit pack with R4.1 software NT6Q68MEE5 3

1x2488M/2x622M/4x155M Aggregate circuit pack with R5.0 software

NT6Q69AEE5 3

1x2488M/2x622M/4x155M Aggregate, Ext Temp circuit pack with R5.0 software

NT6Q69BAE5 3

Power Supply Unit and OAM circuit pack

6130 DC Power Supply Unit 150W single-feed NT6Q40AA 4, 5

6130 DC Power Supply Unit 150W single-feed NT6Q40AAE5 4, 5

6130 AC Power Supply Unit 150W NT6Q41AAE5 5

6130 DC PSU Ext Temp 225W NT6Q40BAE5 5

6130 Standard OAM, Ext Temp Circuit Pack NT6Q43BAE5 6

OAM circuit pack NT6Q43ABE5 6

Fillers and Fan modules

6130 Fan Tray with Filter NT6Q42AA 7

6130 Fan Tray with Filter NT6Q42AAE5 7

6130 Hinged Fan Tray with Filter NT6Q42ABE5 7

6130 Fan Tray, Ext Temp (with Filter) NT6Q42BAE5

Filler Panel for tributary circuit pack slot NT6Q70AA, 8

Filler Panel for tributary circuit pack slot NT6Q70AAE6 8

Filler Panel for top I/O slot NT6Q70ADE6 9

6130 Top Right IO Filler Panel NT6Q70AHE6 13

6130 Top Left IO Filler Panel NT6Q70AIE6 13

Filler Panel for aggregate circuit pack slot NT6Q70AE 10

Filler Panel for aggregate circuit pack slot NT6Q70AEE6 10

Air Filter NT6Q70DAE6 11

Table 8-8 (continued)6130 chassis and components




6130 shelf assembly kitThe 6130 system kits described in Table 8-8 on page 8-18 include shelf mounting brackets for a 19 in. rack. For 21 in. or 23 in. standard bay installations, separate brackets can be obtained with the 6130 shelf assembly kit. It is recommended to order one 6130 shelf assembly kit, as listed in Table 8-9, for each NE.

Note 1: The 6130 system kit contains a chassis equipped with two DC power supply unit, one OAM circuit pack, one fan module with filter, two top I/O filler panels and 19” flange.

Note 2: The NT6Q60AME5 system kit does not include PSU units. Order this kit plus AC PSUs for applications that require AC power.

Note 3: SFPs for the STM-1/4/16/OC-3/12/48 interfaces need to be ordered separately.

Note 4: The DC PSU provides a single-feed 6130 shelf power termination up to 6 A.

Note 5: The PSU can be ordered as spare or replacement.

Note 6: The OAM circuit pack can be ordered as spare or replacement.

Note 7: Each fan module consists of four fans. This module can be ordered as spare or replacement.

Note 8: An empty tributary circuit pack slot must be covered with a tributary filler panel. The tributary filler panel must be ordered separately.

Note 9: The two top I/O slots must be covered with top I/O filler panels. Two top I/O filler panels come equipped with the chassis, but can be ordered separately as spare or replacement.

Note 10: If a 2x155/622M aggregate circuit pack is equipped in slot 6, then the aggregate slot 7 must be covered with a aggregate filler panel. The aggregate filler panel must be ordered separately.

Note 11: The air filter is part of the fan module which is included with the 6130 system kit. The air filter can be ordered as spare or replacement.

Note 12: The DC Power Supply is 225W Ext Temp, OAM is Ext Temp and Fan Tray is Ext Temp.

Note 13: The two top I/O slots must be covered with I/O filler panels. Two I/O filler panels come equipped with the chassis, but can be ordered separately as spare or replacement.

Table 8-96130 shelf assembly kit


6130 shelf assembly kit - cable routing brackets, rack mounting screws, 21” and 23” flange, cage nuts, earthing cable

NT6Q70CA 1, 2

6130 shelf assembly kit - cable routing brackets, rack mounting screws, 21” and 23” flange, cage nuts, earthing cable

NT6Q70CAE6 1, 2

6130 - 19” Mounting Kit - brackets, screws & cage nuts NT6Q70CBE6

Note 1: This shelf assembly kit provides installation brackets for the 6130 chassis. Included in the kit are cable routing brackets, rack mounting screws, 21” and 23” flange, cage nuts and earthing cable.

Note 2: It is recommended to have an 6130 shelf assembly kit for each 6130 shelf installation.

Table 8-8 (continued)6130 chassis and components




Tributary circuit packs & I/O ModulesTable 8-10 provides a list of all the circuit packs that can be inserted into the tributary slots of the 6130 chassis.

Table 8-11 provides a list of all the I/O modules that can be inserted into the I/O slots of the 6130 chassis.

For rules on equipping the shelf, refer to Shelf equipping rules on page 8-5.

Table 8-10Circuit packs for tributary slots


8xETH Circuit Pack NT6Q13ACE5 1

8xETH Circuit Pack (Ext Temp) NT6Q13BAE5 1

4x10/100BT+4x100FX L1 Circuit Pack NT6Q13MAE5, 1, 2

4x10/100BT+4x100FX L1 Circuit Pack NT6Q13MBE5 1, 2

4x10/100BT+4x100FX L1 622M Circuit Pack NT6Q14BAE5 1, 2

2xGE Circuit Pack NT6Q20ABE5 1, 2

2xGE Circuit Pack (Ext Temp) NT6Q20BAE5 1, 2

2xGE+8x10/100BT L1 1.2G NT6Q22AAE5 1, 2

L2PA622M Circuit Pack NT6Q21AAE5, 1, 2, 3

L2PA622M Circuit Pack NT6Q21ABE5 1, 2, 3

L2PA1G2 Circuit Pack NT6Q21GAE5, 1, 2, 4

L2PA1G2 Circuit Pack NT6Q21GBE5 1, 2, 4

28xE1/DS1 Circuit Pack NT6Q10AB 1

28xE1/DS1 Circuit Pack (Rev2) NT6Q10ABE5 1

28xE1/DS1 Circuit Pack (Ext Temp) NT6Q10BA 1

28xE1/DS1 Circuit Pack (Ext Temp) NT6Q10BAE5 1

63xE1/DS1Circuit Pack NT6Q11AAE5 1

28xE1/DS1(W/P) Circuit Pack NT6Q10MAE5 1

3xE3/DS3 Circuit Pack NT6Q12ABE5 1

3xE3/DS3 Circuit Pack NT6Q12ACE5 1

3xE3/DS3 Circuit Pack (Ext Temp) NT6Q12BAE5 1

3xE3/DS3(W/P) Circuit Pack NT6Q12MAE5 1



2x155M Circuit Pack NT6Q17ACE5 1, 2

2x622M/8x155M Circuit Pack NT6Q18AAE5 1, 2, 5, 6, 7

2x622M/8x155M Rev2 (Low Power) Circuit Pack NT6Q18ABE5 1, 2, 6

Transmux Circuit Pack with Trib Protection NT6Q12NAE5 1

8xGE EoPDH L2 NT6Q23AAE5 2, 8

Note 1: Up to four tributary circuit packs can be inserted into the 6130 chassis.

Note 2: SFPs for the STM-1/4/OC-3/12, 100FX and GE interfaces need to be ordered separately.

Note 3: Up to two L2PA622M circuit packs can be equipped per 6130 NE.

Note 4: Up to three L2PA1G2 circuit packs can be equipped per 6130 NE.

Note 5: Up to three 2x622M/8x155M (NT6Q18AAE5) circuit packs can be equipped per 6130 NE equipped with the 1x2.5G aggregate cards. Up to two 2x622M/8x155M (NT6Q18AAE5) circuit packs can be equipped per 6130 NE equipped with the 1x2.5G+4x155M/2x622M aggregate cards.



Note 8: Up to two can be equipped per 6130 NE.

Table 8-11I/O Modules for the 6130 I/O slots


28xE1/DS1 1+1 I/O NT6Q44AAE5 1

3xE3/DS3 1+1 I/O NT6Q44BAE5 2

84xE1/DS1 1:N I/O NT6Q44CAE5 3

Note 1: The 28xE1/DS1 1+1 I/O module is required with the 28xE1/DS1(W/P) circuit packs for 1+1 equipment protection.

Note 2: The 3xE3/DS3 1+1 I/O module is required with the 3xE3/DS3(W/P) or Transmux circuit pack for 1+1 equipment protection.

Note 3: The 84xE1/DS1 1:N I/O module is required with the 28xE1/DS1(W/P) circuit pack for 1:N equipment protection.

Table 8-10 (continued)Circuit packs for tributary slots




Small form-factor pluggable (SFP) modulesTable 8-12 lists the small form-factor pluggable modules. lists the STM-16/OC-48 DWDM small form-factor pluggable module.

Table 8-12Small form-factor pluggable (SFP) modules

Description Order Code Notes

STM-1/OC-3 SFPs

STM-1/OC-3 SR-0 (Multimode) 1310 nm Enhanced SFP Module NTTP02AD 1, 2, 5

STM-1/OC-3 IR1/S1.1 1310 nm XCT Enhanced SFP Module NTTP02CD 1, 2

STM-1/OC-3 IR1/S1.1 1310 nm XCT Enhanced SFP Module NTTP02CDE6 1, 2

STM-1/OC-3 LR1/L1.1 1310 nm XCT Enhanced SFP Module NTTP02ED 1, 2

STM-1/OC-3 LR2/L1.2 1550 nm XCT Enhanced SFP Module NTTP02FD 1, 2

STM-4/OC-12 SFPs

STM-4/OC-12 LR1/L4.1 1310 nm XCT Enhanced SFP Module NTTP05EF 1, 2

STM-4/OC-12 LR1/L4.1 1310 nm XCT Enhanced SFP Module NTTP05EFE6 1, 2

STM-4/OC-12 LR2/L4.2 1550 nm XCT Enhanced SFP Module NTTP05FF 1, 2



STM-16/OC-48 SFPs

STM-16/OC-48 SR1/I16.1 1310 nm XCT Enhanced SFP Module NTTP03BF 1, 2

STM-16/OC-48 SR1/I16.1 1310 nm XCT Enhanced SFP Module NTTP03BFE6 1, 2

STM-16/OC-48 IR1/S16.1 1310 nm XCT Enhanced SFP Module NTTP03CF 1, 2

STM-16/OC-48 IR1/S16.1 1310 nm XCT Enhanced SFP Module NTTP03CFE6 1, 2

STM-16/OC-48 LR1/L16.1 1310 nm XCT Enhanced SFP Module NTTP03EF 1, 2

STM-16/OC-48 LR1/L16.1 1310 nm XCT Enhanced SFP Module NTTP03EFE6 1, 2

STM-16/OC-48 LR2/L16.2 1550 nm XCT Enhanced SFP Module NTTP03FF 1, 2

STM-16/OC-48 LR2/L16.2 1550 nm XCT Enhanced SFP Module NTTP03FFE6 1, 2

STM-1/4/OC-3/12 SFPs

STM-1/4/OC-3/12 IR1/S1.1_S4.1 1310 nm XCT Enhanced SFP Module NTTP04CF 1, 2

STM-1/4/OC-3/12 IR1/S1.1_S4.1 1310 nm XCT Enhanced SFP Module NTTP04CFE6 1, 2

STM-1/4/OC-3/12 IR-1 / S-1.1_S-4.1, 1310nm, -40/+85C, SFP, LC, Enhanced MSA E6

NTTP04CDE6 1, 2

STM-1/4/16/OC-3/12/48 CWDM SFPs

STM-1/4/16/OC-3/12/48 CWDM (1471 nm) XCT Enhanced SFP Module

NTK590LH 1, 2


NTK590LHE6 1, 2


NTK590MH 1, 2


NTK590MHE6 1, 2


NTK590NH 1, 2


NTK590PH 1, 2


NTK590QH 1, 2


NTK590QHE6 1, 2

Table 8-12 (continued)Small form-factor pluggable (SFP) modules





NTK590RH 1, 2


NTK590SH 1, 2


NTK590TH 1, 2


NTK590THE6 1, 2

100Base SFPs

100Base-LX10 1310 nm, 10 km SFP Module NTTP08SD 2, 5

100Base-BX10-U Bidirectional upstream, 1310 nm Tx, 10 km SFP Module

NTTP09BD 2, 3, 4, 5

100Base-BX10-D Bidirectional downstream, 1530 nm Tx, 10 km SFP Module

NTTP10BD 2, 3, 4, 5





GE SFPs

GE SX SFP Module NTTP01AF 2, 6

GE SX, 850nm, -10/+85C, SFP, LC, Enhanced MSA NTTP01AFE6 2, 6

GE LX SFP Module NTTP01CF 2, 6

GE LX SFP Module NTTP01CFE6 2, 6

GE SX, 850nm, -10/+85C, SFP, LC, Enhanced MSA NTTP06AF 2, 6

GE SX, 850nm, -10/+85C, SFP, LC, Enhanced MSA NTTP06AFE6 2, 6

GE 1000-BaseZX 1550 nm XCT Enhanced SFP Module NTTP07FF 2

GE 1000-BaseZX 1550 nm XCT Enhanced SFP Module NTTP07FFE6 2

1000Base-BX10-U Bidirectional upstream, 1310 nm Tx, 10 km SFP Module

NTTP58BD 2, 3, 6

1000Base-BX10-D Bidirectional downstream, 1490 nm Tx, 10 km SFP Module

NTTP59BD 2, 3, 6

GE electrical 1000-BaseT SFP Module NTTP61AAE6 8, 6

GE/FC100 1.25 Gbit/s 24 dB CWDM 1471 nm SFP Module NTK591LB 2

GE/FC100 1.25 Gbit/s 24 dB CWDM 1491 nm SFP Module NTK591MB 2

GE/FC100 1.25 Gbit/s 24 dB CWDM 1511 nm SFP Module NTK591NB 2

GE/FC100 1.25 Gbit/s 24 dB CWDM 1531 nm SFP Module NTK591PB 2

GE/FC100 1.25 Gbit/s 24 dB CWDM 1551 nm SFP Module NTK591QB 2

GE/FC100 1.25 Gbit/s 24 dB CWDM 1571 nm SFP Module NTK591RB 2

GE/FC100 1.25 Gbit/s 24 dB CWDM 1591 nm SFP Module NTK591SB 2

GE/FC100 1.25 Gbit/s 24 dB CWDM 1611 nm SFP Module NTK591TB 2





STM-1e electrical SFPs

STM-1e Enhanced SFP Module NTTP60AE 7

Note 1: This module is used with the STM-1/4/16/OC-3/12/48 optical interface ports.

Note 2: This SFP module comes with LC connectors.

Note 3: Used for a bidirectional link over a single fiber with an upstream SFP fitted at one end of the link and an downstream SFP fitted at the other end of the link. The upstream SFP transmits at 1310 nm and receives at 1530 nm, the downstream SFP transmits at 1530 nm and receives at 1310 nm.

Note 4: This module is used with the STM-1/OC-3 optical interface ports for 1-Fiber bidirectional applications.

Note 5: This module is used with the 100FX optical interface ports.

Note 6: This module is used with the GE interface ports.

Note 7: This SFP module comes with coax connectors and is supported for the 2x155M and 2x622M/8x155M tributary circuit pack at the STM-1 line rate only.

Note 8: This module provides an electrical interface with a reach of 100 m over Cat-5 100 ohm cable.

Table 8-13DWDM small form-factor pluggable (SFP) modules

Description Order Code Notes OMX Band & Channel (Ch)

CPL Group

STM-16/OC-48 1528.77 nm SFP NTK585AA 1, 5 Band 1 Ch 1 -

STM-16/OC-48 1530.33 nm SFP NTK585AE 1, 5, 6 Band 1 Ch 3 Group 1

STM-16/OC-48 1531.12 nm SFP NTK585AG 6 - Group 1

STM-16/OC-48 1531.90 nm SFP NTK585AJ 1, 5, 6 Band 1 Ch 4 Group 1

STM-16/OC-48 1532.68 nm SFP NTK585AL 6 - Group 1

STM-16/OC-48 1533.47 nm SFP NTK585AN 1, 5 Band 1 Ch 2 -

STM-16/OC-48 1534.25 nm SFP NTK585AQ 6 - Group 2

STM-16/OC-48 1535.04 nm SFP NTK585AS 6 - Group 2

STM-16/OC-48 1535.82 nm SFP NTK585AU 6 - Group 2

STM-16/OC-48 1536.61 nm SFP NTK585AW 6 - Group 2

STM-16/OC-48 1538.19 nm SFP NTK585BA 2, 5, 6 Band 2 Ch 1 Group 3

STM-16/OC-48 1538.98 nm SFP NTK585BC 6 - Group 3

STM-16/OC-48 1539.77 nm SFP NTK585BE 2, 5, 6 Band 2 Ch 3 Group 3

STM-16/OC-48 1540.56 nm SFP NTK585BG 6 - Group 3





STM-16/OC-48 1541.35 nm SFP NTK585BJ 2, 5 Band 2 Ch 4 -

STM-16/OC-48 1542.14 nm SFP NTK585BL 6 - Group 4

STM-16/OC-48 1542.94 nm SFP NTK585BN 2, 5, 6 Band 2 Ch 2 Group 4

STM-16/OC-48 1543.73 nm SFP NTK585BQ 6 - Group 4

STM-16/OC-48 1544.53 nm SFP NTK585BS 6 - Group 4

STM-16/OC-48 1546.12 nm SFP NTK585BW 6 - Group 5

STM-16/OC-48 1546.92 nm SFP NTK585BY 6 - Group 5

STM-16/OC-48 1547.72 nm SFP NTK585CA 3, 5, 6 Band 3 Ch 1 Group 5

STM-16/OC-48 1548.51 nm SFP NTK585CC 6 - Group 5

STM-16/OC-48 1549.32 nm SFP NTK585CE 3, 5 Band 3 Ch 3 -

STM-16/OC-48 1550.12 nm SFP NTK585CG 6 - Group 6

STM-16/OC-48 1550.92 nm SFP NTK585CJ 3, 5, 6 Band 3 Ch 4 Group 6

STM-16/OC-48 1551.72 nm SFP NTK585CL 6 - Group 6

STM-16/OC-48 1552.52 nm SFP NTK585CN 3, 5, 6 Band 3 Ch 2 Group 6

STM-16/OC-48 1554.13 nm SFP NTK585CS 6 - Group 7

STM-16/OC-48 1554.94 nm SFP NTK585CU 6 - Group 7

STM-16/OC-48 1555.75 nm SFP NTK585CW 6 - Group 7

STM-16/OC-48 1556.55 nm SFP NTK585CY 6 - Group 7

STM-16/OC-48 1557.36 nm SFP NTK585DA 4, 5 Band 4 Ch 1 -

STM-16/OC-48 1558.17 nm SFP NTK585DC 6 - Group 8

STM-16/OC-48 1558.98 nm SFP NTK585DE 4, 5, 6 Band 4 Ch 3 Group 8

STM-16/OC-48 1559.79 nm SFP NTK585DG 6 - Group 8

STM-16/OC-48 1560.61 nm SFP NTK585DJ 4, 5, 6 Band 4 Ch 4 Group 8

STM-16/OC-48 1562.23 nm SFP NTK585DN 4, 5, 6 Band 4 Ch 2 Group 9

STM-16/OC-48 1563.05 nm SFP NTK585DQ 6 - Group 9

STM-16/OC-48 1563.86 nm SFP NTK585DS 6 - Group 9

STM-16/OC-48 1564.68 nm SFP NTK585DU 6 - Group 9

Table 8-13 (continued)DWDM small form-factor pluggable (SFP) modules


CPL Group



Electrical interface hardwareTable 8-14 lists the hardware associated to the 28xE1/DS1 and 28xE1/DS1(W/P) circuit packs, when conversion for 75 ohm ports is required for E1 services. For rules on equipping the shelf, refer to Shelf equipping rules on page 8-5.

Note 1: These wavelengths are compatible with Optical Metro 5000 DWDM band 1.




Note 5: Refer to the Optera Metro 5000 technical publication documentation for more details on OMX modules and optical link engineering.

Note 6: Refer to the CPL technical publication documentation for more details on optical link engineering.

Table 8-14E1 interface conversion hardware


75 ohm BNC Termination Panel (16 channel) NT6Q71EA 1, 2

75 ohm BNC Termination Panel (16 channel) NT6Q71EAE5 1, 2

Telco to Telco 1M Cable - Right Routing NT6Q75AA 3

Telco to Telco 1M Cable - Right Routing NT6Q75AAE6 3

Telco to Telco 2M Cable - Right Routing NT6Q75BA 3

Telco to Telco 2M Cable - Right Routing NT6Q75BAE6 3

Telco to Telco 5M Cable - Right Routing NT6Q75CA 3

Telco to Telco 5M Cable - Right Routing NT6Q75CAE6 3

Telco to Telco 1M Cable - Left Routing NT6Q74AA 3

Telco to Telco 1M Cable - Left Routing NT6Q74AAE6 3

Telco to Telco 5M Cable - Left Routing NT6Q74CA 3

Table 8-13 (continued)DWDM small form-factor pluggable (SFP) modules


CPL Group



E1/DS1 cable assembliesTable 8-15 and Table 8-16 lists the available E1/DS1 interface cables respectively. These cables are used to provide E1 (input and output) connectivity for 120 ohm and 75 ohm applications, where no termination panel is required and DS1 connectivity for 100 ohm applications.

Attention: Refer to E1/DS1 cable pinouts and assemblies on page 7-12 for the cable requirements if the cables are to be sourced locally.

Telco to Telco 5M Cable - Left Routing NT6Q74CAE6 3

Telco to Telco 10M Cable - Left Routing NT6Q74DAE6 3

Note 1: This panel provides conversion from 120 ohm to 75 ohm for E1 service only. The unit is a 1U high rack-mountable panel.

Note 2: This termination panel can be used to convert E1 services from the 28xE1/DS1 circuit pack, 28xE1/DS1 1+1 I/O module and 84xE1/DS1 1:N I/O module. An additional overlay sticker is provided for proper labeling when converting the 17-28 E1 ports of the 28xE1/DS1 circuit pack, 28xE1/DS1 1+1 I/O module and 84xE1/DS1 1:N I/O module.

Note 3: These cables are required for connecting the E1 ports on the 75 ohm termination panel. Please refer to Site engineering recommendations on page 8-16 for details on applications requiring right routing and applications requiring left routing.

Table 8-15E1 cable assemblies and connectors


Cables

120Ohm Telco 5M Cable - Right Routing NT6Q73BA 1, 2

120Ohm Telco 5M Cable - Right Routing NT6Q73BAE6 1, 2

120Ohm Telco 10M Cable - Right Routing NT6Q73CA 1, 2

120Ohm Telco 10M Cable - Right Routing NT6Q73CAE6 1, 2

120Ohm Telco 20M Cable - Right Routing NT6Q73EA 1, 2

120Ohm Telco 20M Cable - Right Routing NT6Q73EAE6 1, 2

120Ohm Telco 5M Cable - Left Routing NT6Q72BA 1, 2

120Ohm Telco 5M Cable - Left Routing NT6Q72BAE6 1, 2

120Ohm Telco 10M Cable - Left Routing NT6Q72CA 1, 2

Table 8-14 (continued)E1 interface conversion hardware




120Ohm Telco 10M Cable - Left Routing NT6Q72CAE6 1, 2

120Ohm Telco 15M Cable - Left Routing NT6Q72DA 1, 2

120Ohm Telco 15M Cable - Left Routing NT6Q72DAE6 1, 2

120Ohm Telco 20M Cable - Left Routing NT6Q72EA 1, 2

120Ohm Telco 20M Cable - Left Routing NT6Q72EAE6 1, 2

E1 High Density I/O cable 75 ohm, 5 m NTTC41ABE6 3

E1 High Density I/O cable 75 ohm, 10 M NTTC41ACE6 3

E1 High Density I/O cable 75 ohm, 20 M NTTC41AEE6 3

E1 High Density I/O cable 120 ohm, 5 M NTTC41BBE6 4

E1 High Density I/O cable 120 ohm, 10 M NTTC41BCE6 4

E1 High Density I/O cable 120 ohm, 20 M NTTC41BEE6 4

Connector kits

Connector Kit, Coax, BNC, Male/Plug, Free, 3M 138 Cable, Qty 65

NTTC00AAE6 5

Connector Kit, Coax, BNC, Female, Flange Mount, 3M 138 Cable, Qty 65

NTTC00ANE6 6

Connector Kit, Coax, BT-43, Plug, 13 mm DDF 3M 138 Cable, Qty 65 NTTC00BBE6 7

Connector Kit, Coax, BT-43, Plug, 10 mm DDF, 3M 138 Cable, Qty 65 NTTC00BCE6 8

Single connectors

Connector Coax, BNC 75 ohm, Male Straight Cable Plug for use with 3M 138 Type 2.1 mm Outside Diameter Cable

N0104116 9

Connector Coax, BNC 75 ohm, Female Straight Flange Mount Jack for use with 3M 138 Type 2.1 mm Outside Diameter Cable

N0104117 9

Connector Coax, BT-43 Straight Bulkhead Plug, 13 mm DDF, for use with 3M 138 Cable Type 2.1 mm Outside Diameter Cable

N0104123 9

Table 8-15 (continued)E1 cable assemblies and connectors




..

Connector Coax, BT-43 Straight Bulkhead Plug, 10 mm DDF, for use with 3M 138 Cable Type 2.1 mm Outside Diameter Cable

N0104122 9

STM-1e Connector, BNC 75ohm, Male, Straight, Plug N0104109

Note 1: These cables provides 64-pin balanced 120 ohm for the E1 services on the 28xE1/DS1 circuit pack, 28xE1/DS1 1+1 I/O module and 84xE1/DS1 1:N I/O module. Please refer to Site engineering recommendations on page 8-16 for details on applications requiring right routing and applications requiring left routing.

Note 2: These cables have a shielded connector to connect to the 28xE1/DS1 circuit pack, 28xE1/DS1 1+1 I/O module and 84xE1/DS1 1:N I/O module.

Note 3: This 160-pin cable provides 64 unbalanced 75 ohm E1 connections (32 Tx ports and 32 Rx ports) for E1 services on the 63xE1/DS1circuit pack. Two cable assemblies are required for each 63xE1/DS1circuit pack to support access to all 63 ports.

Note 4: This 160-pin cable provides 64 balanced 120 ohm E1 connections (32 Tx ports and 32 Rx ports) for E1 services on the 63xE1/DS1circuit pack. Two cable assemblies are required for each 63xE1/DS1circuit pack to support access to all 63 ports.

Note 5: This kit contains 65 N0104116 field terminable connectors (BNC, 75 ohm, Male, Straight, Plug) for the E1 75 ohm cable assemblies (NTTC41AxE6).

Note 6: This kit contains 65 N0104117 field terminable coaxial connectors (BNC, 75 ohm, Female, Straight, Flange Mount) for the E1 75 ohm cable assemblies (NTTC41AxE6).

Note 7: This kit contains 65 N0104123 field terminable connectors (BT-43, Straight, Bulkhead, Plug, 13mm DDF) for the E1 75 ohm cable assemblies (NTTC41AxE6).

Note 8: This kit contains 65 N0104122 field terminable connectors (BT-43, Straight, Bulkhead, Plug, 10mm DDF) for the E1 75 ohm cable assemblies (NTTC41AxE6).

Note 9: This item is a single field terminable connector for the E1 I/O 75 ohm cable assemblies (NTTC41AxBE6).

Table 8-16DS1 cable assemblies


100Ohm Telco 15M Cable - Right Routing NT6Q73QA 1, 2

100Ohm Telco 30M Cable - Right Routing NT6Q73TA 1, 2

100Ohm Telco 15M Cable - Left Routing NT6Q72QA 1, 2

100Ohm Telco 30M Cable - Left Routing NT6Q72TA 1, 2

Note 1: These cables provides 64-pin balanced 100 ohm for the DS1 services on the on the 28xE1/DS1 circuit pack, 28xE1/DS1 1+1 I/O module and 84xE1/DS1 1:N I/O module. Please refer to Site engineering recommendations on page 8-16 for details on applications requiring right routing and applications requiring left routing.

Note 2: These cables have a shielded connector to connect to the 28xE1/DS1 circuit pack, 28xE1/DS1 1+1 I/O module and 84xE1/DS1 1:N I/O module.

Table 8-15 (continued)E1 cable assemblies and connectors




E3/DS3 cable assembliesTable 8-17 lists the available E3/DS3 coaxial cables for the 3xE3/DS3 and 3xE3/DS3(W/P) circuit packs. These cables are used to provide E3/DS3 (input and output) connectivity to the 6130 network element.

Table 8-17E3/DS3 cable assemblies


BNC Connector (735A) N0104114 1

DS3 735A Coaxial Cable - 10M BNC NT7E43BB 2, 3

DS3 735A Coaxial Cable - 10M BNC NT7E43BBE6 2, 3

DS3 735A Coaxial Cable - 30M BNC NT7E43BD 2, 3

DS3 735A Coaxial Cable - 60M BNC NT7E43BG 2, 3

75Ohm 10M Cable Assembly, SMB Male - BNC Male, RG59 Equivalent

NT6Q78AAE6 1

Note 1: Use this connector to terminate the E3/DS3 cabling at the customer interface equipment.

Note 2: Two cable assemblies are required per E3/DS3 port (for receive and transmit).

Note 3: This cable is terminated with a BNC at one end only. A BNC connector (N0104114) should be ordered to connect to the customer interface equipment.

Note 4: This cable is used with the Transmux circuit pack.



STM-1e cable assembliesTable 8-18 lists the available STM-1 coaxial cableforms used to provide STM-1e connectivity to the STM-1e SFP modules.

Table 8-18STM-1e cable assemblies


STM-1e cables

Cable Assembly, Co-axial, DIN 1.0/2.3, RG179DT cable, single, 10 m NTTC04AA 1

Cable Assembly, Co-axial, DIN 1.0/2.3, RG179DT cable, single, 20 m NTTC04AB 1

Cable Assembly, Co-axial, DIN 1.0/2.3, RG179DT cable, single, 30 m NTTC04AC 1

Cable Assembly, Co-axial, DIN 1.0/2.3, RG179DT cable, single, 40 m NTTC04AD 1

Cable Assembly, Co-axial, DIN 1.0/2.3, RG179DT cable, single, 50 m NTTC04AE 1

Cable Assembly, Co-axial, DIN 1.0/2.3, RG179DT cable, single, 60 m NTTC04AF 1

Cable Assembly, Co-axial, DIN 1.0/2.3, RG179DT cable, single, 10 m NTTC04AAE6 1

Cable Assembly, Co-axial, DIN 1.0/2.3, RG179DT cable, single, 20 m NTTC04ABE6 1

Cable Assembly, Co-axial, DIN 1.0/2.3, RG179DT cable, single, 30 m NTTC04ACE6 1

Cable Assembly, Co-axial, DIN 1.0/2.3, RG179DT cable, single, 40 m NTTC04ADE6 1

Cable Assembly, Co-axial, DIN 1.0/2.3, RG179DT cable, single, 50 m NTTC04AEE6 1

Cable Assembly, Co-axial, DIN 1.0/2.3, RG179DT cable, single, 60 m NTTC04AFE6 1

Single connectors

Connector Coax, BNC 75 ohm, Male, Straight Plug for use with RG179DT Cable

A0360953 2

Connector Coax, BNC 75 ohm, Female Straight, Bulkhead, Jack, Crimp/Crimp, for use with RG179DT Cable

A0678277 2

Connector Coax, BT43 75 ohm, Male, Straight, Bulkhead DDF, Crimp/Crimp, for use with RG179DT Cable

A0620780 2

Connector Coax, HDC43 Bulkhead Plug (Male) Crimp/Crimp, RG179/U, DDF Mount, Single PC. Body

N0032563 2

Connector Coax, DIN 1.0/2.3 mm, Straight Cable Plug (Male) Crimp/Crimp 75 ohm RG179/U

N0032582 2

Note 1: This cable provides a single STM-1e co-axial connector. The cable uses RG179DT coaxial cable. You must order an appropriate connector for the open end of each cable assembly. Two cable assemblies are required for every STM-1e SFP module.

Note 2: These are single field terminable connectors for the STM-1e cable assemblies (NTTC04Ax).



Ethernet service cable assembliesTable 8-19 lists the available Ethernet cableforms used to provide connectivity to the 10/100BT interfaces associated with the 8xETH, 4x10/100BT+4x100FX L1, 2xGE+8x10/100BT L1 1.2G, L2PA622M and L2PA1G2 circuit packs. Shielded twisted pair (STP) cables are required to connect to the Ethernet ports on those circuit packs.

Attention: 10/100BT ports on those circuit packs are wired as MDI/MDI-X, and auto-detect the type of cable connected to it (straight or crossover).

Table 8-19Ethernet service cable assemblies


Ethernet service (STP) cables

Cable Assembly, STP Cat 5E, RJ45, TIA568, Crossover, Single, 5 m NTTC09CA 1

Cable Assembly, STP Cat 5E, RJ45, TIA568, Crossover, Single, 5 m NTTC09CAE6 1

Cable Assembly, STP Cat 5E, RJ45, TIA568, Crossover, Single, 10 m NTTC09CB 1

Cable Assembly, STP Cat 5E, RJ45, TIA568, Crossover, Single, 15 m NTTC09CC 1

Cable Assembly, STP Cat 5E, RJ45, TIA568, Crossover, Single, 20 m NTTC09CD 1

Cable Assembly, STP Cat 5E, RJ45, TIA568, Crossover, Single, 30 m NTTC09CE 1

Cable Assembly, STP Cat 5E, RJ45, TIA568, Crossover, Single, 30 m NTTC09CEE6 1

Cable Assembly, STP Cat 5E, RJ45, TIA568, Crossover, Single, 40 m NTTC09CF 1

Cable Assembly, STP Cat 5E, RJ45, TIA568B, Straight, Single, 5 m NTTC09DA 1

Cable Assembly, STP Cat 5E, RJ45, TIA568B, Straight, Single, 5 m NTTC09DAE6 1

Cable Assembly, STP Cat 5E, RJ45, TIA568B, Straight, Single, 10 m NTTC09DB 1

Cable Assembly, STP Cat 5E, RJ45, TIA568B, Straight, Single, 15 m NTTC09DC 1

Cable Assembly, STP Cat 5E, RJ45, TIA568B, Straight, Single, 15 m NTTC09DCE6 1

Cable Assembly, STP Cat 5E, RJ45, TIA568B, Straight, Single, 20 m NTTC09DD 1

Cable Assembly, STP Cat 5E, RJ45, TIA568B, Straight, Single, 30 m NTTC09DE 1

Cable Assembly, STP Cat 5E, RJ45, TIA568B, Straight, Single, 30 m NTTC09DEE6 1

Note 1: This cable provides an Ethernet connection for the 10/100BT interfaces on the 8xETH, 4x10/100BT+4x100FX L1, 2xGE+8x10/100BT L1 1.2G, L2PA622M and L2PA1G2 circuit packs. Each cable has two RJ45 connectors and uses shielded twisted pair Category 5E cable.



Optical fiber patch cordsTable 8-20 lists the available optical fiber patch cords.

Table 8-20Optical fiber patch cords


Optical patchcords, LC-LC, SM, Simplex NTTC50Ax 1,2

Optical patchcords, LC-SC, SM, Simplex NTTC50Bx 1,2

Optical patchcords, LC-FC, SM, Simplex NTTC50Cx 1,2

Optical patchcords, LC-ST, SM, Simplex NTTC50Dx 1,2

Optical patchcords, LC-LC, SM, Simplex NTTC50AxE6 1,2

Optical patchcords, LC-SC, SM, Simplex NTTC50BxE6 1,2

Optical patchcords, LC-FC, SM, Simplex NTTC50CxE6 1,2

Optical patchcords, LC-ST, SM, Simplex NTTC50DxE6 1,2

Optical patchcords, LC-LC, SM, Duplex NTTC53Ax 1,2

Optical patchcords, LC-SC, SM, Duplex NTTC53Bx 1,2

Optical patchcords, LC-FC, SM, Duplex NTTC53Cx 1,2

Optical patchcords, LC-ST, SM, Duplex NTTC53Dx 1,2

Optical patchcords, LC-LC, SM, Duplex NTTC53AxE6 1,2

Optical patchcords, LC-SC, SM, Duplex NTTC53BxE6 1,2

Optical patchcords, LC-FC, SM, Duplex NTTC53CxE6 1,2

Optical patchcords, LC-ST, SM, Duplex NTTC53DxE6 1,2

Optical patchcords, LC-LC, MM 50 micron, Simplex NTTC56Ax 1,3

Optical patchcords, LC-LC, MM 50 micron, Simplex NTTC56ACE6 1,3

Optical patchcords, LC-SC, MM 50 micron, Simplex NTTC56Bx 1,3

Optical patchcords, LC-SC, MM 50 micron, Simplex NTTC56BBE6 1,3

Optical patchcords, LC-FC, MM 50 micron, Simplex NTTC56Cx 1,3

Optical patchcords, LC-ST, MM 50 micron, Simplex NTTC56Dx 1,3

Optical patchcords, LC-LC, MM 50 micron, Duplex NTTC59Ax 1,3

Optical patchcords, LC-SC, MM 50 micron, Duplex NTTC59Bx 1,3

Optical patchcords, LC-FC, MM 50 micron, Duplex NTTC59Cx 1,3

Optical patchcords, LC-ST, MM 50 micron, Duplex NTTC59Dx 1,3

Optical patchcords, LC-LC, MM 50 micron, Duplex NTTC59AxE6 1,3



Optical patchcords, LC-SC, MM 50 micron, Duplex NTTC59BxE6 1,3

Optical patchcords, LC-FC, MM 50 micron, Duplex NTTC59CxE6 1,3

Optical patchcords, LC-ST, MM 50 micron, Duplex NTTC59DxE6 1,3

Optical patchcords, LC-LC, MM 62.5 micron, Simplex NTTC62Ax 1,4

Optical patchcords, LC-SC, MM 62.5 micron, Simplex NTTC62Bx 1,4

Optical patchcords, LC-SC, MM 62.5 micron, Simplex NTTC62BBE6 1,4

Optical patchcords, LC-FC, MM 62.5 micron, Simplex NTTC62Cx 1,4

Optical patchcords, LC-ST, MM 62.5 micron, Simplex NTTC62Dx 1,4

Optical patchcords, LC-LC, MM 62.5 micron, Duplex NTTC65Ax 1,4

Optical patchcords, LC-SC, MM 62.5 micron, Duplex NTTC65Bx 1,4

Optical patchcords, LC-LC, MM 62.5 micron, Duplex NTTC65AxE6 1,4

Optical patchcords, LC-SC, MM 62.5 micron, Duplex NTTC65BxE6 1,4

Optical patchcords, LC-FC, MM 62.5 micron, Duplex NTTC65Cx 1,4

Optical patchcords, LC-ST, MM 62.5 micron, Duplex NTTC65Dx 1,4

Optical patchcords, LC-LC, Mode Conditioning 50 micron, Duplex NTTC71Ax 1,5

Optical patchcords, LC-SC, Mode Conditioning 50 micron, Duplex NTTC71Bx 1,5

Optical patchcords, LC-FC, Mode Conditioning 50 micron, Duplex NTTC71Cx 1,5

Optical patchcords, LC-ST, Mode Conditioning 50 micron, Duplex NTTC71Dx 1,5

Optical patchcords, LC-LC, Mode Conditioning 62.5 micron, Duplex NTTC77Ax 1,6

Optical patchcords, LC-SC, Mode Conditioning 62.5 micron, Duplex NTTC77Bx 1,6

Table 8-20 (continued)Optical fiber patch cords




Table 8-21 lists the available lengths of optical fiber patchcords.

Optical patchcords, LC-FC, Mode Conditioning 62.5 micron, Duplex NTTC77Cx 1,6

Optical patchcords, LC-ST, Mode Conditioning 62.5 micron, Duplex NTTC77Dx 1,6

Note 1: The optical patchcords are available in different lengths. The last digit of the order code defines the length as shown in Table 8-21 on page 8-38.

Note 2: The singlemode fibers are used to transmit 1310 nm, 1550 nm and CWDM frequency signals on singlemode fiber plant.

Note 3: The 50 micron multimode fibers are used to transmit 850 nm frequency signals on 50 micron multimode fiber plant.

Note 4: The 62.5 micron multimode fibers are used to transmit 850 nm frequency signals on 62.5 micron multimode fiber plant.

Note 5: The 50 micron mode conditioning patchcords are used to transmit 1310 nm frequency signals on 50 micron multimode fiber plant.

Note 6: The 62.5 micron mode conditioning patchcords are used to transmit 1310 nm frequency signals on 62.5 micron multimode fiber plant.

Table 8-21Lengths of optical fiber patchords

Length Last digit of order code

1 meter A

2 meters B

3 meters C

5 meters D

7 meters E

10 meters F

13 meters G

15 meters H

20 meters J

25 meters K

30 meters L

Note: This table defines the length and last digit of the order codes shown in Table 8-20 on page 8-36. For example, an NTTC50AD is an optical patchcord, LC-LC, SM, Simplex, 5 meters.

Table 8-20 (continued)Optical fiber patch cords




OAM cable assembliesTable 8-22 through Table 8-24 list the available OAM cable assemblies. These cables are used to provide synchronization, alarm, user interface and network element connectivity. Refer to Procedure 8-2 on page 8-65 for ordering instructions.

Attention: The LAN and Craft ports on the OAM circuit pack are wired as MDI/MDI-X, and auto-detect the type of cable connected to it (straight or crossover).

Table 8-22DCN and craft access cables


F1 cable NT6Q71AF 1

Modem Cable NT6Q71AG 2

Cable Assembly, STP Cat 5E, RJ45, TIA568, Crossover, Single, 5 m NTTC09CA 3

Cable Assembly, STP Cat 5E, RJ45, TIA568, Crossover, Single, 5 m NTTC09CAE6 3

Cable Assembly, STP Cat 5E, RJ45, TIA568, Crossover, Single, 10 m NTTC09CB 3

Cable Assembly, STP Cat 5E, RJ45, TIA568, Crossover, Single, 15 m NTTC09CC 3

Cable Assembly, STP Cat 5E, RJ45, TIA568, Crossover, Single, 20 m NTTC09CD 3

Cable Assembly, STP Cat 5E, RJ45, TIA568, Crossover, Single, 30 m NTTC09CE 3

Cable Assembly, STP Cat 5E, RJ45, TIA568, Crossover, Single, 30 m NTTC09CEE6 3

Cable Assembly, STP Cat 5E, RJ45, TIA568, Crossover, Single, 40 m NTTC09CF 3

Cable Assembly, STP Cat 5E, RJ45, TIA568B, Straight, Single, 5 m NTTC09DA 3

Cable Assembly, STP Cat 5E, RJ45, TIA568B, Straight, Single, 10 m NTTC09DB 3

Cable Assembly, STP Cat 5E, RJ45, TIA568B, Straight, Single, 15 m NTTC09DC 3

Cable Assembly, STP Cat 5E, RJ45, TIA568B, Straight, Single, 20 m NTTC09DD 3

Cable Assembly, STP Cat 5E, RJ45, TIA568B, Straight, Single, 30 m NTTC09DE 3



Cable Assembly, STP Cat 5E, RJ45, TIA568B, Straight, Single, 40 m NTTC09DF 3

Cable Assembly, STP Cat 5E, RJ45, TIA568B, Straight, Single, 60 m NTTC09DH 3

Note 1: This F1 interface cable connects to the serial port on the OAM circuit pack and supports an asynchronous interface.

Note 2: This modem cable has the DSR pin isolated.

Note 3: Shielded twisted pair (STP) cables are required to connect to the LAN and Craft Ethernet ports on the OAM circuit pack.

Table 8-23Alarm and telemetry cables


6130 - Environmental alarm cable kit, 3M NT6Q59AB 1

6130 - Environmental alarm cable kit, 3M NT6Q59ABE6 1

Note 1: This environmental alarm cable kit provides a pair of alarm cables(NT6Q71AB) for the ALMIN and ALMOUT ports. These cables provide the 7 alarm inputs or the critical, major, minor alarm outputs of the shelf to a cross connect location.

Table 8-24Synchronization cable


Clock (BITS) Cable (120 ohm), 5M NT6Q71AC 1, 3

Clock (BITS) Cable (inc 75 ohm convertor), 5M NT6Q71AE 2, 3

Clock (BITS) Cable (120 ohm), 5M NT6Q71ACE6 1, 3

Clock (BITS) Cable (inc 75 ohm convertor), 5M NT6Q71AEE6 2, 3

Note 1: This clock cable supports 120 ohm impedance with RJ-45 connector for connection to the RJ-45 ESI port on the OAM circuit pack. This cable is used for BITS timing in SDH and SONET modes.

Note 2: This clock cable supports 75 ohm impedance and comes with a balun converter for connection to the RJ-45 ESI port on the OAM circuit pack.

Note 3: This clock cable supports 4 synchronization signals (2 input and 2 output).

Table 8-22 (continued)DCN and craft access cables




Power and earthing cable assembliesTable 8-25 lists the available power and earthing cable assemblies for the 6130 chassis. For 6130 NEs equipped with two single-DC feed PSUs, two DC cables must be ordered for each network element installation.

For more information on the PSU, refer to Power supply unit on page 4-7. Refer to Procedure 8-2 on page 8-65 for ordering instructions.

Table 8-25Power and earthing cable assemblies


6130 - DC cable, 14AWG, - 3M NT6Q59CA 1

6130 - DC cable, 14AWG, - 10M NT6Q59DA 2

6130 - DC cable, 14AWG, - 3M NT6Q59CAE6 1

6130 - DC cable, 14AWG, - 10M NT6Q59DAE6 2

6130 - DC Cable Kit, 14AWG, - 3M North America NT6Q59PA 3

6130 - DC cable kit, 14AWG, - 10M North America NT6Q59QA 4

6130 DC Cable Kit 3M EU NT6Q59GAE6

6130 DC Cable Kit 10M EU NT6Q59HAE6

Earthing cable, 14AWG, 3M NT6Q71AA 5

Earthing cable, 14AWG, 3M NT6Q71AAE6 5

Ciena Euro/C13 2 meter AC cord NTK955CB 6

Ciena Danish/C13 2 meter AC cord NTK955CC 6

Ciena Israel/C13 2 meter AC cord NTK955CE 6

Ciena Italian/C13 2 meter AC cord NTK955CF 6

Ciena Swiss/C13 2 meter AC cord NTK955CG 6

Ciena U.K./C13 2 meter AC cord NTK955CH 6

Ciena North America/C13 2.5 meter AC cord NTK955CK 6

Ciena Euro/C13 2 meter AC cord NTK955CBE6 6

Ciena Danish/C13 2 meter AC cord NTK955CCE6 6

Ciena Israel/C13 2 meter AC cord NTK955CEE6 6

Ciena Italian/C13 2 meter AC cord NTK955CFE6 6

Ciena Swiss/C13 2 meter AC cord NTK955CGE6 6



Software loadThis section provides the information for ordering 6130 software, as shown in Table 8-26.

Ciena U.K./C13 2 meter AC cord NTK955CHE6 6

Ciena North America/C13 2.5 meter AC cord NTK955CKE6 6

Note 1: This DC cable provides a 3 meter BL/BK/GR power cable.

Note 2: This DC cable provides a 10 meter BL/BK/GR power cable.

Note 3: This DC cable provides a 3 meter RD/BK/GR power cable for North American standards.

Note 4: This DC cable provides a 10 meter RD/BK/GR power cable for North American standards.

Note 5: One earthing cable is included in the NT6Q70CA installation kit.

Note 6: An AC power cord must be ordered for the corresponding deployment region of the 6130 AC system

Table 8-26Software superset


6130 R1.0 CD-ROM NT6Q83AA 1

6130 R2.0 CD-ROM NT6Q83BA 1

6130 R3.0 CD-ROM NT6Q83CA 1

6130 R3.01 CD-ROM NT6Q83CB 1

6130 R4.0 CD-ROM NT6Q83DA 1

6130 R4.1 CD-ROM NT6Q83DB 1

6130 R5.0 CD-ROM NT6Q83EA 1

Note 1: This code provides one copy of the 6130 software load on a CD-ROM. The local craft access terminal load is imbedded in the network element software load.

Table 8-25 (continued)Power and earthing cable assemblies




Right to use licensesThe right to use licences are listed in Table 8-27.

Site Manager for 6100This section provides the information for ordering the Site Manager for 6100 software CD-ROM, right to use license and documentation (fundamentals guide), as shown in Table 8-28.

Table 8-27Right to use licenses


6130 R1.0 SW Certificate 1/NE NT6Q85AA 1

6130 R2.0 SW Certificate 1/NE NT6Q85BA 1

6130 R3.0 SW Certificate 1/NE NT6Q85CA 1

6130 R3.01 SW Certificate 1/NE NT6Q85CB 1

6130 R4.0 SW Certificate 1/NE NT6Q85DA 1

6130 R4.1 SW Certificate 1/NE NT6Q85DB 1

6130 R5.0 SW Certificate 1/NE NT6Q85EA 1

6130 Base SW RTU 1/NE NT6Q82AA 2

Note 1: One 6130 software certificate is required for each 6130 network element.

Note 2: One 6130 Base RTU is required for each 6130 network element.

Table 8-286100 Site Manager


Site Manager for 6130 SW RTU license NT6Q90ZB 1

Site Manager for 6100 Rel 1.0 software CD-ROM NT6Q90AA 2

Site Manager for 6100 Rel 1.0 Planning and Installation Guide NT6Q91AA 2

Site Manager for 6100 Rel 3.0 software CD-ROM NT6Q90AC 3

Site Manager for 6100 Rel 3.0 Fundamentals NT6Q91AC 3



Engineering and support servicesCiena offers the following engineering and support services for the 6130. In addition to the services described below, Ciena offers a selection of services to help you plan, deploy, operate, and maintain your optical networks. For more information about these services, contact your Ciena representative or visit www.ciena.com/services.

6130 documentationThis section provides documentation ordering information and a brief overview of the Ciena technical publication libraries and individual documents that can be ordered for 6130 network elements. Documentation is available on paper and on CD-ROM. Table 8-30 lists the ordering information for technical publication packages.

Site Manager for 6100 Rel 4.0 Fundamentals NT6Q91AD 4

6100 Site Manager CD Rel 4.0 NT6Q90AD 4

Note 1: One 6130 RTU is required for each 6130 network element.

Note 2: Site Manager for 6100 Rel. 1.0 is required for 6130 Rel.3.0



Table 8-29Engineering and support services


Hot staging service for 6130 NTYY99CV 1

Note 1: Ciena staging services are designed to prepare network components for integration into a customer’s network. By centralizing the execution of services typically performed in the field at a staging facility, the product can be delivered to the customer in its most simplified, cost effective, and integrated form. Hot staging services for the 6130 product consist of system testing validation prior to delivery to the customer site.

Table 8-28 (continued)6100 Site Manager




Table 8-306130 documentation

Description Order code

Release 1.0 documentation

6130 R1.0 technical publication (Paper) NT6Q65BA

6130 R1.0 technical publication (CD-ROM) NT6Q64BA

6130 R1.0 Planning Guide NT6Q92MA


6130 R2.0 technical publication (Paper) NT6Q65BB

6130 R2.0 technical publication (CD-ROM) (see Note 2) NT6Q64BB

6130 R2.0 Planning Guide NT6Q92MB


6130 R3.0 technical publication (Paper) NT6Q65BC

6130 R3.0 technical publication (CD-ROM) (see Note 2) NT6Q64BC

6130 R3.0 Planning Guide NT6Q92MC


6130 R4.0 technical publication (Paper) NT6Q65BD

6130 R4.0 technical publication (CD-ROM) (see Note 2) NT6Q64BD

6130 R4.0 Planning Guide NT6Q92MD

6100 Data Application Guide (for 6110, 6130 and 6150) NTRN15CA


6130 R5.0 technical publication CD-ROM (see Note 2) NT6Q64BF

Note 1: Refer to table Table 8-31 for a list of documents included in the technical publication suite.

Note 2: All technical publications are included in the CD-ROM.



Table 8-31 lists the 6130 Technical Publication Library Suite.

Change application proceduresTable 8-32 lists the 6130 change application procedures (CAPs).

Table 8-316130 Technical Publication Library Suite

Technical Publication Document code

About the 6130 technical publication Library 323-1855-090

TL1 Reference 323-1855-190

Local Craft Access User Guide 323-1855-195

Installation, Commissioning and Testing Procedures 323-1855-201

Provisioning and Protection Switching Procedures 323-1855-310

Bandwidth and Data Services Procedures 323-1855-320

Trouble Clearing and Module Replacement Procedures 323-1855-543

Table 8-326130 CAPs

CAPs Document code

6130 Upgrade CAP from Release 1.0 to Release 1.01 NT6Q93MA

6130 Upgrade CAP from Release 1.0/1.01 to Release 2.0 NT6Q93MB

6130 Upgrade CAP from Release 2.0 to Release 3.0 NT6Q93MC

6130 Upgrade CAP from Release 3.0 to Release 3.0.1 NT6Q93MD

6130 Upgrade CAP from Release 3.0/3.0.1 to Release 4.0 NT6Q93ME

6130 Upgrade CAP from Rel4.0 to Rel4.1 NT6Q93MF

6130 Upgrade CAP from Rel4.0 to Rel5.0 NT6Q93MG



RoHS compliant equipmentCiena is fully committed to meeting the requirements of the European Union Environmental Directives (EUED) and in particular the Restriction of Hazardous Substances (RoHS) Directive 2002/95/EC. The RoHS Directive became law for customers within the EU from 1st July 2006.

As a consequence of this, equipment for the 6130 is being made RoHS compliant. To help differentiate between the compliant and non-compliant equipment, Ciena has adopted a policy for equipment that has been updated to become for RoHS compliant of either:

• adding “E5”, “E6” or “L6” as a suffix to the existing product equipment code (PEC). E5 indicates that it is RoHS 5/6 compliant, E6 indicates that it is RoHS 6/6 compliant, and L6 indicates that it is Low Smoke Zero Halogen (LSZH) and RoHS 6/6 compliant.

• changing a single digit in the PEC (for example, ‘NTRU0501’ changes to ‘NTRU6501’ where the 5th digit is changed to ‘6’ to indicate that it is RoHS 6/6 compliant)

The PEC for equipment that is already RoHS compliant remains the same.

Customers who operate within the EU must order the RoHS compliant version of 6130 equipment for equipment being supplied after 1st July 2006. There is no change to the behavior or functionality of equipment that has been updated to become RoHS compliant, nor is there any change required to the software deployed - the revised RoHS compliant equipment is backward compatible with the non-RoHS compliant version. Thus, customers outside the EU may order the standard equipment but may receive a RoHS compliant version.

RoHS compliant equipment include labels which indicate the RoHS compliance level.

Further information on the Ciena RoHS strategy will be made available on the appropriate product pages on the Ciena web site (www.ciena.com).

Ordering proceduresUse the following procedures to order equipment, software, documentation, and services for an 6130 network deployment.



Procedure 8-1Ordering 6130 chassis, circuit packs, and software

Use this procedure to order 6130 chassis, circuit packs, and software. Repeat this procedure for each network element at a site in the 6130 network.

Before you start• Complete a network design.

• Read 6130 network element configuration rules on page 8-2.

• Photocopy on page 8-63 and Table 8-35 on page 8-69 (if required).

Procedure tasks• Record requirements (step 2).

• Order chassis (step 33).

• Order 6130 assembly kit (step 34).

• Order circuit packs (step 35).

• Order small form-factor pluggable (SFP) modules (step 53).

• Order the 75 ohm termination panel (step 54)

• Order E1/DS1 cables (step 55).

• Order software and RTU licences (step 60).

Expected results • You have a complete list of chassis, circuit packs, and software for an 6130 site.

• If the expected results do not occur:

— Review the network design and repeat the procedure.

— Contact your next level of support.



Procedure 8-1 (continued)Ordering 6130 chassis, circuit packs, and software

Action

Step Action

Attention: Use a photocopy of on page 8-63 for this procedure. All line number references are to this table unless noted otherwise.

1 Determine the type of aggregate circuit pack(s) required.

2 Determine the number of 10/100BT Layer 1 (L1) Ethernet Private Line (EPL) services that are required, record the number in Line 4. If no 10/100BT L1 EPL services are required, enter ‘none’ on Line 4.

— A maximum of 32 10/100BT L1 EPL ports can be provisioned per 6130 shelf (8 ports for each 8xETH circuit pack or for each 2xGE+8x10/100BT L1 1.2G circuit pack).

— The 4x10/100BT+4x100FX L1 and 4x10/100BT+4x100FX L1 622M circuit pack supports four 10/100BT ports.

3 Determine the number of 100FX L1 EPL services that are required, record the number in Line 5. If no 100FX L1 EPL services are required, enter ‘none’ on Line 5.

— Each 4x10/100BT+4x100FX L1 or 4x10/100BT+4x100FX L1 622M circuit pack supports 4 10/100BT L1 EPL ports and 4 100FX L1 EPL ports.

— A maximum of 16 100FX L1 EPL ports can be provisioned per 6130 shelf (4 ports for each 4x10/100BT+4x100FX L1 circuit pack).

If you require Then

the 6130 NE to be used in an application with STM-1/4/OC-3/12 node capacity and the node redundancy mode is set to non-redundant

Enter ‘one NT6Q66AEE5 2x155/622M aggregate circuit pack’ in Line 3.

the 6130 NE to be used in an application with STM-1/4/OC-3/12 node capacity and the node redundancy mode is set to redundant

Enter ‘two NT6Q67AEE5 1x155/622M aggregate circuit packs’ in Line 3.

the 6130 NE to be used in an application with STM-4/16/OC-12/48 node capacity and 2.5G cross-connect capacity for the 4 tributary slots

Enter ‘two NT6Q68AEE5 1x2.5G aggregate circuit packs’ in Line 3.

the 6130 NE to be used in an application with STM-4/16/OC-12/48 node capacity, STM-1/4/OC-3/12 tributary ports on the aggregate cards and 5G cross-connect capacity for the 4 tributary slots

Enter ‘two NT6Q69AEE5 1x2.5G+4x155M/2x622M aggregate circuit packs’ in Line 3. If extended temperature is required enter NT6Q69BAE5 instead.




Step Action

4 Determine the number of GE L1 EPL services that are required, record the number in Line 6. If no GE EPL services are required, enter ‘none’ on Line 6.

— A maximum of 8 GE L1 EPL ports can be provisioned per 6130 shelf (2 ports for each 2xGE circuit pack or 2 ports for each 2xGE+8x10/100BT L1 1.2G circuit pack).

5 Based on the values recorded on Line 4, Line 5 and Line 6, determine the number of 8x10/100BT (8xETH) L1 and/or 4x10/100BT+4x100FX L1 and/or 4x10/100BT+4x100FX L1 622M and/or 2xGE and/or 2xGE+8x10/100BT L1 1.2G circuit pack(s) that are required. Record the number of circuit packs on Line 7, Line 8, Line 9, Line 10 and Line 11. Enter ‘none’ if no circuit packs are required.

6 Determine the number of 10/100BT Layer 2 (L2) services that are required, record the number in Line 12. If no 10/100BT L2 services are required, enter ‘none’ on Line 12.

— A maximum of 24 10/100BT L2 ports can be provisioned per 6130 shelf (8 ports for each L2PA1G2 circuit pack). 32 ports can be provisioned if the 225W PSU is used, which would allow 4 L2PA1G2 circuit packs.

— A maximum of 8 100BT or 1000BT ports can be provisioned per 6130 shelf (4 ports each EoPDH circuit pack)

7 Determine the number of 100FX L2 services that are required, record the number in Line 13. If no 100FX L2 services are required, enter ‘none’ on Line 13.

— A maximum of 6 100FX L2 ports can be provisioned per 6130 shelf (2 ports for each L2PA1G2 circuit pack).

8 Determine the number of GE L2 services that are required, record the number in Line 14. If no GE L2 services are required, enter ‘none’ on Line 14.

— A maximum of 6 GE L2 ports can be provisioned per 6130 shelf (2 ports for each L2PA1G2 circuit pack). 8 ports can be provisioned if the 225W PSU is used, which would allow 4 L2PA1G2 circuit packs.

— A maximum of 8 GE ports can be provisioned per 6130 shelf (4 ports each EoPDH circuit pack)

9 Based on the values recorded on Line 12, Line 13 and Line 14, determine the number of L2PA622M and/or L2PA1G2 circuit pack that are required. Record the number of circuit packs on Line 15 and/or Line 16. Enter ‘none’ if no circuit packs are required.

— A maximum of two L2PA622M circuit packs can be equipped per 6130 shelf (With 150W PSU). Four circuit packs if equipped with 225W PSU)

— A maximum of three L2PA1G2 circuit packs can be equipped per 6130 shelf (With 150W PSU). Four circuit packs if equipped with 225W PSU)




Step Action

— A maximum of 2 EoPDH circuit packs can be equipped per 6130 shelf. (With 225W PSU)

— Each L2PA622M or L2PA1G2 circuit pack supports 2 GE or 2 100FX L2 ports in addition to the 8 10/100BT L2 ports.

10 Determine the number of E1/DS1 services that are required, record the number in Line 17. If no E1/DS1 services are required, enter ‘none’ on Line 17.

— A maximum of 112 E1/DS1 ports can be provisioned per 6130 shelf in unprotected mode with the 28xE1/DS1 circuit pack (28 ports for each 28xE1/DS1 circuit packs).

— A maximum of 252 E1 ports can be provisioned per 6130 shelf in unprotected mode with the 63xE1/DS1circuit pack (63 ports for each 63xE1/DS1circuit packs).

— A maximum of 112 E1/DS1 ports can be provisioned per 6130 shelf in unprotected mode (28 ports for each E1/DS1 circuit pack) when slots 4 and 8 are equipped with 28xE1/DS1(W/P) circuit packs and slots 5 and 9 are equipped with 28xE1/DS1 circuit packs.

— A maximum of 56 E1/DS1 ports can be provisioned per 6130 shelf with 1+1 equipment protection (28 ports for each 28xE1/DS1(W/P) circuit packs).

— A maximum of 84 E1/DS1 ports can be provisioned per 6130 shelf with 1:3 equipment protection (28 ports for each 28xE1/DS1(W/P) circuit packs).

11 Determine if you require E1/DS1 circuit packs with connectors on the faceplate of the circuit pack or with connectors on separate I/O modules.

— The 28xE1/DS1 and 63xE1/DS1circuit pack have the E1/DS1 connectors on the faceplate of the circuit pack and the 28xE1/DS1(W/P) circuit pack has connectors on separate I/O modules.

— The 28xE1/DS1(W/P) circuit pack supports 1+1 & 1:N equipment protection and can also be used in unprotected mode. The 28xE1/DS1 circuit pack can only be used in unprotected mode.

12 Determine the number of 28xE1/DS1 or 63xE1/DS1circuit packs that are required based on the number recorded on Line 17 and record the number of 28xE1/DS1 circuit packs in Line 18 or the number of 63xE1/DS1circuit packs in Line 19. Go to step 17.

If Then

E1/DS1 circuit packs with separate I/O modules are required or if E1/DS1 equipment protection is required

go to step 13

E1/DS1 circuit packs with connectors on the faceplate of the circuit pack are required

go to step 12




Step Action

13 Determine the number of 28xE1/DS1(W/P) circuit packs that are required

14 One 84xE1/DS1 1:N I/O modules is required. Enter “1” on Line 22. Enter “0” on Line 21. Go to step 17.

15 Determine the number of 28xE1/DS1 1+1 I/O modules required. Divide the number of 28xE1/DS1(W/P) circuit packs recorded on Line 20 by 2 and round up to the next integer and record the number obtained on Line 21. Enter “0” on Line 22. Go to step 17.

16 Determine the number of 28xE1/DS1 1+1 I/O modules required (when the 28xE1/DS1(W/P) circuit packs are used in unprotected mode). Take the number recorded on Line 20 and record it on Line 21. Enter “0” on Line 22. Go to step 17.

17 Determine the number of E3/DS3 services that are required, record the number in Line 23. If no E3/DS3 services are required, enter ‘none’ on Line 23.

— A maximum of 12 E3/DS3 ports can be provisioned per 6130 shelf (3 ports for each 3xE3/DS3 circuit pack).

— A maximum of 24 E3/DS3 ports can be provisioned per 6130 shelf (6 ports for each Transmux circuit pack).

— A maximum of 6 E3/DS3 ports can be provisioned per 6130 shelf with 1+1 equipment protection.

If Then

1+1 equipment protection is required for E1/DS1 services

Divide the number recorded on Line 17 by 28 and round up to the next integer. This will give the number of working circuit packs required. Multiply this number by 2 (for the protection circuit packs) and record the total number of circuit packs on Line 20. Go to step 15.

1:N equipment protection is required for E1/DS1 services

Divide the number recorded on Line 17 by 28 and round up to the next integer. This will give the number of working circuit packs required (up to 3 working circuit packs can be used per shelf). One circuit pack is also required for the protection slot. Add the number of working circuit packs with the number of protection circuit packs and record the total number of circuit packs (working and protection) on Line 20. Go to step 14

No equipment protection is required for E1/DS1 services (i.e. unprotected)

Divide the number recorded on Line 17 by 28 and round up to the next integer. This will give the number circuit packs required. Record the number of circuit packs on Line 20. Go to step 16.




Step Action

18 Determine if you require E3/DS3 circuit packs with connectors on the faceplate of the circuit pack or with connectors on separate I/O modules.

— The 3xE3/DS3 circuit pack has the E3/DS3 connectors on the faceplate of the circuit pack and the 3xE3/DS3(W/P) circuit pack has connectors on separate I/O modules.

— The 3xE3/DS3(W/P) circuit pack supports 1+1 equipment protection and can also be used in unprotected mode. The 3xE3/DS3 circuit pack can only be used in unprotected mode.

— Transmux can support 1+1 equipment protection. This requires a 3xE3/DS3 1+1 I/O module.

19 Determine the number of 3xE3/DS3(W/P) circuit packs that are required

20 Determine the number of 3xE3/DS3 1+1 I/O modules required. Divide the number recorded on Line 23 by 3 and round up to the next integer. This will give the number of 3xE3/DS3 1+1 I/O modules required. Record the number obtained on Line 26. Go to step 22.

21 Determine the number of 3xE3/DS3 circuit pack that are required. Divide the number recorded on Line 23 by 3 and record the round up integer value on Line 24. Enter ‘none’ if no 3xE3/DS3 circuit pack is required.

If Then

E3/DS3 circuit packs with separate I/O modules are required or if E3/DS3 equipment protection is required

go to step 19

E3/DS3 circuit packs with connectors on the faceplate of the circuit pack are required

go to step 21

If Then

1+1 equipment protection is required for E3/DS3 services

Divide the number recorded on Line 23 by 3 and round up to the next integer. This will give the number of working circuit packs required. Multiply this number by 2 (for the protection circuit packs) and record the total number of circuit packs on Line 25. Go to step 20.

No equipment protection is required for E3/DS3 services (i.e. unprotected)

Divide the number recorded on Line 23 by 3 and round up to the next integer. This will give the number circuit packs required. Record the number of circuit packs on Line 25. Go to step 20.




Step Action

22 Determine the number of STM-1/OC-3 services that are required, record the number in Line 27. If no STM-1/OC-3 services are required, enter ‘none’ on Line 27.

— Up to three 2x622M/8x155M (NT6Q18AAE5) tributary circuit packs can be equipped in a 6130 shelf equipped with the 1x2.5G aggregate cards.

— Up to two 2x622M/8x155M (NT6Q18AAE5) tributary circuit packs can be equipped in a 6130 shelf equipped with the 1x2.5G+4x155M/2x622M aggregate cards.

— For NEBS Radiated Emissions compliancy, in 6130 deployments which include one or more DS-1 I/O cards (NT6Q44AAE5), only one (1) NT6Q18AAE5 circuit pack per 6130 shelf is supported and it must be installed in tributary slot #5.

— Up to four 2x622M/8x155M (NT6Q18ABE5) tributary circuit packs can be equipped in a 6130 shelf

— A maximum of 16 STM-1/OC-3 ports can be provisioned per shelf with redundant 1x2.5G aggregate cards.

— A maximum of 40 STM-1/OC-3 ports can be provisioned per shelf with redundant 1x2.5G+4x155M/8x622M aggregate cards.

23 Determine the number of STM-4/OC-12 services that are required, record the number in Line 28. If no STM-4/OC-12 services are required, enter ‘none’ on Line 28.

— Up to three 2x622M/8x155M (NT6Q18AAE5) tributary circuit packs can be equipped in a 6130 shelf equipped with the 1x2.5G aggregate cards.

— Up to two 2x622M/8x155M (NT6Q18AAE5) tributary circuit packs can be equipped in a 6130 shelf equipped with the 1x2.5G+4x155M/2x622M aggregate cards.

— Up to four 2x622M/8x155M (NT6Q18ABE5) tributary circuit packs can be equipped in a 6130 shelf

— A maximum of 2 STM-4/OC-12 ports can be provisioned per shelf with redundant 1x2.5G aggregate cards.

— A maximum of 12 STM-4/OC-12 ports can be provisioned per shelf with redundant 1x2.5G+4x155M/8x622M aggregate cards.

24 Based on the values recorded in Line 27 and Line 28, determine the number of 2x622M/8x155M and/or 2x622M/8x155M Rev 2 (low power) and/or 2x155M tributary circuit pack(s) that are required. Record the number of circuit packs on Line 29 and/or Line 30 and/or Line 31. Enter ‘none’ on Line 29 and/or Line 30 and/or Line 31 if no circuit packs are required.




Step Action

25 Add the number of tributary circuit packs recorded on Line 15, Line 16 and Line 30.

26 More than one 6130 shelf may be required if the total power consumption of the shelf exceeds the capacity of the PSU. Determine total shelf power consumption. Go to Shelf equipping rules on page 8-5, step 19 and calculate the 6130 shelf power requirements.

— When 2 or more of the L2PA622M and/or L2PA1G2 and/or 2x622M/8x155M (NT6Q18ABE5) circuit packs are used in one 6130 shelf, the total power requirement of the shelf may exceed the 6130 PSU capacity.

27 Add the number of tributary circuit packs recorded on Line 7, Line 8, Line 9, Line 10, Line 11, Line 15, Line 16, Line 18, Line 19, Line 20, Line 24, Line 25, Line 29, Line 30 and Line 31.

Attention: The 6130 chassis has four tributary slots for services. Up to four circuit packs can be added to the chassis. Refer to Shelf equipping rules on page 8-5 for more details.

If the number is Then

2 or greater go to step 26

If the number lower than 2 go to step 27

If the power requirement is Then

150W or more Re-assign some of the services to another 6130 shelf and ensure that the 6130 shelf power requirement does not exceed 150W, then go to step 2 on page 8-49, or use the 225W PSU if it is below 225W.

less than 150W go to step 27

If you need Then

4 tributary circuit packs or less go to step 29

5 tributary circuit packs or more more than one 6130 shelf needs to be ordered. Re-assign some of the services to another 6130 shelf and ensure that up to 4 tributary circuit pack is required per shelf, then go to step 2 on page 8-49




Step Action

28 Ensure that all tributary circuit packs recorded on Line 7, Line 8, Line 9, Line 10, Line 11, Line 15, Line 16, Line 18, Line 19, Line 20, Line 24, Line 25, Line 29, Line 30 and Line 31 are supported by the aggregate card(s) selected in Line 3. Please refer to Table 8-4 for the list of circuit packs supported by the various aggregate cards.

29 Determine the type of E1/DS1 cables required.

30 Determine the number of 64-pin Telco cables for the E1/DS1 interfaces of the 28xE1/DS1 and 28xE1/DS1(W/P) circuit packs.

If you require Then

E1 electrical interfaces at 75 Ohm

Enter ‘75 ohm’ in Line 32.

E1 electrical interfaces at 120 Ohm


DS1 electrical interfaces at 100 Ohm


no electrical E1/DS1 services Enter ‘none’ in Line 32.

If Line 17 is in the range Then

from 1 to 16 Enter ‘1’ in Line 33. Go to step 31








none Enter ‘none’ on Line 33. Go to step 33




Step Action

31 Determine the number of 160-pin Telco cables for the E1 interfaces of the 63xE1/DS1circuit pack.

32 Determine the required length, in meters, for E1/DS1 cables and enter the length in Line 35.

33 Order the 6130 shelf

34 Order one (1) NT6Q70CAE6, 6130 assembly kit.

If Line 17 is in the range Then









none Enter ‘none’ on Line 34. Go to step 33

If Then

Line 2 is “DC” Order one (1) NT6Q60ABE5, 6130 DC system or NT6Q60BAE5

Line 2 is “AC” Then order one (1) NT6Q60AME5, 6130 system kit (without PSU) and two (2) NT6Q41AAE5, 6130 AC PSU circuit pack.




Step Action

35 Order the aggregate circuit pack(s) with 6130 Release 5.0 software.

36 The number of 8xETH circuit pack(s) required is recorded on Line 7. Order this quantity of NT6Q13AC or NT6Q13BAE5 (Ext Temp), 8xETH tributary circuit pack(s).

37 The number of 4x10/100BT+4x100FX L1 circuit pack(s) required is recorded on Line 8. Order this quantity of NT6Q13MAE5 or NT6Q13MBE5, 4x10/100BT+4x100FX L1 tributary circuit pack(s).

38 The number of 4x10/100BT+4x100FX L1 622M circuit pack(s) required is recorded on Line 9. Order this quantity of NT6Q14BAE5, 4x10/100BT+4x100FX L1 622M tributary circuit pack(s).

39 The number of 2xGE+8x10/100BT L1 1.2G circuit pack(s) required is recorded on Line 10. Order this quantity of NT6Q22AAE5, 2xGE+8x10/100BT L1 1.2G tributary circuit pack(s).

40 The number of 2xGE circuit pack(s) required is recorded on Line 11. Order this quantity of NT6Q20ABE5 or NT6Q20BAE5 (Ext Temp), 2xGE tributary circuit pack(s).

41 The number of L2PA622M circuit pack(s) required is recorded on Line 15. Order this quantity of NT6Q21AAE5 or NT6Q21ABE5 L2PA622M tributary circuit pack(s).

42 The number of L2PA1G2 circuit pack(s) required is recorded on Line 16. Order this quantity of NT6Q21GBE5, L2PA tributary circuit pack(s).

43 The number of 28xE1/DS1 circuit pack(s) required is recorded on Line 18. Order this quantity of NT6Q10ABE5 or NT6Q10BAE5 (Ext Temp), 28xE1/DS1 tributary circuit pack(s).

If Then order

Line 3 is ‘one NT6Q66ADE5 2x155/622M aggregate circuit pack’

one (1) NT6Q66ADE5, 2x155/622M aggregate circuit pack, and

one (1) NT6Q70AE, Filler Panel for aggregate slot 7

Line 3 is ‘two NT6Q67ADE5 1x155/622M aggregate circuit packs’

two (2) NT6Q67ADE5, 1x155/622M aggregate circuit packs

Line 3 is ‘two NT6Q68ADE5 1x2.5G aggregate circuit packs’

two (2) NT6Q68ADE5, 1x2.5G aggregate circuit packs

Line 3 is ‘two NT6Q69ADE5 1x2.5G+4x155M/2x622M aggregate circuit packs’

two (2) NT6Q69ADE5, 1x2.5G+4x155M/2x622M aggregate circuit packs




Step Action

44 The number of 63xE1/DS1circuit pack(s) required is recorded on Line 19. Order this quantity of NT6Q11AAE5, 63xE1/DS1 tributary circuit pack(s).

45 The number of 28xE1/DS1(W/P) circuit pack(s) required is recorded on Line 20. Order this quantity of NT6Q10MAE5, 28xE1/DS1(W/P) tributary circuit pack(s).

46 The number of 28xE1/DS1 1+1 I/O module required is recorded on Line 21. Order this quantity of NT6Q44AAE5, 28xE1/DS1 1+1 I/O module(s).

47 The number of 28xE1/DS1 1:N I/O module required is recorded on Line 22. Order this quantity of NT6Q44CAE5, 28xE1/DS1 1:N I/O module(s).

48 The number of 3xE3/DS3 circuit pack(s) required is recorded on Line 24. Order this quantity of NT6Q12ACE5 or NT6Q12BAE5 (Ext Temp), 3xE3/DS3 tributary circuit pack(s).

49 The number of 3xE3/DS3(W/P) circuit pack(s) required is recorded on Line 25. Order this quantity of NT6Q12MAE5, 3xE3/DS3(W/P) circuit pack(s).

50 The number of 3xE3/DS3 1+1 I/O module(s) required is recorded on Line 26. Order this quantity of NT6Q44BAE5, 3xE3/DS3 1+1 I/O module(s).

51 The number of 2x155M tributary circuit pack(s) required is recorded on Line 29. Order this quantity of NT6Q17ACE5, 2x155M tributary circuit pack(s).

52 The number of 2x622M/8x155M or 2x622M/8x155M Rev 2 (low power) tributary circuit pack(s) required is recorded on Line 30 and or Line 31. Order this quantity of NT6Q18AAE5 (2x622M/8x155M) or NT6Q18ABE5 (2x622M/8x155M Rev 2 (low power)) tributary circuit pack(s).

53 Order the small form-factor pluggable (SFP) modules.

Refer to Table 8-12 on page 8-23 and Shelf equipping rules on page 8-5 for orderable part numbers and application rules for the small form-factor pluggable modules.

54 Determine the next step:

If Line 32 is Then

75 ohm Go to step 55.

120 ohm Go to step 57

100 ohm Go to step 59

none Go to step 60




Step Action

55 Order the 75Ohm BNC termination panel and the E1 cables for the 75 ohm termination panel for the E1/DS1 services provided by the 28xE1/DS1 and/or 28xE1/DS1(W/P) circuit packs. Right and/or left routing cables maybe required depending on the application. Refer to Site engineering recommendations steps 7 and 8 on page 8-17 for details on E1/DS1 cable routing.

56 Order the E1 75 Ohm cables for the 63xE1/DS1circuit pack. Refer to Site engineering recommendations steps 7 and 8 on page 8-17 for details on E1/DS1 cable routing.

Go to step 60.

The number recorded in Line 33 is the total number of 64-pin Telco cables required for E1/DS1 services on the 28xE1/DS1 and 28xE1/DS1(W/P) circuit packs. The number in Line 33 is equal to the number of left routing cables + the number of right routing cables.

Order the number of NT6Q71EA, 75 ohm BNC termination panel as specified on Line 33.

Based on the Site engineering recommendations steps 7 and 8 on page 8-17, determine the number of left routing cables and the number of right routing cables required.

If Line 35 is Then order the number of right routing cables times of

1 or less one (1) NT6Q75AA (Right routing - 1 meter cable)

between 1 and 2 one (1) NT6Q75BA (Right routing - 2 meter cable)

between 2 and 5 one (1) NT6Q75CA (Right routing - 5 meter cable)

If Line 35 is Then order the number of left routing cables times of

1 or less one (1) NT6Q74AA (Left routing - 1 meter cable)

between 1 and 5 one (1) NT6Q74CA (Left routing - 5 meter cable)

between 5 and 10 one (1) NT6Q74DA (Left routing - 10 meter cable)

The number recorded in Line 34 is the total number of 160-pin Telco cables required for E1/DS1 services on the 63xE1/DS1circuit pack.

If Line 35 is Then order the number of cables times of

5 or less one (1) NTTC41ABE6 (E1 High Density I/O cable 75 ohm, 5 m)

between 5 and 10 one (1) NTTC41ACE6 (E1 High Density I/O cable 75 ohm, 10 m)

between 10 and 20 one (1) NTTC41AEE6 (E1 High Density I/O cable 75 ohm, 20 m)




Step Action

57 Order the E1 cables for the 120 ohm application for the E1/DS1 services provided by the 28xE1/DS1 and 28xE1/DS1(W/P) circuit packs:

58 Order the E1 cables for the 120 ohm application for the E1 services on the 63xE1/DS1circuit pack. Following cable supports DS1 services.

Go to step 60.

The number recorded in Line 33 is the total number of 64-pin Telco cables required for E1/DS1 services on the 28xE1/DS1 and 28xE1/DS1(W/P) circuit packs. The number in Line 33 is equal to the number of left routing cables + the number of right routing cables.



5 or less one (1) NT6Q73BA (Right routing - 5 meter cable)

between 5 and 10 one (1) NT6Q73CA (Right routing - 10 meter cable)

between 10 and 15 one (1) NT6Q73DA (Right routing - 15 meter cable)

between 15 and 20 one (1) NT6Q73EA (Right routing - 20 meter cable)


5 or less one (1) NT6Q72BA (Left routing - 5 meter cable)

between 5 and 10 one (1) NT6Q72CA (Left routing - 10 meter cable)

between 10 and 15 one (1) NT6Q72DA (Left routing - 15 meter cable)

between 15 and 20 one (1) NT6Q72EA (Left routing - 20 meter cable)

The number recorded in Line 34 is the total number of 160-pin Telco cables required for E1/DS1 services on the 63xE1/DS1circuit pack. The number in Line 34 is equal to the number of right routing cables.

Based on the Site engineering recommendations steps 7 and 8 on page 8-17, determine the number of right routing cables required.

If Line 35 is Then order the number cables times of

5 or less one (1) NTTC41BBE6 (E1 High Density I/O cable 120 ohm, 5 m)

between 5 and 10 one (1) NTTC41BCE6 (E1 High Density I/O cable 120 ohm, 10 m)

between 10 and 20 one (1) NTTC41BEE6 (E1 High Density I/O cable 120 ohm, 20 m)




Step Action

59 Order the DS1 cables for the E1/DS1 services:

60 Order one (1) NT6Q83DA CD-ROM copy of Release 5.0 software for each site.

61 Order 6130 Release 5.0 software certificates. Order one NT6Q85DA for each 6130 shelf.

62 Order 6130 RTU licences. Order one NT6Q82AA for each 6130 shelf.

63 For each empty slot of the chassis, order the appropriate filler panel. Refer to Table 8-8 on page 8-18 and Shelf equipping rules on page 8-5 for orderable part numbers and application rules.

64 Repeat this procedure for each network element at this site. When all network elements have been ordered for this site, continue the ordering process with Procedure 8-2 on page 8-65.

—end—

The number recorded in Line 33 is the total number of 64-pin Telco cables required for E1/DS1 services. The number in Line 33 is equal to the number of left routing cables + the number of right routing cables. If the DS1 service is used with the 63xE1/DS1 circuit pack order the NTTC41BxE6 cable.



15 or less one (1) NT6Q73QA (Right routing - 15 meter cable)

between 15 and 30 one (1) NT6Q73TA (Right routing - 30 meter cable)


15 or less one (1) NT6Q72QA (Left routing - 15 meter cable)

between 15 and 30 one (1) NT6Q72TA (Left routing - 30 meter cable)



Table 8-336130 shelf ordering worksheet

Line Description Value

Line 1 Software release required 4.0

Line 2 Power configuration required (AC or DC)

Line 3 Aggregate circuit pack(s) required

Line 4 Number of 10/100BT L1 Ethernet Private Line (EPL) services

Line 5 Number of 100FX L1 EPL services

Line 6 Number of GE L1 EPL services

Line 7 Number of 8xETH circuit pack(s)

Line 8 Number of 4x10/100BT+4x100FX L1 circuit pack(s)

Line 9 Number of 4x10/100BT+4x100FX L1 622M circuit pack(s)

Line 10 Number of 2xGE+8x10/100BT L1 1.2G circuit pack(s)

Line 11 Number of 2xGE circuit pack(s)

Line 12 Number of 10/100BT Layer 2 (L2) services

Line 13 Number of 100FX L2 services

Line 14 Number of GE L2 services

Line 15 Number of L2PA622M circuit pack(s)

Line 16 Number of L2PA1G2 circuit pack(s)

Line 17 Number of E1/DS1 services

Line 18 Number of 28xE1/DS1 circuit pack(s)

Line 19 Number of 63xE1/DS1circuit pack(s)

Line 20 Number of 28xE1/DS1(W/P) circuit pack(s)

Line 21 Number of 28xE1/DS1 1+1 I/O modules

Line 22 Number of 84xE1/DS1 1:N I/O modules

Line 23 Number of E3/DS3 services

Line 24 Number of 3xE3/DS3 circuit pack(s)

Line 25 Number of 3xE3/DS3(W/P) circuit pack(s)

Line 26 Number of 3xE3/DS3 1+1 I/O modules

Line 27 Number of STM-1/OC-3 services



Line 28 Number of STM-4/OC-12 services

Line 29 Number of 2x155M circuit pack(s)

Line 30 Number of 2x622M/8x155M circuit pack(s)

Line 31 Number of 2x622M/8x155M Rev2 (low power) circuit pack(s)

Line 32 Impedance of electrical E1/DS1 interfaces (75 Ohm, 120 Ohm, 100 Ohm)

Line 33 Number of 64-pin Telco cables for E1/DS1 services (1, 2, 3, 4, 5, 6, 7, 8, none)

Line 34 Number of 160-pin Telco cables for E1/DS1 services (1, 2, 3, 4, 5, 6, 7, 8, none)

Line 35 Length for the E1/DS1 cables

Table 8-33 (continued)6130 shelf ordering worksheet




Procedure 8-2Ordering cables, documentation, and services

Use this procedure to order cables, documentation, and services for the 6130 equipment ordered in Procedure 8-1 on page 8-48. Repeat this procedure for each site in the 6130 network.

Action

Step Action

Attention: Use a photocopy of Table 8-34 on page 8-68 for this procedure. Line references in this procedure refer to this table unless otherwise noted.

1 Record site specific information on Line 1 through Line 8 of Table 8-34 on page 8-68.

Before you start• Complete a network design, including a DCN and a synchronization plan.

• Read 6130 network element configuration rules on page 8-2.

• Photocopy Table 8-34 on page 8-68 and Table 8-35 on page 8-69 (if required).

Procedure tasks• Record site specific information (step 1).

• Order power cables (step 2).

• Order optical fiber patch cords (step 4), Ethernet cables (step 5) and E3/DS3 cables (step 6)

• Order OAM cables (environmental alarm, DCN, and synchronization) (step 8 to step 9).

• Order documentation (step 10) and Site Manager for 6100 (step 11).

• Order services (step 12).

Expected results • You have a complete list of cables, documentation, and services for an 6130 site.

• If the expected results do not occur:

— Review the network design and repeat the procedure.

— Contact your next level of support.



Procedure 8-2 (continued)Ordering cables, documentation, and services

Step Action

2 Order DC power cables for the number of 6130 NEs specified in Line 2. Order the appropriate DC cable for the region, as specified in Line 1, and for the length required, as shown on Line 4. Two DC power cables must be ordered for each network element.

Refer to Table 8-25 on page 8-41 and Bay equipping rules on page 8-5 for orderable codes and application rules.

3 Order AC power cables for the number of 6130 NEs specified in Line 3. Order the appropriate AC cable for the region, as specified in Line 1. Two AC power cables must be ordered for each network element.

Refer to Table 8-25 on page 8-41 and Bay equipping rules on page 8-5 for orderable codes and application rules.

4 Order fiber patchcords. Refer to Table 8-20 on page 8-36 and Table 8-21 on page 8-38 for orderable codes and application rules.

Attention: The STM-1/4/16/OC-3/12/48, 100FX and GE optical SFP modules on the 6130 support duplex LC connections. Ciena recommends the use of duplex patchcords wherever allowed by the subtending equipment.

5 Order Ethernet cables for the 10/100BT ports on tributary circuit packs. Refer to Table 8-19 on page 8-35 for orderable codes.

6 Order the coaxial cables and connectors for the E3/DS3 ports on tributary circuit packs. Refer to E3/DS3 cable assemblies on page 8-33 for orderable codes.

7 Order the coaxial cables and connectors for the STM-1e ports on tributary circuit packs. Refer to Table 8-18 on page 8-34 for orderable codes.

8 Order environmental alarm kits. Order one environmental alarm kit for the number 6130 network elements specified on Line 5. Refer to Table 8-23 on page 8-40 for orderable part numbers and application rules.

9 Order the number of LAN 10/100 Ethernet cables specified in Line 6 to connect to the 6130 network elements to the DCN.

A regular straight 10/100 Ethernet cable (RJ-45 to HUB RJ-45) will accommodate this connection. Refer to Table 8-22 on page 8-39 for orderable part numbers and application rules.



Procedure 8-2 (continued)Ordering cables, documentation, and services

Step Action

10 Order documentation. Ciena recommends that one CD-ROM be ordered for each site. Alternatively, a paper library is available. Refer to Table 8-30 on page 8-45 for orderable codes and application notes.

11 6100 Site Manager is available for nodal management of the 6130 NE. If required, order the 6100 Site Manager software CD-ROM, RTU license and documentation (fundamentals guide).

— Refer to Table 8-28 on page 8-43 for orderable codes and application notes. The 6100 Site Manager is available only on CD-ROM and it needs to be ordered separately.

— The nodal management can be done with 6100 Site Manager or with the 6130 Web User Interface (WUI). The 6130 WUI is built-in the network element software and does not need to be ordered separately.

12 Staging services are available to simplify installation of 6130 equipment. Refer to Engineering and support services on page 8-44 for a description of this service.

Ciena offers a selection of services to help you plan, deploy, operate, and maintain your optical networks. For more information about these services, contact your Ciena representative or visit www.ciena.com/services.

13 Repeat this procedure for the next site in the network deployment, until all sites have been completed.

—end—



Table 8-34Worksheet for ordering cables, documentation and services for 6130 network elements


Line 1 Region of deployment for 6130 shelves (North America or other)?

Line 2 Total number of 6130 shelves using DC PSUs at this site?

Line 3 Total number of 6130 shelves using AC PSUs at this site?

Line 4 Length required for the DC power cables (3M or 10M)?

Line 5 Total number of 6130 shelves requiring environmental alarm cables?

Line 6 Total number of 6130 shelves connected to the DCN directly via 10/100BT Ethernet at this site?

Line 7 Are external synchronization interfaces required at this site?

Line 8 Are 75 ohm or 120/100 ohm interfaces required for ESI connector at this site?



Table 8-35Ordering summary

Description PEC/RoHS Code

Quantity

6130 chassis and components

• 6130 System kit

— 6130 DC System; chassis, dual PSU, Fan, OAM card, top I/O Fillers and 19” flange

— 6130 System; chassis, Fan, OAM card, top I/O fillers and 19” flange

— 6130 DC System Ext Temp; Chassis, dual PSU, std OAM & fan

• 6130 Power Supply Unit

— 6130 DC PSU 225W

— 6130 DC PSU 150W

— 6130 AC PSU 150W

• 6130 Fan module and Air Filter

— 6130 Fan Tray with Filter

— 6130 Hinged Fan Tray with Filter

— 6130 Fan Tray, Ext Temp (with Filter)

— Air Filter

• 6130 OAM circuit pack

— 6130 OAM circuit pack

— 6130 Standard OAM, Ext Temp Circuit Pack

• 6130 Filler cards

— Filler Panel for tributary slot

— 6130 Top Right IO Filler Panel

— 6130 Top Left IO Filler Panel

— 6130 Aggregate Filler Panel

NT6Q60ABE5

NT6Q60AME5

NT6Q60BAE5

NT6Q40BAE5

NT6Q40AAE5

NT6Q41AAE5

NT6Q42AAE5

NT6Q42ABE5

NT6Q42BAE5

NT6Q70DAE6

NT6Q43ABE5

NT6Q43BAE5

NT6Q70AAE6

NT6Q70AHE6

NT6Q70AIE6

NT6Q70AEE6

6130 shelf installation kit

• 6130 Assy Kit - cable routing bracket, 21”/23” flange, rack mounting screws, cage nuts, earthing cable

• 6130 - 19” Mounting Kit - brackets, screws & cage nuts

NT6Q70CAE6

NT6Q70CBE6

Aggregate circuit packs with 6130 Release 4.0 software



• 1x2.5G aggregate circuit pack

• 1x2.5G+4x155M/2x622M aggregate circuit pack

NT6Q66ADE5

NT6Q67ADE5

NT6Q68ADE5

NT6Q69ADE5



Aggregate circuit packs with 6130 Release 5.0 software

• 6130 R5.0 2x622M Aggregate (one per shelf)

• 6130 R5.0 1x622M Aggregate (1+1 protected per shelf)

• 6130 R4.1 1x2488M Aggregate (1+1 protected per shelf)

• 6130 R4.1 1x2488M Aggregate, no DCC (1+1 protected per shelf)

• 6130 R5.0 1x2488M/2x622M/4x155M Agg (1+1 protected per shelf)

• 6130 R5.0 1x2488M/2x622M/4x155M Agg, Ext Temp (1+1 protected per shelf)

NT6Q66AEE5

NT6Q67AEE5

NT6Q68AEE5

NT6Q68MEE5

NT6Q69AEE5

NT6Q69BAE5

Table 8-35 (continued)Ordering summary


Quantity



Tributary interface circuit packs

• 10/100BT and 100FX L1 circuit packs

— 8xETH circuit pack

— 8xETH circuit pack (Ext Temp)

— 4x10/100BT+4x100FX L1 circuit pack

— 4x10/100BT+4x100FX L1 circuit pack - Rev. 2

— 4x10/100BT+4x100FX L1 622M circuit pack

• GE circuit pack

— 2xGE circuit pack

— 2xGE circuit pack (Ext Temp)

• GE and 10/100BT L1 circuit pack

— 2xGE+8x10/100BT L1 1.2G circuit pack

• GE, 100FX and 10/100BT L2 circuit pack

— L2PA622M circuit pack

— L2PA622M-rev2 circuit pack

— L2PA1G2 circuit pack

— L2PA1G2-rev2 circuit pack

— 8xGE EoPDH circuit pack

• E1/DS1 circuit packs


— 28xE1/DS1 circuit pack (Ext Temp)

— 63xE1 circuit pack

— 28xE1/DS1(W/P) circuit pack

• E3/DS3 circuit pack


— 3xE3/DS3 circuit pack - Rev. 2

— 3xE3/DS3 circuit pack (Ext Temp)

— 3xE3/DS3(W/P) circuit pack

— Transmux

• STM-1/OC-3 and STM-4/OC-12 circuit packs

— 2x155M circuit pack

— 2x622M/8x155M circuit pack

— 2x622M/8x155M -Rev2 (Low Power) circuit pack

I/O modules

• E1/DS1 I/O modules

— 28xE1/DS1 1+1 I/O module

— 84xE1/DS1 1:N I/O module

• E3/DS3 I/O modules

— 3xE3/DS3 1+1 I/O module

NT6Q13ACE5

NT6Q13BAE5

NT6Q13MAE5

NT6Q13MBE5

NT6Q14BAE5

NT6Q20ABE5

NT6Q20BAE5

NT6Q22AAE5

NT6Q21AAE5

NT6Q21ABE5

NT6Q21GAE5

NTNT6Q23AE5

E56Q21GBE5

NT6Q10ABE5

NT6Q10BAE5

NT6Q11AAE5

NT6Q10MAE5

NT6Q12ABE5

NT6Q12ACE5

NT6Q12BAE5

NT6Q12MAE5

NT6Q12NAE5

NT6Q17ACE5

NT6Q18AAE5

NT6Q18ABE5

NT6Q44AAE5

NT6Q44CAE5

NT6Q44BAE5



Quantity



Pluggable modules

• STM-1/OC-3 SFPs

— STM-1/OC-3SR-0 (multimode) 1310 nm enhanced SFP module (Ext Temp)

— STM-1/OC-3 IR1/S1.1 1310 nm XCT enhanced SFP module (Ext Temp)

— STM-1/OC-3 LR1/L1.1 1310 nm XCT enhanced SFP module (Ext Temp)

— STM-1/OC-3 LR2/L1.2 1550 nm XCT enhanced SFP module (Ext Temp)

• STM-1/4/OC-3/12 SFPs

— OC-3/12/STM-1/4 IR1/S1.1_S4.1 1310 nm XCT enhanced SFP module

— OC-3/12/STM-1/4 IR-1 / S-1.1_S-4.1, 1310nm, 3.3V, -40/+85C, SFP, 20pins, LC, Enhanced MSA E6

• STM-4/OC-12 SFPs

— STM-4/OC-12 LR1/L4.1 1310 nm XCT enhanced SFP module

— STM-4/OC-12 LR2/L4.2 1550 nm XCT enhanced SFP module

• STM-16/OC-48 SFPs

— STM-16/OC-48 SR1/I16.1 1310 nm XCT enhanced SFP

— STM-16/OC-48 IR1/S16.1 1310 nm XCT enhanced SFP

— STM-16/OC-48 LR1/L16.1 1310 nm XCT enhanced SFP

— STM-16/OC-48 LR2/L16.2 1550 nm XCT enhanced SFP

• STM-1/4/16/OC-3/12/48 CWDM SFPs

— STM-1/4/16/OC-3/12/48 CWDM 1471 nm SFP module








• STM-1e (electrical) SFPs

— STM-1e enhanced SFP module

• 100Base SFPs

— 100Base-LX10, 1310, 10 km SFP module

— 100Base-BX10-U bidirectional-upstream, 1310 nm Tx, 10 km SFP module

— 100Base-BX10-D bidirectional-downstream, 1530 nm Tx, 10 km SFP module

NTTP02AD

NTTP02CD

NTTP02ED

NTTP02FD

NTTP04CF

NTTP04CDE6

NTTP05EF

NTTP05FF

NTTP03BF

NTTP03CF

NTTP03EF

NTTP03FF

NTK590LH

NTK590MH

NTK590NH

NTK590PH

NTK590QH

NTK590RH

NTK590SH

NTK590TH

NTTP60AE

NTTP08SD

NTTP09BD

NTTP10BD



Quantity



• STM-16/OC-48 DWDM SFPs— STM-16/OC-48 1528.77 nm SFP module

— STM-16/OC-48 1530.33 nm SFP module




































NTK585AA

NTK585AE

NTK585AG

NTK585AJ

NTK585AL

NTK585AN

NTK585AQ

NTK585AS

NTK585AU

NTK585AW

NTK585BA

NTK585BC

NTK585BE

NTK585BG

NTK585BJ

NTK585BL

NTK585BN

NTK585BQ

NTK585BS

NTK585BW

NTK585BY

NTK585CA

NTK585CC

NTK585CE

NTK585CG

NTK585CJ

NTK585CL

NTK585CN

NTK585CS

NTK585CU

NTK585CW

NTK585CY

NTK585DA

NTK585DC

NTK585DE

NTK585DG

NTK585DJ



Quantity



Pluggable modules (continued)





• GE SFPs

— GE SX SFP module

— GE LX SFP module

— 1000Base-BX10-U bidi-upstream, 1310 nm Tx, 10 km SFP

— 1000Base-BX10-D bidi-downstream, 1490 nm Tx, 10 km SFP

— GE Electrical 1000-BaseT SFP module

— GE SX, 850nm,SFP module

— GE 1000-BaseZX 1550nm XCT Enhanced SFP Module

NTK585DN

NTK585DQ

NTK585DS

NTK585DU

NTTP01AFE6

NTTP01CF

NTTP58BD

NTTP59BD

NTTP61AAE6

NTTP06AF

NTTP07FFE6

— GE/FC100 1.25 Gbit/s 24 dB CWDM 1471 nm SFP module








NTK591LBNTK591MB

NTK591NB

NTK591PB

NTK591QB

NTK591RB

NTK591SB

NTK591TB



Quantity



Electrical interface hardware

• E1 interface conversion hardware

— 75 ohm BNC Term Panel, 16 channel

— Telco to Telco 1M Cable - Right Routing



— Telco to Telco 1M Cable - Left Routing

—

— Telco to Telco 5M Cable - Left Routing

— Telco to Telco 10M Cable - Left Routing• E1 cable assemblies

— 120Ohm Telco 5M Cable - Right Routing




— 120Ohm Telco 5M Cable - Left Routing




— E1 High Density I/O cable 75 ohm, 5 M






• DS1 cable assemblies



• E3/DS3 cable assemblies

— BNC Connector (735A)

— DS3 735A Coaxial Cable - 10M BNC



— 75Ohm 10M Cable Assembly, SMB Male - BNC Male, RG59 Equivalent

NT6Q71EA

NT6Q75AAE6

NT6Q75BAE6

NT6Q75CAE6

NT6Q74AAE6

NT6Q74CAE6

NT6Q74DAE6

NT6Q73BAE6

NT6Q73CAE6

NT6Q73DAE6

NT6Q73EAE6

NT6Q72BAE6

NT6Q72CAE6

NT6Q72DAE6

NT6Q72EAE6

NTTC41ABE6

NTTC41ACE6

NTTC41AEE6

NTTC41BBE6

NTTC41BCE6

NTTC41BEE6

-

-

N0104114

NT7E43BBE6

NT7E43BDE6

NT7E43BGE6

NT6Q78AAE6



Quantity



Software and licences

• 6130 R4.0 CD-ROM

• 6130 R4.1 CD-ROM

• 6130 R5.0 CD-ROM

• Right to use licences

— 6130 R4.0 SW Certificate 1/NE

— 6130 Base SW RTU 1/NE



NT6Q83DA

NT6Q83DB

NT6Q83EA

NT6Q85DA

NT6Q82AA

NT6Q85DB

NT6Q85EA

Site Manager for 6100 software and license (note that some documentation are included in the TP CD-ROM and is here as a reference purpose)

• Site Manager for 6100 Rel 3.0 CD-ROM

• Site Manager for 6130 Right to use license

• Site Manager for 6100 Rel 3.0 Fundamentals

• 6100 Site Manager Rel 4.0 Installation and User Guide

• 6100 Site Manager CD Rel 4.0

NT6Q90AC

NT6Q90ZB

NT6Q91AC

NT6Q91AD

NT6Q90AD

Engineering and support services

• Hot staging for 6130 N/A

Documentation

• 6130 R5.0 technical publication (CD-ROM) NT6Q64BF

• Change application procedures

— 6130 Upgrade CAP from Rel. 3.0/3.0.1 to Rel. 4.0

— 6130 Upgrade CAP from Rel4.0 to Rel4.1

— 6130 Upgrade CAP from Rel4.0 to Rel5.0

NT6Q93ME

NT6Q93MF

NT6Q93MG



Quantity



Cables

• Optical fiber patch cords (add length and code as appropriate, see Table 8-21 on page 8-38 for details).E6 codes are RoHS compliant, L6 codes are Low Smoke Zero Halogen (LSZH) and RoHS compliant.

— Optical patchcords, LC-LC, SM, Simplex

— Optical patchcords, LC-SC, SM, Simplex

— Optical patchcords, LC-FC, SM, Simplex

— Optical patchcords, LC-ST, SM, Simplex

— Optical patchcords, LC-LC, SM, Duplex

— Optical patchcords, LC-SC, SM, Duplex

— Optical patchcords, LC-FC, SM, Duplex

— Optical patchcords, LC-ST, SM, Duplex

— Optical patchcords, LC-LC, MM 50 micron, Simplex

— Optical patchcords, LC-SC, MM 50 micron, Simplex

— Optical patchcords, LC-FC, MM 50 micron, Simplex

— Optical patchcords, LC-ST, MM 50 micron, Simplex

— Optical patchcords, LC-LC, MM 50 micron, Duplex

— Optical patchcords, LC-SC, MM 50 micron, Duplex

— Optical patchcords, LC-FC, MM 50 micron, Duplex

— Optical patchcords, LC-ST, MM 50 micron, Duplex

NTTC50AxE6NTTC50AxL6

NTTC50BxE6NTTC50BxL6

NTTC50CxE6NTTC50CxL6

NTTC50DxE6NTTC50DxL6















Quantity



• Optical fiber patch cords (continued)

— Optical patchcords, LC-LC, MM 62.5 micron, Simplex

— Optical patchcords, LC-SC, MM 62.5 micron, Simplex

— Optical patchcords, LC-FC, MM 62.5 micron, Simplex

— Optical patchcords, LC-ST, MM 62.5 micron, Simplex

— Optical patchcords, LC-LC, MM 62.5 micron, Duplex

— Optical patchcords, LC-SC, MM 62.5 micron, Duplex

— Optical patchcords, LC-FC, MM 62.5 micron, Duplex

— Optical patchcords, LC-ST, MM 62.5 micron, Duplex

— Optical patchcords, LC-LC, Mode Conditioning 50 micron, Duplex

— Optical patchcords, LC-SC, Mode Conditioning 50 micron, Duplex

— Optical patchcords, LC-FC, Mode Conditioning 50 micron, Duplex

— Optical patchcords, LC-ST, Mode Conditioning 50 micron, Duplex

— Optical patchcords, LC-LC, Mode Conditioning 62.5 micron, Duplex

— Optical patchcords, LC-SC, Mode Conditioning 62.5 micron, Duplex

— Optical patchcords, LC-FC, Mode Conditioning 62.5 micron, Duplex

— Optical patchcords, LC-ST, Mode Conditioning 62.5 micron, Duplex



















Quantity



• Synchronization cables

— Clock (BITS) Cable (120/100 ohm)

— Clock (BITS) Cable (inc 75 ohm convertor)

NT6Q71ACE6

NT6Q71AEE5

• Power and earthing cable assemblies

— 6130 - DC Cable Kit - 3M

— 6130 - DC Cable Kit - 10M

— 6130 - DC Cable Kit - 3M North America

— 6130 - DC Cable Kit - 10M North America

— Earthing Cable

— Ciena Euro/C13 2 meter AC cord

— Ciena Danish/C13 2 meter AC cord

— Ciena Israel/C13 2 meter AC cord

— Ciena Italian/C13 2 meter AC cord

— Ciena Swiss/C13 2 meter AC cord

— Ciena U.K./C13 2 meter AC cord

— Ciena North America/C13 2.5 meter AC cord

NT6Q59CAE6

NT6Q59DAE6

-

-

NT6Q71AAE6

NTK955CBE6

NTK955CCE6

NTK955CEE6

NTK955CFEE6

NTK955CGE6

NTK955CHE6

NTK955CKE6

• STM-1e cable assemblies and connectors

— Cable assembly, co-axial, DIN 1.0/2.3, RG179DT cable, single, 10 m






— Connector coax, BNC 75 ohm, male, straight plug for use with RG179DT cable

— BNC Connector (735A)

NTTC04AAE6

NTTC04ABE6

NTTC04ACE6

NTTC04ADE6

NTTC04AEE6

NTTC04AFE6

N0104109

N0104114

• Ethernet cables for LAN, Craft ports on OAM module and 10/100BT ports on tributary circuit packs (Shielded Twisted Pair -STP)

— Cable assembly, STP Cat 5E, RJ45, TIA568, crossover, single, 5 m

— Cable assembly, STP Cat 5E, RJ45, TIA568, crossover, single, 30 m

NTTC09CAE6

NTTC09CEE6



Quantity




9-1

Technical assistance 9-

This chapter includes information on how to contact Ciena for technical assistance.Table 9-1Topics in this chapter

Technical assistance topics Page

Technical support and information 9-2

Ciena web site 9-2

CE mark 9-2

Field return information 9-3


9-2 Technical assistance

Technical support and informationFor technical support and information from Ciena, refer to the following table.

Ciena web siteYou can also contact us through the Ciena web site at: www.ciena.com. Select the link Support.

CE markThe following is an example of the Conformité Européenne (CE) mark indicating that all electromagnetic compatibility (EMC) and other electrotechnical requirements are met and that the product complies with all applicable standards.

Customer Technical Support/Warranty

In North America 1-800-CIENA24 (243-6224)410-865-4961

In Central and Latin America 800-CIENA-24-7 (800-243-6224-7)410-865-4944 (USA)

In Europe, Middle East,and Africa

800-CIENA-24-7 (800-243-6224-7)+44-207-012-5508

In Asia-Pacific 800-CIENA-24-7 (800-243-6224-7)+81-3-6367-3989+91-124-4340-600

This product/product family complies with the provisions of the Low Voltage Directive 73/23/EEC, and with the essential protection requirements of the EMC Directive 89/336/EEC as amended by 92/31/EEC, when it is properly installed and maintained and when it is used for the purposes for which it is intended.


Technical assistance 9-3

Field return information Complete the following Field Return Information Form and include the form when returning any damaged circuit packs to the factory. Insert the completed form into an anti-static bag. Attach this bag to the failed circuit pack.

Attention: Some of the information that you must provide (such as alarms raised) require you to log in to the network element.

Field Return Information Form

Customer Identification

Customer name:

Site location:

Originator name:

Originator phone number:

Originator pager number:

Project manager name:

Project manager phone number:

Circuit pack description

PEC:

Release:

Serial number:

NE physical slot number (shelf # and slot #):

Network element

NE name:

NE number:

NE type:

NE configuration:

NE application load release:

Failure symptoms

List of raised alarms related to the failed circuit pack:


9-4 Technical assistance

Field Return Information Form (continued)

Failure data

LED status:

Optical input power at the receive interface: __ dBm

Optical output power at the transmit interface: __ dBm

Failure time

Troubleshooting data

Visual inspection of the backplane pins:

Tested against other positions:

Slot #:___ Results:___ Slot #:___ Results:___

Slot #:___ Results:___ Slot #:___ Results:___

Actions performed to clear problems:

Internal pigtail cleaned:

External pigtail cleaned:

Special instructions:

General comments:

Tracking information

Change request (CR) number:

Emergency recovery (ER) contact name:

Emergency recovery (ER) contact telephone number:


10-1

Appendix A: Data communications planning 10-

This chapter provides an overview of 6130 network data communications. Table 10-1 lists the topics covered in this chapter.

This Appendix provides information on typical DCN configurations/models and provides some examples and guidance on provisioning different configurations. For general information about the 6130 data communication architecture and features, refer to OAM&P description on page 6-1.


Topic Page

Introduction 10-2

OAM&P Ports 10-3

Network Interface 10-4

STM-1/4/16/OC-3/12/48 Data Communication Channel 10-7

IP communication 10-12

OSI data communications 10-17

Application protocols 10-23

Diagnostic commands 10-24

Firewall considerations 10-25

Engineering guidelines 10-25

Supported DCN design examples 10-28

IP networks, addressing, and masks 10-95

IP routing protocols 10-99


10-2 Appendix A: Data communications planning

The Data Communications Network Planning Guide, NTR710AM provides information on DCN planning for some OSI-based Ciena products. This guide includes general information on OSI data communications and addressing and can be used as a reference for OSI data communications information.

Introduction6130 is an IP managed optical network element (NE), which has the capabilities to communicate through both TCP/IP Internet Protocol (IP) and OSI Connectionless Network Protocol (CLNP) based networks.

Connectivity of the 6130 network element to its management system can be achieved through:

• the LAN port (10/100Base-T, RJ-45) located along the OAM port interfaces on the OAM circuit pack.

• the Craft port (10/100Base-T, RJ-45) located along the OAM port interfaces on the OAM circuit pack.

• the M1/F1 port via modem.

• SDH/SONET Regenerator Section (RS)/Section 192 kbps DCC (D1-D3 bytes) of the optical line interfaces.

• SDH/SONET Regenerator Section (RS)/Section 64 kbps user channel (F1 byte) of the optical line interfaces.

• SDH/SONET Multiplexor Section (MS)/Line 576 kbps DCC (D4-D12 bytes) of the optical line interfaces.

• SDH/SONET Path DCC (F2, F3, or F2-F3 bytes) of the optical line interfaces.

• SDH VC12 management channel of the optical line interfaces.

• SDH E1 management channel on any E1 port on the 63xE1/DS1circuit pack, on the first E1 port of the 28xE1/DS1 circuit pack or on the first port of the 28xE1/DS1(W/P) circuit pack.

Depending on the network topology, the 6130 can be configured to operate as either:

• an IP router: IP communications are routed using static and/or dynamic routing protocol to subtended NEs

• an IP host: IP communications are not forwarded to other NEs with static routing entries providing default routing to the connected IP router.

The 6130 can use integrated IS-IS (iIS-IS) protocol with auto-tunneling in order to establish communications with OSI based network elements.


Appendix A: Data communications planning 10-3

6130 supports Generic Routing Encapsulation (GRE) which can tunnel IP management communications into OSI Protocol Data Units (PDU). The GRE tunnel can be terminated on an 6130, other GRE capable NE, or a dedicated router to extract the IP management communications before being forwarded to the management system.

6130 supports transparent DCC capabilities which allows the NE to pass-through DCC bytes (E1, F1, D1-D3, E2, D4-D12) used by other network elements. This functionality provides additional integration capabilities into an existing network without affecting the current DCN configuration.

Remote access to an 6130 NE can be achieved through asynchronous RS-232 modem connection through the serial M1/F1 communication port.

OAM&P PortsThis section describes the ports which can be used to perform OAM&P operations on an 6130 network element.

M1/F1 port6130 shelf supports a serial communication port which can operate under the following applications:

• Point-to-point (PPP) - asynchronous RS232 communication with external modem.

• User Data Channel (UDC) - asynchronous 64 kbps clear channel using the F1 byte of the regenerator section/section overhead. The F1 byte user data channel is supported for the STM-1/4/16/OC-3/12/48 interfaces of the aggregate circuit pack(s) and for STM-1/4/OC-3/12 interfaces of the 2x622M/8x155M circuit pack(s).

LAN port (LAN-1-6)The 6130 shelf supports a 10/100BT Ethernet port on the OAM circuit pack to interface with the external DCN.

It auto-senses the operating speed (10 Mbit/s or 100 Mbit/s), but operates only at half-duplex mode.

The LAN port is wired as MDI/MDI-X, and auto-detect the type of cable connected to it (straight or crossover).



The provisionable IP subnet mask is in prefix notation which indicates the number of binary 1s in the mask, preceded by the “/”.

Network InterfaceThe network interfaces of the 6130 network element are logical representation of the management channels for OAM&P. Each network element has a minimum of one network interface (eth0) for the LAN port. A maximum of 42 DCC in-band channels can be provisioned per network element. Besides the eth0 network interface, 42 additional DCC network interfaces can be a combination of the E1/VC12 management channel (mgmt1 or mgmt2) and the embedded communication channel of the SFP interfaces. Static and dynamic (Auto) GRE tunnels are also represented as network interface entities.

The eth0 network interface is created by default and can not be deleted.

The mgmt1 and mgmt2 network interfaces are created when the E1/VC12 management channels are provisioned via the DCN/Management Channel application, and they are deleted when the E1/VC12 management channels are unprovisioned from the application. Only IP/PPP is supported over the E1/VC12 management channels (and it supports only OSPF as routing protocols).

The ecc network interfaces are created by selecting the appropriate RS/Section or MS/Line overhead bytes (F1, F2, F3, F2F3, D1-D3, or D4-D12) for the embedded communication channel in the Provision ECC page. These ECC network interfaces are deleted from the network interface page. Either IP/PPP or OSI/LAPD is supported over the embedded communication channels.

Table 10-2Subnet mask

Mask Dotted equivalent

/24 255.255.255.0

/25 255.255.255.128

/26 255.255.255.192

/27 255.255.255.224

/28 255.255.255.240

/29 255.255.255.248

/30 255.255.255.252

/32 255.255.255.255



The static and Auto GRE tunnels are also created as network interfaces. When iIS-IS is enabled at the nodal level on the network element, the Auto GRE tunnel (AGRE) network interface is automatically created and will be deleted upon disabling the iIS-IS nodal parameter. Upon enabling nodal iIS-IS on the NE, a static GRE tunnel (SGRE) network interface can be created by specifying the remote manual area address, remote system ID (MAC address) and the NSAP selector byte.

See Table 10-3 for a summary of the provisionable parameters applicable to each type of network interfaces. Refer to Table 10-4 or more information on the parameters supported for OSPF and iISIS routing protocols.

Table 10-3Network interface provisionable parameters summary

Network interface

Admin Status

Layer 2 parameters Layer 3 parameters

OSPFsupport

iISISsupport

eth0(LAN port)

<Up/Down>

(see Note 1)

• Layer 2 Protocol=MAC • Layer3 Protocol=IP

• MTU=<1518> bytes

Yes No

mgmt1mgmt2(E1/VC12)

<Up/Down> • Layer2 Protocol=<Standard PPP, RFC1661 / PPP, HDLC framing>

• Magic Number=<Disable/Enable>

(see Note 3)

• Layer3 Protocol=IP


Yes No

ecc(STM-1/4/16 / OC-3/12/48 ports)

<Up/Down> • Layer2 Protocol=<Standard PPP, RFC1661 / PPP, HDLC framing>

• Magic Number=<Disable/Enable>



Yes

(see Note 2)

Yes

(see Note 2)

• Layer2 Protocol=<Datalink LAPD>

• Layer3 Protocol=OSI

• MTU=<512> bytes

No Yes



For more information on the detail procedures, refer to Provisioning and Protection Switching Procedures, 323-1855-310.

AGRE

(see Note 4)

<Up> • Layer2 Protocol=GRE • Layer3 Protocol=IP

• MTU=446 bytes

No No

SGRE-1

(see Note 5)

<Up/Down> • Layer2 Protocol=GRE

• Remote MAA=<490000>

• Remote SID=<000000000000>

• NSAP Selector Byte=<2F>


• MTU=<446> bytes

Yes No

Note 1: It is recommended to leave the Eth0 network interface port in Admin Up state.

Note 2: OSPF and iISIS cannot be simultaneously enabled for a network interface.

Note 3: E1/VC12 management communication between 6130 and 6110 (Release 1, Release 2.0, Release 2.01 software) should use Layer 2 Protocol as Standard PPP, RFC1661.

Note 4: The Auto GRE tunnel is automatically created when iISIS is enabled at the nodal level on the NE. The AGRE network interface parameters are not user-provisionable.

Note 5: The Static GRE tunnel can only be created if iISIS is enabled at the nodal level.

Table 10-4Dynamic routing protocol parameters

Routing Protocol

Status Provisionable parameters Network Interfacesupport

OSPF <Enable / Disable>

• Hello Interval=<10>

• Router Dead Interval=<40>

• OSPF Authentication Mode=<Disable authentication / Simple password>

• Password/Key=<>

• eth0

• mgmt1, mgmt2

• ecc_x_x

• SGRE-x

iISIS

(see Note)

<Enable / Disable>

• L1 Default Metric=<4>

• L2 Default Metric =<4>

• L2 Routing Only=<Disable / Enable>

• ecc_x_x

Note: In this release, the L2 Default Metric and L2 Routing Only parameters are not supported for iISIS routing protocol.

Table 10-3 (continued)Network interface provisionable parameters summary

Network interface

Admin Status

Layer 2 parameters Layer 3 parameters

OSPFsupport

iISISsupport



STM-1/4/16/OC-3/12/48 Data Communication ChannelEach line optical port can support communications on the selected regenerator section (RS)/section or the multiplexer section (MS)/line overhead byte(s).

Each DCC interface supports High-Level Data Link Control (HDLC), Point-to-Point Protocol (PPP), or Link Access Procedure D-Channel (LAPD). HDLC and PPP are IP-based datalink layer and LAPD is an OSI-based datalink layer. PPP is the default datalink layer.

The 6130 uses an IP-based data communications infrastructure for network element management and interworking with IP-managed network elements. 6130 also supports Open Systems Interconnection (OSI) based infrastructures for interoperability with OSI-managed network elements.

Data link layer protocolsThe following are the supported data link layer 2 protocols used with 6130 network element through the DCC channels:

LAPDLink Access Procedure D-Channel (LAPD) is a data link layer 2 protocol used by 6130 for interworking with OSI networks over DCC.

The 6130 network element supports LAPD layer 2 protocol on all STM-n/OC-n ports terminating the layer 1 channel using the over-head bytes. The 6130 network supports at least as many LAPD instances as the number of STM-n/OC-n ports in the 6130 network element.

Attention: The 6130 network element can support presentation of either LAPD or PPP to the layer 1 interface. Each layer 1 interface can only terminate either LAPD or PPP protocol, but not both simultaneously.

It is possible to configure layer 2 protocol for each layer 1 interface independently, on a per layer 1 interface basis.

LAPD detects and reports to higher layers the up or down status of the physical interface. An alarm to indicate link failure shall be supported.

Standard PPP, RFC1661Point-to-point protocol (PPP) is a data link layer 2 protocol used to pass data between two systems on behalf of the network layer 3 protocol such as TCP/IP Internet Protocol (IP). 6130 uses the standard PPP as per RFC1661.



Attention: PPP uses IP Control Protocol (IPCP) over OSI Network Layer Control Protocol (OSINLCP) to pass data between layer 2 and layer 3 protocols. Recommended for standard implementation.

Use this option for interworking with any Ciena equipment which supports IP/PPP over DCC channel.

Operates in an un-numbered IP mode, using the Router ID (refer to as circuitless IP for Ciena routers and loopback address for Cisco routers).

The DCN interface that is configured to operate on IP over Standard PPP does not support configuration of the interface IP address through IP Control Protocol (IP CP) negotiation. The 6130 network element while sending IPCP IP Address Configure-Ack packet (which is sent in response to the IPCP IP Address Configure-Req packet) will send the Router-ID as its IP address.

PPP, HDLC framingHigh-Level Data Link Control (HDLC) is a data link layer 2 protocol used to pass data between two systems on behalf of the network layer 3 protocol such as TCP/IP Internet Protocol (IP).

Attention: The 6130 uses the proprietary cHDLC encapsulation and will not interwork with other Ciena equipment except for the 6110 and 6150.

Operates in an un-numbered IP mode, using the Router ID (refer to as circuitless IP for Ciena routers and loopback address for Cisco routers).

Use for interworking with other cHDLC DCC network element.

When iISIS is selected as the routing protocol, PPP with HDLC framing cannot be selected as a Layer 2 Protocol.

STM-1/4/16/OC-3/12/48 DCC operation modeThe DCC operation depends on the implemented protection scheme.

1+1 MSP/APS systemThe route diversity is provisionable and can either be Route-Diversity-Enabled (ON) or Route-Diversity-Disabled (OFF) while configuring 1+1 MSP/APS for the STM/OC ports of the aggregate circuit pack(s), 2x155M and



2x622M/8x155M tributary circuit packs. On the 6130 network element, the route diversity is enabled by default in SDH mode and disabled by default in SONET mode.

In the Route-Diversity-Disabled option, the DCN operation bridges transmit and select receiver based on the MSP/APS state machine. The layer 2 and above are presented with only one network interface:

• In the receiver direction, only one of the two layer 1 interfaces (from among the configured working and configured protected belonging to the MSP/APS pair) will be presented to the layer 2 termination protocol. The presented interface shall follow the active path as defined by the MSP/APS state machine.

• In the transmit direction, both layer 1 interfaces (configured working and configured protected port of the MSP/APS pair) transmit the same information sent from the layer 2 protocol (bridge).

Attention: In the Route-Diversity-Disabled option, no DCN configuration is allowed on the configured protected port of the MSP/APS pair.

“Route diversity disabled” mode uses a single DCC channel which is switched with the traffic for management, which is unlike the “route diversity enabled” mode where each interface of the 1+1 MSP/APS link has a separate DCC channel that is not switched with the MSP/APS protected traffic.

In the Route-Diversity-Enabled option, the DCN operation on the configured working and configured protected ports belonging to MSP/APS are treated independently. The transmit and receive data of the two layer 1 interfaces (belonging to the configured working and configured protected ports belonging of MSP/APS pair) is independently presented to the layer 2 termination protocol as two independent interfaces. The layer 2 and above are presented with two independent network interfaces.

Attention: In the Route-Diversity-Enabled option, DCN configuration is allowed on the configured protected port of the MSP/APS pair.

If 6130 NE is interworking with another network element (e.g OM3000/4000) which has its interface set to bi-directional MSP/APS switching mode, route diversity should be provisioned to the same at the 6130 NE and the far-end NE. Otherwise, DCC alarms may be raised on the non-6130 NE which can be ignored or disabled.



When an 6130 NE, which has its DCC route diversity disabled, is interworking in a 1+1 MSP/APS uni-directional switching mode with other NE (e.g. OM3000/4000) with route diversity enabled, a single fibre break in the Rx direction of the non-6130 NE in working path can result in lost of communication between the two NEs because the 6130 NE can still receive traffic on the working interface which the transmit has failed, therefore bi-directional LAPD adjacency can not be established on neither the working path nor the protection path, and hence loss of communication. There will no loss of communication if both fibres (Tx and Rx) on the working path fail at the same time so that bi-directional LAPD adjacency can be establish on the protection path.

Bi-directional switching mode is the recommended protection scheme used for 1+1 MSP/APS in order to guarantee full data communication between interworking network elements.

SNCP/UPSR MS-SPRing/BLSR or unprotected systemIn this configuration, each STM-1/4/16/OC-3/12/48 link is considered as an individual port, allowing the DCC to be configured independently. The following are the supported combinations for each DCC:

• STM/OC port with DCC disabled

• STM/OC port with PPP/IP or cHDLC/IP

• STM/OC port with LAPD/CLNP (OSI)

Overhead transparency6130 supports overhead bytes transparency via overhead tunnel provisioning, by specifying the source and destination optical port, and selecting the passthrough RS/Section or MS/Line overhead byte(s). This feature provides the following capabilities:

• Designated byte(s) from the interworking or subtending networking elements are passed transparently through the 6130 network elements.

• Allows interoperability with other vendors’ equipment that do not support a standard-based OSI communication stack.

• Using transparent DCC to forward OSI packets.

• The same overhead bytes cannot be used for provisioning overhead transparency and a DCC channel.

The following are the overhead bytes which are allowed to pass transparently:

• Regenerator Section/Section overhead:

— E1: 64 kbps orderwire channels

— F1: 64 kbps user channel



— D1-D3: 192 kbps OA&M data

• Multiplexer Section/Line overhead

— E2: 64 kbps orderwire channels

— D4-D12: 576 kbps OA&M data

STM-1/4/16/OC-3/12/48 DCC implementation rulesYou must observe the following rules when you implement the DCC:

• Only one section/regenerator section (RS) or line/multiplex section (MS) DCC can be enabled per optical port.

• Each DCC can support HDLC, PPP or LAPD. The default is PPP.

— When using DCC to connect to an 6130 (or any network element that supports IP based DCC datalink layer), select PPP as the protocol.

— When using DCC to connect to an OSI-based DCC datalink layer, select LAPD as the protocol.

• Set the LAPD IP MTU size to 446 when interworking with Optical Cross Connect DX/ HDXc/ HDX, Optical Metro 3000, and 6500. The user has to manually configure the connected SONET/SDH interfaces to 512 bytes for the LAPD MTU. The 6130 LAPD MTU is set to 512 by default.

• Set the LAPD IP MTU size to 446 when interworking with Optical Metro 4000 and TN-1C family of products which has a fixed LAPD MTU of 512 bytes. The 6130 LAPD MTU is set to 512 by default.

• On a DCC interface over SDH/SONET overhead bytes, both OSPF and iISIS routing protocols cannot be enabled simultaneously.

• When using OSPF on the DCC interfaces, topology autodiscovery does not function across the DCC interfaces using OSPF. Autodiscovery does function across DCC interfaces using iISIS.

• If OSPF is configured between 6500 and 6110 (and 6130/6150) the SDCC or LDCC network interface IP MTU has to be set to 1508 bytes, L2 protocol is the default “Standard PPP,RFC1661”. If the MTU parameter is changed while OSPF is enabled on the DCC interface, OSPF state should be manually toggled to trigger re-negotiation of the updated MTU value.



IP communicationTCP/IP Internet Protocol (IP) is a network layer protocol and the 6130 uses IPv4. Each 6130 shelf must have one IP address assigned to it for management purposes. Typically, the IP address used to manage the 6130 is the circuitless IP address. The circuitless IP is designated as Router ID.

The LAN (LAN-1-6) Ethernet interface can be assigned with a single IP address and subnet mask. A gateway network element requires an IP address on a different subnet to the Router ID for the Ethernet interface connected to the external DCN.

For general information on assigning IP addresses in a network, see IP networks, addressing, and masks on page 10-95.

IP addressing implementation rulesYou must observe the following rules when you implement the IP addresses:

• Each network element must be assigned with an IP address and subnet mask for the LAN port, and an IP address for the circuitless IP (Router ID) address.

• For a gateway network element, you must provision an IP address for the LAN port on a different subnet to the Router ID IP address. The LAN interface must be assigned an IP address in the same subnet of the external router port connected to the LAN interface of the gateway network element.

• A node reset (warm restart) on the NE is required after changing the Router ID or Ethernet IP address in order for the new IP addresses to take effect

• Overlapping IP addresses cannot be assigned.

• When assigning private IP addresses, it is recommended that the IP addresses in the range of 10.1.1.0 to 10.4.255.255 are not used. These IP addresses are used by the OM5000 network elements for internal data communications so should not be used in any 6130 network that will contain OM5000 network elements.

• The LAN port has a default IP address of 192.168.1.254/24 which allows a local craft PC with an IP address configured in the same subnet as the LAN interface to access the network element. It is recommended that the IP addresses in the range of 192.168.1.1 to 192.168.1.255 are not used.

CAUTIONCircuitless IP (Router ID) addressThe circuitless IP has a non-provisionable default subnet mask of 255.255.255.255.



• The last octet of the router ID and LAN-1-6 IP addresses can not be 0 or 255.

• For a remotely managed NE, for example, via the DCC of the optical line interface, the LAN port can be left as default IP address of 192.168.1.254/24 for local craft access.

Attention: OSPF routing should always be disabled on the LAN port if it is provisioned with default IP address.

• The Craft port on the OAM circuit pack can be used for local craft access with the Web User Interface (WUI) or Site Manager. The Craft port has the IP address of 192.168.1.254/24 which allows a local craft PC with an IP address configured in the same subnet to access the network element. The Craft port is always enabled and its IP address cannot be changed. The Craft port is running a DHCP server that can be used to assign an IP address (e.g. 192.168.1.253) to the host computer when it is connected to this port. The DHCP server is always enabled on the Craft port.

Static routingAs with standard routers, the 6130 supports configuration of static routes.

Static route implementation rulesYou must observe the following rules when you implement a static route:

• Static routes can be provisioned on any of the network interfaces up to a maximum of 10.

• Static routes on valid PPP interfaces, such as STM-1/4/16/OC-3/12/48 ports, SGRE, AGRE, E1 or VC12 management channels, should be provisioned with next hop IP address 0.0.0.0.

• Set the OSPF parameter to Disable and provision the static route for the appropriate PPP network interface.

Attention: The static routes can be configured in the NE for redistribution (advertising over routing protocols over to other NEs). The redistribution is applied to the routing protocol that is provisioned on the NE: OSPF only, iISIS only or both simultaneously. It is not possible to redistribute a static route only over OSPF or only over iISIS, if both routing protocols are enabled on the network element.



Dynamic routing - OSPFOpen Shortest Path First (OSPF) Protocol is an Interior Gateway Protocol (IGP) that distributes routing information between routers belonging to a single autonomous system (AS). Intended for use in large networks, OSPF is a link-state protocol which supports IP subnetting and the tagging of externally-derived routing information.

6130 provides OSPF v2 routing functionalities and acts as a standard non-backbone OSPF router, interworking with an external customer OSPF DCN.

Attention: OSPF routing is always active on the 6130 network element, and therefore does not need to be enabled at the nodal level. It must only be provisioned on the network interface for which it is required.

The 6130 supports enabling and disabling of OSPF routing protocol per IP-carrying interface, including Eth0, PPP/cHDLC DCC, and SGRE interfaces.

For more information about OSPF, see IP routing protocols on page 10-99.

OSPF routing implementation rulesYou must observe the following rules when you implement the OSPF routing:

• Default user configurable OSPF area of 0.0.0.1 for all network interfaces for which the OSPF parameter is enabled.

• Set the OSPF parameter to Enable to use dynamic routing over the network interfaces.

• When OSPF is enabled on the eth0 network interface (LAN port), the provisioned Ethernet sub-network is advertised as part of the OSPF link state advertisement (LSA).

• The Router ID IP address is used only in OSPF hello packets to form OSPF adjacencies. This allows multiple different OSPF areas of 0.0.0.1 to exist in the customer network as long as the 6130 NEs are connected to different Area Border Routers (ABRs). See Figure 10-1 on page 10-15.

• It is recommended to use the Ethernet IP address as the Router ID IP address if the NE has only direct LAN connectivity.

• It is recommended to use a different Router ID IP address other than the Ethernet IP address if the NE has DCC enabled.

• When OSPF is enabled on the Ethernet port and DCC is being used to provide OA&M, the Router ID IP address should be in a different sub-network other than the Ethernet IP address sub-network.



• Re-distribution of static route into OSPF routing table is supported. By default, static route re-distribution is disabled.

• Route redistribution between OSPF and iISIS routing protocols is supported.

Figure 10-1Multiple OSPF 0.0.0.1 areas

Dynamic routing - Integrated IS-ISIntegrated ISIS (iISIS) is a routing protocol based on the OSI Intra-domain routing protocol with IP specific extensions as specified in ISO/IEC10589 and RFC1195. iISIS allows IP and OSI to co-exist in a single routing domain, allowing IP-only routers, OSI-only routers, and dual IP/OSI routers to be effective in routing in a single network.

6130 network elements support nodal level enabling and disabling of iISIS routing protocol. When enabled at a nodal level, it is possible to enable iISIS routing on a per layer 2 PPP interface or on a per LAPD interface. iISIS is able to communicate with layer 2 protocols to forward OSI-NPDU packets over the LAPD and PPP layer 2 links.

Legend

= IP connection= OSPF routing between NEs/Router= iISIS routing between NEs= Static/Default routing

OMEA

OSPF area 0.0.0.0 OSPF area 0.0.0.1

OSPF area 0.0.0.1

ABR 1

ABR 2

ABR 3



iISIS routing protocol allows the creation of an Link State Packet (LSP) database of all OSI only, IP only, and Dual Stack network elements within its level 1 area. iISIS routing protocol creates IP Routing Information Base (RIB) that contains route information for all network elements that have at least one IP address configured and is in the same level 1 area. iISIS routing protocol also creates CLNP forward information base (FIB) updates based on LSP database for all reachable OSI network elements.

iISIS routing implementation rulesYou must observe the following rules when you implement the iISIS routing:

• Support provisioning of three manual area addresses:

— MAA1 default value of 490000

— MAA2, blank with 3 to 13 bytes long

— MAA3, blank with 3 to 13 bytes long

• Level 1 routing is supported

• Enabling and disabling of iISIS routing protocol is done on a per PPP, LAPD based DCN interface. The default value is iISIS-Disabled.

• The iISIS routing protocol will support only configuration of default metric as the routing metric for each circuit. The range of the default metric shall be [1 - 63] and the default value is 4.

• Route redistribution between OSPF and iISIS routing protocols is supported.

Routing protocol configuration6130 supports nodal level configuration of enabling or disabling of Integrated Intermediate System Intermediate System (iISIS) routing protocol. By default, iISIS routing protocol is disabled. OSPF routing protocol is always enabled at the nodal level, but must be provisioned per network interface.

6130 supports enabling of iISIS at a nodal level, while OSPF is also enabled on the NE. The routing protocols must be specified for each network interface individually. iISIS and OSPF routing can not be simultaneously provisioned on the same network interface.

Proxy ARPProxy ARP allows a gateway network element to respond to address resolution protocol (ARP) requests for subtending network elements that are within the same subnet as the customer DCN address range. The proxy ARP feature removes the need for customers to provision static routes on their routers and routing protocols (OSPF) between the gateway network elements and the customer DCN.



Proxy ARP is only supported on the LAN interface of the 6130 network element. At the gateway 6130 network element, the IP address of neighbouring network elements can be provisioned for Proxy ARP. The GNE will perform proxy ARP for IP addresses of neighbouring NEs that are on the same subnet s the DCN router connected to the LAN interface.

For more information about ARP, see ARP on page 10-98.

Proxy ARP implementation rulesYou must observe the following rules when you implement proxy ARP. At gateway network elements, you must:

• assign a subnet on the DCN router port that connects to the LAN port of the gateway network element that is large enough to support the LAN port and the router ID address of every network element for which the gateway network element will proxy ARP

• ensure that the maximum of number of subtending NEs (6110 and/or 6130) that are managed via the 6130 Gateway NE does not exceed the following values:

— 20 NEs with the 2x155/622M aggregate circuit pack

— 20 NEs with the 1x155/622M aggregate circuit packs

— 20 NEs with the 1x2.5G aggregate circuit packs

— 24 NEs with the 1x2.5G+4x155M/2x622M aggregate circuit packs

— the number of proxy ARP neighbours that can be provisioned at the 6130 Gateway NE is 150 entries. However, ensure that the maximum number of subtending NEs that are managed via the 6130 Gateway NE does not exceed the values listed above.

• provision the IP addresses of the proxy ARP neighbours for which the gateway network element will respond for. The IP addresses should be of the hosts, not the network.

• ensure that the DCN router interfaces connected to the LAN interface will ARP for the specified ARP neighbours

• provision a static route to the DCN network. At the remote/neighbouring NEs, static routes do not need to be provisioned to the router

OSI data communicationsThe Data Communications Network Planning Guide, NTR710AM provides information on DCN planning for some OSI-based Ciena products. This guide includes general information on OSI data communications and addressing and can be used as a reference for OSI data communications information.



CLNPOSI Connectionless Network Protocol (CLNP) is a network layer 3 protocol which provides services to the upper transport layer, similar to the Internet Protocol (IP) in the a TCP/IP environment. CLNP is often referred to as ISO-IP. CLNP uses NSAP addresses to identify network devices. The 6130 supports CLNP protocol as specified in ISO/IEC 8473-1.

Attention: 6130 supports a maximum CLNP packet size of 512 bytes.

The 6130 provides the ability to tunnel IP communications over OSI. The 6130 will route (forward) only IP packets and OSI (CLNP) PDUs (support of reassembly of segmented DPDUs).

In order to communicate to the 6130 NE in an OSI network, the 6130 can use iISIS routing protocol with auto-tunneling to allow the OSI route to the 6130 NE to be learnt through the OSI network. Once iISIS routing is provisioned, static (SGRE) or dynamic (AGRE) IP over OSI tunnels can be provisioned on the network element.

In order to provide communications through the OSI network, the following items need to be performed:

• Configure the 6130 NE to communicate to the OSI area it is connected to.

• Enable iISIS routing protocol at the nodal level, as well as the applicable network interface. The AGRE interface will be automatically created once iISIS is enabled at the nodal level. If required, a SGRE interface can also be provisioned on GRE tunnel terminating equipment, such as 6130, 6500 or external routers. A static or dynamic routing protocol must also be provisioned for the SGRE interface.

CLNP and layer 2 protocols using SNDCFSub-Network Dependent Convergence Function (SNDCF) interfaces are used for multiplexing and de multiplexing packets between layer 3 modules (CLNP, GRE, ESIS, and ISIS) and layer 2 interfaces (LAPD, PPP or MAC).

The 6130 provides a SNDCF interface that allows layer 2 protocols such as LAPD and PPP to interface with CLNP, ESIS, and ISIS routing protocols. The GRE layer module will interact with CLNP via the addition of Network Service User of CLNP.

Configure OSI connectionYou must observe the following rules when you configure the OSI data communication:



• 6130 requires an OSI local manual area address to interop with other OSI products. The local manual area addresses are used to form the NSAP address of each network element in the OSI level 1 area.

• The default manual area address is 490000.

• Up to three local manual area address can be provisioned for iISIS. The 6130 NE can be part of up to 3 areas.

• All NSAP formats are supported:

— ISO Local Addressing Format - e.g. 490000

— ISO DCC Addressing Format - e.g. 39xxxxxxxxxxxxxxxx

• In order to communicate with an Intermediate System (IS) network element, provision the Local Manual Area Address to be the same as the Manual Area Address of the connected IS NE. The iISIS protocol will establish adjacency between NEs in an area if they have one Manual Area Address common.

• For communication to network elements in different OSI area, the Local Manual Area Address has to be the unique area address used in the networks which use both the default 490000 Manual Area Address and a unique 39xxxxxxxxxxxxxxxxx Manual Area Address.

Configure GRE tunnelTCP/IP Generic routing encapsulation (GRE) is a standard transport layer encapsulation protocol which provides a standard method for transporting one arbitrary network layer protocol over another arbitrary network layer protocol (tunneling). A tunnel is effectively a point-to-point connection which allows packets to be enclosed/encapsulated within another packet.

GRE tunnelTwo GRE types are supported:

• Static GRE tunnel : Static tunnels are user defined point-to-point tunnels used to pass packets from one node to another. Static tunnels are ideal for bridging sections of a network which do not support a protocol (for example, routing IP packets through an OSI network). The user creates a static tunnel by specifying a protocol (OSI or IP) and a tunnel termination point (MAC address).

Attention: Creating a static tunnel to a specific destination only allows packets to be sent to that destination. You must configure a tunnel in the opposite direction for packets to be returned.

• Auto GRE tunnel: Auto-tunnels are dynamically created and removed as required by a dual router. Auto-tunnels do not require user intervention but only operate between iISIS capable nodes where OSI communications



can be reached between the nodes. Auto-tunnels configure multiple tunnels to multiple destinations depending upon the best route through multi-protocol networks that support iISIS.

Attention: Static GRE and Auto GRE tunnels support only IP over OSI tunnelling.

Static GRE tunnel6130 supports only one instance of static GRE tunnel per network element. The user creates a static tunnel by specifying a protocol (IP) and a tunnel termination point (OSI address). The static GRE supports only IP over OSI tunneling.

Attention: The static GRE tunnel is user provisionable. For optimal performance the static GRE tunnel should be provisioned provided there is a LAPD interface on which iISIS is enabled. If there is no interface with iISIS enabled then all packets into static GRE shall be dropped.

Creating a static tunnel to a specific destination only allows packets to be sent to that destination. You must configure a tunnel in the opposite direction for packets to be returned.

The 6130 supports enabling of OSPF routing protocol on a static GRE tunnel interface. When enabled, OSPF exchanges packets over the GRE interface and treats the NE of the other end of the GRE tunnel as its neighbor.

Auto GRE tunnel6130 supports auto GRE tunneling with iISIS routing protocol to provide seamless integration of OSI only networks with Dual or IP only networks elements.

The auto GRE tunnel is automatically configured and enabled when iISIS routing protocol is enabled at the nodal level. There is no specific user configuration required. The IP over OSI tunnel creation is done automatically on a per packet basis over all the packets forwarded to the auto GRE interface by IP. A default static route shall be provisioned automatically on the auto GRE (called agre0) interface that is presented to the IP protocol stack. In this scenario, the IP protocol stack shall forward packets that are not routable by any other IP routing table entry to the auto GRE tunnel for further processing. The default route shall have the last priority, as any user provisioned specific static route shall have higher priority than default route when routing packets.



Attention: If an NE contains 0.0.0.0/0 and 10.0.0.0/8 as two routes already present, then auto-GRE creation can cause packets reaching through one of the routes to be dropped. It is better to reconfigure the 0.0.0.0/0 and/or 10.0.0.0/8 routes to another suitable route so that the automatic creation of auto GRE interface route functions seamlessly.

Static routes can be added by the user other than the default route that points to the Auto-GRE tunnel. Then, the packets that did not find a match in the IP routing table will be routed to the Auto-GRE tunnel.

AGRE IP/OSI routing interactionsFigure 10-2 presents a diagram describing the IP packet routing when iISIS routing protocol is enabled. The 6130 supports an IP routing table, which is updated with the least cost route for each IP destination from Static IP routes, OSPF learnt routes and iISIS routes learnt over PPP interfaces, such as connection to IP-capable network elements. IP routes learnt over CLNP are not stored in the native IP routing table, but they are added to the OSI/GRE routing table as part of the OSI routing function. The AGRE interface when provisioned with appropriate static routes, allows for packets to be pushed from the native IP routing domain to the iISIS routing domain (with IP routes that communicate through OSI network elements). At each network element, the AGRE interface must be properly provisioned with static routes covering all destinations which will need to be auto-tunnelled. Once in the OSI routing domain, the IP destinations of a received IP packet are looked up against the OSI/GRE forwarding table to determine the NSAP (OSI address) that provides most specific and least cost route to that IP destination. If a match is found then GRE encapsulation of the IP packet into a CLNP (OSI) PDU with this NSAP as the destination is performed. This CLNP PDU is then routed to this NSAP by looking it up in the OSI routing table.



Figure 10-2IP Packet Routing

Generic GRE implementation rulesYou must observe the following rules when you implement auto or static GRE:

• 6130 supports presentation of both auto and static GRE interfaces to IP layer protocol. The auto GRE interface presented to the IP protocol layer is called agre0. The static GRE interface presented to the IP protocol layer is called sgre1.

• 6130 supports presentation of both auto and static GRE interfaces to CLNP protocol layer.

• The MTU of the GRE network interface presented to the IP must be 446 bytes. The MTU presented to CLNP must be 512 bytes. This is valid for both auto and static GRE interfaces.

Static GRE implementation rulesYou must observe the following rules when you implement static GRE:

• Provision the Remote Manual Area address of the tunnel destination. The tunnel can be either in the same or remote OSI area. The default is 0x490000.



• Provision the Remote System ID of the tunnel destination node. The MAC address of the tunnel destination node can be used as the Remote System ID. When the MAC address is entered for static GRE provisioning, remove the colon characters. The default is 0x000000000000.

• Provision the NSAP Selector Byte of the tunnel destination node. Use hexadecimal 2F (47 in decimal) for GRE protocol.

Attention: When provisioning a static GRE tunnel between the 6130 and 6500, a mismatch of the NSAP selector bytes provisioned at the 6500 and the 6130 is expected. The NSAP Selector Byte provisioned at the 6130 WUI should be set to 2F, and the network selector (NSEL, last byte of NSAP) provisioned from the 6500 craft interface must be set to 00. The 6500 automatically sets the NSEL internally to support the required transport service.

Auto GRE implementation rulesYou must observe the following rules when you implement Auto GRE:

• The default route of 0.0.0.0/0 should not be configured over the LAN port (eth0) and should not be advertised over iISIS on the GNE. This route may interfere with the static route that needs to be configured on the AGRE interface on every 6130 network element.

• On the all 6130 network elements (GNE and remote NEs), it is recommended to manually provision the static route for the AGRE to be within the network element DCN subnet.

• On all remote network elements, the default route of 0.0.0.0/0 can be provisioned over the AGRE interface.

• Starting in Release 4, the default 0.0.0.0/0 AGRE route is not added automatically when iISIS is enabled. This route does not need to be added if there are other provisioned or learned routes that can be used to reach the nodes.

Configure IP routingConfigure the interface to use either static or dynamic routing scheme. Refer to IP communication on page 10-12 for more details.

Application protocolsThis section lists out the supported application protocols and commands which can be useful while working and troubleshooting an 6130 network element.



ftpTCP/IP File transfer protocol (FTP) is a standard application layer protocol used for transferring files across a network. This protocol uses a client/server architecture. Both the FTP client and server are enabled on the 6130. The 6130 supports active FTP.

The FTP protocol is used mainly during firmware, software, or on-line documentation upgrade to handle all file transfers between the source (server) of the image files and the network elements (clients). The FTP protocol is also used for database backup and restore operations.

telnetTCP/IP Telnet is a standard application layer terminal protocol used for accessing remote computers, in a text based communications session between a client and a host.

Both the Telnet client and server are enabled on the 6130.

Diagnostic commandsThis section lists the diagnostic commands which can be used on an 6130 network element in a telnet session.

arpAddress resolution protocol utility

ifconfigDisplays status information for all interfaces.

pingICMP echo request and reply to test IP layer 3 connectivity. This command requires root privilege.

routeDisplays the kernel IP routing table.

tcpdumpPrints out headers of packets on all or specified interface. This command requires root privilege.



Firewall considerationsThe following ports must be passed through any firewall between the management systems and the 6130 network:

• TCP

— 20 (data), 21 (control) - FTP ports used for upgrades, or backup and restore configurations.

— 2023 - Telnet port used for troubleshooting.

— 10001 - Used by TL-1 without prompt and character echo

— 10002 - Used by TL-1 with prompt and character echo

— 20080 - Used by HTTP for Web User Interface (WUI)

• UDP

— None used

Engineering guidelinesThe following are DCN engineering guidelines:

• STM-1/4/16/OC-3/12/48 DCC

— Maximum of 42 DCCs per NE. Refer to Table 6-15 for more details on maximum number of RS / MS DCC interfaces per NE

— Maximum of 1 Regenerator section (RS)/Section or Multiplex section (MS)/Line DCC per optical interface

— RS/Section DCC using D1-D3 bytes at 192 kbps

— MS/Line DCC using D4-D12 bytes at 576 kbps

• LAPD

— MTU frame size of 240 to 512 bytes (default is 512)

— Metric: The DCC default metric is set to 4. When interworking with legacy network elements, use the following DCC metrics:

– MS/Line DCC: 5

– RS/Section DCC: 6

— CLNP supported over LAPD (Default MTU frame size of 512 bytes when presented to CLNP. The MTU size is user configurable and should be in the range [240-512] bytes).

ATTENTIONFor configurations that exceed the following guidelines, contact Ciena for assistance.



• PPP

— MTU frame size of 1518 bytes

— Non-configurable default parameters:

– Maximum receive unit: no limitation

Attention: Does not perform negotiation for MRU and accepts packets of any size

– Authentication protocol: disabled

– Quality protocol: None

– Protocol field compressed: Disabled

– Address and control field compressed: Disabled

– FCS alternatives: 16 bit FCS

— Configurable default parameter:

– Magic number: <Disable>

• OSPF

— Configurable default area of 0.0.0.1

— Maximum of 150 routers in the same OSPF area as the 6130 NE

— Supports non-stub area

— Configurable parameters:

– Hello Interval: 10 seconds. The range is [1-65535] seconds.

– Dead Interval: 40 seconds. The range is [1-65535] seconds.

— Non-configurable default parameters:

– Retransmit Interval: 5 seconds

– Transmit Delay: 1 second

– OSPF Ethernet Cost: 1

– OSPF DCC Cost: 1

– OSPF GRE Costs: 1

– OSPF LAN priority: 1

— OSPF Authentication mode : disabled (default) or Simple Password:

– Enabling and disabling of password based authentication for OSPF on a per layer 2 interface level. If password based authentication is enabled, then password is configurable.



— OSPF Authentication key: String configurable by the user if the OSPF Authentication mode is set to Simple Password.

Attention: For maximum network performance, the external DCN intervals should be aligned with 6130.

• IP

— Maximum of 4096 IP routes (static and dynamic). But for optimal performance it is recommended that not more than 512 entries be added in the IP routing table. (Note that the IP routing table entries include the routing entries added by OSPF or iISIS or Static Route into the IP routing protocol domain).

— Maximum of 10 static routes per NE

– Use Destination Network IP address of 0.0.0.0/0 with next hop IP address for default route

— MTU packet size of 240 to 512 bytes for OSI CLNP/LAPD

— MTU packet size of 1518 bytes for IP/PPP

• GRE

— Tunnels between different OSI areas are supported

— MTU packet size should be 66 bytes less than the MTU for LAPD

• Telnet session

— No restriction on the number of concurrent sessions per network element

— Session timeout is not supported

• TL-1 sessions

— maximum of 4 concurrent sessions per network element

DCN performanceThis section details the guidelines for DCN performance.

• Native IP forwarding capability:

— 400 kbps for typical management messages without OSI interworking

— 320 kbps with IP tunnelling through OSI with GRE

• If an 6130 NE is used as a Gateway NE, then the maximum number of subtending NEs (6110 and/or 6130) is 20 NEs when the 6130 is equipped with the 2x155/622M or 1x155/622M or 1x2.5G aggregate circuit packs.



• If an 6130 NE is used as a Gateway NE, then the maximum number of subtending NEs (6110 and/or 6130) is 24 NEs when the 6130 is equipped with the 1x2.5G+4x155M/2x622M aggregate circuit packs.

• Maximum MS/Line DCC throughput for IP packets is 400 kbps.

— Up to 20 NEs (6110 and/or 6130) can be managed through a MS DCC link.

• Maximum RS DCC throughput for IP packets is 192 kbps.

— Up to 12 NEs (6110 and/or 6130) can be managed through a RS DCC link.

• DCN Loading:

— Minimum link required for OMEA management is 128 kbps

— Minimum link for Craft only connection is 15 kbps under normal conditions

— Average native IP traffic per NE is 4 kbps

— Average resulting OSI traffic per NE with GRE is 6-8 kbps for the core DCN

— Maximum number of IP DCC or OSI DCC hops is 16

Supported DCN design examplesIn order to have a complete understanding of the DCN for 6130 and to ensure that the DCN has the proper level of resiliency and connectivity for all the network elements in the configuration, the following needs to be reviewed while designing the DCN:

• Physical and logical connectivity - Ethernet LAN port, DCC ports, and IP via OSI tunnels usage and provisioning.

• IP network design - IP class, subnets, and IP routing scheme (static or dynamic OSPF).

Attention: For configurations using OSPF routing in the examples below, the default OSPF area 0.0.0.1 is used. In actual network implementations, the OSPF area may be changed, along with the other interfaces, to a unique value.

• OSI network design (if applicable) - Area addresses, IS-IS or iIS-IS routing.



Different options are available for designing a data communications network containing 6130 network elements. The following are examples describing the physical and logical implementations:

• DCN example 1 - Using static routing with direct LAN connections to 6130 network elements.

• DCN example 2 - Using single 6130 GNE with static routing to external DCN. OSPF is used in between 6130 network elements.

• DCN example 3 - Using single 6130 GNE with OSPF to external DCN. OSPF is used in between 6130 network elements.

• DCN example 4 - Using OSPF with dual 6130 GNEs to external OSPF backbone.

• 6100DCN example 5 - Using single OM4000/3000 GNE with GRE tunnels through OM4000/3000 network to reach remote 6130 network elements in linear spurs off OM4000/3000 NE.

• DCN example 6 - Using single OM4000/3000 GNE with GRE tunnels through OM4000/3000 network to reach remote 6130 network elements in SNCP/UPSR ring with an OM4000/3000 network element.

• DCN example 7 - Using dual OM4000/3000 GNEs with GRE tunnels through OM4000/3000 network to reach remote 6130 network elements in SNCP/UPSR ring with generic SONET/SDH network elements.

• DCN example 8 - Using single 6130 GNE with iISIS through OM4000/3000 network to reach remote 6130 network elements in SNCP/UPSR rings with OM4000/3000 network elements. Proxy ARP used at 6130 GNE for access to remote 6130 NEs.

• DCN example 9 - Using single 6500 GNE with iISIS through 6500 network to reach remote 6130 network elements.

• DCN example 10 - Using single 6500 GNE with iISIS to reach remote 6130 network elements in a SNCP/UPSR ring configuration with generic SDH/SONET equipment.

• DCN example 11 - Using VC12 management channels through OM4000 network to reach remote 6130 network elements in SNCP ring with OM4000 and legacy OSI network elements. Transparent DCC used to provided resilient OSI communications.

• DCN example 12 - Using E1 and VC12 management channels to reach remote 6130 network elements in SNCP ring with OM4000 and legacy OSI network element. Transparent DCC used to provided resilient OSI communications.



DCN example 1 - Using static routing with direct LAN connections to 6130 network elements.

In this example (see Figure 10-3 on page 10-31 and Figure 10-4 on page 10-32), each 6130 is directly connected to external DCN via the LAN ports.

Routing protocol (static or dynamic) is not required from the DCN router to each of the 6130 network element. The external router and the 6130 LAN interfaces are in the same subnet. A static route is required from each of the network element to the DCN router interface.

No DCC is used in between the network elements.

This example does not provide redundant access to any of the 6130 network elements because each 6130 NE is connected to the external DCN with one Ethernet port (i.e. LAN port).

DCN provisioning detailsTable 10-5 on page 10-32 and Table 10-6 on page 10-33 detail the DCN parameters for the DCN example 1 configuration.

Attention: For parameters not listed, use the default settings.



Figure 10-3DCN example 1 - Static routing with direct LAN connections to 6130 network elements



Figure 10-4DCN example 1 - IP logical view

Table 10-5DCN example 1 - 6130 DCN provisioning details

Parameters 6130 A 6130 B 6130 C 6130 D 6130 E

1 Set up IP address

LAN-1-6 port:

IP addressNetmaskDefault gateway

Router ID:

IP addressNetmask

47.1.3.5/29-

--

47.1.3.12/29-

--

47.1.4.5/29-

--

47.1.4.18/29-

--

47.1.4.26/29-

--

Legend


OMEA

IP DCN



2 Set up IP routing

LAN-1-6 port OSPF mode

OSPF area for the NE

Static routing 1:

AddressNetmaskNext hop IP addressNext hop interfaceAdvertise

Disable

-

0.0.0.0/047.1.3.1LAN-1-6Disable

Disable

-

0.0.0.0/047.1.3.9LAN-1-6Disable

Disable

-

0.0.0.0/047.1.4.1LAN-1-6Disable

Disable

-

0.0.0.0/047.1.4.17LAN-1-6Disable

Disable

-

0.0.0.0/047.1.4.25LAN-1-6Disable

3 Set up DCC

STM/OC port 1:

ProtocolMTU

STM/OC port 2

ProtocolMTU

Disabled-

Disabled-

Disabled-

Disabled-

Disabled-

Disabled-

Disabled-

Disabled-

Disabled-

Disabled-

Table 10-6DCN example 1 - Router and OMEA provisioning details

Parameters Router 1 Router 2 Router 3 Router 4 Router 5 Router 6 OMEA

1 Set up IP address

Ethernet interface:


47.1.3.1/29-

47.1.3.9/29-

47.1.4.1/29-

47.1.4.17/29-

47.1.4.25/29-

47.1.1.1/29-

47.1.1.5/2947.1.1.1

2 Set up IP routing

Table 10-5 (continued)DCN example 1 - 6130 DCN provisioning details

Parameters 6130 A 6130 B 6130 C 6130 D 6130 E



DCN example 2 - Using single 6130 GNE with static routing to external DCN. OSPF is used in between 6130 network elements.

In this example (see Figure 10-5 on page 10-35 and Figure 10-6 on page 10-36), a single 6130 network element is used as the GNE to establish communication between the external DCN and the 6130 sub-system.

Static routes are used on both the 6130 and the connected external DCN router. The static route provisioned on the external DCN router is redistributed inside the external DCN by the external DCN routing protocol so that the proper route is available for the management system to reach the 6130 sub-system.

OSPF routing protocol is used in between the 6130 network elements using IP over DCC. The default OSPF area (0.0.0.1) is used in this example but it is supported to provision another OSPF area if required.

This example does not provide redundant access to the 6130 sub-system from the external DCN because only one 6130 NE is connected to the external DCN. However, the DCC between the 6130 NEs is redundant.





Figure 10-5DCN example 2 - Single 6130 GNE with static routing





Parameters 6130 A 6130 B 6130 C 6130 D

1 Set up IP address

LAN-1-6 port:


Router ID:

IP addressNetmask

47.1.3.6/29-

47.1.3.66/32

192.168.1.254/24-

47.1.3.67/32

192.168.1.254/24-

47.1.3.68/32

192.168.1.254/24-

47.1.3.69/32

Legend


OMEA



2 Set up IP routing



Static routing 1:


Disable

0.0.0.1

0.0.0.0/047.1.3.1LAN-1-6Enable

Disable

0.0.0.1

-----

Disable

0.0.0.1

-----

Disable

0.0.0.1

-----

3 Set up DCC

STM/OC port 1:

ProtocolMTUOSPF

STM/OC port 2

ProtocolMTUOSPF

PPP1518Enable

PPP1518Enable

PPP1518Enable

PPP1518Enable

PPP1518Enable

PPP1518Enable

PPP1518Enable

PPP1518Enable


Parameters Router 1 Router 2 OMEA

1 Set up IP address

Ethernet interface:


Circuitless IP/ Loopback

IP AddressNetmask

47.1.1.1/29-

47.1.1.128/32

47.1.3.1/29-

47.1.1.129/32

47.1.1.5/2947.1.1.1

--

2 Set up IP routing

Static routing 1:


-----

47.1.3.64/2947.1.3.6EthernetYes

-----


Parameters 6130 A 6130 B 6130 C 6130 D



DCN example 3 - Using single 6130 GNE with OSPF to external DCN. OSPF is used in between 6130 network elements.

In this example (see Figure 10-7 on page 10-39 and Figure 10-8 on page 10-40), a single 6130 network element is used as the GNE to establish communication between the external DCN and the 6130 sub-system.

OSPF routing protocol is used in between the 6130 GNE and the external DCN router, and in between the 6130 network elements using IP over DCC.

The external DCN router connected to the 6130 GNE is acting as an Area Border Router (ABR) which can use the route summarization feature to group the IP routes for the 6130 sub-network into a single route covering all the 6130 Router ID IP addresses.

This example does not provide redundant access to the 6130 sub-system from the external DCN because only one 6130 NE is connected to the external DCN. However, the DCC between the 6130 NEs is redundant.





Figure 10-7DCN example 3 - Single 6130 GNE with OSPF





Parameters 6130 A 6130 B 6130 C 6130 D

1 Set up IP address

LAN-1-6 port:


Router ID:

IP addressNetmask

47.1.3.6/29-

47.1.3.65/32

192.168.1.254/24-

47.1.3.66/32

192.168.1.254/24-

47.1.3.67/32

192.168.1.254/24-

47.1.3.68/32

2 Set up IP routing



Enable

0.0.0.1

Disable

0.0.0.1

Disable

0.0.0.1

Disable

0.0.0.1

Legend


OMEA

OSPF area 0.0.0.1

OSPF area 0.0.0.0



3 Set up DCC

STM/OC port 1:

ProtocolMTUOSPF

STM/OC port 2

ProtocolMTUOSPF

PPP1518Enable

PPP1518Enable

PPP1518Enable

PPP1518Enable

PPP1518Enable

PPP1518Enable

PPP1518Enable

PPP1518Enable



1 Set up IP address

Ethernet interface:



IP AddressNetmask

47.1.1.1/29-

47.1.1.128/32

47.1.3.1/29-

47.1.1.129/32

47.1.1.5/2947.1.1.1

--

2 Set up IP routing

Global OSPF enable

OSPF area

Ethernet OSPF enable

OSPF area

Yes

0.0.0.0

Yes

0.0.0.0

Yes

0.0.0.0

Yes

0.0.0.1


Parameters 6130 A 6130 B 6130 C 6130 D



DCN example 4 - Using OSPF with dual 6130 GNEs to external OSPF backbone.

In this example (see Figure 10-9 on page 10-43 and Figure 10-10 on page 10-44), two 6130 network elements are used as dual GNEs to establish communication between the external DCN and the 6130 sub-system. Typically, the two gateway NEs are located in two different sites and subnets to maximize the network resilience.

Multiple 6130 sub-systems can be connected using Ethernet in between the LAN ports to minimize the number of DCN sites required and to extend the DCN coverage within the engineering limits.

When the 6130 sub-system provides a resilient internal DCN structure (e.g. ring with DCC) so that any link failure inside the ring will not result in losing any connectivity to either of the gateway network elements, the external DCN router, which is acting as the Area Border Router (ABR), can then be configured to use the route summarization feature to group the IP routes for the 6130 sub-network into a single route covering all the 6130 Router ID IP addresses.

When the 6130 sub-system does not provide a resilient internal DCN structure (e.g. linear chain), route summarization should not be used at the ABR or resilient communications will be lost.

Attention: Two or more GNEs can be used within the engineering limits.

DCN provisioning detailsTable 10-11 on page 10-45, Table 10-12 on page 10-45 and Table 10-13 on page 10-46 detail the DCN parameters for the DCN example 4 configuration.




Figure 10-9DCN example 4 - Dual 6130 GNEs with OSPF




Legend


OMEA

OSPF area 0.0.0.1

OSPF area 0.0.0.0




Parameters 6130 A 6130 B 6130 C 6130 D

1 Set up IP address

LAN-1-6 port:


Router ID:

IP addressNetmask

47.1.3.6/29-

47.1.3.65/32

47.1.3.18/28-

47.1.3.66/32

47.1.3.81/30-

47.1.3.67/32

47.1.3.85/30-

47.1.3.68/32

2 Set up IP routing



Enable

0.0.0.1

Enable

0.0.0.1

Enable

0.0.0.1

Enable

0.0.0.1

3 Set up DCC

STM/OC port 1:

ProtocolMTUOSPF

STM/OC port 2:

ProtocolMTUOSPF

PPP1518Enable

PPP1518Enable

PPP1518Enable

PPP1518Enable

PPP1518Enable

PPP1518Enable

PPP1518Enable

PPP1518Enable


Parameters 6130 E 6130 F 6130 G

1 Set up IP address

LAN-1-6 port:


Router ID:

IP addressNetmask

47.1.3.82/30-

47.1.3.69/32

47.1.3.86/30-

47.1.3.70/32

192.168.1.254/24-

47.1.3.71/32

2 Set up IP routing



Enable

0.0.0.1

Enable

0.0.0.1

Disable

0.0.0.1



3 Set up DCC

STM/OC port 1:

ProtocolMTUOSPF

STM/OC port 2:

ProtocolMTUOSPF

PPP1518Enable

PPP1518Enable

PPP1518Enable

PPP1518Enable

PPP1518Enable

PPP1518Enable


Parameters Router 1 Router 2 Router 3 OMEA

1 Set up IP address

Ethernet interface:



IP AddressNetmask

47.1.1.1/29-

47.1.1.128/32

47.1.3.1/29-

47.1.1.129/32

47.1.3.17/28-

47.1.1.130/32

47.1.1.5/2947.1.1.1

--

2 Set up IP routing

Global OSPF enable

OSPF area


OSPF area

Yes

0.0.0.0

Yes

0.0.0.0

Yes

0.0.0.0

Yes

0.0.0.1

Yes

0.0.0.0

Yes

0.0.0.1

-

-


Parameters 6130 E 6130 F 6130 G



6100DCN example 5 - Using single OM4000/3000 GNE with GRE tunnels through OM4000/3000 network to reach remote 6130 network elements in linear spurs off OM4000/3000 NE.

In this example (see Figure 10-11 on page 10-48 and Figure 10-12 on page 10-49), the 6130 NEs are subtended as 1+1 MSP/APS link with OM4000/3000 and IP static routing is used between the router and 6130 NEs through GRE tunnels. The router has a static route over the GRE tunnel to the router ID IP address of the 6100 NE and the 6100 NE has a static route over the GRE tunnel to the router.

Attention: Starting in 6130 Release 4.0, route redistribution between OSPF and iISIS is supported. If OSPF routing is used on the GRE tunnel between the router and the 6130 NE, then the OSPF routes can be redistributed to iISIS at the 6130 NE (i.e. OSI domain). Alternately, static routing can be used on the GRE tunnel as shown in this example.

If the IP addresses (Router ID) of the 6130 NEs are provisioned with different subnets, then dynamic routing (i.e. OSPF or iISIS) or static routing is required between the 6130 NEs and the DCN routers.

For resiliency, a separate OSI GRE tunnel is needed from the external router to each of the 6130 network elements (allowing use of static routing or OSPF routing over SGRE). If resiliency is not required, then only one static IP over OSI GRE tunnel can be provisioned from the router to one of the 6130 NEs. In this configuration, OSPF or static routing can be used over the SGRE). Communication to the other 6130 NE is established using iISIS routing through the OM4000/3000 NE.

The external router redistributes the static IP route into a dynamic routing protocol, in order to advertise the 6130 router IP addresses to the external DCN.

The router on which the IP over OSI GRE tunnels terminate can only be a Cisco router that supports ISO CLNS, with an IOS which has the “IP over CLNS tunnel (CTunnel)” using GRE encapsulation feature. Some older versions of IOS support IP over OSI tunnels using Cisco proprietary encapsulation which is not suitable in this application.





Figure 10-11DCN example 5 - Single OM4K/3K GNE with GRE tunnels to remote 6130 NEs in linear 1+1 MSP/APS with OM4K/3K





Parameters 6130 A 6130 B

1 Set up IP address

LAN-1-6 port:


Router ID:

IP addressNetmask

192.168.1.254/24-

47.1.3.65/32

192.168.1.254/24-

47.1.3.66/32

OMEA

OSPF area 0.0.0.0

Legend




2 Set up IP routing



Static routing 1:


Static routing 2:


Disable

-

47.1.1.0/290.0.0.0SGRE-1No (see Note 1)

47.1.1.129/320.0.0.0SGRE-1No (see Note 1)

Disable

-

47.1.1.0/290.0.0.0SGRE-1No (see Note 1)

47.1.1.129/320.0.0.0SGRE-1No (see Note 1)

3 Set up iISIS (Nodal level)

iISIS Enable:

MAA 1MAA 2MAA 3

Enable

490000--

Enable

490000--

4 Set up DCC

STM/OC port 1:

ProtocolMTUiISIS

STM/OC port 2

ProtocolMTU

LAPD512 (see Note 2)Enable

--


--

5 Set up static GRE tunnel

OSI Local MAA:

MAA 1MAA 2MAA 3

Remote MAA

Remote system ID

NSAP selector

OSPF

MTU for SGRE-1 interface

490000--

490000

Router 2 MAC

2F

Disable

446 (see Note 2)

490000--

490000

Router 2 MAC

2F

Disable

446 (see Note 2)





Note 1: The IP static route can be set to Advertise = No, when a static GRE tunnel is provisioned from the router to each of the 6130 network element. If only one tunnel is provisioned, then the static route should be set to Advertise= Yes.

Note 2: The LAPD MTU is equal to 512 bytes and this corresponds to a MTU of 446 bytes for the IP Layer 3 protocol. This is because the GRE encapsulation adds 66 bytes to the management frames (i.e. 446 + 66 = 512 bytes) so the MTU for the SGRE-1 interface must be set to 446 bytes.

Table 10-15DCN example 5 - Router, OMEA, and OM4K/3K DCN provisioning details

Parameters Router 1 Router 2 OM4K/3K E OM4K/3K C OMEA

1 Set up IP address

Interface:

IP addressNetmask

Interface:


Circuitless IP/ NE-IP:

IP addressNetmask

-

47.1.1.1/29

-

---

47.1.1.128/32

-

--

-

---

47.1.1.129/32

-

--

-

---

--

-

--

-

---

--

-

--

-

47.1.1.5/2947.1.1.1

--

2 Set up IP routing

Global routing

Global OSPF Enable

OSPF area


OSPF area

Static routing 1:

AddressNetmaskNext hop IP addressNext hop interfaceRedistribute

Static routing 2:

AddressNetmaskNext hop IP addressNext hop interfaceRedistribute

-

Yes

0.0.0.0

Yes

0.0.0.0

----

-----

-

Yes

0.0.0.0

No

-

47.1.3.65/3247.1.3.65GRE-1Yes

47.1.3.66/3247.1.3.66GRE-2Yes

iIS-IS

-

-

-

-

----

-----

iIS-IS

-

-

-

-

----

-----

-

-

-

-

-

----

-----





3 Set up DCC

Interface 1:

ProtocolMTU

Interface 2:

ProtocolMTU

Interface 3:

ProtocolMTU

Interface 4:

ProtocolMTU

--

--

--

--

--

--

--

--

S-5-1

LAPD512

S-6-1

LAPD512

--

--

S-5-1

LAPD512

S-6-1

LAPD512

S-1-1

LAPD512

S-2-1

LAPD512

--

--

--

--


OSI Local MAA:

MAA 1MAA 2MAA 3

GRE tunnel 1:

Remote MAARemote system IDNSAP selector

GRE tunnel 2:


39xxx...xx1490000-

---

---

39xxx...xx2490000-

490000NE A MAC2F

490000NE B MAC2F

490000--

---

---

490000--

---

---

---

---

---

Table 10-15 (continued)DCN example 5 - Router, OMEA, and OM4K/3K DCN provisioning details

Parameters Router 1 Router 2 OM4K/3K E OM4K/3K C OMEA



DCN example 6 - Using single OM4000/3000 GNE with GRE tunnels through OM4000/3000 network to reach remote 6130 network elements in SNCP/UPSR ring with an OM4000/3000 network element.

In this example (see Figure 10-13 on page 10-54 and Figure 10-14 on page 10-55), a single ABR is used at the DCN gateway site to establish communication between the external DCN and the 6130/OM4000/3000 sub-systems. A single OM4K/3K is connected to the external DCN via an OSI only enabled port and acts as the GNE for the other OM4K/3K network elements.

For configurations with fully robust (meshed/ring) internal DCN connectivityData communication to the remote subtending 6130 network elements is achieved using IP over OSI GRE tunnels through the OM4K/3K network and these tunnels are terminated directly on the ABR. In order to provide resilient data communication against any fiber breaks in the 6130 system, two tunnels are required from the ABR through the OM4K/3KGNE. iISIS routing is used to establish communication to all 6130 within the ring.

Attention: Starting in 6130 Release 4.0, route redistribution between OSPF and iISIS is supported. If OSPF routing is used on the GRE tunnel between the router and the 6130 NE, then the OSPF routes can be redistributed to iISIS at the 6130 NE (i.e. OSI domain). Alternately, static routing can be used on the GRE tunnel as shown in this example.

If the IP addresses (Router ID) of the 6130 NEs are provisioned with different subnets, then dynamic routing (i.e. OSPF or iISIS) or static routing is required between the 6130 NEs and the DCN routers.

For configurations with non-redundant (linear) internal DCN connectivityData communication to the remote subtending 6130 network elements is achieved using IP over OSI GRE tunnels through the OM4K/3K network and these tunnels are terminated directly on the ABR. In order to provide resilient data communication against any fiber breaks in the 6130 system, two tunnels are required from the ABR through the OM4K/3K GNE. OSPF routing is used to establish communication to all 6130 within the subtending ring.

Attention: OSPF routing can be used on the GRE tunnel to the router and OSPF routing can be used between 6130 network elements.



The ABR on which the IP over OSI GRE tunnels terminate can only be a Cisco router that supports ISO CLNS, with an IOS which has the “IP over CLNS tunnel (CTunnel)” using GRE encapsulation feature. Some older versions of IOS support IP over OSI tunnels using Cisco proprietary encapsulation which is not suitable in this application.



Figure 10-13DCN example 6 - Single OM4K/3K with GRE tunnels to remote 6130 NEs in SNCP/UPSR ring with OM4K/3K





Parameters 6130 A 6130 B 6130 C

1 Set up IP address

LAN-1-6 port:


Router ID:

IP addressNetmask

192.168.1.254/24-

47.1.3.65/32

192.168.1.254/24-

47.1.3.66/32

192.168.1.254/24-

47.1.3.67/32

OMEA

OSPF area 0.0.0.1OSPF area 0.0.0.0

Legend

= IP connection= OSPF routing between NEs= iISIS routing between NEs= Static/Default routing

OSI area



2 Set up IP routing



Static routing 1:


Static routing 2:


Disable

-

47.1.1.0/290.0.0.0SGRE-1Yes (see Note 1)

47.1.1.129/320.0.0.0SGRE-1Yes (see Note 1)

Disable

-

Disable

-

47.1.1.0/290.0.0.0SGRE-1Yes (see Note 1)

47.1.1.129/320.0.0.0SGRE-1Yes (see Note 1)


iISIS Enable:

MAA 1MAA 2MAA 3

Enable

490000--

Enable

490000--

Enable

490000--

4 Set up DCC

STM/OC port 1:

ProtocolMTUiISIS

STM/OC port 2

ProtocolMTUiISIS


PPP1518Enable

PPP1518Enable

PPP1518Enable

PPP1518Enable



OSI Local MAA:

MAA 1MAA 2MAA 3

Remote MAA

Remote system ID

NSAP selector

OSPF


490000--

490000

Router 2 MAC

2F

Disable

446 (see Note 2)

---

-

-

-

-

-

490000--

490000

Router 2 MAC

2F

Disable

446 (see Note 2)





Note 1: The IP static route can be set to Advertise = No if each 6130 network element has a static GRE tunnel to the router.



Parameters Router 1 Router 2 OM4K/3K F OM4K/3K D OMEA

1 Set up IP address

Interface:

IP addressNetmask

Interface:



IP addressNetmask

-

47.1.1.1/29

-

---

47.1.1.128/32

-

--

-

---

47.1.1.129/32

-

--

-

---

--

-

--

-

---

--

-

--

-

47.1.1.5/2947.1.1.1

--

2 Set up IP routing

Global Routing

Global OSPF enable

OSPF area


OSPF area

Static routing 1:

AddressNetmaskNext hop IP addressNext hop interface

Static routing 2:


-

Yes

0.0.0.0

Yes

0.0.0.0

-

Yes

0.0.0.0

No

-

47.1.3.64/2947.1.3.65GRE Tunnel 1

47.1.3.67/3247.1.3.67GRE Tunnel 2

IS-IS

-

-

-

-

IS-IS

-

-

-

-

-

-

-

-

-





3 Set up DCC

Interface 1:

ProtocolMTU

Interface 2:

ProtocolMTU

Interface 3:

ProtocolMTU

Interface 4:

ProtocolMTU

--

--

--

--

--

--

--

--

S-5-1

LAPD512

S-6-1

LAPD512

--

--

S-5-1

LAPD512

S-6-1

LAPD512

S-1-1

LAPD512

S-2-1

LAPD512

--

--

--

--

4 Set up GRE tunnel

OSI Local MAA:

MAA 1MAA 2MAA 3

GRE tunnel 1:


GRE tunnel 2:


39xxx...xx1490000-

---

---

39xxx...xx2490000-

490000NE A MAC2F

490000NE C MAC2F

490000--

---

---

490000--

---

---

---

---

---


Parameters Router 1 Router 2 OM4K/3K F OM4K/3K D OMEA



DCN example 7 - Using dual OM4000/3000 GNEs with GRE tunnels through OM4000/3000 network to reach remote 6130 network elements in SNCP/UPSR ring with generic SONET/SDH network elements.

In this example (see Figure 10-15 on page 10-60 and Figure 10-16 on page 10-61), similar to previous configuration, but with multiple gateway locations with GNEs and routers to maximize the resilience of this solution.

The ABR on which the IP over OSI GRE tunnels terminate can only be a Cisco router that supports ISO CLNS, with an IOS which has the “IP over CLNS tunnel (CTunnel)” using GRE encapsulation feature. Some older versions of IOS support IP over OSI tunnels using Cisco proprietary encapsulation which is not suitable in this application.

Attention: If the IP addresses (Router ID) of the 6130 NEs are provisioned with different subnets, then dynamic routing (i.e. OSPF or iISIS) or static routing is required between the 6130 NEs and the DCN routers.





Figure 10-15DCN example 7 - Dual OM4K/3K GNEs with GRE tunnels to remote 6130 NEs in SNCP/UPSR ring with OM4K/3K






1 Set up IP address

LAN-1-6 port:


Router ID:

IP addressNetmask

192.168.1.254/24-

47.1.3.65/32

192.168.1.254/24-

47.1.3.66/32

192.168.1.254/24-

47.1.3.67/32

OMEA


Legend


OSI area



2 Set up IP routing



Static routing 1:


Static routing 2:


Disable

-

47.1.1.0/290.0.0.0SGRE-1Yes (see Note 1)

47.1.1.129/320.0.0.0SGRE-1Yes (see Note 1)

Disable

-

Disable

-

47.1.1.0/290.0.0.0SGRE-1Yes (see Note 1)

47.1.1.130/320.0.0.0SGRE-1Yes (see Note 1)


iISIS Enable:

MAA 1MAA 2MAA 3

Enable

490000--

Enable

490000--

Enable

490000--

4 Set up DCC

STM/OC port 1:

ProtocolMTUiISIS

STM/OC port 2

ProtocolMTUiISIS


PPP1518Enable

PPP1518Enable

PPP1518Enable

PPP1518Enable


5 Set up GRE tunnel

OSI Local MAA:

MAA 1MAA 2MAA 3

Remote MAA

Remote system ID

NSAP selector

OSPF


490000--

490000

Router 2 MAC

2F

Disable

446 (see Note 2)

---

-

-

-

-

-

490000--

490000

Router 3 MAC

2F

Disable

446 (see Note 2)





Note 1: The IP static route can be set to Advertise = No if each 6130 network element has a static GRE tunnel to the router.



Parameters Router 1 Router 2 Router 3 OM4K/3K F, G & H

OM4K/3K D & E

OMEA

1 Set up IP address

Interface:

IP addressNetmask

Interface:



IP addressNetmask

-

47.1.1.1/29

-

---

47.1.1.128/32

-

--

-

---

47.1.1.129/32

-

--

-

---

47.1.1.130/32

-

--

-

---

--

-

--

-

---

--

-

--

-

47.1.1.5/2947.1.1.1

--

2 Set up IP routing

Global Routing

Global OSPF enable

OSPF area


OSPF area

Static routing 1:


-

Yes

0.0.0.0

Yes

0.0.0.0

-

Yes

0.0.0.0

No

-

47.1.3.64/2947.1.3.65GRE Tunnel

-

Yes

0.0.0.0

No

-

47.1.3.64/2947.1.3.67GRE Tunnel

IS-IS

-

-

-

-

IS-IS

-

-

-

-

-

-

-

-

-





3 Set up DCC

Interface 1:

ProtocolMTU

Interface 2:

ProtocolMTU

Interface 3:

ProtocolMTU

Interface 4:

ProtocolMTU

--

--

--

--

--

--

--

--

--

--

--

--

S-5-1

LAPD512

S-6-1

LAPD512

--

--

S-5-1

LAPD512

S-6-1

LAPD512

S-1-1

LAPD512

S-2-1

LAPD512

--

--

--

--

4 Set up GRE tunnel

OSI Local MAA:

MAA 1MAA 2MAA 3

GRE tunnel 1:


39xxx...xx1490000-

---

39xxx...xx2490000-

490000NE A MAC2F

39xxx...xx2490000-

490000NE C MAC2F

490000--

---

490000--

---

---

---


Parameters Router 1 Router 2 Router 3 OM4K/3K F, G & H

OM4K/3K D & E

OMEA



DCN example 8 - Using single 6130 GNE with iISIS through OM4000/3000 network to reach remote 6130 network elements in SNCP/UPSR rings with OM4000/3000 network elements. Proxy ARP used at 6130 GNE for access to remote 6130 NEs.

In this example (see Figure 10-17 on page 10-66 and Figure 10-18 on page 10-67), 6130 network elements use iISIS routing to establish communication to the remote 6130 through the OM4K/3K network.

Connection between 6130 and OM4K/3K is over SONET/SDH with DCC enabled, with iISIS between various sub-tending 6130 NEs in SNCP/UPSR rings to provide resilience without the need for additional 6130 GNEs. The auto-tunnel interface (AGRE) should have a static route provisioned within the subnet of the 6130 network elements. The remote 6130 NEs are provisioned as proxy ARP neighbours at the 6130 GNE.

An OSI enabled router can be used for the OSI communication for the OM4K/3K to the DCN network.

Attention: If the IP addresses (Router ID and Ethernet IP) of the 6130 NEs are provisioned with different subnets, then dynamic routing (i.e. OSPF or iISIS) or static routing is required between the 6130 NEs connected to the LAN and the DCN routers.

DCN provisioning detailsTable 10-20 on page 10-67, Table 10-21 on page 10-68, Table 10-22 on page 10-70 and Table 10-23 on page 10-71 detail the DCN parameters for the DCN example 8 configuration.




Figure 10-17DCN example 8 - Single 6130 GNE with iISIS routing in SNCP/UPSR rings with OM4K/3K






1 Set up IP address

LAN-1-6 port:


Router ID:

IP addressNetmask

192.168.1.254/24-

47.1.3.73/32

192.168.1.254/24-

47.1.3.74/32

192.168.1.254/24-

47.1.3.75/32

OMEA

OSI area 0.0.0.2

OSPF area 0.0.0.0

Legend

= IP connection

= OSPF routing between NEs/Router

= iISIS routing between NEs

= Static/Default routing



2 Set up IP routing



Static routing 1


Disable

-

0.0.0.0 (see Note:)/00.0.0.0AGRENo

Disable

-

0.0.0.0 (see Note:)/00.0.0.0AGRENo

Disable

-

0.0.0.0 (see Note:)/00.0.0.0AGRENo


iISIS Enable:

MAA 1MAA 2MAA 3

Enable

490000--

Enable

490000--

Enable

490000--

4 Set up DCC

STM/OC port 1:

ProtocolMTUiISIS

STM/OC port 2

ProtocolMTUiISIS

LAPD512Enable

PPP1518Enable

PPP1518Enable

PPP1518Enable

PPP1518Enable

LAPD512Enable

Note: Prior to Release 4, the AGRE network interface and the static route 0.0.0.0/0 for the AGRE interface were automatically created when iISIS is enabled for the NE. Starting in Release 4, then default 0.0.0.0/0 AGRE route is not added automatically when iISIS is enabled. This route does not need to be added if there are other provisioned or learned routes that can be used to reach the nodes.


Parameters 6130 D 6130 E 6130 F(see Note 1)

1 Set up IP address

LAN-1-6 port:


Router ID:

IP addressNetmask

192.168.1.254/24-

47.1.3.76/32

192.168.1.254/24-

47.1.3.77/32

47.1.3.66/28-

47.1.3.66/32





2 Set up IP routing



Static routing 1


Static routing 2


Static routing 3


Disable

-

-

0.0.0.0 (see Note 2)/00.0.0.0AGRENo

Disable

-

-

0.0.0.0 (see Note 2)/00.0.0.0AGRENo

Disable

-

0.0.0.0 (see Note 2)/00.0.0.0AGRENo

47.1.3.72/290.0.0.0AGRENo

47.0.0.0/847.1.3.65Eth0Yes

3 Set up DCC

STM/OC port 1:

ProtocolMTUiISIS

STM/OC port 2

ProtocolMTUiISIS

LAPD512Enable

PPP1518Enable

PPP1518Enable

LAPD512Enable

LAPD512Enable

---


iISIS Enable:

MAA 1MAA 2MAA 3

Enable

490000--

Enable

490000--

Enable

490000--





5 Set up Proxy ARP Neighbours

Proxy ARP Neighbour IP addresses:

Neighbour 1Neighbour 2Neignbour 3Neighbour 4Neighbour 5

- -

47.1.3.7347.1.3.7447.1.3.7547.1.3.7647.1.3.77

Note 1: The 6130 F (GNE) is being managed via the Eth0 IP address.

Note 2: Prior to Release 4, the AGRE network interface and the static route 0.0.0.0/0 for the AGRE interface were automatically created when iISIS is enabled for the NE. Starting in Release 4, then default 0.0.0.0/0 AGRE route is not added automatically when iISIS is enabled. This route does not need to be added if there are other provisioned or learned routes that can be used to reach the nodes.

Table 10-22DCN example 8 - OM4K/3K DCN provisioning details

Parameters OM4K/3K H OM4K/3K J OM4K/3K K OM4K/3K L OM4K/3K M

1 Set up IP routing

Global Routing

Global OSPF enable

OSPF area


OSPF area

IS-IS

-

-

-

-

IS-IS

-

-

-

-

IS-IS

-

-

-

-

IS-IS

-

-

-

-

IS-IS

-

-

-

-

2 Set up DCC

Interface 1:

ProtocolMTU

Interface 2:

ProtocolMTU

Interface 3:

ProtocolMTU

Interface 4:

ProtocolMTU

S-5-1

LAPD512

S-6-1

LAPD512

S-1-1

LAPD512

S-2-1

LAPD512

S-5-1

LAPD512

S-6-1

LAPD512

S-1-1

LAPD512

S-2-1

LAPD512

S-5-1

LAPD512

S-6-1

LAPD512

S-1-1

LAPD512

S-2-1

LAPD512

S-5-1

LAPD512

S-6-1

LAPD512

S-1-1

LAPD512

-

--

S-5-1

LAPD512

S-6-1

LAPD512

-

--

-

--





Table 10-23DCN example 8 - Router and OMEA DCN provisioning details

Parameters Router 1 Router 2 Router 3 OMEA

1 Set up IP address

Interface:

IP addressNetmask

Interface:



IP addressNetmask

-

47.1.1.1/29

-

---

47.1.1.128/32

-

--

Eth0: OSI

---

47.1.1.129/32

-

--

Eth0: IP

47.1.3.65/28-

47.1.1.130/32

-

--

-

47.1.1.5/2947.1.1.1

--

2 Set up IP routing

Global OSPF enable

OSPF area


OSPF area

Static routing 1


Yes

0.0.0.0

Yes

0.0.0.0

Yes

0.0.0.0

No

-

Yes

0.0.0.0

No

-

-----

-

-

-

-



DCN example 9 - Using single 6500 GNE with iISIS through 6500 network to reach remote 6130 network elements.

In this example (see Figure 10-19 on page 10-73 and Figure 10-20 on page 10-74), a single 6500 network element is used as the GNE to establish communication between the external DCN and the 6130 and the 6500 network elements.

iISIS routing protocol is used with auto-tunneling to establish communication from the 6500 GNE to the remote 6130 through the 6500 network.

The remote 6130 NEs are provisioned as proxy ARP neighbours at the 6500 GNE.





Figure 10-19DCN example 9 - Single 6500 GNE with iISIS to remote 6130 NEs






1 Set up IP address

LAN-1-6 port:


Router ID:

IP addressNetmask

192.168.1.254/24-

47.1.3.65/32

192.168.1.254/24-

47.1.3.66/32

192.168.1.254/24-

47.1.3.67/32

OMEA

OSI area 0002

OSPF area 0.0.0.0

Legend

= IP connection

= OSPF routing between NEs/Router

= iISIS routing between NEs

= Static/Default routing

IP DCN



2 Set up IP routing



Static routing 1


Disable

-

0.0.0.0 (see Note:)/00.0.0.0AGRENo

Disable

-

0.0.0.0 (see Note:)/00.0.0.0AGRENo

Disable

-

0.0.0.0 (see Note:)/00.0.0.0AGRENo


iISIS Enable:

MAA 1MAA 2MAA 3

Enable

490000--

Enable

490000--

Enable

490000--

4 Set up DCC

STM/OC port 1:

ProtocolMTUiISIS

STM/OC port 2:

ProtocolMTUiISIS

PPP1518Enable

PPP1518Enable

PPP1518Enable

PPP1518Enable

PPP1518Enable

PPP1518Enable

Note: Prior to Release 4, the AGRE network interface and the static route 0.0.0.0/0 for the AGRE interface were automatically created when iISIS is enabled for the NE. Starting in Release 4, then default 0.0.0.0/0 AGRE route is not added automatically when iISIS is enabled. This route does not need to be added if there are other provisioned or learned routes that can be used to reach the nodes.


Parameters 6500 H 6500 G 6500 F

1 Set up IP address

Interface:

IP addressNetmask


IP addressNetmask

COLAN-X

47.1.3.11/25

47.1.3.92/32

-

--

47.1.3.93/32

-

--

47.1.1.94/32





2 Set up IP routing

Global Routing

Static routing 1

IP SubnetNetmaskNext hop IP addressNext hop interface

Static route redistribution

AddressNetmaskMetric Type


OSPF area

iIS-IS

47.0.0.0/847.1.3.1COLAN-X

47.0.0.0/8External

-

-

iIS-IS

----

---

-

-

iIS-IS

----

---

-

-

3 Set up DCC

Interface 1:

ProtocolMTU

Interface 2:

ProtocolMTU

Interface 3:

ProtocolMTU

Interface 4:

ProtocolMTU

S-5-1

PPP1500

S-6-1

PPP1500

-

--

-

--

S-5-1

PPP1500

S-6-1

PPP1500

-

--

-

--

S-1-1

PPP1500

S-2-1

PPP1500

S-5-1

PPP1500

S-6-1

PPP1500

4 Set up MAA

OSI Local MAA:

MAA 1MAA 2MAA 3

490000--

490000--

490000--

5 Set up Proxy ARP


Neighbour 1Neighbour 2Neignbour 3Neighbour 4Neighbour 5

47.1.3.6547.1.3.6647.1.3.6747.1.3.9347.1.3.94

- -


Parameters 6500 H 6500 G 6500 F





1 Set up IP address

Interface:

IP addressNetmask

Interface:



IP addressNetmask

-

47.1.1.1/29

-

---

47.1.1.128/32

-

47.1.3.1/25

-

---

47.1.1.129/32

-

--

-

47.1.1.5/2947.1.1.1

--

2 Set up IP routing

Global OSPF enable

OSPF area


OSPF area

Yes

0.0.0.0

Yes

0.0.0.0

Yes

0.0.0.0

No

-

-

-

-

-



DCN example 10 - Using single 6500 GNE with iISIS to reach remote 6130 network elements in a SNCP/UPSR ring configuration with generic SDH/SONET equipment.

In this example (see Figure 10-21 on page 10-79, Figure 10-22 on page 10-80 and Figure 10-23 on page 10-81), a single 6500 network element is used as the GNE to establish communication between the external DCN and the 6130 within a SNCP/UPSR ring with generic SONET/SDH equipment (such as OM3000, OM4000 and TN-1C network elements).

iISIS routing protocol is used with auto-tunneling to establish communication from the 6500 GNE to the remote 6130 network elements.

The remote 6130 NEs are provisioned as proxy ARP neighbours at the 6500 GNE.





Figure 10-21DCN example 10 - Single 6500 with iISIS to reach remote 6130 NEs in SNCP/UPSR with generic SDH/SONET equipment




Legend


OMEA

OSPF area 0.0.0.0

OSI area 0002



Figure 10-23DCN example 10 - iIS-IS / IS-IS logical view



Table 10-27DCN example 10 - 6130, 6500, and OSI NE DCN provisioning details

Parameters 6130 A 6130 B NE C NE F 6500 G 6500 H

1 Set up IP address

LAN-1-6 port:


Router ID:

IP addressNetmask

192.168.1.254/24-

47.1.3.65/32

192.168.1.254/24-

47.1.3.66/32

---

--

---

--

---

47.1.3.93/32

COLANX

47.1.3.2/25-

47.1.3.92/32

2 Set up IP routing

Global Routing

Route redistribution

LAN-1-6/Ethernet port OSPF mode


Static routing 1



AddressNetmaskMetric Type

-

-

Disable

-

0.0.0.0/00.0.0.0AGRENo

-

-

Disable

-

0.0.0.0/00.0.0.0AGRENo

IS-IS

-

-

-

IS-IS

-

-

-

iIS-IS

-

-

-

iIS-IS


No

-

47.0.0.0/847.1.3.1COLAN-X-

47.0.0.0/8External


iISIS Enable:

MAA 1MAA 2MAA 3

Enable

490000--

Enable

490000--



4 Set up DCC

Interface 1:

ProtocolMTUiISIS

Interface 2

ProtocolMTUiISIS

Interface 3

ProtocolMTU

Interface 4

ProtocolMTU

STM/OC P1

LAPD512Enable

STM/OC P2

PPP1518Enable

-

--

-

--

STM/OC P1

PPP1518Enable

STM/OC P2

LAPD512Enable

-

--

-

--

S-5-1

LAPD512

S-6-1

LAPD512

-

--

-

--

S-5-1

LAPD512

S-6-1

LAPD512

S-1-1

LAPD512

S-2-1

LAPD512

S-5-1

LAPD512Yes

S-6-1

PPP1500Yes

-

--

-

--

S-5-1

PPP1500Yes

S-6-1

LAPD512Yes

-

--

-

--

5 Set up Proxy ARP


Neighbour 1Neighbour 2Neignbour 3

- - - - -

47.1.3.6547.1.3.6647.1.3.93



1 Set up IP address

Interface:

IP addressNetmask

Interface:



IP addressNetmask

47.1.1.1/29

-

---

47.1.1.128/32

47.1.3.1/25

-

---

47.1.1.129/32

-

--

-

47.1.1.5/2947.1.1.1

--

2 Set up IP routing

Global OSPF enable

OSPF area


OSPF area

Yes

0.0.0.0

Yes

0.0.0.0

Yes

0.0.0.0

No

-

-

-

-

-

Table 10-27 (continued)DCN example 10 - 6130, 6500, and OSI NE DCN provisioning details

Parameters 6130 A 6130 B NE C NE F 6500 G 6500 H



DCN example 11 - Using VC12 management channels through OM4000 network to reach remote 6130 network elements in SNCP ring with OM4000 and legacy OSI network elements. Transparent DCC used to provided resilient OSI communications.

In this example (see Figure 10-24 on page 10-85 and Figure 10-25 on page 10-86), VC12 management channels are used to establish communication between the external DCN and the 6130 network element in a SNCP ring of 6130, OM4000 and legacy OSI network elements.

Attention: This example is only applicable to SDH networks, as VC12 management channels are currently supported only for 6130 network elements provisioned in SDH mode.

Dual OM4000 network elements are connected to the external DCN via an OSI only enabled port and act as the GNEs for the other OM4000 and legacy OSI network elements.

Data communication to the remote subtending 6130 network elements is achieved using VC12 management channels through the OM4000 network and are directly terminated on the routers. In order to provide resilient data communication against any fiber breaks in the 6130 system, two VC12 management channels are required from the routers to two 6130 network elements on the ring. Transparent DCC is provisioned on the 6130 network elements to provide resilient data communications between the OM4000 and the OSI legacy equipment.

Attention: OSPF routing protocol will be used on the VC12 management channels to the DCN routers.

The VC12 management channel can be terminated on a physical E1 interface on the external DCN router. An E1 connection must be provisioned from the OM4000 GNE to the router.





Figure 10-24DCN example 11 - VC12 management channels to remote 6130 NEs in SNCP ring with OM4K and legacy OSI network elements






1 Set up IP address

LAN-1-6 port:


Router ID:

IP addressNetmask

192.168.1.254/24-

47.1.3.65/32

192.168.1.254/24-

47.1.3.66/32

192.168.1.254/24-

47.1.3.67/32

2 Set up IP routing



Disable

0.0.0.1

Disable

0.0.0.1

Disable

0.0.0.1

OMEA

OSPF area 0.0.0.1

OSPF area 0.0.0.0

Legend

= IP connection= OSPF routing between NEs



3 Set up VC12 Management Channels

MGMT-1:

TypeMTULayer 2 ProtocolOSPFOSPF area

MGMT-2

TypeMTULayer 2 ProtocolOSPFOSPF area

VC121500PPP, HDLC FramingEnable0.0.0.1






4 DCC Overhead Tunnel

Source Port:Destination Port:Overhead Byte

STM/OC port 1STM/OC port 2DCC_M



Table 10-30DCN example 11 - OSI NE and OM4000 DCN provisioning details

Parameters NE D NE E OM4000 F OM4000 G OM4000 H

1 Set up IP address

Interface:

IP addressNetmask

Interface:



IP addressNetmask

-

--

-

---

--

-

--

-

---

--

-

--

-

---

--

-

--

-

---

--

-

--

-

---

--

2 Set up IP routing

Global OSPF enable

OSPF area


OSPF area

IS-IS

-

-

-

IS-IS

-

-

-

IS-IS

-

-

-

IS-IS

-

-

-

IS-IS

-

-

-





3 Set up DCC

Interface 1:

ProtocolIP MTU

Interface 2:

ProtocollP MTU

Interface 3:

ProtocollP MTU

Interface 4:

ProtocollP MTU

S-5-1

LAPD512

S-6-1

LAPD512

--

--

S-5-1

LAPD512

S-6-1

LAPD512

--

--

S-5-1

LAPD512

S-6-1

LAPD512

S-1-1

LAPD512

S-2-1

LAPD512

S-5-1

LAPD512

S-6-1

LAPD512

--

--

S-5-1

LAPD512

S-6-1

LAPD512

--

--

4 E1 Connection

E1 Connection to Router No No No Yes Yes


Parameters Router 1 Router 2 (see Note:)

Router 3(see Note:)

OMEA

1 Set up IP address

Interface:


Circuitless IP/ loopback:

IP addressNetmask

47.1.1.1/29-

47.1.1.128/32

47.1.3.1/29-

47.1.1.129/32

47.1.3.17/28-

47.1.1.130/32

47.1.1.5/2947.1.1.1

2 Set up IP routing

Global OSPF enable

OSPF area


OSPF area

Yes

0.0.0.0

Yes

0.0.0.0

Yes

0.0.0.0

No

-

Yes

0.0.0.0

No

-

-

-

Table 10-30 (continued)DCN example 11 - OSI NE and OM4000 DCN provisioning details

Parameters NE D NE E OM4000 F OM4000 G OM4000 H



3 Set up E1 interface

Interface 1:

OSPFMTUOSFP area

---

E1 interface

Enable15000.0.0.1

E1 interface

Enable15000.0.0.1

---

Note: This solution was validated with a Cisco Router.

Table 10-31 (continued)DCN example 11 - Router and OMEA DCN provisioning details

Parameters Router 1 Router 2 (see Note:)

Router 3(see Note:)

OMEA



DCN example 12 - Using E1 and VC12 management channels to reach remote 6130 network elements in SNCP ring with OM4000 and legacy OSI network element. Transparent DCC used to provided resilient OSI communications.

In this example (see Figure 10-26 on page 10-91 and Figure 10-27 on page 10-92), E1 and VC12 management channels are used to establish communication between the external DCN and the 6130 network element in a SNCP ring of 6130, OM4000 and legacy OSI network elements.

Attention: This example is only applicable to SDH networks, as E1 and VC12 management channels are currently supported only for 6130 network elements provisioned in SDH mode.

The OM4000 network element is connected to the external DCN via two paths. An OSI connection to the OSI router, and an E1 connection to the IP router. The OM4000 acts as the GNE for the legacy OSI network element.

Data communication to the 6130 GNE is achieved using direct E1 management channel to the external DCN router. Connectivity to the remote 6130 is achieved using a mix of E1 and VC12 management channels through the OM4000 and legacy OSI network elements. In order to provide resilient data communication against any fiber breaks in the 6130 system, management channels are required from the routers to both 6130 network elements on the ring. Transparent DCC is provisioned on the 6130 network elements to provide resilient data communications between the OM4000 and the OSI legacy equipment.

Attention: OSPF routing protocol will be used on the E1 and VC12 management channels.

If the iISIS protocol is used between the 6130 NEs for DCC communication, then OSPF cannot be used on the E1 management channel. In this case, static routes need to be provisioned between the router and the gateway 6130 NE.

The VC12 management channel can be terminated on a physical E1 interface on the OSI network element. An E1 connection must be provisioned from the OM4000 GNE to the router.





Figure 10-26DCN example 12 - E1 and VC12 management channels to remote 6130 NEs in SNCP ring with OM4K and legacy OSI network elements






1 Set up IP address

LAN-1-6 port:


Router ID:

IP addressNetmask

192.168.1.254/24-

47.1.3.65/32

192.168.1.254/24-

47.1.3.66/32

2 Set up IP routing



Disable

0.0.0.1

Disable

0.0.0.1

Legend


OMEA




3 Set up E1 and VC12 Management Channels

MGMT-1:

TypeMTULayer 2 ProtocolMagic NumberOSPF

MGMT-2

TypeMTULayer 2 ProtocolMagic NumberOSPF

E11500Standard PPP, RFC 1661EnableEnable

VC121500PPP, HDLC Framing DisableEnable

VC121500PPP, HDLC FramingDisableEnable

VC121500PPP, HDLC FramingDisableEnable

4 DCC Overhead Tunnel

Source Port:Destination Port:Overhead Byte



Table 10-33DCN example 12 - OSI NE and OM4000 DCN provisioning details

Parameters NE C OM4000 D

1 Set up IP address

Interface:

IP addressNetmask

Interface:



IP addressNetmask

-

--

-

---

--

-

--

-

---

--

2 Set up IP routing

Global OSPF enable

OSPF area


OSPF area

IS-IS

-

-

-

IS-IS

-

-

-





3 Set up DCC

Interface 1:

ProtocolIP MTU

Interface 2:

ProtocollP MTU

S-5-1

LAPD512

S-6-1

LAPD512

S-5-1

LAPD512

S-6-1

LAPD512

4 E1 Connection

E1 Connection to Router No Yes


Parameters Router 1 Router 2(see Note:)

Router 3(see Note:)

OMEA

1 Set up IP address

Interface:


Circuitless IP/ loopback:

IP addressNetmask

47.1.1.1/29-

47.1.1.128/32

47.1.3.1/29-

47.1.1.129/32

47.1.3.17/28-

47.1.1.130/32

47.1.1.5/2947.1.1.1

2 Set up IP routing

Global OSPF enable

OSPF area


OSPF area

Yes

0.0.0.0

Yes

0.0.0.0

Yes

0.0.0.0

No

-

Yes

0.0.0.0

No

-

-

-

3 Set up E1 interface

Interface 1:

OSPFIP MTUOSPF area

Interface 2:

OSPFIP MTUOSPF area

---

E1 interface

Enable15000.0.0.1

E1 interface

Enable15000.0.0.1

---

---

Note: This solution was validated with a Cisco Router.

Table 10-33 (continued)DCN example 12 - OSI NE and OM4000 DCN provisioning details

Parameters NE C OM4000 D



IP networks, addressing, and masksThis section briefly explains the concepts of IP (Internet Protocol, version 4) addressing and uses examples from DCN to illustrate.

• Every interface within an IP system must have a unique IP address (four bytes expressed in decimal and separated by dots [for example, 192.168.12.43]). For more information on this notation, refer to Dotted decimal notation for IP addresses on page 10-96.

• The IP addresses available for the system are divided into networks and further subdivided into subnetworks.

• Devices must be grouped together such that they are directly connected only to other devices with IP addresses conforming to the same subnetwork addresses.

• There are two groups of networks: public and private networks.

— Public networks are those networks which can be connected to the Internet; therefore they are accessible from any device outside that network, as long as this device is also connected to the Internet.

— Private networks are isolated from the outside world; therefore they cannot be connected to the Internet, and as such they are not accessible by any device that does not belong to the same network. Well-defined ranges of addresses are reserved for private networks.

– One of the address ranges available for private networks is 192.168.x.y (x = 0 to 255, y = 0 to 255, which is the decimal representation of an 8-bit binary number); ‘x’ is the part of the IP address which is available for the network address. For example, 192.168.1.0, 192.168.2.0, and 192.168.3.0 are three different network addresses. Every device or interface connected to network 192.168.1.0 must have an IP address that is 192.168.1.y, where ‘y’ is the part of the IP address which is available for both the subnetworks and the host ID (identifier).

• The subnetwork mask identifies the number of bits allocated to the host ID and the number allocated to the subnetwork.

• When subnetting a network, two addresses are not available: those identified by all ones (used as a broadcast address), and all zeros (reserved by convention as it is used to identify the network).

• As for subnets, host addresses of all ones (broadcast) and all zeros (by convention) are not available.

• The network designer will decide how many bits define the subnetwork and how many define the host ID, according to the actual and possible future network architecture.



It is important to note that the original distinction of addresses between classes A, B, and C did not allow the network designer to vary the length of the subnetwork mask once an IP address was assigned. In fact, classes A, B, and C defined a rigid scheme for assigning the number of bits which identify the networks, and those which identify the host ID, regardless of the network designer’s needs. For its intrinsic limits, the notation for classes A, B, and C is no longer used.

The next section of this information shows the bit significance of the dotted decimal notation.

Dotted decimal notation for IP addressesAn IP address is 32 bits long. To aid memory of this string of digits, the address is split into 4 groups of 8 bits each. These are represented by a decimal number between 0 and 255 for ease of display. The decimal number has no other significance.

The decimal number represented by the eight bits can be determined by looking up the decimal value of each bit and then simply adding them up:

• 00000001 is represented by 1








Example: 10010001




• Total 145

An IP address contains a 32-bit address field and a 32-bit subnet mask. The mask defines which part of the address is a network address and which is a device address. The mask thus allows a router to decide whether the address of the packet is destined for one of the subnets to which it is connected. For example:

An address of 47.9.64.172 has a mask of 255.255.240.0; the mask is AND’ed with the address:



Address of packet is:

00101111.00001001.01000000.10101100Mask is:

11111111.11111111.11110000.00000000This means that the network part of the address is:

00101111.00001001.01000000.00000000The device part of the address is:

00000000.00000000.00000000.10101100occupying the last 12 bits.

CIDR (Classless Inter-Domain Routing) addresses represent masks in a different way. A CIDR address is defined by a starting address and a mask which defines the size of the address allocation. For example:

An allocation of addresses in the range 196.0.16.0 to 196.0.31.255 can be represented by:

196.0.16.0/20 (see note)where the 20 is a mask of 20 contiguous 1 bits.

Start address is:

11000100.00000000.00010000.00000000End address is:

11000100.00000000.00011111.11111111And the mask is:

11111111.11111111.11110000.00000000

The last 12 bits are available to the user to use as subnet address and device address.

Attention: This notation is conventional for CIDR addresses. However, the method in which an IP address is configured can vary according to the router where it is performed. For example, the IP address notation 196.0.16.0/20 can be used to configure a Cisco router, whereas Ciena routers require the full notation 196.0.16.0 with the subnetwork mask 255.255.240.0. There is no substantial difference between these two methods.



Circuitless IP interfaceA circuitless IP interface is a virtual interface that exists in software only. The special property of this interface is that it always exists and is therefore always included in the routing tables. Ethernet and serial interfaces cease to exist if a connector falls out, or if the device at the other end of the cable fails for any reason. The interface then shuts down and is removed from the routing tables. Note that circuitless IP is a Bay term; Cisco uses the term ‘loopback’ for these interfaces. Having an interface that always exists within a router is very useful for the following reasons:

1 If a tunnel is set up between two router interfaces and one of the interfaces fails, the tunnel fails. However, when the tunnel is set up between two circuitless IP interfaces, if the normal route fails, the tunnel is re-routed if another route exists and does not fail.

2 If during a Telnet session on a router the interface to which the session is connected goes down, then the session is lost. Another connection via the IP address of an alternative interface must be made. If Telnet sessions are set up to connect to the router using the circuitless IP interface, then loss of one interface is not a problem, providing the router has at least one working IP interface.

3 Other interfaces can be referenced to the circuitless IP interface. This is known as an unnumbered interface. This applies only to point-to-point interfaces (that is, not an Ethernet port). This reduces the number of IP addresses needed.

Attention: It is more difficult to find faults in a network with an unnumbered link, and topologies from some network management systems are easier to follow with unnumbered serial links. The use of unnumbered links is still permissible where sufficient IP addressing space is not available.

4 The circuitless IP interface identifies a router for OSPF (Open Shortest Path First), tunnelling, and management.

ARPARP (Address Resolution Protocol) is used to map IP addresses to LAN (Local Area Network) hardware addresses. When a host wishes to send a packet to a host on another network, it sends the packet to its gateway for forwarding. It can also do the same for a packet destined for a host within the same network but it leads to excessively high traffic levels, especially if a large number of hosts are on the LAN. Therefore, in order to reduce the traffic on a LAN, a node uses ARP with another node when it determines that the destination address is on a directly attached network. The node can determine if the host is local by comparing the network portion of its own IP address (including the subnet) with the target address.

Therefore, in order to avoid using the gateway, the originating host needs to determine the destination host’s local data link layer address. It achieves this by sending out an ARP request message containing its own IP address and



data link layer address, and the IP address of the destination host. This message is sent via the gateway. The destination host then responds with an ARP reply message containing its own data link layer address and uses the originating host’s data link layer address as the destination address. Thus the reply does not need to go via the gateway. The originating host and destination host store the learned network and data link layer address pairing in their ARP caches for future use, thus avoiding the use of the gateway altogether. The rest of the hosts on the LAN build up similar caches, thus reducing LAN traffic.

IP routing protocolsThe primary function of IP, which resides at the network layer (3) of the OSI (Open Systems Interconnect) model, is to receive data from the higher layer protocols (TCP [Transmission Control Protocol] or UDP [User Datagram Protocol] layers) on a source host, create a datagram and route the datagram through a network to a destination host. Secondary functions of IP include fragmentation and reassembly of the datagram, and packet lifetime control. The most important IP routing protocols are explained in the following sections.

OSPFOSPF (Open Shortest Path First) is an open protocol, as defined in Request For Comments (RFC) 1247. It is based on the Dijkstra’s ‘Shortest Path First’ algorithm, which is a link state routing mechanism.

In an OSPF network, each router maintains a link-state database that describes the topology of the autonomous system (AS). The database contains the local state for each router in the AS, including the router’s usable interfaces and reachable neighbors. Each router periodically checks for changes in its local state and shares any changes detected by flooding link-state advertisements (LSAs) throughout the AS. Routers synchronize their topological databases based on the sharing of information from LSAs.

From the topological database, each router constructs a shortest-path tree, with itself as the root. The shortest-path tree gives the optimal route to each destination in the AS. Routing information from outside the AS appears on the tree as leaves. OSPF routes IP traffic based solely on the destination IP address and subnet mask, and IP Type of Service (TOS) contained in the IP packet header.

OSPF is designed specifically for use on larger networks, providing several features to reduce the amount of traffic and processing overhead associated with the routing protocol. Amongst these features are the ability to segment a large network into a number of areas, and route summarization, a technique which greatly reduces the volume of route advertisement traffic where the addressing scheme is hierarchical.



The manner in which a network is segmented into areas is governed by strict rules. There is a core area—known as the backbone area—which is area 0.0.0.0, sometimes referred to as area 0. All other areas are connected directly to the backbone area, or, where this is not possible, connected indirectly using a ‘virtual link’ or tunnel. See Figure 10-28 on page 10-103.

The topology of each OSPF area is invisible to entities outside the area. This area partitioning system speeds up routing, because all packets with destinations within an area are contained within that area; packets destined for another area are sent to the backbone area for redirection.

The rules for area use within OSPF networks contrast with the way areas are implemented in OSI in the following ways:

• There is no requirement for a backbone area within OSI.

• The border between OSI areas is between routers (that is, a OSI router can only reside in one area), whereas the border between OSPF areas runs through a router (that is, an OSPF router may be in more than one area).

Interfacing OSPF networks with non-OSPF networksThe DCN design does not support running other IP routing protocols within the OSPF network. However, there are applications where non-OSPF is the only protocol available and these networks must be able to send to and receive packets from the OSPF network.

There are two ways in which this can be done:

1 static routes (see Figure 10-30)2 redistribution.

RedistributionRedistribution gives visibility of both networks using dynamic routing. Routes from one area to subnets in the other are costed within limitations. There is no easy way for non-OSPF to interpret OSPF metrics and vice versa.

• The boundary router advertises all OSPF routes into the non-OSPF network with a cost of one hop.

• Redistributing non-OSPF routes into the OSPF network is more complex. To a router within the OSPF network, networks in the non-OSPF network within one hop of the boundary router have the same cost as the cost of reaching the boundary router. To a router within the OSPF network, networks in the non-OSPF network beyond one hop of the boundary router have a cost equal to the number of hops required in the non-OSPF network. The cost to reach the boundary router within the OSPF area is considered to be zero. How this is implemented varies between router manufacturers.



A router (boundary router) must always be used as the interface between the two networks. There may be more than one router performing this role.

Implementing OSPF in a networkThis section covers issues that the implementer of an OSPF network needs to be aware of.

TermsSome terms associated with OSPF are:

• Costs Routes have a cost associated with them. The higher the cost the less favourable the route. OSPF has a number of metrics which are converted with algorithm into a cost.

• Policy filters This parameter only applies when an OSPF network uses external routes. An announce filter acts on the outward advertisements form the OSPF area and the accept filter acts on inward advertisements. As the LSPs are modified by the filter and the resultant used to produce a routing table, it follows that policy filters need to be applied to all routers in the OSPF network and not just to the boundary router.

• Link state is the status of a link between two routers.

• Cost of a link is computed from bandwidth, real cost, availability, reliability and other link metrics.

• OSPF area is a collection of connected routers which exchange link state updates.

• Adjacencies database lists all a router’s neighbours.

• Link State Database is a list of link states from all other routers in the OSPF area. All routers have identical link state databases.

• OSPF routing table is produced from the OSPF link state database.

• Routing table (forwarding table). The best routes are chosen from all protocol routing tables. Note that each router has a different routing table.

• Backbone area Area to which all other OSPF areas are connected, either directly or via a virtual link. It is referred to as area 0.0.0.0 or area 0.

• Standard area Area which is not the backbone area but which receives all link state updates from external networks.

• Stub areas These are areas which can have more than one interface, but by definition do not carry transit data and do not receive link state updates from external networks. All routers in a stub area must be set to be stub routers. How this is implemented varies between router manufacturers.

• Totally stubby areas Stub areas which do not receive summary LSAs.

• NSSA (Not So Stubby Areas) Stub areas which receive certain link state updates from external networks.



• Router ID This is the number by which each router is known to OSPF. On a Bay router the default is the IP address of the first configured interface. On Cisco the default is the highest configured IP address. On both routers it should be manually configured to be the same as the circuitless IP/loopback address.

• Border router A router which is in the backbone area and one or more other OSPF areas.

• Boundary router (or ASBR—Autonomous System Boundary Router) A router which is the gateway between an OSPF network and another network which uses a separate routing mechanism, including static routes.

• Designated router Link state routing protocols have an inherent problem when a number of routers exist on the same LAN. The solution is for a router to be elected as a proxy for all the routers on the LAN, this is known as a designated router (DR). The DR creates a dummy routing entity with which all routers on the LAN form an adjacency. There are no other adjacencies formed on the LAN. Thus, routers on a LAN will have only one link on the LAN, rather than one for each of the other routers on the LAN. This means that the number of links on a LAN with n routers is reduced from n * (n - 1) to n * 2:

— A router with a priority of 0 never becomes DR.

— If a router with a higher priority connects to the network there is no re-election.

— Changing router priorities does not cause a re-election.

— Changing router IDs does not cause a re-election.

• OSPF multicasts. Packets sent out with 224.0.0.5 are sent to all OSPF routers. Packets sent out with 224.0.0.6 are sent to all OSPF designated routers.

Topology considerationsAn OSPF network has to be planned out in areas to take full advantage of the protocol.

With OSPF packets destined for an area outside the current area are sent to area 0. Thus it may be inferred that all areas must have a connection to area 0. There may be more than one connection between an area and area 0 but there must be no inter-area connections.

It can be concluded that OSPF networks are tree structures which lend themselves to hierarchical addressing schemes using variable length subnet masks.

OSPF places demands upon a routing processor. It is recommended that no more than 50 OSPF routers be placed within an OSPF area.



The designated router on a LAN in a network running OSPF has a very high processor utilization. It may be that some routers are unsuitable for this role and so should be allocated a priority of 0. If it is not possible to have an area connected directly to area 0, a virtual route may be used as in Figure 10-28 (dashed line).

Figure 10-28OSPF areas

Wherever possible the DCN network should be fitted into one area (area 0). This gives the benefit of OSPF speed and versatility without the restrictions on topology.

Basic OSPF configuration steps for each interface are:

1 Enable OSPF. 2 Define an OSPF area.3 Define interface type.4 Define interface metrics.

Other parameters may need to be changed.

Advantages of OSPFOSPF is link state technology as opposed to the distance vector technology and OSPF addresses the requirements of large scalable networks. Issues addressed by OSPF are:

• Speed of convergence With OSPF convergence is quicker because routing changes are flooded throughout the network and new routing tables computed in parallel.

• Variable length subnet masks OSPF supports variable subnet masking and advertises varying levels of subnets.

Area 1

Area 3

Area4

Area 2

Area 6

virtual route

AUTONOMOUS SYSTEM (AU)

Area 0(Backbone)



• Route summarization OSPF supports route summarization which is the consolidation of multiple routes into one single advertisement. It requires a hierarchical network but has the advantage of confining topology changes to within an area and so significantly reduces the workload on routers in other areas.

Figure 10-29Route summarization

.

• Supernetting Supernetting comes from the introduction of CIDR. Address space is allocated without class as a contiguous number of class C addresses. For example, an allocation of addresses in the range 196.0.16.0 to 196.0.31.255 could be represented by 196.0.16/20. Such an entry in a routing table is referred to as a supernet. Subnetting is used to achieve route summarization and cannot be used with routing protocols such as RIP which categorize IP addresses by class.

• Network reachability There is no path limit with OSPF.

• Bandwidth considerations OSPF just sends out link state updates when they occur, with a maximum interval of 30 minutes.

• Route selection OSPF determines a best route using the concept of cost. Each interface configured with OSPF has a metric parameter, whose value has been derived from the formula 108/interface speed (however, it is at the discretion of the engineer to change it, if required—for example when the link is busy). According to the formula, some values are:

— Ethernet 100BaseTX: 1— Ethernet 10BaseT: 10— Serial at 2 Mbit/s: 48— Serial at 64 kbit/s: 1562

Area Border Router

140.100.10.0/24140.100.20.0/24140.100.30.0/24140.100.40.0/24

Route summarization

140.100.0.0/16140.150.10.0/24

Route summarization allows the right hand networks to be advertised using one update

140.150.10.0/24



Route preferenceAll routing protocols are assigned a preference which allows the router to select routes when different protocols each report a path to the same network. It could be considered as a measure of believability. The exact ranking of protocols depends on the router manufacturer, but link state routing protocols (for example, OSPF) are considered more reliable than distance vector routing protocols (for example, RIP). A static route should be assigned a high preference and a default route a low one.

Static and default routesStatic routes are manually configured on a router in contrast to routes learned via a routing protocol. Static routes are permanent and remain in the routing table even though an interface associated with the route goes down. They are most commonly used for:

• Defining routes to use when two autonomous systems must exchange routing information, rather than having entire routing tables exchanged. Often subnetworks linked to a corporate network do not wish to receive routing updates but require some facilities provided by the corporate network. The intermediate router on the border would advertise to the corporate network that it had a route to the subnetwork.

• A network which has dial-on-demand links. Routing updates passing over this link would keep the link up permanently. A static route ensures that the link is only enabled when traffic data requires the link to reach its destination.

Routers must be configured to listen to and redistribute static routes.

Default routes are a form of static routes in that they provide a catch-all for destinations not contained in routing tables. In effect they provide a static route to a large network rather than a specific IP address or subnetwork. In the case of the subnetwork attached to a corporate network, the intermediate router on the border has a default route to the corporate network advertised into the subnetwork.

Figure 10-30 shows an example of the way that static routes and default routes are used.



Figure 10-30Default and static routes

Intermediate router SubnetworkCorporate Network

default route to corporate network

static route to subnetwork

route advertisement

route advertisement

47.132.32.0/20

(0.0.0.0 mask 0.0.0.0)

(47.132.32.0 mask 255.255.240.0)

and Internet gateway


6130 Multiservice Optical Platform

Planning Guide

Copyright© 2011-2012 Ciena® Corporation. All Rights Reserved

Release 5.0 Publication: NT6Q92ME Document status: StandardDocument issue: 3 Document release date: May 2012

CONTACT CIENAFor additional information, office locations, and phone numbers, please visit the Ciena web site at www.ciena.com

Documents

Ciena OME 6130 R5.0 Planning Issue3