Volume 1 - General Information Release 1.4 Rev A

Turin Networks Inc.

Traverse SystemSONET Documentation

Release 1.4Publication Date: December 2003Document Number: 800-0101-04 Rev. A

Volume 1General Information

FCC Compliance

This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to Part 15 of the FCC Rules. This equipment generates, uses, and can radiate radio frequency energy and, if not installed and used in accordance with the installation instructions may cause harmful interference to radio communications.

Canadian Compliance

This Class B digital apparatus meets all requirements of the Canadian Interference-Causing Equipment Regulations. Cet appareil numérique de la classe B respects toutes les exigences du Règlement sur le matériel brouilleur du Canada.

International Declaration of Conformity

We, Turin Networks, Inc. declare under our sole responsibility that the Traverse platform (models: Traverse 2000, Traverse 1600, and Traverse 600) to which this declaration relates, is in conformity with the following standards:

EMC StandardsEN55022 EN55024 CISPR-22

Safety StandardsEN60950 CSA 22.2 No. 60950, ASINZS 3260IEC 60950 Third Edition. Compliant with all CB scheme member country deviations.

Following the provisions of the EMC Directive 89/336/EEC of the Council of the European Union.

Copyright © 2003 Turin Networks, Inc.

All rights reserved. This document contains proprietary and confidential information of Turin Networks, Inc., and may not be used, reproduced, or distributed except as authorized by Turin Networks. No part of this publication may be reproduced in any form or by any means or used to make any derivative work (such as translation, transformation or adaptation) without written permission from Turin Networks Inc.

Turin Networks Trademarks

Turin Networks, the Turin Networks logo, Traverse, Traverse 2000, Traverse 1600, Traverse 600, TransAccess 100, TransNav, and Creating The Broadband Edge are trademarks of Turin Networks, Inc. or its affiliates in the United States and other countries. All other trademarks, service marks, product names, or brand names mentioned in this document are the property of their respective owners.

Government UseUse, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in FAR 12.212 (Commercial Computer Software-Restricted Rights) and DFAR 227.7202 (Rights in Technical Data and Computer Software), as applicable.

VOLUME 1 GENERAL INFORMATION

ContentsVolume 1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii

Section 1 System OverviewChapter 1Introduction to the Traverse Platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1Chapter 2Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13

Section 2 Hardware DescriptionsChapter 1Traverse Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1Chapter 2General Control Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-21Chapter 3SONET/SDH Modules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-27Chapter 4VC and VT Switching Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-37Chapter 5Electrical Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-41Chapter 6Ethernet Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-49Chapter 7TransAccess 100 Mux. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-57

Section 3 Management System OverviewChapter 1TransNav Management System Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1Chapter 2Network Management Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7Chapter 3User Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13Chapter 4Management System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-17

Section 4 Planning and EngineeringChapter 1Traverse Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1Chapter 2Network Cabling using Electrical Connector Modules. . . . . . . . . . . . . . . . . . 4-17Chapter 3TransAccess 100 Mux. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-23

Section 5 AppendicesAppendix ACompliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

Release 1.4 Turin Networks Page i

Volume 1 General Information

Appendix BAcronyms and Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Index-1

Page ii Turin Networks Release 1.4

Volume 1 Description

Introduction This description contains the following documentation topics: What’s New?, page iii. Documentation Set Description, page iv. Information Mapping, page v. If You Need Help, page v. Calling for Repairs, page v.

What’s New? Volume 1, General Information includes the following enhancements with respect to the new Release 1.4 feature set.

Release Feature Volume Reference

1:2 equipment protection and3-slot DS3 Electrical Connector Module (ECM).

Section 4—Planning and Engineering, Chapter 2—“Network Cabling using Electrical Connector Modules,” ECM and Module Placement Planning Guidelines, page 4-19.

12-port DS3/EC-1/E3 module. Section 2—Hardware Descriptions, Chapter 5—“Electrical Modules,” 12-Port DS3/E3/EC-1 Clear Channel Module, page 2-43.

24-port DS3/EC-1/E3 module. Section 2—Hardware Descriptions, Chapter 5—“Electrical Modules,” 24-Port DS3/E3/EC-1 Clear Channel Module, page 2-44.

2-port GbE SX plus 16-port 10/100BaseTX module.

Section 2—Hardware Descriptions, Chapter 6—“Ethernet Modules,” GbE/Fast Ethernet Combo Modules, page 2-54.

4-port OC-12 LR2 module. Section 2—Hardware Descriptions, Chapter 3—“SONET/SDH Modules,” 4-Port OC-12/STM-4 Modules, page 2-30.

DCS3/1 test access, optical transmux.

Section 1—System Overview, Chapter 2—“Applications,” New Generation Wideband DCS, page 1-16.

Ethernet enhancements. Section 1—System Overview, Chapter 2—“Applications,” Managed Ethernet Services over SONET/SDH, page 1-18.

Front inlet fan tray (FIFT). Section 2—Hardware Descriptions, Chapter 1—“Traverse Platforms,” Fan Tray with Fan Module and Air Ramp, page 2-14.

SONET enhancements. Section 1—System Overview, Chapter 2—“Applications,” Multiservice SONET/SDH Transport, page 1-14.

Release 1.4 Turin Networks Page iii

Documentation Set Description

Documentation Set Description

The Traverse™ system documentation set is comprised of five volumes and is written to meet users’ needs as described in the table below.

The documentation set meets Telcordia™ Generic Requirements for Supplier-Provided Documentation GR–454 requirements.

Volume Description Target Audience

Volume 1, General Information

This volume provides a detailed overview of the Traverse system. It also includes engineering and planning information.

Anyone with the need to understand the Traverse system and its applications.

Volume 2, Installation and Configuration

This volume provides required equipment and tools, and step-by-step procedures for: Hardware installation. Power cabling. Network cabling. Power-up. Configuration.

Installers, Field and Network Engineers.

Volume 3, Provisioning

This volume provides provisioning concepts related to the Traverse system. Step-by-step procedures for provisioning using the TransNav Management System are provided.

Network Engineers, Provisioning and Network Operations Center (NOC) personnel.

Volume 4, Maintenance and Testing

This volume provides required equipment and tools, and step-by-step procedures for: Routine maintenance. Module replacement. Alarms and recommended actions. Troubleshooting. Performance monitoring. Loopback tests. Traverse system software upgrade.

Field and Network Engineers.

Volume 5, TransNav Management System

This volume provides an overview of the TransNav™ Management System. It also includes: Hardware requirements and third party

software requirements. Installation instructions for client/server, third

party, and management system software. Complete descriptions of management system

menus and windows along with reporting, provisioning, fault management, performance management, and system administration functions.

Command Line Interface user’s guide.

Field and Network Engineers, Provisioning, and Network Operations Center (NOC) personnel.

Page iv Turin Networks Release 1.4

Information Mapping

Information Mapping

Traverse system documentation uses Information Mapping format. Information Mapping presents information in small units or blocks. The beginning of an information block is identified by a subject label in the left margin. The end of an information block is identified by a horizontal line. Subject labels allow the reader to scan the document and find a specific subject. Its objective is to make information easy for the reader to access, use and remember.

Each procedure lists the equipment and tools, and provides step-by-step instructions required to perform each task. Graphics are integrated into the procedures whenever possible.

If You Need Help

If you need assistance while working with Traverse products, contact the Turin Networks Technical Assistance Center (TAC): Inside the U.S.: 1-866-TURINET (866-887-4638) Outside the U.S.: 707-665-4400 Online: www.turinnetworks.com/technical.htm

TAC is available 6:00AM to 6:00PM Pacific Time, Monday through Friday (business hours). When the TAC is closed, emergency service only is available on a call-back basis. E-mail support (24-hour response) is also available through at: [email protected].

Calling for Repairs

If repair is necessary, call the Turin Repair Facility at 1-866-TURINET (866-887-4638) for a Return Material Authorization (RMA) number before sending the unit.The RMA number must be prominently displayed on all equipment cartons. The Repair Facility is open from 6:00AM to 6:00PM Pacific Time, Monday through Friday.

When calling outside the United States, use the appropriate international access code, and then call 707-665-4400 to contact the Repair Facility.

When shipping equipment for repair, follow these steps:1. Pack the unit securely.2. Enclose a note describing the exact problem.3. Enclose a copy of the invoice that verifies the warranty status.4. Ship the unit PREPAID to the following address:

Turin Networks, Inc.Turin Repair FacilityAttn: RMA # ________1415 North McDowell Blvd.Petaluma, CA 94954 USA

Release 1.4 Turin Networks Page v

http://www.turinnetworks.com/technical.htm

Page vi Turin Networks Release 1.4

SECTION 1 SYSTEM OVERVIEWSECTION 1SYSTEM OVERVIEW

SECTION 1SYSTEM OVERVIEW

Contents

Chapter 1Introduction to the Traverse Platform

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1Turin Solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1Traverse Product Family . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2Traverse 2000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3Traverse 1600 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4Traverse 600 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

Remote Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5Wall Mount Cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

Traverse Capabilities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7Next Generation SONET/SDH Functionality . . . . . . . . . . . . . . . . . . . . . . 1-7Integrated Wideband DCS Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7Integrated Ethernet Switching and Transport . . . . . . . . . . . . . . . . . . . . . 1-7

Shelf and Rack Interface Densities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8Distributed Switching Architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9Carrier-Class Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9Intelligent Control Plane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10

Resource Discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10Path Calculation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11Service Signaling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11

TransAccess 100 Mux. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12

Chapter 2Applications

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13Multiservice SONET/SDH Transport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14

Integrated DWDM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15SONET to SDH translational gateway. . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15Traverse Multiservice SONET/SDH Advantages: . . . . . . . . . . . . . . . . . . 1-15

New Generation Wideband DCS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-16Key Traverse W-DCS Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-17Traverse New-Generation W-DCS Advantages: . . . . . . . . . . . . . . . . . . . 1-17

Managed Ethernet Services over SONET/SDH . . . . . . . . . . . . . . . . . . . . . . . 1-18Traverse Ethernet Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-19Virtual Concatenation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-20Link Capacity Adjustment Scheme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-20Generic Framing Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-21Traverse Ethernet over SONET/SDH Advantages . . . . . . . . . . . . . . . . . 1-21

Release 1.4 Turin Networks Page vii

Volume 1 Section 1 System Overview

List of FiguresFigure 1-1 Traverse 2000 Shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3Figure 1-2 Traverse 1600 Shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4Figure 1-3 Traverse 600 Shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5Figure 1-4 Traverse 600 Wall Mount Cabinet . . . . . . . . . . . . . . . . . . . . . . . . . 1-6Figure 1-5 TransAccess 100 Muxes Interconnected to a Traverse Shelf . . . . 1-12Figure 1-6 Multiservice SONET/SDH Transport Application. . . . . . . . . . . . . . 1-14Figure 1-7 New Generation Wideband DCS Application . . . . . . . . . . . . . . . . 1-16Figure 1-8 Integrated Ethernet Switching over SONET/SDH . . . . . . . . . . . . . 1-18Figure 1-9 Bandwidth Efficiency with Virtual Concatenation. . . . . . . . . . . . . . 1-20

List of TablesTable 1-1 Traverse Interface Options and Maximum Densities. . . . . . . . . . . 1-8

Page viii Turin Networks Release 1.4


Chapter 1Introduction to the Traverse Platform

Introduction Service providers worldwide are faced with the challenge of modernizing their transport networks to accommodate new high bandwidth IP services, such as broadband Internet access and video-on-demand, in addition to today's revenue-generating voice and leased-line services. Turin Networks flagship Traverse multiservice transport platform is a next-generation solution designed specifically to meet this challenge. Deployed in carriers' access, metro and interoffice (IOF) networks, the Traverse platform transports and manages any combination of traditional electrical TDM and optical SONET/SDH services as well as next-generation switched Ethernet services more efficiently and cost-effectively than legacy solutions.

This chapter includes the following topics: Turin Solution, page 1-1. Traverse Product Family, page 1-2. Traverse Capabilities, page 1-7. Distributed Switching Architecture, page 1-9. Carrier-Class Redundancy, page 1-9. Intelligent Control Plane, page 1-10. TransAccess 100 Mux, page 1-12.

Turin Solution The Traverse platform simplifies carriers' transport networks and lowers their costs by integrating the functions of a SONET/SDH add-drop multiplexer (ADM), a digital cross-connect system (DCS), and an Ethernet switch in a single compact shelf. The Traverse platform's design also supports a wide variety of electrical and optical service interfaces including DS1, E1, DS3/EC-1 (Clear Channel and Transmux), E3, OC-3/STM-1, OC-12/STM-4, OC-48/STM-16, OC-192/STM-64, as well as switched Fast Ethernet and Gigabit Ethernet. This flexibility lowers carriers capital and operational expenditures by reducing the need to purchase and manage multiple separate ADM, DCS, and Ethernet switching systems, as well as the rack space and power they would require.

The Traverse platform supports standard SONET/SDH features such as: comprehensive performance monitoring, the ability to aggregate and groom TDM traffic at both wideband (STS/VC) and broadband (STS/STM) granularities, and applications such as 1+1 point-to-point, linear ADM, optical hub, and protected rings.

Release 1.4 Turin Networks Page 1-1

Volume 1, Section 1: System OverviewTraverse Product Family

In addition to these standard capabilities, the Traverse platform incorporates powerful layer 2 Ethernet switching with advanced standards such as GFP, virtual concatenation and LCAS to ensure optimized transport of IP/Ethernet traffic over SONET/SDH networks. This SONET/SDH-based, packet-optimized architecture enables the Traverse platform to integrate seamlessly with carriers existing networks and protect today's investments, while laying the groundwork for future expansions into new technologies.

Traverse Product Family

Turin Networks Traverse product family is comprised of three scalable platforms optimized for deployments ranging from outside plant (OSP) cabinets and multi-tenant units (MTU) to metro and IOF environments. All three Traverse shelves, including the 20-slot Traverse 2000, the 16-slot Traverse 1600, and the 6-slot Traverse 600, are built upon the same architecture and use the same interface and control modules. Traverse 2000, page 1-3. Traverse 1600, page 1-4. Traverse 600, page 1-5.

Page 1-2 Turin Networks Release 1.4

Chapter 1 Introduction to the Traverse PlatformTraverse 2000

Traverse 2000 The Traverse 2000 platform is a multiservice transport system designed to simplify service provider’s networks and enable the delivery of SONET-based, SDH-based, and next-generation data services. The Traverse 2000 platform is: A 20-slot, 23" rack-mountable shelf (four per 7' rack). Optimized for stacked ring, metro/IOF hub switching and transport applications. Scalable to 95 Gbps of STS/STM switching capacity with industry's highest

DS1/E1 to OC-192/STM-64, 10/100 and Gigabit Ethernet service densities. High-capacity wideband digital cross-connect matrix scales from 96 to 384

protected STS/STM equivalents (2688 to 10,752 VT1.5s).

Figure 1-1 Traverse 2000 Shelf

See Section 2—Hardware Descriptions, Chapter 1—“Traverse Platforms,” Traverse 2000 System, page 2-2 for the complete description and specification for this platform.


Volume 1, Section 1: System OverviewTraverse 1600

Traverse 1600 The Traverse 1600 platform unifies the functions of a next-generation ADM and DCS with an edge Ethernet aggregation switching in a single carrier-class shelf. The Traverse 1600 is: A 16-slot, 19" rack-mountable shelf (four per 7' rack). Optimized for access and metro/IOF ring switching as well as transport

applications. Scalable to 75 Gbps STS/STM switching capacity with high-density DS1/E1 to

OC-192/STM-64, 10/100 and Gigabit Ethernet service flexibility.




Chapter 1 Introduction to the Traverse PlatformTraverse 600

Traverse 600 The Traverse 600 platform is the most a space-efficient member of the Traverse product family. The Traverse 600 is: A compact, 6-slot, 4.5 rack-unit high shelf. Environmentally hardened, and wall- or rack-mountable for deployment in access

rings, MTUs, and OSP cabinets. A flexible solution offering medium density DS1/E1 to OC-48/STM-16, 10/100

and Gigabit Ethernet services.



Remote Applications

A Traverse 600 shelf can be located in remote locations such as building equipment rooms, Controlled Environmental Vaults (CEVs), walk-in cabinets, remote central offices (CO), and multiple-dwelling unit (MDU) environments. It can be installed in standard 23-inch wide central office racks, standard 19-inch wide computer racks, and can also be wall mounted.

The Traverse 600 system is powered by a –48/–60 VDC power source in central office, remote cabinet, or CEV installations. It has front access for easy installation, cable management, and card insertion and removal.

Wall Mount Cabinet

An optional wall mount cabinet is provided for the Traverse 600 system that allows service providers to extend bandwidth to remote commercial buildings and other multiple dwelling units (MDU) and multiple tenant units (MTU). With its compact design, the secure wall mount cabinet can house one Traverse 600 system (4RU) and an


Volume 1, Section 1: System OverviewTraverse 600

integrated AC/DC power distribution/battery charger/alarm (1RU) plus 2RU for additional equipment.

Figure 1-4 Traverse 600 Wall Mount Cabinet


Chapter 1 Introduction to the Traverse PlatformTraverse Capabilities

Traverse Capabilities

The Traverse platform supports a variety of carrier-class features. The system is developed to enable solutions that service providers can implement in today’s highly competitive communications markets.

Next Generation SONET/SDH Functionality

The Traverse platform combines SONET/SDH ADM and broadband DCS functionality to create an advanced bandwidth management system that supports true “any to any” cross-connection ability. This bandwidth management flexibility enables the system to be deployed in any combination of ring and linear topologies, or provide any mix of tributary and trunk connections (DS1/E1 to OC-192/STM-64). In addition to conserving bandwidth for more efficient and cost effective network management, this architecture effectively removes the requirement for expensive external BDCSs in applications such as inter-connected rings.

For a detailed description of this application, see Chapter 2—“Applications,” Multiservice SONET/SDH Transport, page 1-14.

Integrated Wideband DCS Capabilities

The Traverse platform integrates 3/1 cross-connect functionality on the same platform that also provides SONET/SDH transport and high-density electrical service access. With this solution, Turin has created a highly-scalable and economical alternative to replacing or upgrading legacy cross-connects.

An optional, single-slot Traverse VT/VC Switch module complements the Traverse system's inherent STS/STM grooming capabilities with 5 Gbps of bidirectional non-blocking wideband switch capacity (2688 VT1.5 terminations, or 96 STS-1 equivalents). By adding additional VT/VC Switching Modules, the Traverse wideband-DCS solution can scale in increments of 5 Gbps from 96 up to a maximum of 384 fully protected STS-1 equivalents, or 10,768 x 10,768 DS1/VTs, in a single Traverse 2000 shelf.

For a detailed description of this application, see Chapter 2—“Applications,” New Generation Wideband DCS, page 1-16.

Integrated Ethernet Switching and Transport

The Traverse platform also integrates optional high-capacity Ethernet switching capabilities. The Traverse Fast Ethernet and Gigabit Ethernet modules allow service providers to efficiently and cost-effectively provide Ethernet services and transport over their existing SONET/SDH networks – without having to build a dedicated overlay network.

Leveraging GFP, VCAT and LCAS technologies to conserve transport bandwidth, the Traverse platform maps Ethernet traffic flows into dynamically provisioned SONET/SDH channels (shared or dedicated) that are “right-sized” in STS-1 or VC-3/4 increments. With its capability to aggregate and efficiently distribute Ethernet flows, the Traverse platform enables support for point-to-point, point-to-multipoint, and multipoint-to-multipoint Ethernet over SONET/SDH topologies.

For a detailed description of this application, see Chapter 2—“Applications,” Managed Ethernet Services over SONET/SDH, page 1-18.


Volume 1, Section 1: System OverviewShelf and Rack Interface Densities

00

orts per helf

12

48

96

48

84

96

32

48

/32

/ 64

/ 64

32

16

4

–

Shelf and Rack Interface Densities

Each Traverse shelf provides high maximum switching capacities and interface densities in a compact footprint to ensure optimal rack space utilization. The table below shows Traverse interface options, maximum switching capacities, and maximum interface densities per shelf.

Table 1-1 Traverse Interface Options and Maximum Densities1

Service Interface Module

Traverse 2000 Traverse 1600 Traverse 6

Modules per

ShelfPorts per

ShelfPorts per

RackModules

per Shelf

Ports per Shelf

Ports per Rack

Modules per

Shelf

P

S

Maximum switching capacity 95 Gbps 75 Gbps 15 Gbps

28-Port DS1 16 448 1792 12 336 1344 4 1

12-Port DS3/E3/EC-1 Clear Channel 16 192 768 12 144 576 4


12-Port DS3/EC-1 Transmux2 16 192 768 12 144 576 4

21-Port E13 16 336 1344 12 252 1008 4

24-Port Fast Ethernet 10/100BaseTX 16 384 1536 12 288 1152 4

8-Port Gigabit Ethernet GbE LX 18 144 576 14 112 448 4

8-Port Gigabit EthernetGbE SX 18 216 864 14 168 672 4

2-Port Gigabit Ethernet GbE LX plus 8-Port Fast Ethernet 100BaseFX Combo

18 36/144 144/576 14 28/112 112/448 4 8

2-Port Gigabit Ethernet GbE LX plus 16-Port Fast Ethernet 10/100BaseTX Combo

16 32 / 256 128/1024 12 24 / 192 96 / 768 4 8

2-Port Gigabit EthernetGbE SX plus 16-Port Fast Ethernet 10/100BaseTX Combo

16 32 / 256 128/1024 12 24 / 192 96 / 768 4 8

8-Port OC-3/STM-1 18 144 576 14 112 448 4

4-Port OC-12/STM-4 18 72 288 14 56 224 4

1-Port OC-48/STM-16 18 18 72 14 14 56 4

1-Port OC-192/STM-64 (dual slot) 9 9 36 7 7 28 –

1 Unprotected densities.

2 A SONET-only module.

3 An SDH-only module.


Chapter 1 Introduction to the Traverse PlatformCarrier-Class Redundancy

Distributed Switching Architecture

The Traverse platform implements a patent-pending distributed switching architecture that delivers flexibility and true “pay as you grow” system scalability. Within this framework, each individual Traverse module incorporates a powerful switching ASIC (application specific integrated circuit) that participates as a member of the distributed switch fabric across the Traverse platform's fully interconnected passive mesh backplane. This distributed switching technique allows non-blocking increases in system capacity from 2.5 Gbps up to 95 Gbps per (Traverse 2000) shelf. In addition, the flexible nature of this architecture is designed to handle any combination of TDM, cell and packet transmissions with equal facility, and supports any service interface module type (e.g. optical or electrical, trunk or tributary, packet-based or TDM-based) in any system slot.

The Traverse distributed switching ASIC performs both time slot assignment (TSA) and time slot interchange (TSI) functionality at the STS/STM level on all modules. That is, each Traverse line card can pass through, add, drop, or drop-and-continue (broadcast) traffic, including hairpinned connections.

The distributed switching architecture lowers startup costs for the Traverse platform because no centralized switch-fabric is required for the system. In addition, it allows carriers to increase the capacity of their Traverse shelf in an incremental “pay as you grow” manner by adding service modules. Customers pay only for the services and capacity that they require.

Carrier-Class Redundancy

The Traverse platform is engineered to meet the 99.999% availability levels required for carrier-grade deployments. Redundancy and fault-tolerance are built into all system functions to provide a robust and reliable service delivery platform. As a fully ANSI and ETSI capable system, the Traverse platform is both NEBS Level 3 and CE Mark compliant.

The Traverse platform supports a variety of facility and equipment protection schemes: All optical service interface modules (SIM) support 1+1 APS, 1+1 Path, UPSR and

SNCP. The OC-48/STM-16 and OC-192/STM-64 modules also support 2-fiber BLSRs

and MS-SP rings. All electrical modules, including the DS1, E1, DS3/EC-1 and E3 support optional

1:1 or 1:2 equipment protection. The Traverse General Control Modules (GCM) and VT/VC Switching Modules

support 1:1 equipment protection.

All system components including SIMs, GCMs, and the electrical connector modules (ECMs) are hot-swappable and easily accessible. Additionally, both hardware and software upgrades can be performed “in-service” on the Traverse platform, without interruption to existing network traffic. This capability allows the transport network to expand gracefully as new customers and service requirements are added.


Volume 1, Section 1: System OverviewIntelligent Control Plane

Intelligent Control Plane

The Intelligent Control Plane optimizes bandwidth utilization, enables traffic engineering, and provides system management. It is extensible to support multiple technologies, including wavelength, SONET/SDH, virtual tributaries, Ethernet, ATM, MPLS, IP, and all related networking services.

The Intelligent Control Plane is a logical set of connections among Traverse nodes that allows the nodes to exchange control and management information. The set of Traverse nodes that are completely interconnected by the Intelligent Control Plane is called a domain. It performs the following functions across the Traverse Services Network: Resource Discovery: Learns the set of network elements, the available interfaces,

and the topology of links between those interfaces. Path Calculation: For a particular service, calculates a path across the network

that makes efficient use of the network elements and links. Service Signaling: Configures each network element in the path with all the

parameters needed to turn up the service. Policy enforcement: Guides the automatic behavior of the control plane.

The Intelligent Control Plane implements Generalized MPLS signaling methods used to establish transport connectivity in the Traverse Services Network. It automatically discovers neighboring nodes and interconnected links, using Open Shortest Path First (OSPF) with Traffic Engineering (TE) extensions routing protocol.

Resource Discovery

After each Traverse node initializes, it negotiates link properties with the network element at the other end of each link. This includes properties such as data formats and error monitoring. After successfully completing the negotiation, each Traverse node is able to communicate fully with its neighbors.

Next, the topology discovery protocol starts up. This protocol is simple in concept. First it learns what network elements are directly connected to its links. For instance, Traverse node A learns that Traverse node B is its neighbor. Next, it exchanges all the information it has learned with its neighbors, e.g., Traverse node A knows that Traverse node C is two hops away. At the completion of these steps every node has learned the entire network topology. In practice, in a large network, several rounds of messages are exchanged before each Traverse node understands the complete topology. This process completes rapidly and automatically.

The topology discovery protocol (OSPF-TE) also distributes information about resource usage at each Traverse node. This information populates the traffic- engineering database that maintains a record of resource utilization and performance at each node in the network. The discovery protocol runs continuously and updates the traffic-engineering database in real time.

Using the link-state database and the traffic engineering database, the Intelligent Control Plane can find the best path to set up a circuit across the Traverse Services Network. At this point, without any human intervention, every Traverse node participating in the Intelligent Control Plane has complete knowledge of the network. The network is now ready to accept service requests.


Chapter 1 Introduction to the Traverse PlatformIntelligent Control Plane

Path Calculation

A service request is initiated by the Traverse management software sending a request to a single Traverse node—typically one of the end points of the desired service. That Traverse node searches its traffic engineering database to find the “best” path between the service end points. “Best” is defined as the path that minimizes some measure such as number of links or network delay, while also satisfying constraints and policies specified by the user.

The constraints provide a way for human guidance and control of the path selection without requiring manual selection. Typical constraints include: Avoid specific nodes and links. This is used most often to achieve

failure-independent paths. Nodes and links that share some risk (such as fibers in the same conduit, or central offices in the same earthquake zone) are collected into groups. Paths can be requested that draw their resources from different groups.

Include specific nodes. A special case is to fully specify every node in the path. This can be used in cases where manual path calculation is desired.

Meet certain delay or jitter properties. Utilize special topologies such as SONET/SDH rings.

Service Signaling

Once a path has been selected, RSVP-TE1 signaling protocols are used to set up each Traverse node in the path. At each node, resource management is performed to ensure that setting up the service will allow the new service and all existing ones to meet their quality of service obligations. The path calculation takes this into account, although the traffic engineering database may be a few seconds behind the actual network utilization. Each Traverse node along the path does a final check and reserves the resources for the service. If any Traverse node cannot fulfill the service requirements, an error is generated, and all the reserved resources at other Traverse nodes in the path are released. At this point, path calculation is repeated with updated information.

Once service signaling is complete, the service can be made available to the end user. The entire process takes a matter of seconds—real-time service creation that allows service requests to begin generating revenue immediately.

The work of the Intelligent Control Plane does not stop once the service has been created—it is continually updating its traffic engineering database to deal with failures and changing network load.

1 Resource ReSerVation Protocol with Traffic Engineering extensions.


Volume 1, Section 1: System OverviewTransAccess 100 Mux

TransAccess 100 Mux

Turin Networks offers the TransAccess 100 STS-1/T1 Mux as a complement to the Traverse in-chassis DS1 module. The TransAccess 100 Mux is ideally suited for high-density DS1 deployments. The unit is a 1:1 protected STS-1 multiplexer that provides a cost-effective solution for delivering T1 services off high-capacity SONET fiber rings. The TransAccess 100 Mux is a self-contained multiplexer capable of asynchronously mapping 28 DS1 signals into 28 Virtual Tributary (VT1.5) signals and then into a VT structured STS-1 Synchronous Payload Envelope (SPE).

The TransAccess 100 Mux is just one rack unit (1.75-inch) in height, which facilitates space consideration as service providers build out their networks. The TransAccess 100 Mux’s complete circuit redundancy ensures that there is always a one-for-one backup channel if any circuit failure occurs.

Its true plug-and-play architecture reduces the time, cost, and complexity of installation and configuration. TransAccess 100 Mux modules are hot-swappable and can be replaced in minutes, without interrupting service.

Each Traverse 12-port DS3/EC-1 Clear Channel service interface module can support up to twelve TransAccess 100 Muxs. Using six redundant DS3/EC-1 Clear Channel modules, a single Traverse node can support up to seventy-two TransAccess 100 Muxs. Each TransAccess 100 Mux unit has an Ethernet port for control and management communication. As shown in Figure 1-5, the Ethernet port for each TransAccess 100 Mux is connected to an Ethernet hub. The Ethernet hub has a designated uplink Ethernet port to the Traverse General Control Module via the DCN Ethernet interface on the backplane of the Traverse shelf.

Figure 1-5 TransAccess 100 Muxes Interconnected to a Traverse Shelf

The TransNav Management System lets you remotely manage the configuration and status of the TransAccess 100 Mux.

Traverse Shelf

DS

3/E

C1

CC

DS

3/E

C1

CC

GC

M

GC

M

Ethernet Hub

TransAccess 100

TransAccess 100

TransAccess 100

10/100BaseT

10/100BaseT

Support for up to 12TransAccess 100 Muxes

28 DS1

28 DS1

28 DS1

(connected to DCNEthernet interface onthe Traversebackplane)



Chapter 2Applications

Introduction The Traverse platform supports a variety of carrier-class applications. The system is developed to enable solutions that service providers can implement in today’s highly competitive communications markets.

This chapter describes the following applications: Multiservice SONET/SDH Transport, page 1-14. New Generation Wideband DCS, page 1-16. Managed Ethernet Services over SONET/SDH, page 1-18.


Volume 1, Section 1: System OverviewMultiservice SONET/SDH Transport

Multiservice SONET/SDH Transport

SONET and SDH are high-speed optical communications protocols that represent the foundation of today’s global optical transport network. As a principal application, the Traverse platform provides multiservice SONET/SDH transport capabilities that serve the dual roles of an Add-Drop Multiplexer (ADM) and a digital cross-connect system (DCS). In multiservice SONET/SDH transport applications, the Traverse platform aggregates any combination of lower rate signals, grooming and switching them into higher-rate optical signals, or dropping them to be transported on different facilities

Figure 1-6 Multiservice SONET/SDH Transport Application

The Traverse platform is deployable throughout service providers transport networks such as in central offices, POPs, or remote terminals. In these carrier facilities, the Traverse system transports any combination of wideband or broadband services, circuit-based or packet-based voice, data, and video services and interconnects SONET/SDH rings all from a common platform.

Ideal for service providers looking to expand the capacity of their transport networks and evolve to support high-bandwidth IP services such as video, the Traverse platform offers significant advantages over traditional SONET/SDH solutions. In addition to supporting standard protected rings, hub, point-to-point, and linear add/drop deployments, the system’s advanced bandwidth management capability supports both


Chapter 2 ApplicationsMultiservice SONET/SDH Transport

uni- and bi-directional connections, drop-and-continue for dual-node ring interconnection, broadcast, and protected mesh topologies.

Integrated DWDM

Dense wavelength division multiplexing (DWDM) allows multiple streams of data, each using a separate wavelength, to travel along the same fiber at the same time. DWDM multiplies the capacity of a fiber by the number of wavelengths present, allowing service providers to increase the available bandwidth in their networks without incurring the expense of adding fiber. The Traverse platform offers integrated DWDM capabilities, with OC-48/STM-16 and OC-192/STM-64 wavelengths based on the ITU grid, at spacings of 100 GHz.

SONET to SDH Translational Gateway

The Traverse platform supports both North American and International interfaces (DS1 up to OC-192, and E1 up to STM-64) making it ideally suited for deployment as a translational gateway. The Traverse can manage global trunks by translating between a variety of standard ANSI and ETSI signal formats (Asynchronous/SONET and PDH/SDH) and transmitting them between different continents and/or countries. In addition, all Traverse interface modules, with the exception of DS1 and E1,can support either ANSI and ETSI operation by configuring the operating mode through software. This simplifies module ordering and sparing, as well as network operations and maintenance, further lowering costs for global carriers.

Traverse Multiservice SONET/SDH Advantages:

The Traverse product family addresses a wide range of applications across service provider’s access, metro and IOF networks

Support for broad range of electrical and optical ANSI and ETSI interfaces: DS1, DS3/EC-1, E1, E3, OC-3/STM-1, OC-12/STM-4, OC-48/STM-16, OC-192/STM-64, 10/100 and GbE with industry leading port densities

Advanced bandwidth management capabilities enable any combination of linear, ring and inter-connected ring topologies

The high-capacity Traverse architecture scales to an add-drop capacity of 95 Gbps (1824 x 1824 STS-1/STM cross-connect matrix)

Automated end to end service provisioning using Turin’s TransNav™ Management System


Volume 1, Section 1: System OverviewNew Generation Wideband DCS

New Generation Wideband DCS

Wideband Digital Cross-Connect Systems (W-DCS) perform a critical bandwidth management function in carriers' SONET/SDH-based transport networks. These systems switch and groom traffic at the DS1/E1 level for efficient hand-off to the IOF network or for distribution back to the access network. However, with the continued growth in voice and private line services, scaling traditional W-DCSs (typically large, power hungry systems that are difficult to manage) becomes increasingly inefficient from both a capital and operational cost perspective.

Turin Networks helps solve these problems with the option to integrate new generation W-DCS capabilities seamlessly into the Traverse platform. Turin's solution integrates 3/1 cross-connect functionality on the same platform that also provides SONET/SDH transport and high-density electrical service access. With this solution, Turin has created a highly-scalable and economical alternative to replacing or upgrading legacy cross-connects.

Figure 1-7 New Generation Wideband DCS Application

Carriers can deploy the Traverse W-DCS system in end-offices or in hub locations. Here, the Traverse system manages bandwidth by switching and grooming at the VT and VC level between the access network and equipment such as Class 5 switches, ATM switches, and routers. This solution relieves congestion by grooming traffic closer to the edge for more efficient transport to the network core, or for distribution


Chapter 2 ApplicationsNew Generation Wideband DCS

back to the access network. In addition to the cost savings realized by providing better utilization of available transport bandwidth, this relieves the strain on legacy cross-connects and reduces the need to purchase additional ports on legacy W-DCSs.

Key Traverse W-DCS Features

Integrated test access and the transmux capabilities make the Traverse platform a full-featured, extremely economical option for replacing traditional cross-connects. In fact, one Traverse shelf can replace multiple racks of legacy equipment, producing savings in equipment, space, power, and maintenance. Integrated Test Access. Development with the Spirent® Network Tester provides

the Traverse platform with integrated test access functionality, enabling carriers to test and monitor any DS1 or DS3 circuit provisioned on the Traverse switch fabric.

DS3 Transmux. DS3>DS1>VT1.5 transmultiplexing functionality is provided by the Traverse DS3/EC-1 Transmux SIM. This capability is important in applications where incoming traffic is channelized DS3s and the payload of the outgoing circuit needs to be VT-mapped, such as those that are handed off to the Traverse VT1.5 switch fabric.

Optical Transmux. The Transmux component also transparently provides this transmux capability when traffic ingresses and egresses the Traverse system using an optical interface. In this case, the Transmux component receives incoming DS1-mapped STS-1s from the Traverse backplane and converts the outgoing signal to a VT1.5 mapped STS-1.

Traverse New-Generation W-DCS Advantages:

In addition to the key features, the Traverse platform offers the following advantages: Adding optional W-DCS capabilities to the Traverse system creates an advanced

bandwidth management system that supports true “any to any” cross-connection ability.

One system performs integrated switching, grooming, transport, and restoration functions to lower costs and optimize network operations

The W-DCS switching matrix can be scaled in-service from 96 to 384 fully protected STS-1 equivalents (10,752 VTs) in a single Traverse 2000 shelf.

Supports 1:1 and 1:N equipment protection, as well as 1+1 APS/MSP, 1+1 path protection, UPSR/SNCP and BLSR/MS-SP Rings.

Automated end to end service provisioning using Turin’s TransNav™ Management System.


Volume 1, Section 1: System OverviewManaged Ethernet Services over SONET/SDH

Managed Ethernet Services over SONET/SDH

As service providers migrate to a more data-oriented service mix, Ethernet technology is increasingly being deployed as a native connectivity service for ultra-broadband (business-based) Internet access and Transparent LANs. Ethernet is also deployed as a traffic aggregation and high-speed inter-connection technology in the latest generation of packet-based access equipment such as IP-DSLAMs, IP-DLCs, E-PON systems and CMTSs.

To support this growing requirement, Turin Networks integrates high-capacity Ethernet switching capabilities into its Traverse multiservice transport platform. The Traverse Fast Ethernet and Gigabit Ethernet modules allow service providers to efficiently and cost-effectively provide Ethernet services and transport over their existing SONET/SDH networks – without having to build a dedicated overlay network.

Figure 1-8 Integrated Ethernet Switching over SONET/SDH

The Traverse platform has optional integrated Ethernet switching capabilities to enable the aggregation and transport of traffic from IP-based access equipment (such as: IP-DSLAMs or CMTS), or fully managed Ethernet services over service providers’ existing SONET/SDH infrastructure. The combination of SONET/SDH transport and Ethernet service management features in a single integrated platform increases service providers’ revenues and lowers their costs by eliminating the need to build a dedicated


Chapter 2 ApplicationsManaged Ethernet Services over SONET/SDH

Ethernet overlay network. Ethernet services can be deployed incrementally (co-existing with other services such as voice and private lines) minimizing disruptions to current operational procedures.

The Traverse platform’s combined support for high-capacity L2 switching, VCAT, LCAS and GFP standards provide new levels of bandwidth efficiency, and allow delivery of multiple Ethernet service types – in their native mode – over the existing SONET/SDH network.

The Traverse Fast Ethernet and Gigabit Ethernet Switching Modules natively switch and aggregate layer 2 Ethernet flows for reliable, bandwidth-optimized transport over the SONET/SDH optical network. Extensive features are provided for Ethernet bandwidth management and traffic shaping. Flows can be shaped, classified and prioritized on a per-VLAN, per port or per subscriber basis to provide service level agreements (SLAs) with guaranteed maximum and/or minimum delivery rates.

Traverse Ethernet Options

The Traverse platform provides a full suite of Ethernet interface options including an 8-port Gigabit Ethernet (SX or LX) module, a 24-port Fast Ethernet (TX) module, an Ethernet combo module with two Gigabit Ethernet (LX) ports and eight Fast Ethernet (FX) ports. A second Ethernet combo module has two Gigabit Ethernet (LX) ports and 16 Fast Ethernet (TX) ports. The high-density Traverse Ethernet design enables up to 1,344 Fast Ethernet ports or 576 Gigabit Ethernet ports per 7’ rack. In addition, all Ethernet modules can be deployed in any of the Traverse shelves (Traverse 2000, Traverse 1600, and Traverse 600) – simplifying module sparing and ordering.

The Traverse Ethernet modules support advanced traffic management capabilities such as Ethernet rate shaping in 1 Mbps increments and IEEE 802.1Q/p VLAN prioritization. With these capabilities, service providers can realize the revenue benefits of over-subscription by offering and charging for sub-rate services with differentiated levels of QoS. Traffic can be shaped, classified, and prioritized for each VLAN, port, or subscriber to provide service level agreements (SLAs) with guaranteed maximum and/or minimum delivery rates. Extensive queuing mechanisms ensure that SLAs are properly enforced. In addition, powerful Layer 2 switching and statistical multiplexing capabilities efficiently aggregate lower-speed Ethernet traffic flows into shared SONET/SDH channels to conserve bandwidth. With its capability to aggregate and distribute Ethernet flows, the Traverse platform supports point-to-point, point-to-multipoint, and multipoint-to-multipoint topologies, which is not the case with legacy SONET/SDH equipment.

The Traverse platform is also one of the first in the industry to implement several key Ethernet over SONET/SDH standards that significantly improve transport bandwidth conservation and utilization: Virtual Concatenation, page 1-20. Link Capacity Adjustment Scheme, page 1-20. Generic Framing Procedure, page 1-21.

Leveraging GFP, VCAT and LCAS technologies to conserve transport bandwidth, the Traverse platform maps Ethernet traffic flows into dynamically provisioned SONET/SDH channels (shared or dedicated) that are “right-sized” in STS-1 or VC-3/4 increments. With its capability to aggregate and efficiently distribute Ethernet flows,



the Traverse platform enables support for point-to-point, point-to-multipoint, and multipoint-to-multipoint Ethernet over SONET/SDH topologies.

Virtual Concatenation

Virtual Concatenation (VCAT) is an inverse multiplexing technique based on ITU-T G.707/Y.1322 and G.783 standards, that supports the bundling of multiple independent lower-rate channels into a higher rate channel. VCAT enables efficient mapping of Ethernet frames directly into a payload of separate STS-1/VC-3 or STS-3c/STS-3c path signals, known as a virtual concatenation group (VCG). This much improved mapping technique eliminates the rigid hierarchies of the common SONET/SDH containers and enables service providers to provision and transport data services more efficiently.

Figure 1-9 Bandwidth Efficiency with Virtual Concatenation

In this example, legacy contiguous concatenation, the transport efficiency is low. With virtual concatenation, an OC-48/STM-16 link can actually carry two full Gigabit Ethernet links and still have six STS-1/VC-3s available to carry other traffic.

Virtual concatenation also enables the re-use of protection bandwidth by allowing both a working path and its protection path in a group. Virtual concatenation provides a logical mesh of multiple, right-sized transport channels over an existing SONET/SDH transport network. These channels are independent of any higher layer schemes for equal cost multi-path routing or load balancing.

Link Capacity Adjustment Scheme

Link Capacity Adjustment Scheme (LCAS) is a method of dynamically provisioning and reconfiguring SONET/SDH channels to suit customer needs or carrier bandwidth management requirements, based on ITU-T G.7042/Y.1305 standards. LCAS extends the benefits of virtual concatenation by providing a control mechanism that supports the hitless adjustment, or resizing, of these virtually concatenated channels. LCAS also provides a means of removing member links within a VCG that have experienced failure, adding a new level of resiliency to Ethernet over SONET/SDH solutions.

GbE GbE GbE

OC-48/STM-16without virtual concatenation

OC-48/STM-16with virtual concatenation

40% transport efficiency1 x STS-48c/VC-4-16c

92% transport efficiency2 x STS-3c-12v/VC-3-12v

and6 x STS-1/VC-3 channels


Chapter 2 ApplicationsManaged Ethernet Services over SONET/SDH

The dynamic nature of LCAS adds two key values to a SONET/SDH network: dynamic protection management and dynamic bandwidth management. In failure scenarios, LCAS allows members of a VCG to continue to carry traffic. Throughput of a given connection decreases, but the connection remains live. For example, during failures in IP networks, IP routers are able to maintain network topologies even though throughput along various links has decreased. IP routing protocols avoid having to re-converge after a failure while supporting more flexible billing options for operators offering connectivity services.

From an Ethernet services perspective, LCAS provides in-service adjustments of bandwidth associated with a particular customer and flexible protection options for Ethernet over SONET/SDH services. That is, one STS-1/VC-3 allocated to a Gigabit Ethernet service as a back up link.

Generic Framing Procedure

Generic Framing Procedure (GFP) is a universal traffic adaptation protocol, based on ITU-T G.7041 (2001) & ANSI T1.105.02 (2002) standards, for the mapping of all broadband transport—be it Ethernet, IP, Fibre Channel, or other block-coded or packet-oriented data streams—into SONET/SDH or the optical transport network (OTN). GFP offers significant improvements over previous data over SONET/SDH mapping solutions such as packet-over-SONET/SDH, ATM, X.86 or other proprietary mechanisms. The advantage is in its encapsulation framework, which was designed to support either fixed or variable length frame structures.

With GFP, both variable length frames (PDU-oriented) and block-code oriented signals can be accommodated, so data services can be transported in a mode that matches their unique requirements. Unlike HDLC-based protocols, GFP does not rely on special characters or flags for frame delineation. Instead, it uses a modification of the HEC-based delineation technique used in ATM, placing an explicit payload length indicator in the GFP frame header. With this technique, GFP can fix the PDU size to constant value in order to support constant-bit-rate traffic, or it can be changed from frame to frame to support full encapsulation of the variable length user PDU. This eliminates any requirements for segmentation and reassembly or frame padding to fill unused payload space, making chip design much simpler and lower cost.

Traverse Ethernet over SONET/SDH Advantages

SONET/SDH and Ethernet functionality are combined in a single platform to lowers costs, simplify the network, and enable a more seamless migration

The high density Traverse 2000 system supports up to 144 GbE interfaces in a single shelf/chassis (576 per rack), or up to 384 Fast Ethernet interfaces per shelf (1,536 per rack)

Ethernet traffic can be shaped, classified and prioritized to support guaranteed SLAs and differentiated levels of service

GFP, VCAT and LCAS technologies combine to provide highly bandwidth-efficient Ethernet over SONET/SDH transport




SECTION 2 HARDWARE DESCRIPTIONSSECTION 2HARDWARE DESCRIPTIONS

Contents

Chapter 1Traverse Platforms

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1Traverse 2000 System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

Traverse 2000 Front View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2Traverse 2000 Rear View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3Traverse 2000 Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5

Traverse 1600 System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6Traverse 1600 Front View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6Traverse 1600 Rear View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7Traverse 1600 Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9

Traverse 600 System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10Traverse 600 Front View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10Traverse 600 Rear View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10Traverse 600 Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12

Interface Options and Densities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14Fan Tray with Fan Module and Air Ramp . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15Power Distribution and Alarm Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16Traverse Dimensions Summary Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-18Traverse Operating System Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-18

Distributed Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19Upgrades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19General Control Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19Dependability. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-20

Chapter 2General Control Modules

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-21General Control Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22Physical Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-23Timing Subsystem. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-23Alarm Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-24Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-24

Chapter 3SONET/SDH Modules

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-278-Port OC-3/STM-1 Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-28

Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-28


Volume 1 Section 2 Hardware Descriptions

4-Port OC-12/STM-4 Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-30Specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-30

1-Port OC-48/STM-16 Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-32Specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-32

1-Port OC-192/STM-64 Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-34Specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-34

Chapter 4VC and VT Switching Modules

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-37VCX Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-38

Specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-38VT/VC Switch Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-39

Specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-39

Chapter 5Electrical Modules

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4128-Port DS1 XT Module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-42

Specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4212-Port DS3/E3/EC-1 Clear Channel Module . . . . . . . . . . . . . . . . . . . . . . . . . 2-43

Specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4324-Port DS3/E3/EC-1 Clear Channel Module . . . . . . . . . . . . . . . . . . . . . . . . . 2-44

Specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4412-Port DS3/EC-1 Transmux Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-45

Specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4521-Port E1 Module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-46

Specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-46

Chapter 6Ethernet Modules

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-498-Port Gigabit Ethernet Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-50

Specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5024-Port Fast Ethernet Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-52

Specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-52GbE/Fast Ethernet Combo Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-54

Specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-54

Chapter 7TransAccess 100 Mux

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-57TransAccess 100 STS-1/T1 Mux Description . . . . . . . . . . . . . . . . . . . . . . . . . 2-57TransAccess 100 Mux Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-58DS1 Electrical Signal Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-58STS-1 Electrical Signal Specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-59Craft Port Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-59



TransAccess 100 Mux Compliance Standards . . . . . . . . . . . . . . . . . . . . . . . . 2-60

List of FiguresFigure 2-1 Front View of Traverse 2000. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2Figure 2-2 Rear View of Traverse 2000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3Figure 2-3 Front View of Traverse 1600. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6Figure 2-4 Rear View of Traverse 1600 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7Figure 2-5 Front View of Traverse 600. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10Figure 2-6 Rear View of Traverse 600 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10Figure 2-7 Front View Traverse 1600 Fan Tray . . . . . . . . . . . . . . . . . . . . . . . 2-15Figure 2-8 PDAP-2S Front View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16Figure 2-9 PDAP-2S Rear View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17Figure 2-10 PDAP-4S Front View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17Figure 2-11 PDAP-4S Rear View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17Figure 2-12 TransAccess 100 Mux. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-57

List of TablesTable 2-1 Traverse 2000 Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5Table 2-2 Traverse 1600 Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9Table 2-3 Traverse 600 Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12Table 2-4 Traverse Interface Options and Maximum Densities . . . . . . . . . . 2-14Table 2-5 Fan Tray and Fan Module Specifications . . . . . . . . . . . . . . . . . . . 2-15Table 2-6 Traverse Component Dimensions. . . . . . . . . . . . . . . . . . . . . . . . . 2-18Table 2-7 GCM Specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-24Table 2-8 OC-3/STM-1 IR1 Module Specifications . . . . . . . . . . . . . . . . . . . . 2-28Table 2-9 OC-12/STM-4 Interface Specifications . . . . . . . . . . . . . . . . . . . . . 2-30Table 2-10 OC-48/STM-16 Interface Specifications . . . . . . . . . . . . . . . . . . . . 2-32Table 2-11 OC-192/STM-64 Module Specifications . . . . . . . . . . . . . . . . . . . . 2-34Table 2-12 VCX Component Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . 2-38Table 2-13 VT Switch Module Specifications . . . . . . . . . . . . . . . . . . . . . . . . . 2-39Table 2-14 28-port DS1 Module Specifications. . . . . . . . . . . . . . . . . . . . . . . . 2-42Table 2-15 12-port DS3/E3/EC-1 Clear Channel Module Specifications . . . . 2-43Table 2-16 12-port DS3/E3/EC-1 Clear Channel Module Specifications . . . . 2-44Table 2-17 12-port DS3/EC-1 Transmux Module Specifications. . . . . . . . . . . 2-45Table 2-18 21-port E1 Module Specifications . . . . . . . . . . . . . . . . . . . . . . . . . 2-46Table 2-19 GbE Interface Specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-50Table 2-20 Fast Ethernet (10/100 TX) Interface Specifications . . . . . . . . . . . 2-52Table 2-21 Power Consumption for Ethernet Combo Modules. . . . . . . . . . . . 2-54Table 2-22 Fast Ethernet FX Interface Specifications. . . . . . . . . . . . . . . . . . . 2-54Table 2-23 TransAccess 100 Mux Specifications . . . . . . . . . . . . . . . . . . . . . . 2-58Table 2-24 DS1 Electrical Signal Specifications . . . . . . . . . . . . . . . . . . . . . . . 2-58Table 2-25 STS-1 Electrical Signal Specifications . . . . . . . . . . . . . . . . . . . . . 2-59Table 2-26 Craft Port Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-59

Release 1.4 Turin Networks Page iii


Page iv Turin Networks Release 1.4

SECTION 2HARDWARE DESCRIPTIONS

Chapter 1Traverse Platforms

Introduction Turin Networks offers a family of modular platforms. These systems consist of a shelf with common control modules and separate service interface modules required by the customer.

Included in this chapter is information about the following Traverse components: Traverse 2000 System, page 2-2. Traverse 1600 System, page 2-6. Traverse 600 System, page 2-10. Interface Options and Densities, page 2-13. Fan Tray with Fan Module and Air Ramp, page 2-14. Power Distribution and Alarm Panel, page 2-15. Traverse Dimensions Summary Table, page 2-17. Traverse Operating System Software, page 2-17.


Volume 1, Section 2: Hardware DescriptionsTraverse 2000 System

Traverse 2000 System

The Traverse 2000 platform is a 20-slot, 23-inch, rack-mountable shelf. Optimized for stacked ring, metro/IOF hub switching and transport applications, it is also scalable to 95 Gbps of STS/STM switching capacity with industry's highest DS1/E1 to OC-192/STM-64, 10/100 and Gigabit Ethernet service densities. This platform also offers a high-capacity wideband digital cross-connect matrix scales from 96 to 384 protected STS/STM equivalents (2688 to 10,752 VT1.5s).

This section has information on the following topics: Traverse 2000 Front View, page 2-2. Traverse 2000 Rear View, page 2-3. Traverse 2000 Specifications, page 2-5.

Traverse 2000 Front View

Eighteen slots accommodate service interface modules and VT/VC switch modules, and two slots are dedicated to General Control Modules. The Traverse 2000 shelf is configured by populating the system with general control modules (GCM), service interface modules (SIM), and VT/VC switch modules. Module guide rails are built into the shelf to allow for easy insertion of the modules into connectors mounted on the backplane

Figure 2-1 Front View of Traverse 2000

P1 P1

GCM OnlySlots 19 and 20

Slots 1–16: Any Service Interface or VT/VC Switch ModuleSlots 1–18: Any Optical or VT/VC Switch Module


Chapter 1 Traverse PlatformsTraverse 2000 System

Slot N

SystemInterfa

EnviroAlarms

Timing

RS-23

EthernConne

EnviroAlarms

MPX C

SystemInterfa

Traverse 2000 Rear View

The Traverse system’s fully-meshed passive backplane provides full interconnection for modules and external interfaces such as power, timing, alarm, management, and the fan tray module. All power and interface connections are terminated from the rear of the Traverse shelf, except for the serial interface and the Ethernet port (for local craft access), which are on the front faceplate of the GCM.

Figure 2-2 Rear View of Traverse 2000

Slot Numbers. There are 20 slots in each Traverse 2000 shelf: Slots 19 and 20 are reserved for General Control Modules (GCMs). Slots 1–16 slots are for any service interface or VC/VT switch module. Slots 1–18 slots are for any optical interface or VC/VT switch module.

MPX Connectors. Each slot has receptacles for up to two MPX ribbon fiber connectors. Each connector supports from 1 to 12 fiber pairs, for a maximum fiber count of 48 per slot.

Timing Interface. The backplane provides primary and secondary T1/E1 and CC2M (Composite Clock and 2MHz) input and output1 timing interfaces, and primary and

Electrical Connector Module (ECM)

umbers

Alarms ces

nmental Interfaces

Interface

2 for Modem

etction to DCN

nmental Module

onnectors

Power Terminals

Alarms ces


Connectors for ECM

Slots 1–16: Any Service Interface or VT/VC Switch ModuleSlots 1–18: Any Optical or VT/VC Switch Module

1 Composite clock output connections are unused.



secondary BITS input timing interfaces. These timing interfaces are routed to both GCMs which distribute system timing references to all modules.

System and Environmental Alarms Interface. Support is provided for the full set of system alarm outputs, sixteen environmental alarm inputs, eight environmental control outputs, and fail-safe alarm and remote alarm cut-off. The environmental telemetry inputs and outputs are supported by the optional Environmental Alarm Module located on the main backplane, which provides additional system-management functions to accommodate customer-defined alarm input/output requirements. The module is field replaceable and can be replaced without disconnecting the alarm wiring.

Modem Interface. The RS-232C modem interface uses a vertical 8-pin RJ-45 connector that is configured as a data terminal equipment (DTE) port for connection to an external modem, supporting dial-up remote access to the active GCM. Dial-up access can also be achieved by installing a terminal server on the DCN and communicating via Telnet to any other Traverse node on the network. A local VT-100 terminal (or a PC with VT-100 terminal emulation software) can also be connected to the RS-232C connector (Backplane interface).

Ethernet Connection to Data Communications Network. Traverse systems has a 10/100Base T Ethernet interface that can be used to connect a Traverse node to the TransNav system (or to another EMS) and to other remote management devices. The RJ-45 signal connections are bridged to both the primary and secondary GCMs. This enables the TransNav Management System to always talk to the active GCM, even after a protection switching.

A network of Traverse nodes can be managed over the service providers data communications network (DCN) as long as at least one Traverse node is directly connected to that network through the Traverse DCN Ethernet interface. Traverse nodes that have no direct connection to a DCN can communicate with the EMS indirectly, through any Traverse node that is connected to the DCN.

A Traverse node that is not directly connected to a DCN is able to learn a route to Traverse nodes on the DCN without any explicit local provisioning of routing information as long as it is connected via the Turin Control Plane to one or more gateway Traverse nodes. Service providers must use static IP routes to enable devices on the DCN to reach both gateway and non-gateway Traverse nodes.

Power Terminals. The Traverse receives redundant –48 VDC feeds from the PDAP (PDAP-2S or PDAP-4S) or third-party power distribution unit and distributes these to each slot. Each slot has access to both A and B –48 VDC power feeds.

Electrical Connector Modules for Electrical Interfaces. The electrical connector modules enable copper and coax network interface cabling using industry-standard cables and connectors.

The Traverse supports 1:1 and 1:2 equipment protection switching. The left-most of two modules in a 1:1 protection group protects the next consecutive slot in the shelf. The middle of three modules in a 1:2 protection group protects the two adjacent working modules. The protection group can start in any odd or even-numbered slot.

For more information on ECMs, see Section 4—Planning and Engineering, Chapter 2—“Network Cabling using Electrical Connector Modules,” page 4-17.



Traverse 2000 Specifications

This table lists the specifications for the Traverse 2000 platform.

Table 2-1 Traverse 2000 Specifications

Parameter Specification

Number of shelves per 7-foot rack 4

Maximum switching capacity 95 Gbps

Power consumption 400 to 600 watts typical (max. 1300 watts including fan tray).Redundant DC inputs.–48 V to –60 V operating range.

Dimensions (height includes fan tray, depth includes cable covers)

18.28 H x 21.1 W x 13.75 D (inches)

46.34 H x 48.3 W x 34.9 D (centimeters)

Weight Empty: 16 lbsFully loaded including fan: 63 lbs

Empty: 7.2 kgFully loaded including fan: 28.58 kg

Operating temperature –5°C to +55°C

Humidity 90% maximum. Non-condensing

Supported service interface modules 28-Port DS1 XT 12-Port DS3/E3/EC-1 Clear Channel 24-Port DS3/E3/EC-1 Clear Channel 12-Port DS3/EC-1 Transmux 21-Port E1 8-Port OC-3/STM-1 4-Port OC-12/STM-4 1-Port OC-48/STM-16 1-Port OC-192/STM-64 8-Port GBE 24-Port Fast Ethernet 2-port GbE LX plus 8-port 100BaseFX 2-port GbE LX plus 16-port 10/100BaseTX 2-port GbE SX plus 16-port 10/100BaseTX

Supported common modules GCM EGCM EGCM with 1-port OC-12/STM-4 EGCM with 1-port OC-48/STM-16 VT/VC Switch



Traverse 1600 System

The Traverse 1600 is a 16-slot, 19-inch rack-mountable shelf. Optimized for access and metro/IOF ring switching as well as transport applications, it is also scalable to 75 Gbps STS-1/STM switching capacity with high-density DS1/E1 to OC-192/STM-64, 10/100 and Gigabit Ethernet service flexibility.

This section has information on the following topics: Traverse 1600 Front View, page 2-6. Traverse 1600 Rear View, page 2-7. Traverse 1600 Specifications, page 2-9.


Fourteen slots accommodate service interface and VT/VC switch modules, and two slots are dedicated to General Control Modules. The Traverse 1600 shelf is configured by populating the system with GCMs, SIMs, and VT/VC switch modules. Module guide rails are built into the shelf to allow for easy insertion of the modules into connectors mounted on the backplane.


P1P1


Slots 1–12: Any Service Interface or VT/VC Switch ModuleSlots 1–14: Any Optical Service Interface or VT/VC Switch Module






Slot Numbers. There are 16 slots in each Traverse 1600 shelf: Slots 15 and 16 are reserved for General Control Modules (GCMs). Slots 1–12 slots are for any service interface or VC/VT switch module. Slots 1–14 slots are for any optical service interface or VC/VT switch module.


Timing Interface. The backplane provides primary and secondary T1/E1 and CC2M (Composite Clock and 2MHz) input and output2 timing interfaces, and primary and

Slot Numbers

System Alarms Interfaces

Environmental Alarms Interfaces

Timing Interface

RS-232 for Modem

EthernetConnection to DCN

Environmental Alarms Module

MPX Connectors

Power Terminals




Connectors for ECM

Slots 1–12: Any Service Interface or VT/VC Switch ModuleSlots 1–14: Any Optical Service Interface or VT/VC Switch Module



secondary BITS input timing interfaces. These timing interfaces are routed to both GCMs which distribute system timing references to all modules.












For more information on ECMs, see Section 4—Planning and Engineering, Chapter 2—“Network Cabling using Electrical Connector Modules,” page 4-17.

Traverse 1600 Specifications

This table lists the specifications for the Traverse 1600 platform.

Table 2-2 Traverse 1600 Specifications


Number of shelves per 7-foot rack 4

System configuration 16-slot shelf:2 slots for redundant control modules (GCM).14 slots for universal service interface modules.

Maximum switching capacity 75 Gbps

Power consumption 350 to 550 watts typical (max. 1100 watts including fan tray).Redundant DC inputs.–48 V to –60 V operating range.

Dimensions (height includes fan tray, depth includes cable covers)

18.25 H x 17.25 W x 13.75 D (inches)


Weight Empty: 15 lbsFully loaded including fan: 52 lbs

Empty: 6.8 kgFully loaded including fan: 23.59 kg

Supported service interface modules 28-Port DS1 XT 12-Port DS3/E3/EC-1 Clear Channel 24-Port DS3/E3/EC-1 Clear Channel 12-Port DS3/EC-1 Transmux 21-Port E1 8-Port OC-3/STM-1 4-Port OC-12/STM-4 1-Port OC-48/STM-16 1-Port OC-192/STM-64 8-Port GBE 24-Port Fast Ethernet 2-port GbE LX plus 8-port 100BaseFX 2-port GbE LX plus 16-port 10/100BaseTX 2-port GbE SX plus 16-port 10/100BaseTX

Supported common modules GCM EGCM EGCM with 1-port OC-12/STM-4 EGCM with 1-port OC-48/STM-16 VT/VC Switch

Operating temperature –5°C to +55°C

Humidity 90% maximum. Non-condensing



Traverse 600 System

The Traverse 600 system has a smaller physical size than the Traverse 1600 and Traverse 2000 systems, and is most efficiently used by service providers and carriers that do not require the capacity of a full, 16-slot or 20-slot shelf.


The Traverse 600 system has a total of six plug-in slots and can be mounted in standard 19-inch and 23-inch wide racks. Four slots accommodate service or VT/VC switch modules and two slots are for GCMs or GCMs with optional integrated OC-12/STM-4 or OC-48/STM-16 transport.

The unit also has a vertical slot for a field replaceable fan module. The fan module consists of a fan controller, six fans, and an air filter.






Slot Numbers

System Alarms Interfaces


GCM Only: Slots 5 and 6

RS-232 for modemEthernet Connection to DCNEnvironmental

Alarms Module

MPX Connectors

Power Terminals Timing Interface

Service Interface Modules: Slots 1 to 4



Slot Numbers. There are 6 slots in each Traverse 600 shelf: 2 slots are reserved for General Control Modules (GCMs). 4 slots for any service interface and VC/VT switch modules.


Timing Interface. The backplane provides primary and secondary T1/E1 and CC2M (Composite Clock and 2MHz) input and output3 timing interfaces, and primary and secondary BITS input timing interfaces. These timing interfaces are routed to both GCMs which distribute system timing references to all modules.












Traverse 600 SpecificationsThis table lists the specifications for the Traverse 600 platform.Table 2-3 Traverse 600 Specifications

Parameter SpecificationSystem configuration 6-slot shelf:

2 slots for redundant control modules (EGCM1).4 slots for universal service interface modules.

1 This module has an extended temperature functionality (-40°C to +65°C) and can be used in Traverse 600 systems that are deployed in non-environmentally controlled facilities.

Maximum switching capacity 15 Gbps Power consumption 150 to 200 watts typical (maximum 300 watts).

Redundant DC inputs. –48 V to –60 V operating range.Dimensions 6.30 H x 17.25 W x 13.75 D (inches)

16 H x 43.8 W x 30.48 D (centimeters)Weight Fully loaded including fan: < 25 lbs

Fully loaded including fan: < 11.34 kgSupported service interface modules 28-Port DS1 XT 1

12-Port and DS3/E3/EC-1 Clear Channel 1

24-Port DS3/E3/EC-1 Clear Channel 1

12-Port DS3/EC-1 Transmux 21-Port E11

8-Port OC-3/STM-1 4-Port OC-12/STM-4 1-Port OC-48/STM-16 8-Port GBE 24-Port Fast Ethernet 2-port GbE LX plus 8-port 100BaseFX 2-port GbE LX plus 16-port 10/100BaseTX 2-port GbE SX plus 16-port 10/100BaseTX

Supported common modules GCM and EGCM1

EGCM with 1-port OC-12/STM-41

EGCM with 1-port OC-48/STM-161

VT/VC SwitchExtended temperature range –40°C to +65°CHumidity 90% maximum. Non-condensing


Chapter 1 Traverse PlatformsInterface Options and Densities

00

orts per helf

12

48

96

48

84

96

32

48

/32

/ 64

/ 64

32

16

4

–

Interface Options and Densities





Modules per

ShelfPorts per

ShelfPorts per

RackModules

per Shelf

Ports per Shelf

Ports per Rack

Modules per

Shelf

P

S


28-Port DS1 16 448 1792 12 336 1344 4 1




21-Port E13 16 336 1344 12 252 1008 4





18 36/144 144/576 14 28/112 112/448 4 8


16 32 / 256 128/1024 12 24 / 192 96 / 768 4 8


16 32 / 256 128/1024 12 24 / 192 96 / 768 4 8

8-Port OC-3/STM-1 18 144 576 14 112 448 4

4-Port OC-12/STM-4 18 72 288 14 56 224 4

1-Port OC-48/STM-16 18 18 72 14 14 56 4






Volume 1, Section 2: Hardware DescriptionsFan Tray with Fan Module and Air Ramp

Fan Tray with Fan Module and Air Ramp

The Traverse fan tray with fan module cools the GCM and service modules in the shelf. The fan tray draws in cooling air from the front and pushes the air upward through the perforated shelf. The integrated air ramp on the shelf above directs the heated air through to the rear of the shelf. The fan module has 5 fans on the Traverse 1600 tray and 6 fans on the Traverse 2000 tray.

The fan module can force up to 200 cubic feet per minute of cooling air. Use one fan tray per Traverse shelf. The fan tray for the Traverse 1600 system is mountable in either 19-inch or 23-inch wide racks. The fan tray for the Traverse 2000 system fits into 23-inch racks.

Figure 2-7 Front View Traverse 1600 Fan Tray

The fan module receives redundant power from the Traverse system and reports events and alarms to the GCM. If one or more fans fail: The LED on the front of the fan tray turns red. The other fans increase speeds. The GCM raises an alarm in the user interface.

If an individual module exceeds 44°C, the GCM raises an alarm in the GUI and increases the speed of the fans. The fan tray has been designed so that all modules are provided with cool air flow even if a fan fails to operate.

This table lists the specifications for the Traverse fan tray and fan modules for each shelf.

Table 2-5 Fan Tray and Fan Module Specifications

ParameterSpecification

Traverse 2000 Traverse 1600

Number of fans 6 5

Power Consumption 80 watts 70 watts

Dimensions (inches) 3.5 H x 21 W x 12.25 D 3.5 H x 17.25 W x 12.25 D

(centimeters) 8.75 H X 53.34 W x 31.12 D 8.75 H X 43.32 W x 31.12 D

Weight fan module: 3 lbfan tray: 4 lb

fan module: 2 lbfan tray: 3 lb

fan module: 1.36 kgfan tray: 1.81 kg

fan module: 0.91 kgfan tray: 1.36 kg


Chapter 1 Traverse PlatformsPower Distribution and Alarm Panel

Power Distribution and Alarm Panel

There are two different PDAPs4 available with the Traverse system5, the PDAP-2S and PDAP-4S. The PDAP-2S supports up to two and the PDAP-4S supports up to four Traverse shelves and is used with the Traverse 1600 or Traverse 2000 system.

The PDAP receives redundant –48 nominal central office (CO) power, and distributes redundant power to Traverse shelves. The power requirement is a function of the number of modules in a Traverse shelf. Each module requires approximately 42 watts for the DS3/EC-1 Clear Channel module to 90 watts for the double-width OC-192/STM-64 module. The maximum power consumption of a typical Traverse 1600 and Traverse 2000 system (equipped with OC-N/STM-N and Ethernet service interface modules, redundant GCMs, and fan trays) is approximately 900 to 1100 watts.

All power and interface connections are terminated from the rear of the Traverse 1600 and Traverse 2000 shelves, except for the serial interface and the Ethernet port (for local craft access), which are on the front faceplate of the GCM.

Redundant power input (A and B) and return cables enter from the back of the PDAP. The A and B input feed provide power protection for Traverse shelves and auxiliary equipment. The PDAP-2S provides redundant, field replaceable 40 ampere (amp) circuit breakers6 for up to two Traverse shelves and GMT fuses (from 0.25 amp to 10 amp per fuse) for up to 10 pieces of auxiliary equipment. The PDAP-4S provides redundant, field replaceable 40 amp TPA fuses6 for up to four Traverse shelves and GMT fuses (from 0.25 amp to 15 amp per fuse) for up to 5 pieces of auxiliary equipment. The field replaceable circuit breakers and fuses are accessible without having to remove the front panel.

The PDAP provides visual alarm status indicators for input power, fuse power, and critical, major, and minor bay alarms.

The PDAP-2S layout is diagrammed in the following figures.

Figure 2-8 PDAP-2S Front View

4 PDAP refers to both the PDAP-2S and PDAP-4S, unless specified otherwise.

5 Refer to pre-Release 1.3 Traverse system documentation for information about the original, superseded PDAP type (Model#: TPA-PDAP).

6 Optional PDAP-2S circuit breakers and PDAP-4S TPA fuses are available up to a 50 amp maximum.

Circuit Breakers Alarm LEDs FlangeGMT Fuses


Volume 1, Section 2: Hardware DescriptionsPower Distribution and Alarm Panel

Figure 2-9 PDAP-2S Rear View

The following illustrations show the front and rear views of the PDAP-4S.

Figure 2-10 PDAP-4S Front View

Figure 2-11 PDAP-4S Rear View

The PDAP is mountable in either 19-inch or 23-inch wide racks. It is 16 inches deep, 17 inches wide, and 2 inches high and weighs 12 pounds.

Note: The PDAP is not required if the Traverse system is deployed with an existing legacy power distribution panel.

Battery SupplyNEG VDC Input

Battery Distribution

Battery Return Supply and Distribution

Chassis Ground

TPA Fuses Alarm LEDs FlangeGMT Fuses

TPA

PAT

GMT GMT

Battery and Battery Return “A” Supply

Battery and Battery Return “B” Supply

Battery and Battery Return Distribution Terminal Blocks

Chassis GroundChassis Ground


Chapter 1 Traverse PlatformsTraverse Operating System Software

Traverse Dimensions Summary Table

The following table gives the dimensions for the Traverse components.

Traverse Operating System Software

The versatility and value of the Traverse system is underpinned by the advanced architecture and design of the Turin Networks Traverse Operating System software. The operating system and future extensions to it have one goal: enable service providers to rapidly conceive new service offerings, as well as quickly engineer, deploy, sell, and bill.

The Traverse operating system provides a distributed architecture with numerous redundancy and dependability features. These enable a host of benefits to carriers, among them: Automatic module discovery. Network topology management. Numerous plug-and-play features. Scalable bandwidth (from 1.5 Mbps to 10 Gbps). Demand-based services (ADM, DCS, ATM, IP7). Multiple network topologies (Linear, Ring, Mesh, Add-Drop). A unified Intelligent Control Plane. Distributed networking.

Table 2-6 Traverse Component Dimensions

Assembly Height Width Depth WeightEmpty

WeightFully

Loaded

Traverse 20001

1 Height includes fan tray and depth includes cable covers.

18.25 in 21.14 in 13.75 in. 16 lb 63 lb

46.34 cm 53.7 cm 34.93 cm 7.2 kg 28.58 kg

Traverse 16001

18.25 in. 17.25 in. 13.75 in 15 lb 52 lb

46.34 cm 43.82 cm 34.93 cm 6.8 kg 23.59 kg

Traverse 600

6.50 in. 17.25 in. 13.75 in 8 lb 21 lb

16.51 cm 43.82 cm 34.93 cm 3.63 kg 9.525 kg

Fan Tray (for Traverse 2000 and Traverse 1600)

3.5 in 21.142

17.253

2 Traverse 2000.

3 Traverse 1600.

12.25 in — 7 lb2

5 lb3

8.75 cm 53.7 cm2

43.82 cm331.12 cm — 3.180 kg2

2.27 kg3

PDAP 2 in 17 in 16 in — 12 lb

5.08 cm 43.18 cm 40.64 cm — 5.4431 kg

7 ATM and IP are planned for a future release.


Volume 1, Section 2: Hardware DescriptionsTraverse Operating System Software

Scalable bandwidth with fine-grain Quality of Service management. Intelligent distributed management plane architecture.

Distributed Architecture

Intelligent service provisioning and bandwidth brokering are made possible by the Traverse operating system’s distributed architecture8. This architecture enables a large array of software features: GCM redundancy control. IP-based control plane for neighbor discovery and connection set-up. Equipment provisioning and alarm and performance monitoring for all modules

and components. Facility provisioning, alarm, and performance monitoring for service and timing

interfaces. STS-level and STM-level cross-connect provisioning, alarm and performance

monitoring. VT-level and VC11/VC12-level cross-connect provisioning, alarm, and

performance monitoring. UPSR, BLSR, SNCP, and MS-SP ring operation. 1:1 and 1:2 equipment protection for electrical modules. 1+1 APS, 1+1 MSP, 1+1 Path, and SNCP protection for SONET/SDH interfaces.

Upgrades

You can perform upgrades to the Traverse operating system on all component modules with no impact or interference of Traverse operations and services. Software upgrades or reversions to all modules can be done locally or remotely. Traverse modules can store two complete software images to support software upgrade and reversion. A new image on any service module is backward compatible with the previous version on other service modules. This allows the network operator to upgrade the image of one service module in a Traverse shelf at a time.

Service module configuration and provisioned services are saved in the persistent databases on the GCMs. When a new or replacement service module is inserted (or a Traverse system restarts), the Intelligent Control Plane will configure and provision it with the persistent data; this returns the Traverse system, network, and services to the prior state.

General Control Redundancy

Engineered with multiple fault-tolerant and redundant components, the Traverse operating system can operate from a single GCM or in a system with mated GCMs. In a redundant configuration, each GCM has an arbiter circuit to elect active and standby modes, and to support protection switching. This allows for hitless software upgrades and fault recoveries.

8 The Traverse OS resides on the GCMs and the SIMs.


Chapter 1 Traverse PlatformsTraverse Operating System Software

Dependability

The Traverse operating system is built upon an industry-standard kernel, considerably enhanced by a Turin Networks-developed software layer that provides carrier-class reliability. This implementation includes: Dynamic service module loading and unloading. Application supervision. Network-wide inter-process communication, and other advanced features that

allow for automatic auditing of critical system resources, critical situation detection, and automatic recovery without the necessity of service module reset.

Turin High Availability Framework providing infrastructure for application level data replication over a unified interface.


Volume 1, Section 2: Hardware DescriptionsTraverse Operating System Software



Chapter 2General Control Modules

Introduction The General Control Module (GCM) controls and manages all Traverse shelf modules and services, and the fan tray. This chapter contains the following topics: General Control Module, page 2-22. Physical Access, page 2-23. Timing Subsystem, page 2-23. Alarm Interface, page 2-24. Specifications, page 2-24.

The Traverse system supports GCMs with or without integrated optics: GCM. Enhanced GCM (EGCM). EGCM with 1-port OC-12/STM-4 (IR1). EGCM with 1-port OC-12/STM-4 (LR2). EGCM with 1-port OC-48/STM-16 (IR1). EGCM with 1-port OC-48/STM-16 (LR2).

The information in this chapter applies to the GCM part of these modules only.

For specifications on the optical interfaces, see Chapter 3—“SONET/SDH Modules,” page 2-27.


Volume 1, Section 2: Hardware DescriptionsGeneral Control Module

General Control Module

The GCM controls and manages all Traverse shelf modules and services, and the fan tray. The GCM can operate by itself or with a second GCM for redundancy.

Redundant GCMs provide the following key functions: System initialization. Non-stop operations. Persistent database. System timing. External timing interfaces. Alarm relay interfaces, including environmental alarm inputs and outputs. Craft, management, and control interfaces. Redundant control plane and management plane (including provisioning, alarm

reporting, maintenance, and diagnostics).

Each GCM comes with 128 MB Flash and 256 MB of Synchronized Dynamic Random Access Memory (SDRAM). On-board Flash memory provides primary storage for system software images. It holds two software images and two configuration databases. System firmware, software, configuration, connection, and service databases can be downloaded into the GCM’s Flash memory for software upgrades, system preconfiguration, connection, and service preprovisioning. The GCM’s on-board SDRAM provides run-time storage for system firmware, software, configuration, connection, routing, forwarding, and service databases.

A single GCM failure will not affect systems operations and services. The fault-tolerant operating system supports non-service-affecting system software upgrade and rollback.

GCM with Integrated Optics

The GCM with Integrated optics provides overall control and management functions for the Traverse platform as well as incorporating a single OC-12/STM-4 or OC-48/STM-16 interface for optical trunk connectivity. This module significantly increases the configuration flexibility of the Traverse shelf by effectively freeing up slots for revenue-generating service interface modules.

The GCM with optics offers a true carrier-grade design supporting 1:1 redundancy for system control and optional 1+1 APS/MSP, UPSR/SNCP, and BLSR/MS-SP Rings.


Chapter 2 General Control ModulesTiming Subsystem

Physical Access

GCMs have a RS-232 interface (DB-9) for local technician access and Command Line Interface (CLI) support using a character-oriented terminal, such as a VT-100 terminal or a PC with terminal emulation software1. The serial port on the front faceplate of the GCM also supports hardware/firmware diagnostics and configuration (IP address, module and interface).

The GCMs also have a Ethernet interface (RJ-45) with auto-sensing capability located on the front faceplate, typically for temporary connection of a technician’s PC laptop. One 10/100 Ethernet port is located on the front of the GCM for local technician access. There is also a DCN 10/100 Ethernet port located on the backplane. It is bridged to the active and standby GCMs.

The GCM Ethernet interface is generally used for a temporary connection, but it can be left in place to connect multiple devices to the LAN. When there are two operational GCM modules in a Traverse node, each GCM’s Ethernet interface is active and usable for technician access, regardless of that GCM’s active or standby status. The GCM Ethernet interface on either the active or standby GCM can be used for CLI access as long as the IP routing is set up correctly. The IP address of the GCM Ethernet interface must be in the same network as the PC laptop. For instructions on setting IP addresses during initial commissioning, see Volume 2, Installation and Configuration.

Timing Subsystem

Each GCM has a timing subsystem, which has a Stratum 3 clock, primary and secondary T1/E1 and CC2M (Composite Clock—64KHz or 2MHz) synchronization input and output2 interfaces. The Stratum 3 clock recovers timing from the primary or secondary T1/E1 timing references, or any line interface, then generates and distributes SONET/SDH-compliant clock and frame synchronization pulses to all other modules over a dedicated timing network on the Traverse backplane. The clock supports free-run, locked, and holdover modes of operation.

Redundant GCMs provide 1:1 equipment protection for the timing system.

The Traverse system can distribute timing from any OC or STM interface to the timing output ports on the rear of the shelf. The timing output ports can be set to DS1 SF, ESF, E1 Unframed, Basic Frame, and Multi-Frame, or 2.048 MHz.

The Traverse system supports synchronization-status messages (SSM) to provide automatic re-configuration of line-timed rings, improve reliability of interoffice timing distribution, avoid the creation of timing loops, and troubleshoot synchronization related problems.

1 For CLI access through the GCM RS-232 interface, the active GCM must be used.2 Composite Clock output connectors are not used.


Volume 1, Section 2: Hardware DescriptionsAlarm Interface

Alarm Interface Each GCM has a system alarm interface allowing it to send visual and audible system alarms to system alarm wire-wrapped pins on the Traverse back of the shelf. The alarm outputs are bridged between the GCM slots to provide redundancy for each alarm indication. It can relay critical, major, and minor visual alarms to the PDAP-2S or PDAP-4S, visual and audible alarms to third-party fuse and alarm panel, or the gateway Traverse node.

The GCM can also send and receive additional programmable environmental alarms. An Environmental Alarm Module (EAM), located on the back of the shelf, provides additional environmental alarm input and output capability. The Enhanced GCM along with the EAM supports sixteen environmental alarm inputs and eight environmental alarm outputs.

An Alarm Cut-Off (ACO) button is located on the front of the GCM to silence the alarm buzzer and to reset timers for system maintenance alerts. When the ACO button is pressed, its LED is turned to amber; the alarm relay is opened (disabled), but the alarm condition still exists, and the alarm LED is maintained. A following alarm will switch off both the ACO button and its LED, close (enable) the appropriate alarm relay and switch on the matching LED.

Specifications Specifications for all GCM types are outlined in the table below.

Table 2-7 GCM Specifications


Maximum number per shelf 2 (all platforms)

Technician Serial interface RS-232C DB-9 (DCE)

Technician LAN interface 10/100BaseT Ethernet RJ-45

Backplane DCN Ethernet interface 10/100BaseT Ethernet RJ-45 (on rear of shelf and shared by active and standby GCMs)

Backplane RS-232 interface RS-232C, 8-pin RJ-45 (DTE)

System timing Internal clock: Stratum 3Free-run accuracy: ±4.6 x 10-6 (±7.1 Hz @ 1.544 MHz)Holdover stability: <255 slips (±3.7 x 10-7) for the initial 24 hoursMinimum pull-in/hold-in: ±4.6 x 10-6

Filtering: yes, 3 HzOutput Phase Transients: MTIE = 1 µsReference: External, line, internal

Synchronization interfaces 2 T1 synchronization input and output interfaces2 Composite Clock synchronization input interfaces

GCM Alarm interface

Enhanced GCM Alarm Interface

Visual: critical, major, minorAudible: critical, major, minor2 auxiliary output alarm contacts4 environmental input alarm contacts

16 environmental alarm input contacts8 environmental alarm output contacts

SDRAM 256 MB

Flash 128 MB


Chapter 2 General Control ModulesSpecifications

Temperature range -5°C to +55°C, GCM without optics-40°C to +65°C, EGCM-40°C to +65°C, EGCM with 1-port OC-12/STM-4-40°C to +65°C, EGCM with 1-port OC-48/STM-16

Power consumption 35 watts, GCM without optics40 watts, EGCM42 watts, EGCM with 1-port OC-12/STM-455 watts, EGCM with 1-port OC-48/STM-16

Dimensions 13.9" H x 1.03" W x 11" D (inches)


Weight 2.0 lbs

0.9072 kg

Industry Standards ITU-T G.704, G.707, G.781ANSI T1.105GR-253-CORE, GR-1244-CORE

Table 2-7 GCM Specifications (continued)



Volume 1, Section 2: Hardware DescriptionsSpecifications



Chapter 3SONET/SDH Modules

Introduction The SONET/SDH service interface modules support non-blocking cross-connects, protection switching, and alarm and performance monitoring. Each of the modules provides a physical connection, in accordance with transmission standards and functions.

The information in this chapter describes and gives the specifications for the following Traverse service interface modules: 8-Port OC-3/STM-1 Module, page 2-28. 4-Port OC-12/STM-4 Modules, page 2-30. 1-Port OC-48/STM-16 Modules, page 2-32. 1-Port OC-192/STM-64 Modules, page 2-34.


Volume 1, Section 2: Hardware Descriptions8-Port OC-3/STM-1 Module

8-Port OC-3/STM-1 Module

The 8-port OC-3/STM-1 module for the Traverse platform integrates the capabilities of a high-performance SONET/SDH ADM and a non-blocking cross connect in a single module. Compatible across all of the Traverse platforms, this high-performance module has eight OC-3/STM-1 ports that can be used as a trunk interfaces, as well as for the aggregation and grooming of SONET/SDH services.

Use the single-slot, hot-swappable OC-3/STM-1 module in any of the available optical interface slots of the Traverse 2000, Traverse 1600, or Traverse 600 shelves. Physical access to the optical interface is through an MPX connector on the back of the shelf. Configure the ports to process STM or SONET modes through the user interface.

Specifications

This table lists the specifications for the OC-3/STM-1 IR1 module.

Table 2-8 8-Port OC-3/STM-1 IR1 Module Specifications


Maximum modules per shelf Traverse 2000: 18Traverse 1600: 14

Port data rate 155.52 Mbps

Protection switching 1+1 APS/1+1 MSP, UPSR/SNCP, 1+1 Path

Optical line coding Binary Non-Return-to-Zero

Line format ITU -T Rec. G.707 SONET/SDHANSI T1.105-1995

GR-253-CORE

Connector interface MPX

Fiber media type Standard singlemode fiber

Nominal wavelength 1310 nm, typical

Transmitter output power1 –16 dBm to –8 dBm

Maximum RMS width 7.7 nm

Minimum extinction ratio 8.2 dB

Receiver signal level1 –27 dBm to –7 dBm (223 -1 PRBS, BER=10-10)

Guaranteed link budget1 0 to 11 dB

Power consumption 37 watts

Temperature -5°C to +55°C

Dimensions 13.9 H x 1.03 W x 11 D (inches)


Weight2.0 (pounds)

0.9072 (kilograms)


Chapter 3 SONET/SDH Modules8-Port OC-3/STM-1 Module

Regulatory Standards NEBS: GR-63-CORE, GR-1089-CORESafety: UL60950, EN 60950, IEC 60950, CSA C2.22 No. 60950

Eye Safety: Class 1.EMI: CC Part 15, Class A; EN 300 386; EN 55022, Class A.

Industry Standards ITU -T Rec. G.707 ANSI T1.105-1995

Bellcore GR-253-CORE

1 These values account for the connector loss from connection to the optical interface and the worst case optical path penalty.

Table 2-8 8-Port OC-3/STM-1 IR1 Module Specifications (continued)



Volume 1, Section 2: Hardware Descriptions4-Port OC-12/STM-4 Modules

4-Port OC-12/STM-4 Modules

The four-port OC-12/STM-4 module for the Traverse platform integrates the capabilities of a high-performance SONET/SDH ADM and a non-blocking cross connect in a single module. Compatible across all of the Traverse platforms, this high-performance module has four OC-12/STM-4 ports that can be used as trunk interfaces, as well as for the aggregation and grooming of SONET/SDH services.

Use the single-slot, hot-swappable OC-12/STM-4 module in any of the available optical interface slots of the Traverse 2000, Traverse 1600, or Traverse 600 shelves. Physical access to the optical interface is through an MPX connector on the back of the shelf. Configure the ports to process STM or SONET modes through the user interface.

Specifications

This table lists the specifications for the OC-12/STM-4 interfaces on the following modules: 4-port OC-12/STM-4 IR1. 4-port OC-12/STM-4 LR2. EGCM with 1-port OC-12/STM-4 IR1. EGCM with 1-port OC-12/STM-4 LR2.

Table 2-9 4-Port OC-12/STM-4 Module Specifications


IR1 LR2

Maximum interfaces per shelf Traverse 2000: 20Traverse 1600: 16

Port data rate 622.08 Mbps


Line Format ITU -T Rec. G.707 SONET/SDHANSI T1.105-1995

GR-253-CORE

Protection switching 1+1 APS/1+1 MSP, UPSR/SNCP, 1+1 Path



Nominal wavelength 1310 nm, typical 1550 nm, typical

Transmitter output power1 –16 dBm to –8 dBm -4 to 2 dBm

Maximum RMS width 2.5 nm n/a

Minimum extinction ratio 8.2 dB 10 dB

Receiver signal level1 –27 dBm to –7 dBm -26 dBm to -7 dBm

(223 -1 PRBS, BER=10-10)

Guaranteed link budget1 0 to 11 dB 11 to 22 dB

Max optical path penalty n/a 1 dB






Chapter 3 SONET/SDH Modules4-Port OC-12/STM-4 Modules

Weight2.0 (pounds)

0.9072 (kilograms)






Table 2-9 4-Port OC-12/STM-4 Module Specifications (continued)


IR1 LR2




The single-port OC-48/STM-16 module integrates the capabilities of a high-performance SONET/SDH ADM and a non-blocking cross connect in a single module. Compatible across all of the Traverse platforms, this high-performance module provides a single OC-48/STM-16 port that can be used as a 2.5 Gbps trunk interface, as well as for the aggregation and grooming of SONET/SDH services.

Use the single-slot, hot-swappable OC-12/STM-4 module in any of the available optical interface slots of the Traverse 2000, Traverse 1600, or Traverse 600 shelves. Physical access to the optical interface is through an MPX connector on the back of the shelf. Configure the port to process STM or SONET modes through the user interface.

Specifications

This table lists the specifications for the OC-48/STM-16 interfaces on the following modules: 1-port OC-48/STM-16 SR. 1-port OC-48/STM-16 IR1. 1-port OC-48/STM-16 LR1. 1-port OC-48/STM-16 LR2. 1-port OC-48/STM-16 VR2. 1-Port OC-48/STM-16 VR-x. EGCM with 1-port OC-48/STM-16 IR1. EGCM with 1-port OC-48/STM-16 LR2.


ParameterOC-48/STM-16

SR

OC-48/STM-16

IR

OC-48/STM-16

LR-1(L-16.1)

OC-48/STM-16

LR-2

OC-48/STM-16

VR-2

OC-48/STM-16VR ITU

Channel N-1, N

Maximum interfaces per shelf

Traverse 2000: 20Traverse 1600: 16

Port data rate 2,488. 32 Mbps



GR-253-CORE

Protection switching 1+1 APS/1+1 MSP, UPSR/SNCP, 1+1 Path, BLSR/MS-SP Ring



Wavelength range 1310 nm 1550 nm

42 (ITU channel 19-60)

Transmitter output power1 (dBm) –11 to –3 –6 to 0 –3 to +3 +4 to +10

Minimum sidenode suppression

30 dB

Minimum extinction ratio

8.2 dB



Receiver signal range1 (dBm)

–17 to –3 –17 to 0 –26 to –8 -25 to -8

(223 -1 PRBS, BER=10-10)

Chromatic dispersion tolerance (ps/nm) n/a 1600 3200

Guaranteed link budget,(dB)1 0 to 6 0 to 11 11 to 23 11 to 22 18 to 29

Max optical path penalty n/a 1 dB 2 dB



Dimensions13.9 H x 1.03 W x 11 D (inches)


Weight2.0 (pounds)

0.9072 (kilograms)








SR

OC-48/STM-16

IR

OC-48/STM-16

LR-1(L-16.1)

OC-48/STM-16

LR-2

OC-48/STM-16

VR-2

OC-48/STM-16VR ITU

Channel N-1, N




The single-port, dual-slot OC-192/STM-64 module integrates the capabilities of a high-performance SONET/SDH ADM and a nonblocking cross connect in a single module. Supported on the Traverse 2000 and Traverse 1600 platforms, this high-performance module provides a single OC-192/STM-64 port that can be used as a 10 Gbps trunk interface, as well as for the aggregation and grooming of SONET/SDH services.

Physical access to the optical interface is through an MPX connector on the back of the shelf. Configure the port to process STM or SONET modes through the user interface.

Specifications

This table lists the specifications for the OC-192/STM-64 modules.



SR-1

OC-192/STM-64

IR-2

OC-192/STM-64 L-64.2a

OC-192/STM-64 ELR-2

Modules per shelf Traverse 2000: 9Traverse 1600: 7

Port data rate 9, 953. 28 Mbps



GR-253-CORE

Protection switching 1+1 APS/1+1 MSP, UPSR/SNCP, 1+1 Path, BLSR/MS-SP Ring



Wavelength range 1310 nm 1550 nm

Transmitter output power1 –5 to –1 –2 to +2 +2 to +7

Minimum extinction ratio 10 dB 8.2 dB

Minimum side mode suppression 30 dB

Receiver signal range1(dBm) –14 to 0 –11 to +3 –20 to –4 -23 to -4

(223 -1 PRBS, BER=10-12)

Guaranteed link budget1 0 to 9 3 to 9 11 to 22 11 to 25

Optical path penalty n/a 2

Chromatic dispersion tolerance (ps/nm)

n/a 800 1600





Weight 4.2 (pounds)

1.9051 (kilograms)










SR-1

OC-192/STM-64

IR-2

OC-192/STM-64 L-64.2a

OC-192/STM-64 ELR-2





Chapter 4VC and VT Switching Modules

Introduction The Traverse system cross connects at the VT-1.5, VC-11, and VC-12 levels using one of the following components: VCX Component, page 2-38. VT/VC Switch Module, page 2-39.

Switching at this level of granularity requires less multiplexing and demultiplexing between VC or STS terminations. Also, these components provide important groom-and-fill capabilities. These capabilities mean as many lower-speed channels as possible are packed into a circuit. This packing makes the network more efficient and enables faster service provisioning.

Multiple VCX components and VT Switches can be deployed to create a larger non-blocking cross connect fabric. These can be added in the same Traverse shelf and distributed across a network.


Volume 1, Section 2: Hardware DescriptionsVCX Component

VCX Component

The virtual container (VC) cross-connect (VCX) component is connected to any STM module to increase the use of resources. This component has a termination capacity for up to 16 unidirectional STM-1s (48 unidirectional VC3s) or 8 bidirectional STM-1 (24 bidirectional VC3s). It can support up to 504 bidirectional E1 services or 672 bidirectional DS1 services.

The VCX component supports following features: Converts high order VC-3 signals to low order VC-3 signals. Switches traffic at the high order VC3 level. Switches traffic at the low order (VC11 and VC12) level. Mixes high order and low order traffic on a AU-4. Mixed AU-4 payloads have a

combination of TUG-3s that contain both payloads of TU-3s and TUG-2s. Converts low order traffic mapped at the AU-3 level to the AU-4 level.

Specifically, the integrated VCX component performs the following transport functions: E1 transport through TUG2/TUG3/VC4. E1 transport through TUG2/VC3. DS1 transport through TUG2/TUG3/VC4. DS1 transport through TUG2/VC3. E3 transport through low order VC3 in a mixed VC11/VC12/VC3-payload VC4. DS3 transport through low order VC3 in a mixed VC11/VC12/VC3-payload VC4. Conversion between AU3-mapped VC12 and AU4-mapped VC12. Conversion between AU3-mapped VC11 and AU4-mapped VC11. Bidirectional and unidirectional VC12. Bidirectional and unidirectional VC11. Unidirectional VC11 and VC12 multicast.

This component operates with a mated VCX in a 1:1 equipment protection group. Use this component to cross connect VCs off of all supported protection groups: 1+1 MSP, and SNCP and MS-SP rings.

SpecificationsThis table lists the specifications for the VCX Switch subassembly are shown in the table below.Table 2-12 VCX Component Specifications

Parameter Value

VC-11 switching capacity 1344

VC-12 switching capacity 1008

Data rate 2.5 Gbps

Architecture Non-blocking time division switch


Industry Standards ITU-T G.707.ANSI T1.105-1995.Bellcore GR-253-CORE.Bellcore GR-2996 Section 5.Bellcore TR-233 Section 4 (compliant with applicable sections).


Chapter 4 VC and VT Switching ModulesVT/VC Switch Module

VT/VC Switch Module

The VT/VC Switch 2688 module integrates wideband switching and grooming functions into the Traverse platform. The module provides 2688 VT-1.5 tributary terminations across eight STS-12 inputs (equivalent to an STS-96). This module has 5 Gbps of bi-directional non-blocking capacity and is a powerful solution that complements the Traverse system's inherent switching and grooming capabilities. In addition to serving as a wideband digital cross-connect, the VT/VC Switch 2688 module is optimized for VT/VC ADM aggregation and terminal multiplexer applications.

Leveraging the Traverse platform's distributed architecture, a shelf can be equipped with multiple VT/VC Switch 2688 modules to enable non-blocking scalability to more than 384 protected STS-1 equivalents (10,752 + VT1.5 path terminations).

Use the VT/VC Switch module in any of the universal slots on any of the Traverse 2000, Traverse 1600, or Traverse 600 shelves. The VT/VC Switch provides the following cross-connect functions: Support for unidirectional and bidirectional cross connections at the VT/VC level. Support for multicast cross connections of any VT/VC payload. Adds or drops any VT/VC payload from any path on any OC-N/STM-N module. Aggregates VT/VC connections from any incoming signal to any outgoing signal. VT/VC-level services over Dual Ring Interconnection (DRI).

This module operates with a mated module in a 1:1 equipment protection group. Use this module to cross connect VT/VCs off of all supported protection groups: 1+1 APS, UPSR, BLSR, 1+1 path protection, 1+1 MSP, SNCP, and MS-SP Rings.

SpecificationsProduct specifications for the VT/VC Switch are shown in the table below.

Table 2-13 VT Switch Module Specifications


VT 1.5 switching capacity 2688 x 2688

STS-1 termination capacity 96

Data rate 5.0 Gbps

Maximum number per shelf 10 in a 384 STS-1 equivalent DCS application.

Architecture Non-blocking time division switch


Dimensions 13.9" H x 1.03" W x 11" D

Weight 2.0 lbs

Industry Standards ITU-T G.707.ANSI T1.105-1995.Bellcore GR-253-CORE.Bellcore GR-2996 Section 5.Bellcore TR-233 Section 4 (compliant with applicable sections).


Volume 1, Section 2: Hardware DescriptionsVT/VC Switch Module



Chapter 5Electrical Modules

Introduction The information in this chapter describes and gives the specifications for the following Traverse service interface modules (SIM): 28-Port DS1 XT Module, page 2-42. 12-Port DS3/E3/EC-1 Clear Channel Module, page 2-43. 24-Port DS3/E3/EC-1 Clear Channel Module, page 2-44. 12-Port DS3/EC-1 Transmux Module, page 2-45. 21-Port E1 Module, page 2-46.


Volume 1, Section 2: Hardware Descriptions28-Port DS1 XT Module

28-Port DS1 XT Module

The 28-port DS1 Extended Temperature module delivers high-density wideband access to the Traverse platform. The DS1 XT module maps ingress DS1 line signals into VT-1.5 or DS3 structured STS-1s, which are switched/cross-connected to an egress card. Use the optional VT Switch module to use transport bandwidth efficiently.

Use the single-slot, hot-swappable DS1 XT module in any of the available electrical interface slots of the Traverse 2000, Traverse 1600, or Traverse 600 shelves. Physical interfaces are 64 pin Telco connectors on the back of the shelf. The module also has an extended temperature functionality (-40°C to +65°C) and can be used in Traverse 600 systems that are deployed in non-environmentally controlled facilities.

Specifications

This table lists the specifications for the 28-port DS1 XT module.

Table 2-14 28-port DS1 Module Specifications



Protection Switching 1:1 or 1:2 Equipment Protection

Bit rate 1.544 Mbps

Line-rate accuracy +/–50 bps (+/–32 ppm)

STS/AU-4 structure DS3 mapped or VT-1.5/VC-11 mapped

Frame structure ESF, SF

Line code AMI, B8ZS (per ANSI T1.102-1993)

Output pulse amplitude 2.4 –3.6 V peak to peak

Output pulse shape Per GR-499-CORE

Output power level 12.6 to 17.9 dBm in a 3 kHz (+/– 1 kHz) band centered at 772 kHz; –16.4 to –11.1 dBm in a 3 kHz (+/– 1 kHz) band centered at 1,544 kHz

Connector Telco 64 (ECM required)

Impedance 100 ohm (+/–5%)

Loopback modes Terminal, Equipment, and Facility

Maximum line length 655 feet using ABAM #22 AWG

Extended temperature range –40°C to +65°C




Weight2.0 (pounds)

0.9072 (kilograms)



Industry Standards ANSI T1.102, T1.102.GR-499-CORE, GR-253-CORE.


Chapter 5 Electrical Modules12-Port DS3/E3/EC-1 Clear Channel Module

12-Port DS3/E3/EC-1 Clear Channel Module

The 12-port DS3/E3/EC-1 Clear Channel module delivers high-density broadband access to the Traverse platform. The module provides asynchronous mapping of ingress DS3, EC-1, or E3 line signals into a SONET or SDH signal, which are switched/cross-connected to an egress card. Here they are either transmitted to an output line interface of the same type, or multiplexed into a higher rate signal for transmission. Independently configure any of the 12 ports for EC-1 or clear channel DS3 or E3 through the user interface.

Use the single-slot, hot-swappable DS3/EC-1 module in any of the available electrical interface slots of the Traverse 2000, Traverse 1600, or Traverse 600 shelves. Physical I/O interfaces are on the back of the shelf.

Specifications

This table lists the product specifications for the 12-port DS3/EC-1 Clear Channel module.

Table 2-15 12-port DS3/E3/EC-1 Clear Channel Module Specifications


DS3 Value E3 Value EC-1 Value

Maximummodules per shelf



Bit rate 44.736 Mbps +/–20 ppm 2.048 Mbps, +/–50 bps (+/–32 ppm)

51.840 Mbps +/–20 ppm

Frame format C-bit and M23 (per GR-499, ANSI T1.107)Unframed (per GR-499)

E3 framing per G.751 or G.832

EC-1 framing (per GR-253 and ANSI

T1.105)

Line code HDB3

Termination Unbalanced Coaxial Cable

Input impedance 75 Ohm

Cable loss 450 ft. (137.2 meters)

Connector BNC (ECM required)

Loopback modes Terminal and Facility

Temperature Range -5°C to +55°C




Weight2.0 (pounds)

0.9072 (kilograms)

Regulatory Stan-dards

NEBS: GR-63-CORE, GR-1089-CORESafety: UL60950, EN 60950, IEC 60950, CSA C2.22 No. 60950


Industry Standards ITU-T G.751, G.832ANSI T1.105, T1.107

Bellcore: GR-499-CORE, GR-253-CORE


Volume 1, Section 2: Hardware Descriptions24-Port DS3/E3/EC-1 Clear Channel Module

24-Port DS3/E3/EC-1 Clear Channel Module

The 24-port DS3/EC-1 Clear Channel module delivers high-density broadband access to the Traverse platform. The module provides asynchronous mapping of ingress DS3, EC-1, or E3 line signals into a SONET or SDH signal, which are switched (cross-connected) to an egress card. Here they are either transmitted to an output line interface of the same type, or multiplexed into a higher rate signal for transmission. Independently configure any of the 24 ports for EC-1 or clear channel DS3 or E3 through the user interface.

Use the single-slot, hot-swappable 24-port DS3/EC-1 module in any of the available electrical interface slots of the Traverse 2000, Traverse 1600, or Traverse 600 shelves. Physical I/O interfaces are on the back of the shelf.

Specifications

This table lists the product specifications for the 24-port DS3/EC-1 Clear Channel module.

Table 2-16 24-port DS3/E3/EC-1 Clear Channel Module Specifications


DS3 Value E3 Value EC-1 Value

Maximum modules per shelf



Bit rate 44.736 Mbps +/–20 ppm 2.048 Mbps, +/–50 bps (+/–32 ppm)

51.840 Mbps +/–20 ppm

Frame format C-bit and M23 (per GR-499, ANSI T1.107)Unframed (per GR-499)

E3 framing per G.751 or G.832

EC-1 framing (per GR-253 and ANSI

T1.105)

Line code HDB3










Weight2.0 (pounds)

0.9072 (kilograms)

Regulatory Stan-dards

NEBS: GR-63-CORE, GR-1089-CORESafety: UL60950, EN 60950, IEC 60950, CSA C2.22 No. 60950


Industry Standards ITU-T G.751, G.832ANSI T1.105, T1.107

Bellcore: GR-499-CORE, GR-253-CORE


Chapter 5 Electrical Modules12-Port DS3/EC-1 Transmux Module

12-Port DS3/EC-1 Transmux Module

The 12-port DS3/EC-1 Transmux module provides DS3 to DS1 to VT transmultiplexing (transmux) functions for channelized DS3 access to the Traverse platform. An ideal solution for bridging legacy TDM networks with an expanding fiber infrastructure, the Transmux module converts T1s to VT1.5s allowing them to be transported across an optical link, creating greater bandwidth efficiencies.

Use the single-slot, 12-port Transmux module in any electrical interface slot of the Traverse 2000, Traverse 1600, or Traverse 600 shelves. In addition to transmux functionality, any port can be independently configured for DS3 clear channel or EC-1 operation through the user interface.

Specifications

This table lists product specifications for the DS3/EC-1 Transmux module

Table 2-17 12-port DS3/EC-1 Transmux Module Specifications


DS3 Value EC-1 Value

Maximummodules per shelf



Bit rate 44.736 Mbps +/–20 ppm 51.840 Mbps +/–20 ppm

Frame format C-bit and M23 (per GR-499 and ANSI T1.107)

Unframed (per GR-499)

EC-1 framing (per GR-253 and ANSI T1.105)

Line code HDB3










Weight2.0 (pounds)

0.9072 (kilograms)



Industry Standards ITU-T G.707, G783.ANSI T1.105, T1.107

GR-499-CORE, GR-253-CORE


Volume 1, Section 2: Hardware Descriptions21-Port E1 Module

21-Port E1 Module

The 21-port E1 Extended Temperature module delivers high-density wideband access to the Traverse platform. The E1 XT module maps ingress E1 line signals into VC11 or DS3 structured STM, which are switched/cross-connected to an egress card. Use the optional VCX hardware to use transport bandwidth efficiently.

Use the single-slot, hot-swappable E1 XT module in any of the available electrical interface slots of the Traverse 2000, Traverse 1600, or Traverse 600 shelves. Physical interfaces are 64 pin Telco connectors on the back of the shelf. The module also has an extended temperature functionality (-40°C to +65°C) and can be used in Traverse 600 systems that are deployed in non-environmentally controlled facilities.

Specifications

This table lists the product specifications for the E1 module.

Table 2-18 21-port E1 Module Specifications


Maximum number per shelf Traverse 2000: 16Traverse 1600: 12


Bit rate 2.048 Mbps,

Line-rate accuracy +/–50 bps (+/–32 ppm)

AU-4/STS structure VC-12 mapped

Frame format CRC4

Line code AMI, HDB3

Impedance 75 ohm unbalanced120 ohm balanced

Pulse amplitude 2.37V for 75 ohm3.0V for 120 ohm

Output pulse shape Per ITU-T G.703

Output power level Per ITU-T G.703

Connector Unbalanced, BNC (ECM required)Balanced, DB-15

Loopback modes Terminal, Equipment, and Facility

Maximum line length Per ITU-T G.703

Extended temperature range –40°C to +65°C




Weight2.0 (pounds)

0.9072 (kilograms)


Chapter 5 Electrical Modules21-Port E1 Module

Regulatory Standards NEBS: GR-63-CORE, GR-1089-CORESafety: UL60950, EN 60950, IEC 60950, CSA C2.22 No.

60950Eye Safety: Class 1.

EMI: CC Part 15, Class A; EN 300 386; EN 55022, Class A.

Industry Standards ETS 300 417.ITU-T G.783.

ITU-T G.707, ITU-T G.783.ITU-T G.704, ITU-T G.703.

Table 2-18 21-port E1 Module Specifications (continued)



Volume 1, Section 2: Hardware Descriptions21-Port E1 Module



Chapter 6Ethernet Modules

Introduction Turin Networks offers a number of Ethernet interfaces in a combination of modules: 8-Port Gigabit Ethernet Module, page 2-50. 24-Port Fast Ethernet Module, page 2-52. GbE/Fast Ethernet Combo Modules, page 2-54.

These Ethernet modules allow the Traverse system to support Ethernet access, aggregation, and transport over SONET/SDH applications such as Internet access service (IAS), transparent LAN (TLS) interconnect, and service provider peer interconnections.


Volume 1, Section 2: Hardware Descriptions8-Port Gigabit Ethernet Module

8-Port Gigabit Ethernet Module

The single-slot 8-Port Gigabit Ethernet (GbE) module is based on Ethernet transmission standards and provides native rate access with its high throughput and effective bandwidth utilization. GbE modules integrate a full IEEE 802.1D Layer 2 switch and SONET/SDH mapper. They can aggregate and transport Ethernet frames in the SONET/SDH contiguous payload. The GbE modules operate in full-duplex mode and perform Layer 2 classification, Ethernet and VLAN aggregation and switching, and per-port and per-flow traffic management.

The GbE with Virtual Concatenation module supports standard and high order virtual concatenation and provides up to a maximum of 24 Ethernet over SDH or SONET trunks. It allows optical bandwidth to be tuned in small increments on demand eliminating stranded bandwidth. The GbE with VC module maps frames directly into a payload of N separate transport paths rather than using the fixed contiguous concatenated transport channels.

Specifications

This table lists the specifications for the GbE interfaces on the following modules: 8-port GbE LX. 2-port GbE LX plus 8-port 100BaseFX. 2-port GbE LX plus 16-port 10/100BaseTX. 2-port GbE SX plus 16-port 10/100BaseTX.

Table 2-19 8-Port GbE Module Specifications


GbE SX GbE LX


Connector MPX

Port data rate 1 Gbps

Frame length range 64 to 9,600 Bytes (default 1,522)

Bandwidth and Traffic Management Specifications

Transport bandwidth Up to 2.488 Gbps

Concatenation Standard SVC-3 or STS-1 VC-4 or STS-3c

VC-4-4c or STS-12cVC-4-16c or STS-43c

VCAT/LCASVC-3-nv or STS-1-nvVC-4-nv or STS-3c-nv

Transport circuits 24

Rate shaping Ethernet bandwidth guarantees and limits in 1 Mbps increments

VLANs 4093

MAC addresses up to 32, 000

Mapping HD, X.86, GFP


Chapter 6 Ethernet Modules8-Port Gigabit Ethernet Module

Optical Interface Specifications

Fiber media type Singlemode fiber (SX) Singlemode fiber (LX)

Nominal wavelength 850 nm 1310 nm

Transmitter output power1 –9.5 dBm –10 dBm

Receiver level1 –16 dBm –18 dBm

223 -1 PRBS, BER=10-10

Guaranteed link budget1 6.5 dB 8 dB

Maximum reach 2.5 km 20 km

Physical Specifications




Weight 2.1 lbs

0.9525 kg


Eye Safety: Class 1.EMI: FCC Part 15, Class A; EN 300 386; EN 55022, Class A.

ETSI: ETS 300 019-1-3, 019-2-3 (Environmental)

Industry Standards ITU -T Rec: G.707, G.783, G.957ANSI: T1.105, T1.107

Bellcore GR-253-CORE, GR-1377-COREIEEE: 802.3z/x/ad, 802.1D/p/Q VLAN

RFC: 1157, 1213, 1643, 2239, 1661, 1662.


Table 2-19 8-Port GbE Module Specifications (continued)


GbE SX GbE LX


Volume 1, Section 2: Hardware Descriptions24-Port Fast Ethernet Module

24-Port Fast Ethernet Module

The single-slot 24-port Fast Ethernet (10/100BaseTX) module is based on Ethernet transmission standards and provides native rate access with its high throughput and effective bandwidth utilization. The Fast Ethernet module operates in full-duplex mode and performs Layer 2 classification, Ethernet and VLAN aggregation and switching, and per-port and per-flow traffic management.

Each port on the 10/100BaseTX module supports automatic MDI (Medium Dependent Interface) and MDI-X determination. It can be connected to either a straight-through cable or a cross-over cable. Auto-MDIX will automatically detect and correct wiring problems such as MDI crossover, swapped pairs, and reverse polarity.

Specifications

This table lists the specifications for the Fast Ethernet interfaces on the following modules: 2-port GbE LX plus 16-port 10/100BaseTX 2-port GbE SX plus 16-port 10/100BaseTX 10/100BaseTX

Table 2-20 24-Port Fast Ethernet (10/100 TX) Module Specifications



Connector RJ-45

Media and Reach 2 pairs Twisted Pair Category 5 UTPReach: 328 ft or 100 meters

Port data rate 10 or 100 Mbps (auto-negotiated)

Frame length range 64 to 9,600 Bytes (default 1,522)

Peak differential signal amplitude 10 Mbps = 4.0 volts100 Mbps = 2.0 volts


Transport bandwidth Up to 2.488 Gbps



Virtual/LCASVC-3-nv or STS-1-nvVC-4-nv or STS-3c-nv



VLANs 4093

MAC addresses up to 32,000

Mapping HD, X.86, GFP




Chapter 6 Ethernet Modules24-Port Fast Ethernet Module



Weight 2.1 lbs

0.9525 kg





Bellcore GR-253-CORE, GR-1377-COREIEEE: 802.3u/x/ad, 802.1D/p/Q VLAN

Table 2-20 24-Port Fast Ethernet (10/100 TX) Module Specifications (continued)



Volume 1, Section 2: Hardware DescriptionsGbE/Fast Ethernet Combo Modules

GbE/Fast Ethernet Combo Modules

Turin Networks offers the following single-slot Gigabit/Fast Ethernet interface combo modules: 2-port GbE LX plus 8-port 100BaseFX

2-port Gigabit Ethernet LX with Virtual Concatenation (optical interface)/8-port 100BaseFX with Virtual Concatenation (optical interface).

2-port GbE LX plus 16-port 10/100BaseTX2-port Gigabit Ethernet LX with Virtual Concatenation (optical interface)/16-port 10/100BaseTX with Virtual Concatenation (twisted pair/copper interface).

2-port GbE SX plus 16-port 10/100BaseTX2-port Gigabit Ethernet SX with Virtual Concatenation (optical interface)/16-port 10/100BaseTX with Virtual Concatenation (twisted pair/copper interface).

For GbE LX and SX interface specifications, see 8-Port Gigabit Ethernet Module, page 2-50.

For Fast Ethernet interface specifications, see 24-Port Fast Ethernet Module, page 2-52.

Specifications

This table lists the power consumption values for supported Ethernet combo modules.

This table lists the specifications for the Fast Ethernet FX interfaces.

Table 2-21 Power Consumption for Ethernet Combo Modules

Ethernet Combo Module Power Consumption

2-port GbE LX plus 8-port 100BaseFX 68 watts

2-port GbE LX plus 16-port 10/100BaseTX 67 watts

2-port GbE SX plus 16-port 10/100BaseTX 67 watts

Table 2-22 GbE Combo Fast Ethernet FX Module Specifications



Connector MPX

Port data rate 100 Mbps

Frame length 9,600 Bytes (default 1,522)


Transport bandwidth Up to 2.488 Gbps (one STM-16 or OC-48)



VCAT/LCASVC-3-nv or STS-1-nvVC-4-nv or STS-3c-nv




Chapter 6 Ethernet ModulesGbE/Fast Ethernet Combo Modules

VLANs 4093

MAC addresses up to 32, 000

Mapping HDLC, X.86, GFP

Optical Interface Specifications

Fiber media type Singlemode fiber

Nominal wavelength 1310 nm

Transmitter output power1 –16 dBm

Receiver level1 –29 dBm ( 223 -1 PRBS, BER=10-10)

Guaranteed link budget1 13 dB

Maximum reach 32.5 km




Weight 2.1 lbs

0.9525 kg





Bellcore GR-253-CORE, GR-1377-COREIEEE: 802.3z/x/ad, 802.1D/p/Q VLAN


Table 2-22 GbE Combo Fast Ethernet FX Module Specifications (continued)



Volume 1, Section 2: Hardware DescriptionsGbE/Fast Ethernet Combo Modules




Introduction As a complement to the Traverse in-chassis DS1 module, the TransAccess 100 Mux provides a cost-effective solution for delivering T1 services off high-capacity SONET rings and the Traverse system. It is a low cost and low power consumption STS-1 multiplexer. It provides customers with limited rack space the ability to deploy a large number of STS-1s.

This chapter contains the following topics: TransAccess 100 STS-1/T1 Mux Description, page 2-57. TransAccess 100 Mux Specifications, page 2-58. DS1 Electrical Signal Specifications, page 2-58. STS-1 Electrical Signal Specifications, page 2-59. Craft Port Specifications, page 2-59. TransAccess 100 Mux Compliance Standards, page 2-60.

TransAccess 100 STS-1/T1 Mux Description

A self-contained multiplexer, the TransAccess 100 Mux is capable of asynchronously mapping 28 DS1 signals into 28 Virtual Tributary (VT1.5) signals and then into a VT structured STS-1.

Figure 2-12 TransAccess 100 Mux

For maximum protection, 1:1 redundancy is provided on both the high-speed and low-speed interfaces. The 28 DS1 low-speed signals are mapped on one Mapper card occupying one card slot to provide one STS-1 signal. The protection card occupies the second card slot and the DS1 and EC-1 signals are bridged on both cards. The unit can be employed as an STS-1 B8ZS electrical input to the Traverse system. The Main and Standby cards are hot-swappable without service interruption.


Volume 1, Section 2: Hardware DescriptionsTransAccess 100 Mux Specifications

TransAccess 100 Mux Specifications

This table lists the specifications for the TransAccess 100 Mux equipment.

DS1 Electrical Signal Specifications

This table lists the specifications for the DS1 signals.

Table 2-23 TransAccess 100 Mux Specifications

Specification Description

Low-speed channel capacity Up to 28 lines of 1.544 Mbps dataMultiplexed data rate 51.840 Mbps ± 20 ppmSignal interface 51.840 Mbps ± 20 ppmLine impedance 75 ohms ± 5% unbalancedReframe time STS1: 2 msOperating mode Full duplexPower consumption 45 Watts maximumWeight 8 lb. (3.6287 kg) fully loaded

Table 2-24 DS1 Electrical Signal Specifications


Nominal line 1.544 Mbps ± 130 ppmAIS line rate 1.544 Mbps ± 32 ppmLine code Half-width bipolar AMI or B8ZSTermination One balanced twisted pair for each direction of transmissionImpedance 100 ohms ± 5% (balanced)Pulse shape Meets TR-TSY-000499 mask with amplitude of between 2.4

and 3.6 volts1

1 A 100 ohms T1 patch cable is required when measuring the pulse mask.

Power level For an all-ones pattern, the power in a band no wider than 3 kHz: Centered at 772 kHz is between 12.6 and

17.9 dBm Centered at 1544 kHz is at least 29 dB below the power

level at 772 kHzPulse imbalance Less than 0.5 dB difference between total power of positive

and negative pulsesJitter generation Less than 0.3 time slots RMSCable ABAM or equivalentMaximum span 655 feet to cross connect


Chapter 7 TransAccess 100 MuxCraft Port Specifications

STS-1 Electrical Signal Specifications

This table lists the specifications for the EC1 signals.

Craft Port Specifications

The TransAccess 100 Mux’s technician access craft port is used to set the IP address and IP mask. It is also used for downloading software upgrades and patches. All other management functions are handled through the TransNav system or the Turin CLI.

Table 2-25 STS-1 Electrical Signal Specifications


Nominal line 51.840 Mbps ± 20 ppmLine code B3ZS (bipolar with three-zero substitution)Termination One coaxial line is used for each direction of

transmission.Impedance 75 ohms ± 5% (unbalanced)Pulse shape Meets TR-TSY-000499 mask with amplitude of

between 0.36 and 0.85 volts peakPulse imbalance Less than 3.5 dB difference between total power

of positive and negative pulsesJitter generation Less than 0.3 time slots RMSCable 728A RG-6U or equivalentMaximum span 450 feet to the STX cross connect

Table 2-26 Craft Port Specifications


Memory Non-volatile (retains settings)

Password protection Administration and user level

User interface Menu driven

Terminal supported VT-100 (or equivalent) or PC (using VT-100 terminal emulation)

Modem capability External

Baud rate 9600, 19200, and 38400 bps (default is 9600)

Performance monitoring capabilities

Supports full OAM&P

Craft data RS-232D

Craft terminal connection RJ-45 modular jack


Volume 1, Section 2: Hardware DescriptionsTransAccess 100 Mux Compliance Standards

TransAccess 100 Mux Compliance Standards

The TransAccess 100 Mux complies with the following industry standards: FCC Part Class A. UL 1950. CSA 22.2. GR-499-CORE, GR-253-CORE. GR-1089, GR-63 (NEBS compliant).


SECTION 3 MANAGEMENT SYSTEM OVERVIEWSECTION 1SYSTEM OVERVIEW

SECTION 1

Contents

Chapter 1TransNav Management System Overview

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1What Is the TransNav Management System?. . . . . . . . . . . . . . . . . . . . . . . . . 3-1TransNav Software Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2Client Workstation Application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2Management Server Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3Node Agent Application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3TransNav Management System Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3Interoperability with Third-party Management Systems . . . . . . . . . . . . . . . . . 3-4Autodiscovery and Preprovisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4Simultaneous Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4Scalability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5Reliability, Availability and Serviceability (RAS) . . . . . . . . . . . . . . . . . . . . . . . 3-5

Chapter 2Network Management Features

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7Fault and Event Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7

Alarm Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7Data Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7Flexible Filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7Flexible Scoping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7Sorting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7Clearing Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7

Configuration Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8Equipment Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8Preprovisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8Service Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9Accounting Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9Performance Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9Security Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9Node Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10System Log Collection and Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10Report Generation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11

General Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11Data Set Snapshots. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11


Volume 1 Section 3 Management System Overview

Chapter 3User Interfaces

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13TransNav System Access Methods. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13Graphical User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14Map View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14Shelf View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15Command Line Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16Domain Level. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16Node Level. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16

Chapter 4Management System Requirements

TransNav Management System Requirements. . . . . . . . . . . . . . . . . . . . . . . . 3-17TransNav Management Server Hardware Requirements . . . . . . . . . . . . . . . . 3-18Sun Solaris Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18Windows 2000 Professional Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-19TransNav Management Server Software Requirements . . . . . . . . . . . . . . . . . 3-21TransNav Client Workstation Hardware Requirements . . . . . . . . . . . . . . . . . . 3-22TransNav GUI Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-23

List of FiguresFigure 3-1 TransNav Software Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2Figure 3-2 Map View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14Figure 3-3 Shelf View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15

List of TablesTable 3-1 Access Groups and Rights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9Table 3-2 Accessing the TransNav Management System. . . . . . . . . . . . . . . 3-13Table 3-3 Server Hardware Recommendations to Support up to 50 Nodes . 3-18Table 3-4 Server Hardware Recommendations to Support up to 100 Nodes3-19Table 3-5 Server Hardware Requirements for Windows 2000 Professional . 3-19Table 3-6 Server Software Requirements for Sun Solaris . . . . . . . . . . . . . . . 3-21Table 3-7 Server Software Requirements for Windows 2000 Professional . . 3-21Table 3-8 Minimum Requirements for Client Hardware. . . . . . . . . . . . . . . . . 3-22Table 3-9 Minimum Requirements for GUI Software. . . . . . . . . . . . . . . . . . . 3-23


SECTION 3MANAGEMENT SYSTEM OVERVIEW

Chapter 1TransNav Management System Overview

Introduction This chapter describes the TransNav Management System: What Is the TransNav Management System?, page 3-1. TransNav Software Functional Description, page 3-2. Client Workstation Application, page 3-2. Management Server Application, page 3-3. Node Agent Application, page 3-3. TransNav Management System Features, page 3-3.

What Is the TransNav Management System?

The TransNav Management System is an advanced element and subnetwork management system designed for comprehensive management of the TransNav network. The Java™-based TransNav software smoothly integrates into existing automated and manual operations support system (OSS) infrastructure.

The multi-level management architecture applies the latest distributed and evolvable technologies. These features not only enable you to create and deploy profitable new services, but also transition gracefully to a more dynamic and data-centric, multi-service optical transport network.

The TransNav Management System consists of an integrated set of software components that reside on the server, the client work stations, and on the individual nodes. Client Workstation Application. Provides the user interface for managing the

network. The management system supports both a graphical user interface (GUI) and a command line interface (CLI).

Management Server Application. Communicates with the nodes and provides classical element management FCAPS functionality (fault, configuration, accounting, performance, and security), as well as policy management, reporting, and system administration.

Node Agent Application. Resides on the General Control Module (GCM) and maintains a persistent database of management information for the node. It also controls the flow of information between the management server and the node.


Volume 1, Section 3: Management System OverviewTransNav Software Functional Description

TransNav Software Functional Description

The TransNav Management System is an all Java-based, highly integrated system that uses the identical architecture on the Traverse network nodes and the management server(s). The architecture leverages the Java Dynamic Management Kit (JDMK) implementation of Java Management extensions (JMX) to provide an efficient client-server architecture.

Figure 3-1 TransNav Software Architecture

All communication between nodes and the server or between the client application and the server uses the Java Remote Method Invocation (RMI) system over TCP/IP. The server also uses RMI internally between the JDMK servers and JDMK clients.

Information flows southbound from the GUI client to the Session Manager to the Application Server to the Traverse Node Gateway Client inside the management server and then down to the Traverse Node Gateway Agent embedded in the node, via RMI over TCP/IP.

Client Workstation Application

The client workstation application provides the user interface for managing the network. The TransNav Management System supports both a graphical user interface (GUI) and a command line interface (CLI). Refer to TransNav Software Functional Description, page 3-2 for a graphical representation of the client workstation application.

The client workstation application (either the GUI or the CLI) communicates with the session manager on the management server. Download the GUI applet or application from the management server or simply telnet to the server to access the CLI.


Chapter 1 TransNav Management System OverviewTransNav Management System Features

Management Server Application

The management server application communicates with nodes and provides classical element management FCAPS functionality (fault, configuration, accounting, performance, and security), as well as policy management, reporting, and system administration. Refer to TransNav Software Functional Description, page 3-2 for a graphical representation of the management server application.

Security management, logging, and external interfaces to upstream applications are all implemented in the upper level session management component on the management server. These functions are implemented as a JDMK server and are responsible for servicing both the GUI client applet and the northbound interfaces.

A separate SMNP agent, also implemented as a JDMK server, supports SNMP traps (fault management) for simplified version control. The SNMP agent works with the fault management application module.

The agent on the node passes node-level data to the management server via RMI over TCP/IP. On the management server, the Node Gateway Controller receives the information and pre-processes it. The Node Gateway Controller then passes the pre-processed information to the management functions within the Application Server.

The Application Server is responsible for persistence at the server side and to this end, manages the entire interface with the underlying SQL database.

Node Agent Application

Each node has a redundant GCM with a persistent relational database management system that records provisioning, alarm, maintenance, and diagnostic information for the node. Refer to TransNav Software Functional Description, page 3-2 for a graphical representation of the node agent application.

Each GCM uses Java agents (M-Beans [management beans]) to communicate with Java applications on the management server and synchronize data between the server and the nodes it manages

TransNav Management System Features

The TransNav Management System provides comprehensive management for both the nodes and for the connections between nodes through the Intelligent Control Plane. This specifically includes efficient integration of management plane and control plane functions, and policy-based management.

The TransNav Management System features include: Interoperability with Third-party Management Systems, page 3-4. Autodiscovery and Preprovisioning, page 3-4. Simultaneous Users, page 3-4. Scalability, page 3-5. Reliability, Availability and Serviceability (RAS), page 3-5.


Volume 1, Section 3: Management System OverviewInteroperability with Third-party Management Systems

Interoperability with Third-party Management Systems

The TransNav Management System supports other telecommunications management network layer functions at the network management layer, the service management layer, and the business management layer through a variety of northbound interfaces. The management system provides options to support the following interfaces: Forwarding of SNMP traps to SNMP network management systems for integrated

higher-layer fault management. Domain-level and node-level CLI via scripts.

Near-term future releases will support: TL1 alarm and performance management forwarding from the management server. A bi-directional TL1 interface for flow-through circuit and service provisioning

from the management server. A CORBA® interface based on the TeleManagement Forum NML-EML CORBA

interface from the Multi-Technology Network Management working group. Integration with Enterprise Application Integration (EAI) buses and other custom

interfaces.

Autodiscovery and Preprovisioning

Each node uses a process called autodiscovery to learn the addresses of all equipment in its control plane domain. The CLI is used to enter the host name or IP address of the gateway node(s). The management system then discovers and manages all the nodes in the domain without requiring any other preprovisioned information.

The TransNav Management System supports preprovisioning, which allows you to perform provisioning functions independent of service activation. The effectiveness of preprovisioning depends upon effective traffic engineering to ensure that network capacity is available upon activation. Upon installation, a node is discovered automatically and the management server forwards the preprovisioned information to the node.

Simultaneous Users

The number of simultaneous users depends on whether the management server is running on a Windows® 2000 Professional server (for few nodes and users) or a Sun Solaris™ server (for small-to-large numbers of nodes and users). The maximums specified represent the estimated number of users for acceptable response time. The TransNav Management System does not restrict the number of simultaneous users either by software licensing or system configuration parameters. Customer usage patterns may allow more simultaneous users with reasonable response time than specified. The TransNav Management System supports: Five (5) simultaneous client user interface sessions for Microsoft Windows 2000

Professional servers. Fifteen (15) simultaneous client user interface sessions for a minimum Sun Solaris

server configuration. Greater number of simultaneous Sun Solaris server-based client user session can be supported. The maximum depends upon TransNav Sun Solaris server capacity and/or number of servers, and is scalable with additional server equipment.

One GUI session or domain-level CLI session counts as a simultaneous user.


Chapter 1 TransNav Management System OverviewReliability, Availability and Serviceability (RAS)

Scalability Turin will work with customers to specify configurations to support the scalability required. The TransNav Management System supports: 15 to 25 Traverse nodes for Windows 2000 Professional servers. Any quantity of Traverse nodes and simultaneous users for Sun Solaris servers by:

– Selecting a multi-processor Sun Solaris server with the potential capacity to support the estimated maximum requirements; and the addition of CPUs, memory and disk capacity as needed.

– Distributing various components of the management system over multiple Sun Solaris servers.

Reliability, Availability and Serviceability (RAS)

Turin works closely with customers to configure hardware and software to achieve desired levels of high availability for their Sun Solaris server-based TransNav system deployments. This includes supporting secondary network operation centers for disaster recovery. Our goal is to achieve exceptional service reliability and availability in a cost-effective manner.


Volume 1, Section 3: Management System OverviewReliability, Availability and Serviceability (RAS)



Chapter 2Network Management Features

Introduction The TransNav Management System provides classical element management functionality (FCAPS—fault, configuration, accounting, performance, and security), plus policy management, reporting, and system administration. Fault and Event Management, page 3-7. Configuration Management, page 3-8. Accounting Management, page 3-9. Performance Management, page 3-9. Security Management, page 3-9. Node Administration, page 3-10. System Log Collection and Storage, page 3-10. Report Generation, page 3-11.

Fault and Event Management

The TransNav Management System GUI enables each technician to open multiple alarm windows. The number of windows is limited only by effective use of the workstation’s screen area and the client workstation system resources such as memory and CPU load.

In the GUI, windows and dialog boxes have the following characteristics:

Alarm Data. The system provides a count of the number of outstanding alarms by severity level. This information is available on at a network level as well as and for each individual node.

Data Sequence. Each user can specify the sequence in which data fields will appear for each window.

Flexible Filtering. The user can determine what data appears in the selected fields for each separate alarm window.

Flexible Scoping. The user can determine which nodes and equipment appear in the selected fields for each separate alarm window.

Sorting. By selecting a column heading, e.g., “severity,” the alarm window is sorted by that category.

Clearing Alarms. Only a node clears alarms. Alarms received by the management system are automatically marked as cleared and added to the display. The user can also


Volume 1, Section 3: Management System OverviewConfiguration Management

set the retention duration of cleared alarm messages in the server alarm database and the alarm display.

Graphical buttons and a context menu provide the following options: Acknowledge the alarm. Select a detailed alarm view that allows the user to view alarm details in addition to

adding comments. Set filters that allow the user to include or exclude alarms from specific sources

from being displayed in the Alarm window. Open a new alarm window.

Configuration Management

Use the TransNav Management System for all configuration management requirements: Equipment Configuration, page 3-8. Preprovisioning, page 3-8. Service Provisioning, page 3-9.

Equipment Configuration

Once a node is installed and activated, it discovers its specific components and forwards that information to the management system, which in turn populates its databases and builds the graphical representation of the equipment. The Intelligent Control Plane automatically discovers the network and forwards that information to the management plane, which creates the network topology map.

The node-level CLI is used for initial system configuration. For detailed information, see Volume 2, Installation and Configuration.

The TransNav Management System supports Telcordia CLEI™ (Common Language® Equipment Identifier codes) codes per GR-485-CORE. These are encoded on individual modules.

Preprovisioning The TransNav Management System supports complete preprovisioning of all nodes. Preprovisioning facilitates rapid turn-up of new nodes and node expansions as well as support for planning and equipment capital control. Preprovisioning of customer services enables the service provider to efficiently schedule provisioning work independent of service activation.

The management system stores the parameters of the service request and sends them to the Intelligent Control Plane upon activation. If the management system is unable to complete activation, it provides appropriate alarms including insight into the nature of the inability to complete provisioning and activation of the service. The effectiveness of preprovisioning depends upon effective traffic engineering to ensure that network capacity is available upon activation.


Chapter 2 Network Management FeaturesSecurity Management

Service Provisioning

The TransNav Management System provides end-to-end provisioning of services and requires minimal input from the user. Alternatively, the user can set the constraints (each hop and time slot) of a service. You can provision a service using any of the following methods: Graphical user interface. Script language (typical for batch provisioning). Domain-level CLI interface

Support for automated flow-through provisioning by the TransNav Management System is planned for a future release.

Accounting Management

Accounting data for all services is based primarily on performance management data and transmitted from the nodes to the management system.

Using this data, the service provider can track service levels and ensure that traffic complies with service level agreements (SLAs). SLA monitoring enables the service provider to create a billing opportunity and to charge a premium for the guaranteed level of service.

Performance Management

Nodes collect performance management data and forward it to the management server to store in the database. The data is processed in two ways: The service provider’s management system administrator can set threshold

crossing alert thresholds. The threshold crossing alert appears as an event in on the GUI Events tab.

The TransNav Management System provides basic reports and can export the data for analysis and graphical presentation by applications such as Microsoft® Excel. In a future release, the management system will provide an interface to Clear Communications Corporation Clearview® solution for more extensive real-time SLA management.

Security Management

Security management refers to the establishment of management user accounts with specific access privileges and tracking of account activity so that potential breaches of security can be detected.

Access control on the TransNav Management System is through use of access groups. The management system has several pre-defined access groups. Any user can be in one or more access groups. Access is cumulative; a user who is in two access groups has the privileges of both access groups. Security applies to both the GUI and CLI. Access groups and rights are defined in the following table.Table 3-1 Access Groups and Rights

Access Group Allowable Operations

Admin Provision and view everything.

Equipment Config Configure and view all node, module, port, and control plane parameters.

Service Config Provision and view all services.

User Management Configure and view all user account data and security logs.


Volume 1, Section 3: Management System OverviewNode Administration

Node Administration

The TransNav Management System provides the following capabilities to support efficient remote administration of nodes: Software management and administration. Synchronization of the node and management system databases.

The management system database is a super set of each node’s database and eliminates the need for remote backup and restore of the node itself. The database on each node is synchronized with the management server database, based on user-defined policies.

Equipment alarm and event history analysis. Remote restore of the database on the node for disaster recovery in the event of:

– A failure of both General Control Modules, or a major central office (CO) catastrophe.

– Some major, unpredictable service provider network failure that creates uncertainty about the general state of node databases.

The TransNav Management System has a local persistent database on the fault-protected general control modules (GCM) that protects against a single GCM failure. A major advantage of the Intelligent Control Plane automatic mesh service set-up and restoration mechanism is to maintain service connectivity.

System Log Collection and Storage

The TransNav Management System collects a broad array of information that is stored in the server database for reporting and analysis.

The following is a representative list of data that can be extracted from the server database: All user actions from the domain-level GUI or CLI or through the node-level CLI. Alarm and event history including performance management threshold crossing

alerts.– Equipment configuration history.– Node equipment alarm log.

Security logs.– User list denoting each user’s profile.– Sign-on/sign-off log.– Failed log-on attempts.

Performance management data.

Fault Provision alarm severities; view alarm and event logs.

Report Create, schedule, and view reports.

View View everything.

Table 3-1 Access Groups and Rights (continued)

Access Group Allowable Operations


Chapter 2 Network Management FeaturesReport Generation

Report Generation

All reports can be printed or exported as text-formatted comma delimited files.

General Reports. The TransNav Management System allows a set of pre-defined reports to be either scheduled or executed on demand. These reports encompass such functions as: Equipment inventory. Historical alarms. Historical events. Performance monitoring/management. Resource availability. Service availability. Domain service.

Reports can be set to be run once, hourly, daily, weekly, and monthly.

Data Set Snapshots. The TransNav Management System also provides a simple form of reporting that produces a file based on a set of information that is currently displayed in the GUI. For example, the GUI displays active alarms in a dialog box. The set of active alarms is a data set; the windowing capability of the GUI presents as much of this data set as possible in the display’s dialog box, allowing the user to scroll to view more of the data set. The management system allows the user to print, or save to a file, any data that the system can display in a dialog box. (Note: This is different from the “screen capture” function of the client workstation’s operating system, which captures only as much of the data set that is actually visible in the dialog box.)


Volume 1, Section 3: Management System OverviewReport Generation



Chapter 3User Interfaces

Introduction You can access the TransNav Management System using a graphical user interface (GUI) or a command line interface (CLI). See Graphical User Interface, page 3-14 for a description of the GUI. See Command Line Interface, page 3-16 for a description of the CLI.

TransNav System Access Methods

The following table lists the different access methods you can use to connect to the TransNav management server.

Table 3-2 Accessing the TransNav Management System

Management System Interface Access Method

Domain-level GUI Installed client application (recommended). Applet from web browser interface. Local connection to node and remote connection

(DCC bytes) to management server.

Domain-level CLI Telnet to management server. Local connection to node and remote login to

management server.

Node-level CLI Local connection to node. Local connection to node and remote login to a

different node in the domain.


Volume 1, Section 3: Management System OverviewGraphical User Interface

Graphical User Interface

The GUI supports operators and administrators who are located in a network operations center or in a remote location. It allows them to perform a wide range of provisioning and monitoring tasks for either a single node or a domain (network) of many nodes.

There are two main views in the GUI: Map View, page 3-14. Shelf View, page 3-15.

Map View The Map View displays all the nodes in one Traverse domain. Map View displays when you first start the GUI. From Map View, you can see and manage all the nodes in a network domain, the links between the nodes, and network services.

The graphic area displays a background image (usually a map of physical locations of the nodes) and icons that represent each node in your network.

Figure 3-2 Map View

The menu bar is context-sensitive. Commands are displayed as available (highlighted) or unavailable (dimmed) depending on the selected object.You can see which object you have selected by the white rectangle around the object in the graphic and the name displayed on the top and bottom bars of the window.The Context-sensitive tabs provide domain or node information on alarms, events, configuration information, protection, and services. Click a node to display node-specific information. Click anywhere on the map to display domain-specific information.

Menu bar

Currently selected object

Contextsensitive tabs


Chapter 3 User InterfacesShelf View

Shelf View Shelf View displays all the cards in a node and their associated ports. You can navigate to Shelf View in three ways: Select Show Shelf View from the View menu. Double-click the node in Map View. Right-click a node in Map View and select Show Shelf View.

Figure 3-3 Shelf View

The menu bar is context-sensitive. Commands are displayed as available (highlighted) or unavailable (dimmed) depending on the selected object.

You can see which object you have selected by the white rectangle around the object in the graphic and the name displayed on the top and bottom bars of the window.

Context-sensitive tabs (in the bottom half of the screen) which provide information on alarms, events, configuration information, protection, and services. In Shelf View, these tabs provide single node, card or port information. Click a card to display card-specific information. Click a port to display port-specific information. Click a BITS clock to display timing BITS timing information.

Currently selected object

Menu bar

BITS clock

Contextsensitive tabs


Volume 1, Section 3: Management System OverviewCommand Line Interface

Command Line Interface

You can also access the TransNav Management System using a command line interface (CLI). The CLI is intuitive, easy to learn, and easy to use. The hierarchical command mode is also a similar concept found within the industry.

The CLI has the following features: Command line editing: use backspace and cursor keys to edit the current line, and

to call up previous lines for re-editing and re-submission. Hierarchical command modes: organization of commands into modes with

increasingly narrow problem domain scope. Context-sensitive help: request a list of commands for the current context and

arguments for the current command, with brief explanations of each command. Command completion: enter a command or argument’s left most substring and

view a list of possible allowable completions. Abbreviate any command or argument to its left most unique substring (for many commands, one character).

Context-sensitive prompt: the prompt for each command displays the current command mode.

You can access a single node (node-level) or a network (domain-level) of nodes using the command line interface.

See Section 7—CLI User’s Guide, page 7-1 for a detailed information on the command line interface.

Domain Level Use domain-level commands to perform network commissioning, provisioning, and monitoring tasks. Domain-level commands affect multiple nodes in a network and include: Setting the gateway node. Configuring network links. Creating performance monitoring templates and alarm profiles. Creating protection rings and services. Generating reports.

Accessing the domain-level CLI automatically gives you access to the node-level CLI.

Node Level Use node-level CLI commands to perform commissioning, provisioning, or monitoring tasks on a any node on the network. Node-level commands affect only one node and include configuring protection groups, equipment, interfaces, timing, and performing software upgrades.



Chapter 4Management System Requirements

TransNav Management System Requirements

The TransNav Management System CD software package contains both server and client workstation applications. The server functions communicate with the nodes and maintain a database of topology, configuration, fault, and performance data for all nodes in the network. The client workstation application provides the user interface for managing the network.

All of the nodes in a service provider’s network are contained in multiple Control Plane Domains with a maximum of one hundred nodes per domain. One TransNav management server can manage multiple Control Plane domains.

Use the requirements listed in the following sections to help you determine the management system requirements for your network. TransNav Management Server Hardware Requirements, page 3-18. TransNav Management Server Software Requirements, page 3-21. TransNav Client Workstation Hardware Requirements, page 3-22. TransNav GUI Software Requirements, page 3-23.


Volume 1, Section 3: Management System OverviewTransNav Management Server Hardware Requirements

TransNav Management Server Hardware Requirements

Use the information in this section to help determine TransNav Management System server hardware requirements for your network. You can operate a management server using either a Sun Solaris platform or a Windows 2000 Professional platform. Sun Solaris Server, page 3-18. Windows 2000 Professional Server, page 3-19.

Sun Solaris Server

TransNav system server software is supported on the following desktop server supporting XWindows for running the client workstation application:

The following two tables recommend TransNav server hardware configurations for supporting up to 50 nodes and up to 100 nodes. Table 3-3 Server Hardware Recommendations to Support up to 50 Nodes,

page 3-18. Table 3-4 Server Hardware Recommendations to Support up to 100 Nodes,

page 3-19.

Table 3-3 Server Hardware Recommendations to Support up to 50 Nodes

Component Description

Server SunFire 280R

CPU Two UltraSPARC III processors (1.2 GHz)

Memory (RAM) 2 GB

Hard Drives 36 GB of hard disk space (RAID controller optional; more disk space if hot-spare is desired or if more storage is desired for log files)

CD-ROM Drive Internal or External

Backup System Internal is optional, SAN (Storage Area Network) is recommended

Network Two 10/100Base-T Ethernet cards. One card connects to the Data Communications Network (DCN) and the other card connects to the Local Area Network (LAN) connecting the client workstations.


Chapter 4 Management System RequirementsWindows 2000 Professional Server

Windows 2000 Professional Server

Use Windows 2000 Professional server for smaller networks (15 or fewer nodes) and 5 or fewer simultaneous users. Table 3-5 provides hardware configuration requirements for the Windows 2000 Professional operating environment.

Table 3-4 Server Hardware Recommendations to Support up to 100 Nodes


Server SunFire 280R

CPU Two UltraSPARC III processors (1.2 GHz)

Memory (RAM) 4 GB

Hard Drives 72 GB of hard disk space (RAID controller optional; more disk space if hot-spare is desired or if more storage is desired for log files)

CD-ROM Drive Internal or External

Backup System Internal is optional, SAN (Storage Area Network) is recommended

Network Two 10/100Base-T Ethernet cards. One card connects to the Data Communications Network (DCN) and the other card connects to the Local Area Network (LAN) connecting the client workstations.

Table 3-5 Server Hardware Requirements for Windows 2000 Professional


CPU Intel Celeron 1.7 GHz processor or better (Celeron or P4) i845E chipset, with 400 MHz front side bus.

Memory (RAM) 1 GB recommended, PC133 or better.

Hard Drives Minimum 60 GB, ATA-100 7,200 rpm. (SCSI 10,000 rpm drive optional).

CD-ROM Drive Internal or external.

Monitor Server only: High resolution 15-inch.(1024 x 768).Server and client: High resolution 21-inch (1280 x 1024).


Volume 1, Section 3: Management System OverviewWindows 2000 Professional Server

Disk Backup System

Required if not able to backup TransNav database to server on the network.

Network One or two 10/100BaseT Ethernet cards. One Ethernet Network Interface Card (NIC) connects to the Data Communications Network (DCN). The second optional Ethernet NIC connects to the Local Area Network (LAN) connecting the client workstations.

Table 3-5 Server Hardware Requirements for Windows 2000 Professional



Chapter 4 Management System RequirementsTransNav Management Server Software Requirements

TransNav Management Server Software Requirements

Use the information in this section to determine the management server software requirements for your network. You can operate the management using either of the following operating environments: Sun Solaris platform (Table 3-6)—larger networks (more than 15 nodes), more

than 5 simultaneous users. Windows 2000 professional platform (Table 3-7)—smaller networks (15 nodes or

less), 5 or fewer simultaneous users.

Table 3-6 Server Software Requirements for Sun Solaris


Operating Environment

Sun Solaris 8. Solaris 8 recommended patch cluster: Generic_108528-15

or later (July, 29, 2002). Bash shell.

Server Software Latest version of the TransNav software provided by Turin Networks, Inc., Customer Service.

PDF Viewer Adobe® Acrobat® Reader® versions 3, 4, or 5. Download the application for free from Adobe’s site at: www.adobe.com/products/acrobat.

Table 3-7 Server Software Requirements for Windows 2000 Professional



Windows 2000 Professional Service Pack 2.

Server Software Latest version of the TransNav software provided by Turin Networks, Inc., Customer Service.

PDF Viewer Adobe Acrobat Reader versions 3, 4, or 5. Download the application for free from Adobe’s site at: www.adobe.com/products/acrobat.


http://www.adobe.com/products/acrobat


Volume 1, Section 3: Management System OverviewTransNav Client Workstation Hardware Requirements

TransNav Client Workstation Hardware Requirements

To access the TransNav management server from the graphical user interface (GUI), you require a client workstation. Access the GUI by installing the application directly on the client workstation or through a Web browser using an applet.

Turin recommends installing the application directly on the client workstation for faster initialization, operation and response time.

The GUI application and applet are supported on Windows NT®, Windows® 2000, Windows 2000 Professional, and Sun SPARC® machines with the minimum configurations listed in Table 3-8.

Table 3-8 Minimum Requirements for Client Hardware


CPU Sun SPARC (Solaris version independent) workstation1.or

Windows PC capable of running Windows NT, Windows 2000 or Windows 2000 Professional2.

1 The GUI has not been implemented on the Sun i386 or Intel-based LINUX configurations.

2 The client application and GUI applet have not been tested on Windows 98 or Windows XP. Successful operation is not guaranteed with these operating systems.

Memory (RAM) 512 MB or greater for fastest response time with multiple applications open.

256 MB minimum for fastest response time (assumes that at least 75 MB of free memory is available for the TransNav GUI).

128 MB minimum (assumes that no other applications are open and fast response time is not required). Significant disk swapping will occur.

Hard Drive Space 500 MB minimum, 1 GB recommended.

Monitor High resolution 21-inch (1280 x 1024) monitor or high resolution laptop.

CD-ROM Drive Internal or External.

Network One 10/100BaseT Ethernet Card.


Chapter 4 Management System RequirementsTransNav GUI Software Requirements

TransNav GUI Software Requirements

The following table lists the software required to install the GUI application on either the Sun Solaris, Microsoft Windows NT, or Windows 2000 operating environments.

Table 3-9 Minimum Requirements for GUI Software



Any of the following operating environments: Sun Solaris 7 or Sun Solaris 8. Microsoft Windows NT v4 Service Pack 6. Microsoft Windows 2000. Microsoft Windows 2000 Professional Service Pack 2.

Web Browsers for applet

Microsoft Internet Explorer v5.5 or later.or

Netscape® Navigator® v4.7 or later.

Each with Sun JDK plug-in v1.3 or later (download from www.sun.com).

PDF Viewer Adobe Acrobat Reader versions 3, 4, or 5. Download the application for free from Adobe’s site at: www.adobe.com/products/acrobat


http://www.sun.com


Volume 1, Section 3: Management System OverviewTransNav GUI Software Requirements


SECTION 4 PLANNING AND ENGINEERINGSECTION 2PLANNING AND ENGINEERING

SECTION 2

Contents

Chapter 1Traverse Specifications

Traverse Shelf Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1Module Placement Guidelines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2Traverse Dimensions Summary Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4Traverse Rack Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5Fan Tray with Integrated Air Ramp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7Power Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7Power Distribution and Alarm Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8Power Cabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9Power Consumption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10

General Control Modules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10SONET/SDH Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10Electrical Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11Ethernet Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11Shelf Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11

Fiber Optic Module Cabling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12Electrical Coax and Copper Module Cabling. . . . . . . . . . . . . . . . . . . . . . . . . . 4-12Traverse Interface Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13Fiber Connector Shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14Shelf and Rack Density . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14Regulatory Compliance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15

Chapter 2Network Cabling using Electrical Connector Modules

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-17ECM Placement at the Traverse Main Backplane. . . . . . . . . . . . . . . . . . . . . . 4-18ECM and Module Placement Planning Guidelines . . . . . . . . . . . . . . . . . . . . . 4-19Electrical Connection Module Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-20Cable Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21


Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-23Power Distribution Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-23Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-24Integration with Traverse System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-24Interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-25Environmental . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-25


Volume 1 Section 4 Planning and Engineering

Relay Contacts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-25

List of FiguresFigure 4-1 Traverse 2000 Shelf Front View . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1Figure 4-2 Traverse Mounting Heights Using PDAP-2S in a 23-Inch Rack . . 4-5Figure 4-3 Four Traverse 1600 Shelves and the PDAP-4S in a

Single Rack Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6Figure 4-4 PDAP-2S Power Cabling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9Figure 4-5 PDAP-4S Power Cabling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9Figure 4-6 Electrical Connector Modules (Front View) . . . . . . . . . . . . . . . . . . 4-17Figure 4-7 2-Slot ECM Placement—Traverse 2000 Main Backplane . . . . . . 4-18Figure 4-8 Traverse Shelf with Cable Management Bar . . . . . . . . . . . . . . . . . 4-21Figure 4-9 TransAccess 100 Mux Shelf Interconnection to Traverse Shelf . . 4-24

List of TablesTable 4-1 Module Placement Guidelines. . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2Table 4-2 Redundancy Rules for GCM Types. . . . . . . . . . . . . . . . . . . . . . . . 4-3Table 4-3 Traverse Component Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . 4-4Table 4-4 Power Distribution Per Traverse Module . . . . . . . . . . . . . . . . . . . . 4-10Table 4-5 Traverse Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13Table 4-6 Traverse Interface Options and Maximum Densities. . . . . . . . . . . 4-14Table 4-7 Regulatory Compliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15Table 4-8 Electrical Connector Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-20Table 4-9 TransAccess 100 Mux Dimensions . . . . . . . . . . . . . . . . . . . . . . . . 4-23Table 4-10 TransAccess 100 Mux Power Specifications. . . . . . . . . . . . . . . . . 4-24Table 4-11 TransAccess 100 Mux Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . 4-25Table 4-12 TransAccess 100 Mux Environmental Specifications . . . . . . . . . . 4-25Table 4-13 TransAccess 100 Mux Relay Contact Closure Ratings. . . . . . . . . 4-25


SECTION 4PLANNING AND ENGINEERING

Chapter 1Traverse Specifications

Traverse Shelf Configuration

Traverse systems consist of General Control Modules (GCMs), VT/VC switch modules, and Service Interface Modules (SIMs) that mount in the 16-slot Traverse 1600 shelf or 20-slot Traverse 2000 shelf. A summary table of shelf dimensions are provided in Table 4-3 on page 4-5.

Figure 4-1 Traverse 2000 Shelf Front View

Traverse systems are configured by populating the shelves with GCMs, SIMs, and VT/VC Switch modules. A minimum shelf configuration consists of one GCM and one SIM. Module guide rails are built into the shelves to allow for easy insertion of the modules into connectors mounted on the backplane.

P1 P1


Volume 1, Section 4: Planning and EngineeringModule Placement Guidelines

t

e

ts

ce he

s.

ot o

Module Placement Guidelines

The following table provides guidelines for placement of modules in a Traverse shelf:

Table 4-1 Module Placement Guidelines

Module TypeTraverse

1600 Slot #s

Traverse 2000

Slot #sComments

GCM,Enhanced GCM (EGCM),GCM OC-12/STM-4,GCM OC-48/STM-16

GCMA and GCMB

(slots 15 and 16)

GCMA and GCMB

(slots 19 and 20)

Redundant GCMs are recommended for equipment protection. However, if only one GCM is used it can be placed in either sloGCMA or GCMB.

Redundant GCMs can be different types. See Table 4-2 Redundancy Rules for GCM Types below.

DS1, DS3/E3/EC-1 CC (12-port),DS3/E3/EC-1 CC (24-port),DS3/EC-1 TMUXE1

1–12 1–16 In a 1:1 equipment protection scheme1, the module to the left protects the right-adjacent working module. In an unprotected scheme, place modules in any valid slot; the 2-slot DS3/E3 electrical connector module (ECM) provides access to only the right-most DS3/E3/EC-1 module so place an optic module in thleft-most slot.

In a 1:2 equipment protection scheme, the center module protecthe left- and right-adjacent working modules. In an unprotected scheme, place modules in any valid slot; the 3-slot DS3/E3 ECMprovides access to only the left- and right-most DS3/E3/EC-1 modules so place an optic module in the center slot.

10/100BaseTX,GbE LX plus10/100BaseTX Combo,GbE SX plus10/100BaseTX Combo

1–12 1–16 Use the following module placement options when placing any 10/100BaseTX-inclusive modules in a Traverse shelf with DS1,DS3/E3/EC-1 CC, DS3/EC-1 TMUX, or E1 modules: Place an OC-N/STM-N module or place a 1-slot wide blank

faceplate between the 10/100BaseTX and an electrical interfamodule, if the 10/100BaseTX-inclusive module is placed to tright of the electrical interface module.or

Place 10/100BaseTX-inclusive modules directly to the left ofDS1, DS3/EC-1/EC-1 CC, or DS3/EC-1 TMUX or E1 moduleAn OC-N/STM-N module or 1-slot wide blank faceplate is nrequired if the 10/100BaseTX-inclusive modules are placed tthe left of electrical interface modules.

GbE LX,GbE LX plus 100BaseFX Combo,OC-3/STM-1,OC-12/STM-4,OC-48/STM-16,

1–14 1–18 None.


Chapter 1 Traverse SpecificationsModule Placement Guidelines

on .

e

The following module placement scheme is recommended but not required: Place DS1, DS3/E3/EC-1 CC, DS3/EC-1 TMUX, and 10/100BaseTX (see

important note above for 10/100BaseTX placement) modules from the left-most slots (beginning with slots 1 and 2) and work towards the center of the shelf as required up to Traverse 1600 slot 12, or Traverse 2000 slot 16.

Place VT Switch 2688 modules next to the GCM modules, place additional modules toward the center of the shelf as required.

Place OC-N and GbE modules (optical modules) beginning in the right-most available slot (starting at Traverse 1600 slot 14 or Traverse 2000 slot 18), place additional modules towards the center of the shelf as required.

The following table shows the redundancy rules for all GCM types:

OC-192/STM-64 1/2, 3/4, 5/6, 7/8, 9/10, 11/12, and

13/14

1/2, 3/4, 5/6, 7/8, 9/10,

11/12, 13/14, 15/16, and

17/18

The OC-192/STM-64 modules require two slots for placement. The left side of the OC-192/STM-64 module is placed in an oddnumbered slot.

VT Switch (2688) 1–14 1–18 In a 1:1 equipment protection scheme, the working and protectiVT Switch 2688 modules must be placed adjacently in the shelf

1 Refer to pre-Release 1.3 Traverse system documentation for placement restrictions with respect to the superseded Traverse backplandesign supporting only 1:1 protection schemes.

Table 4-1 Module Placement Guidelines (continued)

Module TypeTraverse

1600 Slot #s

Traverse 2000

Slot #sComments

Important: Place an OC-N or 1-slot wide blank faceplate between any 10/100BaseTX-inclusive module and an electrical module (DS1, DS3/E3/EC-1 CC, or DS3/EC-1 TMUX module), if the 10/100BaseTX-inclusive module is placed to the right of an electrical interface module. A blank faceplate or OC-N module is not required if the 10/100BaseTX-inclusive module is placed to the left of an electrical module.

Important: 1-slot wide blank faceplates must be placed in any empty slots to ensure EMI protection and proper cooling.

Table 4-2 Redundancy Rules for GCM Types

Active GCM Standby GCM

GCM GCM

GCM EGCM1


Volume 1, Section 4: Planning and EngineeringModule Placement Guidelines

Please refer to Volume 2, Installation and Configuration, Section 6—Start-up and Module Placement, Chapter 2—“Module Placement” for additional information.

EGCM1 GCM

EGCM EGCM

GCM OC-N/STM-N2 GCM OC-N/STM-N2

1 EGCM environmental alarm function should not be used in this redundancy combination.

2 Traverse supports in-service upgrade from a node running R1.2 (or greater) software with two regular GCM modules to a node running R1.4 software with two GCM OC-N/STM-N modules.

Table 4-2 Redundancy Rules for GCM Types

Active GCM Standby GCM


Chapter 1 Traverse SpecificationsTraverse Dimensions Summary Table

Traverse Dimensions Summary Table

The following table gives the dimensions for the Traverse components.

Table 4-3 Traverse Component Dimensions

Assembly Height Width Depth WeightEmpty

WeightFully

Loaded

Traverse 20001

1 Height includes fan tray and depth includes cable covers.

18.25 in 21.14 in 13.75 in. 16 lb 63 lb

46.34 cm 53.7 cm 34.93 cm 7.2 kg 28.58 kg

Traverse 16001

18.25 in. 17.25 in. 13.75 in 15 lb 52 lb

46.34 cm 43.82 cm 34.93 cm 6.8 kg 23.59 kg

Traverse 600

6.50 in. 17.25 in. 13.75 in 8 lb 21 lb

16.51 cm 43.82 cm 34.93 cm 3.63 kg 9.525 kg

Fan Tray (for Traverse 2000 and Traverse 1600)

3.5 in 21.142

17.253

2 Traverse 2000.

3 Traverse 1600.

12.25 in — 7 lb2

5 lb3

8.75 cm 53.7 cm2

43.82 cm331.12 cm — 3.180 kg2

2.27 kg3

PDAP 2 in 17 in 16 in — 12 lb

5.08 cm 43.18 cm 40.64 cm — 5.4431 kg


Volume 1, Section 4: Planning and EngineeringTraverse Rack Configuration

Traverse Rack Configuration

The Traverse 1600 shelf can be installed in either a standard 19-inch or 23-inch wide relay rack1. The Traverse 2000 shelf must be installed in a standard 23-inch wide relay rack.

Figure 4-2 shows the mounting heights for installing two Traverse 1600 or Traverse 2000 shelves with fan trays and air ramps, plus the Power Distribution and Alarm Panel (PDAP-2S2) in a 23-inch wide rack. To provide proper air flow, 3/8-inch of space is required between the PDAP and the first (top most) Traverse shelf assembly.

Figure 4-2 Traverse Mounting Heights Using PDAP-2S in a 23-Inch Rack

1 Mounting brackets are provided for installing the Traverse 1600 shelf in a 23-inch wide rack.

2 The PDAP-2S supports up to two Traverse shelves in a relay rack. The PDAP-4S distributes power to up to four Traverse 1600 or Traverse 2000 shelves in a in a single 7-foot high rack.

17.75 inches fromtop of Shelf #2 tobottom of fan trayfor Shelf #2

SD

82.00 PDAP-2S (top)

62 inches Shelf #2 (top)

Fan Tray withintegrated air ramp62.375 inches (bottom)

Notes:1. Pre-install shelf mounting screwsin locations shown to takeadvantage of keyhole slots to aidinstallation.2. Leave about 1/4 inch clearancebetween rack and head of mountingscrews.3. Install shelves from bottom up.Lowest unit in rack should beinstalled first.4. This configuration requiresapproximately 23 rack units ofusable space in the rack. (1 RackUnit = 1.75 inches.)5. The PDAP-2S must be placed inthe top of the rack. The PDAP-2Suses the first set of mounting holesfor installation. The top most 20-slot shelf assembly goes directlyunder the PDAP-2S. There shouldbe a slight gap between the twounits of about 3/8".6. The fan tray with integrated airramp mounts directly under the 20-slot shelf assembly. There shouldbe no gap between the shelfassembly and the fan tray.Note: An air ramp is not needed forthe bottom-most shelf (#2) in theexample configuration.

17.75 inches fromtop of Shelf #1 tobottom of fan trayfor Shelf #1

80.00 PDAP-2S bottom)

Fan Tray withintegrated air ramp44.75 inches (bottom)

79.625 inches Shelf #1 (top)


Chapter 1 Traverse SpecificationsTraverse Rack Configuration

Figure 4-3 shows an example of four Traverse 1600 shelves installed with the PDAP-4S in a 19-inch wide relay rack.

Figure 4-3 Four Traverse 1600 Shelves and the PDAP-4Sin a Single Rack Configuration

SD

P1P1

P1P1

P1P1

P1P1

PDAP-4S

Traverse 1600

Fan Tray withintegrated air ramp

Traverse 1600

Traverse 1600

Traverse 1600





Volume 1, Section 4: Planning and EngineeringFan Tray with Integrated Air Ramp

Fan Tray with Integrated Air Ramp

The Traverse fan tray with fan modules cools the GCM and service modules in the shelf. The fan tray draws in cooling air from the front and pushes the air upward through the perforated shelf. The integrated air ramp on the shelf above directs the heated air through to the rear of the shelf.

One fan tray is installed per Traverse 1600 or Traverse 2000. The fan tray is installed directly below the Traverse 1600 or Traverse 2000 shelf. The fan tray includes circuitry that allows it to report events and alarms to the General Control Module. If a fan fails to operate, an alarm is sent to the GCM and the system will increase the speed of the other fans. In addition, the system will increase fan speed when temperature levels are detected that exceed the factory-set threshold.

For a detailed description and specifications of the fan tray, see Section 2—Hardware Descriptions, Chapter 1—“Traverse Platforms,” Fan Tray with Fan Module and Air Ramp, page 2-14.

Power Requirements

There are two different PDAPs3 available with the Traverse system, the PDAP-2S and PDAP-4S. The PDAP-2S supports up to two and the PDAP-4S supports up to four Traverse shelves and is used with the Traverse 1600 or Traverse 2000 system.

PDAP receives redundant –48 VDC nominal central office (CO) power, and distributes redundant power to the Traverse 1600 or Traverse 2000 shelves.

The Traverse shelf can receive two (redundant) power feeds to the chassis. The Traverse operates between -42.5 VDC to -70 VDC.

The power requirement is a function of the number of modules in a Traverse shelf. Each module requires approximately 42 watts for the DS3/EC-1 module to 90 watts for the double-width OC-192/STM-64 module. The maximum power consumption of a typical Traverse 1600 or Traverse 2000 system (equipped with OC-N/STM-N and Ethernet service interface modules, redundant GCMs, and fan tray) is approximately 900 to 1100 watts.

Each module has an on-board power supply and converter. The power supply on each module includes a soft start circuit to limit in-rush current, voltage filter, and fuse to protect it from potential DC transients. When unacceptable power input is detected, the module automatically shuts down.

All power and interface connections are terminated from the rear of the Traverse shelf, except for the serial interface and the Ethernet port (for local craft access), which are on the front faceplate of the GCM.

PDAP Temperature/Humidity – Operating

–5°C to +55°C/90% Relative Humidity @+28°C

PDAP Temperature/Humidity – Storage–40°C to +70°C/95% Relative Humidity @+40°C

3 PDAP refers to both the PDAP-2S and PDAP-4S, unless specified otherwise.


Chapter 1 Traverse SpecificationsPower Distribution and Alarm Panel

Power Distribution and Alarm Panel

The PDAP-2S can be installed in a 19 or 23-inch wide telco rack. It is 2 inches high, 17 inches wide, and 16 inches deep. It weighs 12 pounds. It provides circuit breakers for up to two Traverse shelves and GMT fuses for auxiliary equipment. The PDAP-4S can be installed in a 19 or 23-inch telco rack. It is 1.75 inches high, 17.25 inches wide, and 10 inches deep. It weighs 14 pounds. It provides TPA fuses for up to four Traverse shelves and GMT fuses for auxiliary equipment.

Redundant power input (A and B) and return cables enter from the back of the PDAP. The A and B input feed provide power protection for Traverse shelves and auxiliary equipment. The PDAP-2S provides redundant, field replaceable 40 ampere (amp) circuit breakers4 for up to two Traverse shelves and GMT fuses (from 0.25 amps to 10 amps per fuse) for up to 10 pieces of auxiliary equipment. The PDAP-4S provides redundant, field replaceable 40 amp TPA fuses4 for up to four Traverse shelves and GMT fuses (from 0.25 amps to 15 amps per fuse) for up to 5 pieces of auxiliary equipment. The PDAP’s field replaceable circuit breakers and fuses are accessible without having to remove the front panel.

Note: Audible and visual critical, major, minor, and remote alarm output contacts are terminated at the Traverse main backplane. Environmental alarm inputs and outputs are also terminated at the Traverse main backplane. An optional Environmental Alarm Module (EAM) is required to support environmental input and output signals.

4 Optional PDAP-2S circuit breakers and PDAP-4S TPA fuses are available up to a 50 amp maximum.


Volume 1, Section 4: Planning and EngineeringPower Cabling

Power Cabling Redundant central office battery and battery return is connected to the PDAP. The PDAP-2S distributes battery and battery return to up to two Traverse shelves and up to ten pieces of auxiliary equipment in a rack. The PDAP-4S distributes battery and battery return to up to four Traverse shelves and up to five pieces of auxiliary equipment in a rack.

Both the PDAP-2S and PDAP-4S have two DC power inputs (Battery ‘A’ and Battery ‘B’). Each of these inputs is capable of supplying power to the Traverse system during central office maintenance operations. The recommended gauge wire for power cabling is #8 AWG.

Figure 4-4 PDAP-2S Power Cabling

Figure 4-5 PDAP-4S Power Cabling

Please refer to Volume 2, Installation and Configuration, for detailed instructions for power cabling.

Battery “A” DistributionBattery “B” Distribution Battery and Battery Return Bus Bars

TPA

PAT

GMT GMT

Battery and Battery Return “A” Supply

Battery and Battery Return “B” Supply

Battery and Battery Return Distribution Terminal Blocks

Chassis GroundChassis Ground


Chapter 1 Traverse SpecificationsPower Consumption

Power Consumption

The power draw of the Traverse system is dependent on the configuration of each system. From a base configuration consisting of the chassis and a fan tray, the addition of each module increases the power draw of the system.

A typical single shelf configuration consume from 745W to 915W. Fully equipped configurations are normally less than 1000 watts. All Traverse modules operate between –42.5 and –70 VDC.

The table below provides power information for General Control Modules, Service Interface Modules, the VT/VC Switch modules, fan tray, and PDAP.

Table 4-4 Power Distribution Per Traverse Module

Interface Module or Component Type Watts Per Module / Component

General Control Modules

General Control Module (GCM) 35

Enhanced GCM 40

GCM with 1-port OC-12/STM-4 IR1 42

GCM with 1-port OC-12/STM-4 LR2 42

GCM with 1-port OC-48/STM-16 IR1 55

GCM with 1-port OC-48/STM-16 LR2 55

SONET/SDH Modules

8-Port OC-3/STM-1 IR1 37


4-Port OC-12/STM-4 LR2 42

1-Port OC-48/STM-16 SR 41




1-Port OC-48/STM-16 VR2 41

1-Port OC-48/STM-16 with VCX component 41

1-Port OC-48/STM-16 VR ITU Channel N-1, N 41

1-Port OC-192/STM-64 SR1 90


1-Port OC-192/STM-64 LR2a 90

1-Port OC-192/STM-64 ELR2a 90

1-Port OC-192/STM-64 ELR FEC ITU 193.7 90


Volume 1, Section 4: Planning and EngineeringPower Consumption

Electrical Modules

28-Port DS1 49



12-Port DS3/EC-1 Transmux 46

21-Port E1 49

VT Switch 42

Ethernet Modules

8-Port GbE LX 63

8-Port GbE SX 63

24-Port 10/100BaseTX 55

2-port GbE LX plus 8-port 100BaseFX 68

2-port GbE LX plus 16-port 10/100BaseTX 67

2-port GbE SX plus 16-port 10/100BaseTX 67

Shelf Components

Fan Tray Traverse 2000 80

Fan Tray Traverse 1600 70

PDAP-2S < 1

PDAP-4S < 1

Table 4-4 Power Distribution Per Traverse Module (continued)

Interface Module or Component Type Watts Per Module / Component


Chapter 1 Traverse SpecificationsElectrical Coax and Copper Module Cabling

Fiber Optic Module Cabling

The Traverse backplane allows each optical Service Interface Module (SIM) to terminate up to 48 fibers, or support up to 24 optical interfaces. It has female duplex backplane housings5 to accept the MPX6 multifiber array connectors located on the optical SIMs. All MPX connectors have a precise alignment mechanism to provide quick and easy installation. The optical backplane supports singlemode and multimode fiber optic cable.

A fiber optic patch panel may be used to provide access and standard connectors (SC, FC, or FT) for termination of fiber optic cables from the Optical Distribution Frame (ODF) and from the Traverse fiber optic backplane. Fiber optic cable with an MPX female connector on one end must be used to make the connection at the Traverse fiber optic backplane. An SC connector on the other end of the fiber optic cable is the recommended option. Fiber optic cable with fan out for termination to single fiber connectors (MPX, FC, or FT) is another option.

Electrical Coax and Copper Module Cabling

The DS3/E3/EC-1 Clear Channel and DS3/EC-1 Transmux modules are cabled using standard coax cables with BNC or SMB connectors. Coax cables are connected to the DS3/E3 electrical connector module (ECM) at the main backplane. The main backplane supports 1:1 and 1:2 equipment protection switching.

The 10/100BaseTX, GbE-LX plus 10/100BaseTX Combo, GbE-SX plus 10/100BaseTX Combo, DS1, and E1 modules are cabled using standard twisted-pair copper cables with Telco connectors. Twisted-pair cables are connected to 10/100BaseT or DS1/E1 ECMs at the main backplane.

See Chapter 2—“Network Cabling using Electrical Connector Modules,” page 4-17 for more information on ECMs.

5 16 on the Traverse 1600 backplane and 20 on the Traverse 2000 backplane.

6 The AMP LIGHTRAY MPX™ interconnection system is designed for blind-mate backplane and bulkhead dense fiber-to-fiber interconnect applications.


Volume 1, Section 4: Planning and EngineeringTraverse Interface Types

Traverse Interface Types

This table lists reach and rate information for the optical modules and connector type for the electrical interface modules.

Table 4-5 Traverse Interfaces

Interface Type Rate Module Description

Fiber

OC-3/STM-1 OC-3/STM-1 IR1 Intermediate reach, singlemode

OC-12/STM-4 OC-12/STM-4 IR1 Intermediate reach, singlemode

OC-12/STM-4 LR2 Intermediate reach, singlemode

OC-48/STM-16

OC-48/STM-16 SR Short reach, singlemode

OC-48/STM-16 IR1 Long reach, singlemode

OC-48/STM-16 IR1 with VCX Long reach, singlemode

OC-48/STM-16 LR1 Long reach, singlemode

OC-48/STM-16 LR2 Long reach, singlemode

OC-48/STM-16 VR2 Very Long reach, singlemode

OC-48/STM-16 VR ITU Channel N-1, N (Future)

Very long reach, singlemode

OC-192/STM-64

OC-192/STM-64 SR1 Short reach, singlemode

OC-192/STM-64 IR2 Intermediate reach, singlemode

OC-192/STM-64 LR2a Long reach, singlemode

OC-192/STM-64 ELR2a Long reach, singlemode

OC-192/STM-64 ELR FEC ITU 193.7 Long reach, singlemode

STS-N11 Mb2

GbE LX Long reach, singlemode

GbE plus 100BaseFX Reach: 5 km/15 km, singlemode

GbE plus 10/100BaseTX Reach: 5 km/328 ft or 100 meters, singlemode

Coaxial DS3/E3DS3/E3/EC-1 Clear Channel Electrical Connector Module (ECM) with 75

Ω BNC or SMB connectorsDS3/EC-1 Transmux

Twisted Pair

DS1/E1 DS1/E1 ECM withTelco 64

Fast Ethernet10/100BaseTX

ECM with Telco 50GbE plus 10/100BaseTX

1 Ethernet frames coming from a GbE interface are mapped into one shared or dedicated STS/VC path which is transported across a SONET/SDH network to another GbE interface. The network operator configures SONET/SDH capacities at standard rates or virtually concatenated rates for transport.

2 Provisionable in 1Mb increments for service.


Chapter 1 Traverse SpecificationsShelf and Rack Density

00

orts per helf

12

48

96

48

84

96

32

48

/32

/ 64

/ 64

32

16

4

–

Fiber Connector Shelf

Fiber cable from the fiber optic connector shelf connects to the Traverse optical backplane using an MPX female connector. All connectors have a precise alignment mechanism to provide quick and easy installation.

Shelf and Rack Density





Modules per

ShelfPorts per

ShelfPorts per

RackModules

per Shelf

Ports per Shelf

Ports per Rack

Modules per

Shelf

P

S


28-Port DS1 16 448 1792 12 336 1344 4 1




21-Port E13 16 336 1344 12 252 1008 4





18 36/144 144/576 14 28/112 112/448 4 8


16 32 / 256 128/1024 12 24 / 192 96 / 768 4 8


16 32 / 256 128/1024 12 24 / 192 96 / 768 4 8

8-Port OC-3/STM-1 18 144 576 14 112 448 4

4-Port OC-12/STM-4 18 72 288 14 56 224 4

1-Port OC-48/STM-16 18 18 72 14 14 56 4






Volume 1, Section 4: Planning and EngineeringRegulatory Compliance

Regulatory Compliance

Table 4-7 provides Traverse regulatory compliance information.

Table 4-7 Regulatory Compliance


NEBS

SR-3580, Level 3

GR-63-CORE

GR-1089-CORE

Safety UL 60950, EN 60950, IEC 60950, CSA C2.22 No. 60950

EMI

FCC Part 15, Class A

EN 300 386

EN 55022, Class A

Environmental

Storage: –40ºC to +70ºC, 95% max. relative humidity

Operational: –5ºC to +55ºC, 90% max. relative humidity

Altitude: 13,123 ft. (4000 m), 45ºC

Seismic: NEBS Zone 4

Storage tests: ETS 300 019-2-1, Class T1.2

Transportation tests: ETS 300 019-2-2, Class T2.3

Operational tests: ETS 300 019-2-3, Class T3.1 & T3.1E



Chapter 2Network Cabling using Electrical Connector Modules

Introduction There are five types of electrical connector modules (ECM) used for copper and coax cabling at the Traverse main backplane: 2-slot-wide DS1/E1 (Telco 64). 2-slot-wide DS3/E3 (24 BNC). 2-slot-wide 10/100BaseT (Telco 50). 3-slot-wide DS3/E3 (48 BNC). 3-slot-wide DS3/E3 (96 Mini-SMB).

The electrical connector modules enable copper and coax network interface cabling using industry-standard cables and connectors.

Figure 4-6 Electrical Connector Modules (Front View)

10/100BaseT ECM(Telco 50)

DS3/E3 ECM(24 BNC)

DS3/E3 ECM(96 Mini-SMB)

DS3/E3 ECM(48 BNC)

DS1/E1 ECM(Telco 64)


Volume 1, Section 4: Planning and EngineeringECM Placement at the Traverse Main Backplane

ECM Placement at the Traverse Main Backplane

The ECMs plug into the main backplane 2 mm connectors of any corresponding odd or even slot1. The 2-slot ECM occupies the width of two slots and the 3-slot ECM occupies the width of three slots on the main backplane. For example, the 2-slot ECM for slots 1 and 2 plugs into the 2 mm connectors of slot 1. The following graphic shows slot 1 main backplane 2 mm connectors in dark grey, and the outline of the 2-slot ECM in light grey.

Figure 4-7 2-Slot ECM Placement—Traverse 2000 Main Backplane

1 Refer to pre-Release 1.3 Traverse system documentation for placement restrictions with respect to the superseded Traverse backplane design supporting only 1:1 protection schemes. The protection module must be in the odd-numbered slot and the working module in the even-numbered slot.

1234567891011121314151617181920

2-slot ECM

Slot 1Connectors


Chapter 2 Network Cabling using Electrical Connector ModulesECM and Module Placement Planning Guidelines

ECM and Module Placement Planning Guidelines

Since ECMs are two and three slots in width and different protection schemes, the following guidelines apply for module placement planning and cabling:1. 1:2 equipment protection module placement.

– Using a 3-slot DS3/E3 ECM, place like modules (12- or 24-port DS3/E3/EC-1 CC)2 in any three adjacent slots. The protection group can start in any odd or even slot. The module in the center slot is the protection module for the working modules in the two adjacent slots.

or– Using a 2-slot DS1/E1 ECM, place like modules (DS1) in any three adjacent

slots. The protection group can start in any odd or even slot. The module in the center slot is the protection module for the working modules in the two adjacent slots.

2. 1:1 equipment protection module placement.Using a 2-slot DS1/E1 or DS3/E3 ECM, place like modules (DS1, DS3/EC-1 CC, DS3/EC-1 TMUX, 12- or 24-port DS3/E3/EC-1 CC) in any two adjacent slots. The protection group can start in any odd or even slot3. The module in the left-most slot is the protection module for the working module in the right-adjacent slot.

3. Unprotected module placement – Using a 2-slot DS1/E1 or 10/100BaseTX ECM, place two like

copper-interface modules (DS1 or 10/100BaseTX) in adjacent slots and connect cables to the ECM for both modules.

or– Using a 3-slot DS3/E3 ECM, place two like copper-interface modules (12- or

24-port DS3/E3/EC-1 CC) in the left- and right-most slots and an optical module (OC-3, OC-12 or OC-48) in the center slot and connect the copper-interface cables to the ECM accordingly.

or– Using any of the 2-slot ECMs, place a DS1, DS3/EC-1 CC, DS3/EC-1 TMUX

or 10/100BaseTX module in one slot and an optical module (OC-3, OC-12 or OC-48) in the other slot and connect the copper-interface cables to the ECM accordingly.

2 The pre-Release 1.4 DS3/EC-1 CC and DS3/EC-1 TMUX modules are not used in the 1:2 protection group.

3 Refer to pre-Release 1.3 Traverse system documentation for placement restrictions with respect to the superseded Traverse backplane design supporting only 1:1 protection schemes. The protection module must be in the odd-numbered slot and the working module in the even-numbered slot.


Volume 1, Section 4: Planning and EngineeringElectrical Connection Module Types

AWG,

5A C

5A C

alent, nector.

5 co 50

Electrical Connection Module Types

The following table provides port, connector and cable information for each type of ECM. The total number of ports supported for each ECM is based on like modules placed adjacently in the shelf.

Table 4-8 Electrical Connector Modules

ECM Type

Total # of Ports

Type of EMC Connectors Cable Description1:2

Equipment Protection

1:1 Equipment Protection

Unprotected

DS1/E1 (DS1 ports) 56 28 56 (4) female Telco 64

(CHAMP)Copper 32-pair cable, 24 with 180º male Telco 64 connector.DS1/E1

(E1 ports) 42 21 42

DS3/E3, 2-slot (24 BNC) N/A 12 12

(24) female 75Ω BNC Coax, AT&T 734A or 73equivalent, with male BNconnector.

DS3/E3, 3-slot (48 BNC) 24 12 24

(48) female 75Ω BNC Coax, AT&T 734A or 73equivalent, with male BNconnector.

DS3/E3, 3-slot (96 Mini-SMB) 48 24 48 (96) female 75Ω

Mini-SMBCoax, AT&T 735A equivwith male Mini-SMB con

10/100BaseT N/A N/A 48(4) female Telco 50 (Centronics)

Copper, 25-pair category cable, with 180º male Telconnector.


Chapter 2 Network Cabling using Electrical Connector ModulesCable Management

Cable Management

Copper and coax cables are tie-wrapped to a cable management bar mounted across the back of the Traverse shelf. Cables are routed out the right side of the shelf (viewed from the back of the shelf) and routed up the rack to intermediate patch panels. The following graphic shows an example Traverse 1600 shelf with 10/100BaseT, DS1/E1, and DS3/E3 (24 BNC) ECMs and the cable management bar.

Figure 4-8 Traverse Shelf with Cable Management Bar

Intermediate patch panels may be located in the same or adjacent rack as the Traverse shelf. DS3 and E3 ports can be configured for different line build-out (LBO) options, depending on the distance between the Traverse shelf and the next piece of network equipment. The TransNav Management System is used to set LBO.

Cable Management

Bar

Route Copper/Coax Cables to the Right Side of the Traverse

Shelf


Volume 1, Section 4: Planning and EngineeringCable Management




Introduction The TransAccess 100 STS-1/T1 Mux can be installed in either standard 19-inch or 23-inch wide racks. Rack extension adapters must be used when installed in a 23-inch rack. The TransAccess 100 Mux mounting brackets1 can be placed 2 inches or 5 inches from the front of the unit. The TransAccess 100 Mux is one rack unit (1.75") in height.

Note: Do not exceed four TransAccess 100 Mux units per foot of vertical rack space.

The TransAccess 100 Mux can also be mounted on a wall. When mounted on a wall, it should be mounted to a plywood panel and oriented such that the fan is located at the top to facilitate cooling. The Mapper card insertion would be from the left side and the input/output cables would be on the right. Sufficient spacing must be provided for servicing.

An AC/DC converter(s) can be used for the power source and a modular 8-position cross-connect panel.

Power Distribution Unit

The TransAccess 100 Mux requires a separate power distribution unit2 (PDU). Turin Networks recommends the ADC power distribution unit. The PDU should be installed in the same rack as the TransAccess 100 Mux.

1 Mounting brackets are provided with each TransAccess 100 Mux.

Table 4-9 TransAccess 100 Mux Dimensions

Height Depth Width WeightFully Loaded

1.75 in.(4.445 cm)

12.0 in.1

(30.48 cm)

1 Cover to tie bars.

17.15 in.2

(43.815 cm)

2 Without mounting brackets.

8 lb.(3.6287 kg)

2 The PDAP provides power distribution for the Traverse shelves only. A separate PDU must be installed for TransAccess 100 Mux deployments.


Volume 1, Section 4: Planning and EngineeringPower

Power

Integration with Traverse System

Up to twelve TransAccess 100 Muxes can be connected to one Traverse 12-port DS3/EC-1 Clear Channel module. A single Traverse 1600 node using six redundant DS3/EC-1 Clear Channel modules can support up to seventy-two (72) TransAccess 100 Muxes, a Traverse 2000 node can support up to ninety-six (96) TransAccess 100 Muxes.

Each TransAccess 100 Mux has an Ethernet port for control and management communication. Using the Ethernet port, each TransAccess 100 Mux is connected to an Ethernet hub. Turin Networks recommends the 16-port Garretcom Magnum DS8016 Ethernet hub. The Ethernet hub has a designated uplink Ethernet port to the Traverse node via the DCN Ethernet interface on the Traverse backplane..

Note: If more than sixteen (16) TransAccess 100 Muxes are installed in the same office, you must install additional Ethernet hubs in a tree architecture. One Ethernet hub port is required for each TransAccess 100 Mux installed.

Table 4-10 TransAccess 100 Mux Power Specifications


Voltage –41.5 to –56.3 Vdc

Power consumption 45 Watts maximum

Current draw 0.75 Amps typical

Recommended fuse 2-3 Amps

Figure 4-9 TransAccess 100 Mux Shelf Interconnection to Traverse Shelf

28 DS1

28 DS1

28 DS1 12 maximum

2

1

10/100BaseT

Ethernet Hub

GCM

EC-1

DS3/EC-1ClearChannel

Traverse

SD

A TM S V S1 2 3 4 5 6 7 8 9 10 1 1 1 2

Li nk St at u sF ai lFa ilA ct i v eA c t iv e

Col l is i o n

PO R T S T A TU S

Pa c ket

P ac k etL in k S ta tu sET H E RN E T P OR T

1 2 3 4 5 6 7 8 1 2111 09

EthernetHub

C on s ole

P1

P2

P3

P4

P5

P6

P7

P8

P9

P10

P11

P12

P1

P2

P3

P4

P5

P6

P7

P8

P9

P1 0

P1 1

P1 2

P1 P1 P1 P1


Chapter 3 TransAccess 100 MuxRelay Contacts

Interfaces

Environmental

Relay Contacts

Table 4-11 TransAccess 100 Mux Interfaces


STS-1 BNC, male

T1 64 pin Amp, female

Craft/modem/PPP 8 pin modular, female

Ethernet/Telnet 10BaseT

Alarm contact Wire wrap

Power Dual feed terminals

Table 4-12 TransAccess 100 Mux Environmental Specifications


Operating temperature 32ºF to 104ºF (0ºC to 40ºC)

Relative humidity Up to 90%, non-condensing

Altitude Up to 10,000 ft. (3,048 meters) above sea level

Table 4-13 TransAccess 100 Mux Relay Contact Closure Ratings

Contact Rating Location and Description

FE (Far-End)MN (Minor)MJ (Major)CR (Critical)

0.3 Amp @ 110 VDC0.3 Amp @ 125 VAC

Wire-wrap interface on rear of ACX091 cage

Neither can be ACO’ed


Volume 1, Section 4: Planning and EngineeringRelay Contacts


SECTION 5 APPENDICESSECTION 5

Contents

Appendix ACompliance

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1Compliance and Certification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1ETSI Environmental Standards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1NEBS Compliance and Certification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1UL and FCC Standards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2Reliability at Turin Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2Reliability Development. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2Reliability in Production. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3

Appendix BAcronyms and Abbreviations

Acronyms and Abbreviations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5SONET/SDH Channel Capacities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17VT/VC Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17

List of TablesTable 5-1 SONET/SDH Digital Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17Table 5-2 Virtual Tributary/Virtual Container Hierarchy. . . . . . . . . . . . . . . . . 5-17


Volume 1 Section 5 Appendices


SECTION 5APPENDICES

Appendix ACompliance

Introduction The highest levels of quality testing and the most stringent compliance standards that can be achieved are the goals of the Quality Assurance division of Turin Networks. The Turin Quality Management System is scheduled to be certified to TL 9000 and ISO 9001.

Compliance and Certification

CE Mark has been obtained for all products destined for the European Telecommunications Standards Institute (ETSI) market. CE Mark on Turin’s products is based on the following testing: Electro-Magnetic Compatibility (EMC): ETS 300 386, EN55022, EN55024,

CISPR-22, Class B for deployment in other than telecommunication centers. Safety (CB Scheme): EN60950, CSA 22.2 No. 60950, AS/NZS 3260, IEC 60950

3rd Edition, compliant with all CB Scheme member country deviations.

ETSI Environmental Standards

In addition to the testing required for CE Mark, Turin’s products are also tested to the following ETSI specifications: Storage: ETS 300 019-2-1, class T1.2 Transportation: ETS 300 019-2-2, class T2.3 Operational: ETS 300 019-2-3, class T3.1 and T3.1E

NEBS Compliance and Certification

Network Equipment-Building Systems (NEBS) standards define a rigid and extensive set of performance, quality, environmental, and safety requirements developed by Telcordia.

Level Three Compliance

The NEBS testing for the Turin Networks Traverse 1600, Traverse 2000, and Traverse 600 systems includes all applicable tests specified in Telcordia document SR-3580, commonly referred to as NEBS Level 3. The Turin NEBS test program also includes testing for the following: Acoustic noise. Altitude to 13,000 feet above sea level. Earthquakes: meets zone 4 requirements. Face plate temperature.


Volume 1, Section 5: AppendicesUL and FCC Standards

Heat dissipation. Illumination.

Acceptance criteria is in accordance with the most stringent standards imposed by the Regional Bell Operating Companies (RBOCs). In some cases these standards exceed the criteria specified in GR-63-CORE and GR-1089-CORE.

UL and FCC Standards

The Traverse 1600, Traverse 2000, and Traverse 600 system is being tested to the requirements of UL 60950 and FCC part 15.

Reliability at Turin Networks

The Traverse 1600 and Traverse 2000 systems can be configured in the network in several different ways: SONET/SDH terminal multiplexer. SONET/SDH add/drop multiplexer. Broadband/High Order digital cross connect. Broadband/High Order switch.

Most of the requirements specified by Telcordia for the above-listed types of configurations are for a per-channel availability of 99.999%.

As required by GR-418-CORE and GR-499-CORE, circuit pack failure rate predictions are performed in accordance with the requirements of TR-332. Also, GR-418-CORE and SR-TSY-001171 are used in the analysis of system availability and other reliability parameters. The current predicted per-channel availability meets the 99.999% requirement.

Reliability Development

During product development, reliability growth is achieved primarily through Highly Accelerated Life Testing (HALT). HALT is a proactive technique to improve products and field reliability, not to measure the reliability of the product. The stresses applied during HALT far exceed the field environment, and are intended to expose the weak links in the design and processes in a very short period of time.

These stresses applied during HALT include such things as: Exposure to temperature extremes from as low as –50º C to as high as +110º C, or

to the upper destruct limit. Rapid rates of change of temperature, as high as 60º C per minute. Omni-axial random vibration, up to 30 G’s rms or to the upper destruct limit. Power cycling. Internal voltage margining. Varying clock frequencies. Exposure to high humidity.

Once failures are precipitated during HALT, corrective action is implemented in order to increase the robustness of the product. Then the HALT process is continued in an effort to identify the next weakest link. This Halt Corrective Action cycle is continued until the fundamental limit of the technology is reached, at which point the robustness of the hardware has been optimized.


Appendix A ComplianceReliability in Production

Where HALT is used to improve the reliability of the product, standard, accelerated-life testing is used to measure the reliability of the improved product. Prior to releasing hardware to production, accelerated life testing is conducted on an operating system, at 60° C for 1500 hours (minimum), far exceeding the GR-418-CORE requirement of 117 hours at 50° C. One purpose of this testing is to simulate the first year of operational life, as a minimum, and to determine by way of life test data, the product MTBF and availability.

Reliability in Production

The production process includes a comprehensive suite of tests, designed to ensure optimum product reliability and performance in the field. This production testing includes the following: Automatic X-ray inspection. Highly Accelerated Stress Screening (HASS). In-circuit test, with boundary scan. Board-level functional test. System test.

The automatic X-ray inspection is conducted on all circuit boards, with all components and solder joints being inspected. For certain component technologies such as ball-grid-arrays (BGAs), there is no method other than X-ray that adequately verifies solder quality.

Highly Accelerated Stress Screening (HASS) is a screening method that applies stresses that far exceed conventional burn-in techniques. The HASS profile is derived from the HALT results, where the operational and destruct limits of the hardware have been determined. The HASS stresses also generally exceed the field environment, though they do not overstress the product. The proof of screen process verifies that the HASS profile does not consume useful life.


Volume 1, Section 5: AppendicesReliability in Production


SECTION 5APPENDICES

Appendix BAcronyms and Abbreviations

Acronyms and Abbreviations

Acronyms are formed from the initial letter or letters of each of the successive parts or major parts of a compound term. Turin Networks uses the following set of acronyms and abbreviations in product literature and documentation.

AAL ATM Adaptation Layer

ABR Available Bit Rate

ACO Alarm Cut-Off

ACR Actual Cell Rate

ADM Add-Drop Multiplexer

ADP Actual Departure Potential

ADT Actual Departure Time

AINI ATM Internetworking Interface

AIS Alarm Indication Signal

AMI Alternate Mark Inversion

APS Automatic Protection Switching

APSBF Automatic Protection Switching Byte Failure

APSCM Automatic Protection Switching Channel Mismatch

APSMM Automatic Protection Switching Mode Mismatch

ASIC Application-Specific Integrated Circuit

ASP Applications Service Provider

ATM Asynchronous Transfer Mode

AU Administrative Unit

AU-N Administrative Unit level N (N = 3 or 4)

AUG Administrative Unit Group

AWG American Wire Gauge


Volume 1, Section 5: AppendicesAcronyms and Abbreviations

B-DCS Broadband Digital Cross-connect System

B3ZS Bipolar 3 Zero Substitution

B8ZS Bipolar 8 Zero Substitution

BDFB Battery Distribution Fuse Bay

BER Bit Error Rate

BERT Bit Error Rate Tester

BGP4 Broadband Gateway Protocol, version 4

B-ICI B-ISDN Inter-carrier Interface

BIP Bit Interleaved Parity

BITS Building Integrated Timing Supply

BLSR Bi-directional Line Switching Ring

BML Business Management Layer

BPV Bipolar Violation

B-RAS Broadband Remote Access Server

C2O Cable to Optic

CAC Call Admission Control or Connection Admission Control

CAM Content Addressable Memory

CBR Constant Bit Rate

CC Clear Channel

CDP Contracted Deadline Potential

CDV Cell Delay Variation

CDVT Cell Delay Variation Tolerance

CES Circuit Emulation Service

CEV Controlled Environmental Vault

CLEC Competitive Local Exchange Carrier

CLEI Common Language Equipment Identifier

CLFI Common Language Facility Identification

CLI Command Line Interface

CLLI Common Language Location Identifier

CLR Cell Loss Ratio

CO Central Office Environment

COBRA Copper and Optical Broadband Remote Access

COE Central Office or Connection Oriented

CORBA Common Object Request Broker Architecture


Appendix B Acronyms and AbbreviationsAcronyms and Abbreviations

COS Class of Service

COT Central Office Terminal

CP Call Processing

CPE Customer Premises Equipment

C-Plane Control Plane

CPU Central Processing Unit

CRC Cyclic Redundancy Check

CR-LDP Constraint-based Routing Label Distribution Protocol

CSU Channel Service Unit

CTD Cell Transfer Delay

CV Code Violation

CWDM Coarse Wavelength Division Multiplexing

DB Decibel

dBm decibels relative to milliwatt

DCC Data Communications Channel

DCE Data Circuit-terminating Equipment

DCN Data Communications Network

DCS Digital Cross-connect System

DHCP Dynamic Host Configuration Protocol

DLC Digital Loop Carrier

DM Degraded Minute

DQ Degraded Quality Level

DS Digital Signal

DS0 Digital Signal Zero (64 Kbps data/voice channel)

DS1 Digital Signal Level 1 (T1 equivalent)

DS3 Digital Signal Level 3 (T3 equivalent)

DSLAM Digital Subscriber Line Access Multiplexer

DSX-1 Digital Signal Level 1 cross connect

DSX-3 Digital Signal Level 3 cross connect

DTE Data Terminal Equipment

DVC Dynamic Virtual Concatenation

DWDM Dense Wavelength Division Multiplexing

DXC Digital Cross Connect

EAI Enterprise Application Integration



EC-1 Electrical Carrier Level 1 (STS1 equivalent)

EDFA Erbium-Doped Fiber Amplifiers

EEE Electronic Equipment Enclosure

EMI Electromagnetic Interference

EML Element Management Layer

EMS Element Management System

EOC Embedded Operations Channel

ERDI Enhanced Remote Defect Indicator

ES Errored Second

ESCON Enterprise Systems Connection

ESD Electrostatic Discharge

ESF Extended Super Frame

ETSI European Telecommunications Standards Institute

EXZ Excessive Zeros

FC Failure Count

FCS Frame Check Sequence

FDDI Fiber Distributed Data Interface

FDL Facilities Data Link

FDM Frequency Division Multiplexing

FE Far End

FEBE Far-End Block Error

FEC Forward Error Correction

FEP Far-End Protection

FERF Far-End Receiver Failure

FIB Forwarding Information Base

FITB Fiber in the Building

FITL Fiber in the Loop

FITR Fiber in the Riser

FPP Fast Pattern Processor

FR Frame Relay

FSAN Full Services Access Network (consortium)

FTP File Transfer Protocol

FTTB Fiber to the Building

FTTC Fiber to the Curb



FTTH Fiber to the Home

Gb Giga bit

GB Giga byte

GbE Gigabit Ethernet

Gbps Gigabits per second

GCM General Control Module

GCRA Generic Cell Rate Algorithm

GFR Guaranteed Frame Rate

Ghz Gigahertz

GMPLS Generalized Multiprotocol Label Switching

GND Ground (electrical)

GR Generic Requirement

GUI Graphical User Interface

HDLC High-speed Data Link Controller

HDB3 High Density Bipolar 3

HEC Header Error Control

HO Higher Order

HOVC Higher Order Virtual Concatenation

HO-DXC Higher Order Digital Cross Connect

HP Higher Order Path

IAD Interface Access Device

IAS Internet Access Service

ID Identifier

IDT Inter-DXC Trunk

IEC Interexchange Carrier

IEEE Institute of Electrical and Electronic Engineers

IETF Internet Engineering Task Force

ILEC Incumbent Local Exchange Carrier

I/O Input/Output

IP Internet Protocol

IPC InterProcess Control or InterProcessor Control

IR Intermediate Reach

ISD Idle Signal Detection

ISO International Organization for Standardization



ISP Internet Service Provider

ITU International Telecommunication Union

IWF Interworking Function

JDK Java Development Kit

JDMK Java Dynamic Management Kit

JRE Java Runtime Environment

Kb Kilo bit

KB Kilo byte

Kbps Kilo bits per second

kHz Kilohertz

Km Kilometer

LAN Local Area Network

LBC Laser Bias Current

LBO Line Build Out

LC Line Card

LCN Local Communications Network

LEC Local Exchange Carrier

LED Light Emitting Diode

LIU Line Interface Unit

LMI Local Management Interface

LO Low Order

LOF Loss of Frame

LOP Loss of Pointer

LOS Loss of Signal

LOSS Loss of Signal Seconds

LO-DXC Low Order Digital Cross Connect

LP Low Order Path

LR Long Reach (fiber)

LSM Loss of Sync Message

LSP Label Switch Path

LSR Label Switch Router

LTE Line Terminating Equipment

MAC Medium Access Control

MAN Metropolitan Area Network



Mb Mega bit

MB Mega byte

Mbps Mega bits per second

MBS Maximum Burst Size

MCP Management Control Processor

MCR Minimum Cost Routing or Minimum Cell Rate

MDF Main Distribution Frame

MDU Multiple Dwelling Unit

MGCP/MEGACO Media Gateway Control Protocol / MEdia GAteway COntrol protocol

MGN Management Gateway Node

MHz Megahertz

MMF Multimode Fiber

MLPPP Multi-Link Point-to-Point Protocol

M-Plane Management Plane

MPLS MultiProtocol Label Switching

MPOA MultiProtocol Over ATM

ms Millisecond

MSF Multiservice Switching Forum

MS Multiplex Section

MSP Multiplex Section Protection

MSPP Multiservice Provisioning Platform

MS-SPRing Multiplex Shared Protection Ring

MTBF Mean Time Between Failure

MTTR Mean Time to Repair

MTU Maximum Transmission Unit

mV Millivolt

NBI Northbound Interface

NC Normally Closed (contacts)

NDIS Network Design and Inventory System

NE Network Element

NEBS Network Equipment-Building Systems

NGDLC Next Generation Digital Loop Carrier

NIC Network Interface Card



NID Network Interface Device

NMF Node-level Management Function

NML Network Management Layer

NMS Network Management System

NNI Network Node Interface

NO Normally Open (contacts)

NRT Non-Real Time

ns nanosecond

NSA Non-Service Affecting

NTP Network Time Protocol

NUT Non-preemptive Unprotected Traffic

OAM&P Operations, Administration, Maintenance & Provisioning

OC Optical Carrier

OC-1 Optical Carrier 1 (51.84 Mbps)



OC-48 Optical Carrier 48 (2.488 Gbps)

OC-192 Optical Carrier 192 (9.953 Gbps)

OC-N Optical Carrier-number

OLT Optical Line Termination/Terminal

ONT Optical Network Terminal

ONU Optical Network Unit

OOB Out Of Band

OOF Out Of Frame

OPR Optical Power Receive

OPT Optical Power Transmit

OS Operating System

OSP OutSide Plant

OSPF Open Shortest Path First

OSS Operations Support System

OSSAN Operations Support System Access Nodes

PC Personal Computer

PCA Protection Channel Access

PCR Peak Cell Rate



PDAP Power Distribution and Alarm Panel

PDI Payload Defect Indication

PDU Power Distribution Unit

PG Protection Group

PLCP Physical Layer Convergence Protocol

PLM Payload Label Mismatch

PM Performance Management or Performance Monitoring

PNNI Private Network-to-Network Interface

POH Path Overhead

PON Passive Optical Network

POP Point of Presence

POS Packet Over SONET

POST Power On Self Test

POTS Plain Old Telephone Service

PPM Parts per Minute

PPP Point-to-Point Protocol

PRC Primary Reference Clock

PSC Protection Switching Count

PSD Protection Switching Duration

PTE Path Terminating Equipment

PTP Physical Termination Point

PVC Permanent Virtual Circuit

QoS Quality of Service

RAI Remote Alarm Indication

RBOC Regional Bell Operating Companies

RED Random Early Discard

REI Remote Error Indication

RFI Remote Failure Indication

RIB Routing Information Base

RMI Remote Method Invocation

RRO Record Route Object

RSVP Resource Reservation Protocol

RT Remote Terminal

RTN Return (voltage return)



RU Rack Unit

RX Receive

s Second

SA Service Affecting

SAN Storage Area Network

SC Shelf Controller

SD Signal Degrade

SDH Synchronous Digital Hierarchy, the E1-based equivalent to SONET that is the standard outside North America

SEF Severely Errored Framing

SerDes Serializer/De-serializer

SES Severely Errored Second

SF Super Frame or Signal Failure

SFO Sync Frequency Offset

SIM Service Interface Module

SLA Service Level Agreement

SMF Singlemode Fiber

SML Service Management Layer

SMM Service Mediation Module

SNCP/I Subnetwork Connection Protection / Inherent monitoring

SNCP/N Subnetwork Connection Protection / Non-intrusive monitoring

SNMP Simple Network Management Protocol

SONET Synchronous Optical NETwork, the North American standard

SPC SONET Permanent Circuit

SPE Synchronous Payload Envelope

SPRing Shared Protection Ring

SPVC Soft Permanent Virtual Circuit

SQL Structured Query Language

SR Short Reach (fiber)

SSM Synchronization-status messages

STM-1 Synchronous Transfer Mode - Level 1 (155.52 Mbps)

STM-4 Synchronous Transfer Mode - Level 4 (622.08 Mbps)

STM-16 Synchronous Transfer Mode - Level 16 (2.488 Gbps)



STM-64 Synchronous Transfer Mode - Level 64 (9.953 Gbps)

STS Synchronous Transport Signal

STS-1 Synchronous Transport Signal Level 1

STS-3 Synchronous Transport Signal Level 3

STS-3c Synchronous Transport Signal Level 3, concatenated

STS-Nc Contiguous Concatenation of N STS-1 SPEs

STS-N-Xv Virtual Concatenation of X STS-N SPEs

SVC Switched Virtual Circuit

TAC Technical Assistance Center

TAP Technician Access Port

TC Transmission Convergence

TCA Threshold Crossing Alert

TCP/IP Transmission Control Protocol/Internet Protocol

TDM Time Division Multiplexing

TE Terminal Equipment

TED Traffic Engineering Database

TIM Trace Identifier Mismatch

TLS Transparent LAN Services

TMN Telecommunications Management Network

TOH Transport Overhead

TSI Time Slot Interchange

TSN Traverse Services Network

TU Tributary Unit

TUG Tributary Unit Group

TX Transmit

UAS Unavailable Second

UBR Unspecified Bit Rate

UGC Universal Gateway Carrier

UL Underwriters Laboratories

UNEQ Unequipped

UNI User-Network Interface (per ATM Forum)

UPC Universal Packet Carrier or Usage Parameter Control

UPSR Unidirectional Path Switched Ring



UTC Universal Transport Carrier or Universal Time Coordinated

UVC Universal Voice Carrier or Universal Video Carrier

VAP Virtual Access Partitioning

VBR Variable Bit Rate

VC Virtual Circuit or Virtual Concatenation

VC-N Virtual Container Level N (N = 11, 12, 2, 3, 4)

VC-N-Xc Contiguous Concatenation of X Virtual Containers at level N.

VC-N-Xv Virtual Concatenation of X Virtual Containers at level N.

VCC Virtual Channel Connection

VCI Virtual Channel Identifier

VCSEL Vertical Cavity Surface Emitting Laser

VDC Volts Direct Current

VLAN Virtual Local Area Network

VLR Very Long Reach

VOM Volt Ohm Meter

VP Virtual Path

VPC Virtual Path Connection

VPI Virtual Path Identifier

VPI/VCI Combined, VPI and VCI identify a connection on an ATM network

VPN Virtual Private Network

VSA Virtual-Scheduling Algorithm

VT Virtual Tributary

VTG Virtual Tributary Group

V-UNI Virtual User Network Interface

W Watt

W-DCS Wideband Digital Cross-connect System

WAN Wide Area Network

WDM Wave Division Multiplex

WTR Wait-to-Restore

For a compendium of telecommunications terms, see Newton’s Telecom Dictionary, by Harry Newton, published by CMP Books, New York, NY. See http://www.harrynewton.com for more information.


Appendix B Acronyms and AbbreviationsVT/VC Hierarchy

SONET/SDH Channel Capacities

Table 5-1 SONET/SDH Digital Hierarchy

VT/VC Hierarchy

Table 5-2 Virtual Tributary/Virtual Container Hierarchy

SONETOptical

Rate

SONET Electrical

Equivalent

SONETLevel of

Concatenation

Line Rate (Mbps)

Maximum Payload

Rate (Mbps)

Maximum Overhead

Rate (Mbps)

SDH Equivalent

Rate

OC-1 STS-1 – 51.840 50.112 1.728 –

OC-3 – STS-3c 155.520 150.336 5.184 STM-1

OC-9 – STS-9c 466.560 451.008 15.552 STM-3

OC-12 – STS-12c 622.080 601.344 20.736 STM-4

OC-18 – STS-18c 933.120 902.016 31.104 STM-6

OC-24 – STS-24c 1244.160 1202.688 41.472 STM-8

OC-36 – STS-36c 1866.240 1804.032 62.208 STM-13

OC-48 – STS-48c 2488.320 2405.376 82.944 STM-16

OC-96 – STS-96c 4976.640 4810.752 165.588 STM-32

OC-192 – STS-192c 9953.280 9621.504 331.776 STM-64

VT/VC Type Bit Rate (Mbps)

Payload Capacity (Mbps)

Signal/Service VT/VCs Per Group

VT Per STS-1VCs Per VC-3

VT-1.5/VC-11 1.728 1.544 DS1 4 28

VT-2/VC-12 2.403 2.048 E1 3 21

VT3/VC-12 3.456 3.152 DS1C 2 14

VT6/VC-2 6.912 6.312 DS2 2 7


Volume 1, Section 5: AppendicesVT/VC Hierarchy


INDEX

Numerics1:1 equipment protection

module placement, 4-19

AAlarms

alarm windows, GUI, 3-7clearing alarms, 3-7

Autodiscovery, 3-4Intelligent Control Plane, 3-8intelligent control plane, 1-10

BBackplane

BITS input timing interfaces, 2-4, 2-8, 2-11data communications network, 2-4, 2-8, 2-11description, 2-3, 2-7, 2-10environmental alarm module, 2-4, 2-8, 2-11receptacles for fiber connectors, 2-3, 2-7, 2-11timing references, input and output, 2-3, 2-7, 2-11

CCables

electrical coax, 4-13fiber optic, 4-13fiber optic connectors, 4-13

CE Mark, 5-1Circuit breakers

PDAP, 2-15, 4-9CLI

domain-level, 3-16node-level, 3-16

Client hardware recommendations, 3-22Client workstation software recommendations, 3-23Command Line Interface (CLI)

domain-level CLI, 3-4node-level CLI, 3-10

Compliance and certification, 5-1, 5-2Configuration management

equipment configuration, 3-8preprovisioning, 3-8service provisioning, 3-9

Craft accessinterface, 2-3, 2-7, 2-10interfaces, 2-15, 4-8

DData communications network (DCN)

connectivity, 2-4, 2-8, 2-11Data rate

DS1 module, 2-42DS3/EC-1 clear channel module, 2-43, 2-44, 2-45E1 module, 2-46

Dataset snapshots, 3-11Dimensions

PDAP, 4-9TransAccess 100 Mux, 4-23Traverse 1600 shelf, 2-17, 4-5Traverse 2000 shelf, 2-17, 4-5Traverse 600 chassis, 2-17, 4-5

Distributed architecturefeatures, 2-18

DomainManagement server, 3-17

Domain-level CLI, 3-4DS1 module

front view (figure), 2-42power consumption, 2-42specifications, 2-42

DS3 moduleelectrical coax cabling, 4-13

DS3/EC-1 clear channel moduledata rate, 2-43, 2-44, 2-45front view (figure), 2-43, 2-44power consumption, 2-43, 2-44, 2-45specifications, 2-43, 2-44, 2-45

DS3/EC-1 transmux modulefront view (figure), 2-45

EE1 module

power consumption, 2-46specifications, 2-46

Electrical connector modules (ECM)descriptions, 4-17placement, 4-18placement planning guidelines, 4-19types, 4-20

Electro-Magnetic Compatibility (EMC), 5-1EMI, 4-16Environmental alarm module

backplane, 2-4, 2-8, 2-11Environmental alarms, 2-4, 2-8, 2-11Environmental specifications, 4-16

Release 1.4 Turin Networks Index-1

Index

Environmental standards, 5-1Ethernet

Ethernet port, 2-3, 2-7, 2-10, 2-15, 4-8ETSI environmental standards, 5-1Event Management, 3-7Extended temperature

DS1 module, 2-12, 2-42, 2-46

FFan tray

description, 2-14power consumption, 4-12rack configuration, 4-8

Fan tray moduledescription, 2-14

Fault Management, 3-7FCC standards, 5-2Fiber optic

connector shelf, 4-15connectors, 4-13, 4-15interfaces, 4-14MPX connectors, 4-13

GGeneral control

redundancy, 2-18General Control Module

redundancy, 2-18remote restore, 3-10

General reports, 3-11GMPLS, 1-10GMT fuses

PDAP, 2-15, 4-9Graphical user interface (GUI)

description, 3-14fault and event management, 3-7hardware requirements, 3-22performance management, 3-9software requirements, 3-23

HHardware

Management server hardware requirements, 3-18Hardware requirements

Graphical user interface, 3-22Management server, 3-18

High Availability Framework (HAF), 2-19Highly Accelerated Life Testing (HALT), 5-2Highly Accelerated Stress Screening (HASS), 5-3

IIntelligent Control Plane

autodiscovery, 3-8distributed architecture, 2-18node connectivity, 3-3preprovisioning, 3-8role in upgrades, 2-18service connectivity, 3-10

Intelligent control planeautodiscovery, 1-10connectivity, 1-10description, 1-10domain, 1-10domain, autodiscovery, 1-10GMPLS, 1-10node connectivity, 1-10OSPF, 1-10path calculation, 1-11policy enforcement, 1-10RSVP-TE, 1-11service connectivity, 1-11service signaling, 1-11

MManagement Plane, 3-8Management server

hardware requirements, 3-18software requirements, 3-21

Management Systemaccounting management, 3-9alarm data, 3-7clearing alarms, 3-7dataset snapshots, 3-11domain-level CLI, 3-4equipment provisioning, 3-8fault management, 3-7flexible filtering, 3-7flexible scoping, 3-7general reports, 3-11Management Plane, 3-8node-level CLI, 3-10performance management, 3-9preprovisioning, 3-8report generation, 3-11security management, 3-9service provisioning, 3-9system log collection and storage, 3-10

Modem interface, 2-4, 2-8, 2-11Module cabling, 4-13

electrical coax, 4-13fiber optic, 4-13

Index-2 Turin Networks Release 1.4

Index

Module placement, 4-21:1 equipment protection, 4-19guidelines, 4-2unprotected, 4-19

MPX connectors, 4-13

NNEBS, 4-16NEBS compliance, 5-1Node-level CLI, 3-10

OOC-12/STM-4 module

front view (figure), 2-30OC-192/STM-64 module

description, 2-34front view (figure), 2-34

OC-48/STM-16 modulefront view (figure), 2-32

Operating system softwarefeatures, 2-17upgrades, 2-18

OSPF, 1-10

PPDAP

alarm status indicators, 2-15circuit breakers, 2-15, 4-9dimensions, 2-16GMT fuses, 2-15, 4-9operating temperature/humidity, 4-8storage temperature/humidity, 4-8TPA fuses, 2-15, 4-9

PDAP-2Scentral office power, 2-15description, 2-15dimensions, 2-15

Power cabling, 4-10Power consumption

all modules, 4-11DS1 module, 2-42DS3/EC-1 clear channel module, 2-43, 2-44, 2-45E1 module, 2-46Fan tray, 4-12TransAccess 100 Mux, 4-24

Power Distribution and Alarm Panelsee PDAP

Power requirements, 4-8Power, module power consumption, 4-11Preprovisioning, 3-4

RRack configuration

fan tray, 4-8Redundancy

GCMs, 2-18Regulatory compliance, 4-16Relay contacts

TransAccess 100 Mux, 4-25Report generation, 3-11RJ-45 connector

Backplane RS-232 interface, 2-4, 2-8, 2-11RS-232 serial port, 2-4, 2-8, 2-11RSVP-TE, 1-11

SSafety compliance, 4-16Security management, 3-9Service Interface Modules (SIMs)

electrical coax cabling, 4-13electrical copper cabling, 4-13fiber optic cabling, 4-13module, shelf, and rack densities, 1-8, 2-13, 4-15power consumption, 4-11slot assignments, 4-1Traverse 1600, 1-8, 2-13, 4-15Traverse 2000, 1-8, 2-13, 4-15Traverse 600, 1-8, 2-13, 4-15

Service provisioning, 1-11Service signaling, 1-11Software

Management server software requirements, 3-21Operating System, 2-17upgrades, 2-18

Software requirementsGraphical user interface, 3-23GUI, 3-23Management server, 3-21

TTelnet access, 2-4, 2-8, 2-11Temperature

operational, 4-16PDAP, operating, 4-8PDAP, storage, 4-8reliability testing, 5-2storage, 4-16TransAccess 100 Mux, 4-25

TL1 interface, 3-4TPA fuses

PDAP, 2-15, 4-9

Release 1.4 Turin Networks Index-3

Index

TransAccess 100 Muxaltitude, 4-25dimensions, 4-23environmental specifications, 4-25Ethernet hub, 4-24Ethernet port, 4-24installation planning, 4-23integration, 4-24interfaces, 4-25power distribution unit, 4-23power specifications, 4-24relative humidity, 4-25relay contacts, 4-25temperature, 4-25

TraverseCE mark, 5-1Highly Accelerated Life Testing (HALT), 5-2Highly Accelerated Stress Screening (HASS), 5-3module placement, 4-2NEBS compliance, 5-1operating system software, 2-17PDAP, 4-8power requirements, 4-8reliability, 5-2UL standards, 5-2upgradability, 2-18

Traverse 1600dimensions, 2-17, 4-5fan tray module, 2-14, 4-8PDAP, 2-15Service Interface Modules (SIMs), 1-8, 2-13, 4-15

Traverse 2000dimensions, 2-17, 4-5PDAP, 2-15Service Interface Modules (SIMs), 1-8, 2-13, 4-15

Traverse 600description, 2-10dimensions, 2-17, 4-5remote applications, 1-5Service Interface Modules (SIMs), 1-8, 2-13, 4-15wall mount cabinet, 1-5

UUL standards, 5-2Upgrades, 2-18

VVCX Switch module

power consumption, 4-11VT/VC Switch

power consumption, 4-11VT-100 terminal, 2-4, 2-8, 2-11

WWall mount cabinet, 1-5

Index-4 Turin Networks Release 1.4

Date post:	10-Apr-2015
Category:	Documents
Upload:	greg-williams
View:	135 times
Download:	0 times

Volume 1 - General Information Release 1.4 Rev A

Documents