Beruflich Dokumente
Kultur Dokumente
Traverse System
SONET Documentation
Volume 1
General Information
Release 1.4
Publication Date: December 2003
Document Number: 800-0101-04 Rev. A
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 Standards
EN55022 EN55024 CISPR-22
Safety Standards
EN60950 CSA 22.2 No. 60950, ASINZS 3260
IEC 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 Use
Use, 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.
V OLUME 1 G ENERAL I NFORMATION
Contents
Volume 1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii
Section 5 Appendices
Appendix A
Compliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
Appendix B
Acronyms and Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Index-1
What’s New? Volume 1, General Information includes the following enhancements with respect to
the new Release 1.4 feature set.
1:2 equipment protection and Section 4—Planning and Engineering, Chapter 2—“Network Cabling
3-slot DS3 Electrical using Electrical Connector Modules,” ECM and Module Placement
Connector Module (ECM). Planning Guidelines, page 4-19.
2-port GbE SX plus 16-port Section 2—Hardware Descriptions, Chapter 6—“Ethernet Modules,”
10/100BaseTX module. GbE/Fast Ethernet Combo Modules, page 2-54.
DCS3/1 test access, optical Section 1—System Overview, Chapter 2—“Applications,” New
transmux. Generation Wideband DCS, page 1-16.
Front inlet fan tray (FIFT). Section 2—Hardware Descriptions, Chapter 1—“Traverse Platforms,”
Fan Tray with Fan Module and Air Ramp, page 2-14.
Documentation The Traverse™ system documentation set is comprised of five volumes and is written
Set Description 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 1, This volume provides a detailed overview of the Anyone with the need
General Traverse system. It also includes engineering and to understand the
Information planning information. Traverse system and
its applications.
Volume 2, This volume provides required equipment and Installers, Field and
Installation tools, and step-by-step procedures for: Network Engineers.
and ■ Hardware installation.
Configuration ■ Power cabling.
■ Network cabling.
■ Power-up.
■ Configuration.
Volume 3, This volume provides provisioning concepts Network Engineers,
Provisioning related to the Traverse system. Step-by-step Provisioning and
procedures for provisioning using the TransNav Network Operations
Management System are provided. Center (NOC)
personnel.
Volume 4, This volume provides required equipment and Field and Network
Maintenance tools, and step-by-step procedures for: Engineers.
and Testing ■ Routine maintenance.
■ Module replacement.
■ Alarms and recommended actions.
■ Troubleshooting.
■ Performance monitoring.
■ Loopback tests.
■ Traverse system software upgrade.
Volume 5, This volume provides an overview of the Field and Network
TransNav TransNav™ Management System. It also includes: Engineers,
Management ■ Hardware requirements and third party Provisioning, and
System software requirements. Network Operations
■ Installation instructions for client/server, third Center (NOC)
party, and management system software. personnel.
■ 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.
If You Need If you need assistance while working with Traverse products, contact the Turin
Help 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:
support@turinnetworks.com.
Calling for If repair is necessary, call the Turin Repair Facility at 1-866-TURINET (866-887-4638)
Repairs 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 Facility
Attn: RMA # ________
1415 North McDowell Blvd.
Petaluma, CA 94954 USA
Contents
Chapter 1
Introduction to the Traverse Platform
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Turin Solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Traverse Product Family . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Traverse 2000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Traverse 1600 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Traverse 600 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
Remote Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
Wall Mount Cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
Traverse Capabilities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7
Next Generation SONET/SDH Functionality . . . . . . . . . . . . . . . . . . . . . . 1-7
Integrated Wideband DCS Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7
Integrated Ethernet Switching and Transport . . . . . . . . . . . . . . . . . . . . . 1-7
Shelf and Rack Interface Densities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8
Distributed Switching Architecture. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9
Carrier-Class Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9
Intelligent Control Plane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10
Resource Discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10
Path Calculation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11
Service Signaling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11
TransAccess 100 Mux. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12
Chapter 2
Applications
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13
Multiservice SONET/SDH Transport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14
Integrated DWDM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15
SONET to SDH translational gateway. . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15
Traverse Multiservice SONET/SDH Advantages: . . . . . . . . . . . . . . . . . . 1-15
New Generation Wideband DCS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-16
Key Traverse W-DCS Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-17
Traverse New-Generation W-DCS Advantages: . . . . . . . . . . . . . . . . . . . 1-17
Managed Ethernet Services over SONET/SDH . . . . . . . . . . . . . . . . . . . . . . . 1-18
Traverse Ethernet Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-19
Virtual Concatenation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-20
Link Capacity Adjustment Scheme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-20
Generic Framing Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-21
Traverse Ethernet over SONET/SDH Advantages . . . . . . . . . . . . . . . . . 1-21
List of Figures
Figure 1-1 Traverse 2000 Shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Figure 1-2 Traverse 1600 Shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Figure 1-3 Traverse 600 Shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
Figure 1-4 Traverse 600 Wall Mount Cabinet . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
Figure 1-5 TransAccess 100 Muxes Interconnected to a Traverse Shelf . . . . 1-12
Figure 1-6 Multiservice SONET/SDH Transport Application. . . . . . . . . . . . . . 1-14
Figure 1-7 New Generation Wideband DCS Application . . . . . . . . . . . . . . . . 1-16
Figure 1-8 Integrated Ethernet Switching over SONET/SDH . . . . . . . . . . . . . 1-18
Figure 1-9 Bandwidth Efficiency with Virtual Concatenation. . . . . . . . . . . . . . 1-20
List of Tables
Table 1-1 Traverse Interface Options and Maximum Densities. . . . . . . . . . . 1-8
Chapter 1
Introduction 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.
Traverse Turin Networks Traverse product family is comprised of three scalable platforms
Product Family 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.
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).
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.
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.
Traverse The Traverse platform supports a variety of carrier-class features. The system is
Capabilities developed to enable solutions that service providers can implement in today’s highly
competitive communications markets.
Shelf and Rack Each Traverse shelf provides high maximum switching capacities and interface
Interface densities in a compact footprint to ensure optimal rack space utilization. The table
Densities below shows Traverse interface options, maximum switching capacities, and maximum
interface densities per shelf.
Table 1-1 Traverse Interface Options and Maximum Densities1
2-Port Gigabit Ethernet GbE LX plus 8-Port 18 36/144 144/576 14 28/112 112/448 4 8/32
Fast Ethernet 100BaseFX Combo
1-Port OC-48/STM-16 18 18 72 14 14 56 4 4
1
Unprotected densities.
2
A SONET-only module.
3
An SDH-only module.
Carrier-Class The Traverse platform is engineered to meet the 99.999% availability levels required
Redundancy 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.
Intelligent The Intelligent Control Plane optimizes bandwidth utilization, enables traffic
Control Plane 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.
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.
TransAccess Turin Networks offers the TransAccess 100 STS-1/T1 Mux as a complement to the
100 Mux 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.
DS3/EC1 CC
DS3/EC1 CC
GCM
GCM
Traverse Shelf
10/100BaseT
(connected to DCN
Ethernet interface on
Ethernet Hub the Traverse
backplane)
10/100BaseT
Support for up to 12
TransAccess 100 Muxes
28 DS1 TransAccess 100
The TransNav Management System lets you remotely manage the configuration and
status of the TransAccess 100 Mux.
Chapter 2
Applications
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.
Multiservice SONET and SDH are high-speed optical communications protocols that represent the
SONET/SDH foundation of today’s global optical transport network. As a principal application, the
Transport 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
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.
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
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.
Managed As service providers migrate to a more data-oriented service mix, Ethernet technology
Ethernet is increasingly being deployed as a native connectivity service for ultra-broadband
Services over (business-based) Internet access and Transparent LANs. Ethernet is also deployed as a
SONET/SDH 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.
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
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.
OC-48/STM-16 OC-48/STM-16
without virtual concatenation 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.
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.
Contents
Chapter 1
Traverse Platforms
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Traverse 2000 System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Traverse 2000 Front View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Traverse 2000 Rear View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
Traverse 2000 Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
Traverse 1600 System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
Traverse 1600 Front View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
Traverse 1600 Rear View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
Traverse 1600 Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9
Traverse 600 System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10
Traverse 600 Front View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10
Traverse 600 Rear View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10
Traverse 600 Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12
Interface Options and Densities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14
Fan Tray with Fan Module and Air Ramp . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15
Power Distribution and Alarm Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16
Traverse Dimensions Summary Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-18
Traverse Operating System Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-18
Distributed Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19
Upgrades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19
General Control Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19
Dependability. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-20
Chapter 2
General Control Modules
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-21
General Control Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22
Physical Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-23
Timing Subsystem. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-23
Alarm Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-24
Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-24
Chapter 3
SONET/SDH Modules
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-27
8-Port OC-3/STM-1 Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-28
Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-28
Chapter 4
VC and VT Switching Modules
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-37
VCX Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-38
Specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-38
VT/VC Switch Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-39
Specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-39
Chapter 5
Electrical Modules
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-41
28-Port DS1 XT Module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-42
Specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-42
12-Port DS3/E3/EC-1 Clear Channel Module . . . . . . . . . . . . . . . . . . . . . . . . . 2-43
Specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-43
24-Port DS3/E3/EC-1 Clear Channel Module . . . . . . . . . . . . . . . . . . . . . . . . . 2-44
Specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-44
12-Port DS3/EC-1 Transmux Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-45
Specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-45
21-Port E1 Module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-46
Specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-46
Chapter 6
Ethernet Modules
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-49
8-Port Gigabit Ethernet Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-50
Specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-50
24-Port Fast Ethernet Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-52
Specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-52
GbE/Fast Ethernet Combo Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-54
Specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-54
Chapter 7
TransAccess 100 Mux
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-57
TransAccess 100 STS-1/T1 Mux Description . . . . . . . . . . . . . . . . . . . . . . . . . 2-57
TransAccess 100 Mux Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-58
DS1 Electrical Signal Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-58
STS-1 Electrical Signal Specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-59
Craft Port Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-59
List of Figures
Figure 2-1 Front View of Traverse 2000. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Figure 2-2 Rear View of Traverse 2000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
Figure 2-3 Front View of Traverse 1600. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
Figure 2-4 Rear View of Traverse 1600 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
Figure 2-5 Front View of Traverse 600. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10
Figure 2-6 Rear View of Traverse 600 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10
Figure 2-7 Front View Traverse 1600 Fan Tray . . . . . . . . . . . . . . . . . . . . . . . 2-15
Figure 2-8 PDAP-2S Front View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16
Figure 2-9 PDAP-2S Rear View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17
Figure 2-10 PDAP-4S Front View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17
Figure 2-11 PDAP-4S Rear View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17
Figure 2-12 TransAccess 100 Mux. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-57
List of Tables
Table 2-1 Traverse 2000 Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
Table 2-2 Traverse 1600 Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9
Table 2-3 Traverse 600 Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12
Table 2-4 Traverse Interface Options and Maximum Densities . . . . . . . . . . 2-14
Table 2-5 Fan Tray and Fan Module Specifications . . . . . . . . . . . . . . . . . . . 2-15
Table 2-6 Traverse Component Dimensions. . . . . . . . . . . . . . . . . . . . . . . . . 2-18
Table 2-7 GCM Specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-24
Table 2-8 OC-3/STM-1 IR1 Module Specifications . . . . . . . . . . . . . . . . . . . . 2-28
Table 2-9 OC-12/STM-4 Interface Specifications . . . . . . . . . . . . . . . . . . . . . 2-30
Table 2-10 OC-48/STM-16 Interface Specifications . . . . . . . . . . . . . . . . . . . . 2-32
Table 2-11 OC-192/STM-64 Module Specifications . . . . . . . . . . . . . . . . . . . . 2-34
Table 2-12 VCX Component Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . 2-38
Table 2-13 VT Switch Module Specifications . . . . . . . . . . . . . . . . . . . . . . . . . 2-39
Table 2-14 28-port DS1 Module Specifications. . . . . . . . . . . . . . . . . . . . . . . . 2-42
Table 2-15 12-port DS3/E3/EC-1 Clear Channel Module Specifications . . . . 2-43
Table 2-16 12-port DS3/E3/EC-1 Clear Channel Module Specifications . . . . 2-44
Table 2-17 12-port DS3/EC-1 Transmux Module Specifications. . . . . . . . . . . 2-45
Table 2-18 21-port E1 Module Specifications . . . . . . . . . . . . . . . . . . . . . . . . . 2-46
Table 2-19 GbE Interface Specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-50
Table 2-20 Fast Ethernet (10/100 TX) Interface Specifications . . . . . . . . . . . 2-52
Table 2-21 Power Consumption for Ethernet Combo Modules. . . . . . . . . . . . 2-54
Table 2-22 Fast Ethernet FX Interface Specifications. . . . . . . . . . . . . . . . . . . 2-54
Table 2-23 TransAccess 100 Mux Specifications . . . . . . . . . . . . . . . . . . . . . . 2-58
Table 2-24 DS1 Electrical Signal Specifications . . . . . . . . . . . . . . . . . . . . . . . 2-58
Table 2-25 STS-1 Electrical Signal Specifications . . . . . . . . . . . . . . . . . . . . . 2-59
Table 2-26 Craft Port Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-59
Chapter 1
Traverse 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.
Traverse 2000 The Traverse 2000 platform is a 20-slot, 23-inch, rack-mountable shelf. Optimized for
System 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.
P1 P1
Slots 1–16: Any Service Interface or VT/VC Switch Module GCM Only
Slots 1–18: Any Optical or VT/VC Switch Module Slots 19 and 20
GCM Only Slots 1–16: Any Service Interface or VT/VC Switch Module
Slots 19 and 20 Slots 1–18: Any Optical or VT/VC Switch Module
Slot Numbers
MPX Connectors
Timing Interface
System Alarms
Interfaces
System Alarms
Interfaces
Environmental
Alarms Interfaces
Ethernet
Connection to DCN
Environmental
Alarms Module
Power Terminals Connectors for ECM Electrical Connector
Module (ECM)
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 1600 The Traverse 1600 is a 16-slot, 19-inch rack-mountable shelf. Optimized for access and
System 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.
P1 P1
Slots 1–12: Any Service Interface or VT/VC Switch Module GCM Only
Slots 1–14: Any Optical Service Interface or VT/VC Switch Module Slots 14 and 15
GCM Only Slots 1–12: Any Service Interface or VT/VC Switch Module
Slots 15 and 16 Slots 1–14: Any Optical Service Interface or VT/VC Switch Module
Slot Numbers
MPX Connectors
Timing Interface
System Alarms
Interfaces
Environmental
Alarms Interfaces
Ethernet
Connection to DCN
Environmental
Alarms Module
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.
2
Composite clock output connections are unused.
For more information on ECMs, see Section 4—Planning and Engineering, Chapter
2—“Network Cabling using Electrical Connector Modules,” page 4-17.
Traverse 600 The Traverse 600 system has a smaller physical size than the Traverse 1600 and
System 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.
GCM Only:
Slots 5 and 6
Service Interface
Modules: Slots 1 to 4
3
Composite clock output connections are unused.
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.
Traverse 600 Specifications
This table lists the specifications for the Traverse 600 platform.
Table 2-3 Traverse 600 Specifications
Parameter Specification
System configuration 6-slot shelf:
2 slots for redundant control modules (EGCM1).
4 slots for universal service interface modules.
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 kg
Supported 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 Switch
Extended temperature range –40°C to +65°C
Humidity 90% maximum. Non-condensing
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.
Interface Each Traverse shelf provides high maximum switching capacities and interface
Options and densities in a compact footprint to ensure optimal rack space utilization. The table
Densities below shows Traverse interface options, maximum switching capacities, and maximum
interface densities per shelf.
Table 2-4 Traverse Interface Options and Maximum Densities1
2-Port Gigabit Ethernet GbE LX plus 8-Port 18 36/144 144/576 14 28/112 112/448 4 8/32
Fast Ethernet 100BaseFX Combo
1-Port OC-48/STM-16 18 18 72 14 14 56 4 4
1
Unprotected densities.
2
A SONET-only module.
3
An SDH-only module.
Fan Tray with The Traverse fan tray with fan module cools the GCM and service modules in the shelf.
Fan Module The fan tray draws in cooling air from the front and pushes the air upward through the
and Air Ramp 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.
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.
Power There are two different PDAPs4 available with the Traverse system5, the PDAP-2S and
Distribution PDAP-4S. The PDAP-2S supports up to two and the PDAP-4S supports up to four
and Alarm Traverse shelves and is used with the Traverse 1600 or Traverse 2000 system.
Panel 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.
Circuit Breakers GMT Fuses Alarm LEDs Flange
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.
Battery Supply
NEG VDC Input
Battery Distribution
Battery Return Supply
and Distribution
Chassis Ground
The following illustrations show the front and rear views of the PDAP-4S.
TPA Fuses GMT Fuses Alarm LEDs Flange
T T
P P
A A
GMT GMT
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.
Traverse The following table gives the dimensions for the Traverse components.
Dimensions
Table 2-6 Traverse Component Dimensions
Summary
Table Weight
Weight
Assembly Height Width Depth Fully
Empty
Loaded
Traverse 18.25 in 21.14 in 13.75 in. 16 lb 63 lb
20001 46.34 cm 53.7 cm 34.93 cm 7.2 kg 28.58 kg
Traverse 18.25 in. 17.25 in. 13.75 in 15 lb 52 lb
16001 46.34 cm 43.82 cm 34.93 cm 6.8 kg 23.59 kg
Traverse 6.50 in. 17.25 in. 13.75 in 8 lb 21 lb
600 16.51 cm 43.82 cm 34.93 cm 3.63 kg 9.525 kg
Fan Tray 3.5 in 21.142 12.25 in — 7 lb2
(for 17.253 5 lb3
Traverse 8.75 cm 53.7 cm2 31.12 cm — 3.180 kg2
2000 and 43.82 cm3 2.27 kg3
Traverse
1600)
PDAP 2 in 17 in 16 in — 12 lb
5.08 cm 43.18 cm 40.64 cm — 5.4431 kg
1
Height includes fan tray and depth includes cable covers.
2
Traverse 2000.
3
Traverse 1600.
Traverse The versatility and value of the Traverse system is underpinned by the advanced
Operating architecture and design of the Turin Networks Traverse Operating System software.
System The operating system and future extensions to it have one goal: enable service
Software 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.
7
ATM and IP are planned for a future release.
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.
8
The Traverse OS resides on the GCMs and the SIMs.
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.
Chapter 2
General 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.
General The GCM controls and manages all Traverse shelf modules and services, and the fan
Control Module 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.
Physical GCMs have a RS-232 interface (DB-9) for local technician access and Command Line
Access 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 Each GCM has a timing subsystem, which has a Stratum 3 clock, primary and
Subsystem 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.
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.
Chapter 3
SONET/SDH Modules
8-Port The 8-port OC-3/STM-1 module for the Traverse platform integrates the capabilities of
OC-3/STM-1 a high-performance SONET/SDH ADM and a non-blocking cross connect in a single
Module 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.
1
These values account for the connector loss from connection to the optical interface and the worst case
optical path penalty.
4-Port The four-port OC-12/STM-4 module for the Traverse platform integrates the
OC-12/STM-4 capabilities of a high-performance SONET/SDH ADM and a non-blocking cross
Modules 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.
1
These values account for the connector loss from connection to the optical interface and the worst case
optical path penalty.
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.
Chromatic dispersion
n/a 1600 3200
tolerance (ps/nm)
Guaranteed link
0 to 6 0 to 11 11 to 23 11 to 22 18 to 29
budget,(dB)1
Max optical path
n/a 1 dB 2 dB
penalty
Power consumption 41 watts
Temperature -5°C to +55°C
13.9 H x 1.03 W x 11 D (inches)
Dimensions
35.306 H x 2.616 W x 27.94 D (centimeters)
2.0 (pounds)
Weight
0.9072 (kilograms)
Regulatory Standards NEBS: GR-63-CORE, GR-1089-CORE
Safety: 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.
Specifications
This table lists the specifications for the OC-192/STM-64 modules.
1
These values account for the connector loss from connection to the optical interface and the worst case
optical path penalty.
Chapter 4
VC 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.
VCX The virtual container (VC) cross-connect (VCX) component is connected to any STM
Component 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.
Specifications
This 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
Power consumption 42 watts
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).
VT/VC Switch The VT/VC Switch 2688 module integrates wideband switching and grooming
Module 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.
Specifications
Product specifications for the VT/VC Switch are shown in the table below.
Table 2-13 VT Switch Module Specifications
Parameter Specification
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
Power consumption 42 watts
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).
Chapter 5
Electrical 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.
28-Port DS1 XT The 28-port DS1 Extended Temperature module delivers high-density wideband access
Module 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
Parameter Specification
Maximum modules per shelf Traverse 2000: 16
Traverse 1600: 12
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
Power consumption 49 watts
Dimensions 13.9 H x 1.03 W x 11 D (inches)
35.306 H x 2.616 W x 27.94 D (centimeters)
2.0 (pounds)
Weight
0.9072 (kilograms)
Regulatory Standards NEBS: GR-63-CORE, GR-1089-CORE
Safety: 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 ANSI T1.102, T1.102.
GR-499-CORE, GR-253-CORE.
12-Port The 12-port DS3/E3/EC-1 Clear Channel module delivers high-density broadband
DS3/E3/EC-1 access to the Traverse platform. The module provides asynchronous mapping of ingress
Clear Channel DS3, EC-1, or E3 line signals into a SONET or SDH signal, which are
Module 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
Specification
Parameter
DS3 Value E3 Value EC-1 Value
Maximum Traverse 2000: 16
modules per shelf Traverse 1600: 12
Protection Switching 1:1 or 1:2 Equipment Protection
Bit rate 44.736 Mbps +/–20 ppm 2.048 Mbps, +/–50 51.840 Mbps +/–20
bps (+/–32 ppm) ppm
Frame format C-bit and M23 (per E3 framing per G.751 EC-1 framing (per
GR-499, ANSI T1.107) or G.832 GR-253 and ANSI
Unframed (per GR-499) 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
Power consumption 42 watts
Dimensions 13.9 H x 1.03 W x 11 D (inches)
35.306 H x 2.616 W x 27.94 D (centimeters)
2.0 (pounds)
Weight
0.9072 (kilograms)
Regulatory Stan- NEBS: GR-63-CORE, GR-1089-CORE
dards Safety: 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 G.751, G.832
ANSI T1.105, T1.107
Bellcore: GR-499-CORE, GR-253-CORE
24-Port The 24-port DS3/EC-1 Clear Channel module delivers high-density broadband access
DS3/E3/EC-1 to the Traverse platform. The module provides asynchronous mapping of ingress DS3,
Clear Channel EC-1, or E3 line signals into a SONET or SDH signal, which are switched
Module (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
Specification
Parameter
DS3 Value E3 Value EC-1 Value
Maximum modules Traverse 2000: 16
per shelf Traverse 1600: 12
Protection Switching 1:1 or 1:2 Equipment Protection
Bit rate 44.736 Mbps +/–20 ppm 2.048 Mbps, +/–50 51.840 Mbps +/–20
bps (+/–32 ppm) ppm
Frame format C-bit and M23 (per E3 framing per G.751 EC-1 framing (per
GR-499, ANSI T1.107) or G.832 GR-253 and ANSI
Unframed (per GR-499) 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
Power consumption 42 watts
Dimensions 13.9 H x 1.03 W x 11 D (inches)
35.306 H x 2.616 W x 27.94 D (centimeters)
2.0 (pounds)
Weight
0.9072 (kilograms)
Regulatory Stan- NEBS: GR-63-CORE, GR-1089-CORE
dards Safety: 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 G.751, G.832
ANSI T1.105, T1.107
Bellcore: GR-499-CORE, GR-253-CORE
Specifications
This table lists product specifications for the DS3/EC-1 Transmux module
21-Port E1 The 21-port E1 Extended Temperature module delivers high-density wideband access
Module 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.
Chapter 6
Ethernet Modules
8-Port Gigabit The single-slot 8-Port Gigabit Ethernet (GbE) module is based on Ethernet
Ethernet transmission standards and provides native rate access with its high throughput and
Module 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.
1
These values account for the connector loss from connection to the optical interface and the worst case
optical path penalty.
24-Port Fast The single-slot 24-port Fast Ethernet (10/100BaseTX) module is based on Ethernet
Ethernet transmission standards and provides native rate access with its high throughput and
Module 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 (continued)
Parameter Specification
Dimensions 13.9 H x 1.03 W x 11 D (inches)
35.306 H x 2.616 W x 27.94 D (centimeters)
Weight 2.1 lbs
0.9525 kg
Regulatory Standards NEBS: GR-63-CORE, GR-1089-CORE
Safety: UL60950, EN 60950, IEC 60950, CSA C2.22 No. 60950
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.957
ANSI: T1.105, T1.107
Bellcore GR-253-CORE, GR-1377-CORE
IEEE: 802.3u/x/ad, 802.1D/p/Q VLAN
GbE/Fast Turin Networks offers the following single-slot Gigabit/Fast Ethernet interface combo
Ethernet modules:
Combo ■ 2-port GbE LX plus 8-port 100BaseFX
Modules 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/100BaseTX
2-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/100BaseTX
2-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.
1
These values account for the connector loss from connection to the optical interface and the worst case
optical path penalty.
Chapter 7
TransAccess 100 Mux
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.
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.
TransAccess This table lists the specifications for the TransAccess 100 Mux equipment.
100 Mux
Table 2-23 TransAccess 100 Mux Specifications
Specifications
Specification Description
Low-speed channel capacity Up to 28 lines of 1.544 Mbps data
Multiplexed data rate 51.840 Mbps ± 20 ppm
Signal interface 51.840 Mbps ± 20 ppm
Line impedance 75 ohms ± 5% unbalanced
Reframe time STS1: 2 ms
Operating mode Full duplex
Power consumption 45 Watts maximum
Weight 8 lb. (3.6287 kg) fully loaded
DS1 Electrical This table lists the specifications for the DS1 signals.
Signal
Table 2-24 DS1 Electrical Signal Specifications
Specifications
Specification Description
Nominal line 1.544 Mbps ± 130 ppm
AIS line rate 1.544 Mbps ± 32 ppm
Line code Half-width bipolar AMI or B8ZS
Termination One balanced twisted pair for each direction of transmission
Impedance 100 ohms ± 5% (balanced)
Pulse shape Meets TR-TSY-000499 mask with amplitude of between 2.4
and 3.6 volts1
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 kHz
Pulse imbalance Less than 0.5 dB difference between total power of positive
and negative pulses
Jitter generation Less than 0.3 time slots RMS
Cable ABAM or equivalent
Maximum span 655 feet to cross connect
1
A 100 ohms T1 patch cable is required when measuring the pulse mask.
STS-1 This table lists the specifications for the EC1 signals.
Electrical
Table 2-25 STS-1 Electrical Signal Specifications
Signal
Specifications Specification Description
Nominal line 51.840 Mbps ± 20 ppm
Line 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 peak
Pulse imbalance Less than 3.5 dB difference between total power
of positive and negative pulses
Jitter generation Less than 0.3 time slots RMS
Cable 728A RG-6U or equivalent
Maximum span 450 feet to the STX cross connect
Craft Port The TransAccess 100 Mux’s technician access craft port is used to set the IP address
Specifications 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.
Specification Description
TransAccess The TransAccess 100 Mux complies with the following industry standards:
100 Mux ■ FCC Part Class A.
Compliance ■ UL 1950.
Standards ■ CSA 22.2.
■ GR-499-CORE, GR-253-CORE.
■ GR-1089, GR-63 (NEBS compliant).
Contents
Chapter 1
TransNav Management System Overview
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
What Is the TransNav Management System?. . . . . . . . . . . . . . . . . . . . . . . . . 3-1
TransNav Software Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Client Workstation Application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Management Server Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Node Agent Application. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
TransNav Management System Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Interoperability with Third-party Management Systems . . . . . . . . . . . . . . . . . 3-4
Autodiscovery and Preprovisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
Simultaneous Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
Scalability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
Reliability, Availability and Serviceability (RAS) . . . . . . . . . . . . . . . . . . . . . . . 3-5
Chapter 2
Network Management Features
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
Fault and Event Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
Alarm Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
Data Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
Flexible Filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
Flexible Scoping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
Sorting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
Clearing Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
Configuration Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
Equipment Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
Preprovisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
Service Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
Accounting Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
Performance Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
Security Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
Node Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
System Log Collection and Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
Report Generation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11
General Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11
Data Set Snapshots. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11
Chapter 3
User Interfaces
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13
TransNav System Access Methods. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13
Graphical User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14
Map View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14
Shelf View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15
Command Line Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16
Domain Level. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16
Node Level. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16
Chapter 4
Management System Requirements
TransNav Management System Requirements. . . . . . . . . . . . . . . . . . . . . . . . 3-17
TransNav Management Server Hardware Requirements . . . . . . . . . . . . . . . . 3-18
Sun Solaris Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18
Windows 2000 Professional Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-19
TransNav Management Server Software Requirements . . . . . . . . . . . . . . . . . 3-21
TransNav Client Workstation Hardware Requirements . . . . . . . . . . . . . . . . . . 3-22
TransNav GUI Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-23
List of Figures
Figure 3-1 TransNav Software Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Figure 3-2 Map View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14
Figure 3-3 Shelf View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15
List of Tables
Table 3-1 Access Groups and Rights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
Table 3-2 Accessing the TransNav Management System. . . . . . . . . . . . . . . 3-13
Table 3-3 Server Hardware Recommendations to Support up to 50 Nodes . 3-18
Table 3-4 Server Hardware Recommendations to Support up to 100 Nodes 3-19
Table 3-5 Server Hardware Requirements for Windows 2000 Professional . 3-19
Table 3-6 Server Software Requirements for Sun Solaris . . . . . . . . . . . . . . . 3-21
Table 3-7 Server Software Requirements for Windows 2000 Professional . . 3-21
Table 3-8 Minimum Requirements for Client Hardware. . . . . . . . . . . . . . . . . 3-22
Table 3-9 Minimum Requirements for GUI Software . . . . . . . . . . . . . . . . . . . 3-23
Chapter 1
TransNav Management System Overview
What Is the The TransNav Management System is an advanced element and subnetwork
TransNav management system designed for comprehensive management of the TransNav
Management network. The Java™-based TransNav software smoothly integrates into existing
System? 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.
TransNav The TransNav Management System is an all Java-based, highly integrated system that
Software uses the identical architecture on the Traverse network nodes and the management
Functional server(s). The architecture leverages the Java Dynamic Management Kit (JDMK)
Description implementation of Java Management extensions (JMX) to provide an efficient
client-server 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 The client workstation application provides the user interface for managing the
Workstation network. The TransNav Management System supports both a graphical user interface
Application (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.
Management The management server application communicates with nodes and provides classical
Server element management FCAPS functionality (fault, configuration, accounting,
Application 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 Each node has a redundant GCM with a persistent relational database management
Application 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 The TransNav Management System provides comprehensive management for both the
Management nodes and for the connections between nodes through the Intelligent Control Plane.
System This specifically includes efficient integration of management plane and control plane
Features 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.
Autodiscovery Each node uses a process called autodiscovery to learn the addresses of all equipment
and in its control plane domain. The CLI is used to enter the host name or IP address of the
Preprovisioning 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 The number of simultaneous users depends on whether the management server is
Users 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.
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, Turin works closely with customers to configure hardware and software to achieve
Availability and desired levels of high availability for their Sun Solaris server-based TransNav system
Serviceability deployments. This includes supporting secondary network operation centers for
(RAS) disaster recovery. Our goal is to achieve exceptional service reliability and availability
in a cost-effective manner.
Chapter 2
Network Management Features
Fault and The TransNav Management System GUI enables each technician to open multiple
Event alarm windows. The number of windows is limited only by effective use of the
Management 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
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 Use the TransNav Management System for all configuration management
Management requirements:
■ Equipment Configuration, page 3-8.
■ Preprovisioning, page 3-8.
■ Service Provisioning, page 3-9.
Equipment Once a node is installed and activated, it discovers its specific components and
Configuration 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.
Service The TransNav Management System provides end-to-end provisioning of services and
Provisioning 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 Accounting data for all services is based primarily on performance management data
Management 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 Nodes collect performance management data and forward it to the management server
Management 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 Security management refers to the establishment of management user accounts with
Management 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
Node The TransNav Management System provides the following capabilities to support
Administration 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 The TransNav Management System collects a broad array of information that is stored
Collection and in the server database for reporting and analysis.
Storage 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.
Report All reports can be printed or exported as text-formatted comma delimited files.
Generation 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.)
Chapter 3
User 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 The following table lists the different access methods you can use to connect to the
System Access TransNav management server.
Methods
Table 3-2 Accessing the TransNav Management System
Management System
Access Method
Interface
Graphical User The GUI supports operators and administrators who are located in a network operations
Interface 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.
Menu bar
Currently selected
object
Context
sensitive tabs
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.
Menu bar
BITS clock
Context
sensitive tabs
Command Line You can also access the TransNav Management System using a command line interface
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 4
Management System Requirements
TransNav The TransNav Management System CD software package contains both server and
Management client workstation applications. The server functions communicate with the nodes and
System maintain a database of topology, configuration, fault, and performance data for all
Requirements 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.
TransNav Use the information in this section to help determine TransNav Management System
Management server hardware requirements for your network. You can operate a management server
Server using either a Sun Solaris platform or a Windows 2000 Professional platform.
Hardware ■ Sun Solaris Server, page 3-18.
Requirements ■ Windows 2000 Professional Server, page 3-19.
Sun Solaris TransNav system server software is supported on the following desktop server
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.
Component Description
Component Description
Windows 2000 Use Windows 2000 Professional server for smaller networks (15 or fewer nodes) and 5
Professional or fewer simultaneous users. Table 3-5 provides hardware configuration requirements
Server for the Windows 2000 Professional operating environment.
Component Description
Component Description
TransNav Use the information in this section to determine the management server software
Management requirements for your network. You can operate the management using either of the
Server following operating environments:
Software ■ Sun Solaris platform (Table 3-6)—larger networks (more than 15 nodes), more
Requirements than 5 simultaneous users.
■ Windows 2000 professional platform (Table 3-7)—smaller networks (15 nodes or
less), 5 or fewer simultaneous users.
Component Description
Component Description
TransNav To access the TransNav management server from the graphical user interface (GUI),
Client you require a client workstation. Access the GUI by installing the application directly
Workstation on the client workstation or through a Web browser using an applet.
Hardware Turin recommends installing the application directly on the client workstation for faster
Requirements 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
Component Description
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.
TransNav GUI The following table lists the software required to install the GUI application on either
Software the Sun Solaris, Microsoft Windows NT, or Windows 2000 operating environments.
Requirements
Table 3-9 Minimum Requirements for GUI Software
Component Description
Contents
Chapter 1
Traverse Specifications
Traverse Shelf Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
Module Placement Guidelines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Traverse Dimensions Summary Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
Traverse Rack Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
Fan Tray with Integrated Air Ramp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7
Power Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7
Power Distribution and Alarm Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8
Power Cabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9
Power Consumption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10
General Control Modules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10
SONET/SDH Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10
Electrical Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11
Ethernet Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11
Shelf Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11
Fiber Optic Module Cabling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12
Electrical Coax and Copper Module Cabling. . . . . . . . . . . . . . . . . . . . . . . . . . 4-12
Traverse Interface Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13
Fiber Connector Shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14
Shelf and Rack Density . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14
Regulatory Compliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15
Chapter 2
Network Cabling using Electrical Connector Modules
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-17
ECM Placement at the Traverse Main Backplane. . . . . . . . . . . . . . . . . . . . . . 4-18
ECM and Module Placement Planning Guidelines . . . . . . . . . . . . . . . . . . . . . 4-19
Electrical Connection Module Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-20
Cable Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21
Chapter 3
TransAccess 100 Mux
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-23
Power Distribution Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-23
Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-24
Integration with Traverse System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-24
Interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-25
Environmental . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-25
List of Figures
Figure 4-1 Traverse 2000 Shelf Front View . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
Figure 4-2 Traverse Mounting Heights Using PDAP-2S in a 23-Inch Rack . . 4-5
Figure 4-3 Four Traverse 1600 Shelves and the PDAP-4S in a
Single Rack Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6
Figure 4-4 PDAP-2S Power Cabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9
Figure 4-5 PDAP-4S Power Cabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9
Figure 4-6 Electrical Connector Modules (Front View) . . . . . . . . . . . . . . . . . . 4-17
Figure 4-7 2-Slot ECM Placement—Traverse 2000 Main Backplane . . . . . . 4-18
Figure 4-8 Traverse Shelf with Cable Management Bar . . . . . . . . . . . . . . . . . 4-21
Figure 4-9 TransAccess 100 Mux Shelf Interconnection to Traverse Shelf . . 4-24
List of Tables
Table 4-1 Module Placement Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Table 4-2 Redundancy Rules for GCM Types . . . . . . . . . . . . . . . . . . . . . . . . 4-3
Table 4-3 Traverse Component Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
Table 4-4 Power Distribution Per Traverse Module . . . . . . . . . . . . . . . . . . . . 4-10
Table 4-5 Traverse Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13
Table 4-6 Traverse Interface Options and Maximum Densities. . . . . . . . . . . 4-14
Table 4-7 Regulatory Compliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15
Table 4-8 Electrical Connector Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-20
Table 4-9 TransAccess 100 Mux Dimensions . . . . . . . . . . . . . . . . . . . . . . . . 4-23
Table 4-10 TransAccess 100 Mux Power Specifications. . . . . . . . . . . . . . . . . 4-24
Table 4-11 TransAccess 100 Mux Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . 4-25
Table 4-12 TransAccess 100 Mux Environmental Specifications . . . . . . . . . . 4-25
Table 4-13 TransAccess 100 Mux Relay Contact Closure Ratings . . . . . . . . . 4-25
Chapter 1
Traverse Specifications
Traverse Shelf Traverse systems consist of General Control Modules (GCMs), VT/VC switch
Configuration 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.
P1 P1
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.
Module The following table provides guidelines for placement of modules in a Traverse shelf:
Placement
Guidelines
Table 4-1 Module Placement Guidelines
Traverse Traverse
Module Type 1600 2000 Comments
Slot #s Slot #s
GCM, GCMA and GCMA and Redundant GCMs are recommended for equipment protection.
Enhanced GCM (EGCM), GCMB GCMB However, if only one GCM is used it can be placed in either slot
GCM OC-12/STM-4, (slots 15 and (slots 19 and GCMA or GCMB.
GCM OC-48/STM-16 16) 20)
Redundant GCMs can be different types. See Table 4-2
Redundancy Rules for GCM Types below.
DS1, 1–12 1–16 In a 1:1 equipment protection scheme1, the module to the left
DS3/E3/EC-1 CC (12-port), protects the right-adjacent working module. In an unprotected
DS3/E3/EC-1 CC (24-port), scheme, place modules in any valid slot; the 2-slot DS3/E3
DS3/EC-1 TMUX electrical connector module (ECM) provides access to only the
E1 right-most DS3/E3/EC-1 module so place an optic module in the
left-most slot.
10/100BaseTX, 1–12 1–16 Use the following module placement options when placing any
GbE LX plus 10/100BaseTX-inclusive modules in a Traverse shelf with DS1,
10/100BaseTX Combo, DS3/E3/EC-1 CC, DS3/EC-1 TMUX, or E1 modules:
GbE SX plus ■ Place an OC-N/STM-N module or place a 1-slot wide blank
10/100BaseTX Combo faceplate between the 10/100BaseTX and an electrical interface
module, if the 10/100BaseTX-inclusive module is placed to the
right of the electrical interface module.
or
■ Place 10/100BaseTX-inclusive modules directly to the left of
DS1, DS3/EC-1/EC-1 CC, or DS3/EC-1 TMUX or E1 modules.
An OC-N/STM-N module or 1-slot wide blank faceplate is not
required if the 10/100BaseTX-inclusive modules are placed to
the left of electrical interface modules.
Traverse Traverse
Module Type 1600 2000 Comments
Slot #s Slot #s
OC-192/STM-64 1/2, 3/4, 5/6, 1/2, 3/4, 5/6, The OC-192/STM-64 modules require two slots for placement.
7/8, 9/10, 7/8, 9/10, The left side of the OC-192/STM-64 module is placed in an odd
11/12, and 11/12, 13/14, numbered slot.
13/14 15/16, and
17/18
VT Switch (2688) 1–14 1–18 In a 1:1 equipment protection scheme, the working and protection
VT 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 backplane
design supporting only 1:1 protection schemes.
GCM GCM
GCM EGCM1
EGCM1 GCM
EGCM EGCM
2
GCM OC-N/STM-N 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.
Traverse The following table gives the dimensions for the Traverse components.
Dimensions
Table 4-3 Traverse Component Dimensions
Summary
Table Weight
Weight
Assembly Height Width Depth Fully
Empty
Loaded
PDAP 2 in 17 in 16 in — 12 lb
1
Height includes fan tray and depth includes cable covers.
2
Traverse 2000.
3
Traverse 1600.
Traverse Rack The Traverse 1600 shelf can be installed in either a standard 19-inch or 23-inch wide
Configuration 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.
SD
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.
Figure 4-3 shows an example of four Traverse 1600 shelves installed with the
PDAP-4S in a 19-inch wide relay rack.
SD
PDAP-4S
P1 P1
Traverse 1600
Traverse 1600 P1 P1
Traverse 1600 P1 P1
Traverse 1600 P1 P1
Fan Tray with The Traverse fan tray with fan modules cools the GCM and service modules in the
Integrated Air shelf. The fan tray draws in cooling air from the front and pushes the air upward
Ramp 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 There are two different PDAPs3 available with the Traverse system, the PDAP-2S and
Requirements 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.
Power The PDAP-2S can be installed in a 19 or 23-inch wide telco rack. It is 2 inches high, 17
Distribution inches wide, and 16 inches deep. It weighs 12 pounds. It provides circuit breakers for
and Alarm up to two Traverse shelves and GMT fuses for auxiliary equipment. The PDAP-4S can
Panel 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.
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.
Battery “B” Distribution Battery and Battery Return Battery “A” Distribution
Bus Bars
T T
P P
A A
GMT GMT
Please refer to Volume 2, Installation and Configuration, for detailed instructions for
power cabling.
Power The power draw of the Traverse system is dependent on the configuration of each
Consumption 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.
1-Port OC-48/STM-16 SR 41
21-Port E1 49
VT Switch 42
24-Port 10/100BaseTX 55
PDAP-2S <1
PDAP-4S <1
Fiber Optic The Traverse backplane allows each optical Service Interface Module (SIM) to
Module terminate up to 48 fibers, or support up to 24 optical interfaces. It has female duplex
Cabling 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 The DS3/E3/EC-1 Clear Channel and DS3/EC-1 Transmux modules are cabled using
and Copper standard coax cables with BNC or SMB connectors. Coax cables are connected to the
Module DS3/E3 electrical connector module (ECM) at the main backplane. The main
Cabling 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.
Traverse This table lists reach and rate information for the optical modules and connector type
Interface Types for the electrical interface modules.
Interface
Rate Module Description
Type
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.
Fiber Fiber cable from the fiber optic connector shelf connects to the Traverse optical
Connector backplane using an MPX female connector. All connectors have a precise alignment
Shelf mechanism to provide quick and easy installation.
Shelf and Rack Each Traverse shelf provides high maximum switching capacities and interface
Density 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 4-6 Traverse Interface Options and Maximum Densities1
2-Port Gigabit Ethernet GbE LX plus 8-Port 18 36/144 144/576 14 28/112 112/448 4 8/32
Fast Ethernet 100BaseFX Combo
1-Port OC-48/STM-16 18 18 72 14 14 56 4 4
1
Unprotected densities.
2
A SONET-only module.
3
An SDH-only module.
Specification Description
SR-3580, Level 3
NEBS GR-63-CORE
GR-1089-CORE
Safety UL 60950, EN 60950, IEC 60950, CSA C2.22 No. 60950
FCC Part 15, Class A
EMI EN 300 386
EN 55022, Class A
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
Environmental 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 2
Network 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.
DS1/E1 ECM DS3/E3 ECM 10/100BaseT ECM DS3/E3 ECM DS3/E3 ECM
(Telco 64) (24 BNC) (Telco 50) (48 BNC) (96 Mini-SMB)
ECM The ECMs plug into the main backplane 2 mm connectors of any corresponding odd or
Placement at even slot1. The 2-slot ECM occupies the width of two slots and the 3-slot ECM
the Traverse occupies the width of three slots on the main backplane. For example, the 2-slot ECM
Main for slots 1 and 2 plugs into the 2 mm connectors of slot 1. The following graphic shows
Backplane slot 1 main backplane 2 mm connectors in dark grey, and the outline of the 2-slot ECM
in light grey.
20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
2-slot ECM
Slot 1
Connectors
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.
ECM and Since ECMs are two and three slots in width and different protection schemes, the
Module following guidelines apply for module placement planning and cabling:
Placement 1. 1:2 equipment protection module placement.
Planning – Using a 3-slot DS3/E3 ECM, place like modules (12- or 24-port DS3/E3/EC-1
Guidelines 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.
Electrical The following table provides port, connector and cable information for each type of
Connection ECM. The total number of ports supported for each ECM is based on like modules
Module Types placed adjacently in the shelf.
Total # of Ports
Type of EMC
ECM Type 1:2 1:1 Cable Description
Connectors
Equipment Equipment Unprotected
Protection Protection
DS1/E1
56 28 56
(DS1 ports) (4) female Telco 64 Copper 32-pair cable, 24 AWG,
(CHAMP) with 180º male Telco 64
DS1/E1 connector.
42 21 42
(E1 ports)
Cable Copper and coax cables are tie-wrapped to a cable management bar mounted across the
Management 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.
Cable
Management
Bar
Route
Copper/Coax
Cables to the
Right Side of
the Traverse
Shelf
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.
Chapter 3
TransAccess 100 Mux
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.
Weight
Height Depth Width
Fully Loaded
1
Cover to tie bars.
2
Without mounting brackets.
Power The TransAccess 100 Mux requires a separate power distribution unit2 (PDU). Turin
Distribution Networks recommends the ADC power distribution unit. The PDU should be installed
Unit in the same rack as the TransAccess 100 Mux.
1
Mounting brackets are provided with each TransAccess 100 Mux.
2
The PDAP provides power distribution for the Traverse shelves only. A separate PDU must be installed
for TransAccess 100 Mux deployments.
Power
Table 4-10 TransAccess 100 Mux Power Specifications
Specification Description
Integration Up to twelve TransAccess 100 Muxes can be connected to one Traverse 12-port
with Traverse DS3/EC-1 Clear Channel module. A single Traverse 1600 node using six redundant
System 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.
.
Traverse
P1 P1 P1 P1 P1 P1
P2 P2
P3 P3
P4 P4
P5 P5
P6 P6
P7 P7
P8 P8
P9 P9
P10 P1 0
GCM
P11 P1 1
P12 P1 2
DS3/EC-1
Clear
Channel
EC-1 10/100BaseT
SD
Li n k St a t u s Ln
i k S ta tu s P ac k et
Ethernet Hub
ET H E RN E T P O R T Fa li Co l l si i o n F ai l
A c t iv e Pa c ke t A ct i v e
1 2 3 4 5 6 7 8 9 10 11 12 C on s oe
l
Ethernet
Hub 1 2 3 4 5 6 7 8 9 10 11 12
A TM SV S
PO R T S T A TU S
28 DS1 1
28 DS1 2
28 DS1 12 maximum
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.
Interfaces
Table 4-11 TransAccess 100 Mux Interfaces
Specification Description
Environmental
Table 4-12 TransAccess 100 Mux Environmental Specifications
Specification Description
Relay Contacts
Table 4-13 TransAccess 100 Mux Relay Contact Closure Ratings
Contents
Appendix A
Compliance
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
Compliance and Certification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
ETSI Environmental Standards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
NEBS Compliance and Certification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
UL and FCC Standards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
Reliability at Turin Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
Reliability Development. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
Reliability in Production . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3
Appendix B
Acronyms and Abbreviations
Acronyms and Abbreviations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5
SONET/SDH Channel Capacities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17
VT/VC Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17
List of Tables
Table 5-1 SONET/SDH Digital Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17
Table 5-2 Virtual Tributary/Virtual Container Hierarchy. . . . . . . . . . . . . . . . . 5-17
Appendix A
Compliance
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 CE Mark has been obtained for all products destined for the European
and Telecommunications Standards Institute (ETSI) market. CE Mark on Turin’s products
Certification 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 In addition to the testing required for CE Mark, Turin’s products are also tested to the
Environmental following ETSI specifications:
Standards ■ 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 Network Equipment-Building Systems (NEBS) standards define a rigid and extensive
Compliance set of performance, quality, environmental, and safety requirements developed by
and Telcordia.
Certification 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.
■ 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 The Traverse 1600, Traverse 2000, and Traverse 600 system is being tested to the
Standards requirements of UL 60950 and FCC part 15.
Reliability at The Traverse 1600 and Traverse 2000 systems can be configured in the network in
Turin Networks 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 During product development, reliability growth is achieved primarily through Highly
Development 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.
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 The production process includes a comprehensive suite of tests, designed to ensure
Production 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.
Appendix B
Acronyms and Abbreviations
Acronyms and Acronyms are formed from the initial letter or letters of each of the successive parts or
Abbreviations major parts of a compound term. Turin Networks uses the following set of acronyms
and abbreviations in product literature and documentation.
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
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)
Numerics D
1:1 equipment protection Data communications network (DCN)
module placement, 4-19 connectivity, 2-4, 2-8, 2-11
Data rate
A DS1 module, 2-42
DS3/EC-1 clear channel module, 2-43, 2-44, 2-45
Alarms
E1 module, 2-46
alarm windows, GUI, 3-7
Dataset snapshots, 3-11
clearing alarms, 3-7
Dimensions
Autodiscovery, 3-4
PDAP, 4-9
Intelligent Control Plane, 3-8
TransAccess 100 Mux, 4-23
intelligent control plane, 1-10
Traverse 1600 shelf, 2-17, 4-5
B Traverse 2000 shelf, 2-17, 4-5
Traverse 600 chassis, 2-17, 4-5
Backplane Distributed architecture
BITS input timing interfaces, 2-4, 2-8, 2-11 features, 2-18
data communications network, 2-4, 2-8, 2-11 Domain
description, 2-3, 2-7, 2-10 Management server, 3-17
environmental alarm module, 2-4, 2-8, 2-11 Domain-level CLI, 3-4
receptacles for fiber connectors, 2-3, 2-7, 2-11 DS1 module
timing references, input and output, 2-3, 2-7, 2-11 front view (figure), 2-42
power consumption, 2-42
C specifications, 2-42
Cables DS3 module
electrical coax, 4-13 electrical coax cabling, 4-13
fiber optic, 4-13 DS3/EC-1 clear channel module
fiber optic connectors, 4-13 data rate, 2-43, 2-44, 2-45
CE Mark, 5-1 front view (figure), 2-43, 2-44
Circuit breakers power consumption, 2-43, 2-44, 2-45
PDAP, 2-15, 4-9 specifications, 2-43, 2-44, 2-45
CLI DS3/EC-1 transmux module
domain-level, 3-16 front view (figure), 2-45
node-level, 3-16
Client hardware recommendations, 3-22 E
Client workstation software recommendations, 3-23 E1 module
Command Line Interface (CLI) power consumption, 2-46
domain-level CLI, 3-4 specifications, 2-46
node-level CLI, 3-10 Electrical connector modules (ECM)
Compliance and certification, 5-1, 5-2 descriptions, 4-17
Configuration management placement, 4-18
equipment configuration, 3-8 placement planning guidelines, 4-19
preprovisioning, 3-8 types, 4-20
service provisioning, 3-9 Electro-Magnetic Compatibility (EMC), 5-1
Craft access EMI, 4-16
interface, 2-3, 2-7, 2-10 Environmental alarm module
interfaces, 2-15, 4-8 backplane, 2-4, 2-8, 2-11
Environmental alarms, 2-4, 2-8, 2-11
Environmental specifications, 4-16
G M
General control Management Plane, 3-8
redundancy, 2-18 Management server
General Control Module hardware requirements, 3-18
redundancy, 2-18 software requirements, 3-21
remote restore, 3-10 Management System
General reports, 3-11 accounting management, 3-9
GMPLS, 1-10 alarm data, 3-7
GMT fuses clearing alarms, 3-7
PDAP, 2-15, 4-9 dataset snapshots, 3-11
Graphical user interface (GUI) domain-level CLI, 3-4
description, 3-14 equipment provisioning, 3-8
fault and event management, 3-7 fault management, 3-7
hardware requirements, 3-22 flexible filtering, 3-7
performance management, 3-9 flexible scoping, 3-7
software requirements, 3-23 general reports, 3-11
Management Plane, 3-8
H node-level CLI, 3-10
Hardware performance management, 3-9
Management server hardware requirements, 3-18 preprovisioning, 3-8
Hardware requirements report generation, 3-11
Graphical user interface, 3-22 security management, 3-9
Management server, 3-18 service provisioning, 3-9
High Availability Framework (HAF), 2-19 system log collection and storage, 3-10
Highly Accelerated Life Testing (HALT), 5-2 Modem interface, 2-4, 2-8, 2-11
Highly Accelerated Stress Screening (HASS), 5-3 Module cabling, 4-13
electrical coax, 4-13
fiber optic, 4-13