Download pdf - Force10 Networks Inc....Force10 Networks Inc. TraverseEdge 100 System Documentation Release TE3.2.x Publication Date: June 2008 Document Number: 800-0010-TE322 Rev. B User Guide Release

Force10 Networks Inc.

TraverseEdge 100 System Documentation

Release TE3.2.xPublication Date: June 2008

Document Number: 800-0010-TE322 Rev. B

User Guide

Copyright © 2008 Force10 Networks, Inc.

All rights reserved. Force10 Networks ® reserves the right to change, modify, revise this publication without notice.

TrademarksForce10 Networks® and E-Series® are registered trademarks of Force10 Networks, Inc. Traverse, TraverseEdge, TraversePacketEdge, TransAccess, are registered trademarks of Force10 Networks, Inc. Force10, the Force10 logo, and TransNav are trademarks of Force10 Networks, Inc. or its affiliates in the United States and other countries and are protected by U.S. and international copyright laws. All other brand and product names are registered trademarks or trademarks of their respective holders. Statement of ConditionsIn the interest of improving internal design, operational function, and/or reliability, Force10 Networks, Inc. reserves the right to make changes to products described in this document without notice. Force10 Networks, Inc. does not assume any liability that may occur due to the use or application of the product(s) described herein.

TRAVERSEEDGE 100 USER GUIDE

ContentsAbout this Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v

Section 1 Product Overview and ApplicationsChapter 1Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1Chapter 2Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

Section 2 Product Description and SpecificationsChapter 1Platform Description and Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1Chapter 2Electrical Ports Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11Chapter 3Ethernet Ports Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17Chapter 4SONET/STM Ports Specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-21Chapter 5Alarm Interface Specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-27Chapter 6Timing Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-31Chapter 7Management Interfaces Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-35Chapter 8Power Interface Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-39Chapter 9Network Topologies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-43

Section 3 Installation and ConfigurationChapter 1Installation Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1Chapter 2Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3Chapter 3Common Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9Chapter 4Hardware Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-25Chapter 5Alarm Interface Cabling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-31Chapter 6Timing Interface Cabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-39Chapter 7Power Cabling Procedures—DC/DC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-45Chapter 8Power Cabling Procedures—AC/DC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-57

Release TE3.2.x Force10 Networks Page i

TraverseEdge 100 User Guide

Chapter 9Management Interfaces Cabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-63Chapter 10Node Start-up and Initial Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-69Chapter 11Network Interface Cabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-79Chapter 12Cable Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-87

Section 4 Provisioning the NetworkChapter 1Configuring the Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1Chapter 2Configuring Network Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9Chapter 3Creating a UPSR/SNCP Protection Group . . . . . . . . . . . . . . . . . . . . . . . . . . 4-17Chapter 4Creating 1+1APS/MSP Protection Groups . . . . . . . . . . . . . . . . . . . . . . . . . . 4-23Chapter 5Creating a 1+1 Optimized Protection Group . . . . . . . . . . . . . . . . . . . . . . . . . 4-27

Section 5 Creating TDM ServicesChapter 1Service Creation Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1Chapter 2Service Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7Chapter 3Common Procedures for Creating Services . . . . . . . . . . . . . . . . . . . . . . . . . 5-13Chapter 4Configuring SONET Equipment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17Chapter 5Creating SONET Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-33Chapter 6Configuring SDH Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-43Chapter 7Creating SDH Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-59

Section 6 Creating Ethernet ServicesChapter 1Ethernet Services Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1Chapter 2Configuring Ethernet Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5Chapter 3Ethernet Over SONET or SDH (EOS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-25Chapter 4Link Capacity Adjustment Scheme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-37Chapter 5Rapid Spanning Tree Protocol. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-47

Page ii Force10 Networks Release TE3.2.x


Chapter 6Ethernet Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-57Chapter 7Ethernet Traffic Management on the TE-100 . . . . . . . . . . . . . . . . . . . . . . . . 6-71

Section 7 AppendicesAppendix AInstallation and Commissioning Checklists . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1Appendix BProvisioning Checklists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-17Appendix CAcronyms and Abbreviations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-25

Index

Release TE3.2.x Force10 Networks Page iii


Page iv Force10 Networks Release TE3.2.x

TraverseEdge 100 User Guide [TE3.2.x]Document DescriptionDescription

About this Document

Introduction This documentation set covers the following product lines:• Traverse System Product Documentation• TraverseEdge 100 System Product Documentation• TraverseEdge 206 System Product Documentation• TransNav Management System Product Documentation• TransNav Xpert Management System Product Documentation• Operations Documentation• Information Mapping

Refer to “What’s New in the Documentation?” to review the new and changed features for this release.

Traverse System Product Documentation

The Traverse® system product documentation set includes the documents described in the table below.

Table 1 Traverse System Product Documentation

Document Description Target Audience

Traverse Product Overview

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

Anyone who wants to understand the Traverse system and its applications.

Traverse Installation and Configuration

This document provides required equipment, tools, and step-by-step procedures for:• Hardware installation• Power cabling• Network cabling• Node power up• Node start-up

Installers, field, and network engineers

Release TE3.2.x Force10 Networks Page v

Traverse System Product Documentation

Traverse Provisioning

This document provides step-by-step procedures for provisioning a network of Traverse nodes using the TransNav management system. See the TransNav Management System Product Documentation.

Network engineers, provisioning, and network operations center (NOC) personnel

Node-level GUI Guide

This document provides a description of the navigational components of the Traverse Node-level graphical user interface (GUI). The Node-level GUI is a shelf view of a specific node.

Field engineers

Table 1 Traverse System Product Documentation (continued)


Page vi Force10 Networks Release TE3.2.x

TraverseEdge 100 System Product Documentation


The TraverseEdge™ 100 (TE-100) User Guide includes the sections described in the table below.

Table 2 TraverseEdge 100 System Product Documentation

Section Description Target Audience

Product Overview This section provides a detailed overview of the TraverseEdge system.

Anyone who wants to understand the TraverseEdge system and its applications

Description and Specifications

This section includes engineering and planning information.

Field and network engineers

Installation and Configuration

This document identifies required equipment and tools and provides step-by-step procedures for:• Hardware installation• Power cabling• Network cabling• Node power up• Node start-up

Installers, field, and network engineers

Provisioning the Network

This section provides step-by-step procedures for provisioning a TraverseEdge network using the TransNav management system. Also see the TransNav Management System Product Documentation.


Configuring Equipment

This section provides step-by-step procedures for configuring card and interface parameters of a TraverseEdge using the TransNav management system. Also see the TransNav Management System Product Documentation.


Creating TDM Services

This section provides step-by-step procedures for provisioning a TraverseEdge network using the TransNav management system. Also see the TransNav Management System Product Documentation.


Creating Ethernet Services

This section provides step-by-step procedures for provisioning a TraverseEdge network using the TransNav management system. See the TransNav Management System Product Documentation.


Appendices This section provides installation and provisioning checklists, compliance information, and acronym descriptions.

Installers and anyone who wants reference information.

Release TE3.2.x Force10 Networks Page vii



The document below provides operation and maintenance information for the TraverseEdge 206 (TE-206) product.

Table 3 TE-206 Documentation


TraverseEdge 206 Application Engineering Guide

Provides information vital for the proper deployment of a TE-206 system. Information provided deals with: • environmental requirements• specifications• applications


TraverseEdge 206 Hardware Description Guide

Provides detailed information for each card, shelf and accessory in a TE-206 system. Information provided includes:• card level diagrams• operational requirements• specifications• applications


TraverseEdge 206 Hardware Installation Guide

Provides information vital for proper installation of TE-206 equipment. Information provided deals with: • site layout• required hardware• power connections• cable connections• interfaces that must be hardwired

Installers, field and network engineers

TraverseEdge 206 Users Guide

Provides information vital for proper operation and maintenance of Force10 Networks TE-206 system. Information provided deals with processes and procedures for: • turn-up • test• maintenance duties • input command sequences • valid parameters • expected responses using TN-Sight

Field and network engineers, provisioning and network operation center (NOC) personnel

TraverseEdge 206 TL1 Guide

Provides information vital for proper communication with Force10 Networks TE-206 system. Information provided deals with: • all TL-1 command structures • valid parameters • expected responses• error codes

Page viii Force10 Networks Release TE3.2.x

TransNav Management System Product Documentation

TransNav Management System Product Documentation

The TransNav™ management system product documentation set includes the documents described in the table below.

Table 4 TransNav Management System Product Documentation


TransNav Management System Product Overview

This document provides a detailed overview of the TransNav management system.

This document includes hardware and software requirements for the management system. It also includes network management planning information.

Anyone who wants to understand the TransNav management system

TransNav Management System Server Guide

This document describes the management server component of the management system and provides procedures and troubleshooting information for the server.

Field and network engineers, provisioning, and network operations center (NOC) personnelTransNav

Management System GUI Guide

This document describes the graphical user interface including installation instructions and logon procedures.

This document describes every menu, window, and screen a user sees in the graphical user interface.

TransNav Management System CLI Guide

This document includes a quick reference to the command line interface (CLI). Also included are comprehensive lists of both the node-level and domain-level CLI commands.

TransNav Management System TL1 Guide

This document describes the syntax of the TL1 language in the TransNav environment.

This document also defines all input commands and expected responses for retrieval commands as well as autonomous messages that the system outputs due to internal system events.

Release TE3.2.x Force10 Networks Page ix

TransNav Xpert Management System Product Documentation

TransNav Xpert Management System Product Documentation

The document below provides operation and maintenance information for the TransNav XpertTM-managed products.

Operations Documentation

The document below provides operations and maintenance information for the TransNav managed products.

Information Mapping

Traverse, TransNav, and TraverseEdge 100 system documentation uses the Information Mapping format which presents information in small units or blocks. The beginning of an information block is identified by a subject label in the left margin; the end is identified by a horizontal line. Subject labels allow the reader to scan the document and

Table 5 TN-Xpert Documentation


TransNav Xpert Installation Guide

This document provides information to properly install and maintain TN-Xpert Client and Server for both Solaris and Windows environments. Information provided deals with: • operation system configuration• database installation• user account configuration • TN-Xpert software installation • Network Element IP connectivity


TransNav Xpert Users Guide

Provides information vital for proper operation and maintenance of the TE-206 and TE-2020 systems. Information provided deals with processes and procedures for:• turn up• test• maintenance duties• input command sequences• valid parameters• expected responses using TN-Xpert


Table 6 Operations Documentation


Operations and Maintenance

This document identifies required equipment and tools. It also provides step-by-step procedures for:• Alarms and recommended actions• Performance monitoring• Equipment LED and status• Diagnostics• Test access (SONET network only)• Routine maintenance• Node software upgrades• Node hardware upgrades


Page x Force10 Networks Release TE3.2.x

Information Mapping

find a specific subject. Its objective is to make information easy for the reader to access, use, and remember.

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

Release TE3.2.x Force10 Networks Page xi

Information Mapping

Page xii Force10 Networks Release TE3.2.x

SECTION 1 PRODUCT OVERVIEW AND APPLICATIONSSECTION 1SYSTEM OVERVIEW

SECTION 1SYSTEM OVERVIEW

Contents

Chapter 1Overview

Force10 Solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-vMultiservice Optimized Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-viEthernet Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-viKey Ethernet Transport Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-vi

Generic Framing Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-viiVirtual Concatenation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-viiLink Capacity Adjustment Scheme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-vii

Key Ethernet Switching Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-viiRapid Spanning Tree Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-viiEthernet Traffic Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-vii

Carrier-Class Reliability. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-viiiVersatile Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-viiiComprehen- sive Manage- ment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-viii

Chapter 2Applications

Multiservice Access and Transport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-xMultiservice Access and Transport Advantages . . . . . . . . . . . . . . . . . . . 1-x

Wireless Backhaul. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-xiWireless Backhaul Advantages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-xi



SECTION 1PRODUCT OVERVIEW

Chapter 1 Overview

Introduction The TraverseEdge™ 100 (TE-100) is a cost-effective and efficient edge multiplexer that delivers differentiated new Ethernet and IP services as well as legacy voice and TDM services. The flexible and compact (2RU) shelf aggregates a combination of Fast Ethernet, Gigabit Ethernet, DS1/E1 and DS3/E3 services onto dual OC-3/12/48 or STM-1/4/16 trunk interfaces. Targeted for wireless, wireline and private network applications, the TE-100 is ideally suited for metro access rings, MTUs (offering both AC or DC), outside plant cabinets, cell sites, and other locations.

This chapter includes the following topics:• Force10 Solution, page 1-1• Multiservice Optimized Architecture, page 1-2• Key Ethernet Transport Features, page 1-2• Carrier-Class Reliability, page 1-4• Versatile Configuration, page 1-4• Comprehen- sive Manage- ment, page 1-4

Force10 Solution

Figure 1-1 TE-100 Shelf

The TE-100 multiplexer is ideally suited for applications in metro access networks, or as an end node in cell sites and customer locations such as multiple tenant units (MTUs). The TE-100 system is temperature hardened, which means it can be used in outside plant cabinets. This platform is a truly global solution, supporting both ANSI/SONET and ETSI/SDH deployments.

Release TE3.2.x Force10 Networks Page 1-1

TraverseEdge 100 User Guide, Section 1: Product OverviewMultiservice Optimized Architecture

As a next-generation edge platform, the TE-100 multiplexer is:• A compact 2RU high shelf ideally suited for installation in customer locations,

OSP cabinets, and central offices.• A multiservice solution that integrates layer 2 Ethernet switching and

SONET/SDH bandwidth management functions to efficiently aggregate and deliver both TDM and Ethernet services.

• Reliable, with full 1:1 equipment protection available for all tributary ports and system functions, as well as 1+1 APS/MSP and UPSR/SNCP facility protection for optical network ports.

• Flexible, offering native DS1/E1, DS3/E3, Fast Ethernet, and Gigabit Ethernet tributary interfaces, as well as modular, fully protected OC-3/-12/-48 SONET or STM-1/-4/-16 SDH trunk interfaces using small form-factor pluggable (SFP) optics.

A single shelf that extends SONET, SDH, and Ethernet to the provider edge, the TE-100 shelf allows service providers to converge high-speed data, video and voice services over their existing infrastructure with the highest levels of reliability and cost-efficiency. The TE-100 interoperates seamlessly with Force10 Networks’ industry-leading solution for metro core SONET, SDH, Ethernet, and TDM aggregation - the Traverse platform.

See Chapter 1—“Platform Description and Specifications,” page 2-1 for a complete description and specification.

Multiservice Optimized Architecture

The multiservice design of the TE-100 shelf combines high or low order level grooming and Ethernet switching to support evolving access applications. This capability allows service providers to deliver new Ethernet services without having to build dedicated overlay networks. Integrated bandwidth management capabilities enable service providers to manage traffic down to the T1/E1 level, ensuring optimal transport network efficiency.

Ethernet Services

The TE-100 platform features a powerful 5 Gbps Layer 2 Ethernet switch fabric that supports delivery of point-to-point Ethernet Private Line and multipoint Ethernet Private LAN/Transparent LAN services.

Point-to-point Ethernet Private Line (EPL) services provide dedicated Ethernet connectivity that does not compete for bandwidth with other services.

Multipoint Ethernet Private LAN/Transparent LAN services provide shared Ethernet connectivity that competes for bandwidth with other services. For these oversubscribed services, intelligent VLAN and flow control mechanisms enable differentiated classes of service and carrier-grade service level agreements (SLAs) that can be defined and scaled in 1 Mbps bandwidth increments.

Key Ethernet Transport Features

The TE-100 multiplexer is one of the first in the industry to implement several key Ethernet over SONET/SDH (EoS) standards that significantly improve transport bandwidth conservation and utilization. The TE-100 system implements a full range of standards-based EoS features designed to provide the efficient transport of Ethernet over existing networks:

Page 1-2 Force10 Networks Release TE3.2.x

Chapter 1 OverviewKey Ethernet Switching Features

Generic Framing Procedure

The TE-100 system supports ITU-T G.7041 (2001) & ANSI T1.105.02 (2002) Generic Framing Procedure (GFP). GFP is a universal traffic adaptation technique used to map broadband traffic—be it Ethernet, IP, Fibre Channel, or other block-coded or packet-oriented data streams—into the optical transport network. The GFP encapsulation framework supports both fixed or variable length frame structures.

Virtual Concatenation

The TE-100 system supports ITU-T G.707/Y.1322 and G.783 Virtual Concatenation (VCAT). VCAT is an inverse multiplexing technique that bundles multiple independent lower-rate channels into a higher rate channel. VCAT enables efficient mapping of Ethernet frames directly into a payload of separate high or low order path signals, known as a virtual concatenation group (VCG). This mapping technique eliminates the rigid hierarchies of the common SONET/SDH containers and enables service providers to provision and transport data services with greater bandwidth efficiency.

Link Capacity Adjustment Scheme

The TE-100 system supports link capacity adjustment scheme (LCAS). LCAS is a method of dynamically provisioning and reconfiguring TDM channels to suit customer needs or carrier bandwidth management requirements, based on ITU-T G.7042/Y.1305 standards. LCAS extends the benefits of virtual concatenation by providing a control mechanism that supports the hitless adjustment (or resizing) of these virtually concatenated channels.

Key Ethernet Switching Features

Rapid Spanning Tree Protocol

The TE-100 system supports IEEE 802.1W Rapid Spanning Tree Protocol (RSTP). RSTP is based on a distributed algorithm that selects a single switch in the network topology to act as the root of the spanning tree. The algorithm assigns port roles to individual ports on each switch. Port roles determine whether the port is to be part of the active topology connecting the bridge or switch to the root bridge (a root port), or connecting a LAN through the switch to the root bridge (a designated port). Regardless of their roles, ports can serve as alternate or redundant ports that provide connectivity in the event of a failure.

Ethernet Traffic Management

Ethernet traffic management provides features to support rate limiting, shaping, and congestion.• Rate Limiting. Rate limiting allows service providers to sell partial rate service.

Classifiers divide customer traffic into classes. Class-based Policing measures the customer traffic and marks it as in or out of contract for each class.

• Shaping. Shaping allows service providers control over the rate at which the system sends data on an output port—usually because a downstream device can only handle traffic at a lower rate than the native speed of the port.


TraverseEdge 100 User Guide, Section 1: Product OverviewCarrier-Class Reliability

• Congestion. Congestion results when a system attempts to send more data than a port can handle. Class-based Random Early Discard (RED) provides queuing or dropping of extra traffic. Class-based Scheduling allocates the output bandwidth of the port.

Carrier-Class Reliability

The TE-100 multiplexer is designed to deliver greater reliability and redundancy than competing products. Additionally, the system supports in service hardware and software upgrades with minimal interruption to existing network traffic. The TE-100 platform is NEBS Level 2 compliant.

Versatile Configuration

The physical design of the TE-100 shelf supports a combination of optical networking, TDM (either SONET or SDH), and Ethernet interfaces.

The SONET version supports 28 DS1, 3 DS3, 6 10/100 Fast Ethernet, and 2 Gigabit Ethernet (GbE) SFP interfaces. The system card supports redundant configuration as an option and provides dual OC-3/12, or OC-48 network interfaces using SFP optics. The SONET interfaces can be configured for linear 1+1 APS or UPSR topologies.

The SDH version supports 21 E1, 3 E3, 6 10/100 Fast Ethernet, and 2 Gigabit Ethernet (GbE) SFP interfaces. The system card supports redundant configuration as an option and provides dual STM-1, STM-4, or STM-16 network interfaces using SFP optics. The STM interfaces can be configured for linear 1+1 MSP or SNCP ring topologies.

Comprehen- sive Manage- ment

Force10 ’s TransNav management system provides comprehensive management of the TE-100 platform, enabling carriers to engineer, deploy, manage, and bill for new services. Fault, configuration, performance, and service management/monitoring functions are facilitated at the element and sub-network level through an easy-to-use GUI.


SECTION 1PRODUCT OVERVIEW

Chapter 2 Applications

Introduction The TraverseEdge 100 (TE-100) multiplexer targets applications for wireline and wireless carriers who are evolving to advanced new packet-based services while supporting revenue-generating TDM services. The TDM switching matrix and high-capacity Ethernet switching fabric ensure optimum bandwidth utilization with mixed traffic loads. In addition to being suitable for deployments in metro access networks, or as an end node in cell sites and customer locations, the TE-100 shelf is environmentally hardened for use in outside plant cabinets.

This chapter explains the following applications:• Multiservice Access and Transport, page 1-6• Wireless Backhaul, page 1-7


TraverseEdge 100 User Guide, Section 1: Product OverviewMultiservice Access and Transport

Multiservice Access and Transport

The compact, affordable design of the TE-100 multiplexer is ideally suited for multiservice applications serving enterprise customers in access rings, or as an end-node in MTUs, business parks, and outside plant cabinets.

Figure 1-2 Multiservice Access and Transport Application

Most often deployed in conjunction with high capacity metro/IOF core platforms like Force10's Traverse 2000, the TraverseEdge 100 aggregates a mix of TDM and Ethernet services, and multiplexes them onto dual optical trunk interfaces for transport across the carrier network. Native DS1 and DS3 or E1 and E3 subscriber ports can deliver reliable, secure TDM private lines, while the 10/100 and GbE subscriber ports can be provisioned for carrier-class point-to-point or multi-point Ethernet connectivity. GFP, LCAS, HO/LO VCAT, and RSTP capabilities ensure that Ethernet services are transported over the SONET or SDH infrastructure with maximum reliability and efficiency.

Multiservice Access and Transport Advantages

The TE-100 offers the following advantages:• Ideal for access ring (central office), customer located equipment (CLE), MTU, or

outside plant (OSP) environments• Integrates standard SONET or SDH, and Ethernet switching and transport in a

compact 2RU-high shelf• Supports linear and ring topologies• In ANSI operation, provides DS1, DS3, 10/100, and GbE connectivity• In ITU operation, provides E1, E3, 10/100, and GbE connectivity• Supports both point-to-point and multi-point Ethernet services.

TraverseEdge 100

TraverseEdge 100

Traverse2000


Chapter 2 ApplicationsWireless Backhaul

• Optimized Ethernet over SONET/SDH (EoS) transport using GFP, HO/LO VCAT, LCAS, and RSTP

• Complements Force10’s Traverse platform for multiservice TDM and Ethernet aggregation and grooming in the head-end

• TransNav management system delivers fast, intuitive service provisioning and management

Wireless Backhaul

Wireless service providers are looking to migrate to a unified network that supports both TDM voice and new 3G/UMTS/EDGE data services.

Figure 1-3 Wireless Backhaul Application

Force10’s TE-100 multiplexer is an evolutionary and highly affordable solution ideally suited for this application. The hybrid design, which integrates high order and low order grooming as well as Ethernet switching in a 2RU shelf, eliminates the need for multiple overlays to support new data services. In addition, the system implements low order VCAT technology to improve utilization of circuits currently being leased for data transport, further lowering costs. Deployed in the wireless base station controller (BSC), the TE-100 platform can provide either DS1 and DS3 ports or E1 and E3 for aggregating circuits from the BTS, as well as 10/100 and GbE ports for aggregating data services. SONET/SDH transport is used to backhaul this traffic to the MSC with maximum reliability in an optical linear or ring topology.

Wireless Backhaul Advantages

The TE-100 multiplexer offers the following advantages:• Ideal for BSC deployments, delivering phased migration to data services • In ANSI operation, provides DS1, DS3, 10/100 and GbE connectivity with

efficient OC-3, OC-12, or OC-48 backhaul• In ITU operation, provides E1, E3, 10/100, and GbE connectivity with efficient

STM-1, STM-4, or STM-16 backhaul• A compact 2RU-high shelf that integrates Ethernet and standard SONET or SDH

Traverse 2000

TraverseEdge 100

EoS transport using LO-VCAT maximizes bandwidth efficiency and lowers costs.

Traverse 2000 provides LO groomingdata grooming, and ring termination on a single shelf.

TraverseEdge 100 provides wireless voice/TDM and data/Ethernet (Edge/UMTS, Ev-DO) traffic aggregation as well TDM backhaul.


TraverseEdge 100 User Guide, Section 1: Product OverviewWireless Backhaul

• Optimized EoS transport using GFP, HO/LO VCAT, LCAS, and RSTP. Complements Force10’s Traverse platforms for multiservice TDM and Ethernet aggregation and grooming in the MSC.

• TransNav management system delivers fast, intuitive service provisioning and management.


SECTION 2 PRODUCT DESCRIPTION AND SPECIFICATIONSSECTION 1SYSTEM OVERVIEW

SECTION 1SYSTEM OVERVIEW

Contents

Chapter 1Platform Description and Specifications

TE-100 Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2Dimensions Summary Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4Front View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5

System Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5Interface Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5Fan Assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5

Rear View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6System Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6Small Form-factor Pluggable (SFP) Transceivers. . . . . . . . . . . . . . . . . . . . . . 2-7Interface Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8Rack Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8Fan Assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9Fan Assembly Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9Regulatory Compliance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10

Chapter 2Electrical Ports Specifications

DS1 Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12DS1 Port Specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12

DS3 Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13DS3 Port Specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13

E1 Ports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14E1 Port Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14

E3 Ports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15E3 Port Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15

Chapter 3Ethernet Ports Specifications

Gigabit Ethernet Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-18

Fast Ethernet Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19

Chapter 4SONET/STM Ports Specifications

Industry Standards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-21


TraverseEdge 100 User Guide, Section 2 Product Description and Specifications

OC-3/STM-1 SFP Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22Specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22

OC-12/STM-4 SFP Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-23Specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-23

OC-48/STM-16 SFP Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-24Specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-24

Protection Switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-25Optical Interface Specifications (Summary). . . . . . . . . . . . . . . . . . . . . . . . . . . 2-26

Chapter 5Alarm Interface Specifications

Alarm InterfaceDescription . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-27Normally-open Contacts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-28Fail-safe Alarm. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-28Environmental Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-28

Alarm Outpu Wire-Wrap Posts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-29Environmental Alarm Input Wire-Wrap Posts . . . . . . . . . . . . . . . . . . . . . . . . . 2-29Alarm Contact Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-30Alarm Cut-Off (ACO) Button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-30

Chapter 6Timing Specifications

Timing Interface Input and Output Wire-Wrap Posts . . . . . . . . . . . . . . . . . . . . 2-32Timing Interface Contacts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-33

Chapter 7Management Interfaces Specifications

DCN Ethernet Interface Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-36RS-232 CLI Modem Interface (DTE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-37Data Communication Equipment RS-232 Interface (DCE) . . . . . . . . . . . . . . . 2-38

Chapter 8Power Interface Specifications

PDAP-15A DC/DC (optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-39PDAP Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-40TE-100-AC/DC Power Converter (optional). . . . . . . . . . . . . . . . . . . . . . . . . . . 2-40TE-100-AC/DC Power Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-41

Chapter 9Network Topologies

Terminal Point-to-Point Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-43Ring Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-44Typical TE-100 Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-44Network Management Planning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-45


SECTION 2PLATFORM SPECIFICATIONS

Chapter 1 Platform Description and Specifications

Introduction The TraverseEdge 100 (TE-100) shelf is a 3-slot, rack-mountable shelf. Its compact, hardened design makes it suitable for installation in a business building, Operator Service Provider (OSP) cabinet, or Central Office (CO). Hot-swappable Small Form-factor Pluggable (SFP) transceivers provide optical media and interface rate flexibility.

This chapter describes the physical attributes of the TE-100 shelf and its component parts.• TE-100 Specifications, page 2-2• Dimensions Summary Table, page 2-4• Front View, page 2-5• Rear View, page 2-6• System Modules, page 2-6• Interface Module, page 2-8• Small Form-factor Pluggable (SFP) Transceivers, page 2-7• Fan Assembly, page 2-9• Regulatory Compliance, page 2-10


TraverseEdge 100 User Guide, Section 2: Platform SpecificationsTE-100 Specifications

TE-100 Specifications

The TE-100 shelf has all trunk, tributary, and management interfaces accessible from the front panel. The shelf accommodates two system modules, an interface module, and a fan assembly.

Figure 2-1 TE-100 Shelf

This table lists the specifications for the TE-100 shelf.

Interface Module

System Module

System Module

Table 2-1 TE-100 SpecificationsParameter Specification

System configuration 3-slot shelf:• 2 slots for system modules with integrated SONET interfaces• 1 slot for the interface module

Maximum switching capacity 5 Gbps

Note: The 5 Gbps is the total of 2.5 Gbps in the eastbound direction and 2.5 Gbps in the westbound direction.

Power Consumption:• 100 watts maximum in a fully configured system• 36 watts, OC-3/OC-12 system module• 36 watts, STM-1/STM-4 system module• 34 watts, OC-48 system module• 34 watts, STM-16 system module• 4 watts, interface module• 15 watts, fan tray

Dual redundant -48 VDC power feeds

Operating range: –40 VDC to –60 VDCDimensions 3.5” (H) x 17.25” (W) x 11.8” (D)

90 mm (H) x 438 mm (W) x 300 mm (D)Weight 9.65 lbs. (3.38 kg) - fully configured Operating temperature –40°C to +65°CHumidity 10-95% non-condensing


Chapter 1 Platform Description and SpecificationsTE-100 Specifications

Network Interfaces Trunk Interfaces• 2 SONET OC-3, OC-12, or OC-48 ports

LC SMF connectors, IR or LR optics using SFP transceiversOR

• 2 SDH STM-1, STM-4, or STM-16LC SMF connectors, IR or LR optics using SFP transceivers

Tributary Interfaces• 2 Gigabit Ethernet ports

LC connectors, SX (MMF) or LX (SMF) optics using SFP transceivers

• 6 Fast Ethernet portsRJ45 connectors

• 3 DS3 OR E3 portsmini-BNC connectors

• 28 DS1 or 21 E1portsRJ45 connectors

Management Interfaces • Serial console port (RS232/DCE)• Serial port for modem (RS232/DTE)• DCN (RJ45 10/100BaseTX)

System timing Clock: Stratum 3 Free-run accuracy: ±4.6 x 10-6 (±7.1 Hz @ 1.544 MHz) Holdover stability: <255 slips (±3.7 x 10-7) for the initial 24 hours Minimum pull-in/hold-in: ±4.6 x 10-6Filtering: yes, 3 Hz Output Phase Transients: MTIE = 1 µs Reference: External, line, internal

Synchronization interfaces 2 T1 synchronization input and output interfaces2 2MHz synchronization input interfaces.

Alarm Interface Critical, Major, Minor, Remote, and Audible Outputs (NO, C, NC)4 environmental input alarm contacts (EnvIN, RTN)2 environmental output alarm contacts (NO, C)1 ACO input alarm contact (ACO_IN, RTN)1 Failsafe output alarm contact (NC, C)

Memory, System module SDRAM, 256 MBFlash, 128 MB

Table 2-1 TE-100 Specifications (continued)Parameter Specification


TraverseEdge 100 User Guide, Section 2: Platform SpecificationsDimensions Summary Table

Dimensions Summary Table

The following table gives the dimensions for the TE-100 components.

Functional • SONET Multiplexing VT1.5, STS-1

• SDH MultiplexingVC-11, VC-12, STM-0

• Sychronization Line and backup Stratum 3 timing, G.957, G.691

• Ethernet over SONET/SDH • LO Virtual Concatenation• HO Virtual Concatenation• Link Capacity Adjustment Scheme (LCAS)• Generic Framing Procedure (GFP)

• Ethernet • Layer 2 switching, 5Gbps capacity• 802.1Q VLANs, rate limiting in 1Mbps increments• Port or VLAN-based CoS• Point-to-point and multipoint services

Protection Options • 1+1 APS or UPSR protection on trunk interfaces• 1+1 MSP or SNCP ring protection on trunk interfaces• 1+1 VT path protected service (OC-3 and OC-12 only)• 1+1 VC path protected services (STM-1 and STM-4 only)• 1+1 STS path protected services• 1+1 STM path protected services• 1:1 equipment protection on all system functions and access

services—DS1, DS3, 10/100BaseTX, and GbE— when equipped with two system modules

• 1:1 equipment protection on all system functions and access services—E1, E3, 10/100BaseTX, and GbE— when equipped with two system modules

Table 2-1 TE-100 Specifications (continued)Parameter Specification

Table 2-2 TE-100 Component Dimensions

Assembly Height Width Depth WeightEmpty

WeightFully Loaded

Shelf 3.5 in 17.25 in 11.8 in 3.2 lb 9.65 lb

90 mm 438 mm 300 mm 1.5 kg 3.38 kg

System module 1 in 14.5 in 8 in n/a 1.85 lb

25.4 mm 368.3 mm 203.2 mm n/a .84 kg

Interface module 1.6 in 17 in 8 in n/a 2.4 lb

40.69 mm 431.8 mm 203.2 mm n/a 1.09 kg

Fan assembly 2.00 in 1.75 in 9 in n/a .70 lb

50.8 mm W 44.5 mm 228.6 mm n/a 1.1 kg

PDAP (optional) 1.75in 17.25 10 in n/a ~10 lb

45 mm 438 mm 254 mm n/a ~4.5 kg


Chapter 1 Platform Description and SpecificationsFront View

Front View The TE-100 shelf configuration hosts up to two system modules, for redundancy, and one interface module. Module guide rails are built into the shelf to allow for easy insertion of modules into backplane connectors. The fan assembly comes pre-installed. You can access all physical interfaces through the front panel, with the exception of the alarm and timing interfaces.

This graphic shows the front of a shelf.

Figure 2-2 Front Panel

System Module

The system module comes in two different versions, OC-3/OC-12 or OC-48. Each version supports two OC-N trunk interfaces using hot-swappable SFP optical transceivers, and is the processing core of the shelf, providing support for all service and management interface ports on the interface module.

The system module also provides an RS232 management interface.

Interface Module

The interface module contains ports for all tributary interfaces (DS1, DS3, Fast Ethernet, and GbE) and two additional management interfaces.

Fan Assembly

The TE-100 shelf has a pre-installed, field-replaceable fan assembly. The fan assembly consists of three fans and a replaceable, cleanable air filter.

Interface Module

System Module

System ModuleRS232DCE Interface

28 DS1 Ports or

21 E1 Ports

Optical Facilities: (4 SFP sockets with 2 usable lines)

3 DS3 Ports or

2 E3 Ports

2 GbE Ports

(SFPs)RS232 DTE

Interface (modem)

DCN Interface

6 Fast Ethernet

Ports

Fan Assembly


TraverseEdge 100 User Guide, Section 2: Platform SpecificationsRear View

Rear View This graphic shows the rear view of the shelf.

Figure 2-3 Rear View

The back of the shelf provides access to all alarm and timing interfaces. Signals are routed through the interface module. The backplane also provides connectivity between the system and interface modules.

System Modules

One system module supports two trunk interfaces and supplies all system, control, interface, and management functions. It also contains all active electronics, with the exception of the GbE SFP optical transceivers.

Figure 2-4 System Modules

The two system module versions available are:• OC-3/STM-1/OC-12/STM-4

Supports the optical trunk interfaces as well as the service interfaces. This module has programmable OC-3/STM-1 or OC-12/STM-4 SFP optical transceivers for all applications (short, intermediate, and long reach).

• OC-48/STM-16 Supports the OC-48/STM-16 trunk interfaces as well as the service interfaces. This module has OC-48/STM-16 SFP optical transceivers for all applications (short, intermediate, and long reach).

With one system module, the shelf has no equipment protection. With two system modules, it has 1:1 equipment protection for all common system functions and interfaces (excluding the GbE SFP transceivers).

Board Power Connector

External Power

Connector

Copper Interface

High speed and control

signal

Eprom

Failsafe relay

Fan tray connector

Perforations for Fan Exhaust

Timing and Alarm Wire- Wrap Pins

System Module 2

System Module 1RS232 CLI(or vxWorks Shell) DCE

2 Optical Facilities(4 SFPs but only 2 usable lines)

Fan Assembly


Chapter 1 Platform Description and SpecificationsSmall Form-factor Pluggable (SFP) Transceivers

The system modules also have an alarm cut-off (ACO) button, a LED lamp test control, and a Reset button that allows the operator to initiate a cold reboot.

For detailed port specifications, see the following chapters:• Chapter 4—“SONET/STM Ports Specifications,” page 2-21• Chapter 7—“Management Interfaces Specifications,” page 2-35

Small Form-factor Pluggable (SFP) Transceivers

Each system module has sockets for two SFPs. The OC-3/STM-1/OC-12/STM-4 version of the system module accepts either OC-3/STM-1 or OC-12/STM-4 transceivers. The OC-48/STM-16 version accepts only OC-48/STM-16 transceivers.

Figure 2-5 Small Form-Factor Pluggable (SFP) Transceivers

The SFPs are hot swappable, i.e., they can be removed or inserted while the system is on. See Chapter 4—“SONET/STM Ports Specifications,” page 2-21 for details.

The interface module has a stacked pair of GbE SFPs that can also be removed or inserted while the system is on. See Chapter 3—“Ethernet Ports Specifications,” Gigabit Ethernet Ports, page 2-17 for details.

Optical Facilities: (4 SFPs but only 2 usable lines)

2 GbE Ports(SFPs)


TraverseEdge 100 User Guide, Section 2: Platform SpecificationsInterface Module

Interface Module

The interface module provides a single interface point for equipment-protected services. These services typically require redundant equipment at either end of a single unprotected facility.

Figure 2-6 Interface Module

This module, which fits only in the bottom slot, holds the interfaces for the Ethernet and TDM interfaces. It also holds the DCN Ethernet and RS-232 management interfaces for Telnet access. LEDs indicate status.

DS1/E1, 10/100BaseTx, and RS-232 interfaces use RJ-45 connectors. The DS3/E3 ports use 75Ω Mini-BNC connectors. GbE uses a dual-stacked SFP carrier.

For detailed port specifications, see the following chapters:• Chapter 2—“Electrical Ports Specifications,” page 2-11• Chapter 3—“Ethernet Ports Specifications,” page 2-17• Chapter 4—“SONET/STM Ports Specifications,” page 2-21• Chapter 7—“Management Interfaces Specifications,” page 2-35

Rack Configuration

The TE-100 shelf installs either in a standard 19-inch (500 mm) or 23-inch (600 mm) wide relay rack. It requires extender brackets for installation in the wider rack. The shelf has a hardened design that lets you install it in an outdoor cabinet.

Because the fan directs cooling air from side to side, you can install the TE-100 shelf directly under the (optional) power distribution and alarm panel (PDAP) without providing a gap for airflow, if necessary.

28 DS1 Portsor

21 E1 Ports3 DS3 or E3 Ports

2 GbE Ports

(SFPs)RS232 DTE

Interface(modem)

DCN Interface

6 Fast Ethernet

Ports


Chapter 1 Platform Description and SpecificationsFan Assembly Specifications

Fan Assembly The fan assembly maintains the optimum operating temperature for the system and interface modules. It has three small fans (dimension of each fan: 1.5 x 1.5 x .9 inches), receiving redundant 12VDC power feeds from the system module..

Figure 2-7 Fan Assembly

The fan assembly is in a vertical slot on the left front of the shelf. It draws ambient air through the perforation on the left wall and forces the air over the system and interface modules in the horizontal slots. Finally it sends air out through the perforation on the right wall. Each fan runs at approximately 11,000 RPM, drawing about 17.6CFM of air. At a 75% effective rate, the fan assembly forces about 40CFM of ambient air through the shelf.

The assembly has a replaceable, cleanable stainless steel mesh air filter.

When one fan fails, the remaining two fans can cool the shelf adequately for normal system operation per GR-63-CORE. When the system detects ambient temperature lower than -5o C, it turns off all fans by default.

When the fans change states (e.g., arrival/on, failure, off, removal), the system reports fan alarms, events, and provides a status update.

The fan assembly has two LEDs: Power and Failure. When all fans are working, the Power light is GREEN and the Failure light is OFF. If one or more fans fail, the Failure light turns RED.

Fan Assembly Specifications

This table lists the specifications for the fan assembly.

Fan Assembly

Fan Assembly with filter

Table 2-3 Fan Assembly Specifications

Parameter Specifications

Number of fans 3

Power (nominal)

Consumption (max)

15 watts

15 watts

Dimensions (inches)

(millimeters)

2.00 H x 1.25 W x 9D

50.8 H X 44.5 W x 228.6 D

Weight .7 lb


TraverseEdge 100 User Guide, Section 2: Platform SpecificationsRegulatory Compliance

Regulatory Compliance

The following table lists TE-100 regulatory compliance information.

Table 2-4 Regulatory Compliance

Specification Description

ANSI T1.105.02

T1.319-2002

EMI FCC Part 15, Class A

EN 300

EN 55022, Class A

EN 61000

Environmental Airborne contaminants: NEBS Section 4.5, GR-1274-CO

Operational: –40°C to +65°C, 85% max. relative humidity

Altitude: 13,123 ft. (4000 m) above sea level

Storage: –40ºC to +85ºC, 95% max. relative humidity

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

IEEE 802.3i

802.3u

802.3x

802.3z

802.1D

802.1p

802.1Q

802.1W

ITU-T G.707

G.783 (VCAT)

G.7042 (LCAS)

G.7041 (GFP)

NEBS - Level 2 Certified

GR-63-CORE

GR-1089-CORE

Zone 4 Earthquake

TRW-NWT-000-295 IBN Grounding Requirements

Safety IEC60950

EN60950

Telcordia GR-253

Eye Safety Class 1



Chapter 2 Electrical Ports Specifications

Introduction The electrical service ports on the TraverseEdge 100 (TE-100) interface module uses industry-standard cables and connectors. This chapter lists specifications for these ports: • DS1 Ports, page 2-12• DS3 Ports, page 2-13• E1 Ports, page 2-14• E3 Ports, page 2-15


TraverseEdge 100 User Guide, Section 2: Platform SpecificationsDS1 Ports

DS1 Ports The TE-100 shelf has twenty-eight DS1 interfaces available for services in ANSI operation. They are located on the front panel of the interface module, as shown in the following picture.

Figure 2-8 DS1 Ports

When the shelf is equipped with two system modules, these ports have 1:1 equipment protection. Each received DS1 signal can be mapped bit-asynchronously into a VT1.5 path or multiplexed into a channelized DS3 and mapped into an STS-1 for transport. For pinouts, see Figure 3-57 DS1/E1 Cable with RJ-45 Connector (RJ-48c Pinouts), page 3-81.

DS1 Port Specifications

This table lists product specifications for the DS1 port.

Table 2-5 DS1 Port Specifications

Parameter Specification

Module Interface module

Protection switching 1:1 Electrical Equipment Protection with second system module(switching time <= 50 ms)

Bit rate 1.544 Mbps

Line-rate accuracy ± 50bps (± 32 ppm) or better when not synchronized to a network clock

Mapping format DS3-mapped or VT1.5-structured

Frame structure Unframed (default), SF, ESF, SLC-96

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

Output pulse amplitude 2.4 -3.6 V peak to peak

Output pulse shape per GR-499-CORE

Connector RJ-45 (RJ-48c pinouts)

Test load impedance 100 Ohms ± 5%Loopback modes Terminal and Facility

Medium One balanced twisted pair for each direction of transmission

Maximum line length 655 feet (199.6 m) using AT&T Technologies, Inc. 22ga. ABAM (or equivalent)137.2 meters (450 ft.)

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

28 DS1 ports


Chapter 2 Electrical Ports SpecificationsDS3 Ports

DS3 Ports The TE-100 shelf has three DS3 interfaces available for tributary services in ANSI operation. They are located on the front panel of the interface module, as shown in the following picture.

Figure 2-9 DS3 Ports

When the shelf has two system modules, these ports have 1:1 equipment protection. Each un-channelized DS3 signal received can be mapped into an STS-1 for transport.

DS3 Port Specifications

This table lists product specifications for the DS3 ports in ANSI operation.

Table 2-6 DS3 Port Specifications




Bit rate 44.736 Mbps ± 20 ppm or better in a self-timed free running mode

Frame structure Unframed, C-bit parity or M23 per ANSI T1.107-1995

Line code Default to Bipolar with 3 Zero Suppression (B3ZS) per ANSI T1.102-1993, or Alternate Mark Inversion (AMI)

Signal level DSX-3

Receiver input impedance 75 Ohm ± 5%Connector 75 Ω mini-BNC (Bayonet-Neill-Concelman) connectors

Loopback modes Terminal and Facility

Medium One unbalanced coaxial line for each directional of transmission

Maximum Line Length 450 feet (137m) using 75 Ω coaxial cable

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

3 DS3 ports


TraverseEdge 100 User Guide, Section 2: Platform SpecificationsE1 Ports

E1 Ports The TE-100 shelf has 21 E1 interfaces available for tributary services in ITU operation. They are located on the front panel of the interface module, as shown in the following picture. Only the first 21 ports are available.

Figure 2-10 E1 Ports

When the shelf is equipped with two system modules, these ports have 1:1 equipment protection. In ITU operation, each received E1 signal can be mapped bit-asynchronously into a TU-12 path, or multiplexed into a channelized DS3/E3 then mapped into a VC-3/TU-3 for transport.

E1 Port Specifications

This table lists product specifications for the E1 port in ITU operation.

Table 2-7 E1 Port Specifications




Bit rate 2.048 Mbps

Line-rate accuracy ± 50bps (± 32 ppm) or better when not synchronized to a network clock

AU-4/STS structure VC-12 mapped

Frame structure CRC4

Line code HDB3 (per G.703 Annex A)

Output pulse amplitude 0.95 to 1.05 (ITU-T G.703)

Output pulse shape Per ITU-T G.703

Connector RJ-45 (RJ-48c pinouts)

Test load impedance 120 Ohms balanced


Medium One symmetric pair in each transmission direction

Maximum line length 655 feet (199.6 m) using AT&T Technologies, Inc. 22ga. ABAM (or equivalent) 137.2 meters (450 ft.)

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

ITU-T G.704, ITU-T G.703 (Table 7 and Figure 15)Input Jitter: ITU-T G.824 (Table 16 and Figure 13)

Output Jitter: ITU-T G.824 (Table 1)

In ITU operation, only the first 21 physical ports are available for services.


Chapter 2 Electrical Ports SpecificationsE3 Ports

E3 Ports The TE-100 shelf has three E3 or three DS3 interfaces available for tributary services in ITU operation. They are located on the front panel of the interface module, as shown in the following picture. Change the operation mode of the interfaces on the Config tab of the interface module.

Figure 2-11 E3 Ports

When the shelf has two system modules, these ports have 1:1 equipment protection. Each unchannelized E3 signal received can be mapped into an STM-0 for transport.

E3 Port Specifications

This table lists product specifications for the E3 ports in ITU operation.

Table 2-8 E3 Port Specifications




Bit rate 34.368 Mbps ± 20 ppm or better in a self-timed free running mode

Frame structure unframed, ITU G.751 or G.832 E3 framing formats

Line code High Density Bipolar of order 3 (HDB3) per ITU-T G.703

Signal level pulse shape and amplitude per G.703

Receiver input impedance 75 Ohm ± 5%Connector 75 Ω mini-BNC (Bayonet-Neill-Concelman) connectors


Medium One unbalanced coaxial line for each directional of transmission

Maximum Line Length 450 feet (137m) using 75 Ω coaxial cable

Industry Standards ITU-T G.703 (Table 4 and Figure 10)Input Jitter: ITU-T G.824 (Table 8 and Figure 6)

Output Jitter: ITU-T G.824 (Table 1)

3 E3 ports


TraverseEdge 100 User Guide, Section 2: Platform SpecificationsE3 Ports



Chapter 3 Ethernet Ports Specifications

Introduction The TraverseEdge 100 (TE-100) shelf supports the following types of Ethernet ports: • Gigabit Ethernet Ports, page 2-17• Fast Ethernet Ports, page 2-19

These ports allow the shelf to support Ethernet access, aggregation, and transport over SONET/SDH applications.

Gigabit Ethernet Ports

The TE-100 shelf has two Gigabit Ethernet (GbE) ports that use SFPs (small form pluggable transceivers) to provide a physical connection for SX, LX, and ZX optics. The SFPs meet the requirements in IEEE specification 802.3 for 1000BaseSX and 1000BaseLX.

All Ethernet port management functions operate independently of Ethernet service management functions. Operators can modify port provisioning regardless of whether those ports are currently used in activated Ethernet services.

Figure 2-12 Gigabit Ethernet Ports

The TE-100 Gigabit Ethernet ports are based on Ethernet transmission standards and provide native rate access with high throughput and effective bandwidth utilization. GbE ports integrate a IEEE 802.1D Layer 2 switch and SONET mapper. They can aggregate and transport Ethernet frames in the SONET contiguous payload. The GbE ports operate in full-duplex mode and perform Layer 2 classification, Ethernet and VLAN aggregation and switching, and per-port and per-flow traffic management.

Important: Only use SFPs approved by Force10 or equipment damage may occur, thus voiding any TE-100 warranty.

2 Gbe SFP Ports


TraverseEdge 100 User Guide, Section 2: Platform SpecificationsGigabit Ethernet Ports

On the TE-100, the mapper supports OC-12 worth of STS’s (six STS’s in each direction).

Specifications

This table lists the specifications for the two GbE ports.

Table 2-9 GbE Ports Specifications

ParameterSpecification

GbE SX GbE LX


Protection 1:1 equipment protection with second system module(switching time <= 50 ms)

Interface type 2 GbE SFP optical transceivers

Connector LC SMF connectors

Port data rate 1 Gbps


Bandwidth and Traffic Management Specifications per shelf

Transport bandwidth up to 2.488 Gbps

Concatenation Standard/VCAT/LCASVT1.5, STS-1, STS-3c

VC-12, HO VC-3, VC-4

Transport circuits 8 VCGs

Rate shaping Ethernet bandwidth guarantees and limits in 1 Mbps increments

Mapping GFP

Optical Interface Specifications

Media Multi-mode fiber (SX)

Single mode fiber (LX)

Single mode fiber(ZX)

Nominal wavelength (typical)1

1 For wavelength ranges see Chapter 4—“SONET/STM Ports Specifications,” Optical Interface Specifications (Summary), page 2-26.

850 nm 1310 nm 1430 nm

Transmitter output power2

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

–9.5 to -4 dBm –9 to -3 dBm 0 to 4 dBm

Receiver level1 –17 to -3 dBm –19 to -3 dBm -22 to 0 dBm

223 -1 PRBS, BER=10-10

Dispersion penalty 0 dB 1dB

Reach 0 10 km 80 km

Industry Standards Telcordia GR-253-CORE, GR-1377-COREIEEE 802.3z/x/ad, 802.1D/p/Q VLAN

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


Chapter 3 Ethernet Ports SpecificationsFast Ethernet Ports

Fast Ethernet Ports

The six Fast Ethernet (10/100BaseTX) ports are based on Ethernet transmission standards and provide native rate access with its high throughput and effective bandwidth utilization. The Fast Ethernet ports operate in full-duplex mode and perform Layer 2 classification, Ethernet and VLAN aggregation and switching, and per-port and per-flow traffic management.

Figure 2-13 6 Fast Ethernet Ports

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

For pinouts, see Figure 3-59 10/100BaseTX RJ-45 Pinouts, page 3-83.

Specifications

This table lists the specifications for the Fast Ethernet ports.

Table 2-10 Fast Ethernet (10/100 TX) Ports Specifications

Parameter Specification (FE)


Protection switching 1:1 equipment protection with second system module(switching time <= 50 ms)

Connector RJ-45

Media 2 pairs Twisted Pair Category 5 UTP

Reach 328 ft. or 100 meters

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

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

Loopback modes Terminal only

Bandwidth and Traffic Management Specifications per TE-100 shelf

Transport bandwidth up to 2.488 Gbps

Concatenation Standard/VCAT/LCASVT1.5, STS-1, STS-3c

VC-12, HO VC-3, VC-4

Transport circuits 8 VCGs

Rate shaping Ethernet bandwidth guarantees and limits in 1 Mbps increments

Mapping GFP

Industry Standards Telcordia GR-253-CORE, GR-1377-COREIEEE 802.3u/x/ad, 802.1D/p/Q VLAN

6 Fast Ethernet Ports


TraverseEdge 100 User Guide, Section 2: Platform SpecificationsFast Ethernet Ports


SECTION 2SECTION 2PLATFORM SPECIFICATIONS

Chapter 4 SONET/STM Ports Specifications

Introduction The TraverseEdge 100 (TE-100) system module has sockets for hot-swappable small form factor pluggable (SFP) transceivers that provide optical media and interface rate flexibility. The different versions of the system module provide SONET/SDH sockets for either OC-3/OC-12 or STM-1/4 SFPs and either OC-48 or STM-16 SFPs.

The SFPs provide these optical capabilities:• OC-3 or OC-12 section, line, STS path, and VT path termination• OC-48 section, line, and STS path termination• STM-1 or STM-4 regenerator section, multiplex section, high order, and low order

path termination• STM-16 regenerator section, multiplex section, and high order path termination

This chapter covers the following topics:• OC-3/STM-1 SFP Ports, page 2-22• OC-12/STM-4 SFP Ports, page 2-23• OC-48/STM-16 SFP Ports, page 2-24• Protection Switching, page 2-25• Optical Interface Specifications (Summary), page 2-26

Industry Standards

All SFP transceivers conform with the following industry standards:• ITU -T Rec. G.707, G. 783, G. 957 (Table 1, 2, and Figure 2)• ANSI T1.105-1995• Bellcore GR-253-CORE• Jitter Generation: ITU-T G.813 (Table 6)• Network Jitter: ITU-T G.825 (Table 4)• Input Jitter Tolerance: ITU-T G.825 (Table 3)

Important: Only use SFPs approved by Force10 to avoid possible equipment damage which will void any TE-100 warranty.


TraverseEdge 100 User Guide, Section 2: Platform SpecificationsOC-3/STM-1 SFP Ports

OC-3/STM-1 SFP Ports

Figure 2-14 OC-3/STM-1 Ports

System modules can be equipped with OC-3/STM-1 SFP optical transceivers for 15 km and 80 km applications.

Specifications

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

Table 2-11 OC-3/STM-1 Port Specifications

Parameter Specifications

IR1 (S-1.1) LR2 (L-1.2)

Module System module

Maximum active ports per shelf 1

Port data rate up to 155.52 Mbps

Approximate distance 15 km 80 km

Protection switching 1+1 APS, UPSR, 1+1 VT path, 1+1 STS path1+1 MSP, SNCP HO and LO path

Optical line coding Binary Non-Return-to-Zero

Line format ANSI T1.105-1995GR-253-CORE

ITU -T Rec. G.707 SONET/SDH

Connector SFP (LC SMF)

Fiber media type Standard singlemode fiber


1 For wavelength ranges see Optical Interface Specifications (Summary), page 2-26.

1310 nm 1550 nm



–15 to –8 dBm -5 to 0 dBm

Minimum extinction ratio 8.2 dB 10

Receiver signal level2 –29 to –7 dBm -33 to -10 dBm

–29 to –7 dBm (223 -1 PRBS, BER=10-10)

Dispersion penalty 0 dB 1 dB

OC-3/STM-1 Ports


Chapter 4 SONET/STM Ports SpecificationsOC-12/STM-4 SFP Ports



System modules can be equipped with OC-12/STM-4 SFP optical transceivers for 15 km and 80 km applications.

Specifications




IR1 (S-4.1) LR2 (L-4.2)



Port data rate 622.08 Mbps

Approximate distance 15 km 80 km

Protection switching 1+1 APS, UPSR, 1+1 VT path, 1+1 STS path1+1 MSP, SNCP HO and LO path


Line Format SONET ANSI T1.105-1995GR-253-CORE






1310 nm 1550 nm



–15 to –8 dBm -3 to 2 dBm

Minimum extinction ratio 8.2 dB 10 dB

Receiver signal level2 –28 to –7 dBm -28 to -8 dBm

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

Dispersion penalty 0 dB 1 dB

OC-12 Ports


TraverseEdge 100 User Guide, Section 2: Platform SpecificationsOC-48/STM-16 SFP Ports



System modules can be equipped with OC-48/STM-16 SFP optical transceivers for 2 km, 15 km, 40 km, 80 km, and 100 km applications.

Specifications




SR1 (I-16)

IR1(S-16.1)

LR1(L-16.1)

LR2(L-16.2)



Port data rate 2,488. 32 Mbps

Approximate distance 2 km 15 km 40 km 80 km

Protection switching 1+1 APS, UPSR, 1+1 STS path1+1 MSP, SNCP HO path protection


Line format ANSI T1.105-1995 GR-253-CORE






1310 nm 1550 nm

Transmitter output power2 –10 to –3 dBm -5 to 0 dBm –2 to +3 dBm

Minimum side mode suppression 30 dB

Minimum extinction ratio 8.2 dB

Receiver signal range2


–18 to –3 dBm

–18 to 0 dBm

–27 to –8 dBm

–26 to –8 dBm

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

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

Dispersion penalty 0 dB 0 dB 1 dB 2 dB

OC-48/STM-16 Ports


Chapter 4 SONET/STM Ports SpecificationsProtection Switching

Protection Switching

Protection switching for the optical ports is available in a one- or two-system module configuration.• With one system module, the transceiver in slot 2 provides facility protection. In

this configuration, the SFPs are in slots 1 and 2.• With two system modules, the second module provides facility protection as well

as equipment protection. In this configuration, the SFPs are slot 1 on the upper module and slot 2 on the lower one (as shown in Figure 2-17).

This graphic shows the SFPs in place for both configurations.

Figure 2-17 Facility Protection

When one or both system modules are present, one port is active and one is on standby. See Section 3—Installation and Configuration, Chapter 3—“Common Procedures,” Install a Second System Module, page 3-18 for step-by-step instructions on installing a second system module.

Active Port

Standby Port

Active Port Standby Port

Two System ModulesFacility and Equipment Protection

One System ModuleFacility Protection Only


TraverseEdge 100 U

ser Guide, Section

2: Platform

Specifications

Optical Interface Specifications (Sum

mary)

Page 2-26

Optical Interface Specifications

The table below summarizes all optical interface specifications. This table represents data for Force10 -approved SFPs. Additional SFPs may now be available; contact your Force10 Sales representative.

alty (dispersion).larger range than specified.

WARNING! The optical receiver of the OC-N long-reach optics can be damaged permanently if iver without proper s.

ur, thus voiding any TE-100

RxWavelength

Range(nm)

Dispersion Tolerance (ps/nm)

Temperature Range (degC)

1260 to 1600 0 -40 to 85

1260 to 1600 0 0 to 70

1260 to 1600 0 -40 to 85

1260 to 1600 0 -5 to 70

1260 to 1600 0 0 to 70

1260 to 1600 0 0 to 70

1260 to 1600 0 0 to 70

1260 to 1600 1600 0 to 70

1260 to 1600 1760 -5 to 70

1260 to 1600 1750 0 to 70

770 to 860 0 0 to 70

1270 to 1355 0 0 to 70

1260 to 1620 1600 -5 to 70

Force10 Netw

orksR

elease TE3.2.x

(Summary)

Table Notes:• All TE-100 optical ports use SFP optical cards.• The RX power (min) and Attenuation (max) values assume the worst case optical path pen• Not all vendors specify RX wavelength range. It is likely that the card will operate over a

overloaded. Do not connect the optical transmitter directly to the optical receattenuation. A minimum of 10 dB attenuation is required for long reach optic

Important: Only use SFPs approved by Force10 or equipment damage may occwarranty.

Table 2-14 SONET, STM, and GbE Optics

Application Approx Distance

(km)

Tx Power Range(dBm)

Rx Power Range(dBm)

Dispersion Penalty

(db)

Attenuation Range

Extinction Ratio (dB)

Tx Wavelength

Range(nm)SONET STM

OC-3 IR-1 STM-1 S-1.1 15 -15 to -8 -29 to -7 0 0 to 14 8.2 1261 to 1360

OC-3 LR-2 STM-1 L-1.2 80 -5 to 0 -33 to -10 1 10 to 28 10 1480 to 1580

OC-12 IR-1 STM-4 S-4.1 15 -15 to -8 -28 to -7 0 0 to 13 8.2 1274 to 1356

OC-12 LR-2 STM-4 L-4.2 80 -3 to 2 -27 to -8 1 10 to 24 10 1480 to 1580

OC-48 SR-1 STM-16 I-16 2 -10 to -3 -18 to -3 0 0 to 8 8.2 1266 to 1360

OC-48 IR-1 STM-16 S.16.1 15 -5 to 0 -18 to 0 0 0 to 13 8.2 1260 to 1360

OC-48 LR-1 STM-16 L-16.1 40 -2 to 3 -27 to -8 1 11 to 25 8.2 1280 to 1335

OC-48 LR-2 STM-16 L-16.2 80 -2 to 3 -26 to -8 2 11 to 24 8.2 1500 to 1580

OC-48 LR-2 STM-16 L-16.2 80 0 to 5 -26 to -8 2 13 to 26 8.2 1470 to 1610

OC-48 ELR STM-16 100 0 to 4 -27 to -8 2 12 to 27 8.2 1529.55 to 1562.23

1000Base SX 1000Base SX 0 -9.5 to -4 -17 to -3 0 0 to 7.5 9 830 to 860

1000Base LX 1000Base LX 10 -9 to -3 -19 to -3 0 0 to 10 9 1270 to 1360

1000Base ZX 1000Base ZX 80 0 to 4 -22 to 0 1 4 to 22 9 1430 to 1580


Chapter 5 Alarm Interface Specifications

Introduction This chapter includes the following topics:• Alarm Interface Description, page 2-27• Alarm Output Wire-Wrap Posts, page 2-29• Environmental Alarm Input Wire-Wrap Posts, page 2-29• Alarm Contact Summary, page 2-30• Alarm Cut-Off (ACO) Button, page 2-30

Alarm Interface Description

The TraverseEdge 100 (TE-100) system supports standard system critical, major, minor; visual and audible alarms, four environmental inputs, two environmental outputs, and an ACO. The following graphic shows where the system, environmental, and ACO alarm wire-wrap posts are located on the back of the TE-100 shelf.

Figure 2-18 Wire-Wrap Posts on Backplane

System Alarm Wire-Wrap

Posts

Environmental Alarm Wire-Wrap Posts

1-4 Inputs 1-2 Outputs

ACO Wire-Wrap

Posts


TraverseEdge 100 User Guide, Section 2: Platform SpecificationsAlarm Interface Description

The TE-100 system module generates system alarm signals and provides the common (COM), normally-open (NO), and normally-closed (NC) contacts through individual relays. The TE-100 shelf handles both alarm outputs and inputs. • Alarm outputs: When an alarm occurs, the system sets or clears an alarm and

changes the contact status accordingly. • Alarm inputs: When an external alarm event changes the contact status, the

system sets or clears the alarm.

Normally-open Contacts

System alarms operate by default using the COM and NO contacts. When an alarm state occurs the circuit between the COM and NO contacts is closed, generating a visual or audible alarm. A single system module is capable of generating and maintaining system alarms if the standby system module is out of service.

Fail-safe Alarm

All system alarms are masked, and a fail-safe alarm is generated if both system modules go out-of-service. The fail-safe alarm is the only normally-closed alarm. The fail-safe alarm is generated when system modules are installed and operational and go into an out-of-service state. The fail-safe alarm is also generated when both system modules are physically removed from the TE-100 shelf.

Environmental Alarms

On the back of the TE-100 shelf are four environmental alarm inputs and two environmental control outputs.


Chapter 5 Alarm Interface SpecificationsEnvironmental Alarm Input Wire-Wrap Posts

Alarm Output Wire-Wrap Posts

The rear of the shelf provides access to system alarm contacts through 0.045-inch (1.1 mm) square wire-wrap posts on 0.200-inch (0.5 mm) centers. The example below shows a typical alarm output setup using the optional Force10 -supplied power distribution and alarm panel (PDAP). The output alarms are dark gray.

Figure 2-19 System Alarm Wire-Wrap Posts

Environmental Alarm Input Wire-Wrap Posts

The following graphic shows the input environmental alarm labeling and wire-wrap post numbers located on the back of the shelf. The wire-wrap posts shown in dark gray are used for environmental alarm input cabling. The input alarms are dark gray.

Figure 2-20 Environmental Alarm Input Wire-Wrap Posts

Important: Other power sources may require different contact closures.

Important: Each set of system alarms provides common (COM), normally-open (NO), and normally-closed (NC) contacts. All alarms, except the fail-safe alarm, are connected using the NO and COM contacts. Connect the fail-safe alarm using NC and COM contacts.

Wire the posts shown in dark gray

to make alarm cabling

connections

1 2

CRITICALNO

3

4 5

MAJOR

6

7 8

MINOR

9

10 11

AUDIBLE

12

C NC

1514

FAILSAFE

13

1

IN RTN

2 4

3 6

4 8

17

ACO

16

(ENV) ALARMINPUT

1 10

NO C

2 12

(ENV) ALARMOUTPUT

1 2

3

5

9

11

7

TE100_00013

2

CRITICALNO

3

5

MAJOR

6

8

MINOR

9

11

AUDIBLE

12

C NC

1514

FAILSAFE

13

1

IN RTN

2 4

3 6

4 8

17

ACO

16

(ENV) ALARMINPUT

1 10

NO C

2 12

(ENV) ALARMOUTPUT

1 2

3

5

9

11

7

1

4

7

10

te100_00014

Wire the posts shown in dark gray to make alarm input cabling connections


TraverseEdge 100 User Guide, Section 2: Platform SpecificationsAlarm Contact Summary

Alarm Contact Summary

The following table summarizes the operation of the TE-100 alarm outputs and inputs:

Alarm Cut-Off (ACO) Button

An Alarm Cut-Off (ACO) button on the front of the system module lets you silence the alarm buzzer and reset timers for system maintenance alerts. Pressing the ACO button causes its LED to become amber and the alarm relay to open (disabling the alarm). The alarm condition still exists and the alarm LED is maintained. A secondary alarm switches off both the ACO button and its LED, closes (enable) the appropriate alarm relay, and switches on the matching LED.

Table 2-15 Alarm Outputs and Inputs

Alarm ContactContact Status

Alarm Set Alarm Clear

Outputs

Critical, Major, Minor, Audible NO/C Closed Open

C/NC Open Closed

Failsafe NO/C Open Closed

C/NC Closed Open

Env 1 & 2 NO/C Closed Open

n/a n/a n/a

Inputs

Env 1 through 4 IN/RTN Closed Open

ACO IN/RTN Closed Open



Chapter 6 Timing Specifications

Introduction Each TraverseEdge 100 (TE-100) shelf has a timing subsystem with a Stratum 3 clock and includes OC-3/STM-1, OC-12/STM-4, or OC-48/STM-16 Line and External DS1, as well as 2MHz and 64/8KHz timing interfaces. The shelf 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. The TE-100 system operates in and switches among these timing modes: Free-run (Stratum 3), Line, External and Hold-over.

The backplane provides primary and secondary T1input and output timing interfaces, and primary and secondary external input timing interfaces. These timing interfaces are routed to the system module which controls the timing references to the interface module.

When two system modules are in place, the timing system has 1:1 equipment protection.

The TE-100 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/E1, SF, ESF, Unframed, Basic Frame, and Multi-Frame.

This chapter includes the following topics:• Timing Interface Input and Output Wire-Wrap Posts, page 2-32• Timing Interface Contacts, page 2-33


TraverseEdge 100 User Guide, Section 2: Platform SpecificationsTiming Interface Input and Output Wire-Wrap Posts

Timing Interface Input and Output Wire-Wrap Posts

The back of the shelf provides access to timing interface contacts via 0.200-inch (0.5 mm) spaced, 0.045-inch (1.1 mm) square wire-wrap posts.

If you are using a coax cable from your timing source, you will need a standalone 75.120 W balun to connect to the wire-wrap posts.

The following graphic shows where these wire-wrap posts are located on the rear of the shelf.

Figure 2-21 Timing Interface Wire-Wrap Posts

The following graphic shows the timing interface labeling and wire-wrap post numbers.

Figure 2-22 Timing Interface1 Wire-Wrap Post Numbers and Labeling

1 E1, CC, 2M (2MHz) are SDH timing interfaces. (Planned for future release.)

T1/E1 CC2MAINB

AINB

AOUT

B

AOUT

B

-+

-+

-+

-+

-+ -+

-+

-+

-+

7 8

1 2 1 2

3 4 3 4

5 6 5 6

9 10 9 10

7 8


Chapter 6 Timing SpecificationsTiming Interface Contacts

Timing Interface Contacts

The following table provides T1/E1 timing interface contacts supported by the TE-100 system. (DS1 timing inputs are labeled T1/E1 on the back of the TE-100 shelf and are referred to as T1/E1 throughout this guide.)

The following table provides Composite Clock (CC2M) timing interface contacts supported by the system.

Table 2-16 T1 Timing Interface Wire-Wrap Posts

T1 Timing Interface Wire-Wrap Posts

Post# Description Post

# Description

1 T1/E1_INA+ 2 T1/E1_INA-3 T1/E1_INB+ 4 T1/E1_INB-5 Shield 6 Shield7 T1/E1_OUTA+ 8 T1/E1_OUTA-9 T1/E1_OUTB+ 10 T1/E1_OUTB-

Table 2-17 Composite Clock Timing Interface Wire-Wrap Posts

Composite Clock Timing Wire-Wrap Posts

Post# Description Post

# Description

1 CC2M_INA+ 2 CC2M_INA-3 CC2M_INB+ 4 CC2M_INB-5 Shield 6 Shield7 CC2M_OUTA+ 8 CC2M_OUTA-9 CC2M_OUTB+ 10 CC2M_OUTB-


TraverseEdge 100 User Guide, Section 2: Platform SpecificationsTiming Interface Contacts



Chapter 7 Management Interfaces Specifications

Introduction The system and interface modules on the TraverseEdge 100 (TE-100) shelf have interfaces for local technician access and Command Line Interface (CLI) support using a character-oriented terminal, such as a VT-100 or a PC with terminal emulation software:• DCN Ethernet Interface Connection, page 2-36• RS-232 CLI Modem Interface (DTE), page 2-37 • Data Communication Equipment RS-232 Interface (DCE), page 2-38

The three communication interfaces are shown here:

Figure 2-23 Three Communication Interfaces

DCN Ethernet Interface(RJ-45)

DTE RS-232 Interface(RJ-45)

RS-232 DCE Interfaces(RJ-45)


TraverseEdge 100 User Guide, Section 2: Platform SpecificationsDCN Ethernet Interface Connection

DCN Ethernet Interface Connection

This 10/100Base T Ethernet interface is located on the interface module. You can use it to connect a TE-100 node to the TransNav management system and to other remote management devices. The RJ-45 signal connections are bridged to the system module. The TransNav management system can always communicate to the active system module, even after a protection switch.

You can manage a network of TE-100 nodes over the service provider’s data communications network (DCN) as long as at least one TE-100 node is directly connected to that network through the TE-100 DCN Ethernet interface. This node is referred to as the TE-100 management gateway node (MGN). TE-100 nodes that have no direct connection to a DCN can communicate with the TransNav system indirectly, through the data communications channel (DCC) of an OC3/12 or OC-48 module interface.

The DCN Ethernet interface also allows telnet access directly to any node in the network through the DCC.

The DCN Ethernet interface is a data terminal equipment (DTE) interface type, supports both 10BaseT and 100BaseT, supports half- and full-duplex modes, and is compliant to IEEE 802.3 signal definition for an 8-pin RJ-45 connector.

Pinouts for the DCN Ethernet interface are provided in the following table.

Figure 2-24 DCN Ethernet Interface Connection Pinouts

DCN Ethernet RJ-45

Pin Description

1 ETH_TX+

2 ETH_TX-

3 ETH_RX

4 NC

5 NC

6 ETH_RX-

7 NC

8 NC


Chapter 7 Management Interfaces SpecificationsRS-232 CLI Modem Interface (DTE)

RS-232 CLI Modem Interface (DTE)

The RS-232 CLI modem interface, located on the interface module, uses an 8-pin RJ-45 connector that is configured as a data terminal equipment (DTE) port for connection to an external modem. It supports dial-up remote access to the active system module.

Pinout recommendations for the RS-232 CLI modem interface are provided in the following table.

Figure 2-25 RS-232 CLI Modem Interface (DTE) Pinouts

RS-232 Interface RJ-45DB Pinouts

EIA/TIA-561

Pin Description DB-9 DB-25

1

2

3 DTR 4 20

4 GND 5 7

5 RXD 3 3

6 TXD 2 2

7

8


TraverseEdge 100 User Guide, Section 2: Platform SpecificationsData Communication Equipment RS-232 Interface (DCE)

Data Communication Equipment RS-232 Interface (DCE)

This interface is provided by an RJ-45 on the front panel of each system module. It is an RS-232 interface that can be used for Command Line Interface (CLI) and OS access.

Pinouts for the DCE interface are provided in the following table.

Note: A DCE RJ-45 to DB-9 adapter is made available for ease of console connection.

Figure 2-26 RS-232 Interface (DCE) and DB-9 Pinouts

RS-232 Interface RJ-45 DB-9 Pinouts

Pin Description DB-9

1

2

3 TXD (IN) 3

4 GND 5

5

6 RXD (OUT) 2

7

8

9 8 7 6

5 4 3 2 1



Chapter 8 Power Interface Specifications

Introduction The TE-100 can use a direct DC connection for power. Force10 also offers an optional DC/DC power distribution and alarm panel (PDAP-15A) or external AC/DC power converter for use with the TraverseEdge 100 (TE-100) system.• PDAP-15A DC/DC (optional), page 2-39.• TE-100-AC/DC Power Converter (optional), page 2-40.

PDAP-15A DC/DC (optional)

The PDAP-15A provides GMT fuses (from 0.25 amps to 15 amps per fuse) for up to ten pieces of auxiliary equipment. The PDAP’s field replaceable fuses are accessible without having to remove the front panel. Force10 recommends a .

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

The PDAP-15A can be installed in a 19-inch (483 mm) or 23-inch (584 mm) telco rack.

The following illustrations show the front and rear views of the PDAP-15A.

Figure 2-27 PDAP Front View

Figure 2-28 PDAP Rear View

The PDAP-15A is not required if the TE-100 system is deployed with an existing power distribution panel. For specifications, see PDAP Specifications, page 2-40.

GMT Fuses

Alarm LEDs

Battery and Battery Return “B” Supply Battery and Battery Return

Distribution Terminal BlocksBattery and Battery Return “A” Supply

Chassis Ground


TraverseEdge 100 User Guide, Section 2: Platform SpecificationsPDAP Specifications


PDAP Specifications

This table lists the specifications for the PDAP-15A.

TE-100-AC/DC Power Converter (optional)

The external TE-100-AC/DC power converter unit—power supply with AC power cord—is not required if the TE-100 system is deployed with an existing power distribution panel or other external power source. One unit powers the shelf. Optionally, two units can share the load under normal conditions and provide power protection and hot-swap capability. In the redundant configuration, Force10 recommends the two units be put on separate circuit breakers.

The TE-100-AC/DC power supply has an AC input inlet and a DC output cable.

Figure 2-29 TE-100-AC/DC Power Supply

The TE-100 AC Power Cord—North American (1 for each power supply) has an AC input connector and a three-prong plug that inserts into an AC power outlet.

Figure 2-30 TE-100 AC Power Cord, USA

Table 2-18 PDAP-15A Specifications


Power Consumption < 1 watts

GMT Fuse Recommendation 3 amp fuse per power feeder (TE-100)

Dimensions (inches) 1.75 H x 17.25 W x 10 D

(millimeters) 44.5 H x 438 W x 254 D

Weight (pounds) 10 lbs

(kilograms) 4.5 kg

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

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

Power supply

DC output cable—battery and battery return wires

AC input inlet

AC input connector Three-prong AC plug

Chapter 8 Power Interface SpecificationsTE-100-AC/DC Power Specifications

TE-100-AC/DC Power Specifications

This table lists the specifications for the TE-100-AC/DC power supply.

Note: For further details, see http://www.trcelectronics.com/Sinpro/PDF/spu130.pdf.

This table lists the specifications for the TE-100-AC/DC power supply.

Table 2-19 TE-100-AC/DC Power Supply Specifications


Dimensions (inches) 1.46 H x 6.58 W x 2.56 D

(millimeters) 37 H x 167 W x 65 D

Output Power 130 watts

Output Voltage ~ 40 to 50 VDC

Operating Temperature/Humidity –0°C to +40°C/95% Relative Humidity

Storage Temperature/Humidity –40°C to +85°C/95% Relative Humidity

AC Input Inlet Type IEC 320/C14

DC Output Cable Length 71” (1800 mm)

Table 2-20 TE-100-AC/DC Power Cord Specifications


Three-prong Plug Type EL 302 (NEMA 5-15P)

AC Input Connector EL 701 (IEC 60320/C13)

Overall Length 6’ (1.83 m)

Operating Temperature –0°C to +40°C/95% Relative Humidity


TraverseEdge 100 User Guide, Section 2: Platform SpecificationsTE-100-AC/DC Power Specifications



Chapter 9 Network Topologies

Introduction The TraverseEdge 100 (TE-100) system is configurable for different topologies to satisfy important carrier objectives for cost reduction, network simplification, bandwidth efficiency, survivability, and service provisioning. This chapter contains the following topics:• Terminal Point-to-Point Topology, page 2-43• Ring Topology, page 2-44• Typical TE-100 Deployment, page 2-44• Network Management Planning, page 2-45

Terminal Point-to-Point Topology

You can configure the TE-100 system in a terminal point-to-point network (two nodes). The OC-3/12/48 interfaces on the TE-100 system support point-to-point topology. The facilities can be either unprotected or 1+1 APS/MSP protected.

This diagram shows TE-100 to a Traverse or a third-party ADM system in a traditional point-to-point topology. The entire SONET/SDH payload is terminated at each end of a fiber span.

Figure 2-31 Point-to-point Terminal Topology

Traverse or equivalent

te100_00015


TraverseEdge 100 User Guide, Section 2: Platform SpecificationsRing Topology

Ring Topology The TE-100 system can be deployed in a ring as shown below. One TE-100 node can be connected to only two other nodes, either to another TE-100 or to a Traverse (or equivalent) system. In this configuration, the ring can be either unprotected or protected as a uni-directional path switched ring (UPSR). A typical UPSR ring is shown in this diagram. For more information about network topologies and protection schemes, see Section 4—Configuring the Network, Chapter 3—“Creating a UPSR/SNCP Protection Group,” page 4-17.

Figure 2-32 OC3/12/48 UPSR Ring Topology

Typical TE-100 Deployment

Among the more complex topologies the TE-100 multiplexer can support is the following mix of ring and point-to-point. Here the TE-100 nodes are acting as edge multiplexers.

Figure 2-33 TE-100 Multiservice Edge Multiplexer

te100_00016

CoreNetworkT1

10/100or GbE

T3

T1

10/100or GbE

T3

T1

10/100or GbE

T3

BusinessLine

Services

BusinessLine

Services

OC-3/12/48Linear 1+1

155Mbps to 2.5 GbpsOC-N

Metro Access Ring(s)

OC-192 MetroSONET Ring

te100-00017


Chapter 9 Network TopologiesNetwork Management Planning

Network Management Planning

For details on deploying the TransNav management system, planning your network, and specifying IP addresses for in-band and out-of-band configurations, see the TransNav Management System Product Overview Guide chapter on network planning.


TraverseEdge 100 User Guide, Section 2: Platform SpecificationsNetwork Management Planning


SECTION 3 INSTALLATION AND CONFIGURATIONSECTION 3INSTALLATION AND CONFIGURATION

Contents

Chapter 1Installation Overview

Installation Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1Installation Checklists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2

Chapter 2Precautions

Environmental Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4Hardware Installation Precautions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4Electrical Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4Fiber Optic Cabling Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5Module Precautions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7Electrostatic Discharge Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8ESD Jack Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8

Chapter 3Common Procedures

Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9Removing and Replacing the Back Cover. . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10Inserting and Removing Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11Insert a Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12Remove a Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13Inserting and Removing a Blank Faceplate. . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13Insert a Blank Faceplate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14Remove a Blank Faceplate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14Inserting and Removing SFPs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15Insert an SFP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15Remove an SFP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-17Install a Second System Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18System Module Replacement as Standby— LED Indicators . . . . . . . . . . . . . 3-19Inserting a Replacement System Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-20Upgrading from Lower Speed System Module . . . . . . . . . . . . . . . . . . . . . . . . 3-20Replacing a Interface Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-20Inserting and Removing the Fan Assembly. . . . . . . . . . . . . . . . . . . . . . . . . . . 3-21Inserting and Removing the Fan Assembly Air Filter . . . . . . . . . . . . . . . . . . . 3-22Removing and Replacing the PDAP Protective Back Cover. . . . . . . . . . . . . . 3-23

Chapter 4Hardware Installation

Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-25


TraverseEdge 100 User Guide, Section 3 Installation and Configuration

Power Distribution and Alarm Panel (PDAP) Description . . . . . . . . . . . . . . . . 3-26Power System (PDAP-15A) Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-27Back Cover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-28Hardware Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-28Grounding the Shelf. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-30Rack Adapter Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-30

Chapter 5Alarm Interface Cabling

Before You Begin. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-31Visual Alarm Output Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-32Audible Alarm Output Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-33Optional Force10 PDAP-15A for Alarm Connections . . . . . . . . . . . . . . . . . . . 3-34PDAP-15A Power, Fuse, and Visual Alarm Wire-Wrap Posts. . . . . . . . . . . . . 3-35PDAP-15A Power Alarm Connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-36PDAP-15A Fuse Alarm Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-37PDAP-15A Visual Alarm Input Connections . . . . . . . . . . . . . . . . . . . . . . . . . . 3-38

Chapter 6Timing Interface Cabling

Before You Begin. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-39External Timing Interface Input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-40External Timing Interface Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-412MHz Timing Interface Output. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-42

Chapter 7Power Cabling Procedures—DC/DC

Before You Begin. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-46Power Cabling to the Backplane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-47PDAP Battery Distribution Cabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-47PDAP Battery Return Distribution Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-49Power Cabling to the Front Panel (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . 3-50Connecting PDAP-15A and External Power Supply . . . . . . . . . . . . . . . . . . . . 3-52Battery Supply Cabling to the PDAP-15A . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-53Battery Return Supply Cabling to the PDAP-15A . . . . . . . . . . . . . . . . . . . . . . 3-54Connect Supply Cables to the External Power Source . . . . . . . . . . . . . . . . . . 3-55Verify Polarity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-56Verify Voltage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-56Turn On Power to the Shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-56

Chapter 8Power Cabling Procedures—AC/DC

Before You Begin. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-58Power Cabling to the Backplane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-58TE-100-AC/DC Power Cabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-59Power Cabling to the Front Panel (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . 3-60



Chapter 9Management Interfaces Cabling

Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-64Connect the RS-232 DCE Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-64Connect the DCN Ethernet Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-66Connect the RS-232 DTE Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-67

Chapter 10Node Start-up and Initial Configuration

Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-69CLI Commands and Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-70Required Node Commissioning Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . 3-71Conditional Node Commissioning Parameters . . . . . . . . . . . . . . . . . . . . . . . . 3-73Node Start-Up and Initial Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-74Visual Status During and After Start-up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-77

Flashing red. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-77Solid green . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-77

Chapter 11Network Interface Cabling

Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-80DS1/E1 Cabling Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-81DS3/E3 Cabling Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8210/100BaseTX Fast Ethernet Cabling Procedure . . . . . . . . . . . . . . . . . . . . . . 3-83Fiber Optic Cabling Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-84Fiber Optic Transmit and Receive Testing . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-85

Chapter 12Cable Management

Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-87Cable Strain-Relief Bar (optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-88Routing Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-88




SECTION 3INSTALLATION AND CONFIGURATION

Chapter 1 Installation Overview

Introduction This chapter describes the following topics on installing a TraverseEdge 100 (TE-100) shelf and completing the initial node configuration. • Installation Process, page 3-1• Installation Checklists, page 3-2

Installation Process

Use these steps as a guideline to installing and configuring a TE-100 system.

Table 3-1 Installation Process and References

Step Procedure Reference

1 Read the precautions before attempting to install the shelf.

Chapter 2—“Precautions,” page 3-3.

2 Familiarize yourself with common procedures such as inserting and removing modules, SFPs, and back cover.

Chapter 3—“Common Procedures,” page 3-9.

3 Install the hardware, e.g., the optional power distribution and alarm panel (PDAP-15A) and the TE-100 shelf.

Chapter 4—“Hardware Installation,” page 3-25.

4 Install the alarm cabling. Chapter 5—“Alarm Interface Cabling,” page 3-31.

5 Install the timing cabling. Chapter 6—“Timing Interface Cabling,” page 3-39.

6 Bring power cabling from the power source (e.g., PDAP-15A) to the back or front of the shelf. Turn on power to the shelf.

Chapter 7—“Power Cabling Procedures—DC/DC,” page 3-45.

7 Insert one system module and install a cable between the RS-232 DCE interface on the module and a PC or laptop. Set up basic parameters, using the CLI interface.

Chapter 9—“Management Interfaces Cabling,” Connect the RS-232 DCE Interface, page 3-64 and Chapter 10—“Node Start-up and Initial Configuration,” page 3-69.

8 Install network cabling. Chapter 11—“Network Interface Cabling,” page 3-79.

9 Install other management interfaces as needed (DCN and DTE).

Chapter 9—“Management Interfaces Cabling,” page 3-63.


TraverseEdge 100 User Guide, Section 3: Installation and ConfigurationInstallation Checklists

Installation Checklists

See Appendix A—“Installation and Commissioning Checklists,” page 7-1 for a quick reference on installation procedures.



Chapter 2 Precautions

Introduction This chapter provides all necessary precautions. Follow these precautions to ensure personal safety and to avoid any equipment damage during installation, configuration, or maintenance procedures. The precautions listed in this chapter relate to the TE-100 shelf.• Environmental Precautions, page 3-4• Hardware Installation Precautions, page 3-4• Electrical Precautions, page 3-4• Fiber Optic Cabling Precautions, page 3-5• Module Precautions, page 3-7• Electrostatic Discharge Protection, page 3-8• ESD Jack Locations, page 3-8

Three types of warnings and precaution statements are used in the documentation.

WARNING! May cause personal injury if the warning is not followed; for example, this warning applies to electrical hazards.

WARNING! May cause personal injury if the warning is not followed; for example, this warning applies to optical hazards.

Important: May cause equipment damage if the precaution is not followed; for example, this note applies to electrostatic damage to equipment.


TraverseEdge 100 User Guide, Section 3: Installation and ConfigurationEnvironmental Precautions

Environmental Precautions

Hardware Installation Precautions

Electrical Precautions

Important: TE-100 shelves are designed to comply with GR-1089-CORE and GR-63-CORE and CE Mark requirements. Install and operate the shelf in environments that do not expose wiring, cabling, or connectors to the outside plant. Acceptable applications include Central Office Environments (COEs), Electronic Equipment Enclosures (EEEs), Controlled Environment Vaults (CEVs), huts, and customer premises environment.

Important: Always use caution while working in an environment with rotating or moving equipment parts (e.g., fan assemblies).

Important: This symbol is on the product and means do not discard Force10 products into residential or commercial waste.

Most countries or regions have established methods and procedures to collect and recycle electronic and electrical waste. Contact your local authorities for established procedures. If no local procedures are available, contact the Force10 Networks Technical Assistance Center (TAC).

Important: Always use thread-forming screws when installing a TE-100 shelf to ensure electrical continuity. This is especially critical when installing equipment in a rack coated with a non-conductive coating.

Important: The TE-100 shelf has a removable back cover to provide access to the backplane. The cover removes easily for cabling, but must be replaced during normal operation to ensure proper air flow and electromagnetic interference (EMI) protection.


WARNING! Only power-certified personnel should install power equipment and cabling.


Chapter 2 PrecautionsFiber Optic Cabling Precautions

Fiber Optic Cabling Precautions

WARNING! Do not connect central office battery and battery return supply cables at the central office source until all cabling at the Fuse Panel and TE-100 shelf backplane is complete. Ensure that Fuse Panel circuit breakers are in the OFF position before connecting battery and battery return supply cables to the central office source.

WARNING! For NEBS compliance, remove paint and any other non-conductive coatings on the surfaces between the mounting hardware and the rack framework. Clean all surfaces and apply anti-oxidant before joining. Coat all bare conductors with an appropriate anti-oxidant compound before crimp connections are made. Bring all connectors to a bright finish and coat with an anti-oxidant before making the connection.

Important: Always use a properly grounded Electrostatic Discharge (ESD) wrist strap when connecting copper cables to the Fuse Panel, backplane, and fan tray holder. Plug the ESD wrist strap into the ESD jack on the fan module, backplane or other confirmed source of earth ground. Refer to ESD Jack Locations, page 3-8.

WARNING! The TE-100 system is a class 1 product that contains a class IIIb laser, intended for operation in a closed environment with fiber attached. Do not look into the optical connector with power applied. Laser output is invisible, and eye damage can result. Do not defeat safety features that prevent looking into the optical connector.

WARNING! Follow all warning labels when working with optical fibers. Always wear eye protection when working with optical fibers. Never look directly into the end of a terminated or unterminated fiber or connector as it may cause eye damage.

Important: To prevent possible damage to the fiber optic cables, do not twist or cross one cable over another.

Important: To prevent possible damage to the fiber optic cables, do not bend optical fibers in a radius less than 1.5 inches (38 mm).


TraverseEdge 100 User Guide, Section 3: Installation and ConfigurationFiber Optic Cabling Precautions


Important: Always use a properly grounded Electrostatic Discharge (ESD) wrist strap when connecting optical cables to the fiber optic backplane. Plug the ESD wrist strap into the ESD jack on the TE-100 fan assembly or other confirmed source of earth ground. Refer to ESD Jack Locations, page 3-8.

Chapter 2 PrecautionsModule Precautions

Module Precautions Important: Always use a properly grounded Electrostatic Discharge

(ESD) wrist strap when handling TE-100 modules to prevent damage to the circuitry. Plug the ESD wrist strap into the ESD jack on the TE-100 fan assembly or other confirmed source of earth ground. Refer to ESD Jack Locations, page 3-8.

Important: Handle modules with care. Dropping a module can cause component or other damage beyond repair or use.

Important: Handle modules by the edges and faceplate only. Do not touch any module connectors or components.

Important: Observe all electrostatic sensitive device warnings and precautions when handling TE-100 modules.

Important: Insert the module in the TE-100 shelf using the guides for proper alignment. Make sure the module is horizontal, from left to right and that the module stays in the guides.

Important: Modules should insert easily into the TE-100 shelf; do not force the module into position. If the module does not insert easily, slide it back out and verify you are placing it in the correct position and inserting the module into the correct guides.

Important: To ensure EMI protection and proper cooling, place one-slot wide blank faceplates in an empty TE-100 slot (i.e., if you have only one system module). See Section 3—Installation and Configuration, Chapter 3—“Common Procedures,” Inserting and Removing a Blank Faceplate, page 3-13.


TraverseEdge 100 User Guide, Section 3: Installation and ConfigurationElectrostatic Discharge Protection

Electrostatic Discharge Protection

To avoid damage to integrated circuits, a properly grounded Electrostatic Discharge (ESD) wrist strap must be worn during the following installation and maintenance activities:• Handling TE-100 modules • Connecting copper or optical cables

ESD Jack Locations

ESD jacks provide a ground for the ESD wrist strap and are located on the fan assembly and on the backplane.

Figure 3-1 Fan Assembly with ESD Jack

Figure 3-2 ESD Jack on Back of Shelf

ESD Jack

ESD Jack



Chapter 3 Common Procedures

Introduction This chapter walks you through common procedures that are usually performed often.• Before You Begin, page 3-9• Removing and Replacing the Back Cover, page 3-10• Inserting and Removing Modules, page 3-11• Inserting and Removing a Blank Faceplate, page 3-13• Inserting and Removing SFPs, page 3-15• Install a Second System Module, page 3-18• System Module Replacement as Standby— LED Indicators, page 3-19• Inserting a Replacement System Module, page 3-20• Upgrading from Lower Speed System Module, page 3-20• Replacing a Interface Module, page 3-20• Inserting and Removing the Fan Assembly, page 3-21• Inserting and Removing the Fan Assembly Air Filter, page 3-22• Removing and Replacing the PDAP Protective Back Cover, page 3-23

Before You Begin

Review this information before you perform these common procedures.

Table 3-2 Common Procedures Requirements

Requirement Reference

Electrostatic Discharge (ESD) wrist strap. See Section 3—Installation and Configuration, Chapter 2—“Precautions,” ESD Jack Locations, page 3-8.

Equipment

TE-100 shelf and back cover.

PDAP and PDAP back cover.

Fan assembly and air filter.

System and interface modules.

SFPs


TraverseEdge 100 User Guide, Section 3: Installation and ConfigurationRemoving and Replacing the Back Cover

Removing and Replacing the Back Cover

The back cover is removed from the shelf during installation and cabling activities. The cover must be replaced after cabling is complete to ensure air cooling and electromagnetic interference (EMI) protection during normal operation.

Tools

Large flat blade screwdriver.

Large Phillips screwdriver.

Table 3-2 Common Procedures Requirements (continued)


Important: Always wear a properly grounded Electrostatic Discharge (ESD) wrist strap when removing back covers from the shelf as there are static-sensitive components on the backplane.

Table 3-3 Remove and Replace the Back Cover

Step Procedure

1 To remove the back cover, loosen the 4 captive fasteners until the panel pulls off easily.

Figure 3-3 View of the back panel and 4 captive screws

2 To replace the back cover, fit the cover onto the shelf and hand-tighten the captive fasteners.

3 The Remove and Replace the Back Cover procedure is complete.


Chapter 3 Common ProceduresInserting and Removing Modules

Inserting and Removing Modules

See the following topics for procedures on inserting and removing modules in the TE-100 shelf:• Insert a Module, page 3-12• Remove a Module, page 3-13

Important: Always use a properly grounded Electrostatic Discharge (ESD) wrist strap when handling TE-100 modules to prevent damage to the circuitry. Plug the ESD wrist strap into the ESD jack on the fan assembly, backplane, or other confirmed source of earth ground. Refer to Section 3—Installation and Configuration, Chapter 2—“Precautions,” ESD Jack Locations, page 3-8.

Important: Handle modules by the edges and faceplate only. Do not touch any module connectors or components.

Important: Observe all electrostatic sensitive device warnings and precautions when handling TE-100 modules.

Important: Insert the module into the shelf using the guides at the sides of the card cage for proper alignment. Make sure the module is horizontal, from side to side and that the module stays in the guides from the front to the back of the shelf.

Important: Modules should insert easily into the shelf; do not force the module into position. If the module does not insert easily, slide it back out and verify you are placing it in the correct position and inserting the module into the correct guides side to side.

Important: To ensure EMI protection and proper cooling, place one-slot wide blank faceplates in any empty slot.


TraverseEdge 100 User Guide, Section 3: Installation and ConfigurationInsert a Module


Insert a Module Follow these steps to insert a module.

Table 3-4 Insert a Module

Step Procedure

1 Make sure that the locking tabs at the right and left of the front panel are in the unlocked positions.

Figure 3-4 Module Locking Tab in the Unlocked Position

2 Hold the module parallel to the shelf, lining up the rear edges of the module with the guides.

Figure 3-5 TE-100 Shelf with Guides

3 Insert the module into the shelf, using the guides for proper alignment.

Each slot has guides to align the module into proper position for contact with the backplane. Use these guides to make sure the module is properly aligned. It is easier to align a module when the shelf is at eye level.

4 Push the center of the module face until the locking tabs start to close.

5 Push the locking tabs into their locked position to secure the module. The module is locked into position when the right and left tabs are pressed in completely.

Figure 3-6 Module Tab in the Locked Position

6 Hand-tighten the captive fasteners on the right and left sides of the module.

7 The Insert a Module procedure is complete.

Locking Tab in Unlocked Position

Guides for System Module Alignment

Guides for Interface Module Alignment

Locking Tab in Locked Position

Chapter 3 Common ProceduresInserting and Removing a Blank Faceplate

Remove a Module

Follow these steps to remove a module.

Inserting and Removing a Blank Faceplate

If your shelf has only one system module, install a blank faceplate to cover the empty slot. Below is a shelf with a system module in slot one and a blank faceplate in slot two.

Figure 3-8 Blank Faceplate in Slot Two

See the following topics for procedures on inserting and removing blank faceplates in the TE-100 shelf:• Insert a Blank Faceplate, page 3-14• Remove a Blank Faceplate, page 3-14

Table 3-5 Remove a Module

Step Procedure

1 Loosen the captive fasteners on either side of the module to be removed.

2 Pull the locking tabs out to unlock the module:

Figure 3-7 Module Tabs in the Unlocked Position

3 Pull the module straight out of the slot.

4 The Remove a Module procedure is complete.

Locking Tab in Unlocked Position

Important: Always wear a properly grounded Electrostatic Discharge (ESD) wrist strap when removing back covers from the shelf as there are static-sensitive components on the backplane.

System Module

Blank Faceplate


TraverseEdge 100 User Guide, Section 3: Installation and ConfigurationInsert a Blank Faceplate

Insert a Blank Faceplate

Follow these steps to insert a blank faceplate.

Remove a Blank Faceplate

Follow these steps to remove a blank faceplate.

Table 3-6 Insert a Blank Faceplate

Step Procedure

1 To install the blank faceplate, slide it into place with the gaskets at the top, as shown here, and hand-tighten the captive screws at either end.

Figure 3-9 Inserting Blank Faceplate with Gaskets on Top

2 The Insert a Blank Faceplate procedure is complete.

Table 3-7 Remove the Blank Faceplate

Step Procedure

1 Unscrew the captive fasteners.

2 Slide the faceplate out of the slot.

3 The Remove the Blank Faceplate procedure is complete.


Chapter 3 Common ProceduresInsert an SFP

Inserting and Removing SFPs

The TE-100 shelf comes equipped with system modules that support OC-3/STM-1 and OC-12/STM-4 SFP transceivers or system modules that support OC-48/STM-16 SFP transceivers.

Each system module has sockets for two SFPs. Possible configurations are as follows:• One system module with two SFPs• Two system modules and two SFPs (one SFP in each slot (slot-1/port-1 and

slot-2/port-2)

The system module SFPs are hot swappable, i.e., they can be removed or inserted while the system is on.

The interface module has two GbE SFP sockets to house 2 GbE SFPs. These SFPs can also be removed or inserted while the system is on.

SFP latches vary, depending on the manufacturer. The procedures below show SFPs with bale-clasp latches. Some SFPs have tabs on the bottom that click into place when inserted. To remove these SFPs, you grasp the SFP between thumb and forefinger, pressing the latch to release it as you pull the SFP gently from the socket.

Figure 3-10 SFP with Bottom-Tab Latch

See the following topics for procedures on inserting and removing SFPs in the TE-100 shelf:• Insert an SFP, page 3-15• Remove an SFP, page 3-17

Insert an SFP Follow these steps to insert SFPs, keeping in mind that the latches on your SFPs may vary slightly from the ones shown.


Important: A properly grounded ESD wrist strap must be worn at all times while handling SFPs.


TraverseEdge 100 User Guide, Section 3: Installation and ConfigurationInsert an SFP

Table 3-8 Insert an SFP

Step Procedure

1 Verify that the SFP is correct, either optical SFPs for the system module or the GbE SFPs for the interface module.

2 Orient the SFP as shown in the figure below.

Note: All SFP sockets are oriented as shown here, with the exception of the lower GbE SFP socket on the interface module. The lower GbE SFP has a latch-down orientation.

Figure 3-11 SFPs with Latch-up Orientation

3 Move the bail clasp down to unlatch it before inserting it into the slot.

4 Slide the SFP into the slot and move the bail clasp up (or, in the case of the lower GbE SFP, move it down) to secure it.

Figure 3-12 One System Module With Two SFPs

Figure 3-13 Two System Modules With Two SFPs

Figure 3-14 Interface Module with Two GbE SFPs

5 The Insert an SFP procedure is complete. For cabling information, see Chapter 11—“Network Interface Cabling,” Fiber Optic Cabling Procedures, page 3-84.

Move top clasp up and bottom clasp down to latch


Chapter 3 Common ProceduresRemove an SFP

Remove an SFP

Follow these steps to remove an SFP. You do not need to power down the system to insert or remove SFPs. They are hot swappable.

Important: A properly grounded ESD wrist strap must be worn at all times while handling TE-100 SFPs.

Table 3-9 Remove an SFP

Step Procedure

1 Disconnect the network fiber-optic cable from the SFP transceiver module connector, and insert the dust plugs in the SFP transceiver optical bores and the fiber-optic cable LC connectors.

For reattachment of fiber-optic cables, note which connector plug is transmit (TX) and which is receive (RX).

2 Pull the bale-clasp latch out and down to eject the SFP transceiver from the socket connector. Or, in the case of the lower GbE SFP, pull the latch out and up.

If the bale-clasp latch is obstructed and you cannot use your index finger to open it, use a small, flat-blade screwdriver or other long, narrow instrument to open the bale-clasp latch.

Figure 3-15 SFPs with Latch-up Orientation

3 Grasp the SFP transceiver between your thumb and index finger, and carefully remove it from the socket.

If your SFP has a bottom tab, grasp the SFP between thumb and index finger, pressing the tab to release the catch, and carefully remove it from the socket.

4 The Remove an SFP procedure is complete. For cabling information, see Chapter 11—“Network Interface Cabling,” Fiber Optic Cabling Procedures, page 3-84.

bale-clasp latch with latch-up orientation


TraverseEdge 100 User Guide, Section 3: Installation and ConfigurationInstall a Second System Module

Install a Second System Module

Adding a second system module triggers an automatic upgrade to equipment protection. Once you lock the second module in place, you have standby 1:1 equipment protection for all ports on the interface module. You must, however, move one SONET/STM SFP to the new system module.

If one system module is installed AND facility or path protection is enabled the first port on the system module is always the active port (slot-1/port-1). The second port the standby port (slot-1/port-2).

If two system modules are installed AND facility or path protection is enabled, the first port on the upper system module is the active port (slot-1/port-1). The second port on the lower module is the standby port (slot-2/port-2). In this two-system module configuration, both extra ports (slot-1/port-2 and slot-2/port-1) are not usable. 1:1 equipment protection for the interface ports is automatic.

To install a second system module and provide automatic 1:1 equipment protection for the interface ports, follow this procedure.

WARNING! Follow the procedure appropriate to your configuration to avoid dropping traffic.

Table 3-10 Install Second System Module

Step Procedure

1 Install the new system module in the empty slot. See Section 3—Installation and Configuration, Chapter 3—“Common Procedures,” Inserting and Removing Modules, page 3-11 for installation instructions.

2 Are you installing the new system module in slot 2?• Yes. Move the SFP and cables from the second socket in the original

module to the second socket on the new system module.

Figure 3-16 Moving SFP to New Module in Lower Slot

Go to Step 4.• No. Go to Step 3.

Original System Module

NewSystem Module

Before moving SFP and cables

After moving SFP and cables


Chapter 3 Common ProceduresSystem Module Replacement as Standby— LED Indicators

System Module Replacement as Standby— LED Indicators

When a new system module is placed as the standby module, the Power and Active/Standby LED indications are as follows:

The LEDs in the following tables apply to all cards.

3 If you are installing the new system module in the upper slot, move the SFP and cables from the first socket in the original module to the first socket on the new system module.

Figure 3-17 Moving SFP to New Module in Upper Slot

4 The Install Second System Module procedure is complete.

Table 3-10 Install Second System Module (continued)

Step Procedure

NewSystem Module

OriginalSystem Module

Before moving SFP and cables

After moving SFP and cables

Table 3-11 Power and Active/Standby—All Cards

LEDRED Amber GREEN OFF

Flashing Solid Flashing Solid Flashing Solid

Power

Initialization and diagnosis is underway but not complete.

Hardware failure

detected; replace the

card.

N/A N/A N/A

Initialization is complete and

the card is operational.

No power.

Active/ Standby N/A N/A

The card is unlocked and in Standby mode. Synchronization with the Active card is not complete.

The card is unlocked. The card type does not match the provisioned card type or the card is placed in an invalid slot.

The card is unlocked and in Standby mode. Synchronization with the Active card is complete.

The Active card is unlocked and operational.

The card is locked or initialization is not complete.


TraverseEdge 100 User Guide, Section 3: Installation and ConfigurationInserting a Replacement System Module

Inserting a Replacement System Module

Follow the step-by-step instructions to insert a module in Section 3—Installation and Configuration, Chapter 3—“Common Procedures,” Inserting and Removing Modules, page 3-11.

Upgrading from Lower Speed System Module

If you are upgrading from an OC-3/12 or STM-1/4 system module to an OC-48 or STM-16 system module, you are essentially starting over, as the database related to the previous card is automatically deleted. Repeat all the steps for installing, configuring, setting up the node, provisioning, and setting up services. (See Sections 3 through 6 of this guide for details.)

Replacing a Interface Module

As the system modules supply all the data for the interface module, you can insert the module, replace all the cabling, and all ports should be functional. There is no software running on the interface module.

WARNING! If you are upgrading from an OC-3/12 system module to an OC-48 system module, you must set up the node to recognize the new bandwidth (see Section 3—Installation and Configuration, Chapter 10—“Node Start-up and Initial Configuration,” page 3-69). You will have to make a fresh start with provisioning and setting up services, as the database related to the previous card is automatically deleted.

Important: A properly grounded ESD wrist strap must be worn at all times while handling TE-100 modules to prevent damage to the circuitry.

Important: Handle modules by the edges and face plate only. Do not touch any module connectors or components.


Chapter 3 Common ProceduresInserting and Removing the Fan Assembly

Inserting and Removing the Fan Assembly

The TE-100 system has a single fan assembly that slides into the fan cage to the left of the system modules.

Follow this procedure to insert the fan assembly.

Follow this procedure to remove the fan assembly.

Table 3-12 Insert the Fan Assembly

Step Procedure

1 Slide the fan assembly into the fan cage.

Important: Do not force the fan assembly into position. If it does not plug in easily, slide it back out and check for any obstructions that might prevent it from sliding into position.

Figure 3-18 Fan Cage and Assembly

2 Tighten the captive fastener to secure the fan assembly in place.

3 The Insert the Fan Assembly procedure is complete.

Table 3-13 Remove the Fan Assembly

Step Procedure

1 Loosen the captive fastener that holds the fan assembly in place.

2 Slide the fan assembly out of the fan cage.

3 The Remove the Fan Assembly procedure is complete.

Captive Fastener

Fan Cage


TraverseEdge 100 User Guide, Section 3: Installation and ConfigurationInserting and Removing the Fan Assembly Air Filter

Inserting and Removing the Fan Assembly Air Filter

The TE-100 fan assembly includes a metal air filter that is attached to the side of the fan assembly before the fan assembly is installed.

Follow this procedure to install the air filter.

Follow this procedure to remove the air filter.

Table 3-14 Insert the Fan Assembly Air Filter

Step Procedure

1 Make sure the air filter is clean and free of dust particles.

2 Slide the air filter into place, lining up the small tabs with the small holes on the fan assembly.

Figure 3-19 Attaching the Air Filter

3 The Insert the Fan Assembly procedure is complete.

Table 3-15 Remove the Fan Assembly Air Filter

Step Procedure

1 Lift the air filter from the fan assembly.

Figure 3-20 Removing the Air Filter

2 The Remove the Fan Assembly Air Filter procedure is complete.

Tabs Lined up with Holes

Pull up on the air filter


Chapter 3 Common ProceduresRemoving and Replacing the PDAP Protective Back Cover

Removing and Replacing the PDAP Protective Back Cover

Follow these instructions to remove the PDAP-15A protective back cover.

Follow these instructions to replace the PDAP protective back cover.

WARNING! The protective back cover is removed from the PDAP during power cabling activities. PDAP back covers must be replaced after cabling is complete and before –48 VDC power supply cables are connected to the central office source. The PDAP protective back cover must remain in place during normal operation to protect against possible electric shock.

Table 3-16 Remove the PDAP-15A Protective Back Cover

Step Procedure

1 Loosen (you need not remove) the two thumb screws securing the protective cover onto the back panel.

2 Pull the protective cover straight out to remove.

3 The Remove the PDAP-15A Protective Back Cover procedure is complete.

Table 3-17 Replace the PDAP-15A Protective Back Cover

Step Procedure

1 Align the protective cover to the back panel with the two thumb screws.

2 Tighten two thumb screws to secure the protective cover.

3 The Replace the PDAP-15A Protective Back Cover procedure is complete.


TraverseEdge 100 User Guide, Section 3: Installation and ConfigurationRemoving and Replacing the PDAP Protective Back Cover



Chapter 4 Hardware Installation

Introduction This chapter provides instructions for installing the power distribution and alarm panel (PDAP-15A, an optional power supply solution provided by Force10 ) and the TraverseEdge 100 (TE-100) shelf into a 7-foot (2200 mm), 19- or 23-inch (ETSI/500 mm or 600 mm) telco rack.• Before You Begin, page 3-25• Power Distribution and Alarm Panel (PDAP) Description, page 3-26• Power System (PDAP-15A) Installation, page 3-27• Back Cover, page 3-28• Hardware Installation, page 3-28• Grounding the Shelf, page 3-30• Rack Adapter Installation, page 3-30

Before You Begin

Review this information before you start the installation procedure.

Table 3-18 Installation Procedure Requirements


Familiarize yourself with all precautions and common procedures

See Section 3—Installation and Configuration, Chapter 2—“Precautions,” page 3-3 and Section 3—Installation and Configuration, Chapter 3—“Common Procedures,” page 3-9.

Electrostatic Discharge (ESD) wrist strap See Section 3—Installation and Configuration, Chapter 2—“Precautions,” ESD Jack Locations, page 3-8

Equipment and Tools

Standard 7-foot (2200 mm) high, 19- or 23-inch (ETSI/500 mm or 600 mm) wide telco rack

Standard conductive plated rack adapters with tread-forming screws required for rack installation

Stepladder (optional)

PDAP-15A Installation

Power system (e.g., PDAP-15A)


TraverseEdge 100 User Guide, Section 3: Installation and ConfigurationPower Distribution and Alarm Panel (PDAP) Description

Power Distribution and Alarm Panel (PDAP) Description

The TE-100 system is powered by an external power supply (or central office) battery (–48 VDC). The redundant external power supply (or central office) battery and battery return can be connected to the optional Power Distribution and Alarm Panel (PDAP-15A) supplied by Force10 or to an equivalent GMT fuse panel to meet building installation requirements.

The Force10 PDAP-15A has a 10-position Universal GMT Panel. Fuse input connections are made at the back of the PDAP-15A.

The PDAP-15A provides the following:• Terminates redundant –48 VDC central office battery.• Terminates central office battery return.• Distributes redundant battery and battery return.• Provides power protection for TE-100 shelves and auxiliary equipment.• Displays input power, fuse power, and critical, major, and minor bay alarms.• Provides a power disconnect device for the TE-100 shelves and auxiliary

equipment

For detailed specifications, see Section 2—Platform Specifications, Chapter 8—“Power Interface Specifications,” PDAP Specifications, page 2-40.

The following procedures assume that you are using the Force10 PDAP. If you are using another fuse panel, you may find these steps helpful for general reference.

Green (6 mm2 yellow-green) copper ground wire (up to #6 AWG for the PDAP-15A depending on the input interrupt device) for grounding.

1 double-hole copper barrel cable lugs (M5 stud with 5/8-inch spacing) for ground terminal connection.

Large phillips head screwdriver or lex socket

Four 12-24 thread-forming screws

TE-100 Shelf Installation

TE-100 shelf

Fourteen 12-24 thread-forming screws

A 5/16-inch socket for all thread-forming screws

A 1/4-inch socket (or nutdriver) for TE-100 shelf backplane power terminal connections

Table 3-18 Installation Procedure Requirements (continued)



Chapter 4 Hardware InstallationPower System (PDAP-15A) Installation

Power System (PDAP-15A) Installation

Install the power system hardware (e.g., PDAP-15A) in the bay and rack designated by your engineering work order. Install the power system at the top (using the first set of mounting holes) of a rack above the TE-100 shelf.

Note: Standard conductive plated rack adapters may be required for installation. If so, refer to Rack Adapter Installation, page 3-30.

WARNING! Ensure battery supply cables are not connected to the PDAP-15A or central office battery source before beginning this procedure to avoid personal injury.

Important: Always wear a properly grounded Electrostatic Discharge (ESD) wrist strap when making cable connections to the PDAP-15A and TE-100 backplane.

Important: Complete battery and battery return distribution cabling before bringing central office battery and battery return supply to the PDAP-15A.

WARNING! For NEBS compliance, remove paint and any other non-conductive coatings on the surfaces between the mounting hardware and the rack framework. Clean all surfaces and apply anti-oxidant before joining. Coat all bare conductors with an appropriate anti-oxidant compound before crimp connections are made. Bring all connectors to a bright finish and coat with an anti-oxidant before making the connection.

Table 3-19 Install Power System Hardware

Step Procedure

1 The PDAP-15A has a flange with a keyhole slot. Partially tighten a 12-24 thread-forming screw in the correct position on each side of the rack, leave about 1/4 inch (6.3 mm) of space between the rack and the screw head.

2 Position and lower the power system so the keyhole slots rest on the partially tightened screws.

3 Tighten screws.

Figure 3-21 Typical PDAP Rack Installation


TraverseEdge 100 User Guide, Section 3: Installation and ConfigurationBack Cover


Back Cover The TE-100 shelf has a removable back cover to provide access to the backplane. The cover is easily removed for cabling, but must be replaced during normal operation to ensure proper air flow and electromagnetic interference (EMI) protection. Refer to Section 3—Installation and Configuration, Removing and Replacing the Back Cover, page 3-10.

Hardware Installation

Install the TE-100 shelf in the central office bay and rack designated by your engineering work order, using a minimum of six 12-24 thread-forming screws.

The instructions may be too detailed if you are experienced in central office installations. In this case, scan the topic labels in the left margin for tasks to review or refer to Appendix A—“Installation and Commissioning Checklists,” page 7-1.

4 Place two additional screws and tighten to secure the power system to the rack.

5 Connect the grounding wire to the PDAP and to a confirmed source of Earth ground.

Figure 3-22 PDAP-15A Chassis Ground

6 The Install Power System Hardware procedure is complete. Continue to the next procedure, Install the TE-100 Shelf.

Table 3-19 Install Power System Hardware (continued)

Step Procedure

Chassis Ground

Important: Always use a properly grounded Electrostatic Discharge (ESD) wrist strap when handling TE-100 modules. Plug the ESD wrist strap into the ESD jack on the TE-100 fan assembly, backplane, or other confirmed source of earth ground. Refer to Section 3—Installation and Configuration, Chapter 2—“Precautions,” ESD Jack Locations, page 3-8.

Important: Observe all electrostatic sensitive device warnings and precautions when handling the TE-100 shelf.

Chapter 4 Hardware InstallationHardware Installation

Standard conductive plated rack adapters may be required for installation. If so, refer to Rack Adapter Installation, page 3-30.

Table 3-20 Install the TE-100 Shelf

Step Procedure

1 Does your installation require a rack adapter installation?• Yes. Refer to Chapter 4—“Hardware Installation,” Rack Adapter

Installation, page 3-30.• No. Go to the next step.

2 Lift the shelf to its assigned position in the rack.

Note: If you plan to install a cable strain-relief bar, allow enough space to accommodate the bar and cables below the shelf.

3 Align the flange holes with the holes in the rack.

4 Place a thread-forming screws through flange slots on both sides of the shelf and adjust as needed to maintain squareness.

Figure 3-23 Flange Slots on the Shelf

5 Partially tighten the thread-forming screws, and use a level to position the shelf.

6 After positioning the shelf using the level, tighten the screws to secure and ground the shelf to the rack.

7 The Install the TE-100 Shelf procedure is complete. Go to Section 3—Installation and Configuration, Chapter 5—“Alarm Interface Cabling,” page 3-31.

Important: Do not install TE-100 modules (cards) until all installation and cabling procedures are complete.

Mount with 2 fasteners per

side


TraverseEdge 100 User Guide, Section 3: Installation and ConfigurationGrounding the Shelf

Grounding the Shelf

The shelf is grounded to the rack using thread-forming screws and conductive plated rack adapters (as required for 23-inch (600 mm) rack installation). No additional grounding procedures are required when installed in a properly grounded telco rack.

Rack Adapter Installation

Use standard rack adapters to install TE-100 shelf components into a 23-inch (600 mm) telco rack. Rack adapters come with thread-forming mounting screws and in various lengths depending on your installation requirements.

Install the TE-100 shelf in the central office bay and rack designated by your engineering work order using a minimum of six 12-24 thread-forming screws.

Important: (SONET network only) For NEBS compliance, remove paint and any other non-conductive coatings on the surfaces between the mounting hardware and the rack framework. Clean all surfaces and apply anti-oxidant before joining.

Table 3-21 Install Rack Adapters

Step Procedure

1 Install conductive plated rack adapters on both sides of the rack. Align and position the rack adapter slots with the holes in the rack.

2 Place and tighten thread-forming screws through the rack adapter slots and into the rack. Thread-forming screws are used to ground the rack adapters (and TE-100 shelf) to the rack.

3 Place and tighten screws on each side of the TE-100 to secure it to the rack adapters (and thus the rack).

4 The Install Rack Adapters procedure is complete. Continue to the Hardware Installation, page 3-29.



Chapter 5 Alarm Interface Cabling

Introduction For a description of the TraverseEdge 100 (TE-100) alarms specifications, refer to Section 2—Platform Specifications, Chapter 5—“Alarm Interface Specifications,” page 2-27.

This chapter provides step-by-step instructions on how to connect visual, power, and alarm cables to the back of the TE-100 shelf. • Before You Begin, page 3-31• Visual Alarm Output Connections, page 3-32• Audible Alarm Output Connections, page 3-33• Optional Force10 PDAP-15A for Alarm Connections, page 3-34

The step-by-step instructions may be too detailed if you are experienced in CO installations. In this case, scan the topic labels in the left margin for tasks to review or refer to Section 7—Appendices, Alarm Cabling Checklist, page 7-4.

Before You Begin

Review this information before you start the initial configuration procedure.

Table 3-22 Alarm Interface Cabling Procedures Requirements



Optional Power Distribution and Alarm Panel (PDAP-A15).

Section 3—Installation and Configuration, Chapter 4—“Hardware Installation,” Power Distribution and Alarm Panel (PDAP) Description, page 3-26.

Tools and Equipment

22 or 24 AWG or 0.32 mm copper area wire.

Flats or wire cutters.

Wire-wrap tool for .045-inch x .045-inch (1.1 mm x 1.1 mm) posts.


TraverseEdge 100 User Guide, Section 3: Installation and ConfigurationVisual Alarm Output Connections

Visual Alarm Output Connections

Follow these steps to complete visual alarm output connections to the TE-100 backplane.

Important: Always wear a properly Electrostatic Discharge (ESD) wrist strap when making alarm wire connections to the TE-100 backplane.

Table 3-23 Connect Visual Alarm Outputs at the Shelf

Step Procedure

1 Are visual alarm input connections complete at a fuse panel?• Yes. Continue to Step 4 of this procedure.• No.

– If you have a Force10 PDAP-15A, complete the all procedures in the section Optional Force10 PDAP-15A for Alarm Connections, page 3-34 and then return to Step 4 of this procedure.

– If visual alarm input connections are made at some other central office visual alarm panel, go to Step 2.

2 Connect CO visual (critical, major and minor) alarm wires to the CO visual alarm panel following local procedures.

Note: Two wires are required for each visual alarm (critical, major, minor), a normally-open (NO) and common (C) wire.

3 Route the visual alarm wires from the CO visual alarm panel across the horizontal cable rack following local procedures.

4 Route the visual alarm wires down the rack rails to the TE-100 shelf in the rack following local procedures.

5 Remove the back cover from the backplane. Refer to Section 3—Installation and Configuration, Chapter 3—“Common Procedures,” Removing and Replacing the Back Cover, page 3-10 for detailed instructions.

6 Bring the visual alarm wires through the side cable port on the right side of the shelf.


Chapter 5 Alarm Interface CablingAudible Alarm Output Connections

Audible Alarm Output Connections

Follow these steps to complete audible alarm connections at the TE-100 backplane.

7 Bring the visual alarm wires over to the visual alarm wire-wrap posts on the backplane.

Figure 3-24 Visual Alarm Wire-Wrap Posts

8 Cut the visual critical alarm wires to the correct length and strip back the insulation by 3/4 inch (7 mm) exposing enough wire to make a minimum of five turns.

9 Terminate the wire on the critical alarm normally-open (NO) and the common (C) posts using a wire-wrap tool.

10 Repeat Steps 8 and 9 for major and minor visual alarm connections.

11 The Connect Visual Alarm Outputs at the Shelf procedure is complete. Continue to the Audible Alarm Output Connections, page 3-33.

Table 3-23 Connect Visual Alarm Outputs at the Shelf (continued)

Step Procedure

Critical, major, and minor visual alarm wire-wrap posts

Important: Always wear a properly Electrostatic Discharge (ESD) wrist strap when making alarm wire connections to the TE-100 backplane.

Table 3-24 Connect Audible Alarm Relay Outputs

Step Procedure

1 Connect CO audible (critical, major and minor) alarm wires to the CO alarm panel following local procedures.

Note: Two wires are required for each audible alarm (critical, major, minor), a normally-open (NO) and common (C) wire.

2 Route the audible alarm wires from the CO alarm panel across the horizontal cable rack and down the rack rails to the first shelf backplane following local procedures.


TraverseEdge 100 User Guide, Section 3: Installation and ConfigurationOptional Force10 PDAP-15A for Alarm Connections

Optional Force10 PDAP-15A for Alarm Connections

A Force10 Power Distribution and Alarm Panel (PDAP) is available to provide power distribution and alarm capabilities in a TE-100 installation. It is an optional, adjunct component of the TE-100 system.

The PDAP alarm connection topics are as follows:• PDAP-15A Power, Fuse, and Visual Alarm Wire-Wrap Posts, page 3-35• PDAP-15A Power Alarm Connections, page 3-36• PDAP-15A Fuse Alarm Connections, page 3-37• PDAP-15A Visual Alarm Input Connections, page 3-38

3 Remove the back cover from the backplane. Refer to Section 3—Installation and Configuration, Chapter 3—“Common Procedures,” Removing and Replacing the Back Cover, page 3-10 for detailed instructions.

4 Bring the audible alarm wires through the side cable port on the right side of the shelf.

5 Bring the audible alarm wires over to the audible alarm wire-wrap posts on the back of the shelf.

Figure 3-25 Audible Alarm Wire-Wrap Posts

6 Cut the audible alarm wires to the correct length and strip back the insulation by 3/4 inches (7 mm) exposing enough wire to make a minimum of five turns.

7 Terminate the wire on the audible alarm normally-open (NO) and common (C) posts using a wire-wrap tool.

8 The Connect Audible Alarm Relay Outputs procedure is complete. Continue to Chapter 6—“Timing Interface Cabling,” page 3-39.

Table 3-24 Connect Audible Alarm Relay Outputs (continued)

Step Procedure

Audible alarm wire-wrap posts

Route wires in this direction


Chapter 5 Alarm Interface CablingPDAP-15A Power, Fuse, and Visual Alarm Wire-Wrap Posts


PDAP-15A Power, Fuse, and Visual Alarm Wire-Wrap Posts

Power and fuse alarm cabling is connected from the PDAP-15A to one of the following components:• CO alarm panel for visual reporting of power failure, visual or audible reporting of

fuse A or B failure.• Back of the TE-100 shelf as environmental alarm input connections.

Visual alarm cabling is connected from the back of the shelf to 0.045-inch (1.1 mm) wire-wrap posts on the back of the PDAP-15A. The following graphic shows where these wire-wrap posts are located.

Figure 3-26 PDAP-15A Power, Fuse, and Visual Alarm Wire-Wrap Posts

The following graphic provides PDAP-15A power, fuse, and visual alarm labeling and wire-wrap post numbers.

Figure 3-27 PDAP-15A Alarm Wire-Wrap Post Numbers and Labeling

Power, Fuse, and Visual Alarm Wire-Wrap Posts

1

9

17

NO

NC

C

2

10

18

3

11

19

4

12

20

5

13

21

6

14

22

7

15

23

8

16

24

CRIT

MAJ

MIN

VIS AUD NC NO C

CONTACTS ACTIVATE

PWR FUSE BAY ALARMS

A R

te100_00019

TraverseEdge 100 User Guide, Section 3: Installation and ConfigurationPDAP-15A Power Alarm Connections

PDAP-15A Power Alarm Connections

Follow these steps to complete power alarm connections at PDAP-15A.

Important: Always wear a properly Electrostatic Discharge (ESD) wrist strap when making alarm wire connections to the PDAP-15A.

Table 3-25 Connect PDAP-15A Power Alarms

Step Procedure

1 Two alarm wires are required for Power alarms, normally-open (NO) and common (C) or normally-closed (NC) and common (C). Strip back the insulation by 3/4 inches (7 mm) exposing enough wire to make a minimum of five turns.

2 Power alarm wires are connected to wire-wrap posts on the back of the PDAP-15A. Terminate the power alarm wires using a wire-wrap tool.

Figure 3-28 PDAP-15A Power Alarm Input Wire-Wrap Posts

3 Route power alarm wires to the CO power alarm panel following local procedures.

4 Connect power alarm wires to the external or CO power alarm panel following local procedures.

Note: Two wires are required for the power alarm (normally-open and common or normally-closed and common).

5 The Connect PDAP-15A Power Alarms procedure is complete. Proceed to the Connect PDAP-15A Fuse Alarms procedure.

1

9

17

NO

NC

C

te100_00021


Chapter 5 Alarm Interface CablingPDAP-15A Fuse Alarm Connections

PDAP-15A Fuse Alarm Connections

Follow these steps to complete fuse alarm connections at PDAP-15A.


Table 3-26 Connect PDAP-15A Fuse Alarms

Step Procedure

1 Two alarm wires are required for visual and audible fuse alarms, normally-open (NO) and common (C) or normally-closed (NC) and common (C). Strip back the insulation by 3/4 inches (7 mm) exposing enough wire to make a minimum of five turns.

2 Fuse alarm wires are connected to wire-wrap posts on the back of the PDAP-15A. Terminate the visual fuse alarm wires using a wire-wrap tool.

Figure 3-29 PDAP-15A Fuse Alarm Input Wire-Wrap Posts

3 Repeat Steps 1 and 2 for the audible fuse alarm wires.

4 Route wires to the CO fuse alarm panel following local procedures.

5 Connect visual and audible fuse alarm wires to the CO fuse alarm panel following local procedures.

Note: Two wires are required for each fuse alarm (normally-open and common or normally-closed and common).

6 The Connect PDAP-15A Fuse Alarms procedure is complete. Proceed to the Connect PDAP-15A Visual Alarm Inputs procedure.

2

10

18

3

11

19

VIS AUD

FUSE

NO

NC

C

te100_00022


TraverseEdge 100 User Guide, Section 3: Installation and ConfigurationPDAP-15A Visual Alarm Input Connections

PDAP-15A Visual Alarm Input Connections

Follow these steps to complete visual alarm input connections at the back of the PDAP-15A.


Table 3-27 Connect PDAP-15A Visual Alarm Inputs

Step Procedure

1 Will visual alarm input connections be made at the PDAP-15A?• If yes, go to Step 2.• If no, and visual alarm input connections are made at a central office

visual alarm panel, go to the Visual Alarm Output Connections procedure on page 3-32.

2 Two alarm wires are required for each type of visual alarm. Strip back the insulation by 3/4 inches (7 mm) exposing enough wire to make a minimum of five turns.

3 Visual alarm input wires are connected to wire-wrap posts on the back of the PDAP-15A. Terminate the two alarm wires for critical (CRIT) activate (A) and Return (R) using a wire-wrap tool.

Figure 3-30 PDAP-15A Visual Alarm Input Wire-Wrap Posts

4 Repeat Steps 1 and 2 for major (MAJ)/common (C) and minor (MIN)/common (C) wires.

5 Route visual alarm cables to the left side of the PDAP-15A and down the rack rails to the first TE-100 shelf.

6 The Connect PDAP-15A Visual Alarm Inputs procedure is complete.

7

15

23

8

16

24

CRIT

MAJ

MIN

BAY ALARMS

A R

TE100-00023



Chapter 6 Timing Interface Cabling

Introduction This chapter provides step-by-step instructions for connecting timing inputs from the external clock timing source and timing outputs from a TraverseEdge 100 (TE-100) shelf with wire-wrap posts to the external clock.• Before You Begin, page 3-39• External Timing Interface Input, page 3-40• External Timing Interface Output, page 3-41

For timing interface specifications, refer first to Section 2—Platform Specifications, Chapter 6—“Timing Specifications,” page 2-31. For timing configuration information, refer to Section 4—Configuring the Network, Chapter 2—“Configuring Network Timing,” page 4-9.

The step-by-step instructions may be too detailed if you are experienced in CO installations. In this case, scan the topic labels in the left margin for tasks to review or refer to Section 7—Appendices, Timing Checklist, page 7-6.

Before You Begin


Table 3-28 Timing Interface Cabling Procedures Requirements



Tools and Equipment

2-pair 22 AWG or 0.32 mm copper area wire (with drain wire). If you are using a coax cable from your timing source, you will need a standalone 75.120 Ω balun to connect to the wire-wrap posts.

Flats or wire cutters.

Wire-wrap tool for .045-inch x .045-inch (1.1 mm x 1.1 mm) posts.


TraverseEdge 100 User Guide, Section 3: Installation and ConfigurationExternal Timing Interface Input

External Timing Interface Input

Follow these steps to complete external timing interface primary and secondary1 input connections at the backplane.

1 The secondary external timing input connection is optional.

Important: Always wear a properly grounded Electrostatic Discharge (ESD) wrist strap when making connections to the TE-100 main backplane.

Table 3-29 Complete External Timing Interface Input Connections

Step Procedure

1 Are you using coax cable (instead of twisted-pair wire) from the external timing source to TE-100 shelf?• Yes. Connect timing coax cables to the external primary and

secondary timing source and run the cables to the shelf following local procedures. Continue to Step 3.

• No. Go to the next step.

2 Connect 22 AWG (0.32 mm) timing wires to the external primary and secondary (optional) timing source and run the cables to the TE-100 shelf following local procedures.

Note: Two 2-pair wires are required for primary and secondary (T1/E1_INA and T1/E1_INB) connections.

3 Route the primary and secondary timing wires across the horizontal cable rack and down the rack rails to the left side of the shelf.

4 Remove the back cover from the shelf. Refer to Section 3—Installation and Configuration, Chapter 3—“Common Procedures,” Removing and Replacing the Back Cover, page 3-10 for detailed instructions.

5 Bring the primary and secondary input timing wires through the side cable port to the T1/E1_INA and T1/E1_INB wire-wrap posts on the backplane.

Figure 3-31 External Timing Input Wire-Wrap Posts

Bring primary and secondary input timing wires here


Chapter 6 Timing Interface CablingExternal Timing Interface Output

External Timing Interface Output

Follow these steps to complete external timing interface primary and secondary (optional) output connections to the TE-100 shelf.

6 Are you using coax cables (instead of twisted-pair wire) from the external timing source to the TE-100 shelf?• Yes. Cut the coax cables to the correct length and terminate to the

standalone 75/120Ω baluns using BNC connectors. Terminate twisted-pair wire to the baluns IDC connectors.

• No. Continue to Step 8.

7 Cut the primary and secondary input timing wires to the correct length and strip back the insulation by 3/4 inches (7 mm) exposing enough wire to make a minimum of five turns.

8 Terminate primary and secondary wires on the timing interface posts using a wire-wrap tool.

9 Terminate drain wire to shield wire-wrap posts using wire-wrap tool.

10 The Complete External Timing Interface Input Connections procedure is complete. Continue to the next procedure, Complete the External Timing Interface Output Connections.

Table 3-29 Complete External Timing Interface Input Connections (continued)

Step Procedure

Important: Always wear a properly grounded Electrostatic Discharge (ESD) wrist strap when making connections to the TE-100 shelf.

Table 3-30 Complete the External Timing Interface Output Connections

Step Procedure

1 Remove the back cover from the TE-100 shelf. Refer to Section 3—Installation and Configuration, Chapter 3—“Common Procedures,” Removing and Replacing the Back Cover, page 3-10 for detailed instructions.

2 Strip back the insulation by 3/4 inches (7 mm) exposing enough wire to make a minimum of five turns).

Note: Two 2-pair wires are required for primary and secondary (T1/E1_OUTA and T1/E1_OUTB) connections.


TraverseEdge 100 User Guide, Section 3: Installation and Configuration2MHz Timing Interface Output

2MHz Timing Interface Output

Follow these steps to complete 2MHz timing interface primary and secondary output connections to the TE-100 shelf. The secondary 2MHz timing output connection is optional.

3 Terminate primary and secondary output timing wires on T1/E1_OUTA and T1/E1_OUTB wire-wrap posts using a wire-wrap tool.

Figure 3-32 T1 Timing Output Wire-Wrap Posts

4 Route the primary and secondary output timing wires up the rack rails and across the horizontal cable rack to the central office SASE clock.

5 Terminate output timing wires at the central office SASE clock.

6 The Complete the External Timing Interface Output Connections procedure is complete. Continue to the next section.

Table 3-30 Complete the External Timing Interface Output Connections

Step Procedure

Terminate primary and secondary

output timing wires here

Note that the CC/2M output connectors

are not used

Important: Always wear a properly grounded Electrostatic Discharge (ESD) wrist strap when making connections to the TE-100 main backplane.

Table 3-31 2MHz Timing Interface Output Connections

Step Procedure

1 Remove the back cover from the shelf. Please refer to Section 3—Installation and Configuration, Removing and Replacing the Back Cover, page 3-10 for detailed instructions.

2 Strip back the insulation on the primary and secondary (optional) output timing wires by 7 mm.

Note: Two 2-pair wires are required for primary and secondary (CC2M_OUTA and CC2M_OUTB) connections.

3 Terminate primary and secondary output timing wires on CC2M_OUTA and CC2M_OUTB wire-wrap posts using a wire-wrap tool.


Chapter 6 Timing Interface Cabling2MHz Timing Interface Output

4 Route the 2MHz primary and secondary output timing wires up the rack rails and across the horizontal cable rack to the central office SASE clock.

5 Terminate 2MHz output timing wires at the central office external clock.

6 Are there additional TE-100 shelves in the rack that provide 2MHz timing signals to the central office external clock lock?• Yes. Repeat Steps 1 through 5 for each shelf.• No. The 2MHz Timing Interface Output Connections procedure is

complete. Continue to Chapter 7—“Power Cabling Procedures—DC/DC,” page 3-45.

Table 3-31 2MHz Timing Interface Output Connections (continued)

Step Procedure


TraverseEdge 100 User Guide, Section 3: Installation and Configuration2MHz Timing Interface Output



Chapter 7 Power Cabling Procedures—DC/DC

Introduction A Force10 power distribution and alarm panel (PDAP-15A) is available to provide DC/DC power distribution and alarm capabilities in a TraverseEdge 100 (TE-100) system installation. For power terminal interface specifications, refer to Section 2—Platform Specifications, Chapter 8—“Power Interface Specifications,” page 2-39.

The TE-100 shelf allows you to connect cables from the PDAP-15A or other power supply source to the back or front of the shelf.

This chapter provides step-by step procedures for bringing power to the TE-100 shelf.• Before You Begin, page 3-46• Power Cabling to the Backplane, page 3-47• Power Cabling to the Front Panel (Optional), page 3-50• Connecting PDAP-15A and External Power Supply, page 3-52

The instructions may be too detailed if you are an experienced installer. In this case, scan the topic labels in the left margin for tasks to review or refer to Section 3—Installation and Configuration, Power Cabling to the Backplane, page 3-47.

WARNING! If you require an external AC/DC power source installation for the TE-100, see Chapter 8—“Power Cabling Procedures—AC/DC,” page 3-57.


TraverseEdge 100 User Guide, Section 3: Installation and ConfigurationBefore You Begin

Before You Begin


Table 3-32 Power Cabling Procedure Requirements


PDAP-15A (or the equivalent) and TE-100 shelf is installed

Section 3—Installation and Configuration, Chapter 4—“Hardware Installation,” page 3-25


General Tools and Equipment

Small and medium flat blade screwdrivers

Volt-Ohm Meter

Two 4 amp GMT fuses

Backplane Power Cabling Tools

Single-hole copper barrel cable lugs

5 supplied cables, #16 AWG (or equivalent):• 2 red - 48 VDC A and B• 2 black (return A and return B)• 1 green chassis ground

Front-Panel Power Cabling Tools

1 supplied cable bundle with white plug at one end and bare wire (or lugs) at the other

1 green vertical plug

PDAP-15A Connection with External Power Supply Tools

2 (customer-supplied) battery supply cables

2 (customer-supplied) battery return supply cables

4 (customer-supplied) cable lugs for connection at the central office battery source

4 double-hole copper barrel cable lugs (M5 stud with 5/8-inch spacing) for battery and battery return supply cable connection to the PDAP-15A

4 M5 nuts to connect battery and battery return supply cables at the PDAP-15A

4 M5 lock washers to connect battery and battery return supply cables at the PDAP-15A

Wrench with 5/16-inch nut socket


Chapter 7 Power Cabling Procedures—DC/DCPDAP Battery Distribution Cabling

Power Cabling to the Backplane

You can connect power to the back or front of the shelf. The following topics first describe the procedures for rear access and then front-panel access.• PDAP Battery Distribution Cabling, page 3-47• PDAP Battery Return Distribution Cables, page 3-49• Power Cabling to the Front Panel (Optional), page 3-50

PDAP Battery Distribution Cabling

Follow these steps to connect battery distribution cables from the PDAP-15A to a TE-100 shelf.

Table 3-33 Connect the PDAP-15A Battery Distribution Cabling

Step Procedure

1 Remove the protective cover from the back of the PDAP-15A. Refer to Section 3—Installation and Configuration, Chapter 3—“Common Procedures,” Removing and Replacing the PDAP Protective Back Cover, page 3-23 for detailed instructions.

2 Remove the back cover from the first TE-100 shelf in the rack. Refer to Section 3—Installation and Configuration, Chapter 3—“Common Procedures,” Removing and Replacing the Back Cover, page 3-10 for detailed instructions.

3 Use the supplied red cable or use a crimping tool to attach a single-hole copper barrel cable lug to one end of an 16 AWG red (9 mm blue) wire for the battery distribution cable.

4 Remove the KEP nut from the battery "A" distribution power terminal, position A1 (shelf 1).

Figure 3-33 PDAP-15A Battery Distribution Power Terminals

5 Place the single-hole copper barrel cable lug on the battery "A" distribution power terminal. Replace and tighten the nut.

6 Route the battery "A" distribution cable to the left side of the PDAP-15A and down the rack rails to the TE-100 shelf.

Battery “B” Distribution Battery “A” Distribution


TraverseEdge 100 User Guide, Section 3: Installation and ConfigurationPDAP Battery Distribution Cabling

7 Bring the battery "A" distribution cable through the side cable port of the shelf to the –48VDC A power terminal (labeled -A) on the back of the TE-100 shelf to determine the length of the cable.

Figure 3-34 Backplane Power Distribution

8 Use diagonal cutters to cut the battery distribution cable to the correct length.

9 Use a crimping tool to attach a single-hole copper barrel cable lug to the end of the battery distribution cable.

10 Remove the screw labeled -A from the power terminal.

Figure 3-35 Remove - A Screw from Power Terminal

11 Place the battery distribution copper barrel cable lug over the –48VDC A power terminal on the backplane. Replace and tighten the screw.

12 The Connect the PDAP-15A Battery Distribution Cabling procedure is complete. Continue to the next procedure, Connect the PDAP-15A Battery Return Distribution Cabling.

Table 3-33 Connect the PDAP-15A Battery Distribution Cabling (continued)

Step Procedure

Insert the -48VDC (-A) cable here

Insert the -48VDC (+A) cable here

Insert the -48VDC (+B) cable here

Insert the -48VDC (-B) cable here

Remove this screw


Chapter 7 Power Cabling Procedures—DC/DCPDAP Battery Return Distribution Cables

PDAP Battery Return Distribution Cables

Follow these steps to connect battery return distribution cables from the PDAP-15A to a shelf.

Table 3-34 Connect the PDAP-15A Battery Return Distribution Cabling

Step Procedure

1 Use the supplied black cable. Alternately, use a crimping tool to attach a single-hole copper barrel cable lug to one end of an 16 AWG (9 mm) black wire for the battery return distribution cable.

2 The PDAP-15A provides battery return A and B distribution terminal lugs. Remove the KEP nuts from the battery return terminal lug.

Figure 3-36 PDAP-15A Battery Return Distribution Terminals

3 Place the copper barrel cable lug on the battery return terminals. Replace and tighten the KEP nut.

4 Route the battery “A” return distribution cable to the left side of the PDAP-15A and down the rack rails to the first TE-100 shelf.

5 Bring the battery return distribution cable through the side port of the shelf to the RETURN_A power terminals on the back of the TE-100 shelf to determine the length of the cable.

6 Use diagonal cutters to cut the battery distribution cable to the correct length.

7 Use a crimping tool to attach a single-hole copper barrel cable lug to the end of the battery return distribution cable.

8 Remove the screw labeled +A from the power terminal.

Figure 3-37 Remove + A Screw from Power Terminal

9 Place the battery return distribution cable lug over the RETURN A power terminal. Replace and tighten the screw.

Battery “B” Return Distribution Battery “A” Return Distribution

Remove this screw


TraverseEdge 100 User Guide, Section 3: Installation and ConfigurationPower Cabling to the Front Panel (Optional)

Power Cabling to the Front Panel (Optional)

You can connect power to the front panel of the TE-100 shelf.

Follow this procedure if your site requires front-panel access for power cabling. Shown here is the backplane when the first part of this procedure (connecting the supplied cables) is complete:

Figure 3-38 Backplane with Cables for Front Panel Power Access

10 Repeat Steps 1 through 9 to connect battery return “B” distribution cable. Connect the battery return cable from position B1 on the PDAP-15A battery return distribution bus bar to the RETURN_B power terminals.

11 The Connect the PDAP-15A Battery Return Distribution Cabling procedure is complete. Continue to the next procedure, Connecting PDAP-15A and External Power Supply, page 3-52.

Table 3-34 Connect the PDAP-15A Battery Return Distribution Cabling

Step Procedure

WARNING! To avoid personal injury, ensure that cables are not connected to the power source before beginning this procedure.

Important: Always wear a properly grounded Electrostatic Discharge (ESD) wrist strap when making cable connections to the TE-100 shelf.

Important: Complete cabling before bringing power supply to the shelf.

Backplane Power Connectors

Cable connecting backplane power and front power access plug

Backplane Power Cable


Chapter 7 Power Cabling Procedures—DC/DCPower Cabling to the Front Panel (Optional)

Table 3-35 Set Up Front Panel Power Cabling Access

Step Procedure

1 Remove the protective cover from the back of the shelf. Refer to Section 3—Installation and Configuration, Chapter 3—“Common Procedures,” Removing and Replacing the Back Cover, page 3-10 for detailed instructions.

2 Remove the screws from the external power terminals.

Figure 3-39 Power Terminals on the Backplane

3 Using the supplied cable bundle (with the white plug at one end), place the single-hole copper barrel cable lugs on the power terminals, using the labels on the backplane and the cables as a guide.

4 Replace and tighten the screws.

5 Plug the other end of the cable bundle into the white socket of the front-access cable bundle (already installed). (See Figure 3-38 Backplane with Cables for Front Panel Power Access, page 3-50.)

6 Plug the supplied green vertical plug into the green socket on the left side of the front panel.

Figure 3-40 Front Panel Power Access Plug

7 Bring the battery distribution cables from the PDAP-15A to the plug on the front panel by following steps 1-8 of the Connect the PDAP-15A Battery Distribution Cabling procedure on page 3-47.

Remove the 5 screws






TraverseEdge 100 User Guide, Section 3: Installation and ConfigurationConnecting PDAP-15A and External Power Supply

Connecting PDAP-15A and External Power Supply

This section provides step-by-step instructions on how to connect:• Battery cables from the external power supply to the PDAP-15A• Battery return cables from the external battery return supply to the PDAP-15A

The topics are as follows:• Battery Supply Cabling to the PDAP-15A, page 3-53• Battery Return Supply Cabling to the PDAP-15A, page 3-54• Connect Supply Cables to the External Power Source, page 3-55• Verify Polarity, page 3-56• Verify Voltage, page 3-56

The instructions may be too detailed if you are an experienced installer. In this case, scan the topic labels in the left margin for tasks to review or refer to Section 7—Appendices, PDAP-15A DC/DC Power Cabling Checklist, page 7-7.

8 Strip the ends of the cables and insert the wire into the plug at the label -A and use a small flat screwdriver to tighten the screw on the front of the plug until the wire is secure.

9 Bring the battery distribution return cables from the PDAP-15A to the plug on the front panel by following Steps 1 through 6 of the Connect the PDAP-15A Battery Return Distribution Cabling procedure on page page 3-49.

10 Strip the ends of the cables and insert the wire into the plug at the label +A. Use a small flat screwdriver to tighten the screw on the front of the plug until the wire is secure.

11 Repeat Steps 7 through 10 for -B and +B cables.

12 The Set Up Front Panel Power Cabling Access procedure is complete.

Table 3-35 Set Up Front Panel Power Cabling Access (continued)

Step Procedure


Chapter 7 Power Cabling Procedures—DC/DCBattery Supply Cabling to the PDAP-15A

Battery Supply Cabling to the PDAP-15A

Battery "A" and "B" supply cables (customer-supplied) are run from the central office battery distribution fuse bay (or other battery source) to the PDAP-15A. Complete battery and battery return distribution cabling before bringing central office battery and battery return supply cables to the PDAP-15A.

Follow these steps to connect battery supply cables to the PDAP-15A.

WARNING! Ensure battery supply cables are not connected to central office battery source before beginning this procedure to avoid personal injury.

Important: Always wear a properly grounded Electrostatic Discharge (ESD) wrist strap when making cable connections to the PDAP-15A.

Table 3-36 Connect the Battery Supply Cabling

Step Procedure

1 Run battery "A" and "B" supply cables from central office battery distribution fuse bay across the horizontal cable rack and down the rack rails to the PDAP-15A following local procedures.

2 Remove the protective cover from the back of the PDAP-15A. Refer to Section 3—Installation and Configuration, Chapter 3—“Common Procedures,” Removing and Replacing the PDAP Protective Back Cover, page 3-23 for detailed instructions.

3 Bring the cables to the battery "A" and "B" supply PDAP-15A terminal studs.

Figure 3-41 PDAP-15A Battery Supply Terminal Lugs

4 Cut the battery supply cables to the correct length.

5 Use a crimping tool to attach double-hole copper barrel cable lugs to the ends of the battery supply cables for connection to the PDAP-15A.

6 Remove the nuts and lock washers from the PDAP-15A battery "A" and "B" NEG VDC input terminal lugs.

7 Place the double-hole copper barrel cable lug on the battery "A" NEG VDC input terminal lugs. Replace the lock washers and tighten nuts.

Battery “A” Supply Terminals

Battery “B” Supply Terminals


TraverseEdge 100 User Guide, Section 3: Installation and ConfigurationBattery Return Supply Cabling to the PDAP-15A

Battery Return Supply Cabling to the PDAP-15A

Battery return supply cables (customer-supplied) are run from the central office battery return bus bar (or other central office battery return source) to the PDAP-15A. Follow these steps to connect battery return supply cables to the PDAP-15A.

8 Place the double-hole copper barrel cable lug on the battery "B" NEG VDC input lugs. Replace the lock washers and tighten the nuts.

9 The Connect the Battery Supply Cabling is complete. Continue to the next procedure, Connect the Battery Return Supply Cabling.

Table 3-36 Connect the Battery Supply Cabling (continued)

Step Procedure

Table 3-37 Connect the Battery Return Supply Cabling

Step Procedure

1 Run battery return “A” and “B” supply cables from the battery return supply across the horizontal cable rack and down the rails to the PDAP-15A battery return terminals following local procedures.

Figure 3-42 Battery Return Supply Terminal Lugs at the PDAP-15A

2 Cut the battery return supply cables to the correct length.

3 Use a crimping tool to attach double-hole copper barrel cable lugs to the end of the battery return supply cables for connection to the PDAP-15A.

4 Remove the lock washers, flat washers, and nuts from the PDAP-15A battery return “A” and “B” RTN terminals.

5 Place the double-hole copper barrel cable lug on the battery return “A” RTN terminal lugs. Replace the lock washers, flat washers, and tighten the nuts.

6 Place the double-hole copper barrel cable lug on the battery return “B” RTN terminal lugs. Replace the lock washers, flat washers, and tighten the nuts.

7 Attach two clamp-on ferrites around A feed and two ferrites around B feed (-48 and RTN) cables 6-inches (152.4 mm) from the rack.

Note: The ferrites may have already been pre-secured to the cables.

Battery “A” Return Supply Terminals

Battery “B” Return Supply Terminals


Chapter 7 Power Cabling Procedures—DC/DCConnect Supply Cables to the External Power Source

Connect Supply Cables to the External Power Source

Follow these steps to connect battery and battery return supply cables and lugs (customer-supplied) to the central office source.

8 Important: Use a Volt-Ohm Meter (VOM) to verify continuity of battery and battery return supply cables.

9 Replace the protective cover on the back of the PDAP-15A. Refer to Section 3—Installation and Configuration, Chapter 3—“Common Procedures,” Removing and Replacing the PDAP Protective Back Cover, page 3-23 for detailed instructions.

10 The Connect the Battery Return Supply Cabling is complete. Continue to the next procedure, Connect the Supply Cables to the Central Office Source.

Table 3-37 Connect the Battery Return Supply Cabling (continued)

Step Procedure

WARNING! Use extreme caution when working with battery and battery return supply cables. Remove all metal jewelry when working with power circuits.

WARNING! Complete continuity testing before connecting battery and battery return cables to the central office source.

Table 3-38 Connect the Supply Cables to the Central Office Source

Step Procedure

1 WARNING! Before connecting the supply cables, go to the front of the PDAP-15A and verify that the GMT fuse positions are empty or contain dummy fuses.

Figure 3-43 PDAP-15A Front View

2 Connect battery and battery return supply cables (at the central office battery distribution fuse bay and battery return source) following local procedures or arrange for a local central office technician to make these connections.

3 The Connect the Supply Cables to the Central Office Source procedure is complete. Proceed to the topic Verify Polarity, page 3-56.

Make sure GMT fuses are empty or contain dummy fuses


TraverseEdge 100 User Guide, Section 3: Installation and ConfigurationVerify Polarity

Verify Polarity Confirm polarity between the battery and battery return supply PDAP-15A connections.

Verify Voltage Use a VOM to measure the voltage present at the NEG VDC “A” and “B” input lugs on the PDAP-15A. The voltage reading must be between –48 and –60 VDC.

Turn On Power to the Shelf

Once you have verified voltage, you can plug the 3 amp fuses into the front of the PDAP-15A, one in the A first position and one in the B first position.

Figure 3-44 PDAP-15A Front View

Proceed to Section 3—Installation and Configuration, Chapter 9—“Management Interfaces Cabling,” page 3-63.

WARNING! Go to the front of the PDAP-15A and verify all fuse holders are empty before verifying polarity or voltage.

4 amp GMT fuse 4 amp GMT fuse



Chapter 8 Power Cabling Procedures—AC/DC

Introduction A Force10 external AC/DC power supply (TE-100-AC/DC) is available to provide power capabilities in a TraverseEdge 100 (TE-100) system installation. For power terminal interface specifications, refer to Section 2—Platform Specifications, Chapter 8—“Power Interface Specifications,” page 2-39.

The TE-100 shelf allows you to connect cables from the TE-100-AC/DC power converter or other power supply source to the back or front of the shelf.

This chapter provides step-by step procedures for bringing power to the TE-100 shelf.• Before You Begin, page 3-58• Power Cabling to the Backplane, page 3-58• Power Cabling to the Front Panel (Optional), page 3-60

The instructions may be too detailed if you are an experienced installer. In this case, scan the topic labels in the left margin for tasks to review or refer to Section 7—Appendices, TE-100-AD/DC Power Cabling Checklist, page 7-10.

WARNING! If you require an external DC/DC power source installation for the TE-100, see Chapter 7—“Power Cabling Procedures—DC/DC,” page 3-45.



Before You Begin


Power Cabling to the Backplane

You can connect power to the back or front of the shelf. The following topics first describe the procedures for rear access and then front-panel access.• TE-100-AC/DC Power Cabling, page 3-59• Power Cabling to the Front Panel (Optional), page 3-60

Table 3-39 Power Cabling Procedure Requirements


TE-100 shelf installed Section 3—Installation and Configuration, Chapter 4—“Hardware Installation,” page 3-25

Electrostatic Discharge (ESD) wrist strap Section 3—Installation and Configuration, Chapter 2—“Precautions,” ESD Jack Locations, page 3-8

General Tools and Equipment

Small and medium flat blade screwdrivers

Volt-Ohm Meter

Backplane Power Cabling Tools

2 (optionally) supplied TE-100-AC/DC power DC output cables, each with:• 1 red (- 48 VDC)• 1 black (RETURN)• 1 green chassis ground

Section 2—Platform Specifications, Chapter 8—“Power Interface Specifications,” TE-100-AC/DC Power Converter (optional), page 2-40

Front-Panel Power Cabling Tools

1 supplied cable bundle with white plug at one end and bare wire (or lugs) at the other

1 green vertical plug

TE-100-AC/DC Connection with External Power Supply Tools

2 (optionally) supplied TE-100-AC/DC power supplies (only one unit required to power the shelf; but two for redundancy)

Section 2—Platform Specifications, Chapter 8—“Power Interface Specifications,” TE-100-AC/DC Power Converter (optional), page 2-40

2 (optionally) supplied AC power cords


Chapter 8 Power Cabling Procedures—AC/DCTE-100-AC/DC Power Cabling

TE-100-AC/DC Power Cabling

Follow these steps to connect power from the TE-100-AC/DC power converter to a TE-100 shelf.

Table 3-40 TE-100-AC/DC Power Cabling

Step Procedure

1 Remove the back cover from the first TE-100 shelf in the rack. Refer to Section 3—Installation and Configuration, Chapter 3—“Common Procedures,” Removing and Replacing the Back Cover, page 3-10 for detailed instructions.

2 Connect the AC input connector from the power cord to the AC input inlet on the power supply brick.

Figure 3-45 AC Input Connector and AC Input Inlet

3 Remove the screw labeled -A and +A from the TE-100 power terminal.

Figure 3-46 Remove - A and +A Screw from Power Terminal

4 For redundant power configuration—with a second AC/DC power converter unit—repeat Steps 2–4 for the battery and battery return "B" distribution cable wires.

Note: Force10 recommends you put the two AC/DC power converter units on separate circuit breakers.

5 (SDH network only) Attach one ferrite (1 turn) around each A and B feed cable pair (-48 and RTN) 6-inches (152.4 mm) from the rack.

AC input connector AC input inlet

Remove these screws



Power Cabling to the Front Panel (Optional)

You can connect power to the front panel of the TE-100 shelf.

6 Connect the AC power cord three-prong plug into the AC power outlet.

WARNING! Complete continuity testing before connecting the power cord to the source.

Figure 3-47 AC Three-prong Plug and AC Outlet

7 Confirm polarity between the power and power return supply connections at the TE-100.

8 Use a Volt-Ohm Meter (VOM) to measure the voltage present at the NEG VDC "A" and "B" inputs. Voltage reading must be between –48 and –60 VDC.

9 The TE-100-AC/DC Power Cabling procedure is complete.

Table 3-40 TE-100-AC/DC Power Cabling (continued)

Step Procedure

AC three-prong plug AC outlet

WARNING! To avoid personal injury, ensure that cables are not connected to the power source before beginning this procedure.

Important: Always wear a properly grounded Electrostatic Discharge (ESD) wrist strap when making cable connections to the TE-100 shelf.

Important: Complete cabling before bringing power supply to the shelf.


Chapter 8 Power Cabling Procedures—AC/DCPower Cabling to the Front Panel (Optional)

Follow this procedure if your site requires front-panel access for power cabling. Shown here is the backplane when the first part of this procedure (connecting the supplied cables) is complete:

Figure 3-48 Backplane with Cables for Front Panel Power Access

Table 3-41 Set Up Front Panel Power Cabling Access

Step Procedure

1 Remove the protective cover from the back of the TE-100 shelf. Refer to Section 3—Installation and Configuration, Chapter 3—“Common Procedures,” Removing and Replacing the Back Cover, page 3-10 for detailed instructions.

2 Remove the screws from the external power terminals.

Figure 3-49 Power Terminals on the Backplane

3 Using the supplied cable bundle (with the white plug at one end), place the single-hole copper barrel cable lugs on the power terminals, using the labels on the backplane and the cables as a guide.

4 Replace and tighten the screws.

5 Plug the other end of the cable bundle into the white socket of the front-access cable bundle (already installed). (See Figure 3-48 Backplane with Cables for Front Panel Power Access, page 3-61.)

Backplane Power Connectors

Cable connecting backplane power and front power access plug

Backplane Power Cable

Remove the 5 screws



6 Plug the supplied green vertical plug into the green socket on the left side of the front panel.

Figure 3-50 Front Access Power Supply Plug

7 Connect the DC output cable battery (red wire) to the –48VDC A power terminal (labeled -A) and battery return (black wire) to the RTN A power terminal (labeled A) on the front access power supply plug of the TE-100 shelf. Use a small flat screwdriver to tighten the screw on the front of the plug until the wire is secure.

8 Repeat for -B and +B cables, as necessary.

9 The Set Up Front Panel Power Cabling Access procedure is complete.

Table 3-41 Set Up Front Panel Power Cabling Access (continued)

Step Procedure







Chapter 9 Management Interfaces Cabling

Introduction The TraverseEdge 100 (TE-100) shelf has three management interfaces, two on the interface module and one on the system module. If you have a second system module, you also have a second RS-232 DCE interface; use the interface on the active system module for debugging or connection to a laptop.

For Ethernet DCN and RS-232 specifications, refer first to Section 2—Platform Specifications, Chapter 7—“Management Interfaces Specifications,” page 2-35.

This chapter provides management interface information and step-by-step instructions on how to connect interface cables to the DCN Ethernet (RJ-45) and RS-232 connectors.• Before You Begin, page 3-64• Connect the RS-232 DCE Interface, page 3-64• Connect the DCN Ethernet Interface, page 3-66• Connect the RS-232 DTE Interface, page 3-67

The step-by-step instructions below may be too detailed if you are an experienced installer. In this case, scan the topic labels in the left margin for tasks to review or refer to Section 7—Appendices, Management Interface Cabling Checklist, page 7-12.



Before You Begin


Connect the RS-232 DCE Interface

Follow these steps to complete the external RS-232 DCE interface connection on the system module. This interface is useful for initial configuration and debugging at the site. See Chapter 10—“Node Start-up and Initial Configuration,” page 3-69 for details.

Table 3-42 Management Interface Cabling Procedures Requirements



Tools and Equipment

RJ-45 to DB-9 (female) adapter for RS-232 DCE console management interface

Category 5 Ethernet cable with RJ-45 (M-M) connectors

Console cable for PC connection (A standard, straight-through serial port cable with a 9-pin RS-232-C (DB-9) connector to match the connector on your PC) (user-supplied)

Wire wrap tool or RJ-45 crimp tool, cutter, and plugs to modify DCN or External RS-232 cabling (user-supplied)

4-pair twisted wire (Category 5 Ethernet cable) (user-supplied)

RJ-45 to DB-9 adapter for RS-232 DTE modem connection (user-supplied)

Modem cable for modem connection (user-supplied)

External non-Windows™ modem (user-supplied)

Important: Always wear an Electrostatic Discharge (ESD) wrist strap when making connections to the TE-100 shelf.

Table 3-43 Connect the RS-232 DCE Interface

Step Procedure

1 Connect a user-supplied console cable to the laptop or terminal.

2 Connect the DB-9 end of the supplied RS-232 DCE RJ-45 to DB-9 adapter to the console cable.

Note: For your general reference, see Section 2—Platform Specifications, Data Communication Equipment RS-232 Interface (DCE), page 2-38 for specific pinouts.

3 Connect a Category 5 cable with an RJ-45 connector to the RJ-45 end of the RS-232 DCE RJ-45 to DB-9 adapter.


Chapter 9 Management Interfaces CablingConnect the RS-232 DCE Interface

4 Route the Category 5 cable from the laptop or terminal along the rack rails to the left side of the TE-100 shelf following local procedures.

5 Bring the Category 5 cable over to the RJ-45 connector on the system module.

6 Cut the Category 5 cable to the correct length.

7 Insert the RJ-45 plug into the RJ-45 connector on the system module.

Figure 3-51 RS-232 DCE Interface on Front of TE-100 Shelf

8 The Connect the RS-232 DCE Interface procedure is completed.

Do you need to make a DCN or RS-232 DTE connection?• Yes. Go to the Connect the DCN Ethernet Interface procedure or the

Connect the RS-232 DTE Interface procedure.• No. Go to Chapter 10—“Node Start-up and Initial Configuration,”

page 3-69.

Table 3-43 Connect the RS-232 DCE Interface (continued)

Step Procedure



TraverseEdge 100 User Guide, Section 3: Installation and ConfigurationConnect the DCN Ethernet Interface

Connect the DCN Ethernet Interface

Follow these steps to connect the DCN Ethernet interface on the interface module.


Table 3-44 Connect the DCN Ethernet Interface

Step Procedure

1 Connect the Ethernet cable at the LAN/WAN network device in the central office. See Step 5 for pinouts.

2 Route the Ethernet cable along the rack rails to the left side of the TE-100 shelf following local procedures.

3 Bring the Ethernet cable to the RJ-45 connector on the interface module.

4 Cut the Ethernet cable to the correct length.

5 Strip the cable and terminate on an RJ-45 plug using a crimp tool. RJ-45 pinouts are described below.

Figure 3-52 DCN RJ-45 Plug and Ethernet Pinouts


Chapter 9 Management Interfaces CablingConnect the RS-232 DTE Interface


Connect the RS-232 DTE Interface

Follow these steps to connect the external RS-232 DTE interface on the interface module for modem dial-up access.

6 Insert the RJ-45 plug into the RJ-45 connector on the interface module.

Figure 3-53 TE-100 Interface Module DCN Ethernet Interface

7 The Connect the DCN Ethernet Interface procedure is complete.

Do you need to make an RS-232 DTE connection?• Yes. Go to the Connect the RS-232 DTE Interface procedure.• No. Continue to the Chapter 10—“Node Start-up and Initial

Configuration,” page 3-69.

Table 3-44 Connect the DCN Ethernet Interface (continued)

Step Procedure

DCN Ethernet Interface(RJ-45)


Table 3-45 Connect the RS-232 DTE Interface

Step Procedure

1 Connect the RJ-45 to DB-25 adapter at the external modem.

2 Connect the Category 5 cable to the RJ-45 side of the RJ-45 to DB-25 adapter. See Step 6 on page 3-68 for pinouts.

3 Route the Category 5 cable from the external modem along the rack rails to the left side of the TE-100 shelf following local procedures.

4 Bring the Category 5 cable over to the RJ-45 connector on the interface module.

5 Cut the Category 5 cable to the correct length.

TraverseEdge 100 User Guide, Section 3: Installation and ConfigurationConnect the RS-232 DTE Interface

6 Strip the cable and terminate on a RJ-45 plug using a crimp tool. RS-232 interface pinouts along with DB-9 (and DB-25) pinouts are described below:

Figure 3-54 RS-232 DTE RJ-45 Plug and DB-9 Pinouts

7 Insert the RJ-45 plug into the RJ-45 connector on the interface module.

Figure 3-55 TE-100 RS-232 DTE Interface

8 The Connect the RS-232 DTE Interface procedure is completed.

Continue to Chapter 10—“Node Start-up and Initial Configuration,” page 3-69.

Table 3-45 Connect the RS-232 DTE Interface (continued)

Step Procedure

RS-232 DTE Interface(RJ-45)



Chapter 10 Node Start-up and Initial Configuration

Introduction This chapter provides instructions for start-up and configuration of a TraverseEdge 100 (TE-100) node: • Before You Begin, page 3-69• CLI Commands and Conventions, page 3-70• Node Start-Up and Initial Configuration, page 3-74• Visual Status During and After Start-up, page 3-77

The instructions may be too detailed if you are experienced in central office installations. In this case, scan the topic labels in the left margin for tasks to review or refer to Section 7—Appendices, Node Start-up and Commissioning Checklist, page 7-13.

For further network management information, refer to TransNav Management System Product Overview Guide, Section 2—Management System Planning.

Before You Begin


Table 3-46 Node Start-up Requirements


All hardware is installed. Chapter 4—“Hardware Installation,” page 3-25

Alarm, timing, and power cabling is installed.

Chapter 5—“Alarm Interface Cabling,” page 3-31

Chapter 6—“Timing Interface Cabling,” page 3-39

Chapter 7—“Power Cabling Procedures—DC/DC,” page 3-45

Polarity and voltage testing is complete. Chapter 7—“Power Cabling Procedures—DC/DC,” Verify Polarity, page 3-56

Power is turned on to the TE-100 shelf. Chapter 7—“Power Cabling Procedures—DC/DC,” Turn On Power to the Shelf, page 3-56

A PC or laptop with hyperterminal or other VT-100 terminal emulation software.

n/a


TraverseEdge 100 User Guide, Section 3: Installation and ConfigurationCLI Commands and Conventions

CLI Commands and Conventions

Refer to the TransNav Management System CLI Guide, Section 1—Overview and Quick Reference for a complete explanation of commands and usage. The following conventions are used in these procedure tables and are the same as listed in the CLI User’s Guide.

A standard, straight-through serial port cable with a 9-pin RS-232-C (DB-9) connector to match the connector on your PC.

The supplied RS-232 DCE RJ-45 to DB-9 adapter.

Chapter 9—“Management Interfaces Cabling,” Connect the RS-232 DCE Interface, page 3-64

CLI command reference. TransNav Management System CLI Guide

Required node commissioning parameters.

Network administrator

Required Node Commissioning Parameters, page 3-71

See Traverse Product Overview Guide, Section 2—Management System Planning, Chapter 3—“IP Address Planning,” page 2-13 for details on assigning IP addresses to network nodes.

Conditional node commissioning parameters depending where the node is located in the network.

Network administrator

Conditional Node Commissioning Parameters, page 3-73

See Traverse Product Overview Guide, Section 2—Management System Planning, Chapter 3—“IP Address Planning,” page 2-13 for details on assigning IP addresses to network nodes.

Table 3-46 Node Start-up Requirements (continued)


Table 3-47 CLI Command Descriptions

Command DescriptionBoldface Boldface indicates commands and keywords that are

entered literally as shown.Italics Italics indicate arguments; you supply these values.


Chapter 10 Node Start-up and Initial ConfigurationRequired Node Commissioning Parameters

Required Node Commission-ing Parameters

Required Traverse node commissioning parameters are provided by your local network administrator and are listed in the following table.

Table 3-48 Required Node Commissioning Parameters

Parameter Description

Node ID

(node-id)

The Node ID is the node name used to access CLI node-level commands after commissioning. It is also the node name displayed in the TransNav GUI at the bottom of the Shelf View window.

Important: Enter the name of the node (node-id) using a recommended maximum of 15 characters. Use alphanumeric characters only. Do not use punctuation, spaces, or special characters in this field. Additionally, the node name (node-id) is case-sensitive. Ensure that this node name (node-id) is identical to the Node Name GUI parameter that may have been configured during any node preprovisioning.

Node IP

(node-ip)

The Node IP address is also known as the Router IP in a data network environment.

The Node IP address is provided by your local network administrator and is based on the network topology.

See the TransNav Management System Product Overview Guide, Section 2—Management System Planning, Chapter 3—“IP Address Planning,” page 2-13 for details on assigning IP addresses to network nodes.

Standard

(standard)

Standard is required to set the default technology standard for multi-standard (SONET/SDH) cards found during discovery. The Standard parameter values are:• • ANSI_only. An ANSI node only. A user can only see

the ANSI options. • ANSI_default. For an ANSI node, but an operator

will be able to see SDH options. DS3/E3 mode and timing mode can be switched.

• ITU_default. For an SDH node ,but an operator will be able to see ANSI options. DS3/E3 mode and timing mode can be switched.

Optical bandwidth

(opt-bandwidth)

Specifies the optical bandwidth of the system module. Specify one of the following values: • OC3/STM1 for an OC-3 or STM-1 SFP interface• OC12/STM4 for an OC-12 or STM-4 SFP interface• OC48/STM16 for an OC-48 or an STM-16 SFP

interface


TraverseEdge 100 User Guide, Section 3: Installation and ConfigurationConditional Node Commissioning Parameters

Conditional Node Commis-sioning Param-eters

Depending on where the node is located in the network, you may need to commission the parameters described in the following table.

Table 3-49 Conditional Node Commissioning Parameters

Parameter Description

Backplane DCN IP

(bp-dcn-ip)Required on each node that is connected or routed to the management server or on any node with a subtended device.

The backplane DCN Ethernet interface IP address is provided by your local network administrator and is based on the network topology.

Enter an IP address if this node is connected to the management server (either directly or through a router) or to a TransAccess product.

See the Traverse Product Overview Guide, Section 2—Management System Planning, Chapter 3—“IP Address Planning,” page 2-13 for details on assigning IP addresses to network nodes.

Backplane DCN Mask

(bp-dcn-mask)Required for each bp-dcn-ip. This value depends on site practices.

Enter the appropriate address mask of the bp-dcn-ip address.

Backplane DCN Gateway

(bp-dcn-gw-ip)Required for each bp-dcn-ip. This value depends on site practices.

If the node is connected directly to the management server, this address is the IP gateway of the management server.

If there is a router between the management server and this node, this address is the IP address of the port on the router connected to the Ethernet interface on the back of the Traverse node.

EMS IP

(ems-ip)Required if there is a router between this node and the management server.

This address is the IP address of the TransNav management server. This address is provided by your local network administrator and is based on the network topology.

See the Traverse Product Overview Guide, Section 2—Management System Planning, Chapter 3—“IP Address Planning,” page 2-13 for details on assigning IP addresses to network nodes.

EMS Mask

(ems-mask)Required for each ems-ip. This value depends on site practices.

This address is the address mask of the IP address on the management server (ems-ip).

EMS Gateway

(ems-gw-ip)Required for each ems-ip. This value depends on site practices.

This address is the IP address of the port on the router connected to the Ethernet interface on the back of the Traverse shelf. This address is the same address as bp-dcn-gw-ip.


Chapter 10 Node Start-up and Initial ConfigurationNode Start-Up and Initial Configuration

Node Start-Up and Initial Configuration

Node commissioning involves connecting a serial port cable to the RS-232 DCE interface on the system module and to your PC or laptop and configuring the required node parameters, using the CLI interface.

Later, during provisioning, you can configure other node parameters and manage the node or a network of nodes over the service provider’s data communications network (DCN) via the TransNav management system.

Follow these steps to commission the node.

Important: Always wear a properly grounded ESD wrist strap when handling or working with TE-100 modules.

WARNING! Do not change the node ID or node IP address once these are set during initial configuration. Changing the node ID or node IP address will affect services.

Table 3-50 Node Start Up and Initial Configuration

Step Procedure

1 Turn on the power to the node.

2 Insert the interface module. See Section 3—Installation and Configuration, Chapter 3—“Common Procedures,” Inserting and Removing Modules, page 3-11 for details.

3 Insert one system module and wait for the LEDs to become solid green.

4 Connect a serial port cable to the RS-232 DCE interface on the system module and to your PC or laptop.

Figure 3-56 System Module RS-232 DCE Interface

5 Power-up your PC or laptop and Start Hyperterminal or other VT-100 emulation software.



TraverseEdge 100 User Guide, Section 3: Installation and ConfigurationNode Start-Up and Initial Configuration

6 Enter the correct parameters settings for the communications port (COM1 or COM2):

Baud Rate: 9600Data Bits: 8Parity: NoneStop Bits: 1Flow Control: None

7 Important: You may have to type <Enter> several times to establish the session and receive the Force10 logo and session prompt.

Your terminal responds with the Force10 logo.

Please type CLI to start a new session...

8 To logon to the CLI:

Type: CLI<Enter>

9 The CLI responds:

Login:

Type: admin <Enter>

Password:

Type: admin<Enter>

10 At the command line, type the following command sequence:

exec node commission node-id nodeName node-ip aaa.bbb.ccc.ddd standard technologyStandard opt-bandwidth opticalBandwidth <Enter>

See Required Node Commissioning Parameters, page 3-71 for the descriptions of these parameters.

11 At the command prompt:

Changing node commissioning will result in a reinitialization of the Database. Are you sure? [yes|no]:

Type: y to reinitialize the database on the GCM.

Table 3-50 Node Start Up and Initial Configuration (continued)

Step Procedure


Chapter 10 Node Start-up and Initial ConfigurationNode Start-Up and Initial Configuration

12 Is this node connected to a DCN or a subtended device? • No. Go to Step 14.• Yes. Enter the backplane DCN IP address information.

Type: set node ip bp-dcn-ip aaa.bbb.ccc.ddd bp-dcn-mask aaa.bbb.ccc.ddd bp-dcn-gw-ip aaa.bbb.ccc.ddd<Enter>where:aaa.bbb.ccc.ddd is the correct IP address from your network administrator.

13 Is this node is connected or routed to the management server?• No. Go to Step 14.• Yes. Enter the EMS IP information:

Type: set node ip ems-ip aaa.bbb.ccc.ddd ems-mask aaa.bbb.ccc.ddd ems-gw aaa.bbb.ccc.ddd<Enter>where:aaa.bbb.ccc.ddd is the correct IP address from your network administrator.

14 Restart the node:

Type: exec node restart<Enter>

CLI responds: Are you sure you want to execute this command? [yes|no]:

Type: yes<Enter>

The node begins the restart sequence.

15 Exit the terminal emulation session.

16 Do you have a second system module for 1:1 equipment protection?• No. Go to Step 18.• Yes. Go to the next step.

17 Insert the second system module (optional) and wait for all the LEDs to turn solid green.

18 The Node Start Up and Initial Configuration procedure is complete. Continue to Visual Status During and After Start-up, page 3-77

Table 3-50 Node Start Up and Initial Configuration (continued)

Step Procedure


TraverseEdge 100 User Guide, Section 3: Installation and ConfigurationVisual Status During and After Start-up

Visual Status During and After Start-up

The system module power LED indicates the status of start-up and initialization. The power LED will go through the following sequence:

Flashing red. Power On Self Test (POST) is started.

Solid green. Initialization complete and successful.

Table 3-51 Power and Active/Standby—System Modules

LED

RED Amber GREEN OFF

Flashing Steady On Flashing Steady On Flashing Steady On

Power Initializing; POST is started.

Hardware failure detected; replace the module.

N/A N/A N/A Passed initialization and operational.

No power.

Active/ Standby

N/A N/A Standby mode; synchronization with the active card is not complete.

Module type does not match the provisioned module type; or the module is placed in an invalid slot.

Standby mode; synchronization with the active card is complete.

Active and operational.

Initializing; POST is started.



Chapter 11 Network Interface Cabling

Introduction TraverseEdge 100 (TE-100) network interface cabling support for electrical (copper and coax) and optical fiber modules is as follows:

This section includes the following network interface cabling chapters:• Before You Begin, page 3-80• DS1/E1 Cabling Procedure, page 3-81• DS3/E3 Cabling Procedure, page 3-82• 10/100BaseTX Fast Ethernet Cabling Procedure, page 3-83• Fiber Optic Cabling Procedures, page 3-84• Fiber Optic Transmit and Receive Testing, page 3-85

For a overview of TE-100 system installation, refer to Section 3—Installation and Configuration, Chapter 1—“Installation Overview,” page 3-1.

The instructions in this chapter may be too detailed if you are experienced in central office installations. In this case, scan the topic labels in the left margin for tasks to review or refer to Section 7—Appendices, Network Cabling Checklist, page 7-16.



Before You Begin


Table 3-52 Network Interface Cabling Procedures Requirements



Wire wrap tool or RJ-45 crimp tool, cutter, and plugs to modify DS1/E1 or 10/100BaseTX Fast Ethernet cabling.

n/a

SFP Tools and Equipment

GbE SFPs installed on the interface module. Section 3—Installation and Configuration, Chapter 3—“Common Procedures,” Inserting and Removing SFPs, page 3-15.

Fiber optic cables with LC SMF connectors.

DS1 Tools and Equipment

28 AT&T Technologies, Inc. 22ga. ABAM cables with RJ-45 connectors with RJ-48c pinouts (one unbalanced twisted pair for each direction of transmission)

DS3 Tools and Equipment

6 AT&T 734A or 735A equivalent coax cable with male 75Ω Mini-BNC connectors (one unbalanced coaxial line for each directional of transmission).

Tool(s) to make modifications to the cable:• 75Ω Mini-BNC socket connectors• Diagonal cutters• Coax center crimp tool• Coax cable stripping tool• Coax crimp tool

10/100BaseTX Fast Ethernet Tools and Equipment

n 6 AT&T Technologies, Inc. 22ga. ABAM. One clamp-on ferrite per cablen Cables with RJ-45 connectors


Chapter 11 Network Interface CablingDS1/E1 Cabling Procedure

DS1/E1 Cabling Procedure

This procedure describes how to install the DS1 or E1 cables. For specifications, refer to Section 2—Platform Specifications, Chapter 2—“Electrical Ports Specifications,” page 2-11.

Figure 3-57 DS1/E1 Cable with RJ-45 Connector (RJ-48c Pinouts)

Table 3-53 Connect DS1/E1 Cable

Step Procedure

1 Plug the cable into the port until it clicks into position.

2 Route the cable to the right or left, as appropriate, and over the cable support. See Section 3—Installation and Configuration, Chapter 12—“Cable Management,” Routing Cables, page 3-88.

3 The Connect DS1/E1 Cable procedure is complete.

Pin Description Color Code

1 TX- (Ring) White/Orange

2 TX+ (Tip) Orange

3

4 RX- (Ring) Blue

5 RX+ (Tip) White/Blue

6

7 SHEILD

8 SHEILD


TraverseEdge 100 User Guide, Section 3: Installation and ConfigurationDS3/E3 Cabling Procedure

DS3/E3 Cabling Procedure

This procedure describes how to install the DS3 cables. For DS3 specifications, see Section 2—Platform Specifications, Chapter 2—“Electrical Ports Specifications,” DS3 Ports, page 2-13.

Figure 3-58 DS3/E3 Cables with mini-BNC Connectors

Table 3-54 Connect DS3/E3 Cable

Step Procedure

1 Place a mini-BNC cable connector over the connector on the front of the interface module.

2 Turn the connector as you push it forward until the studs on the connection point slide into the slots on the connector and lock it into place.

3 Route the cable to the right or left, as appropriate, over the cable support. Section 3—Installation and Configuration, Chapter 12—“Cable Management,” page 3-87.

4 The Connect DS3/E3 Cable procedure is complete.

Slots that slides over the studs on the connection point


Chapter 11 Network Interface Cabling10/100BaseTX Fast Ethernet Cabling Procedure

10/100BaseTX Fast Ethernet Cabling Procedure

This procedure describes how to install the 10/100BaseTX cables. For specifications, see Section 2—Platform Specifications, Chapter 3—“Ethernet Ports Specifications,” Fast Ethernet Ports, page 2-19.

Figure 3-59 10/100BaseTX RJ-45 Pinouts

Table 3-55 Connect 10/100BaseTX Fast Ethernet Cable

Step Procedure

1 Plug the cable into the port until it clicks into position.

2 Route the cable to the right or left, as appropriate, and over the cable support. See Section 3—Installation and Configuration, Chapter 12—“Cable Management,” page 3-87.

3 The Connect 10/100BaseTX Fast Ethernet Cable procedure is complete.

Pin Description Color Code

1 RX+ Orange

2 RX- White/Orange

3 TX+ White/Green

4

5

6 TX- Green

7

8


TraverseEdge 100 User Guide, Section 3: Installation and ConfigurationFiber Optic Cabling Procedures

Fiber Optic Cabling Procedures

This procedure describes how to install the fiber cables. For specifications, see Section 2—Platform Specifications, Chapter 3—“Ethernet Ports Specifications,” Gigabit Ethernet Ports, page 2-17. For working with SFPs, see Section 3—Installation and Configuration, Chapter 3—“Common Procedures,” Inserting and Removing SFPs, page 3-15.

WARNING! The TE-100 system is a class 1 product that contains a class IIIb laser and is intended for operation in a closed environment with fiber attached. Do not look into the optical connector of the transmitter with power applied. Laser output is invisible, and eye damage can result. Do not defeat safety features that prevent looking into the optical connector.

WARNING! The optical connector system used on the TE-100 fiber optic backplane is designed with a mechanical shutter mechanism that blocks physical and visual access to the optical connector. Do not defeat this safety feature designed to prevent eye damage.

WARNING! Follow all warning labels when working with optical fibers. Always wear eye protection when working with optical fibers. Never look directly into the end of a terminated or unterminated fiber or connector as it may cause eye damage.

Important: Always wear a properly grounded Electrostatic Discharge (ESD) wrist strap when making cable connections to the fiber optic backplane.

Important: Fiber optic cable is very fragile, be careful when handling and routing the cable. Do not make any bends or coils in the cable less than 1½ inches (3.8 mm) in diameter. Kinks or sharp bends in the cable can cause signal distortion.

Table 3-56 Connect Fiber-Optic Cables

Step Procedure

1 Remove the plug from the SFP module so that you can insert the cables. Save the plug for future use.

2 Remove the plugs from the cables and save them as well.


Chapter 11 Network Interface CablingFiber Optic Transmit and Receive Testing

Fiber Optic Transmit and Receive Testing

Refer to Section 2—Platform Specifications, Chapter 4—“SONET/STM Ports Specifications,” Optical Interface Specifications (Summary), page 2-26 for acceptable minimum/maximum output power and receiver levels.

3 Attach the optical fiber cables directly to the SFP module, one cable for transmit (TX) and the second for receive (RX).

Figure 3-60 Fiber Cables

4 Route the cable to the right or left, as appropriate, and over the cable support.

5 The Connect Fiber-Optic Cables procedure is complete.

Table 3-56 Connect Fiber-Optic Cables (continued)

Step Procedure


TraverseEdge 100 User Guide, Section 3: Installation and ConfigurationFiber Optic Transmit and Receive Testing



Chapter 12 Cable Management

Introduction This chapter includes the following topics:• Before You Begin, page 3-87• Cable Strain-Relief Bar (optional), page 3-88• Routing Cables, page 3-88

Before You Begin


Table 3-57 Cable Routing Requirements


All hardware, including the cable-routing brackets, is installed.

Section 3—Installation and Configuration, Chapter 4—“Hardware Installation,” page 3-25.

All cabling is installed. Section 3—Installation and Configuration, Chapter 5—“Alarm Interface Cabling,” page 3-31.

Section 3—Installation and Configuration, Chapter 6—“Timing Interface Cabling,” page 3-39.

Section 3—Installation and Configuration, Chapter 7—“Power Cabling Procedures—DC/DC,” page 3-45.

Section 3—Installation and Configuration, Chapter 11—“Network Interface Cabling,” page 3-79.

Section 3—Installation and Configuration, Chapter 9—“Management Interfaces Cabling,” page 3-63.

Equipment and Tools

Optional cable strain-relief bar (not supplied)

Phillips screwdriver.

Tie-wraps or other securing devices, according to local practice.


TraverseEdge 100 User Guide, Section 3: Installation and ConfigurationCable Strain-Relief Bar (optional)

Cable Strain-Relief Bar (optional)

Because most of the interface module cables are near the bottom of the shelf, you can use a cable strain-relief bar (not supplied) to secure them and then route the cables below the shelf. This arrangement requires leaving sufficient space under the shelf to accommodate the bar and cables.

Figure 3-61 Rear View of TE-100Shelf with Cable Strain-Relief Bar

Routing Cables Follow these steps to route the TE-100 cables away from the front of the shelf.

Table 3-58 Route Cables

Step Procedure

1 Install a tie-bar or other strain-relief device, according to local site practice. Figure 3-61 Rear View of TE-100Shelf with Cable Strain-Relief Bar shows how a bar might be installed.

2 Secure the cables to the strain-relief device using tie-wraps or other site-specific methods.

3 Label all cables at each end of the connection to avoid confusion with cables that are similar in appearance.

4 The Route Cables procedure is complete. Continue to Section 4—Configuring the Network, Chapter 1—“Configuring the Network,” page 4-1.


SECTION 4 PROVISIONING THE NETWORK

MODULE DESCRIPTIONS

Contents

Chapter 1Configuring the Network

Configuration Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1TransNav System Access Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2Provisioning Checklists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3Before You Start Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3Protection Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3Discover TE-100 Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4Navigation in Shelf View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5Configure Node Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6

Chapter 2Configuring Network Timing

Before You Configure Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9Network Timing Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10Guidelines to Configuring Network Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10Configure Global Timing Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11Configure External Timing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12Configure Line Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14Configure Derived References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15

Chapter 3Creating a UPSR/SNCP Protection Group

Example of a UPSR or SNCP Ring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-18Before You Create a UPSR or SNCP Protection Group . . . . . . . . . . . . . . . . . 4-19Guidelines to Create a UPSR or SNCP Protection Group . . . . . . . . . . . . . . . 4-20Create a UPSR or SNCP Ring Protection Group . . . . . . . . . . . . . . . . . . . . . . 4-20

Chapter 4Creating 1+1APS/MSP Protection Groups

APS/MSP Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-23Example of a 1+1 APS/MSP Protection Group . . . . . . . . . . . . . . . . . . . . . . . . 4-24Before You Create a 1+1 APS/MSP Protection Group . . . . . . . . . . . . . . . . . . 4-24Create a 1+1 APS/MSP Protection Group . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-25

Chapter 5Creating a 1+1 Optimized Protection Group

Before You Create a 1+1 Optimized Protection Group . . . . . . . . . . . . . . . . . . 4-28Create a 1+1 Optimized Protection Group . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-28


TraverseEdge 100 User Guide, Section 4 Provisioning the Network


SECTION 4CONFIGURING THE NETWORK

Chapter 1 Configuring the Network

Introduction This chapter describes the following topics on how to provision a TraverseEdge 100 (TE-100) network. • Configuration Process, page 4-1• TransNav System Access Methods, page 4-2• Provisioning Checklists, page 4-3• Before You Start Provisioning, page 4-3• Discover TE-100 Nodes, page 4-4• Navigation in Shelf View, page 4-5• Configure Node Parameters, page 4-6

Configuration Process

Use these steps as a guideline to creating a network.

Table 4-1 TE-100 Network Configuration Process and References


1 TransNav management server is constructed and the management software is installed. The server is initialized and started.


2 Nodes are installed, connected, and commissioned.

Section 3—Installation and Configuration

3 Discover the network and configure optional parameters on each node.

Discover TE-100 Nodes, page 4-4

4 Configure timing options for the network.

Chapter 2—“Configuring Network Timing,” page 4-9

5 Create protection groups. • Chapter 3—“Creating a UPSR/SNCP Protection Group,” page 4-17

• Chapter 4—“Creating 1+1APS/MSP Protection Groups,” page 4-23

• Chapter 5—“Creating a 1+1 Optimized Protection Group,” page 4-28


TraverseEdge 100 User Guide, Section 4: Configuring the NetworkTransNav System Access Methods

TransNav System Access Methods

This document uses the graphical user interface (GUI) to describe all procedures.The following table lists the different access methods you can use to connect to a TransNav management server or a specific Traverse node.

6 If necessary, modify the default parameters for the equipment.

• Section 5—Creating TDM Services, Chapter 4—“Configuring SONET Equipment,” page 5-17

• Section 5—Creating TDM Services, Chapter 6—“Configuring SDH Equipment,” page 5-43

• Section 6—Creating Ethernet Services, Chapter 2—“Configuring Ethernet Equipment,” page 6-5

7 For TDM applications, create TDM services.

Section 5—Creating TDM Services

8 For Ethernet applications, create Ethernet services

Section 6—Creating Ethernet Services

Table 4-1 TE-100 Network Configuration Process and References (continued)


Table 4-2 Accessing the TransNav Management System

Management System Interface Access Method

TransNav GUI • Installed client application (recommended)• Local connection to node and remote connection

(DCC bytes) to a management server• Installed application on a Citrix server

TransNav CLI • Telnet to a management server• Local connection to node and remote connection

(DCC bytes) to a management server

TransNav TL1 • Local connection to the management system and telnet to a node

Node-level GUI • Installed client application (required to view GUI)• Local connection to specific node

Node CLI • Local connection to the node• Local connection to the node and remote login to a

different node in the domain

Node TL1 • Telnet to the management system and connect to a node

• Local connection to the node


Chapter 1 Configuring the NetworkProtection Groups

Provisioning Checklists

See Section 7—Appendices, Appendix A—“Installation and Commissioning Checklists,” page 7-1 for a quick reference on provisioning procedures.

Before You Start Provisioning

Before you start provisioning your network, the following tasks need to be complete.

Wherever possible, a table listing requirements and guidelines precedes each procedure. See each topic for requirements specific to the task.

Protection Groups

Depending on the network requirements, a TE-100 network supports a selection of methods to protect traffic:• Equipment protection groups (optional but not configurable)

With two system modules, the TE-100 shelf supports 1:1 equipment protection for functions performed on the system card and the traffic from the interface ports on the interface module. See Section 3—Installation and Configuration, Chapter 3—“Common Procedures,” Install a Second System Module, page 3-18.

• Path protection group (optional and configurable)Path protection switching is a traffic protection mechanism based on SONET path level indications. Path protection the logical end-to-end path of traffic through a network. See Chapter 3—“Creating a UPSR/SNCP Protection Group,” page 4-17.

• Line protection groups (optional and configurable)Line protection switching is a protection mechanism coordinated by the nodes on either side of the failure condition using the automatic protection switching (APS) or multiplex section protection (MSP) signaling protocol. See the following chapters for more information on line protection groups:– Chapter 4—“Creating 1+1APS/MSP Protection Groups”– Chapter 5—“Creating a 1+1 Optimized Protection Group,” page 4-27

Table 4-3 Before Provisioning Your Network Requirements


Hardware

You have the correct hardware according to your network plan.

Section 2—Platform Specifications, Chapter 9—“Network Topologies,” page 2-43

The hardware is installed and commissioned according to your network plan.

Section 3—Installation and Configuration, Chapter 1—“Installation Overview,” page 3-1

Software

TransNav server is constructed and the management software is installed. The server is initialized and started.


Nodes are installed, commissioned, and connected.

Section 3—Installation and Configuration, Chapter 10—“Node Start-up and Initial Configuration,” page 3-69

You are logged into the graphical user interface. TransNav Management System GUI Guide, Chapter 3—“Starting the Graphical User Interface,” page 2-17


TraverseEdge 100 User Guide, Section 4: Configuring the NetworkDiscover TE-100 Nodes

Discover TE-100 Nodes

Use this procedure to make the nodes in the network appear on the main GUI screen.

Table 4-4 Discover the Network

Step Procedure

1 From the Admin menu, select Discovery to display the Discovery Sources View dialog box.

Figure 4-1 Discovery Sources View Dialog Box

2 For each gateway node, enter the node-ip address of the node in the Host Name box.

Click Add.

3 Click Done to return to the main screen. The nodes appear in the upper left corner of the window.

4 Click and drag nodes to an area on the map to best represent your network.

5 From the File menu, select Save User Preferences to save the placement of the nodes.

6 The Discover the Network procedure is complete.

Continue to the next procedure Discover the Network, page 4-4.

2

3 4


Chapter 1 Configuring the NetworkNavigation in Shelf View

Navigation in Shelf View

After network discovery, nodes are visible in Map View. When you double-click a node, you see Shelf View which includes a network alarm summary and navigation tree on the left, a graphical version of the shelf at the top, and a context-sensitive tabbed screen at the bottom.

Network Alarm Summary

Network Navigation Tree

Context-sensitive Tabbed Screen

Optical Ports 1 and 2 (click for port configuration)

SFP Ports (click for SFP information)

External Synchronization

References A and B

Interface Module Ports (6 FE, 2 GbE,

3 DS3, 28 DS1)


TraverseEdge 100 User Guide, Section 4: Configuring the NetworkConfigure Node Parameters

Configure Node Parameters

After a node is commissioned, configure the following type of information at each node: node location description, alarm profiles, and NTP server IP addresses. Alarm profiles are established to customize service-affecting and non-service-affecting alarm severities for the node.

Use this procedure to configure parameters for each node.

Table 4-5 Configure Node Parameters

Step Procedure

1 Double-click a node to display the Shelf View.

2 Click the Config tab to display the Node Configuration screen.

Figure 4-2 Node Configuration Screen

3 In the Location field, type a descriptive location for the node. For example: Node1 Central Office.

Use alphanumeric characters and spaces only. Do not use punctuation or any other special characters in the Location field.

4 Alarm Profile: Select an Alarm Profile from the list if additional profiles have been created. The default is default.

Alarm Profiles can be viewed or created from the Admin menu using the Alarm Profiles dialog box.


Chapter 1 Configuring the NetworkConfigure Node Parameters

5 Values are displayed in the following fields. Some of these values may have been set during node commissioning using the CLI:• Node ID• Node IP• BP DCN IP• BP DCN Mask• BP DCN Gateway• EMS IP• EMSMask• EMS Gateway

For more information, refer to:• Section 3—Installation and Configuration, Chapter 10—“Node

Start-up and Initial Configuration,” page 3-69.

6 You can enter values for the NTP IP 1 and NTP IP 2 fields if they were not set during the initial start-up procedures. The Network Time Protocol (NTP) server IP address is used by the node to derive the Time of Day that is used for performance monitoring, alarm, and event logging.

NTP IP 1Type: the IP address of the primary NTP server. (For example: aaa.bbb.ccc.ddd)

NTP IP 2Type: the IP address of the secondary NTP server. (For example: aaa.bbb.ccc.ddd)

Force10 recommends using the primary TransNav server as the primary NTP source if you do not already have a NTP source defined. Refer to the TransNav Management System Server Guide, Section 2—Management Server Procedures, Chapter 1—“Creating the Management Servers” for information on how to activate the NTP server on the management server.

7 External Alarm 1–4: These fields display a default value of UNKWN. You can select one of the External Alarm input alarm types (based on the environmental alarms input cabling completed during node installation).

8 Proxy ARP: Enable this parameter if this node is to be used as the proxy server for the IP subnet.

See the TransNav Management System Product Overview Guide, Section 2—Management System Planning, Chapter 3—“IP Address Planning,” Proxy ARP, page 2-18 for a complete description of Proxy ARP.

9 Click Apply.

10 Repeat Steps 1 through 9 for each node.

11 The Configure Node Parameters procedure is complete.

Table 4-5 Configure Node Parameters (continued)

Step Procedure


TraverseEdge 100 User Guide, Section 4: Configuring the NetworkConfigure Node Parameters



Chapter 2 Configuring Network Timing

Introduction Configure the timing source for each node in a server domain. For each node, you can configure either external timing or line timing from OC, EC3, or STM interfaces.

Typically, one node in the central office receives redundant timing signals from an external source. This node becomes the primary timing source for the network. The other nodes receive the timing reference from optical interfaces. The primary reference is the shortest route to the primary timing source.

Synchronized primary and secondary timing inputs from the external timing source are connected at the main backplane and bridged to the shelf’s system control cards.• Before You Configure Timing, page 4-9• Network Timing Example, page 4-10• Guidelines to Configuring Network Timing, page 4-10• Configure Global Timing Options, page 4-11• Configure External Timing, page 4-12• Configure Line Timing, page 4-14• Configure Derived References, page 4-15

Before You Configure Timing

Review this information before you configure network timing.

Table 4-6 Timing Requirements


Read the information in Section 4—Configuring the Network, Chapter 1—“Configuring the Network,” page 4-1.

Ensure that the requirements in Before You Start Provisioning, page 4-3 are met.

Software

Network is discovered. Discover TE-100 Nodes, page 4-4


TraverseEdge 100 User Guide, Section 4: Configuring the NetworkNetwork Timing Example

Network Timing Example

In this example, the network is already connected and configured as a ring. On the TE-100 nodes, the West Ports are port 1 and the East ports are port 2. (In the user interface, the timing reference slot is slot-0.)

Node 1 receives a timing signal from the external clock. The primary line reference at Node B is port-2 (the interface physically connected to Node 1). The primary line reference at Node C is port-1 (the interface physically connected to Node 1). Node A can time off of either port-1 or port-2 because it is equal distance from Node 1.

Figure 4-3 Network Timing

At any node, if all timing references fail, the node will maintain timing from the internal Stratum 3 oscillator.

Guidelines to Configuring Network Timing

Use the following guidelines to configure timing in a Traverse network.• If an external clock is present, always configure external timing for the node. • Configure line timing in such a way that the primary reference is the shortest route

to the primary timing source.• For derived timing, the Traverse can generate a timing signal to a DS1or E1

multi-frame, a T1 ESF, a 2 MHz external reference, or a 64 KHz composite clock.

For information on pinouts for each timing interface, instructions on connecting timing inputs from the central office external timing source, and instruction on connecting timing outputs from a node to the external clock, see the Section 3—Installation and Configuration, Chapter 6—“Timing Interface Cabling,” page 3-39.

This section contains information on configurable timing parameters. For an explanation of all timing parameters, states, and messaging, see the TransNav Management System GUI Guide, Section 3—Network, Chapter 3—“Node Timing,” page 3-21.

Node 1

Timing Mode: ExternalPriority 1 Ref: EXT-APriority 2 Ref: EXT-B

Timing Mode: LineReference 1: slot-0/port-2Reference 2: slot-0/port-1

Timing Mode: LineReference 1: port-1 or port-2Reference 2: port-1 or port-2

Node B

Node C

Node A

Timing Mode: LineReference 1: slot-0/port-1Reference 2: slot-0/port-2


Chapter 2 Configuring Network TimingConfigure Global Timing Options


Configure Global Timing Options

Configure the timing options at each node in the domain. Use this procedure to configure the global settings for system timing.

Table 4-7 Configure Global Timing Options

Step Procedure

1 In Shelf View, click the Timing tab to display the Main timing screen (Main subtab).

Figure 4-4 Shelf View, Timing Tab, Main Subtab

2 From the Standard list, select the timing standard to be used for the shelf:• Select ANSI for North American operation.• Select ITU (default) for operations outside of North America.

3 From Timing Mode list:• Select External to receive timing from an external reference.• Select Line to derive timing from an OC or STM interface.

4 Select the Revertive checkbox to revert back to a primary reference source after the conditions that caused a protection switch to a secondary timing reference are corrected.

5 In the WTR Time field, set a time in minutes that the system will wait before considering the primary timing source as valid again. Enter a value between 1 and 12.

Enter 0 to disable this function.

6 By default, the Ignore SSMR (synchronization status message received) parameter is selected. That is, the node will use provisioned priorities to select the best timing reference.

Clear the checkbox to use the SSM level to prioritize timing references.

7 Click Apply to save the timing configuration settings.

8 The Configure Global Timing Options procedure is complete.

If the Timing Mode is External, continue to Configure External Timing, page 4-12.

If the Timing Mode is Line, continue to Configure Line Timing, page 4-14.

2

43

5

TraverseEdge 100 User Guide, Section 4: Configuring the NetworkConfigure External Timing

Configure External Timing

There are two external references for each node: EXT-A and EXT-B. For redundancy, they both have the same configuration. If both references fail, the node maintains timing from the internal Stratum 3 oscillator. Use this procedure to configure external timing interfaces for a node.

Table 4-8 Configure External Timing

Step Procedure

1 Complete the procedure Configure Global Timing Options, page 4-11.

2 In Shelf View, click the Timing tab, then click the EXT subtab.

Figure 4-5 Shelf View, Timing tab, EXT Subtab

3 From the Mode list: • Select DS1 if the external clock is a dedicated DS1 port. Go to Step 4.

• Select 2 MHz Clock. Go to Step 5.• Select 64 KHz Composite Clock. Go to Step 5.

4 Set the interface parameters for the DS1 timing references:• Line Coding: Defines the DS1 transmission coding type. Select one

of the following:– HDB3: High Density Bipolar Order 3 (default)– AMI: Alternate Mark Inversion

• Framing: Detects and generates the frame format to be used. Select one of the following:– Basic Frame: The timing interface detects and generates the Basic

frame format per ITU-T Rec G.704/2.3 and G.706/4.1.2. This format does not support the SSM.

– Multi-Frame: The timing interface detects and generates CRC-4 Multi-frame format per ITU-T Rec G.706/4.2. This format supports the SSM.

• LineBuildOut: (read only) 120 Ohm• SSM Sa Bit: Choose the SA bit that transmits the SSM message.

Select one of the following: – Bit_SA4 – Bit_SA5 – Bit_SA6 – Bit_SA7 – Bit_SA8

2a

2b3


Chapter 2 Configuring Network TimingConfigure External Timing


5 If the external clock does not support SSM and you want to operate using a received SSM, select the SSM quality for the EXT-A Assigned SSMR, and EXT-B Assigned SSMR parameters.• PRC: Primary reference clock• SSUA: Synchronization supply unit type A. Transit• SSUB: Synchronization supply unit type B. Local• SEC: SDH equipment clock• DUS: Do not use for synchronization. • Signal Fail Present• None

6 For each reference, unlock the administrative state to enable the external timing. Click the Lock icon in the Adm State column next to each reference to unlock the administrative state.

Figure 4-6 Timing Tab, EXT Subtab

7 Click Apply to save the external interface settings.

8 Click the Main subtab to return to the Main timing screen.

Figure 4-7 Timing Tab, Main Subtab, Reference Priority

9 Select Priority 1 and Priority 2 external timing references.

A checkmark indicates the active reference.

10 Click Apply to save the reference list settings.

11 The Configure External Timing procedure is complete.

Table 4-8 Configure External Timing (continued)

Step Procedure

76

Indicates active reference9

8

10

TraverseEdge 100 User Guide, Section 4: Configuring the NetworkConfigure Line Timing

Configure Line Timing

You can establish up to four line timing sources based on your network requirements and the number of OC, EC3, and STM interfaces in the node. You first select the references (up to four per node), then you assign a priority to each one.

The node uses the priority 1 reference unless there is a failure on that reference. If there is a failure, the node switches to the next priority. If all of the references fail, the node maintains timing from the internal stratum 3 oscillator.

You can configure line timing sources and perform switch commands on the Timing tab.

Use this procedure to configure line timing from an OC, EC-3, or STM interface for a node.

Table 4-9 Configure Line Timing

Step Procedure

1 Complete the procedure Configure Global Timing Options, page 4-11.

2 In the Configure Global Timing Options procedure, you selected Line Time in Timing Mode. The Line Facility and Reference List options display on the Timing screen.

Figure 4-8 Line Timing, Timing Tab, Main Subtab

3 For each line reference, select a port for the timing reference. The port needs to be enabled (in an unlocked administrative state).

4 Select a priority for each reference. If there is a failure on the first reference, the node switches to the next reference.

A checkmark indicates the active reference.

5 Click Apply to save the settings.

6 The Configure Line Timing procedure is complete.

Indicates active reference

4

3


Chapter 2 Configuring Network TimingConfigure Derived References

Configure Derived References

Derived timing is the process of providing a timing reference from a line interface and sending it to an external clock. Use this procedure to configure a derived timing reference on a node.

The Traverse can generate a timing signal to an DS1 or E1 multi-frame, a T1 ESF, a2 MHz external reference or a 64 KHz composite clock.

Table 4-10 Configure Derived References

Step Procedure

1 In Shelf View, click the Timing tab to display the Main timing screen (Main subtab).

Figure 4-9 Shelf View, Timing Tab, Derived Timing Options

2 Select the External Out Enabled checkbox. Line Facility and Reference List options appear on the screen.

3 For each line reference, select an OC, EC-3, or STM port for the timing reference. The port needs to be enabled (unlocked administrative state).

2

3

56 7

8


TraverseEdge 100 User Guide, Section 4: Configuring the NetworkConfigure Derived References

4 If the value in the Standard parameter is ANSI, select the SSM (synchronization status message) quality for Quality of RES. Select the level of RES by assigning a particular clock standard from the list available. The system will automatically prioritize RES to the clock standard selected from the following SSM values:• Don’t use for sync (default): Do not use for synchronization. • PRS: Primary Reference Source• Synch-Trace Unknown: The BITS clock connected to the Traverse

network may not have SSM enabled or Ignore SSMR has been selected on the Traverse.

• Stratum 2 • Transit Node: Indicates the lock providing timing to the node is of a

Transit Clock Node level (primarily used outside North America). • Stratum 3E • Stratum 3 • SONET Minimum Clock • Stratum 4e

5 Select a priority for each reference. If there is a failure on the first reference, the node switches to the next reference.

6 Select a reference in order of priority to generate a signal to EXT-A.

7 Select a reference in order of priority to generate a signal to EXT-B.

8 Click Apply to save the derived timing preferences.

9 The Configure Derived References procedure is complete.

Table 4-10 Configure Derived References (continued)

Step Procedure



Chapter 3 Creating a UPSR/SNCP Protection Group

Introduction The TraverseEdge 100 (TE-100) supports both uni-directional path switched ring (UPSR) and subnetwork connection protection (SNCP) protection configurations on a unidirectional ring topology. UPSR/SNCP ring protection provides a self-healing closed loop topology that protects against fiber cuts and node failures by providing duplicate, geographically diverse paths for traffic.

This chapter contains information on creating a UPSR or SNCP ring protection group.• Example of a UPSR or SNCP Ring, page 4-18• Before You Create a UPSR or SNCP Protection Group, page 4-19• Guidelines to Create a UPSR or SNCP Protection Group, page 4-20• Create a UPSR or SNCP Ring Protection Group, page 4-20


TraverseEdge 100 User Guide, Section 4: Configuring the NetworkExample of a UPSR or SNCP Ring

Example of a UPSR or SNCP Ring

A UPSR or an SNCP ring requires two fibers to carry traffic in opposite directions around the fiber ring. Protection switching is performed at the path level. To provide survivability, traffic from the tributary side is bridged into both the working and protecting channels at the source node. Path selection at the destination chooses the best quality signal (working or protecting) before dropping it from the ring.

In a ring, there are source nodes (Node A), destination nodes (Node 1), and intermediate nodes (Node B and Node C). Traffic enters the ring at the source node, travels through the intermediate nodes, and exits the ring at the destination node.

Figure 4-10 Bridging and Selecting Signals in a UPSR or SNCP Ring

In a UPSR or an SNCP ring configuration using TE-100 nodes, the East port is always Port 2 and transmits the working signal clockwise around the ring. The West port is always Port 1 and receives the working signal. Also, the East port on one node is physically connected to the West port on the next.

In normal operation, the source node makes a duplicate of the original traffic and bridges it around the ring in opposite directions. The destination node determines the best quality signal based on path layer indications including path layer defects and maintenance signals.

In a failure scenario, the destination node determines the best quality signal and selects traffic from that path. Path protection is single-ended without any type of coordination with, or notification to, the source node. During a fiber failure and before full service is restored, there is no protection on the ring.

Node 1

Node B

Path Selection

Node C

Node A

Bridging


Chapter 3 Creating a UPSR/SNCP Protection GroupBefore You Create a UPSR or SNCP Protection Group

Before You Create a UPSR or SNCP Protection Group

Review this information before you create a UPSR or SNCP ring protection group.

Table 4-11 UPSR/SNCP Ring Protection Group Requirements



Ensure that the requirements in Before Provisioning Your Network Requirements, page 4-3 are met.

Hardware

Use the optical interfaces on the system modules in a ring protection group.

The nodes are physically connected. The East module on one node is physically connected to the West port on the next.

Section 3—Installation and Configuration.

Software

Network is discovered. Section 4—Configuring the Network, Chapter 1—“Configuring the Network,” Discover TE-100 Nodes, page 4-4.

Timing is configured. Section 4—Configuring the Network, Chapter 2—“Configuring Network Timing,” page 4-9.

There are no path-level alarms (LOS, LOF, AIS-P, SF-BER-P) present on the interfaces you are using to configure the ring.

Click the port, click the Alarms tab, and verify no alarms are present.

These procedures describe the steps to create protection groups only. See TransNav Management System GUI Guide for descriptions of other fields on screen.

TransNav Management System GUI Guide, Section 4—Protection Switching, Chapter 2—“UPSR and SNCP Ring Protection Groups,” page 4-11.


TraverseEdge 100 User Guide, Section 4: Configuring the NetworkGuidelines to Create a UPSR or SNCP Protection Group

Guidelines to Create a UPSR or SNCP Protection Group

A single TE-100 node supports two (2) SONET or STM optical interfaces and one (1) UPSR protection group or SNCP ring protection group.

A single TE-100 node is physically connected to two (2) other nodes. If the node is part of a protection ring, no other type of protection group can be added.

In a ring configuration, the East port is always Port 2 and transmits the working signal clockwise around the ring. The West port is always Port 1 and receives the working signal.

The East port on one node is physically connected to the West port on the next.

Important: For an SDH STM-16 node in an SNCP ring or linear TU-3/VC-3 configuration, at most 12 LO VC-3s are available:

– VC-4 channels 1–4 are unusable for any service, including pass-thru cross-connections, which is typical in TU-3 mode. LO VC-3 provisioning is available for VC-4 endpoints 5–8. VC-4 channels 9–16 can provide further provisioning for anything but LO-VC-3.

– SNCP rings greater than 4 nodes is impractical with LO VC-3 only (although you can provision other services on 5th and greater nodes)

Create a UPSR or SNCP Ring Protection Group

Use this procedure to create a UPSR or SNCP ring protection group.

Table 4-12 Create a UPSR or SNCP Ring Protection Group

Step Procedure

1 Review the information in Before You Create a UPSR or SNCP Protection Group, page 4-19 before you start this procedure.

2 In Map View, click the Protection tab to display the Protection Rings screen.

3 Add a UPSR or an SNCP Ring protection group. From the New list, select SNCP/UPSR.

Figure 4-11 Select SNCP/UPSR

Step 4


Chapter 3 Creating a UPSR/SNCP Protection GroupCreate a UPSR or SNCP Ring Protection Group

4 Click Add to display the Protection Group Creation tab, Add SNCP/UPSR Ring screen.

Figure 4-12 Add SNCP/UPSR Ring Screen

5 In the Name field, enter the name of the node (maximum of 43 characters). Use alphanumeric characters only. Do not use punctuation or any other special character in this field.

6 Add nodes to the ring. In Map View, click a node to add it to the ring. The nodes display on the screen as you select them from Map View.

Figure 4-13 West and East Ports for SNCP/UPSR Ring

7 For each node in the ring (Node column), select a West port from the menu in the West Port column.

The West port of a node is physically connected to the East port of another node.

8 For each node in the ring (Node column), select an East port from the menu in the East Port column.

The East and West ports must be on separate cards in the shelf.

Click Add.

Table 4-12 Create a UPSR or SNCP Ring Protection Group (continued)

Step Procedure

5

6 7 8


TraverseEdge 100 User Guide, Section 4: Configuring the NetworkCreate a UPSR or SNCP Ring Protection Group

9 In Synchronize Protection Group dialog box, click Yes to propagate protection group information to all nodes in the ring.

Important: If you have multiple servers, you must be on the Primary server to synchronize the nodes.

Figure 4-14 Synchronize Confirmation

10 The protection group is listed in the Protection Rings screen and is assigned a 4-digit Ring ID.

Figure 4-15 Protection Rings Screen

11 The Create a UPSR or SNCP Ring Protection Group procedure is complete.

Table 4-12 Create a UPSR or SNCP Ring Protection Group (continued)

Step Procedure



Chapter 4 Creating 1+1APS/MSP Protection Groups

Introduction Line protection switching is a protection mechanism coordinated by the nodes on either side of the failure condition using the automatic protection switching (APS) or multiplex section protection switching (MSP) signaling protocol. Use 1+1 APS/MSP protection groups on simple point-to-point and linear chain topologies.

This chapter describes creating a 1+1 APS protection group on a TraverseEdge 100 (TE-100) node.• Example of a 1+1 APS/MSP Protection Group, page 4-24• Before You Create a 1+1 APS/MSP Protection Group, page 4-24• Create a 1+1 APS/MSP Protection Group, page 4-25

APS/MSP Protocol

The APS protocol is carried in the K1 and K2 bits in the SONET signal between nodes. The APS controllers at the line termination use the channel to exchange requests and acknowledgement for protection switching actions.

The MSP protocol is carried in the K1 and K2 bits in the SDH signal between nodes. The MSP controllers at the multiplex section termination use the channel to exchange requests and acknowledgement for protection switching actions.


TraverseEdge 100 User Guide, Section 4: Configuring the NetworkExample of a 1+1 APS/MSP Protection Group

Example of a 1+1 APS/MSP Protection Group

1+1 APS/MSP uses both the working and the protect fibers to send traffic simultaneously to the next node. That is, the system duplicates the traffic and sends it over both the working and the protect fibers at the same time.

With this protection mechanism, when the system detects a failure, the next node switches to accept traffic from the standby path. The link remains unprotected until service is restored on the working link.

In the following example, a linear chain topology provides direct access to individual eastbound or westbound STS or AU channels at intermediate sites along a fiber route, without unnecessary multiplexing and de-multiplexing of pass-through traffic.

The TE-100 platform supports simple point-to-point and linear chain topologies.

Figure 4-16 1+1 APS/MSP in a Point-to-Point Topology

Configure 1+1 APS/MSP protection at for each facility connected to the next node. In this example, configure one 1+1 APS/MSP protection group at Node A and Node 1.

Before You Create a 1+1 APS/MSP Protection Group

Review this information before you create a 1+1APS/MSP protection group. The TE-100 system supports 1+1 unidirectional and bi-directional protection switching.

Node 1

Node A

Table 4-13 1+1 APS/MSP Protection Groups Requirements




Software

Network is discovered. Section 4—Configuring the Network, Chapter 1—“Configuring the Network,” Discover TE-100 Nodes, page 4-4.


No line-level alarms (LOS, LOF, AIS-L, SF-BER-L) are present on the interfaces you are using to configure the protection group.



TransNav Management System GUI Guide, Section 4—Protection Switching, Chapter 4—“1+1 MSP/APS Protection Groups,” page 4-23.


Chapter 4 Creating 1+1APS/MSP Protection GroupsCreate a 1+1 APS/MSP Protection Group

Create a 1+1 APS/MSP Protection Group

Use this procedure to create a 1+1 APS/MSP protection group.

Table 4-14 Create a 1+1 APS/MSP Protection Group

Step Procedure

1 Review the information in Before You Create a 1+1 APS/MSP Protection Group, page 3-36 before you start this procedure.

2 In Shelf View, click the Protection tab to display the Protection Groups screen.

3 Add a 1+1 APS protection group. From the New list, select 1+1 MPS/APS.

Figure 4-17 Select 1+1 MPS/APS

4 Click Add to display the Protection Group Creation tab, Add 1+1 Protection Group screen.

Figure 4-18 Add 1+1 Protection Group Screen

5 In the Name field, enter the name of the node (maximum of 43 characters). Use alphanumeric characters only. Do not use punctuation or any other special characters in this field.

6 Set the reversion options:• Select the Revertive checkbox to switch traffic back to the working

card when the working port has recovered from the original failure condition or the external command is cleared.

• In the WTR Time field, set a time in minutes that the system will wait after a protection switch occurs before switching back to the working port.Enter a number between 1 and 60; default is 5.

34

567

8

10


TraverseEdge 100 User Guide, Section 4: Configuring the NetworkCreate a 1+1 APS/MSP Protection Group

7 In the Switch Mode parameter, set the behavior of the protection switch on the link. • Select Uni-directional to switch traffic from a failed receive direction

to the standby link.• Select Bi-directional to switch both the transmit and receive directions

to the standby link.

8 Select the Protecting Port for this protection group. On the Protecting row, click the Port field and select the protecting port.

Figure 4-19 Select Protecting and Working Ports

9 Repeat Step 8 to select the working port. On the Working row, click the Port field and select the working port.

10 Click Add to return to the Protection Groups screen on the Protection tab.

Figure 4-20 Protection Groups Screen

The system assigns an ID to the new protection group.

11 Repeat Steps 1 through 10 at the other end of the fiber link.

12 The Create a 1+1 APS/MSP Protection Group procedure is complete.

Table 4-14 Create a 1+1 APS/MSP Protection Group (continued)

Step Procedure



Chapter 5 Creating a 1+1 Optimized Protection Group

Introduction 1+1 optimized protection bridges traffic simultaneously over two lines: section 1 and section 2. There is a primary section and a secondary section.

In normal operation, the system selects traffic from the primary section (active traffic). All switch requests (automatic or forced) are from the primary section to the secondary section. Once a switch request clears, the traffic selector stays on the section to which it was switched. That section then becomes the primary section if there are no further switch requests.

If a failure occurs on the secondary section, the traffic selector remains on traffic from the primary section. If a failure occurs on the secondary section during a protection switch, the initial switch request is abandoned.

This chapter contains the following information:• Before You Create a 1+1 Optimized Protection Group, page 4-28• Create a 1+1 Optimized Protection Group, page 4-28


TraverseEdge 100 User Guide, Section 4: Configuring the NetworkBefore You Create a 1+1 Optimized Protection Group

Before You Create a 1+1 Optimized Protection Group

Review this information before you create a 1+1 optimized protection group.The TE-100 system supports 1+1 bi-directional protection switching.

Create a 1+1 Optimized Protection Group

Use this procedure to create a 1+1 optimized protection group.

Table 4-15 1+1 Optimized Protection Group Requirements




Software

Network is discovered. Section 4—Configuring the Network, Chapter 1—“Configuring the Network,” Discover TE-100 Nodes, page 4-4

Timing is configured. Section 4—Configuring the Network, Chapter 2—“Configuring Network Timing,” page 4-9

No line-level alarms (LOS, LOF, AIS-L, SF-BER-L) are present on the interfaces you are using to configure the protection group.



TransNav Management System GUI Guide, Section 4—Protection Switching, Chapter 4—“1+1 MSP/APS Protection Groups,” page 4-23

Table 4-16 Create a 1+1 Optimized Protection Group

Step Procedure

1 Review the information in Before You Create a 1+1 Optimized Protection Group, page 4-28 before you start this procedure.

2 In Shelf View, click the Protection tab to display the Protection Groups screen.

3 Add an equipment protection group. From the New list, select 1+1_optimized.

Figure 4-21 Select 1+1 Optimized

Step 4


Chapter 5 Creating a 1+1 Optimized Protection GroupCreate a 1+1 Optimized Protection Group

4 Click Add to display the Create Protection Group tab, Add 1+1 Protection Group screen

Figure 4-22 Add 1+1 Optimized Protection Group Screen

5 In the Name field, enter the name of the node (maximum 43 characters). Use alphanumeric characters only. Do not use punctuation or any other special character in this field.

6 In the WTR Time field, set the time (in minutes) after a protection switch that the section carrying active traffic becomes the primary section.

Enter a number in the between 1 and 60; default is 5.

7 Select a port for Section 1. On the Section 1 row, click the Port field and select the first working channel.

Figure 4-23 Select Protecting and Working Ports

8 Repeat Step 7 for Section 2. On the Section 2 row, click the Port field and select the port for the second working channel.

Table 4-16 Create a 1+1 Optimized Protection Group (continued)

Step Procedure

5 6

7

9


TraverseEdge 100 User Guide, Section 4: Configuring the NetworkCreate a 1+1 Optimized Protection Group

9 Click Add to return to the Protection Groups screen on the Protection tab.

Figure 4-24 Protection Groups Screen

The system assigns an ID to the new protection group.

10 The Create a 1+1 Optimized Protection Group procedure is complete.

Table 4-16 Create a 1+1 Optimized Protection Group (continued)

Step Procedure


SECTION 5 CREATING TDM SERVICESSECTION 5CREATING SERVICES

Contents

Chapter 1Service Creation Concepts

TE-100 Services Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1Supported Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2

Multicast Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2Resource Advisory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2VT Switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2

Service Creation Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2Service Creation Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3

1. Add the Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-32. Configure Service Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-33. Select the Service Endpoints. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-44. Configure Service Protection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-45. Configure Other Service Characteristics. . . . . . . . . . . . . . . . . . . . . . . 5-56. Activate the Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5

Before You Start Creating Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5

Chapter 2Service Applications

OC-48 STS UPSR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8STM-16 SNCP Ring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9OC-3/12 VT Path Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10STM-1/-4 Path Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11

Chapter 3Common Procedures for Creating Services

Activate or Deactivate a Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14Duplicate a Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15

Chapter 4Configuring SONET Equipment

Before You Configure SONET Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17Configure Interface Module SONET Parameters . . . . . . . . . . . . . . . . . . . . . . 5-18Configure DS1 Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-20Configure DS3 Clear Channel Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-22Configure BER Thresholds for an STS Path . . . . . . . . . . . . . . . . . . . . . . . . . . 5-24Configure SONET Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-27

Chapter 5Configuring SDH Equipment

Before You Configure SDH Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-33Configure Interface Module SDH Parameters. . . . . . . . . . . . . . . . . . . . . . . . . 5-34


TraverseEdge 100 User Guide, Section 5 Creating TDM Services

Configure E1 Port Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-36Configure E3 Port Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-38Configure BER Thresholds for an STM Path. . . . . . . . . . . . . . . . . . . . . . . . . . 5-40Configure STM-N Port Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-42

Chapter 6Creating SONET Services

Before You Create SONET Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-50Bandwidth Requirements for SONET Services . . . . . . . . . . . . . . . . . . . . . . . . 5-51Endpoints for STS Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-51Endpoints for VT1.5 Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-52Starting STS Numbers for SONET Services . . . . . . . . . . . . . . . . . . . . . . . . . . 5-52Create a SONET Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-53

Chapter 7Creating SDH Services

Before You Create SDH Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-60Bandwidth Requirements for SDH Services . . . . . . . . . . . . . . . . . . . . . . . . . . 5-61Guidelines to Create SDH Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-61Create an SDH Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-62Create an SDH-Endpoint Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-68Create an SDH Transport Path Hop-by-Hop . . . . . . . . . . . . . . . . . . . . . . . . . . 5-74


SECTION 5CREATING TDM SERVICES

Chapter 1 Service Creation Concepts

Introduction Creating services in a TraverseEdge 100 (TE-100) network requires that you first identify switching requirements, bandwidth requirements, and service types. This chapter explains the particulars of services on a TE-100 platform: • TE-100 Services Definition, page 5-1• Supported Features, page 5-2• Service Creation Model, page 5-2• Service Creation Process, page 5-3• Before You Start Creating Services, page 5-5

TE-100 Services Definition

A service in a TE-100 network connects traffic from a source to a destination. The source can be a port, a path, or a subpath. The source originates on the interface module.

The destination of the service varies depending on the connection you are creating. The destination can be a compatible port or another service on the same node.

The TE-100 system supports the following types of services in ANSI mode:• SONET

– OC-48 STS UPSR– OC-3/12 VT UPSR

• DS1 Mux STS UPSR• Mixed traffic: Ethernet and TDM on STS UPSR

The TE-100 system supports the following types of services in ITU mode:• SDH

– STM-16 SNCP – STM-1/4 VC SNCP

• E1 Mux SNCP• Mixed traffic: Ethernet and TDM on SNCP rings


TraverseEdge 100 User Guide, Section 5: Creating TDM ServicesSupported Features

Supported Features

Multicast Connections

Multicast connections are connections made from one source to multiple destinations. The TE-100 system supports multicast connections for the following services:• SONET-STS• SONET-VT• SDH-VC4• SDH-VC3• SDH-VC12• Ethernet bridge and aggregated bridge services

Use multicast connections to create drop-and-continue services in a TE-100 network.

Resource Advisory

If this feature is enabled, the system displays only available resources. Ports, paths, and other resources assigned to activated services appear in the graphical user interface with an asterisk (*).

VT Switching

The TE-100 system supports VT switching only on the OC-3/12 versions.

The TE-100 system supports low order VC switching only on the STM-1/4 versions.

Service Creation Model

You can create services in a TraverseEdge network hop-by-hop only. A hop-by-hop service is a service that you configure between two modules or two ports on one node. That is, you select the source and destination endpoints on one node only.

Figure 5-1 Hop-by-Hop Services Creation Model

By creating a transport path hop-by-hop through the network, you can add or drop traffic, monitor performance, and alarms at each hop.

Trib

utar

y C

ard

Trun

k C

ard

Trun

k C

ard

Trun

k C

ard

Trun

k C

ard

Trib

utar

y C

ard

Intermediatenode

Endpointnode

Endpointnode

Source Destination Source Destination Source Destination


Chapter 1 Service Creation ConceptsService Creation Process

Service Creation Process

1. Add the Service.

On the Service tab, select the service type and click Add.

2. Configure Service Parameters.

Enter the name of the service and configure other general parameters.

1

2


TraverseEdge 100 User Guide, Section 5: Creating TDM ServicesService Creation Process

3. Select the Service Endpoints.

Set the endpoints for this service. Click the Source row in the Endpoint column to display the Choose an Endpoint dialog box. Select the source and click Done to close the dialog box.

Click the Destination row, select the endpoint in the dialog box and click Done.

4. Configure Service Protection.

Click the Protection parameter field to display the Protection dialog box. Select the type of protection for the service by clicking on the tabs in the dialog box.

Configure any applicable parameters.

Click Done to close the dialog box and return to the Create Service tab.

3

4


Chapter 1 Service Creation ConceptsBefore You Start Creating Services

Before You Start Creating Services

Before you start provisioning your network, the following tasks need to be complete.

5. Configure Other Service Characteristics.

Click the Advanced button to display the Advanced Parameters dialog box.

Configure the characteristics of the service.

6. Activate the Service.

On the Service tab, click the service to select it, right-click for the menu, and click Activate.

5

7



Hardware


Section 2—Platform Specifications, Chapter 9—“Network Topologies,” page 2-43


Section 3—Installation and Configuration, Chapter 1—“Installation Overview,” page 3-1


TraverseEdge 100 User Guide, Section 5: Creating TDM ServicesBefore You Start Creating Services

Wherever possible, a table listing requirements and guidelines precedes each procedure. See each topic for requirements specific to the task.

Software

TransNav server is constructed and the management software is installed. The server is initialized and started.

TransNav Management System Server Guide.


Section 3—Installation and Configuration, Chapter 10—“Node Start-up and Initial Configuration,” page 3-69.

You are logged into the graphical user interface. TransNav Management System GUI Guide, Chapter 3—“Starting the Graphical User Interface,” page 2-17.

Table 5-1 Before Provisioning Your Network Requirements (continued)




Chapter 2 Service Applications

Introduction This chapter describes four service applications for a TraverseEdge 100 (TE-100) network: • OC-48 STS UPSR, page 5-8• STM-16 SNCP Ring, page 5-9• OC-3/12 VT Path Protection, page 5-10• STM-1/-4 Path Protection, page 5-11


TraverseEdge 100 User Guide, Section 5: Creating TDM ServicesOC-48 STS UPSR

OC-48 STS UPSR

This hop-by-hop services model shows how a TE-100 node acts as an edge TDM multiplexer. In the diagram below, three TE-100 nodes and one Traverse node are connected in an OC-48 UPSR. The TE-100 nodes are part of an access ring, and the Traverse node is part of a metro transport ring. The Traverse aggregates the traffic from the access ring onto the metro ring.

The hop-by-hop services model below shows the flow of traffic:• TE-100 NodeA adds 28 DS1s to STS -1 and bridges them around the ring.• TE-100 NodeB has simple SONET cross-connects to pass the traffic from NodeA

and NodeC through the node to the Traverse.• TE-100 NodeC adds one DS3 to STS-2 and bridges it around the ring to the

Traverse. NodeC also has simple SONET cross-connects to pass traffic from NodeA and NodeB through the node to the Traverse.

Figure 5-2 OC-48 STS UPSR

NodeA

NodeC

NodeB

1. OC-48 UPSR Protection Group

1. OC-48 STS UPSRWest ports: p-1East ports: p-2

2. Service Type: SONETBandwidth: STS-1Source: NodeA/s-3 (DS1)Dest: NodeA/s-0/p-2/sts-1Protection Type: Full

2.

Node1

4. Service Type: SONETBandwidth: STS-1Source: NodeC/s-3/p-1 (DS3)Dest: NodeC/s-0/p-2/sts-2 (OC-48)Protection Type: Full

4.5. Service Type: SONET (pass-through)Bandwidth: STS-1Source: NodeA/s-0/p-1/sts-2 (OC-48)Dest: NodeA/s-0/p-2/sts-2 (OC-48)Protection Type: Full

5.

5.

3.

3.

sts-1

sts-1 sts-1

sts-1

sts-2sts-2

sts-2

sts-2

3. Service Type: SONET (pass-through)Bandwidth: STS-1Source: NodeB/s-0/p-1/sts-1Dest: NodeB/s-0/p-2/sts-1Protection Type: Full


Chapter 2 Service ApplicationsSTM-16 SNCP Ring

STM-16 SNCP Ring

This hop-by-hop services model shows how a TE-100 node acts as an edge TDM multiplexer. In the diagram below, three TE-100 nodes and one Traverse node are connected in an STM-16 SNCP ring. The TE-100 nodes are part of an access ring, and the Traverse node is part of a metro transport ring. The Traverse aggregates the traffic from the access ring onto the metro ring.

The hop-by-hop services model below shows the flow of traffic:• TE-100 NodeA adds 21 E1s to a HO VC-3 and bridges them around the ring.• TE-100 NodeB has simple SDH cross-connects to pass the traffic from NodeA and

NodeC through the node to the Traverse.• TE-100 NodeC adds one E3 to another HO VC-3 and bridges it around the ring to

the Traverse. NodeC also has simple SDH cross-connects to pass traffic from NodeA and NodeB through the node to the Traverse.

Figure 5-3 STM-16 SNCP Ring

NodeA

NodeC

NodeB

1. STM-16 Protection Group

1. STM-16 SNCP RingWest ports: p-1East ports: p-2

2. Service Type: SDHBandwidth: VC-3Source: NodeA/s-3 (E1)Dest: NodeA/s-0/p-2/a-1/vc3-1Protection Type: Full

2.

Node1

4. Service Type: SDHBandwidth: VC-3Source: NodeC/s-3/p-1 (E3)Dest: NodeC/s-0/p-2/a-1/vc3-2 (STM-16)Protection Type: Full

4.5. Service Type: SDH (pass-through)Bandwidth: VC-3Source: NodeA/s-0/p-1/a-1/vc3-2Dest: NodeA/s-0/p-2/a-1/vc3-2Protection Type: Full

5.

5.

3.

3.

vc3-1

vc3-1 vc3-1

vc3-1

vc3-2vc3-2

vc3-2

vc3-2

3. Service Type: SDH (pass-through)Bandwidth: VC-3Source: NodeB/s-0/p-1/a-1/vc3-1Dest: NodeB/s-0/p-2/a-1/vc3-1Protection Type: Full


TraverseEdge 100 User Guide, Section 5: Creating TDM ServicesOC-3/12 VT Path Protection

OC-3/12 VT Path Protection

This hop-by-hop services model shows three TE-100 nodes and one Traverse node in an OC-3/12 ring topology. Again, the TE-100 nodes are part of an access ring and the Traverse is part of a metro ring. The Traverse aggregates the traffic from the access ring onto the metro ring.

The VTX/VCX component on the system cards enables the adding and dropping of VTs anywhere in the ring.

In this example, the traffic flows as follows:• TE-100 NodeA adds five 1+1 path protected DS1s to STS -1 and bridges them

around the ring.• TE-100 NodeB cross-connects STS-1 and adds five of its own 1+1 path protected

DS1s to the same STS-1 path. • TE-100 NodeC simply passes the traffic from NodeA and NodeB through to the

Traverse.

Figure 5-4 OC-3/12 VT Path Protection

NodeA

NodeC

NodeB

OC-3/12 Ring

Node1

2.

sts-1

sts-1 sts-1

sts-1

2.

1a.

1a. Service Type: SONETBandwidth: VT 1.5Source: NodeA/s-3/p-n (n=1 to 5) (DS1)Dest: NodeA/s-0/p-2/sts-1/vtg-1/vt-n (n=1 to 5)Protection Type: 1+1 Protected

2. Service Type: SONET (pass-through)Bandwidth: STS-1Source: s-0/p-1/sts-1 (OC-3/12)Dest: s-0/p-2/sts-1 (OC-3/12)Protection Type: 1+1 Path Protected

3a. Service Type: SONETBandwidth: VT 1.5Source: NodeB/s-3/p-n (n = 28 to 24) (DS1)Dest: NodeB/s-0/p-2/sts-1/vtg-1/vt-n (n = 6 to 10)Protection Type: 1+1 Path Protected

1b. Service Type: SONETBandwidth: VT 1.5Source: NodeA/s-3/p-n (n=1 to 5) (DS1)Dest: NodeA/s-0/p-1/sts-1/vtg-1/vt-n (n=1 to 5)Protection Type: Unprotected

3b. Service Type: SONETBandwidth: VT 1.5Source: NodeB/s-3/p-n (n=28 to 24) (DS1)Dest: NodeB/s-0/p-1/sts-1/vtg-1/vt-n (n=6 to 10)Protection Type: Unprotected

3b.3a.

1b.


Chapter 2 Service ApplicationsSTM-1/-4 Path Protection

STM-1/-4 Path Protection

This hop-by-hop services model shows three TE-100 nodes and one Traverse node in an STM-1/-4 ring topology. Again, the TE-100 nodes are part of an access ring and the Traverse is part of a metro ring. The Traverse aggregates the traffic from the access ring onto the metro ring.

The VTX/VCX component on the system cards enables the adding and dropping of VCs anywhere in the ring.

In this example, the traffic flows as follows:• TE-100 NodeA adds five 1+1 path protected E1s to VC3-1 and bridges them

around the ring.• TE-100 NodeB cross-connects VC3-1 and adds five of its own 1+1 path protected

E1s to the same path. • TE-100 NodeC simply passes the traffic from NodeA and NodeB through to the

Traverse.

Figure 5-5 STM-1/-4 VC12 Path Protection

NodeA

NodeC

NodeB

STM-1/-4 Ring

Node1

2.

VC-3

VC-3 VC-3

VC-3

2.

1a.

1a. Service Type: SDHBandwidth: VC-12Source: NodeA/s-3/p-n (n=1 to 5) (E1)Dest: NodeA/s-0/p-2/a-1/tug3-1/tug2-1/vc12-n (n=1 to 5)Protection Type: 1+1 Protected

2. Service Type: SDH (pass-through)Bandwidth: VC-3Source: s-0/p-1/a-1/vc3-1Dest: s-0/p-2/a-1/vc3-1Protection Type: 1+1 Path Protected

1b. Service Type: SDHBandwidth: VC-12Source: NodeA/s-3/p-n (n=1 to 5) (E1)Dest: NodeA/s-0/p-1/a-1/tug3-1/tug2-1/vc12-n (n=1 to 5)Protection Type: Unprotected

3b.

1b.

3a. Service Type: SDHBandwidth: VC-12Source: NodeB/s-3/p-n (n=17 to 21) (E1)Dest: NodeB/s-0/p-2/a-1/tug3-1/tug2-1/vc12-n (n=6 to 10)Protection Type: 1+1 Protected

3b. Service Type: SDHBandwidth: VC-12Source: NodeB/s-3/p-n (n=17 to 21) (E1)Dest: NodeB/s-0/p-1/a-1/tug3-1/tug2-1/vc12-n (n=6 to 10)Protection Type: Unprotected

3a.


TraverseEdge 100 User Guide, Section 5: Creating TDM ServicesSTM-1/-4 Path Protection



Chapter 3 Common Procedures for Creating Services

Introduction This chapter contains procedures for the following topics for creating services in a TraverseEdge 100 (TE-100) network:• Activate or Deactivate a Service, page 5-14• Duplicate a Service, page 5-15

See the TransNav Management System GUI Guide for explanations of each screen.


TraverseEdge 100 User Guide, Section 5: Creating TDM ServicesActivate or Deactivate a Service

Activate or Deactivate a Service

Use this procedure to activate or deactivate one service or multiple services.

Table 5-2 Activate or Deactivate a Service

Step Procedure

1 Complete the procedure Create a SONET Service, page 5-37.

2 On the Service tab, complete Step 3 and Step 4.

Figure 5-6 Service Tab—Activate

3 Click a Service from the list.

Hold the Ctrl key and click individual services.

OR

Hold the Shift key and click a range of services.

4 Right-click and select Activate to start the connection carrying traffic.

OR

Right-click and select Deactivate to stop the connection from carrying traffic.

5 The Activate or Deactivate a Service procedure is complete.

34


Chapter 3 Common Procedures for Creating ServicesDuplicate a Service

Duplicate a Service

Use this procedure to create similar services quickly.

Table 5-3 Duplicate a Service

Step Procedure

1 On the Service tab, select a service from the service list.

Figure 5-7 Duplicate a Service

2 Right-click and select Duplicate from the menu to display the Duplicate Service dialog box.

Figure 5-8 Duplicate Service Dialog Box

3 On the Duplicate Service dialog box, click the plus sign in the Add column to add new services to the list.

Add as many rows as you need for new services.

Figure 5-9 Add a New Row for Each New Service

1

2

3

4

6


TraverseEdge 100 User Guide, Section 5: Creating TDM ServicesDuplicate a Service

4 Click a row in the Service Name column and enter a unique name for the service. Use alphanumeric characters and spaces only. Do not use any other punctuation or special characters.

5 Repeat Step 4 for each new service.

6 Click Apply to save the changes. The Status column changes from Ready to Succeeded.

7 Click Done to close the dialog box and return to the service list on the Service tab.

Figure 5-10 Click Apply and Then Click Done

8 On the Service tab, find and select one of the new services.

9 Right-click and select Edit from the menu.

10 On the Create Service tab, select new endpoints for the service.

11 Click Apply to save the changes and return to the service list on the Service tab.

12 Repeat Steps 8 through 11 for each duplicated service.

13 The Duplicate a Service procedure is complete.

Continue to the procedure Activate or Deactivate a Service, page 4-16 to activate the new services.

Table 5-3 Duplicate a Service (continued)

Step Procedure

7



Chapter 4 Configuring SONET Equipment

Introduction You can customize certain parameters on each module (card) in a TraverseEdge 100 (TE-100) shelf. This chapter explains the following information for the cards supported in this release:• Before You Configure SONET Equipment, page 5-17• Configure Interface Module SONET Parameters, page 5-18• Configure DS1 Ports, page 5-20• Configure DS3 Clear Channel Ports, page 5-22• Configure BER Thresholds for an STS Path, page 5-24• Configure SONET Port, page 5-27

These procedures describe how to change configurable parameters only. See the TransNav Management System GUI Guide, Section 5—Equipment, Chapter 1—“Common Equipment,” page 5-3 for explanations of all the parameters and fields on each card.

You can change parameters for each card:• During the preprovisioning process. Upon discovery of the equipment, the

management server downloads the preprovisioned data to the node.• After the equipment is discovered. If a piece of equipment has not been

preprovisioned when it is discovered, it arrives with default values. Change the default values on the Config tab.

Before You Configure SONET Equipment

Review this information before you start to configure SONET equipment on the TE-100 shelf.

Table 5-4 SONET Equipment Requirements



Software

Node is installed and commissioned with ANSI_only or ANSI_default in the standard parameter.



TraverseEdge 100 User Guide, Section 5: Creating TDM ServicesConfigure Interface Module SONET Parameters

Configure Interface Module SONET Parameters

There are configurable parameters on the interface module for DS1 that control how DS1 channels on the module map to a VT payload or multiplex into an STS path.


Protection groups are connected and configured.

See Section 4—Configuring the Network:• Chapter 3—“Creating a UPSR/SNCP Protection

Group,” page 4-17• Chapter 4—“Creating 1+1APS/MSP Protection

Groups,” page 4-23• Chapter 5—“Creating a 1+1 Optimized Protection

Group,” page 4-27

Table 5-4 SONET Equipment Requirements (continued)


Important: Changing these parameters on the interface card is service affecting. You cannot complete this procedure if the card is carrying traffic (if there are services activated).

Table 5-5 Change Interface Module SONET Parameters

Step Procedure

1 Review the information in the topic: Before You Configure SONET Equipment, page 5-17.

2 In Shelf View, click the interface module, then click the Config tab to display the Card Configuration screen.

Figure 5-11 Interface Card, Config Tab

3 In the Customer Tag field, enter an alphanumeric character string to identify the card to a customer.

2

4

5

3


Chapter 4 Configuring SONET EquipmentConfigure Interface Module SONET Parameters

4 Select how the DS1 channels on this module are multiplexed into an STS path. From the DS1 to DS3 Mapping list:• Select VT15 (default) to multiplex the DS1 channels into a

VT1.5-mapped STS.• Select DS3 to multiplex the signal into a DS3-mapped STS.

5 Click Apply to save the changes.

6 The Change Interface Module SONET Parameters procedure is complete. • For detailed LCAS information, see Section 2—Creating Ethernet

Services, Chapter 4—“Link Capacity Adjustment Scheme,” page 2-37• For detailed MAC Address information, see Section 6—Creating

Ethernet Services, Chapter 2—“Configuring Ethernet Equipment,” View or Edit the MAC Address Table, page 6-9.

Table 5-5 Change Interface Module SONET Parameters (continued)

Step Procedure


TraverseEdge 100 User Guide, Section 5: Creating TDM ServicesConfigure DS1 Ports

Configure DS1 Ports

Use this procedure to customize the behavior of a DS1 port.

Table 5-6 Configure DS1 Port

Step Procedure

1 Review the information in Before You Change SONET Equipment Configurations, page 2-4 before you start this procedure.

2 In Shelf View, click a DS1 port on the tributary module.

3 Click the Config tab to display the DS1 Port Configuration screen.

Figure 5-12 DS1 Port Configuration Screen

3

4

6 7

5


Chapter 4 Configuring SONET EquipmentConfigure DS1 Ports

4 Change any of the following parameters for the DS1 interface:

Line Format: Select one of the following:• ESF (default): Extended superframe format• SF: Superframe format• Unframed: Upon detecting an LOF condition (in Unframed mode), the

system does not:– Raise an LOF alarm– Propagate an AIS– Insert an RAI– Count OOF and SEF framing errors

Line Coding: Displays the line coding technique used for performance monitoring at the line layer. Select one of the following:• AMI (default): alternate mark inversion• B8ZS: bipolar 8-zero substitution

AIS Mask (Alarm Indication Signal Mask). Select one of the following:• Yes: Mask AIS/alarm for unused direction• No (default): Do not mask AIS/alarm for any direction

Line Build Out: Displays the distance from the subscriber interface to the physical port on the node. Select one of the following:• 0–133 ft (default)• 133–266 ft• 266–399 ft• 399–533 ft• 533–665 ft

5 Change any of the following general parameters for the interface:

Customer: Select from the list of defined customers.

Customer Tag: Enter an alphanumeric character string to identify the card to a customer.

PM Template: Select from the list of defined performance monitoring templates (of type ds1_ptp_pm). The default value is default, which contains default thresholds for performance monitoring parameters and thresholds for DS1 ports.

Alarm Profile: Select from the list of defined alarm profiles (of type ds1_ptp) to customize service-affecting and non-service-affecting alarm severities. The default is the default ds1_ptp alarm profile.

6 Click the Lock icon to unlock the port. The port must be unlocked to apply changes and monitor potential problems by generating alarms. The Lock icon is located in the lower left corner of the screen.

Table 5-6 Configure DS1 Port (continued)

Step Procedure


TraverseEdge 100 User Guide, Section 5: Creating TDM ServicesConfigure DS3 Clear Channel Ports

Configure DS3 Clear Channel Ports

Use this procedure to customize behavior of a DS3-CC port.


8 The Configure DS1 Port procedure is complete.

Table 5-6 Configure DS1 Port (continued)

Step Procedure

Table 5-7 Configure DS3CC Ports

Step Procedure

1 Review the information in the topic Before You Configure SONET Equipment, page 5-17.

2 In Shelf View, click a DS3-CC port.

3 Click the Config tab to display the DS3 Clear Channel Port Configuration screen.

Figure 5-13 DS3 Clear Channel Port Configuration Screen

3

4

6 7

5


Chapter 4 Configuring SONET EquipmentConfigure DS3 Clear Channel Ports


Line Format: Select one of the following:• M23 (default): Seven DS2 signals asynchronously multiplexed into

the DS3 signal.• CBIT: 28 DS-1 signals are multiplexed into the DS3 signal, with the

C-bit used as control bit.• Unframed: A payload of 44.210 Mbps is supported with M, F, P, X,

and C bits preserved to ensure compatibility. Upon detecting an LOF condition (in Unframed mode), the system does not:– Raise an LOF alarm– Propagate an AIS– Insert an RAI– Count OOF and SEF framing errors

In Band Loopback:• Disabled (default)• Enabled

AIS Mask (Alarm Indication Signal Mask): Select one of the following:• Yes: Mask AIS/alarm for unused direction.• No (default): Do not mask AIS/alarm for any direction.

AIS Format: Select one of the following:• NAS (default): North America Standard. All C-bits shall be set to 0.

All X-bits shall be set to 1. The information bits shall be set to a 1010... repeating sequence, with a 1 immediately following each of the control bit positions.

• ONES: Unformatted all ones.

Line Build Out: Select the length of cable between the node and the intermediate DS3 patch panel: • 0–225 ft (default)• 255–450 ft

Table 5-7 Configure DS3CC Ports (continued)

Step Procedure


TraverseEdge 100 User Guide, Section 5: Creating TDM ServicesConfigure BER Thresholds for an STS Path

Configure BER Thresholds for an STS Path

Configure the thresholds for the path-level signal failed bit error ratio (SFBER) and signal degrade bit error ratio (SDBER) on the system card card. When the thresholds are exceeded, the system raises an SFBER-P or SDBER-P alarm.




PM Template: Select from the list of defined performance monitoring templates (of type ds_ptp_pm). The default value is default, which contains default thresholds for performance monitoring parameters and thresholds for DS1 ports.

Alarm Profile: Select from the list of defined alarm profiles (of type ds_ptp) to customize service-affecting and non-service-affecting alarm severities. The default is the default ds_ptp alarm profile.

6 Click the Lock icon to unlock the port. The port must be unlocked to apply changes and monitor performance by generating alarms. The Lock icon is located in the lower left corner of the screen.


8 The Configure DS3CC Ports procedure is complete.

Table 5-7 Configure DS3CC Ports (continued)

Step Procedure

Table 5-8 Change BER Thresholds for an STS Path

Step Procedure


2 In Shelf View, click the system module.


Chapter 4 Configuring SONET EquipmentConfigure BER Thresholds for an STS Path

3 Click the Config tab to display the Card Configuration screen.

Figure 5-14 SONET Card, Config Tab

These parameters appear depending on the speed of the SONET interface and apply to all the paths on the card.


5 Set the transmission quality (bit error ratio) of failed signals in the STS path. When the error rate crosses the value specified in this parameter, the system raises a signal failed bit error rate (BERSF-P) alarm.

Select one of the following values:• 1E-3 (default for STS-1 SF BER). Value equals 1 x 10-3

• 1E-4 (default for STS-3c and STS-12c SF BER). Value equals 1x10-4

• 1E-5 (default for STS-48c SF BER). Value equals 1 x 10-5

• 1E-6. Value equals 1 x 10-6


6 Set the transmission quality (bit error ratio) of degraded signals (SD) in the STS path. When the error rate crosses the value specified in this parameter, the system raises a signal degraded bit error rate (BERSD-P) alarm. Select one of the following values:• 1E-4. Value equals 1 x 10-4


• 1E-6 (default for STS-1 SD BER). Value equals 1 x 10-6

• 1E-7 (default for STS-3cand STS-12c SD BER). Value equals 1 x 10-7

• 1E-8 (default for STS-48c SD BER). Value equals 1 x 10-8




Table 5-8 Change BER Thresholds for an STS Path (continued)

Step Procedure

2

4 5

6

3


TraverseEdge 100 User Guide, Section 5: Creating TDM ServicesConfigure BER Thresholds for an STS Path


8 The Change BER Thresholds for an STS Path procedure is complete.

Table 5-8 Change BER Thresholds for an STS Path (continued)

Step Procedure


Chapter 4 Configuring SONET EquipmentConfigure SONET Port

Configure SONET Port

Use this procedure to customize the behavior of a SONET port.

Table 5-9 Configure SONET Ports

Step Procedure


2 In Shelf View, click a SONET port in slot 0.

Figure 5-15 SONET Port Configuration Screen

SONET port

3

4

5

6 897


TraverseEdge 100 User Guide, Section 5: Creating TDM ServicesConfigure SONET Port

3 Change any one of the following parameters for the SONET interface:

AIS Mask (Alarm Indication Signal Mask):• Yes: Mask AIS/alarm for unused direction.• No (default): Do not mask AIS/alarm for any direction.

Sync Source: Indicates if this port is used to synchronize status. Valid values are:• Primary: Indicates this port is the primary sync source.• Secondary: Indicates this port is the secondary sync source.• Not used: Indicates this port is not used as the sync source.

SfBer-L: Measures the transmission quality (bit error ratio) of failed signals on the link. When the error rate crosses the value specified in this parameter, the system raises a signal failed bit error rate (BERSF-L) alarm and performs a protection switch. Select one of the following values: • 1E-3 (default). Value equals 1 x 10-3 • 1E-4. Value equals 1 x 10-4 • 1E-5. Value equals 1 x 10-5

Transmitter State: Select one of the following:• On (default): Laser is turned on.• Off: Laser is turned off.

Forced DUS (Do not Use for Synchronization): Select for this port to transmit the SSM (synchronization status message) DUS. This prevents the remote node that receives this signal from using the line as a timing reference.

SdBer-L: Measures the transmission quality (bit error ratio) of degraded signals on the optical link. When the error rate crosses the value specified in this parameter, the system raises a signal degraded bit error rate (BERSD-L) alarm and performs a protection switch. Select one of the following values: • 1E-9. Value equals 1 x 10-9



• 1E-6 (default). Value equals 1 x 10-6


Table 5-9 Configure SONET Ports (continued)

Step Procedure



4 Configure the automatic laser shutdown feature using the following parameters:

Trnsm Auto Shtdwn: Automatically shut down the transmit laser on optical interfaces when the system detects a receive LOS for 500 ms. The system turns the transmit laser off after detecting a receive LOS for 800 ms. The system raises the ALS alarm against the optical facility when the transmitter has been turned off automatically.• Disabled (default). The ALS feature is turned off.• Manual. The operator initiates a single laser pulse from the transmitter

for the amount of time specified in the Recovery Pulse Width parameter. To send the single laser pulse, click the Current Transmitter State button, then click Manual Restart.

• Automatic. The system turns off the transmit laser for a random time between 100 and 300 seconds. The transmit laser turns on if one of the following conditions occur:– The user manually sends a single laser pulse (Current

Transmitter State button). – If the system receives a valid signal for more than 800 ms.– After the random timer expires, the system sends periodic laser

pulses from the transmitter for the amount of time specified in the Recovery Pulse Width parameter.

Current Transmitter State: Click this button to display the current state of the optical transmitter. See Trnsm Auto Shtdwn parameter for details.

Rcvry Pulse Width: The system enables the transmitter for the amount of time specified in this parameter. Valid only if the value in Trnsm Auto Shtdwn is Manual or Automatic. Enter a time between 2 and 10 seconds; default is 5 seconds.

5 Set the section trace formats and identifiers for this interface:

Fwd Section Trc Fmt (Forward Section Trace Format): This port transmits an access point identifier in the J0 byte of the SDH frame so that the section receiver can verify its continued connection. The valid value is 16 bytes.

Fwd Section Trace: The access point identifier transmitted in the J0 byte. Enter an alphanumeric character string.

Rev Section Trc Fmt (Reverse Section Trace Format): This port expects an access point identifier in the J0 byte of the SDH frame to verify its continued connection with the transmitter. If this port receives an incorrect identifier, the system raises an RS-TIM (Regenerator Section - Trace Identifier Mismatch alarm). The valid value is 16 bytes.

Rev Section Trace: The expected access point identifier to be received in the J0 byte. Enter an alphanumeric character string.


Step Procedure



6 Specify if the system uses the DCC bytes to communicate with other nodes in this network.

In the Control Data parameter, select one of the following:• Enabled (default): The management system uses this interface for

management traffic.• Disabled: The management system does not use this interface for

management traffic.

7 If this system uses the DCC bytes to communicate with other nodes in this network, specify which DCC bytes are processed. You can change the value in this parameter only if the value in Control Data is Disabled.

In the Terminate DCC parameter, specify one of the following values:• Section: specifies that the interface uses the D1-D3 bytes (192 Kbps)

of the first STS on this interface for management traffic. • Line (default): specifies that the interface uses the D4-D12 bytes (576

Kbps) of the first STS on this interface for management traffic. • Line&Section: specifies that the interface uses the combined section

DCC and line DCC bytes from the first, second, and third STS on the interface (2.3 Mbps) for management traffic.

• Path (TE-100 OC-3 and OC-12 and Traverse OC-3 interfaces only): specifies that the interface uses the F2 byte (64 Kbps) of the STS for management traffic.

8 If the value in Terminate DCC is Path, specify which path (or paths) to carry management traffic. Click the Path DCC Configuration button to display the Path DCC Configuration dialog box.

Figure 5-16 OC-12 Path DCC Configuration Dialog Box

Select the paths on the interface that you want to use to carry management traffic.

Click Done and return to the Config tab on the main screen.


Step Procedure





PM Template: Select from the list of defined performance monitoring templates (of type sonet_ptp_pm). Default value is default, which contains default thresholds for performance monitoring parameters and thresholds for SONET ports.

Alarm Profile: Select from the list of defined alarm profiles (of type sonet_ptp) to customize service-affecting and non-service-affecting alarm severities. Default is the default sonet_ptp alarm profile.

10 L2 Protocol: Determines the Layer 2 (L2) protocol for this port. • PPP (default): Point-to-point protocol. Use PPP if this port is

connected to another Traverse or TE-100 platform.• LAPD: Link access procedure D-channel. Select LAPD if this port is

connected to legacy third-party ADM equipment and this node is used as an OSI DCC gateway node.

LAPD Role: Select the role of this node in the OSI DCC gateway application.• Network• User

DWDM wl supp value: The DWDM wavelength supplied value.

LAPD Mode: Select the mode of this node in the OSI DCC gateway application.• AITS: Acknowledge information transfer service. Use this value if the

value in L2 Protocol is LAPD.• UITS (default): Unacknowledge information transfer service. Use this

value if the value in L2 Protocol is PPP.

LAPD MTU: Indicates the maximum transmission unit for this node if the value in L2 Protocol is PPP; default is 512.

DWDM wl: Select from the list of defined wavelength frequencies.


12 Click Apply.

13 The Configure SONET Ports procedure is complete.


Step Procedure





Chapter 5 Creating SONET Services

Introduction This chapter explains how to create the following service types in a TraverseEdge 100 (TE-100) network: • SONET-STS. Use this service to transport synchronous traffic through the

network. Use this service to create a transport path for either synchronous or Ethernet traffic through the network.

• SONET-VT1.5. Use this service to switch individual SONET VT1.5 payloads through the network.

This chapter includes the following topics:• Before You Create SONET Services, page 5-34• Bandwidth Requirements for SONET Services, page 5-35• Endpoints for STS Services, page 5-35• Endpoints for VT1.5 Services, page 5-36• Starting STS Numbers for SONET Services, page 5-36• Create a SONET Service, page 5-37


TraverseEdge 100 User Guide, Section 5: Creating TDM ServicesBefore You Create SONET Services

Before You Create SONET Services

Review the information in this topic before you create any SONET services.

Table 5-10 SONET Service Requirements



Software

Node is installed and commissioned with ANSI_only or ANSI_default in the standard parameter

Section 3—Installation and Configuration, Chapter 10—“Node Start-up and Initial Configuration,” page 3-69

Timing is configured Section 4—Configuring the Network, Chapter 2—“Configuring Network Timing,” page 4-9

Protection groups are connected and configured See Section 4—Configuring the Network:• Chapter 3—“Creating a UPSR/SNCP Protection


Groups,” page 4-23• Chapter 5—“Creating a 1+1 Optimized

Protection Group,” page 4-27

Source (tributary) and destination (transport) interfaces are configured correctly

Section 5—Creating TDM Services, Chapter 4—“Configuring SONET Equipment,” page 5-17

These procedures describe how to create a specific service and change only configurable parameters. See the TransNav Management System GUI Guide for descriptions of other fields on the screen.

TransNav Management System GUI Guide, Section 2—Services, Chapter 2—“SONET Services,” page 2-19

Provisioning model. • SONET-STS: hop-by-hop• SONET-VT1.5: hop-by-hop

Chapter 1—“Service Creation Concepts,” Service Creation Model, page 5-2

Bandwidth requirements Chapter 5—“Creating SONET Services,” Bandwidth Requirements for SONET Services, page 5-35 (below)


Chapter 5 Creating SONET ServicesEndpoints for STS Services


Bandwidth Requirements for SONET Services

The bandwidth of the Traverse system depends on the commissioned data rate of the system. The system supports up to the commissioned bandwidth in a protected or unprotected configuration.The following table specifies commissioned data rate and the supported bandwidth.

In an unprotected configuration, you must divide the STSs evenly among the unprotected ports. For example, on an unprotected OC-48 topology, you can use STS-1 through STS-24 on port 1 and STS-25 through STS-48 on port 2.

A system commissioned with the data rate of OC-3 supports up to six STS-1s of bandwidth.

Endpoints for STS Services

The following table lists valid sources and destinations for STS services. Your network may require creating multiple services at multiple nodes.

The Traverse system supports multicast STS connections for 1+1 path-protected and drop-and-continue services.

Table 5-11 Commissioned Data Rate and Supported SONET Bandwidth

Commissioned Data Rate Topology Bandwidth

OC-48 Protected or Unprotected up to 48 STSs

OC-12 Protected or Unprotected up to 12 STSs

OC-3 Protected up to 3 STSs

Unprotected up to 6 STSs

Table 5-12 Endpoints for STS Services

Sources Destinations

Port Type Mapping Port Type Mapping

OC-N node/slot/port/sts OC-NDS3CCall ports DS1

node/slot/port/stsnode/slot

DS3CC node/slot/port OC-NDS3CC

node/slot/port/stsnode/slot/port

DS1 node/slot OC-N node/slot/port/sts

SONET port on backplane for EOS ports

node/slot (Ethernet card)/sts

OC-N node/slot/port/sts

TraverseEdge 100 User Guide, Section 5: Creating TDM ServicesEndpoints for VT1.5 Services

Endpoints for VT1.5 Services

The following table lists valid sources and destinations for VT1.5 services. Your network may require creating multiple services at multiple nodes.

There must be a VT/TU 5G switch card or a card with an integrated VTX/VCX present in the shelf to create this service.

Starting STS Numbers for SONET Services

The starting STS number for any SONET service depends on the required bandwidth. For example, an OC-48 interface has a Src. Starting STS range of 1 to 48 if you select STS-1 in the Bandwidth parameter. If you select STS-12c in the Bandwidth parameter, the Src. Starting STS can be 1, 13, 25, or 37. The following table lists all of the valid starting STSs. The following table lists all the valid starting STS numbers.

Table 5-13 Endpoints for VT1.5 Services

Sources Destinations

Port Type Mapping Port Type Mapping

OC-N node/slot/port/sts/vtg/vt OC-NDS1

node/slot/port/sts/vtg/vtnode/slot/port

DS1 node/slot/port OC-NDS1

node/slot/port/sts/vtg/vtnode/slot/port

SONET port on backplane for EOS ports

node/slot (Ethernet card)/sts/vtg/vt

OC-N node/slot/port/sts/vtg/vt

Table 5-14 Valid Starting STS

Bandwidth

Starting STS

OC-3 OC-12 OC-48

STS-1 1, 2, 3 1, 2, 3, 4,..., 12 1, 2, 3, 4,..., 48

STS-3c 1 1, 4, 7, 10 1, 4, 7, 10, 16, 19,... 48

STS-12c — 1 1, 13, 25, 37

STS-48c — — 1


Chapter 5 Creating SONET ServicesCreate a SONET Service

Create a SONET Service

Use this procedure to create a SONET service.

Table 5-15 Create a SONET Service

Step Procedure

1 Add the SONET service.

Figure 5-17 Service Tab

a. Click the Service tab.b. From the Add button menu, select SONET.c. Click Add to display the Create Service tab.

2 In the Name parameter, enter a unique name for the service. Use alpha-numeric characters and spaces only. Do not use any other punctuation or special characters.

Figure 5-18 Create Service Tab

3 From the Bandwidth parameter, select the total bandwidth for the service: • VT1.5• STS-1 (default)• STS-3c

1a

1b

1c

23

4

5

10 12


TraverseEdge 100 User Guide, Section 5: Creating TDM ServicesCreate a SONET Service

4 Choose the endpoints for the service.

Refer to Endpoints for STS Services, page 5-35 as required.

Refer to Endpoints for VT1.5 Services, page 5-36 as required

Figure 5-19 Choose Endpoints for the Service

a. Click the first row in the Endpoint column to display the Choose an Endpoint dialog box.

b. Navigate the tree and select the correct source endpoint. c. Click Done to close the dialog box and return to the Create Services

tab on the main screen.d. Click the Destination row in the Endpoint column.e. Navigate the tree and select the correct destination endpoint.f. Click Done to close the dialog box and return to the Create Services

tab on the main screen.

Table 5-15 Create a SONET Service (continued)

Step Procedure

4a4b

4c



5 Configure the protection attributes for this service. Click the Protection field to display the Protection dialog box.

Figure 5-20 Protection Dialog Box

In the Protection Type parameter, select one of the following options: • Unprotected (default): Select this option for services that are either

unprotected, 1+1 APS/MSP protected, protected with an equipment protection group, or a 1+1 Path Protection group.

• Any: The system finds the best effort of protection through the network. There may be some spans of unprotected links, but the system will create the service.

• Full: The system only create the service if there is full protection on every transport link in the network.

• 1+1 Path Protected: If this service is protected by another service (two services model).

• UPSR Ingress: If the service is a SONET-VT service and is creating a bidirectional path across two interconnected UPSRs.

6 For services that have a protection type configured, configure the following parameters:• Revertive (default=not selected): Select the checkbox to switch traffic

back to the original path once the failure condition no longer exists.• WTR Time: Specifies the amount of time (in minutes) for the system

to wait before restoring traffic to the original path once the failure condition no longer exists. Specify a value between 1 and 60 minutes; default is 5.

If this service is protected by another service (two services path protection model), go to Step 7.


Step Procedure

510



7 For services protected by another service, click the 1+1 Path Protected tab and configure the HoldOffTimer parameter. This parameter applies only if there is also a 1+1 APS/MSP protection group. Allows line protection to switch first before the path switches. If the line switches within the specified time period, the path does not switch. The hold-off timer starts when path protection detects a path failure.

The range is 0 to 1000 ms. The default is 0 which means path protection performs protection switching immediately.

8 On the Protection dialog box, click Done to return to the Create Service tab on the main screen.

Figure 5-21 Click Done on the Protection Dialog Box

9 Configure more parameters of the service.

Figure 5-22 Advanced Parameters Dialog Box

a. On the Create Services tab, click Advanced to display the Advanced Parameters dialog box. For specific definitions of these parameters, see the TransNav Management System GUI Guide, Section 2—Services, Chapter 2—“SONET Services,” Configure Protection Parameters, page 2-24.

b. Click Done to return to the Create Services tab on the main screen.


Step Procedure

9



10 The Create a SONET Service procedure is complete.

11 Click Apply to save this configuration and return to the Service tab on the main screen.

Continue to the procedure Activate or Deactivate a Service, page 5-14.


Step Procedure



Pa
ge 5-42 Force10 Networks Release TE3.2.x


Chapter 6 Configuring SDH Equipment

Introduction You can customize certain parameters on each module in a TraverseEdge 100 (TE-100) shelf. This chapter explains the following information for the SDH equipment supported in this release:• Before You Configure SDH Equipment, page 5-43• Configure Interface Module SDH Parameters, page 5-45• Configure E1 Port Parameters, page 5-47• Configure E3 Port Parameters, page 5-49• Configure BER Thresholds for an STM Path, page 5-51• Configure STM-N Port Parameters, page 5-53


You can change parameters for each module:• During the preprovisioning process. Upon discovery of the equipment, the

management server downloads the preprovisioned data to the node.• After the equipment is discovered. If a piece of equipment has not been

preprovisioned when it is discovered, it arrives with default values. Change the default values on the Config tab.

Before You Configure SDH Equipment

Review this information before you start to configure SDH equipment on the TE-100 shelf.

Table 5-16 SDH Equipment Requirements



Software

Node is installed and commissioned with ITU_default in the standard parameter.



TraverseEdge 100 User Guide, Section 5: Creating TDM ServicesG.747 Services

G.747 Services The Traverse and TE-100 system supports the ITU standard G.747: Second Order Digital Multiplex Equipment operating at 6312 kbit/s and Multiplexing Three Tributaries at 2048 kbit/s. Specifically, the system can multiplex either 28 DS1 signals or 21 E1 signals into a channelized DS3 signal. The system uses this standard in the transmux application.

The following hierarchy shows E1 or DS1 payloads multiplexed into a SONET signal. Each path shows a valid source or destination for an optical transmux service.

Figure 5-23 E1 and DS1 Payloads on SONET

The following hierarchy shows E1 and DS1 payloads multiplexed into an STM signal. Each path shows a valid source or destination for an optical transmux service.

Figure 5-24 E1 and DS1 Payloads on STM






Group,” page 4-27

Table 5-16 SDH Equipment Requirements (continued)


OC-N

E1

STS

VT2

DS1

DS3

DS1

VT1.5DS3

E1

STM-N

DS1 E1

AU4

VC11 VC12VC3

DS1 E1

AU3

VC11 VC12DS3

DS1 E1

DS3

DS3

DS1 E1

DS3


Chapter 6 Configuring SDH EquipmentConfigure Interface Module SDH Parameters

Configure Interface Module SDH Parameters

Configure how E1 channels on the module map to a VC payload or multiplex into an STM path.

Important: Changing these parameters on the interface card is service affecting. You cannot complete this procedure if the card is carrying traffic (if there are services activated).

Table 5-17 Change Interface Module SDH Parameters

Step Procedure

1 Review the information in the topic: Before You Configure SDH Equipment, page 5-43.

2 In Shelf View, click the interface module, then click the Config tab to display the Card Configuration screen.

Figure 5-25 Change Interface Module SDH Parameters


4 Set the multiplex structure for LO VC3 paths on this shelf.

VC3 Mode. This parameter is available only when the node is commissioned in ITU mode. Select the multiplex structure for VC3 paths for the entire shelf. All TE-100 nodes in the same ring must have the same value in this parameter.• TU3/VC3 (default). Sets the multiplex structure for VC3 paths to

AUG-1/AU-4/TU-3/VC-3.• AU3/VC3. Set the multiplex structure for VC3 paths to

AUG-1/AU-3/VC-3.

2

3

4 5

6 7


TraverseEdge 100 User Guide, Section 5: Creating TDM ServicesConfigure Interface Module SDH Parameters

5 Select how the E1 channels on this module are multiplexed into a TU container. From the E1 Mapping list:• Select DS3 to multiplex the signal into a channelized DS3 then mapped

into a VC-3/TU-3 for transport.• Select VC12 to multiplex the E1 channels into a VC12-mapped TU-12.

6 If required, switch all E3 ports on this shelf to DS3 mode. a. Lock the administrative state of the module. Click the lock icon in the

bottom left of the screen and then click Apply.b. Click the Switch to DS3 button.

7 Click Apply to save the changes to the interface module.

8 The Change Interface Module SDH Parameters procedure is complete. • For detailed LCAS information, see Section 2—Creating Ethernet

Services, Chapter 4—“Link Capacity Adjustment Scheme,” page 2-37.• For detailed MAC Address information, see Section 6—Creating

Ethernet Services, Chapter 2—“Configuring Ethernet Equipment,” View or Edit the MAC Address Table, page 6-9.

Table 5-17 Change Interface Module SDH Parameters (continued)

Step Procedure


Chapter 6 Configuring SDH EquipmentConfigure E1 Port Parameters

Configure E1 Port Parameters

Use this procedure to customize behavior of an E1 port.

Table 5-18 Configure E1 Ports

Step Procedure

1 Review the information in Before You Configure SDH Equipment, page 5-43.

2 In Shelf View, click an E1 port on the tributary card.

3 Click the Config tab to display the E1 Port Configuration screen.

Figure 5-26 E1 Port Configuration Screen

4

76

5

3


TraverseEdge 100 User Guide, Section 5: Creating TDM ServicesConfigure E1 Port Parameters

4 Change any of the following parameters for the E1 interface:

Line Format: Select one of the following:• Basic Frame: Select so the timing interface detects and generates the

Basic frame format per ITU-T Rec G.704/2.3 and G.706/4.1.2. This format does not support the SSM.

• Multi-Frame (default): Select so the timing interface detects and generates CRC-4 Multi-frame format per ITU-T Rec G.706/4.2. This format supports the SSM.

• Unframed: Select so that, upon detecting an LOF condition (in Unframed mode), the system does not:– Raise an LOF alarm– Propagate an AIS– Insert an RAI– Count OOF and SEF framing errors

Line Build Out: Displays the distance from the subscriber interface to the physical port on the node. Select one of the following:• Short Haul (default)• Gain Mode

AIS Mask (Alarm Indication Signal Mask): Select one of the following:• Yes: Mask AIS alarm for unused direction.• No (default): Do not mask AIS alarm for any direction.

AIS Insertion: Select one of the following:• Enabled (default): Generate an AIS when VC12 signal is degraded • Disabled: Do not generate an AIS when VC12 signal is degraded



PM Template: Select from the list of defined performance monitoring templates (of type e1_ptp_pm). Default value is default, which contains default thresholds for performance monitoring parameters and thresholds for DS1 ports.

Alarm Profile: Select from the list of defined alarm profiles (of type ds1_ptp) to customize service-affecting and non-service-affecting alarm severities. Default is the default e1_ptp alarm profile.

6 Click the Lock icon to unlock the port. The port must be unlocked to apply changes and monitor performance by generating alarms. The Lock icon is located in the lower left corner of the screen.


8 The Configure E1 Ports procedure is complete.

Table 5-18 Configure E1 Ports (continued)

Step Procedure


Chapter 6 Configuring SDH EquipmentConfigure E3 Port Parameters

Configure E3 Port Parameters

Use this procedure to customize behavior of an E3-CC port.

Table 5-19 Configure E3CC Port

Step Procedure


2 In Shelf View, click an E3-CC port on the tributary card.

3 Click the Config tab to display the E3 Port Configuration screen.

Figure 5-27 E3 Port Configuration Screen


Line Format: Select one of the following:• G.751 (default)• G.832• Unframed: Upon detecting an LOF condition (in Unframed mode), the

system does not:– Raise an LOF alarm– Propagate an AIS– Insert an RAI– Count OOF and SEF framing errors

RDI: Enables the system to send an RDI (remote defect indicator) signal as soon as it cannot identify valid framing or when it determines it is receiving an AIS.• Select Enabled to allow the system to send an RDI signal.• Select Disabled so the system does not send an RDI.

Line Build Out: Select the length of cable between the node and the intermediate patch panel:• 0–225 ft (default)• 255–450 ft

AIS Mask (Alarm Indication Signal Mask): Select one of the following:• Yes: Mask AIS/alarm for unused direction.• No (default): Do not mask AIS/alarm for any direction.

4

76

5

3


TraverseEdge 100 User Guide, Section 5: Creating TDM ServicesConfigure E3 Port Parameters




PM Template: Select from the list of defined performance monitoring templates (of type e3_ptp_pm). Default value is default, which contains default thresholds for performance monitoring parameters and thresholds for DS1 ports.

Alarm Profile: Select from the list of defined alarm profiles (of type ds_ptp) to customize service-affecting and non-service-affecting alarm severities. Default is the default e3_ptp alarm profile.


7 Click Apply.

8 The Configure E3CC Port procedure is complete.

Table 5-19 Configure E3CC Port (continued)

Step Procedure


Chapter 6 Configuring SDH EquipmentConfigure BER Thresholds for an STM Path

Configure BER Thresholds for an STM Path

Configure the thresholds for the path-level signal failed bit error ratio (SFBER) and signal degrade bit error ratio (SDBER) on the system card card (module). When the thresholds are exceeded, the system raises an SFBER-P or SDBER-P alarm.

Table 5-20 Configure BER Thresholds for an STM Path

Step Procedure

1 Review the information in the topic Before You Configure SDH Equipment, page 5-43.

2 In Shelf View, click the system card, then click the Config tab to display the Card Configuration screen.

These parameters appear depending on the speed of the STM interface and apply to all the paths on the card.


4 Set the transmission quality (bit error ratio) of failed signals in the High Order path. When the error rate crosses the value specified in this parameter, the system raises a signal failed bit error rate (BERSF-P) alarm.

Select one of the following values:• 1E-3 (default for VC-3 SF BER): Value equals 1 x 10-3

• 1E-4 (default for VC-4 and VC-4-4c SF BER): Value equals 1 x 10-4

• 1E-5: Value equals 1 x 10-5

2

4 5

6

3


TraverseEdge 100 User Guide, Section 5: Creating TDM ServicesConfigure BER Thresholds for an STM Path

5 Set the transmission quality (bit error ratio) of degraded signals (SD) in the High Order path. When the error rate crosses the value specified in this parameter, the system raises a signal degraded bit error rate (BERSD-P) alarm. Select one of the following values:• 1E-4. Value equals 1 x 10-4


• 1E-6 (default for VC-3 SD BER). Value equals 1 x 10-6

• 1E-7 (default for VC-4 and VC-4-4c SD BER). Value equals 1 x 10-7





7 The Configure BER Thresholds for an STM Path procedure is complete.

Table 5-20 Configure BER Thresholds for an STM Path (continued)

Step Procedure


Chapter 6 Configuring SDH EquipmentConfigure STM-N Port Parameters

Configure STM-N Port Parameters

Use this procedure to customize behavior of a STM port.

Table 5-21 Configure STM-N Ports

Step Procedure


2 In Shelf View, click a STM-N port in slot 0

Figure 5-28 SDH Port Configuration Screen

STM port

3

4

5

6

1110

7 8

9


TraverseEdge 100 User Guide, Section 5: Creating TDM ServicesConfigure STM-N Port Parameters

3 Change any one of the following parameters for the STM interface:

AIS Mask (Alarm Indication Signal Mask):• Yes: Mask AIS/alarm for unused direction.• No (default): Do not mask AIS/alarm for any direction.

Sync Source: Indicates if this port is used to synchronize status. Valid values are:• Primary: Indicates this port is the primary sync source.• Secondary: Indicates this port is the secondary sync source.• Not used: Indicates this port is not used as the sync source.

SFBER: Measures the transmission quality (bit error ratio) of failed signals on the link. When the error rate crosses the value specified in this parameter, the system raises a signal failed bit error rate (BERSF-L) alarm and performs a protection switch. Select one of the following values: • 1E-3 (default): Value equals 1 x 10-3

• 1E-4: Value equals 1 x 10-4 • 1E-5: Value equals 1 x 10-5

Transmitter State: Select one of the following:• On (default): The laser is turned on.• Off: The laser is turned off.

Forced DUS (Do not Use for Synchronization): Select for this port to transmit the SSM (synchronization status message) DUS. This prevents the remote node that receives this signal from using the line as a timing reference.

SDBER: Measures the transmission quality (bit error ratio) of degraded signals. When the error rate crosses the value specified in this parameter, the system raises a signal degraded bit error rate (BERSD) alarm and performs a protection switch. Select one of the following values: • 1E-9. Value equals 1 x 10-9



• 1E-6 (default). Value equals 1 x 10-6


Table 5-21 Configure STM-N Ports (continued)

Step Procedure



4 Configure the automatic laser shutdown feature using the following parameters:

Trnsm Auto Shtdwn: Automatically shut down the transmit laser on optical interfaces when the system detects a receive LOS for 500 ms. The system turns the transmit laser off after detecting a receive LOS for 800 ms. The system raises the ALS alarm against the optical facility when the transmitter has been turned off automatically.• Disabled (default): The ALS feature is turned off.• Manual. The operator initiates a single laser pulse from the transmitter

for the amount of time specified in the Recovery Pulse Width parameter. To send the single laser pulse, click the Current Transmitter State button, then click Manual Restart.

• Automatic: The system turns off the transmit laser for a random time between 100 and 300 seconds. The transmit laser turns on if one of the following conditions occur:– The user manually sends a single laser pulse (Current

Transmitter State button)– If the system receives a valid signal for more than 800 ms– After the random timer expires, the system sends periodic laser

pulses from the transmitter for the amount of time specified in the Recovery Pulse Width parameter

Current Transmitter State: Click this button to display the current state of the optical transmitter. See Trnsm Auto Shtdwn parameter for details.

Rcvry Pulse Width: The system enables the transmitter for the amount of time specified in this parameter. Valid only if the value in Trnsm Auto Shtdwn is Manual or Automatic. Enter a time between 2 and 10 seconds; default is 5 seconds.


Step Procedure



5 Set the section trace formats and identifiers for this interface:

Fwd Section Trc Fmt (Forward Section Trace Format): This port transmits an access point identifier in the J0 byte of the SDH frame so that the section receiver can verify its continued connection. The valid value is 16 bytes.

Fwd Section Trace: The access point identifier transmitted in the J0 byte. Enter an alphanumeric character string.

Rev Section Trc Fmt (Reverse Section Trace Format): This port expects an access point identifier in the J0 byte of the SDH frame to verify its continued connection with the transmitter. If this port receives an incorrect identifier, the system raises an RS-TIM (Regenerator Section - Trace Identifier Mismatch alarm). The valid value is 16 bytes.

Rev Section Trace: The expected access point identifier to be received in the J0 byte. Enter an alphanumeric character string.

6 Specify if the system uses the DCC bytes to communicate with other nodes in this network.

In the Control Data parameter, select one of the following:• Enabled (default): The management system uses this interface for

management traffic.• Disabled: The management system does not use this interface for

management traffic.

7 If the system uses the DCC bytes to communicate with other nodes in this network, specify which DCC bytes are processed. You can change the value in this parameter only if the value in Control Data is Disabled.

In the Terminate DCC parameter, specify one of the following values:• Regenerator: Specifies that the interface use the D1-D3 bytes

(192 Kbps) of the first AUG-1 on this interface for management traffic.

• Multiplexer (default): Specifies that the interface use the D4-D12 bytes (576 Kbps) of the first AUG-1 on this interface for management traffic.

• Regenerator&Multiplexer: Specifies that the interface use the combined section DCC and line DCC bytes from the first, second, and third AUG-1 on the interface (2.3 Mbps) for management traffic.

• Path (TE-100 STM-1 and STM-4 interfaces only): Specifies that the interfaces uses the F2 byte (64 Kbps) of the AUG for management traffic.)


Step Procedure



8 If the value in Terminate DCC is Path, specify which path (or paths) to carry management traffic. Click the Path DCC Configuration button to display the Path DCC Configuration dialog box.

Figure 5-29 STM-4 Path DCC Configuration Dialog Box

Select the paths on the interface that you want to use to carry management traffic. The paths displayed depend on the value in the VC3 Mode parameter of the interface card (the multiplex structure for VC3 paths for the entire shelf).

Click Done and return to the Config tab on the main screen.




PM Template: Select from the list of defined performance monitoring templates (of type sdh_ptp_pm). Default value is default, which contains default thresholds for performance monitoring parameters and thresholds for STM ports.

Alarm Profile: Select from the list of defined alarm profiles (of type sdh_ptp) to customize service-affecting and non-service-affecting alarm severities. Default is the default sdh_ptp alarm profile.


Step Procedure



10 L2 Protocol: Determines the Layer 2 protocol for this port. • PPP (default): Select to make the port a point-to-point protocol. Use

PPP if this port is connected to another Traverse or TE-100 platform.• LAPD: Select to make the protocol for this port link access procedure

D-channel (LAPD). Select LAPD if this port is connected to legacy third-party ADM equipment and this node is used as an OSI DCC gateway node.

LAPD Role: Select the role of this node in the OSI DCC gateway application.• Network• User (default)

DWDM wl supp value: Indicates the DWDM wavelength supplied value.

LAPD Mode: Select the mode of this node in the OSI DCC gateway application.• AITS (Acknowledge information transfer service): Use this value if

the value in L2 Protocol is LAPD.• UITS (Unacknowledge information transfer service) (default): Select

this mode if the L2 Protocol value is PPP.

LAPD MTU: Indicates the multiple transmission unit if the value in L2 Protocol is PPP. The default is 512.

DWDM wl: Select from the list of defined wavelength frequencies.


12 Click Apply.

13 The Configure STM-N Ports procedure is complete.


Step Procedure



Chapter 7 Creating SDH Services

Introduction This chapter explains how to create the following service types in a TraverseEdge 100 (TE-100) network: • SDH. Use this service to transport synchronous traffic through the network. Also,

use this service as a regular cross-connect when creating a transport path hop-by-hop through the network.

• SDH-Endpoint. Use this service to create a termination point to multiplex low order traffic into the network. Also use this service to create a transport path hop-by-hop through the network.

This chapter includes the following topics:• Before You Create SDH Services, page 5-60• Bandwidth Requirements for SDH Services, page 5-61• Guidelines to Create SDH Services, page 5-61• Create an SDH Service, page 5-62• Create an SDH-Endpoint Service, page 5-68• Create an SDH Transport Path Hop-by-Hop, page 5-73


TraverseEdge 100 User Guide, Section 5: Creating TDM ServicesBefore You Create SDH Services

Before You Create SDH Services

Review the information in this topic before you create any SDH services.

Table 5-22 SDH Service Requirements



Software

Node is installed and commissioned with ITU_default in the standard parameter.



Protection groups are connected and configured. See Section 4—Configuring the Network:• Chapter 3—“Creating a UPSR/SNCP Protection




Source (tributary) and destination (transport) interfaces are configured correctly.

Section 5—Creating TDM Services, Chapter 6—“Configuring SDH Equipment,” page 5-43.

These procedures describe how to create a specific service and change only configurable parameters. See the TransNav Management System GUI Guide for descriptions of other fields on screen.

TransNav Management System GUI Guide, Section 2—Services, Chapter 2—“SONET Services,” page 2-19.

Provisioning model. • SDH: hop-by-hop• SDH-Endpoint: hop-by-hop

Chapter 1—“Service Creation Concepts,” Service Creation Model, page 5-2.

Review the bandwidth requirements. Bandwidth Requirements for SDH Services, page 5-61

Review the service creation guidelines. Guidelines to Create SDH Services, page 5-61


Chapter 7 Creating SDH ServicesGuidelines to Create SDH Services

Bandwidth Requirements for SDH Services

The bandwidth of the Traverse system depends on the commissioned data rate of system. The system supports up to the commissioned bandwidth in a protected or unprotected configuration.The following table specifies commissioned data rate and the supported bandwidth.

In an unprotected configuration, use a specific AUG-1 on port 1 or port 2, but not both. For example, on an unprotected STM-16 topology, use AUG-1 through AUG-8 on port 1 and AUG-9 through AUG-16 on port 2. A system commissioned with the data rate of STM-1 supports up to two AUG-1s of bandwidth.

Guidelines to Create SDH Services

Know the bandwidth requirements of the SDH services. See Bandwidth Requirements for SDH Services, page 5-61.

In ITU operation, the TE-100 shelf supports a VC3 multiplex structure to be either AU3/VC3 or TU3/VC3. That is, the shelf supports either one or the other VC3 structure, not both. The VC3 Mode parameter on the interface card controls this multiplex structure. All TE-100 nodes in the same ring must have the same value in the VC3 Mode parameter.

Table 5-23 Commissioned Data Rate and Supported SDH Bandwidth

Commissioned Data Rate Topology Bandwidth

STM-16 Protected or unprotected up to 16 AUG-1s

STM-4 Protected or unprotected up to 4 AUG-1s

STM-1 Protected up to 1 AUG-1s

Unprotected up to 2 AUG-1s

Table 5-24 Supported SDH Services

Commissioned Data Rate

VC3 Mode Parameter

SupportedServices

STM-16, STM-4, STM-1

AU3/VC3 • DS3/E3• 10/100 TX to VC3/VC4 VCAT• GbE to VC3/VC4 VCAT• E1 to VC12/VC3 or E1 to VC12/TU3/VC4• VC12 to VC4 VCAT

STM-4, STM-1 TU3/VC3 • DS3/E3• 10/100 TX to VC12/VC3/VC4 VCAT• E1 to VC12/TU3/VC4

STM-16(VC4 SNCP pro-tection only)

TU3/VC3 • DS3/E3• 10/100 TX to VC12/VC3/ VC4 VCAT• E1 to VC12/TU3/VC4• Up to 12 LO VC3 per span per the following guidelines.

Do not allocate aug-1, aug-2, aug-3, or aug-4 for any service (including pass-thru crossconnects).

Aug-5, aug-6, aug-7, and aug-8 are available for VC12/TU3/VC4, LO VC3, and HO VC4 services.

Aug-9, aug-10, aug-11, aug-12, aug-13, aug-14, aug-15, aug-16 are available for HO VC4 services only.


TraverseEdge 100 User Guide, Section 5: Creating TDM ServicesCreate an SDH Service

Create an SDH Service

Use this procedure to transport synchronous traffic through the network:

Table 5-25 Create an SDH Service

Step Procedure

1 Add the SDH service.


a. Click the Service tab.b. From the Add button menu, select SDH.c. Click Add to display the Create Service tab.

2 In the Name parameter, enter a unique name for the service. Use alphanumeric characters and spaces only. Do not use any other punctuation or special characters.


3 From the Bandwidth parameter, select the total bandwidth for the service: • VC-12• VC-3 (default)• VC-4• VC-4-4c (for STM-4 and greater interfaces only)• VC-4-16c (for STM-16 and greater interfaces only)

1a

1b

1c

23

4

5

10 12


Chapter 7 Creating SDH ServicesCreate an SDH Service




b. Navigate the tree and select the correct source endpoint. c. Click Done to close the dialog box and return to the Create Service

tab on the main screen.d. Click the Destination row in the Endpoint column.e. Navigate the tree and select the correct destination endpoint.f. Click Done to close the dialog box and return to the Create Service


Table 5-25 Create an SDH Service (continued)

Step Procedure

4a

4b

4c





In the Protection Type parameter, select one of the following options: • Unprotected (default): For services that are either unprotected, 1+1

APS/MSP protected, protected with an equipment protection group, or a 1+1 Path Protection group.


• Full: The system only creates the service if there is full protection on every transport link in the network.

• 1+1 Path Protected: If this service is protected by another service (two services model).

• UPSR Ingress: If the service is a LO VC service and is creating a bi-directional path across two interconnected SNCP rings.

6 For services that have a protection type configured, configure the following parameters:• Revertive (default is not selected): Select the check box to switch

traffic back to the original path once the failure condition no longer exists.

• WTR Time (default is 5): Specifies the amount of time (in minutes) for the system to wait before restoring traffic to the original path once the failure condition no longer exists. Specify a value between 1 and 60 minutes.

If this service is protected by a BLSR or an MS-SPRing, go to Step 7.



Step Procedure

59



7 If the endpoints of the service are on a BLSR or MS-SPRing, click the MSSP/BLSR tab and configure the following parameters: • Ring Source Node ID: Select the BLSR Node ID where the traffic on

this path enters the ring.• Ring Destination Node ID: Select the BLSR Node ID where the

traffic on this path exits the ring.

8 For services protected by another service, click the 1+1 Path Protected tab and configure the HoldOffTimer parameter. This parameter applies only if there is also a 1+1 APS/MSP protection group. Allows line protection to switch first before the path switches. If the line switches within the specified time period, the path does not switch. The hold-off timer starts when path protection detects a path failure.





Step Procedure

9



10 On the Create Service tab, click Advanced to configure more parameters of the service.


For specific definitions of these parameters, see the TransNav Management System GUI Guide, Section 6—Services, Chapter 3—“SDH Services,” Configure Advanced Parameters (Alphabetic Order), page 6-38.

To provision a VT-MUX service, continue to Step 11.

To complete the service, skip to Step 12.


Step Procedure



11 Configure the Payload Mapping parameter for VC-Mux type services if needed.


Select the desired Payload Mapping parameter type. Valid values are: For SDH services:– VC3 (default): Indicates the service endpoint on the Ethernet card

is treated as a VC-3 connection termination ports for use in EOS or EOP ports.

– VC11: Indicates the service endpoint on the Ethernet card will be treated as a set of 28 VC-11 connection termination ports for use in EOS or EOP ports.

– VC12: Indicates the service endpoint on the Ethernet card will be treated as a set of 21 VC-12 connection termination ports for use in EOS or EOP ports.

12 Click Done to return to the Create Service tab on the main screen.

The Create an SDH Service procedure is complete.

13 If this is a hop-by-hop service, click Apply to save this configuration and return to the Service tab on the main screen.

Continue to the procedure: Activate or Deactivate a Service, page 5-14.

14 If this is an end-to-end service, continue to the procedure: Configure the Path Through the Network, page 4-14.


Step Procedure


TraverseEdge 100 User Guide, Section 5: Creating TDM ServicesCreate an SDH-Endpoint Service

Pa

Create an SDH-Endpoint Service

Use an SDH Endpoint service to create a termination point to multiplex low order traffic into the network or to create a transport path hop-by-hop through the network.

Table 5-26 Create an SDH Endpoint Service

Step Procedure

1 Add the SDH Endpoint service.


a. Click the Service tab.b. From the Add button menu, select SDH Endpointc. Click Add to display the Create Service tab.

2 In the Name field, enter a unique name for the service. Use alphanumeric characters and spaces only. Do not use any other punctuation or special characters.


3 From the Bandwidth parameter, select the total bandwidth for the service: • VC-3 (Grooming) (default): This path is VC-3 bandwidth and carries

low order payloads.• VC-4 (Grooming): This path is VC-4 bandwidth and carries low order

payloads.• VC-4 (VC-3): This path is VC-4 bandwidth and carries VC-3 payloads

only.

1a

1b

1c

23

4

5

10 12

ge 5-68 Force10 Networks Release TE3.2.x

Chapter 7 Creating SDH ServicesCreate an SDH-Endpoint Service




b. Navigate the tree and select the correct source endpoint. Click Done to close the dialog box and return to the Create Service tab on the main screen.

c. Click the Destination row in the Endpoint column.d. Navigate the tree and select the correct destination endpoint.e. Click Done to close the dialog box and return to the Create Service


Table 5-26 Create an SDH Endpoint Service (continued)

Step Procedure

4a4b

4c





In the Protection Group Type field, select one of the following options: • Unprotected (default): Select this option for services that are

unprotected, 1+1 APS/MSP protected, protected with an equipment protection group, or a 1+1 Path Protection group.


• Full: The system only creates the service if there is full protection on every transport link in the network.

• 1+1 Path Protected: Select this option if this service is protected by another service (two services model).

• UPSR Ingress: Select this service if the service is a LO VC service and is creating a bi-directional path across two interconnected SNCP rings.

6 For services that have a protection type configured, configure the following parameters:• Revertive (default is not selected): Select the checkbox to switch

traffic back to the original path once the failure condition no longer exists.

• WTR Time: Specifies the amount of time (in minutes) for the system to wait before restoring traffic to the original path once the failure condition no longer exists. Specify a value between 1 and 60 minutes; default is 5.

If this service is protected by a BLSR or an MS-SPRing, go to Step 7.



Step Procedure

510


Chapter 7 Creating SDH ServicesCreate an SDH-Endpoint Service

7 If the endpoints of the service are on a BLSR or MS-SPRing, click the MS-SP/BLSR tab and configure the following parameters: • Ring Source Node ID: Select the BLSR Node ID where the traffic on

this path enters the ring.• Ring Destination Node ID: Select the BLSR Node ID where the

traffic on this path exits the ring.

8 For services protected by another service, click the 1+1 Path Protected tab and configure the HoldOffTimer parameter. This parameter applies only if there is also a 1+1 APS/MSP protection group. Allows line protection to switch before the path switches. If the line switches within the specified time period, the path does not switch. The hold-off timer starts when path protection detects a path failure.





Step Procedure

10



10 On the Create Service tab, click Advanced to configure more parameters of the service.


a. For specific definitions of these parameters, see the TransNav Management System GUI Guide, Section 6—Services, Chapter 3—“SDH Services,” Configure Advanced Parameters (Alphabetic Order), page 6-38.

b. Click Done to return to the Create Service tab on the main screen.

11 The Create an SDH Endpoint Service procedure is complete.

Continue to the procedure Activate or Deactivate a Service, page 16.


Step Procedure


Chapter 7 Creating SDH ServicesCreate an SDH Transport Path Hop-by-Hop

Create an SDH Transport Path Hop-by-Hop

Use an endpoint service in conjunction with an SDH service to create a transport path hop-by-hop through the network. If you create a transport path hop-by-hop through the network, you can add and drop traffic or monitor performance and alarms at each hop. If you create a transport path end-to-end (tunnel service), you can only monitor each end.

The bandwidth of each service must be the same throughout the path.

Table 5-27 Create a Transport Path Hop-by-Hop

Step Procedure

1 Create an endpoint service at the node that adds the traffic. See the procedure Create an SDH Endpoint or SDH Tunnel Service, page 4-64.

2 Create an endpoint service at the node that drops the traffic. See the procedure Create an SDH Endpoint or SDH Tunnel Service, page 4-64.

3 At each intermediate node:

To be able to add traffic onto the transport path in the future from this node, create an SDH Endpoint service on each trunk card. See the procedure Create an SDH Endpoint or SDH Tunnel Service, page 4-64.

To simply pass traffic through this node, create an SDH service between the ingress and egress trunk cards. See the procedure Create an SDH Service, page 5-62.

4 The Create a Transport Path Hop-by-Hop procedure is complete.


TraverseEdge 100 User Guide, Section 5: Creating TDM ServicesCreate an SDH Transport Path Hop-by-Hop


SECTION 6 CREATING ETHERNET SERVICESSECTION 6CREATING ETHERNET SERVICES

Contents

Chapter 1Ethernet Services Overview

Ethernet Configuration Process Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2Ethernet Configuration Procedure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3Before You Configure Ethernet Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4

Chapter 2Configuring Ethernet Equipment

Before You Configure Ethernet Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6Change Ethernet Parameters on the Interface Module. . . . . . . . . . . . . . . . . . 6-7View or Edit the MAC Address Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-9Guidelines to Configure Ethernet Ports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-11

Jumbo frame support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-11VLAN Tagging on Ethernet Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-11VLAN Tagging Guidelines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-13Configure Ethernet Ports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-13Configure Advanced Parameters of Ethernet Ports . . . . . . . . . . . . . . . . . . . . 6-15Auto Negotiation for Ethernet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-18Configure Auto-Negotiation for Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-19View the Negotiated Status of the Link for Ethernet . . . . . . . . . . . . . . . . . . . . 6-23

Chapter 3Ethernet Over SONET or SDH (EOS)

EOS Definition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-25EOS Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-25Virtual Concatenation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-26Guidelines to Configure EOS Ports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-26

EOS Port Members (SONET or SDH Services) . . . . . . . . . . . . . . . . . . . 6-26Virtual Concatenation (VCAT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-27EOS Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-27

Example of EOS Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-29Before You Configure EOS Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-30Configure Ethernet Transport Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-30


TraverseEdge 100 User Guide, Section 6 Creating Ethernet Services

Configure EOS Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-31

Chapter 4Link Capacity Adjustment Scheme

LCAS Operation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-38Failed or Deleted Members on EOS Ports. . . . . . . . . . . . . . . . . . . . . . . . 6-38Restored or Added Members on EOS ports . . . . . . . . . . . . . . . . . . . . . . 6-38Failed or Deleted Members on EOP Ports. . . . . . . . . . . . . . . . . . . . . . . . 6-39

LCAS and Protection Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-40Asymmetric LCAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-40LCAS Interworking. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-41Before You Begin. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-42Guidelines to Configure LCAS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-42Configure LCAS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-43

Chapter 5Rapid Spanning Tree Protocol

Supported RSTP Topologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-50RSTP Bridge Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-51RSTP Port Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-52Guidelines to Configure RSTP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-53Before You Begin. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-54Configure RSTP on an EOS Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-55View RSTP Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-57

Chapter 6Ethernet Services

Ethernet Services Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-61Line Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-62Link Integrity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-63Bridge Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-64

Adding and Removing Endpoints to a Bridge Service . . . . . . . . . . . . . . . 6-64Aggregated Bridge Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-65

Aggregation Bridge Service with an Active/Standby CPE . . . . . . . . . . . . 6-65Ethernet Services and VLAN Tagging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-66Supported VLAN Tagging and Ethernet Service Combinations . . . . . . . . . . . 6-66Reserved VLAN IDs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-67Configurable VLAN IDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-68Guidelines to Configure Ethernet Services . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-69

Line Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-69Bridge Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-69Aggregation Bridge Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-69



Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-70Configure Ethernet Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-71

Chapter 7Ethernet Traffic Management on the TE-100

Ingress Traffic Flow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-76Egress Traffic Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-77Ethernet Traffic Management Description. . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-78Pause Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-79

On Sending PAUSE frames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-79On Receiving PAUSE Frames. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-80

Strict-Port Policing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-80Policing Algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-80Configure Strict-Port Policing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-82Class of Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-82Classifier Template Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-83Create TE-100 Classifier Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-84Queuing Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-85FIFO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-85Priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-86Weighted Fair Queuing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-86Marking Packets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-87




SECTION 6CREATING ETHERNET SERVICES

Chapter 1 Ethernet Services Overview

Introduction This chapter contains the following topics to create Ethernet services in a TraverseEdge 100 (TE-100) network:• Ethernet Configuration Process Flow, page 6-2• Ethernet Configuration Procedure, page 6-3• Before You Configure Ethernet Services, page 6-4


TraverseEdge 100 User Guide, Section 6: Creating Ethernet ServicesEthernet Configuration Process Flow

Ethernet Configuration Process Flow

Use these flowchart as a guideline to configure Ethernet in a TE-100 system.

Figure 6-1 Ethernet Provisioning Flow Chart

Start:The equipment is installed and

connected

Optionaly, configure EOS features:LCASRSTP

Create Ethernet Services

Configure Ethernet TrafficManagement

End

Optionally configure Ethernet features:Auto-Negotiation

Configure optical and Ethernetequipment

(module and port parameters)

Create Ethernet transport services(use SONET/SDH services with EOS

endpoints in slot 3)

Create EOS ports


Chapter 1 Ethernet Services OverviewEthernet Configuration Procedure

Ethernet Configuration Procedure

Use this procedure as a guideline to configure Ethernet services on a TE-100 system.

Table 6-1 TE-100 Network Configuration Process and References


1 The equipment is installed and connected according to the network plan.

Section 3—Installation and Configuration, page 3-1

Section 4—Configuring the Network, Chapter 1—“Configuring the Network,” page 4-1

2 Configure optical equipment and protection groups according to the network plan.




Group,” page 4-27

3 Configure Ethernet equipment. Section 6—Creating Ethernet Services, Chapter 2—“Configuring Ethernet Equipment,” page 6-5

4 Optionally, configure Ethernet features

Section 6—Creating Ethernet Services, Chapter 2—“Configuring Ethernet Equipment,” page 6-5

5 Create and activate Ethernet transport services.

Section 6—Creating Ethernet Services, Chapter 3—“Ethernet Over SONET or SDH (EOS),” EOS Definition, page 6-25

6 Create EOS ports. Section 6—Creating Ethernet Services, Chapter 3—“Ethernet Over SONET or SDH (EOS),” EOS Definition, page 6-25

7 Optionally, configure EOS features.

Section 2—Creating Ethernet Services, Chapter 4—“Link Capacity Adjustment Scheme,” page 2-37

8 Configure Ethernet Services. Section 6—Creating Ethernet Services, Chapter 6—“Ethernet Services,” page 6-57

9 Configure Ethernet Traffic Management.

Section 6—Configuring Ethernet, Chapter 7—“Ethernet Traffic Management on the TE-100,” page 6-71


TraverseEdge 100 User Guide, Section 6: Creating Ethernet ServicesBefore You Configure Ethernet Services

Before You Configure Ethernet Services

Review these requirements before you configure Ethernet services.

Table 6-2 Ethernet Configuration Requirements


Hardware

TE-100 shelf.

Software

Node is installed and commissioned. Section 3—Installation and Configuration, Chapter 10—“Node Start-up and Initial Configuration,” page 3-69


Protection groups are connected and configured. See Section 4—Configuring the Network:• Chapter 3—“Creating a UPSR/SNCP Protection




Equipment is configured.

Guidelines

Bandwidth requirements • Section 2—Platform Specifications, Chapter 3—“Ethernet Ports Specifications,” Gigabit Ethernet Ports, page 2-17

• Section 2—Platform Specifications, Chapter 3—“Ethernet Ports Specifications,” Fast Ethernet Ports, page 2-19



Chapter 2 Configuring Ethernet Equipment

Introduction This chapter explains the following information for Ethernet equipment on the TraverseEdge (TE-100):• Before You Configure Ethernet Equipment, page 6-6• Change Ethernet Parameters on the Interface Module, page 6-7• View or Edit the MAC Address Table, page 6-9• Guidelines to Configure Ethernet Ports, page 6-11.• VLAN Tagging on Ethernet Ports, page 6-11• VLAN Tagging Guidelines, page 6-13• Configure Ethernet Ports, page 6-13• Configure Advanced Parameters of Ethernet Ports, page 6-15• Auto Negotiation for Ethernet, page 6-18• Configure Auto- Negotiation for Ethernet, page 6-19• View the Negotiated Status of the Link for Ethernet, page 6-23



TraverseEdge 100 User Guide, Section 6: Creating Ethernet ServicesBefore You Configure Ethernet Equipment

Before You Configure Ethernet Equipment

Review this information before you start to configure Ethernet equipment on the TE-100 shelf.

Table 6-3 Ethernet Equipment Requirements



Software

Node is installed and commissioned. Section 3—Installation and Configuration, Chapter 10—“Node Start-up and Initial Configuration,” page 3-69.






Group,” page 4-27


Chapter 2 Configuring Ethernet EquipmentChange Ethernet Parameters on the Interface Module

Change Ethernet Parameters on the Interface Module

There are configurable parameters on the interface module for Ethernet services. Use this procedure to customize behavior of the equipment.

Table 6-4 Change Interface Module Parameters

Step Procedure

1 In Shelf View, click the interface module.

2 Click the Config tab to display the Card Configuration screen.

Figure 6-2 Interface Card, Config Tab


2

4

5 6

3


TraverseEdge 100 User Guide, Section 6: Creating Ethernet ServicesChange Ethernet Parameters on the Interface Module

4 Alternate VLAN Ethertype: selects the second Ethertype value (in addition to the standard 0x8100) that the system uses to recognize VLAN tags in incoming packets from all ports on this card. If a port has the Insert Alternate VLAN Ethertype parameter Enabled, then the system uses the value specified in this parameter when a VLAN swap or add operation is performed on a packet being sent out on that port. • 0x8100 (default). The system uses this standard Ethertype value. • 0x9100 The system also accepts packets with the Ethertype value of

0x9100 in the VLAN tag. Use this value only if one or more ports on this card are connected to devices that require this alternative value. In addition, enable the Insert Alternate VLAN Ethertype parameter on those ports.

FE Insert Alternate VLAN Ethertype: If this parameter is enabled, then all of the ETH100TX ports will use the Alternate VLAN Ethertype value when a VLAN swap or add operation is performed on a packet being sent out an ETH100TX port. Enable this parameter if all the ETH100TX ports on this shelf are connected to devices that require this alternative value.

FE EOS Insert Alternate VLAN Ethertype: If this parameter is enabled, then all of the FE EOS ports will use the Alternate VLAN Ethertype value when a VLAN swap or add operation is performed on a packet being sent out an ETH100TX port. Enable this parameter if all the ETH100TX ports on this shelf are connected to devices that require this alternative value.

5 Whenever the system creates a new VLAN tag (either a Customer tag or a Service tag), configure the 3-bit value to insert in the Priority (802.1p) field for packets exiting each class of service.

Egress Priority CoS1. Enter a priority value of 0, 1, 2, 3, 4, 5, 6, or 7. By industry standard: 7 means highest priority, 0 means lowest priority.




Table 6-4 Change Interface Module Parameters (continued)

Step Procedure


Chapter 2 Configuring Ethernet EquipmentView or Edit the MAC Address Table

View or Edit the MAC Address Table

MAC learning is the process the system uses to associate a MAC address with a specific port, based on having received a packet at that port with that MAC address as its Source MAC address. Future packets addressed to that MAC address are forwarded to that single port instead of being “flooded” to all ports. Learning, re-learning, aging, and clearing are all standard MAC table functions.

MAC forwarding in a bridge service follows well-documented rules for determining the set of output ports for a packet based on the destination MAC address in its header.

Use this procedure to view or modify the MAC Address table in the system.

Table 6-5 View or Edit the MAC Address Table

Step Procedure

1 In Shelf View, click Tributary card, then click the Config tab.

2 Click the MAC Address table button to display the MAC Address Queries dialog box. The MAC Address Queries dialog box allows a user to query all MAC addresses in the system.

Figure 6-3 MAC Address Queries Dialog Box


TraverseEdge 100 User Guide, Section 6: Creating Ethernet ServicesView or Edit the MAC Address Table

3 Filter the MAC addresses using all or any of the following options:

MAC Address:• ALL (default) • Define: Enter a specific MAC address

Service: Select a service identification number (SID). The valid values are: • ALL (default): Query all services• Define: Enter a specific SID

Port Id: Select the port number from the drop-down menu. Available when the Port Type value is EOS, ETH, GBE; default is ALL.

Port Type: Select one of the following values to filter the list based on the type of port:• None (default)• ETH: ETH100TX interfaces• GBE: GBE ports• 10GBE: 10GbE ports• EOS: EOS ports

4 Count: Click to count all the MAC addresses learned on this card.

5 Delete All: Click to remove all MAC addresses recorded in the forwarding table.

6 Query: Click to query the MAC addresses if any of the filters were used in Step 3.

7 Delete: Delete the MAC addresses highlighted in the MAC Address list.

8 Close: Close the dialog box and return to the main screen.

9 The View or Edit the MAC Address Table procedure is complete.

Table 6-5 View or Edit the MAC Address Table (continued)

Step Procedure


Chapter 2 Configuring Ethernet EquipmentVLAN Tagging on Ethernet Ports

Guidelines to Configure Ethernet Ports

Jumbo frame support

Jumbo frame support on the TE-100 system is controlled on the egress port. That is, the egress port controls whether or not the system transmits jumbo frame sizes. The following guidelines summarize jumbo frame support on the TE-100 system:• The physical GBE port is configurable to receive and transmit jumbo frame sizes

up to 9600 bytes. • The GbE EOS port is not configurable and can receive and transmit jumbo frames

up to 9600 bytes.• FE ports (both line and EOS) do not support jumbo frames.

On the TE-100 system, jumbo frame support is an egress control. The system accepts all incoming frames on any port, regardless of frame size, but will drop the packet based on the jumbo setting of the egress port. The egress frame length has limitations when jumbo frame support is disabled on the port. The limit is different dependent on whether or not the packet is tagged, 1518 is the untagged limit, 1526 is the limit for tagged. This table summarizes TE-100 support for jumbo frames.

VLAN Tagging on Ethernet Ports

The Traverse Ethernet provisioning model supports multiple services sharing the same Ethernet port or Ethernet-over-SONET/SDH (EOS) port by using the Tagging parameter on the Config tab. The values in the Tagging parameter can be one of the following values: • Port-based. Every packet on this port belongs to the same service, regardless of

whether or not the packet has a VLAN tag.• Customer-tagged. Every packet on this port is assumed to have a VLAN tag that

identifies its service in the customer network. Customer-tagged ports use the customer VLAN tag and allows the service provider to have multiple Ethernet streams sharing the same port (i.e.: separate customer VLAN IDs on same port).

• Service-tagged. Every packet on this port is assumed to have a service provider VLAN tag that identifies its Ethernet service within the service provider network. Service provider VLAN tags are used within the service provider network and are

Table 6-6 Jumbo Frame Support

Type of Port

Port Configuration for Jumbo Frames

Maximum frame size that can be RECEIVED

on the port

Maximum frame size that can be

TRANSMITTED on the port

FE Not configurable Up to 9600 bytes 1518 bytes untagged1526 bytes tagged

FE EOS Not configurable Up to 9600 bytes 1518 bytes untagged1526 bytes tagged

GbE Enabled (default) Up to 9600 bytes Up to 9600 bytes

Disabled Up to 9600 bytes 1518 bytes untagged1526 bytes tagged

GbE EOS Not configurable Up to 9600 bytes Up to 9600 bytes


TraverseEdge 100 User Guide, Section 6: Creating Ethernet ServicesVLAN Tagging on Ethernet Ports

never used on customer-facing ports. The Service tag may be a double-tag if the underlying packet already has a Customer tag. The service provider VLAN tag carries packet class of service used within the service provider network.

• Untagged. Every packet on this port belongs to the same service and no packet has a VLAN tag.

When ports with different Tagging types are combined in the same service, the system performs some VLAN tag manipulation – adding or removing tags – as packets are forwarded among service ports. This table summarizes system behavior between incoming packets (ingress) and outgoing packets (egress) based on the Tagging parameter.

See Chapter 6—“Ethernet Services,” Ethernet Services and VLAN Tagging, page 6-62 for more information on VLAN tagging and Ethernet services.

Table 6-7 VLAN Tag Modification

Ingress PortEgress Port

Port-Based Untagged Customer-Tagged Service-Tagged

Port-Based No change. Not supported. Not supported. Add service tag. (Line and Agg Bridge only.)

Untagged Not supported. No change. Add customer tag. Add service tag.

Customer-Tagged Not supported. Remove customer tag.

No change. Add service tag. (Line and Agg Bridge only.)

Service-Tagged Remove service tag. Remove service tag. Remove service tag. No change.


Chapter 2 Configuring Ethernet EquipmentConfigure Ethernet Ports

VLAN Tagging Guidelines

You cannot change the Tagging parameter of a port if there are one or more services activated on that port.

The TE-100 Ethernet services model does not support the following combinations of values in the Tagging parameter on the ingress and egress ports:• Any service using Port-based and Untagged.• Any service using Port-based and Customer-tagged.• Bridge services using Port-based and Service-tagged.• Bridge service using Customer-tagged and Service-tagged.

A port using Port-based tagging can only have one Ethernet service using that port.

A port using Customer-tagged or Service-tagged tagging can have more than one Ethernet service using that port.

Configure Ethernet Ports

Use this procedure to customize behavior of an Ethernet port.

Table 6-8 Configure Ethernet Ports

Step Procedure

1 Review the information in Before You Configure Ethernet Equipment, page 6-6.

2 In Shelf View, click an Ethernet port.

3 Click the Config tab to display the Ethernet Port Configuration screen.

Figure 6-4 Ethernet TX Port Configuration Screen

For Auto-Negotiation parameters, see Configure Auto- Negotiation for Ethernet, page 6-19.

4 Jumbo Frame Supt (GBE ports only): Indicates whether this port can transmit jumbo frames. Select one of the following:• Enabled (default): Jumbo frame can be transmitted from this GBE

port.• Disabled: Jumbo frame support is disabled. No jumbo frames can be

transmitted from this port.

57

64

8


TraverseEdge 100 User Guide, Section 6: Creating Ethernet ServicesConfigure Ethernet Ports

5 Transmitter State (GBE ports only): Determines if the laser on a GBE port is turned on or off. • On (default). The laser is on.• Off. Select Off to turn off the laser.

6 Configure the Tagging parameter for this port:• Port-based. Every packet on this port belongs to the same service,

regardless of whether or not the packet has a VLAN tag.• Customer-tagged. Every packet on this port is assumed to have a

VLAN tag that identifies its service in the customer network. Customer-tagged ports use the customer VLAN tag and allows the service provider to have multiple Ethernet streams sharing the same port (i.e.: separate customer VLAN IDs on same port).

• Service-tagged. Every packet on this port is assumed to have a service provider VLAN tag that identifies its Ethernet service within the service provider network. Service provider VLAN tags are used within the service provider network and are never used on customer-facing ports. The Service tag may be a double-tag if the underlying packet already has a Customer tag. The service provider VLAN tag carries packet class of service used within the service provider network.

• Untagged. Every packet on this port belongs to the same service and no packet has a VLAN tag.

7 Change any of the following general parameters for the interface:• Customer: Select from the list of defined customers. • Customer Tag: Enter an alphanumeric character string to identify the

port to a customer.• PM Template: Select from the list of defined performance monitoring

templates (of type ethernet_ptp_pm). Default value is default, which contains default thresholds for performance monitoring parameters and thresholds for Ethernet ports.

• Alarm Profile: Select from the list of defined alarm profiles (of type ethernet_ptp) to customize service-affecting and non-service-affecting alarm severities. Default is the default ethernet_ptp alarm profile.

8 Click the Lock icon , located in the lower left corner of the screen, to unlock the port and be able to monitor potential problems.


10 The Configure Ethernet Ports procedure is complete.

Continue to the next procedure: Table 6-9, “Configure Advanced Parameters for Ethernet Ports,” on page<Level2,Level1Appendix2>-15.

Table 6-8 Configure Ethernet Ports (continued)

Step Procedure


Chapter 2 Configuring Ethernet EquipmentConfigure Advanced Parameters of Ethernet Ports

Configure Advanced Parameters of Ethernet Ports

Use this procedure to configure advanced parameters for Ethernet ports:

Table 6-9 Configure Advanced Parameters for Ethernet Ports

Step Procedure

1 Complete the procedure: Configure Ethernet Ports, page 6-13.

2 In Shelf View, click an Ethernet port, click the Config tab, then click the Advanced button at the bottom of the screen.

Figure 6-5 Ethernet TX Port Configuration Screen

3 The Advanced <Eth100Tx or GbE> Port Configuration dialog box appears.

Figure 6-6 Advanced <Eth100TX or GbE> Port Configuration

The parameters in this dialog box appear depending on the type of port you are configuring.

To configure what the system is advertising for auto-negotiation parameters, see Table 6-10 Configure Auto-negotiation, page 6-19.

2


TraverseEdge 100 User Guide, Section 6: Creating Ethernet ServicesConfigure Advanced Parameters of Ethernet Ports

4 Insert Alternate VLAN Ethertype: If this parameter is enabled, then all of the GbE ports will use the Alternate VLAN Ethertype value when a VLAN swap or add operation is performed on a packet being sent out an GbE port. Enable this parameter if this port is connected to devices that require this alternative value.

5 In the Max Info Rate (Mbps) parameter, specify the maximum ingress data rate (in Mbps) allowed for this port.

If the PAUSE feature is enabled for this port, the system sends a PAUSE frame when the ingress rate hits the rate specified in this parameter. The link partner should limit its rate of transmission to the value specified in this parameter.

If the PAUSE feature is disabled for this port, or if the link partner does not respond properly to the PAUSE frame, then the link partner's transmission may exceed MIR. The incoming packets above this rate combined with the MIR Burst Size are discarded.

MIR Burst Size (Kbytes). The size (in KB) that limits the maximum number of bytes available for a burst of ingress frames to conform to MIR. Use this parameter in together with the Max Info Rate (Mbps) parameter as a policer for incoming traffic on this port.

Enter a value in Kbps between 2 and 1,000 in increments of 1 Kbyte. The default value is 64 Kbytes.

6 Classifier Template. Select a classifier for this port. See Chapter 7—“Ethernet Traffic Management on the TE-100,” Class of Service, page 6-78 for more information on classifiers.

7 Default Ingress Priority. Use the value to assign a class of service to untagged packets that arrive on this port. Enter a priority value of 0, 1, 2, 3, 4, 5, 6, or 7. By industry standard: 7 means highest priority, 0 means lowest priority.

Table 6-9 Configure Advanced Parameters for Ethernet Ports (continued)

Step Procedure


Chapter 2 Configuring Ethernet EquipmentConfigure Advanced Parameters of Ethernet Ports

8 For GBE ports, in the Queuing Policy parameter, specify how the queues are managed. Select one of the following values: • FIFO (default). First-in-first-out. Select this queuing policy to

schedule all packets for transmission based on the FIFO algorithm. All traffic uses CoS1. Optionally, configure whether shaping should be employed using the FIFO Shaping Enable and the FIFO Shape Rate parameters. Go to Step 9.

• Priority. Select this queuing policy to schedule all packets for transmission based on strict priority, using three classes of service. There are three priorities: Highest priority traffic uses CoS1, medium priority traffic uses CoS2, and low priority traffic uses CoS3.

• WFQ. Weighted fair queuing. Select this queuing policy to guarantee a specific amount of the port’s bandwidth when there is congestion on the port. WFQ uses three classes of service and the guarantees are specified as weights. If the value in this parameter is WFQ, specify the weights in the three WFQ CoS weight {1 | 2 | 3} parameters. Go to Step 10.

9 Configure the shaping policy for this port: • Shape Enable. Specify if the system will use the number in the

Shaping Rate parameter to shape the traffic being transmitted onto the port.

• Shaping Rate. If Shaping Rate is enabled, specify a number between 1 and 1000 Mbps.

10 If WFQ is the value in the Queuing Policy parameter, configure the following parameters:• WFQ CoS 1 Weight. Weighted queuing policy of CoS1. Enter a

number between 1 and 100 to determine the proportion of bandwidth on this port for CoS1. The default value is 0 which means packets with the CoS1 have no preference in relation to the other classes of service.

• WFQ CoS 2 Weight. Weighted queuing policy of CoS2. Enter a number between 1 and 100 to determine the proportion of bandwidth on this port for CoS2. The default value is 0 which means packets with the CoS2 have no preference in relation to the other classes of service.

• WFQ CoS 3 Weight. Weighted queuing policy of CoS3. Enter a number between 1 and 100 to determine the proportion of bandwidth on this port for CoS3. The default value is 0 which means packets with the CoS3 have no preference in relation to the other classes of service.

11 Click Done to close the Advanced Parameters dialog box and return to the main screen.

12 Click the Lock icon , located in the lower left corner of the screen, to unlock the port and be able to monitor potential problems.


Step Procedure


TraverseEdge 100 User Guide, Section 6: Creating Ethernet ServicesAuto Negotiation for Ethernet

Auto Negotiation for Ethernet

Auto-negotiation is a process described in IEEE standard 802.3 that allows two devices on an Ethernet segment (link partners) to determine mutually agreeable settings for speed, duplex, and pause flow control.

When auto-negotiation is enabled for a port, the system initiates auto-negotiation whenever:• the port receives a signal when there had previously been no signal.• a link partner initiates auto-negotiation.• the operator makes any change to the advertisement parameters for the port.• the operator changes the value in the Auto-negotiation parameter to ON.• the operator requests that auto-negotiation be restarted immediately on a specified

port.

The auto-negotiation process completes in approximately three seconds.

The link is considered down and a Link Fail alarm appears when one of the following instances occur:• The link partners are unable to resolve to a common mode of operation for any

negotiated parameter.• One or more link partners does not advertise any parameters.• If the detected speed and assumed duplex of the link partner are not compatible

with the Traverse.

If auto-negotiation is enabled for an FE port but the link partner does not negotiate, the system assumes that the link partner is operating in half duplex mode.

GbE-10 card GbE TX ports have auto-negotiation “forced” with speed set to 10 Gbps and duplex set to FULL DUPLEX. Manual Pause, Advertise 1000M Full Duplex, and Advertised PAUSE RX are provisionable. Through the Manual Pause parameter, Forced Pause Receive is provisionable and Forced Pause Transmit is disabled. Advertised PAUSE TX is disabled.


14 The Configure Advanced Parameters for Ethernet Ports procedure is complete.


Step Procedure

Important: By default, the Auto-negotiation feature is enabled with the exception of 10GBE ports, where auto-negotiation and pause functionality are unavailable. For GBE-10 TX ports, auto-negotiation is “forced” with speed set to 10 Gbps and duplex set to FULL_DUPLEX. However, the Traverse allows the operator to disable auto-negotiation for both ETH100TX and optical GbE ports.

Force10 recommends that if the peer device is 802.3 compliant, the operator leave the Auto-negotiation feature enabled.


Chapter 2 Configuring Ethernet EquipmentConfigure Auto- Negotiation for Ethernet

Configure Auto-Negotiation for Ethernet

Use the following procedure to help you configure Auto-negotiation on a port.

Table 6-10 Configure Auto-negotiation

Step Procedure

1 In Shelf View, click an Ethernet port, then click the Config tab to display the Ethernet Port Configuration screen.

Figure 6-7 Ethernet Port Configuration

2 In the Auto-negotiation parameter, select one of the following values: • On (default for all port types): Negotiate the speed, duplex attributes,

and pause flow control of the link based on the values in the Advertise parameters (as applicable to the port type). – For ETH100TX ports, go to Step 3.– For GBE ports, go to Step 4.

• Off: The link starts up and initializes with the values in the Manual Speed, Manual Duplex, and Manual PAUSE fields (as applicable to the port type). – For ETH100TX ports, go to Step 5.– For GBE ports, go to Step 6.


TraverseEdge 100 User Guide, Section 6: Creating Ethernet ServicesConfigure Auto- Negotiation for Ethernet

3 Click an ETH100TX port, then click Advanced to display the list of Advanced parameters for this port.

Figure 6-8 ETH100TX Port Auto-negotiation Parameters

If Auto-negotiation is turned on for this port, ETH100TX ports can adver-tise that the port is capable of operating as specified in the following parameters:• Advertise 10M Half Duplex: Enabled (default) or Disabled.

Advertise half duplex and 10 Mbps speed when Auto-negotiation is turned ON. Disable this parameter to specify this port not operate in this mode.

• Advertise 10M Full Duplex: Enabled (default) or Disabled. Advertise full duplex and 10 Mbps speed when Auto-negotiation is turned ON. Disable this parameter to specify this port not operate in this mode.

• Advertise 100M Half Duplex: Enabled (default) or Disabled. Advertise half duplex and 100 Mbps speed when Auto-negotiation is turned ON. Disable this parameter to specify this port not operate in this mode.

• Advertise 100M Full Duplex: Enabled (default) or Disabled. Advertise full duplex and 100 Mbps speed when Auto-negotiation is turned ON. Disable this parameter to specify this port not operate in this mode.

• Advertise PAUSE: Enabled (default) or Disabled. Select Enabled so the system transmits a PAUSE frame when the incoming traffic exceeds MIR / MBS (See Policing Algorithm, page 6-76 for information on these parameters). Select Disabled so the system does not transmit a PAUSE frame.When Enabled, the system responds to a received PAUSE frame by suspending transmission of traffic. When Disabled, the system does not suspend transmission of traffic when it receives a PAUSE frame.

Table 6-10 Configure Auto-negotiation (continued)

Step Procedure


Chapter 2 Configuring Ethernet EquipmentConfigure Auto- Negotiation for Ethernet

4 Click a GBE port, then click Advanced to display the list of Advanced parameters for this port.

Figure 6-9 GBE Port Auto-negotiation Parameters

If Auto-negotiation is turned on for this port, GBE ports can advertise one or more of the following parameters:• Advertise 1000M Full Duplex: Enabled (default) or Disabled.

Advertise full duplex and 1000 Mbps (1 Gbps) speed. • Advertise 1000M Half Duplex (TE-100 only): Enabled (default) or

Disabled. Advertise half duplex and 1000 Mbps (1 Gbps) speed. • Advertise PAUSE RX: Enabled (default) or Disabled. The system

commits to stop transmitting on the link when it receives a PAUSE frame from the link partner. Read-only for optical GBE ports when Auto-negotiation is turned ON. Configurable when Auto-negotiation is turned OFF.

• Advertise PAUSE TX: Enabled (default) or Disabled. The system sends a PAUSE frame to the link partner in times of upstream congestion or if the Traverse detects that this port is receiving traffic over the value specified in the Maximum Information Rate parameter.


Step Procedure


TraverseEdge 100 User Guide, Section 6: Creating Ethernet ServicesConfigure Auto- Negotiation for Ethernet

5 If Auto-negotiation is turned OFF for this ETH100TX port, set the follow-ing parameters:• Manual Duplex: Indicates the mode of operation for this port based

on IEEE standard 802.3.– Full (default): The port operates in full duplex mode and allows

simultaneous transmissions on the link.– Half: The port operates in half-duplex mode and uses CSMA/CD

to share access to the link.• Manual Speed: Configure the data rate of the link:

– 10 Mbps– 100 Mbps (default)

• Manual Pause: Configure if the system will send a PAUSE frame to the link partner in times of upstream congestion or if the traffic on this port is bursting over the value specified in the Maximum Information Rate parameter.

• Crossover: Controls the MDI/MDIX configuration of this port. – Enabled. Select to reverse the transmit and receive on this port.

Turns a straight-through cable into a crossover cable.– Disabled (default)

6 When Auto-negotiation is turned OFF for this optical GBE port, set the following parameters:• Manual Duplex: Indicates the mode of operation for this port based

on IEEE standard 802.3.– Full (default): The port operates in full duplex mode and allows

simultaneous transmissions on the link.– Half: The port operates in half-duplex mode and uses CSMA/CD

to share access to the link.• Manual Speed (Read only): 1000 Mbps (1 Gbps)• Manual PAUSE:

– Enabled. The system will send a PAUSE frame and commit to stopping traffic if it receives a PAUSE frame.

– Disabled. The system does not send or receive PAUSE frames.– TX Only (default). The system will send a PAUSE frame to the

link partner in times of upstream congestion or if the Traverse detects that this port is receiving traffic over the value specified in the Maximum Information Rate parameter.

– RX only. The Traverse commits to stop transmitting on the link when it receives a PAUSE frame from the link partner.

7 The Configure Auto-negotiation procedure is complete.


Step Procedure


Chapter 2 Configuring Ethernet EquipmentView the Negotiated Status of the Link for Ethernet

View the Negotiated Status of the Link for Ethernet

Use this procedure to view the negotiated status of the link.

Table 6-11 View the Negotiated Status of a Link

Step Procedure

1 In Shelf View, click an Ethernet port, then click the Config tab.

Figure 6-10 Ethernet Port Configuration Screen

2 On the Ethernet Port Configuration screen, click the Status button to display the Ethernet Port Status dialog box.

Figure 6-11 Ethernet Port Status Dialog Box

Auto-negotiation: Displays the configured value from the Auto-negotiation parameter.

Configuration Pause: Displays the configured value from the PAUSE parameter.

Configuration Duplex: Displays the configured value from the Duplex parameter.

Configuration Speed: Displays the configured value from the Speed parameter.

System Link Status: Displays the current status of the link. Valid values are:• Up: Indicates the link is active.• Down: Indicates the link is not working.

System Pause: Displays the current status of the PAUSE parameter.

System Duplex: Displays the current status of the Duplex parameter.

System Speed: Displays the current speed of the link.

2


TraverseEdge 100 User Guide, Section 6: Creating Ethernet ServicesView the Negotiated Status of the Link for Ethernet

3 Click Refresh to retrieve the current data.

Click Done to save the changes, close the dialog box, and return to the main screen.

4 The View the Negotiated Status of a Link procedure is complete.

Table 6-11 View the Negotiated Status of a Link (continued)

Step Procedure



Chapter 3 Ethernet Over SONET or SDH (EOS)

Introduction This chapter contains the following topics to create Ethernet over SONET or SDH services in a TraverseEdge 100 (TE-100) network:• EOS Definition, page 6-25• EOS Ports, page 6-25• Virtual Concatenation, page 6-26• Guidelines to Configure EOS Ports, page 6-26• Before You Configure EOS Ports, page 6-30• Configure Ethernet Transport Services, page 6-30• Configure EOS Ports, page 6-31

EOS Definition Ethernet traffic travels over SONET or SDH connections. Creating Ethernet over SONET/SDH (EOS) connections require two components:• EOS ports. On a TE-100 system, an EOS port is a port-like abstraction

representing the adaptation point between Ethernet and SONET/SDH. This EOS port can be thought of as an Ethernet WAN interface, compared to physical Ethernet ports which are Ethernet LAN interfaces.

• Transport connections. Create a regular SONET or SDH service. The SONET/SDH services will have one endpoint on the virtual SONET/STM interface (for Ethernet services) on the tributary card and one endpoint on the SONET/STM interface on the system cards.

EOS Ports An EOS port is a port-like abstraction representing the adaptation point between Ethernet and SONET/SDH.

The following functions take place at an EOS port:• Encapsulation. The cards use frame-mapped GFP, according to ITU-T G.7041, to

encapsulate Ethernet frames for transmission over SONET/SDH transport connections represented by EOS ports.

• Termination. Members of an EOS port are the endpoints of SONET or SDH services.

• Inverse Multiplexing. EOS ports support contiguous concatenation (no fragmentation) and both high and low order virtual concatenation.

• Other features such as MAC learning, LCAS, and RSTP.


TraverseEdge 100 User Guide, Section 6: Creating Ethernet ServicesVirtual Concatenation

The EOS port raises alarms and collects performance monitoring data the same way as a physical Ethernet port. It is also a valid endpoint in an Ethernet service.

Multiple members in an EOS port create a virtual concatenation group (VCG).

An operator creates and activates the SONET or SDH services, then creates the EOS ports on the card.

It is possible to have an EOS port with activated SONET or SDH services yet no Ethernet service connected to the EOS port. In this case, the SONET or SDH services and the EOS port will be operating fine but there is no Ethernet data to send. Any Ethernet data the EOS port receives from the transport network gets dropped.

If an operator creates an EOS port with no members, the system generates a “No Provisioned Members” alarm on that EOS port.

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 encapsulated Ethernet frames directly into a payload of separate path signals, known as a virtual concatenation group (VCG).

For example, in SDH standards, a VC-3-6v is a virtually concatenated path multiplexed onto six VC-3 paths. Its bandwidth is six times that of a VC-3.

In SONET standards, an STS-1-6c is a virtually concatenated path multiplexed onto six STS-1 paths. Its bandwidth is six times that of an STS-1.

This mapping technique eliminates the rigid hierarchies of the common SONET and SDH containers, enabling service providers to provision and transport data services more efficiently.

To create a virtual concatenated group (VCG) for a SONET or SDH circuit on the Traverse system, create an EOS port.

Guidelines to Configure EOS Ports

EOS Port Members (SONET or SDH Services)

Depending on the commissioned mode of the shelf, the TE-100 system has one virtual SONET or STM port on the backplane of the interface module. This virtual port is termed port 0 in the user interface.

The interface module in slot 3 supports termination functions for EOS. The operator can channelize into any or a combination of the following bandwidths: • STS-3c• STS-1• VT1.5• AU-4/VC-4/TUG-3/TUG-2/VC12• AU-3/VC-3 (HO VC-3)• AU-4/VC-4

See Section 5—Creating TDM Services, Chapter 5—“Creating SONET Services,” page 5-33 to create SONET services.

See Section 5—Creating TDM Services, Chapter 7—“Creating SDH Services,” page 5-59 to create SDH services.


Chapter 3 Ethernet Over SONET or SDH (EOS)Guidelines to Configure EOS Ports

The services can be either unidirectional or bidirectional. It is possible to add the transmit direction of an endpoint to an EOS port, and the receive direction of the same endpoint to another EOS port.

It is also possible to add the same endpoint to an EOS port twice, once as unidirectional in the transmit direction and once as unidirectional in the receive direction. Use this method to set up an asymmetric virtual concatenation group.

It is possible to add or remove endpoints dynamically to an EOS port.

Virtual Concatenation (VCAT)

The number of members supported depends on the TE-100 optical transport bandwidth (opt-bandwidth parameter during node commissioning) configuration.

The system supports a maximum differential delay of 100 milliseconds.

An EOS port supports asymmetric virtual concatenated groups. That is, the EOS port supports a different number of SONET or SDH services in the transmit direction is than in the receive direction.

An EOS port supports a mix of protected and unprotected members in the same virtually concatenated group.

An operator can dynamically add or remove protection for an EOS port member.

EOS Ports

A TE-100 supports up to 8 EOS ports. EOS ports 1 through 6 are FE (100 Mbps). EOS ports 7 and 8 are GbE (1000 Mbps).

EOS port members must have the same directionality as their SONET or SDH counterparts. That is, use a uni-directional EOS member with a uni-directional SONET

Table 6-12 Number of Supported VCAT Members

Commissioned Optical

BandwidthOC-48/STM-16 OC-12/STM-4 OC-3/STM-1

Member Size TX RX Bi TX RX Bi TX TX Bi

STS-3c 8 8 16 4 4 8 1 1 2

STS-1 24 24 48 12 12 24 3 3 6

VT-15 641 641 128 641 641 128 641 641 128

VC-4 8 8 16 4 4 8 1 1 2

HO VC3 24 24 48 12 12 24 3 3 6

VC-12 641 641 128 641 641 128 641 641 128

1 63 if LCAS is enabled on the EOS port.


TraverseEdge 100 User Guide, Section 6: Creating Ethernet ServicesGuidelines to Configure EOS Ports

or SDH path. Use a bi-directional EOS member with a bi-directional SONET or SDH service.

You cannot delete any EOS port that is being used in an activated Ethernet service.

It is possible to change the capacity of an LCAS-enabled EOS port by adding or removing members dynamically

Important: The action of changing the capacity of an LCAS-enabled EOS port is not hitless (~100 ms).

Prior to release TE3.2.x, you must add and activate the SONET or SDH service first before adding members to an EOS port. Similarly, you must remove the members from the EOS port before you deactivate or remove the SONET/SDH transport service. Specifically, if you have to change configuration on an Ethernet transport service, use the following sequence of steps:

Important: If any of the SONET/SDH services associated with the members of an EOS port are deactivated before the corresponding members are removed from the EOS, the entire EOS port can fail. Similarly, if members are added to an EOS port before their associated SONET/SDH services are activated, the entire EOS port can fail.1. Remove the member from the EOS port 2. Deactivate the service 3. Modify the parameters 4. Activate the service 5. Add the member back to the EOS port configuration


Chapter 3 Ethernet Over SONET or SDH (EOS)Example of EOS Ports

Example of EOS Ports

An EOS port is a port-like abstraction representing the adaptation point between Ethernet and SONET/SDH. Create the transport services first, then create the EOS ports.

Figure 6-12 EOS Ports on TE-100 and Traverse

3. SDH ServicesBandwidth: VC-12Source: Node/slot/p-0/a-1/tug3-1/tug2-1/vc12-1Destination: Node/slot/port/a-1/tug3-1/tug2-1/vc12-1Protection Type: Full



3. SONET ServicesBandwidth: VT1.5Source: Node/slot/p-0/sts-1/vtg-1/vt-1Destination: Node/slot/port/sts-1/vtg-1/vt-1Protection Type: Full


NodeA

1. SDH-VC4 EndpointBandwidth: VC-3 (Grooming)Source: Node/slot/port/a-1/vc4-1Protection Type: Full

Node 1

W

GCMOC48/STM16

VCXSlot 15

E

Slot 16

GBE/FETXSlot 1

.

..

.

..

2. EOS Port 1 (SDH)Concatenation Size: VC-12Concatenation Type: VirtualEndpoint 1: Node/slot/p-0/a-1/tug3-1/tug2-1/vc12-1Endpoint 2: Node/slot/p-0/a-1/tug3-1/tug2-1/vc12-2Endpoint 3: Node/slot/p-0/a-1/tug3-1/tug2-1/vc12-3

2

23

3

1

GCMOC48/STM16

VCX


2. EOS Port 1 (SONET)Concatenation Size: VT1.5Concatenation Type: VirtualEndpoint 1: Node/slot/p-0/sts-1/vtg-1/vt-1Endpoint 2: Node/slot/p-0/sts-1/vtg-1/vt-2Endpoint 3: Node/slot/p-0/sts-1/vtg-1/vt-3

1

SDH ORSONET


TraverseEdge 100 User Guide, Section 6: Creating Ethernet ServicesBefore You Configure EOS Ports

Before You Configure EOS Ports

Review the information in this topic before you configure EOS ports on the interface module.

Configure Ethernet Transport Services

Configure Ethernet transport services by following the procedures in Section 5—Creating TDM Services:• See Chapter 5—“Creating SONET Services,” page 5-33 for information on

creating SONET services.The SONET services will have one endpoint on the virtual SONET port on the interface module and one endpoint on the SONET port on the system cards.

• See Chapter 7—“Creating SDH Services,” page 5-59 for information on creating SDH services. The SDH services will have one endpoint on the virtual STM port on the interface module and one endpoint on the STM port on the system cards.

Table 6-13 EOS Port Requirements



Hardware

The physical network is connected. Section 3—Installation and Configuration, Chapter 1—“Installation Overview,” page 3-1

Software

Nodes are commissioned. Section 3—Installation and Configuration, Chapter 10—“Node Start-up and Initial Configuration,” page 3-69


Optical protection groups are configured. See Section 4—Configuring the Network:• Chapter 3—“Creating a UPSR/SNCP Protection




Ethernet equipment is configured. Section 6—Creating Ethernet Services, Chapter 2—“Configuring Ethernet Equipment,” page 6-5


Chapter 3 Ethernet Over SONET or SDH (EOS)Configure EOS Ports

Configure EOS Ports

Use this procedure to create and configure EOS ports.

Table 6-14 Creating EOS Ports

Step Procedure

1 Read the information in Before You Configure EOS Ports, page 6-30 before you start this procedure.

2 In Shelf View, click the Ethernet tab, then click Add. The Create EOS tab appears.

3 On the Create EOS tab, configure the parameters for the EOS port.

Figure 6-13 Create EOS Tab

Slot: On a TE-100 system, you can create an EOS port only in slot 3.

EOS Port ID: Enter a number between 1 and 8 to identify the EOS ports in the system. The maximum speed of an EOS Port ID 1, 2, 3, 4, 5, or 6 is 100 Mbps. The maximum speed of an EOS Port ID 7 or 8 is 1,000 Mbps (1 Gbps).

Description: Enter an alphanumeric character string to identify this EOS port in the EOS port list on the EOS subtab.

Concatenation Type: Indicates if this EOS port uses contiguous concatenation or virtual concatenation.• Virtual: This EOS port contains multiple endpoints of the same size

creating a virtual concatenation group. • Contiguous: The EOS port contains a single endpoint.


TraverseEdge 100 User Guide, Section 6: Creating Ethernet ServicesConfigure EOS Ports

Concatenation Size: Select the bandwidth of the transport paths that are members of this EOS port: • VT1.5 (NGE, NGE Plus only)• STS-1• STS-3C• VC-12 (NGE, NGE Plus only)• VC3-HO• VC-4

Tagging: Select one of the following tagging parameters: • Port-based: Every packet on this port is considered to belong to the

same service, regardless of whether or not the packet has a customer VLAN tag. Customer VLAN tags are not significant for service definition.

• Service-tagged: Every packet on this port is assumed to have a service provider VLAN ID that identifies its Ethernet service within the service provider network. Service provider VLAN tags are used within the service provider network and are never used on customer-facing ports. The service provider VLAN tag optionally carries packet class of service and drop precedence information used within the service provider network and not conveyed to the end customer.

RSTP: Click the check box to enable RSTP (Rapid Spanning Tree Protocol).

Note: If you are setting up Virtual RSTP, you should first set up the Virtual RSTP Bridges (VRBs). See Chapter 9—“Rapid Spanning Tree Protocol,” Configure Virtual RSTP, page 7-115 for more information.

VRB: If you are setting up VRSTP and have already set up your VRBs, click this field and select the VRB number from the drop-down menu for this EOS port. Valid values are 1 through 20; default is 1.

Table 6-14 Creating EOS Ports (continued)

Step Procedure



4 Add the endpoints of the EOS port to the endpoint table.

Figure 6-14 Add Endpoints to the EOS Port


b. Navigate the tree and select the desired endpoint. The endpoint must be in the same slot as the slot identified in parameter Slot.

c. Click Done to close the dialog box and return to the Create EOS tab on the main screen.

d. Type a unique number from 1 through 255 in the Member# column. e. Add extra rows to the endpoint table by clicking the plus sign in the

Add column. Add as many rows as required for this EOS port.f. Repeat Steps a. through e. for each required endpoint.


Step Procedure

4a

4b

4d

4c

4e



5 Configure the attributes of each EOS port member.

Direction: Select the direction the traffic travels on the EOS port member. This parameter must match the direction of the EOS port member SONET/SDH service. • Receive: Unidirectional in the receive direction only• Transmit: Unidirectional in the transmit direction only• Bidirectional: Traffic travels in both directions

Admin State: Select to control the suppression of alarms on the EOS port member.• Unlock (default)• Locked

Alarm Profile: Assign an alarm profile to the EOS port member. Select one of the following values:• useParent (default): The member inherits the alarm profile of the EOS

port. • default: Uses the default alarm profile (of type eos_ctp or

sdh_eos_ctp) for the selected endpoint.

6 Click Advanced to set the advanced attributes of the EOS port.

Alarm Profile: Assign an alarm profile to this EOS port. By default, the alarm profile is of type eos or sdh_eos.

PM Template: Assign a PM template to this EOS port. By default, the PM template is of type eos_pm.

GFP FCS Insert: Indicates whether or not the system inserts GFP Payload FCS (frame check sequence) into each frame sent over this EOS port. Payload FCS should be used only when interoperating with other vendors’ systems that require it. Normally it is not used on Traverse systems.• Enabled: The system adds Payload FCS to each frame.• Disabled (default): The system does not add Payload FCS to any

frame.

7 Insert Alternate VLAN Ethertype: For EOS ports 7 or 8 (1 Gbps). If this parameter is enabled, this EOS port will use the Alternate VLAN Ethertype value when a VLAN swap or add operation is performed on a packet being sent out this port.


Step Procedure



8 In the Queuing Policy parameter, specify how the queues are managed. Select one of the following values: • Priority: Select this queuing policy to schedule all packets for

transmission based on strict priority, using three classes of service. There are three priorities: Highest priority traffic uses CoS1, medium priority traffic uses CoS2, and low priority traffic uses CoS3.

• WFQ: Weighted fair queuing. Select this queuing policy to guarantee a specific amount of the port’s bandwidth when there is congestion on the port. WFQ uses three classes of service and the guarantees are specified as weights. If the value in this parameter is WFQ, specify the weights in the three WFQ CoS weight {1 | 2 | 3} parameters. Go to Step 9.

9 If WFQ is the value in the Queuing Priority parameter, configure the following parameters:• WFQ CoS 1 Weight: Weighted queuing policy of CoS1. Enter a

number between 1 and 100 to determine the proportion of bandwidth on this port for CoS1. The default value is 1 which means packets with the CoS1 have no priority in relation to the other classes of service.

• WFQ CoS 2 Weight: Weighted queuing policy of CoS2. Enter a number between 1 and 100 to determine the proportion of bandwidth on this port for CoS2. The default value is 1 which means packets with the CoS2 have no priority in relation to the other classes of service.

• WFQ CoS 3 Weight: Weighted queuing policy of CoS3. Enter a number between 1 and 100 to determine the proportion of bandwidth on this port for CoS3. The default value is 1 which means packets with the CoS3 have no priority in relation to the other classes of service.


11 Click Apply to create this EOS port and return to the Ethernet tab, EOS port subtab.

12 • The Creating EOS Ports procedure is complete. Continue to any of the procedures according to your network plan.


Step Procedure





Chapter 4 Link Capacity Adjustment Scheme

Introduction Link capacity adjustment scheme (LCAS) is a protocol defined in ITU G.7042, “Link capacity adjustment scheme (LCAS) for virtual concatenated signals.” Nodes at the ends of a virtually concatenated group (VCG) use this protocol to manage the group of concatenated SONET or SDH services. Specifically, a system can adjust the group membership in response to autonomic events (member fail or recover) or operator requests (manual add or remove member). LCAS signaling between peers is carried in the SONET/SDH path overhead as outlined in G.7042 and G.707.

See the following topics for a complete description of LCAS capabilities on the TraverseEdge 100 (TE-100) system.• LCAS Operation, page 2-38• LCAS and Protection Groups, page 2-39• Asymmetric LCAS, page 2-39• LCAS Interworking, page 2-40• Before You Begin, page 2-41• Guidelines to Configure LCAS, page 2-41• Configure LCAS, page 2-42


TraverseEdge 100 User Guide, Section 2: Creating Ethernet ServicesLCAS Operation

LCAS Operation

On the Traverse system, LCAS operates on the members of an EOS or EOP port that are in a virtual concatenation group (VCG). The system can adjust the capacity of the VCG membership in response to autonomic events (member fail or recover) or operator requests (manually add or delete).

The Traverse considers a member (unprotected or protected) to be failed if there is a critical alarm associated with that member. The Traverse considers a failed member to have recovered when the critical alarm has cleared.

The system generates an LCAS event whenever a member fails or recovers. Also, if a member is added or deleted to the VCG, the event identifies the EOS or EOP port, the event type (failure or recovery), and the number of currently active members on the port.

On NGE and NGE Plus cards, LCAS-enabled EOS ports must face LCAS-enabled EOS ports on the far-end. If an LCAS-enabled EOS port on an NGE card faces a non-LCAS EOS port on the far end, unexpected behavior may occur.

Due to differences between SONET/SDH conditions and PDH conditions, some differences exist in how LCAS handles failed/deleted members on EOP ports. These differences are discussed separately below.

Failed or Deleted Members on EOS Ports

If a member of an LCAS-enabled VCG fails or is manually deleted, the system automatically removes the member from the VCG. However, the VGG continues to transfer data on the remaining members of the group. There will be a short period during which data being transmitted or received on the VCG is discarded.

When a member fails and the LCAS {LO | HO} Holdoff Timer is enabled on the EOS port, the system does not remove the member until the timer expires. If the SONET/SDH protection mechanism restores the member path, then the period during which data is discarded can be minimized. If the protection mechanism is not successful in restoring the member path, then the period during which data is discarded will be extended while LCAS removes the member from the group.

The system raises a path alarm when a member fails, identifying both the failure and the slot-port-path. The system clears the path alarm when the member recovers.

If LCAS has removed failed members, as long as at least one member remains Ethernet data continues to flow on any activated services that are using the VCG. However, the remaining bandwidth may be insufficient to satisfy the service bandwidth needs.

The system raises a total loss of capacity alarms (TCLT, TCLR) for the VCG as well as path alarms for the individual members when there are no members left in the group. The alarms clear when at least one member returns to health and is added back to the operating VCG. The system also generates partial loss of capacity alarms (PLCT, PLCR) depending on the provisioned thresholds.

If an operator removes the only member from an LCAS-enabled EOS port, the port will fail and the system will generate a “No Provisioned Members” alarm.

Restored or Added Members on EOS ports

When a previously failed member recovers, the system automatically uses LCAS to add the member to the VCG. No data drops when the member is added into the VCG.


Chapter 4 Link Capacity Adjustment SchemeAsymmetric LCAS

However, data is lost when an operator manually adds or removes another member to the group.

If the LCAS {LO | HO} WTR timer is enabled on the EOS port, the system does not restore a failed member until the timer expires.

Failed or Deleted Members on EOP Ports

If an EOP member of an LCAS-enabled VCG fails due to an LOF, AIS, or LOM alarm, the system automatically removes the failed member from the VCAT group while the fault is present.

If an active EOP port member is in an IDLE fault condition, the member stays in the group, however, the system is unable to recover incoming frames resulting in a GFP fault.

Removing an LCAS on a PDH member occurs even if the administrative state of the member has been locked.

EOP port members provide a Loopback option. If an EOP port member is provisioned with Facility Loopback, the system cannot send a source signal on the looped-back member. The system removes the member from the VCAT group even if the member has been locked.

LCAS and Protection Groups

Members of a VCG can be part of a protection group or 1+1 path protected. An unprotected member has a single transport path. A protected member has two transport paths that operate as a path protection group.

When a member is protected, failure of one path will not cause a critical alarm; failure of both paths will. When both paths are failed, the recovery of one path removes the critical alarm.

The LCAS {LO | HO} Holdoff Timer should always be enabled when the VCG members are protected and always be disabled when VCG members are unprotected.

Asymmetric LCAS

Asymmetric LCAS arises when an LCAS-enabled VCG is configured with different bandwidth in each direction. However, there must be at least one path in each direction for LCAS to work. For example, you can configure three uni-directional paths from Node1 to Node2 using STS1, STS2, STS3, and one uni-directional path from Node2 to Node1 using STS10.

The Traverse system correctly transmits and receives Ethernet data when some (but not all) of the members of the VCG are uni-directional paths.

In addition, the Traverse system correctly transmits and receives Ethernet data when some (but not all) of the members of the VCG are bi-directional paths that have failed in only one direction.


TraverseEdge 100 User Guide, Section 2: Creating Ethernet ServicesLCAS Interworking

LCAS Interworking

When two nodes use virtual concatenation for a network connection, it is possible that one side is configured to use LCAS on the connection and the other side is not (or does not support LCAS). That is, when a node is using LCAS it sends LCAS control messages. If a Traverse node does not receive any LCAS control messages, it assumes that the peer is not using LCAS.

This table describes system behavior in interworking scenarios.

Table 2-15 LCAS Interworking and System Behavior

Traverse Peer Node System Behavior

Disabled Disabled If a member of a group fails, the entire group stops carrying traffic.

The system raises the total loss of capacity (TLCT and TCLR) alarms for the EOS port in addition to a SONET/SDH path alarm for the individual member.

The alarms clear when all members are restored and the EOS port starts to carry traffic again.

Enabled Disabled On NGE, 10GbE, and GbE-10 cards:• No traffic passes and the system raises a No

Remote LCAS alarm.• Traffic passes in a non-LCAS mode and raises an

LCAS_Inactive alarm.

On EoPDH cards:• Traffic passes in a non-LCAS mode and raises an

LCAS_Inactive alarm.

Disabled Enabled No traffic passes. The system raises the TLCT and TCLR alarms.

Enabled Enabled If a member of a group fails, the group continues to operate at reduced capacity.

The system removes the failed member from the group until it is able to carry traffic again.

When the member is restored, the system automatically adds it to the group again and increases the capacity.


Chapter 4 Link Capacity Adjustment SchemeGuidelines to Configure LCAS

Before You Begin

Review the information in this topic before you configure the LCAS.

Guidelines to Configure LCAS

The Concatenation Type parameter of the EOS port must be Virtual. See Section 6—Creating Ethernet Services, Chapter 3—“Ethernet Over SONET or SDH (EOS),” page 6-25 for detailed information on EOS ports.

The TE-100 system supports up to 63 LO members if LCAS is enabled, and up to 64 LO members if LCAS is disabled

Table 2-16 LCAS Requirements


Read the information in Read the information in Section 4—Configuring the Network, Chapter 1—“Configuring the Network,” page 4-1.

Hardware

The physical network is connected. Section 3—Installation and Configuration, page 3-1

Software







Ethernet equipment is configured. Section 6—Creating Ethernet Services, Chapter 2—“Configuring Ethernet Equipment,” page 6-5

EOS ports are configured. Section 6—Creating Ethernet Services, Chapter 3—“Ethernet Over SONET or SDH (EOS),” page 6-25


TraverseEdge 100 User Guide, Section 2: Creating Ethernet ServicesConfigure LCAS

Configure LCAS

Use this procedure to configure LCAS on an EOS or EOP port.

Note: EOP ports are only available on EOPDH cards.

Table 2-17 Configure LCAS

Step Procedure

1 In Shelf View, click the Tributary module, then click the Config tab.

Figure 2-15 Interface Card Configuration Tab

2 Configure the LCAS timers for EOS ports on this card. Configure the LCAS timers for EOP ports on this EoPDH card.

When LCAS detects that an Active EOS or EOP port member has failed, it will wait for a period defined by the hold-off timer parameters before removing that member from its fragmentation / reassembly processes (declares it “not Active”). • LCAS LO Holdoff (100 ms): The time in milliseconds LCAS waits

before removing a member from the LO VCAT groups on the card. Enter a value between 0 to 10 seconds, in increments of 100 milliseconds; default is 1 (100 milliseconds).

• LCAS HO Holdoff (100 ms): The time in milliseconds LCAS waits before removing a member from the HO VCAT groups on the card. Enter a value between 0 to 10 seconds, in increments of 100 milliseconds; default is 1 (100 milliseconds).

2 3


Chapter 4 Link Capacity Adjustment SchemeConfigure LCAS

3 Configure the LCAS wait-to-restore times for the EOS or EOP ports on this card (Traverse only).

When LCAS detects that a member has recovered from a failure, it will wait for a period defined by the Wait-to-Restore (WTR) timer before it includes that member back in its fragmentation / reassembly processes (declares it “Active”).• LCAS LO WTR (min): The time in minutes before the system

restores members of the LO VCAT group. Enter a value between 1 to 60 minutes, in increments of 1 minute; default is 5 minutes.

• LCAS HO WTR (min): The time in minutes before the system restores members of the HO VCAT group. Enter a value between 1 to 60 minutes, in increments of 1 minute; default is 5 minutes.

4 In Shelf View, edit the EOS or EOP port to enable LCAS.

Figure 2-16 EOS List on EOS Subtab

a. Click the Ethernet tab.b. Click the EOS or EOP subtab.c. Select the correct EOS or EOP port from the EOS or EOP port list.d. Click Edit to edit the EOS or EOP port configuration parameters.

To enable LCAS on an EOS port, go to Step 5.

To enable LCAS on an EOP port, go to Step 6.

Table 2-17 Configure LCAS (continued)

Step Procedure

4d

4a4b

4c



5 On the Edit EOS tab, click Advanced to display the EOS Port Advanced Parameters dialog box.

Figure 2-17 Edit EOS Tab

The EOS Port Advanced Parameters dialog box displays.

Figure 2-18 EOS Advanced Parameters Dialog Box


Step Procedure

5


Chapter 4 Link Capacity Adjustment SchemeConfigure LCAS

6 On the Edit EOP tab, click Advanced to display the EOP Port Advanced Parameters dialog box.

Figure 2-19 Edit EOP Tab

The EOP Port Advanced Parameters dialog box displays.

Figure 2-20 EOP Advanced Parameters Dialog Box


Step Procedure

7



7 Find and configure the following LCAS parameters for this EOS or EOP port:

LCAS: Enables or disables LCAS operations for this EOS or EOP port.• Select (default): Select the checkbox to enable LCAS to manage VCG

membership on this port. The system can remove any failed members from this service and continue to use this EOS or EOP port at a reduced capacity.

• Unselect (clear the checkbox): VCG membership is statically configured. The system stops carrying any traffic if a member fails or is removed from the VCG.

Apply LCAS WTR (Traverse only): Select the checkbox to apply the LCAS wait-to-restore value to this port.• Select: Use the value specified in the LCAS {LO | HO} WTR timer

(Step 3).• Unselect (default): Do not use the wait-to-restore value.

Apply LCAS Hold Off:• Select: Use the value specified in the LCAS {LO | HO} Holdoff

(100ms) timer (Step 2).• Unselect (default)

PLCT Threshold: Partial Loss of Capacity, Transmit (PLCT) Threshold. Indicates the number of provisioned EOS or EOP port source (transmit) members that should be operating correctly in order for the EOS or EOP port to carry its expected throughput. Whenever the number of correctly-operating source members falls below this threshold, the system will raise a PLCT alarm on the EOS or EOP port. Used only when the EOS or EOP port has LCAS enabled and has at least one provisioned member. Enter a number between 0 and 63. The default is 0, which means that the PLCT alarm will not be raised on this EOS or EOP port.

PLCR Threshold: Partial Loss of Capacity, Receive (PLCR) Threshold. Indicates the number of provisioned EOS or EOP port source (receive) members that should be operating correctly in order for the EOS or EOP port to carry its expected throughput. Whenever the number of correctly-operating source members falls below this threshold, the system will raise a PLCR alarm on the EOS or EOP port. Used only when the EOS or EOP port has LCAS enabled and has at least one provisioned member. Enter a number between 0 and 63. The default is 0, which means that the PLCT alarm will not be raised on this EOS or EOP port. :

8 Repeat Steps ? through 7 at the other end of the transport link.

9 The Configure LCAS procedure is complete.


Step Procedure



Chapter 5 Rapid Spanning Tree Protocol

Introduction This chapter contains the following topics about Rapid Spanning Tree Protocol (RSTP) in a TraverseEdge 100 (TE-100) network:• Supported RSTP Topologies, page 6-48• RSTP Bridge Management, page 6-49• RSTP Port Management, page 6-49• Guidelines to Configure RSTP, page 6-50• Before You Begin, page 6-51• Configure RSTP on an EOS Port, page 6-52• View RSTP Status, page 6-54


TraverseEdge 100 User Guide, Section 6: Creating Ethernet ServicesSupported RSTP Topologies

Supported RSTP Topologies

In Traverse Ethernet applications, enable RSTP among Traverse nodes that participate in bridge services to ensure that the Ethernet topology used to forward packets among the nodes is loop free. The Traverse supports both ring and mesh RSTP topologies.

This diagram illustrates how RSTP might create a spanning tree out of an Ethernet ring. In this example, each Ethernet card is in a separate Traverse node.

The lines between cards represent the point-to-point links that connect the RSTP bridges. These links are SONET/SDH connections that can be either contiguous concatenation paths or virtual concatenation groups. The dashed lines represent customer Ethernet ports.

Figure 6-21 Supported RSTP Topology

IEEE 802.1w defines an RSTP port to have one of the following roles:• Root (R) ports forward Ethernet frames. The system has decided to use this port to

reach the Root Bridge.• Designated (D) ports also forward Ethernet frames. • Alternate (A) ports are blocked but can quickly become forwarding ports when the

topology is reconfigured. In this diagram, one of the links is blocked (heavy line) at one node. The node that has blocked the link does not send or receive any packets on that link. This blockage prevents packets from looping around the ring.

• Edge (E) ports are those that have no further bridges downstream. RSTP does not run on these ports.

ETH

ETH

ETH

ETH

R: Root PortD: Designated portA: Alternate portE: Edge portRoot: Root Bridge of network

R

D

D

Root

D

R

DR D

R DD

RD

R

R

A

EE

ETH

ETH

E

E

E

E

E

E

ETH ETH


Chapter 5 Rapid Spanning Tree ProtocolRSTP Port Management

RSTP Bridge Management

An RSTP bridge is a network element that carries out Layer 2 Ethernet processing (maintaining forwarding tables, making forwarding decisions, and flooding packets). On the Traverse system, an RSTP bridge is represented by the Ethernet card itself.

The Traverse system has one RSTP bridge per Ethernet card. The RSTP bridge attributes are viewable on the Config tab of the Ethernet card.• RSTP Bridge ID. Read-only. An identifier for this card used in the RSTP protocol.

Displayed in the following hexidecimal format: <BridgePriority>000-<MAC address>. Example: 8000-1b2000c144d8.

• RSTP Bridge Priority. Enter an integer between 0 and 15. The default value is 8. The bridge (card) with the lowest Bridge Priority in the spanning tree topology will be selected as the Root Bridge. If the lowest Bridge Priority is shared by multiple bridges, the one with the smallest numerical MAC address will be selected as the Root Bridge. If you do not change the Bridge Priority of any card from its default of 8, this means that the card in the RSTP topology with the lowest MAC address becomes the Root Bridge.

• RSTP Root Port ID. Read-only. The EOS port on this card that currently provides the lowest cost path to the root bridge.

• RSTP Root Bridge ID. Read-only. The Bridge ID of the card that is currently selected as Root Bridge for the spanning tree topology.

RSTP Port Management

An RSTP port is the endpoint of a link that sends and receives packets. On the Traverse system, an RSTP port is represented by the EOS port type.

On an EOS port, configure the following parameters to enable RSTP on the EOS port:• RSTP. Enables or disables RSTP for Bridge services.

– Select Enabled to enable RSTP on this EOS port for bridge services.– Select Disabled to disable RSTP for bridge services.

• RSTP Path Cost. Set the path cost of this link. The total cost of a path between any card and the root bridge is the sum of the costs of all the links in the path. Lower values of this parameter mean that this port is more likely to be included in the lowest cost (more desirable) path from this or any other card to the root bridge. Enter an integer between 1 and 16. The default value is 1.

• RSTP Port Priority. Used when the spanning tree algorithm has determined that several ports on the card provide paths of equal total cost to the root bridge. The port with the lowest Port Priority is chosen as the Root Port. If several ports have the same lowest Port Priority, then the port with the lowest EOS Port ID is chosen as the Root Port. Enter an integer between 1 and 15. The default value is 8.

See View RSTP Status, page 6-54 to view the status of the RSTP port. RSTP port state parameters are as follows: • RSTP Port State. Read only.

– Disabled. This EOS port is not forwarding packets and is not participating in the RSTP operation.


TraverseEdge 100 User Guide, Section 6: Creating Ethernet ServicesGuidelines to Configure RSTP

– Listening. This EOS port is preparing to forward packets. It is temporarily disabled to prevent loops which may occur as the active topology of the LAN changes. Learning is disabled since changes in active topology can lead to incorrect information when the topology becomes stable.

– Learning. This EOS port is preparing to forward packets. It is temporarily disabled to prevent loops which may occur as the active topology of the LAN changes. Learning is enabled to collect information prior to forwarding, in order to reduce the number of frames unnecessarily forwarded.

– Forwarding. This EOS port is forwarding packets.– Blocking. This EOS port is not forwarding packets. It is preventing packets

from looping in the active topology.– Undefined. This EOS port is not using RSTP at all. Either this EOS port does

not have RSTP configured or there is no activated bridge service using this EOS port.

• RSTP Port Role. Read only. This field reads one of the following values.– Alternate. Ports are blocked but can quickly become forwarding ports when

the topology is reconfigured. The node that has blocked the link does not send or receive any packets on that link. This blockage prevents packets from looping around the ring.

– Designated. This EOS port forwards Ethernet frames. – Disabled. RSTP is not enabled for this EOS port.– Root. The system has decided to use this port to reach the Root Bridge. This

port also forwards Ethernet frames.

Guidelines to Configure RSTP

Before you create an EOS port with RSTP enabled for a bridge service, review the following guidelines:• The implementation of RSTP on the TE-100 system intended only to operate

within a network of TraverseEdge nodes using Release TE3.2.x software. RSTP runs on EOS ports and does not run on any physical Ethernet ports.

• Enable RSTP in the Advanced Parameters dialog box of an EOS port. • All EOS port members must be bi-directional links for RSTP to be enabled.• The EOS port must be an endpoint in one or more bridge services. By enabling

RSTP on an EOS port, the port broadcasts that it will forward (based on the MAC address) any packets sent to it. However, when an EOS port doesn’t participate in any Bridge service, it does not perform MAC forwarding at all.

• RSTP supports any Ethernet topology (“RSTP network”) that consists of a set of Ethernet cards (“RSTP bridges”) interconnected by SONET/SDH transport connections (“RSTP links”) where:– The number of RSTP links supported by a single RSTP bridge is up to at least

8 (all 8 EOS ports).– The number of RSTP bridges in the more complex (mesh) topology is any

number up to at least 200.– The number of card-to-card hops between RSTP bridges is up to at least 32.

• The TE-100 platform supports both ring and mesh RSTP topologies. • There can be up to 200 Ethernet cards in an RSTP topology, but there cannot be

more than 32 hops to the RSTP Root Bridge.• There can be up to 32 Ethernet cards in a ring topology.


Chapter 5 Rapid Spanning Tree ProtocolBefore You Begin

• On average, RSTP may take up to three seconds to reconverge whenever there is a topology change in a ring topology network. A topology change includes the addition, removal, failure, or recovery of Ethernet cards or links participating in the RSTP network.

• If a customer uses 802.1d Spanning Tree Protocol (STP) within their own topology, the TE-100 network is completely transparent to any such STP or RSTP implementation. That is, it looks like a multipoint LAN to which the customer’s devices are connected.

Before You Begin

Review the information in this topic before you configure the RSTP.

Table 6-18 RSTP Requirements



Hardware

The physical network is connected. Section 3—Installation and Configuration, Chapter 1—“Installation Overview,” page 3-1

Software







Ethernet modules and interfaces are configured. Section 6—Creating Ethernet Services, Chapter 2—“Configuring Ethernet Equipment,” page 6-5



TraverseEdge 100 User Guide, Section 6: Creating Ethernet ServicesConfigure RSTP on an EOS Port

Configure RSTP on an EOS Port

Use this procedure to help configure RSTP on an EOS port.

Table 6-19 Configure RSTP on an EOS Port

Step Procedure

1 Complete the procedure Creating EOS Ports, page 7-58.

2 In Shelf View, click an Ethernet card, then click the Ethernet tab.

Figure 6-22 Ethernet Card, Ethernet Configuration Tab

3 Edit the EOS port.

Figure 6-23 Ethernet Tab, EOS Subtab

a. Click the EOS subtab.b. Click the EOS port on the card to edit.c. Click the Edit button.

4 On the Edit EOS tab, click the Advanced button.

Figure 6-24 Click Advanced on the Edit EOS Tab

3a

3c

4


Chapter 5 Rapid Spanning Tree ProtocolConfigure RSTP on an EOS Port

5 On the Advanced Parameters dialog box, set the RSTP Path Cost and RSTP Port Priority parameters for this EOS port.

Figure 6-25 RSTP Parameters for EOS Port

RSTP Config: Enables or disables RSTP for bridge services. If RSTP was not enabled on the previous screen, select RSTP Config to enable it.• Select to enable RSTP on this EOS port for bridge services.• Unselected (default). Disables RSTP for bridge services.

RSTP Path Cost: Set the path cost of this link. The total cost of a path between any card and the root bridge is the sum of the costs of all the links in the path. Lower values of this parameter mean that this port is more likely to be included in the lowest cost (more desirable) path from this or any other card to the root bridge. Enter a number between 1 and 16; default is 1.

RSTP Port Priority: Used when the spanning tree algorithm has determined that several ports on the card provide paths of equal total cost to the root bridge. The port with the lowest Port Priority is chosen as the Root Port. If several ports have the same lowest Port Priority, then the port with the lowest EOS Port ID is chosen as the Root Port. Enter a number between 1 and 15; default is 8.

6 Click Done to save the changes, close the Advanced Parameters dialog box, and return to the Edit EOS tab.

7 On the Edit EOS tab, click Apply to save the changes and return to the EOS list on the EOS subtab.

8 The Configure RSTP on an EOS Port procedure is complete.

Table 6-19 Configure RSTP on an EOS Port (continued)

Step Procedure


TraverseEdge 100 User Guide, Section 6: Creating Ethernet ServicesView RSTP Status

View RSTP Status

Use this procedure to view the status of RSTP on an Ethernet card.

Table 6-20 View RSTP Port Status

Step Procedure

1 Complete the procedure: Configure EOS Ports, page 6-31.

2 In Shelf View, click an Ethernet card, then click the Config tab.

Figure 6-26 Ethernet Card Configuration Tab

RSTP Bridge ID. Read-only. An identifier for this card used in the RSTP protocol. Displayed in the following hexidecimal format: <BridgePriority>000-<MAC address>. Example: 8000-1b2000c144d8.

RSTP Root Port ID. Read-only. The EOS port on this card that currently provides the lowest cost path to the root bridge.

RSTP Root Bridge ID. Read-only. The Bridge ID of the card that is currently selected as Root Bridge for the spanning tree topology.


Chapter 5 Rapid Spanning Tree ProtocolView RSTP Status

3 In Shelf View, edit the EOS port.

Figure 6-27 Ethernet Tab, EOS Subtab

a. Click the Ethernet tab.b. Click the EOS subtab.c. Click the EOS port to edit.d. Click the Edit button.

4 On the Edit EOS tab, click Status.

Figure 6-28 Click Status on the Edit EOS Tab

5 On the EOS Port Status dialog box, view the RSTP port status.

Figure 6-29 RSTP Parameters for EOS Port

See RSTP Port Management, page 6-49 for explanations of these parameters.• RSTP Port State• RSTP Port Role

Table 6-20 View RSTP Port Status (continued)

Step Procedure

3b

3a

3c

3d

4


TraverseEdge 100 User Guide, Section 6: Creating Ethernet ServicesView RSTP Status

6 Click Refresh to retrieve the current data for the EOS port.

Click Done to close the EOS Port Status dialog box.

7 On the Edit EOS tab, click Cancel to save the changes and return to the EOS list on the EOS subtab.

8 The View RSTP Port Status procedure is complete.

Table 6-20 View RSTP Port Status (continued)

Step Procedure



Chapter 6 Ethernet Services

Introduction This chapter contains the following topics about creating Ethernet services in a TraverseEdge 100 (TE-100) network:• Ethernet Services Definition, page 6-57• Guidelines to Configure Ethernet Services, page 6-65• Before You Begin, page 6-66• Configure Ethernet Services, page 6-67

Ethernet Services Definition

Ethernet service is a card-level packet forwarding relationship, optionally restricted by VLAN ID, between Ethernet termination points on the same card.

The endpoints in an Ethernet service can be any one of the following types: • GBE• ETH100TX• EOS port. Ethernet-over-SONET/SDH transport connections

The TraverseEdge platform supports the following types of Ethernet services: • Line Services, page 6-58• Bridge Services, page 6-60• Aggregated Bridge Services, page 6-61


TraverseEdge 100 User Guide, Section 6: Creating Ethernet ServicesLine Services

Line Services An Ethernet line service is a forwarding relationship between two endpoints on the same card. Use this service to create a dedicated point-to-point service, a shared point-to-point service, or an internet access application.

Figure 6-30 Line Service

An Ethernet line service transfers packets from one port to another. The set of arriving packets on a port that belong to a particular line service may be (a) all packets, or (b) a subset identified by VLAN. Once identified to a service, the system forwards the packets to, and only to, the other port in the service. Services can share (by VLAN ID) any of the endpoints with other services.

The system does not learn the source MAC addresses on any port in a line service and forwards packets without regard to the destination MAC addresses.

Under some circumstances, the system can modify the VLAN information on the packet. The forwarding mechanism is subject to traffic management, which may end up dropping some of the packets.


Chapter 6 Ethernet ServicesLink Integrity

Link Integrity Link integrity is a feature in which the system provides a reliable point-to-point link between Ethernet ports on two different systems joined by a network transport connection. This is an attribute of a relationship between ports, not on a port itself. Link integrity communicates a failure anywhere in the end-to-end data path to both ports as follows:• If a local Ethernet port fails, the local system informs the remote system of the

failure.• When the local system learns of a remote Ethernet port failure, the local system

disables the transmitter of the local Ethernet port so the local Ethernet port’s link partner will consider the link to be down.

• If the transport connection between the Ethernet ports fails, each of the two end systems will disable the transmitter of its local Ethernet port.

Enable the link integrity feature on Ethernet line services using the Link Integrity parameter. Configure link integrity on two line services that use exactly one Ethernet port and one EOS port on the ingress and egress nodes of the network. Neither the Ethernet port nor the EOS port can be in any other activated service.

Link integrity is not supported on an EOP port on the EoPDH card.


TraverseEdge 100 User Guide, Section 6: Creating Ethernet ServicesBridge Services

Bridge Services

A bridge service is a forwarding relationship between an arbitrary number of endpoints on the same card. Any of the endpoints can be shared (by VLAN ID) with other services. Within a single bridge service, a packet is forwarded to one endpoint or to all endpoints using standard MAC address forwarding rules. Use this service to create a Virtual LAN Service application in the network.

Figure 6-31 Bridge Service

The system learns the source MAC addresses from packets that arrive on any port in a bridge service. The system forwards packets to other ports in the same service based strictly on the destination MAC address.

Adding and Removing Endpoints to a Bridge Service

You can add or remove endpoints to and from an activated bridge service. If, during a transition, the membership of the bridge service is less than two, the system will suspend forwarding packets and will resume forwarding when another member is added.


Chapter 6 Ethernet ServicesAggregated Bridge Services

Aggregated Bridge Services

An aggregation bridge service is a hybrid of a line service and a bridge service. It is a forwarding relationship between a set of endpoints on a card, where one endpoint is considered the aggregation port and the other endpoints are considered ordinary members of the service.

Traffic received on the aggregation port is forwarded just as in a bridge service – to one or more ordinary members based on the destination MAC address. Traffic received on the ordinary members of the service is forwarded directly to the single aggregation port. (This is always an EOS port on a TE-100 system.)

Figure 6-32 Aggregated Bridge Service

The system learns MAC addresses only on the non-aggregation members. Learned MAC addresses are needed to determine forwarding from the aggregation port to the other ports.

Aggregation Bridge Service with an Active/Standby CPE

In this scenario, the aggregation port is an EOS port. The other endpoints are Ethernet ports that connect to different line cards (one Active, one Standby) in a CPE (customer premise equipment) device. The CPE sends and receives on one of the Ethernet ports at a time. The Traverse forwards traffic from both CPE ports to the EOS port. In the other direction, the Traverse forwards traffic from the EOS port to whichever Ethernet port the MAC address has been learned on. Packets addressed to unknown or broadcast MAC addresses are flooded to both Ethernet ports. The CPE device accepts the packets from the active port and ignores packets from the standby port.


TraverseEdge 100 User Guide, Section 6: Creating Ethernet ServicesEthernet Services and VLAN Tagging

Ethernet Services and VLAN Tagging

This table summarizes system behavior between incoming packets (ingress) and outgoing packets (egress) based on the Tagging parameter.

Supported VLAN Tagging and Ethernet Service Combinations

Because line services only contain two ports, VLAN IDs and port-tagging types are known at the time you configure the service.

However, it is possible to add new ports to Bridge and Aggregation Bridge services after these services are activated. Configure the Allowed Port Tagging Type parameter for Bridge and Aggregation Bridge services based on the information in the following table.

Table 6-21 VLAN Tag Modification

Ingress Port

Egress Port

Port-Based Untagged Customer-Tagged Service-Tagged

Port-Based No change. Not supported. Not supported. Add service tag. (Line and Agg Bridge only)

Untagged Not supported No change Add customer tag Add service tag

Customer-Tagged Not supported Remove customer tag

No change Add service tag

(Line and Agg Bridge only)

Service-Tagged Remove service tag

Remove service tag

Remove service tag

No change

Table 6-22 Supported VLAN Tagging and Ethernet Service Combinations

Tagging Type Combinations

Service Type User Provisioned VLAN IDsLine Bridge Agg Bridge

Port-based only None

Port-based and Untagged

not supported not supported not supported n/a

Port-based and Customer-tagged

not supported not supported not supported n/a

Port-based and Service-tagged

not supported Service VIDUnique to shelf

Untagged only None

Untagged and Customer-tagged

Customer VID Unique to shelf


Chapter 6 Ethernet ServicesReserved VLAN IDs

Reserved VLAN IDs

The system reserves VLAN IDs 4000 to 4089 for system use. The system uses VLAN IDs 4090 to 4094 to communicate between system cards. The system uses VLAN ID 4095 for RSTP BPDUs.

Therefore, the valid range of configurable VLAN IDs for Ethernet services is from 1 to 3999.

Untagged and Service-tagged

Service VID Unique to shelf

Customer-tagged only

Customer VID Unique to port

Customer-tagged and Service-tagged

not supported Customer VID Unique to portService VID Unique to shelf

Service-tagged only Service VID unique to shelf

Table 6-22 Supported VLAN Tagging and Ethernet Service Combinations

Tagging Type Combinations

Service Type User Provisioned VLAN IDsLine Bridge Agg Bridge


TraverseEdge 100 User Guide, Section 6: Creating Ethernet ServicesConfigurable VLAN IDs

Configurable VLAN IDs

The valid range of configurable VLAN IDs for Ethernet services is from 1 to 3999. See Reserved VLAN IDs, page 6-63 for information on VLAN IDs 4000 to 4095.

Configure VLAN IDs for Ethernet services on the Create Service tab, Advanced button. Depending on the Ethernet service and the Tagging on the port, you can configure the following parameters:• Service VID. Enter a VLAN ID between 1 and 3999 for Ethernet packets

transmitted to Service-tagged ports in this service. This VLAN ID must be unique on this TE-100 system.

• Customer VID. Enter a VLAN ID between 1 and 3999 for Ethernet packets transmitted to Customer-tagged ports in this service. This VLAN ID must be unique on the Ethernet ports in this service. If the Allowed Port Tagging Type is UT-CT, this VLAN ID must be unique on this TE-100 system.

Use the following guidelines to configure VLAN IDs for Ethernet services:• A service in which all ports are Port-based or Untagged needs no VLAN ID at all.• For a service that contains or could contain Customer-tagged ports, configure a

Customer VID. The Customer VID is used to claim packets arriving on the service’s Customer-tagged ports. If the service is one in which the system adds a Customer VLAN tag to a previously untagged packet, then the Customer VID is also used to construct the added VLAN tag. All Customer-tagged ports in the service recognize and/or insert the same Customer VID.

• For a service that contains or could contain Service-tagged ports, configure an Service VID. The Service VID is used to claim packets arriving on the service’s Service-tagged ports. If the service is one in which the system adds an S-tag to a packet that did not previously have one, then the Service VID is also used to construct the added S-tag. All Service-tagged ports in the service recognize and/or insert the same Service VID.

• For a service that contains or could contain both Customer-tagged and Service-tagged ports, the user must provide both a Customer VID and an Service VID. The Customer VID is used with the Customer-tagged ports, and the Service VID is used with the Service-tagged ports.


Chapter 6 Ethernet ServicesGuidelines to Configure Ethernet Services

Guidelines to Configure Ethernet Services

See Supported VLAN Tagging and Ethernet Service Combinations, page 6-62 for valid combinations of port Tagging types and Ethernet services.

You cannot change the Tagging parameter on a port if there is an activated service using the port.

A TE-100 supports up to 96 simultaneous activated point-to-point forwarding service-ports. Point-to-point service ports are ports that are in a line service or the non-aggregating members of an aggregation bridge service.

A TE-100 supports up to 96 simultaneous activated MAC forwarding service-ports. MAC forwarding ports are any ports in a bridge service and the aggregation port member in an aggregation bridge service.

Line Services

A line service has exactly two member ports on the node. You cannot remove any member from an activated service.

The two ports in a line service can be both Ethernet ports, both EOS ports, or a combination of an Ethernet port and an EOS port.

The TE-100 supports up to 32 Ethernet activated line services.

Enable the link integrity feature on Ethernet line services using the Link Integrity parameter. Configure link integrity on a line service that uses exactly one Ethernet port and one EOS port on the ingress and egress nodes of the network.

Bridge Services

A bridge service can contain up to 16 ports in one service (all eight Ethernet ports as well as all eight EOS ports).

You can add or remove members from an activated bridge service. If, during a transition, the membership of the bridge service is less than two, the system will suspend forwarding packets and will resume forwarding when another member is added.

A TE-100 supports up to eight activated bridge services.

Aggregation Bridge Services

An aggregation service aggregates packets from several Ethernet ports to one EOS port. An aggregation bridge service must have exactly one aggregation port, which cannot be removed or replaced while the service is activated.

The aggregation port must be an EOS port.

In addition to the single EOS aggregation port, an aggregation bridge service can contain up to 8 Ethernet ports (other members).

All non-aggregating service ports must have the same value in the Tagging parameter.

The TE-100 supports up to eight activated aggregation bridge services.

You can add or remove members from an activated aggregation bridge service without disrupting traffic among the existing ports in the service.


TraverseEdge 100 User Guide, Section 6: Creating Ethernet ServicesBefore You Begin

Before You Begin

Review the information in this topic before you configure the Ethernet services.

Table 6-23 Ethernet Service Requirements



Hardware

The physical network is connected. Section 3—Installation and Configuration, page 3-1.

Software

Nodes are commissioned. Section 3—Installation and Configuration, Chapter 10—“Node Start-up and Initial Configuration,” page 3-69.






Ethernet modules and interfaces are configured. Section 6—Creating Ethernet Services, Chapter 2—“Configuring Ethernet Equipment,” page 6-5.


Read the Ethernet Services definitions in this chapter. Know the endpoints and attributes of each service.

• Line Services, page 6-58• Bridge Services, page 6-60• Aggregated Bridge Services, page 6-61


Chapter 6 Ethernet ServicesConfigure Ethernet Services

Configure Ethernet Services

Use the following procedure to help create Ethernet services.

Table 6-24 Configure Ethernet Services

Step Procedure

1 Review the information in the topic: Before You Begin, page 6-66.

2 In Shelf View, add the Ethernet service.

Figure 6-33 Select Ethernet on the Services Tab

a. Click the Service tab.b. From the Add button menu, select Ethernet.c. Click Add to display the Create Service tab.

3 On the Create Service tab, enter the general information about this service.

Figure 6-34 Create Ethernet Line Services

• Name: Enter a unique name for the service. Use alphanumeric characters and spaces only. Do not use any other punctuation or special characters.

• Description: Enter the description of the service. Use alphanumeric characters and spaces only. Do not use any other punctuation or special characters.

• Customer: Select a customer name from the drop-down list box.

2a

2b

2c

3

8

5

4

6

7


TraverseEdge 100 User Guide, Section 6: Creating Ethernet ServicesConfigure Ethernet Services

4 In the Type parameter, select the type of Ethernet service.• Bridge• Line• Aggregated Bridge

5 In the Endpoint table, select the correct endpoints for this service. The endpoints must be on the same Ethernet module.

6 Configure the Advanced Parameters of each service port. Click the Advanced column in the Endpoint table for this service port.

Figure 6-35 Advanced Parameters Ethernet Service Ports

• VLAN Type. Specifies which VLAN ID the system uses on this service port. – Untagged/PrtyTagged– ServiceVLANID (default). The system uses the Service VLAN ID

(Step 7) to determine the VLAN ID for this service.• MAC Address. (Planned for future release.)

Table 6-24 Configure Ethernet Services (continued)

Step Procedure


Chapter 6 Ethernet ServicesConfigure Ethernet Services

7 Configure the Advanced parameters of the Ethernet service. Click the Advanced button to display the Advanced Parameters dialog box.

Figure 6-36 Advanced Parameters

Allowed Port Tagging Type. (Bridge and Agg Bridge services only). Select the correct combination of port Tagging Type parameters from Table 6-22, “Supported VLAN Tagging and Ethernet Service Combinations,” on page 62. You must know the Tagging of all the ports in the service.

Link Integrity (for Line services only). Monitors the status of Ethernet ports and the associated transport connection. Enable the link integrity feature on Ethernet line services using the Link Integrity parameter. Configure link integrity on two line services that use exactly one Ethernet port and one EOS port on the ingress and egress nodes of the network. Neither the Ethernet port nor the EOS port can be in any other activated service. • Disable (default): the Link Integrity feature is not used on this service.• Enabled: Enables the Link Integrity feature on this service whenever

the service is activated.

Service VID. Enter a VLAN ID between 1 and 3999 for Ethernet packets transmitted to Service-tagged ports in this service. This VLAN ID must be unique on this TE-100 system. See Configurable VLAN IDs, page 6-64 for valid VLAN IDs.

Customer VID. Enter a VLAN ID between 1 and 3999 for Ethernet packets transmitted to Customer-tagged ports in this service. This VLAN ID must be unique on the Ethernet ports in this service. If the Allowed Port Tagging Type is UT-CT, this VLAN ID must be unique on this TE-100 system. See Configurable VLAN IDs, page 6-64 for valid VLAN IDs.


9 Click Apply to create the service and return to the services list on the Service tab in the main screen.

10 The Configure Ethernet Services procedure is complete.

Continue to Section 5—Creating TDM Services, Chapter 3—“Common Procedures for Creating Services,” Activate or Deactivate a Service, page 5-14.

Table 6-24 Configure Ethernet Services (continued)

Step Procedure


TraverseEdge 100 User Guide, Section 6: Creating Ethernet ServicesConfigure Ethernet Services


SECTION 6CONFIGURING ETHERNET

Chapter 7 Ethernet Traffic Management on the TE-100

Introduction This chapter contains the following topics:• Ingress Traffic Flow, page 6-72• Egress Traffic Flow, page 6-73• Ethernet Traffic Management Description, page 6-74


TraverseEdge 100 User Guide, Section 6: Configuring EthernetIngress Traffic Flow


Ingress Traffic Flow

This flow chart describes system traffic management behavior once it has received an Ethernet frame.

Figure 6-37 Ingress Traffic Flow

TE100-00025

Determine priority(VLAN tag or

Default IngressPriority for

untagged packets)

Classify packet.Determine CoS.

Packet Dropped

Send PAUSEFrame

Packet Received

Well-FormedPacket?

Y Y

N

Determine servicebased on Tagging

type of ingressport and VLAN tag

Is arrival rate over MIR/MBS?

N

Packet Dropped

Is arrival rate at MIR/MBS?

Is PAUSEenabled?

Y Y

Forwarded basedon forwarding

rules of service

EgressPort(s) Forwarded to one or more

ports based on service type

Chapter 7 Ethernet Traffic Management on the TE-100Egress Traffic Flow

Egress Traffic Flow

This flow chart describes system traffic management behavior before it transmits the packet.

Figure 6-38 Egress Traffic Flow

MarkingYAdd VLAN tag?

For every egress portselected by theforwarding step

FromIngress

Port

N

Can packet bequeued? Packet Dropped

Shaping

Scheduling

PacketTransmitted

Y

N

TE100-00026


TraverseEdge 100 User Guide, Section 6: Configuring EthernetEthernet Traffic Management Description

Ethernet Traffic Management Description

The steps in this table describe system traffic management behavior and reference the following flow charts:• Ingress Traffic Flow, page 6-72.• Egress Traffic Flow, page 6-73.

Table 6-25 Ethernet Traffic Management Flow

Step Reference

1 Receiving and Checking. A packet is received from a physical Ethernet port or from an EOS port.

The system performs Layer 2 check (CRC check, frame size, etc.). Bad packets are counted and dropped. Good packets are counted.

n/a

2 Ingress buffering and shaping. The system calculates the current arrival rate for this port. If it exceeds the configured maximum allowed arrival rate for the ingress port, send a PAUSE frame.

Strict-Port Policing, page 6-76

3 Determine Service. The system references the Tagging parameter of the ingress port. Based on Tagging parameter and the presence (or absence) of VLAN tag in the packet, the system determines which service the packet belongs to.

If the service type is in a bridge service, perform MAC learning on the packet’s Source MAC address for this port and service.

• Section 6—Creating Ethernet Services, Chapter 2—“Configuring Ethernet Equipment,” page 6-5

• Section 6—Creating Ethernet Services, Chapter 6—“Ethernet Services,” page 6-57

4 Classifying Packets. The system references the per-port classifier for this ingress port. Then, the systems processes the Priority in the packet field using the classifier to set class of service (CoS).

Chapter 3—“Classifying and Prioritizing Packets,” page 7-17

5 Forwarding Packets. The system selects one or more egress ports based on the service type, a list of ports in the service, and possibly the packet’s Destination MAC address.

Section 6—Creating Ethernet Services, Chapter 6—“Ethernet Services,” page 6-57

6 Modifying Packets. The system references the Tagging parameter of the egress port. Based on Tagging parameter, and the presence or absence of VLAN tag in the packet, the system performs VLAN modification if necessary.


7 Marking Packets. If the system is adding a VLAN tag, the system encodes the class of service and final drop precedence into the Priority field of the service provider tag.

Marking Packets, page 6-82

8 Shaping Traffic. If the Queuing Policy of the egress port is FIFO and FIFO Shaping is enabled, use the Shaping Rate to delay the packet until it’s time.

If the Queuing Policy is WFQ, shape the traffic according to the provisioned weights for the queues.

Queuing Policy, page 6-80


Chapter 7 Ethernet Traffic Management on the TE-100Pause Control

Pause Control Auto-negotiation is a process described in IEEE 802.3 that allows two devices on an Ethernet segment (link partners) to determine mutually agreeable settings for speed, duplex, and pause flow control. By default, the auto-negotiation feature is always enabled. See Chapter 2—“Configuring Ethernet Equipment,” Auto Negotiation for Ethernet, page 6-18 for information on Auto-Negotiation.

The following sections detail how and when the system sends and receives PAUSE frames.

On Sending PAUSE frames

Transmitting a PAUSE frame is a means for ingress shaping or limiting the incoming flow of traffic from CPE devices to the combined provisioned rate and burst size (MIR/MBS) on the port. The Traverse generates a PAUSE frame only when the rate of incoming traffic approaches the maximum information rate (MIR) limit configured for the port.

If a large burst arrives which would exceed the configured MBS, the system sends a PAUSE frame during the burst, reducing the packet arrival rate back down to the configured rate.

The default value for the MIR on each port type is the maximum data rate for that port. For example, ETH100TX port has a default MIR of 100 Mbps. A GBE port has a default value of 1000 Mbps. This means that by default, ingress shaping is not used and the system will not send a PAUSE frame.

The system invokes flow control early enough so that the there is sufficient buffer space to hold packets that may arrive from the Ethernet port prior to the link partner’s having responded to the PAUSE frame. For purposes of buffer space calculation, the system assumes the link partner operates according to IEEE 802.3, section 31B.3.7.

If the system drops packets because of no buffer space, in spite of having invoked flow control, it counts those packets in the RX DISCARD counter of the port on which the packet arrived.

Flow control operates independently for all Ethernet ports. That is, invoking flow control on one Ethernet port has no effect on the flow of traffic on any other Ethernet port.

9 Scheduling Packets. When the packet reaches the front of the correct output queue, the port has bandwidth to transmit a packet, and the Queuing Policy for the egress port says the next packet should come from this output queue, the system transmits the packet.

Queuing Policy, page 6-80

10 The system transmits the packet based on the forwarding rules of the service.


Table 6-25 Ethernet Traffic Management Flow (continued)

Step Reference


TraverseEdge 100 User Guide, Section 6: Configuring EthernetStrict-Port Policing

To remove flow control, the system sends an IEEE 802.3 PAUSE frame with a timer set to zero.

On Receiving PAUSE Frames

Whenever the Traverse receives PAUSE frame on an Ethernet port and PAUSE is enabled on that port, the system responds by suspending its transmission of packets on that port.

Advertise that the Traverse will transmit a PAUSE frame when it detects congestion on upstream or if the traffic on this port is bursting over the value specified in the Maximum Information Rate / Maximum Burst Size parameters.

If pause control is enabled for the port and the system receives a PAUSE frame on the port, the system does not transmit another packet to the port until it receives a PAUSE frame with a timer of zero on that port. However, the system finishes transmitting any packet that is being transmitted on a port when a PAUSE frame is received on that port.

When pause control is disabled on a port, the system simply removes the PAUSE frame from the data stream and continues to transmit packets accordingly.

Strict-Port Policing

Use maximum information rate (MIR) and MIR burst size (MBS) to do both ingress shaping (using PAUSE flow control) or per-port strict policing. The response of the system to incoming traffic depends on whether PAUSE (or, for GbE, PAUSE TX) is enabled on the Ethernet port.

If PAUSE is enabled on the Ethernet port, the system invokes flow control by sending a PAUSE frame when the ingress traffic approaches MIR. (Approaches means the system reserves a cushion such that traffic that is already in transit before the peer could possibly respond to the PAUSE will be considered conformant according to the token bucket.) If the peer responds correctly to the PAUSE frame, then this mechanism is lossless from TE-100 perspective.

If PAUSE is disabled on the Ethernet port, then the system will not send a PAUSE frame. All traffic that does not conform to the token bucket—traffic that arrives in excess of MIR/MBS—is dropped.

Policing Algorithm

MIR and MBS operate as a single token bucket to police the incoming traffic. Configure MIR and MBS together for strict port policing (i.e. dropping traffic in excess of MIR/MBS) when PAUSE is disabled on the port.

The TE-100 system uses a single token bucket algorithm to police incoming traffic. This token bucket policer is defined by a rate (token arrival rate) and a burst size (bucket depth).

Strict port policing is used when • multiple ingress ports are being aggregated to one egress port, and • it is desired to rate limit one or more ports so that they can not use an unfairly large

part of the bandwidth on the egress port, and • either PAUSE flow control is not available, or the user prefers to drop excess traffic

rather than buffer it in the sending device.


Chapter 7 Ethernet Traffic Management on the TE-100Policing Algorithm

If the traffic is very bursty, consider provisioning a larger MBS value to admit larger bursts than the default (64 Kbytes).

Caution: the TE-100 has limited buffering for queued egress traffic. If a shared egress port is congested, admitting a large burst on one ingress port might affect traffic that arrives on other ingress ports and has to be queued for the same egress port.

The system will enforce a minimum MBS value for an FE port or GbE port. The minimum MBS value is required by the hardware to ensure that PAUSE operates successfully and is in part based on the current MIR value for the port. See the following charts. • Figure 6-39 MIR Burst Size as a function of MIR for FE ports• Figure 6-40 MIR Burst Size as a function of MIR for GbE ports

Figure 6-39 MIR Burst Size as a function of MIR for FE ports

Figure 6-40 MIR Burst Size as a function of MIR for GbE ports


TraverseEdge 100 User Guide, Section 6: Configuring EthernetConfigure Strict-Port Policing

The actual MBS used on a port will be the larger of one of the following values: • The value that the user provisioned for the port. • The minimum MBS corresponding to the MIR that the user provisioned for the

port.

For example, if the MIR on a GbE port is set to 500 Mbps, the minimum MBS value is 100 KBytes. So even if the user leaves MBS at its default value of 64 KBytes, or provisions it to a lower value of 32 KBytes, the system actually implements MBS for that port to allow a burst of up to 100 KBytes. This value is not directly viewable by the user.

Configure Strict-Port Policing

Configure MIR and MBS parameters when you configure the Advanced Parameters for Ethernet equipment parameters on the TE-100 shelf. See Chapter 2—“Configuring Ethernet Equipment,” Configure Advanced Parameters of Ethernet Ports, page 6-15.

Class of Service

Ethernet class of service refers to three bits within a four byte IEEE 802.1Q (VLAN) header used to indicate the priority of the Ethernet frame as it passes through a switched network. The priority bits in the IEEE 802.1Q header are referred to as the IEEE 802.1p bits. These three priority bits allow for eight classes of service.

Classifier Template Guidelines

TE-100 Classifier templates are created on the TransNav server or directly on a TE-100 node. All TE-100 Classifier templates that are created directly on the TE-100 node are automatically synchronized to the TransNav server.

Each TE-100 Classifier template maps each possible 802.1p value (0 through 7) to a Class of Service (queue). Depending on the Queuing Policy of the Egress port, there are up to three possible classes of services: 1, 2, and 3. By default, the “default” TE-100 Classifier template maps every 802.1p value to CoS=1.

You can assign a specific TE-100 (TE-100) Classifier template to each port. The classifier is then used by all services on that port. By default, a port has the “default” TE-100 (TE-100) Classifier template.

TransNav supports the creation of up to 12 TE-100 Classifier templates.

You can edit a Classifier template to change the mapping of 802.1p values to CoS and to synchronize the edited template. The new values shall take effect with no interruption to any activated services using the template.

You cannot delete a Classifier template if there are any provisioned or activated Ethernet services currently using that Classifier template.

You can specify, for any one port an assumed 802.1p value to be applied to all arriving untagged packet for classification purposes. The system assigns to the packet the CoS values that would result from mapping that 802.1p value through the TE-100 Classifier template on the port. By default, the assumed 802.1p value for untagged packets shall be 0 which means all untagged traffic goes to Cos1.


Chapter 7 Ethernet Traffic Management on the TE-100Create TE-100 Classifier Templates

Create TE-100 Classifier Templates

Use this procedure to help create a classifier template on the TransNav server.

Table 6-26 Create a TE-100 Classifier Template

Step Procedure

1 From the Admin menu, click Classifiers. The Classifiers dialog box appears.

Figure 6-41 Classifiers Dialog Box

2 Click Add to add a new classifier to the classifier list. The Classifier Configuration dialog box appears.

Figure 6-42 Classifier Configuration Dialog Box

3 Enter a name for the classifier in the Name field. Enter a unique name for the service. Use alphanumeric characters and spaces only. Do not use any other punctuation or special characters.

4 Configure the class of service (CoS) for each priority level.

Priority {0 | 1 | 2 | 3 | 4 | 5 | 6 | 7} CoS. • 1 for CoS 1• 2 for CoS 2• 3 for CoS 3

5 Click OK to close the dialog box and return to the Classifiers dialog box.


TraverseEdge 100 User Guide, Section 6: Configuring EthernetQueuing Policy

Queuing Policy Queuing policy is a mechanism for specifying the treatment of packets that are queued to be transmitted on an egress port. The TE-100 supports up to three queues that correspond directly to classes of service (CoS1, CoS2, CoS3). Packets of the same CoS are queued on the same queue.

Queuing policy for an Ethernet port or an EOS port is determined by the Queuing Policy parameter. Configure the Queuing Policy of an Ethernet port or EOS port during the configuration process.• See Section 6—Creating Ethernet Services, Chapter 2—“Configuring Ethernet

Equipment,” Configure Ethernet Ports, page 6-13.• Section 6—Creating Ethernet Services, Chapter 3—“Ethernet Over SONET or

SDH (EOS),” , page 6-25.

In the Queuing Policy parameter, specify how the queues are managed. Use one of the following policies: • FIFO, page 6-80• Priority, page 6-81• Weighted Fair Queuing, page 6-81

FIFO First-in-first-out. All FE line-side ports are FIFO only. GBE line side ports also have this option. Use this queuing policy to schedule all packets for transmission based on the FIFO algorithm. All traffic uses CoS1. For GBE ports, optionally configure whether shaping should be employed using the following parameters. • FIFO Shape Enable. If the value in Queuing Policy is FIFO, specify if the system

will use the number in the FIFO Shaping Rate parameter to shape the traffic being transmitted onto the port.

• FIFO Shaping Rate. If the FIFO Shaping Rate is enabled, specify a number between 1 and 1000 Mbps.

6 In Synchronize Template dialog box, click Yes to propagate new classifier template information to all nodes in the network.

Figure 6-43 Synchronize Template Dialog Box

7 Click Done to close the Classifier dialog box and return to the main GUI screen.

8 The Create a TE-100 Classifier Template procedure is complete.

Table 6-26 Create a TE-100 Classifier Template (continued)

Step Procedure


Chapter 7 Ethernet Traffic Management on the TE-100Weighted Fair Queuing

Priority Only EOS ports and GBE ports have this option. Use this queuing policy to schedule all packets for transmission based on strict priority, using three priorities: high, medium, low. Highest priority traffic uses CoS1. Medium priority traffic uses CoS2. Low priority traffic uses CoS3.

Higher priority queues always send queued packets. Only when all higher priority queues are empty does the scheduler look for a packet on a lower priority queue. Typical application is voice vs. data: voice requires low latency and should get absolute priority over data, i.e. whenever there is a voice packet, system picks it over a data packet. Note that lower priorities can be starved (i.e., if voice traffic completely fills the output port, data traffic is never transmitted).

There are no additional parameters to configure to use with Priority queuing.

Weighted Fair Queuing

Only EOS ports and GBE ports have this option. Use this queuing policy to guarantee a specific amount of the port’s bandwidth when there is congestion on the port. WFQ uses three classes of service and the guarantees are specified as weights. If the value in Queuing Policy parameter is WFQ, specify the weights in the three WFQ CoS Weight {1 | 2 | 3 } parameters. • WFQ CoS 1 Weight. Weighted queuing policy of CoS1. Enter a number between

1 and 100 to determine the proportion of bandwidth on this port for CoS1. The default value is 0 which means packets with the CoS1 have no priority in relation to the other classes of service.

• WFQ CoS 2 Weight. Weighted queuing policy of CoS2. Enter a number between 1 and 100 to determine the proportion of bandwidth on this port for CoS2. The default value is 0 which means packets with the CoS2 have no priority in relation to the other classes of service.

• WFQ CoS 3 Weight. Weighted queuing policy of CoS3. Enter a number between 1 and 100 to determine the proportion of bandwidth on this port for CoS3. The default value is 0 which means packets with the CoS3 have no priority in relation to the other classes of service.

The scheduler uses these weights to allocate bandwidth on the port to each class of service. When there is no congestion, every CoS sends all queued packets. For example: weights 10, 25, 0, (35 units). In times of congestion, CoS 1 traffic is guaranteed to get at least 28.6% (10/35) of bandwidth on the port. CoS 2 is guaranteed 71.4% (25/30). CoS 3 is not guaranteed any.

Any bandwidth that is guaranteed for a queue but not actually needed by that queue is available for any other queue to use. For example, CoS 2, though guaranteed an allocation of 71.4%, is only transmitting enough data to use up 20%. That leaves approximately 50% of the bandwidth of the port available for other classes to use. In this case, the scheduler distributes that unclaimed 20% approximately evenly among any queues that are already using up their entire guarantee. In particular, CoS 3, which has no guarantee, gets some of the unclaimed bandwidth from CoS 2.


TraverseEdge 100 User Guide, Section 6: Configuring EthernetMarking Packets

Marking Packets

Whenever the system creates a new VLAN tag (either a Customer tag or a Service tag), configure the 3-bit value to insert in the Priority (802.1p) field for packets exiting each class of service. Configure the following parameters when you configure Ethernet equipment on the system (Chapter 2—“Configuring Ethernet Equipment,” page 6-5):• Egress Priority CoS1. Enter a priority value of 0, 1, 2, 3, 4, 5, 6, or 7. By industry

standard: 7 means highest priority, 0 means lowest priority.• Egress Priority CoS2. Enter a priority value of 0, 1, 2, 3, 4, 5, 6, or 7. By industry

standard: 7 means highest priority, 0 means lowest priority.• Egress Priority CoS3. Enter a priority value of 0, 1, 2, 3, 4, 5, 6, or 7. By industry

standard: 7 means highest priority, 0 means lowest priority.


SECTION 7 APPENDICESSECTION 7APPENDICES

Contents

Appendix AInstallation and Commissioning Checklists

Power System Hardware Installation Checklist. . . . . . . . . . . . . . . . . . . . . . . . 7-2Hardware Installation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3Alarm Cabling Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4Timing Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6PDAP-15A DC/DC Power Cabling Checklist. . . . . . . . . . . . . . . . . . . . . . . . . . 7-7TE-100-AD/DC Power Cabling Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-10Management Interface Cabling Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-12Node Start-up and Commissioning Checklist . . . . . . . . . . . . . . . . . . . . . . . . . 7-13Network Cabling Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-16

Appendix BProvisioning Checklists

Before You Start Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-18Network Configuration Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-19Equipment Configuration Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-20TDM Service Creation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-21Ethernet Service Creation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-23

Appendix CAcronyms and Abbreviations

A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-25B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-26C . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-26D . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-28E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-28F . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-29G . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-30H . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-31I . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-31J. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-32K . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-32L . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-32M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-33N . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-34O . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-35P . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-36Q . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-37


TraverseEdge 100 User Guide, Section 7 Appendices

R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-37S . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-38T. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-39U . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-40V . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-40W . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-41X . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-41SONET/SDH Channel Capacities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-43Non - Synchronous Digital Hierarchies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-43SDH Containers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-43VT Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-44


SECTION 7APPENDICES

Appendix A Installation and Commissioning Checklists

Introduction This chapter includes checklists to provide the basic steps necessary to complete TraverseEdge 100 (TE-100) system hardware installation, cabling and initial configuration steps. Each step references the related detail-level procedure for additional information.• Power System Hardware Installation Checklist, page 7-2• Hardware Installation Checklist, page 7-3• Alarm Cabling Checklist, page 7-4• Timing Checklist, page 7-6• PDAP-15A DC/DC Power Cabling Checklist, page 7-7• TE-100-AD/DC Power Cabling Checklist, page 7-10• Management Interface Cabling Checklist, page 7-12• Node Start-up and Commissioning Checklist, page 7-13• Network Cabling Checklist, page 7-16


TraverseEdge 100 User Guide, Section 7: AppendicesPower System Hardware Installation Checklist

Power System Hardware Installation Checklist

Basic precautions for electrostatic discharge protection, electrical and fiber optic cabling are provided in Section 3—Installation and Configuration, Chapter 2—“Precautions,” page 3-3.

All power system hardware installation detail-level procedure references are to Section 3—Installation and Configuration, Chapter 4—“Hardware Installation,” page 3-27. Required equipment and tools are also provided as part of this chapter.

Table 7-1 Power System Hardware Installation Checklist

Step Description and Procedure Reference ✔

1 Install the power system hardware (e.g., PDAP-15A) using thread-forming screws and ground hardware to a properly grounded telco rack.

Note: Installation of power system hardware in a 23-inch600 mm or ETSI rack requires standard conductive plated rack adapters. Refer to Section 3—Installation and Configuration, Chapter 4—“Hardware Installation,” Rack Adapter Installation, page 3-30.

Power System (PDAP-15A). Install the power system at the top of the equipment rack. The detail-level installation procedure is in Section 3—Installation and Configuration, Chapter 4—“Hardware Installation,” Power System (PDAP-15A) Installation, page 3-27.

2 All Power System Hardware Installation Checklist steps are complete.


Appendix A Installation and Commissioning ChecklistsHardware Installation Checklist

Hardware Installation Checklist


Note: Required equipment and tools are also provided as part of each chapter.

Table 7-2 Hardware Installation Checklist


1 Is power system hardware installation complete?• Yes. Go to Step 2.• No. Refer to the Power System Hardware Installation

Checklist, page 7-2.

2 TE-100 Shelf. Install the first TE-100 shelf below the power system.

Detail-level installation procedures are in Section 3—Installation and Configuration, Chapter 4—“Hardware Installation”.

If rack adapter installation, see Rack Adapter Installation, page 3-30, then Hardware Installation, page 3-28.

3 All Hardware Installation Checklist steps are complete.


TraverseEdge 100 User Guide, Section 7: AppendicesAlarm Cabling Checklist

Alarm Cabling Checklist

Basic precautions for electrostatic discharge protection, electrical and fiber optic cabling are provided in Section 3—Installation and Configuration, Chapter 2—“Precautions,” page 3-3. Cable management is provided in Section 3—Installation and Configuration, Chapter 12—“Cable Management,” page 3-87.

All alarm cabling detail-level procedure references are to Section 3—Installation and Configuration, Chapter 5—“Alarm Interface Cabling,” page 3-31. Required equipment and tools are also provided as part of each cabling chapter.

.

Important: Always wear a properly grounded ESD wrist strap when making connections at the fuse alarm panel (e.g., PDAP-15A) and TE-100 backplane. Plug the ESD wrist strap into the ESD jack provided on the fan assembly, backplane, or other confirmed source of earth ground.

Table 7-3 Alarm Cabling Checklist


1 Connect Fuse Alarm Panel (Optional PDAP-15A) Power Alarm Wires. Connect power alarm wires at the back of the fuse alarm panel and to a central office power alarm panel as required.

The detail-level alarm cabling procedure is in Section 3—Installation and Configuration, Chapter 5—“Alarm Interface Cabling,” PDAP-15A Power Alarm Connections, page 3-36.

2 Connect Fuse Alarm Panel (Optional PDAP-15A) Fuse Alarm Wires. Connect fuse A and B alarm wires on the fuse alarm panel and to a central office fuse alarm panel as required.

The detail-level alarm cabling procedure is in Section 3—Installation and Configuration, Chapter 5—“Alarm Interface Cabling,” PDAP-15A Fuse Alarm Connections, page 3-37.

3 Connect Fuse Alarm Panel (Optional PDAP-15A) Visual Alarm Input Wires. Connect visual alarm input wires at the back of the fuse alarm panel as required.

The detail-level alarm cabling procedure is located in Section 3—Installation and Configuration, Chapter 5—“Alarm Interface Cabling,” PDAP-15A Visual Alarm Input Connections, page 3-38.


Appendix A Installation and Commissioning ChecklistsAlarm Cabling Checklist

4 Connect Visual Alarm Output Wires. Terminate visual alarm output wires at the CRITICAL, MAJOR, MINOR wire-wrap posts on the backplane and at the central office visual alarm panel, if not connected to a PDAP-15A.

Detail-level alarm cabling procedures are located in Section 3—Installation and Configuration, Chapter 5—“Alarm Interface Cabling,” Visual Alarm Output Connections, page 3-32.

5 Connect Audible Alarm Output Wires. Terminate audible alarm output wires at the AUDIBLE wire-wrap posts on the main backplane and to the central office audible alarm panel.

Detail-level alarm cabling procedures are located in Section 3—Installation and Configuration, Chapter 5—“Alarm Interface Cabling,” Audible Alarm Output Connections, page 3-33.

6 Connect Environmental Alarm Input Wires. Terminate environmental alarm input wires at the ENV IN and RTN wire-wrap posts on the main backplane and at the equipment being monitored.

The location of these wire-wrap posts on the main backplane are provided in Section 2—Platform Specifications, Chapter 5—“Alarm Interface Specifications,” Environmental Alarm Input Wire-Wrap Posts, page 2-29.

7 Connect Visual or Audible Fail-safe Alarm Wires at each Shelf in the Rack. Terminate fail-safe alarm wires at the FAILSAFE wire-wrap posts on the main backplane and the central office visual or audible alarm panel.

The location of these wire-wrap posts on the main backplane are provided in Section 2—Platform Specifications, Chapter 5—“Alarm Interface Specifications,” Alarm Output Wire-Wrap Posts, page 2-29.

8 Attach clamp-on ferrites around alarm cable bundles. Two ferrites around the cable bundle, one 6-inches152.4 mm from the rack, the other 12 to 18-inches304.8 to 457.2 mm from the rack.

9 All Alarm Cabling Checklist steps are complete.

Table 7-3 Alarm Cabling Checklist (continued)



TraverseEdge 100 User Guide, Section 7: AppendicesTiming Checklist

Timing Checklist


All timing cabling detail-level procedure references are to Section 3—Installation and Configuration, Chapter 6—“Timing Interface Cabling”. Required equipment and tools are also provided as part of each cabling chapter.

.


Table 7-4 Timing Checklist


1 Connect T1 Timing Wires. Connect input and output timing wires from the central office SASE T1 or Composite Clock timing source to the TE-100 main backplane T1/E1 or CC2M wire-wrap posts.

Detail-level timing interface procedures are located in Section 3—Installation and Configuration, Chapter 6—“Timing Interface Cabling”:• External Timing Interface Input, page 3-40• External Timing Interface Output, page 3-41

2 All Timing Checklist steps are complete.


Appendix A Installation and Commissioning ChecklistsPDAP-15A DC/DC Power Cabling Checklist

PDAP-15A DC/DC Power Cabling Checklist


All power cabling detail-level procedure references are to Section 3—Installation and Configuration, Chapter 7—“Power Cabling Procedures—DC/DC.” Required equipment and tools are also provided as part of each chapter.

.



Table 7-5 PDAP-15A DC/DC Power Cabling Checklist


1 Connect Battery and Battery Return Distribution Cabling. Connect battery and battery return distribution cabling from the back of the PDAP-15A to the TE-100 backplane power terminals (or to the front panel, if the power has been carried there. If so, see Chapter 7—“Power Cabling Procedures—DC/DC,” Power Cabling to the Front Panel (Optional), page 3-50.

Detail-level battery distribution cabling procedures are located in Chapter 7—“Power Cabling Procedures—DC/DC”:• PDAP Battery Distribution Cabling, page 3-47• PDAP Battery Return Distribution Cables, page 3-49

2 Connect Central Office Battery “A” and “B” Supply Cabling. Connect central office battery “A” and “B” supply cabling from the battery distribution fuse bay (BDFB)—or other central office battery source—to PDAP-15A battery supply terminal lugs.

WARNING! Ensure battery supply cables are not connected to central office battery source before beginning this procedure to avoid personal injury.

The detail-level battery supply cabling procedure is located in Battery Supply Cabling to the PDAP-15A, page 3-53.


TraverseEdge 100 User Guide, Section 7: AppendicesPDAP-15A DC/DC Power Cabling Checklist

3 Connect Central Office Battery Return “A” and “B” Supply Cabling. Connect central office battery return “A” and “B” supply cabling from the battery return bus bar (or other central office battery return source) to PDAP-15A battery return supply terminal lugs.

The detail-level battery return supply cabling procedure is located in Battery Return Supply Cabling to the PDAP-15A, page 3-54.

4 Attach clamp-on ferrites around Battery cables at the rack. Two ferrites around A feed and two ferrites around B feed (-48 and RTN) cables 6-inches152.4 mm from the rack.

5 Connect Battery and Battery Return Supply Cables to the Central Office Source. Connect battery and battery return supply cables to the central office source following local procedures or arrange for a local central office technician to make these connections.

WARNING! Complete continuity testing before connecting battery and battery return cables to the central office source.

WARNING! Before connecting the supply cables, go to the front of the PDAP and verify that all PDAP-15A GMT fuse positions are empty or contain dummy fuses.

The detail-level supply cabling to the central office source procedure is located in Connect Supply Cables to the External Power Source, page 3-55.

6 Attach clamp-on ferrites around Battery cables at the CO. At the battery filter, attach one clamp-on ferrite around A feed and one ferrite around B feed (_in and _out) cables 6-inches152.4 mm from the filter.

Table 7-5 PDAP-15A DC/DC Power Cabling Checklist (continued)



Appendix A Installation and Commissioning ChecklistsPDAP-15A DC/DC Power Cabling Checklist

7 Verify Polarity and Voltage. Confirm polarity between the battery and battery return supply connections at the PDAP-15A. Measure the voltage present at the NEG VDC “A” and “B” input lugs on the PDAP.

Procedures are located in Chapter 7—“Power Cabling Procedures—DC/DC”:• Verify Polarity, page 3-56• Verify Voltage, page 3-56

WARNING! Verify that all PDAP-15A GMT fuse holders are empty before or contain dummy fuses before verifying polarity or voltage.

8 All PDAP-15A DC/DC Power Cabling Checklist steps are complete.

Table 7-5 PDAP-15A DC/DC Power Cabling Checklist (continued)



TraverseEdge 100 User Guide, Section 7: AppendicesTE-100-AD/DC Power Cabling Checklist

TE-100-AD/DC Power Cabling Checklist

Basic precautions for electrostatic discharge protection, electrical and fiber optic cabling are provided in Section 3—Installation and Configuration, Chapter 2—“Precautions,” page 3-3. Cable management is provided in

All power cabling detail-level procedure references are to Section 3—Installation and Configuration, Chapter 8—“Power Cabling Procedures—AC/DC.” Required equipment and tools are also provided as part of each chapter.

.


Important: Always wear a properly grounded ESD wrist strap when making connections at the power supply and TE-100 backplane. Plug the ESD wrist strap into the ESD jack provided on the fan assembly, backplane, or other confirmed source of earth ground.

Table 7-6 TE-100-AC/DC Power Cabling Checklist


1 Connect AC Power Cord to AC Power Supply Brick. Connect the AC power cord to the inlet on the power supply brick.

2 Connect Battery and Battery Return Distribution Cabling—Single or Redundant. Connect battery and battery return "A" distribution cabling from the DC output cable to the TE-100 backplane power terminals (or to the front panel, if the power has been carried there. If so, see Chapter 8—“Power Cabling Procedures—AC/DC,” Power Cabling to the Front Panel (Optional), page 3-60.)

For redundant power configuration—with a second AC/DC power converter unit—connect battery and battery return "B" distribution cable wires.

3 For a redundant power configuration, with a second AC/DC power converter unit, repeat Steps 2–4 for the battery and battery return "B" distribution cable wires.

Note: Force10 recommends you put the two AC/DC power converter units on separate circuit breakers.

4 (SDH network only) Attach clamp-on ferrites around power cables at the rack. One ferrite (1 turn) around A feed and one ferrite around B feed (-48 and RTN) cables 6-inches (152.4 mm) from the rack.


Appendix A Installation and Commissioning ChecklistsTE-100-AD/DC Power Cabling Checklist

5 Connect AC Power Cord to the AC Power Outlet Source. Connect the AC power cord three-prong plug into the AC power outlet.

WARNING! Complete continuity testing before connecting the power cord to the source.

6 Verify Polarity and Voltage. Confirm polarity between the power and power return supply connections at the TE-100. Measure the voltage present at the NEG VDC “A” and “B” input.

7 All TE-100-AC/DC Power Cabling Checklist steps are complete.

Table 7-6 TE-100-AC/DC Power Cabling Checklist (continued)



TraverseEdge 100 User Guide, Section 7: AppendicesManagement Interface Cabling Checklist

Management Interface Cabling Checklist

Basic precautions for electrostatic discharge protection, electrical and fiber optic cabling are provided in Section 3—Installation and Configuration, Chapter 2—“Precautions,” page 3-3. Management interface cabling procedures are in Section 3—Installation and Configuration, Chapter 9—“Management Interfaces Cabling”.

Required equipment and tools are also provided as part of each cabling chapter.


Table 7-7 Management Interface Cabling Checklist


1 Connect RS-232 DCE Interface Cabling. Connect RS-232 interface cabling from a laptop, terminal, or an external modem to the RJ-45 connector on the system module front panel.

The detail-level RS-232 interface connection procedure is located in Chapter 9—“Management Interfaces Cabling,” Connect the RS-232 DCE Interface, page 3-64.

2 Connect DCN Ethernet Cabling. Connect DCN Ethernet cabling from the LAN/WAN network device to the (ETHERNET) RJ-45 connector on the interface module front panel.

The detail-level DCN Ethernet interface connection procedure is located in Chapter 9—“Management Interfaces Cabling,” Connect the DCN Ethernet Interface, page 3-66.

3 Connect RS-232 DTE Interface Cabling. Connect RS-232 interface cabling from an external modem to the RS-232 RJ-45 connector on the front panel of the interface module RJ-45 using an RJ-45 to DB-25 adaptor.

The detail-level RS-232 interface connection procedure is located in Chapter 9—“Management Interfaces Cabling,” Connect the RS-232 DTE Interface, page 3-67.

4 All Management Interface Cabling Checklist steps are complete.


Appendix A Installation and Commissioning ChecklistsNode Start-up and Commissioning Checklist

Node Start-up and Commissioning Checklist

Basic precautions for electrostatic discharge protection, electrical and fiber optic cabling are provided in Section 3—Installation and Configuration, Chapter 2—“Precautions,” page 3-3. and Chapter 3—“Common Procedures,” Inserting and Removing Modules.

All TE-100 node start-up and configuration detail-level procedure references are to Chapter 10—“Node Start-up and Initial Configuration,” page 3-69. Required equipment and tools are also provided as part of start-up and module placement chapters.


WARNING! Follow all directions and warning labels when working with optical fibers. Always wear eye protection when working with optical fibers. Never look directly into the end of a terminated or unterminated fiber or connector as it may cause eye damage.

Table 7-8 Node Start-up and Configuration Checklist


1 Switch on Power to the shelf (node). Battery “A” and “B” PDAP-15A fuse holders are located on the front of the PDAP. Install an operable fuse for the installed shelf. Leave the other fuse holders empty.

Refer to Turn On Power to the Shelf, page 3-56.

2 Place the active system module in the shelf.

Important: The power LED is steady on “green” indicating that the system module has power. The steady on “green” Active/Standby LEd indicates that it is the active system module. Initial configuration is done through the active system module via the CLI. Leave the second system module in the unlocked position, as you will insert it later.

3 Connect your Laptop to the Active GCM RS-232 Interface. Connect your laptop to the active GCM RS-232 interface (DB-9) connector using a standard straight-through serial port cable. Open up VT100 emulation software on your laptop and create your terminal emulation session.

The detail-level initial configuration procedure for the following steps is provided in Chapter 10—“Node Start-up and Initial Configuration,” Node Start-Up and Initial Configuration, page 3-74.


TraverseEdge 100 User Guide, Section 7: AppendicesNode Start-up and Commissioning Checklist

4 Logon to the TransNav Management System Command Line Interface (CLI). Enter a login (admin) and password (admin) to access the node for initial configuration.

5 Begin Commissioning Command Sequence:Establish Node Name and Node IP Address. Use the exec node commission command to establish the node name (node-id) and node IP address (node-ip) for the TE-100 node.

Note: The IP address parameters required for node commissioning are provided in Table 3-50 Node Start Up and Initial Configuration, page 3-74.

6 Establish Node Technology Standard. Use the exec node commission command to establish the technology standard (ITU or ANSI) for the TE-100 node.

7 Enter the optical bandwidth. Use the exec node commission command to establish the bandwidth OPT1 for an OC3 SFP interface, OPT2 for an OC12 SFP interface, and OPT3 for an OC48 SFO interface.

8 Restart the Node. Use the exec node restart command to set the node IP address and to make the node operational.

9 Set the DCN parameters.Is the node connected to a DCN?• Yes. Enter the DCN IP information:

Type: set node ip bp-dcn-ip aaa.bbb.ccc.ddd<Enter>Type: set node ip bp-dcn-gw-ip aaa.bbb.ccc.ddd<Enter> Type: set node ip bp-dcn-ip-mask aaa.bbb.ccc.ddd<Enter> where: aaa.bbb.ccc.ddd is the correct IP address from your network administrator.


Table 7-8 Node Start-up and Configuration Checklist (continued)



Appendix A Installation and Commissioning ChecklistsNode Start-up and Commissioning Checklist

10 Set the EMS IP information.Is the EMS server is located across a router?• Yes. Enter the EMS IP information:

Type: set node ip ems-ip aaa.bbb.ccc.ddd<Enter>Type: set node ip ems-gw-ip aaa.bbb.ccc.ddd<Enter>Type: set node ip ems-ip-mask aaa.bbb.ccc.ddd<Enter>where:aaa.bbb.ccc.ddd is the correct IP address from your network administrator.


11 Change the Admin Password. For node security use the exec user change-password command to change the admin password after initial node configuration is complete.

12 Exit the CLI. Exit your terminal emulation session.

13 Place the second system module in the slot and lock it.Do you have a second system module?• Yes.

Important: The Active/Standby LED on the standby system module flashes amber while it is synchronizing with the active system module.

Important: Wait for synchronization to complete. The Active/Standby LED flashes green indicating that it is the standby system module and that synchronization is complete.• No. Go to the next step.

14 Place 1-slot Wide Blank Faceplates. Place 1-slot wide blank faceplates in the empty TE-100 slot to ensure EMI protection and proper cooling.

15 All Node Start-up and Configuration Checklist steps are complete.

Table 7-8 Node Start-up and Configuration Checklist (continued)



TraverseEdge 100 User Guide, Section 7: AppendicesNetwork Cabling Checklist

Network Cabling Checklist


Note: Required equipment and tools are also provided as part of each cabling chapter.

.


WARNING! Follow all directions and warning labels when working with optical fibers. Always wear eye protection when working with optical fibers. Never look directly into the end of a terminated or unterminated fiber or connector as it may cause eye damage.

Table 7-9 Network Cabling Checklist


1 Complete DS1, DS3, E1, E3 and/or 10/100BaseT Cabling. Complete network cabling based on the type of ECM installed.

Detail-level cabling procedures are in:• Chapter 11—“Network Interface Cabling,” DS1/E1 Cabling

Procedure, page 3-81• Chapter 11—“Network Interface Cabling,” DS3/E3 Cabling

Procedure, page 3-82• Chapter 11—“Network Interface Cabling,” 10/100BaseTX

Fast Ethernet Cabling Procedure, page 3-83

2 Connect Fiber Optic Cables. Connect fiber optic cables from the central office optical distribution frame (ODF) or fiber optic patch panel to the TE-100 fiber optic SFPs.

The detail-level fiber optic cabling procedure is in Chapter 11—“Network Interface Cabling,” Fiber Optic Cabling Procedures, page 3-84.

For information on SONET optics, refer to Section 2—Platform Specifications, Chapter 4—“SONET/STM Ports Specifications,” Optical Interface Specifications (Summary), page 2-26.

3 All Network Cabling Checklist steps are complete.


SECTION 7APPENDICES

Appendix B Provisioning Checklists

Introduction Use the checklists in this appendix to bring a TraverseEdge 100 (TE-100) network into service and to create services for transport over the network using the TransNav management system graphical user interface (GUI). • Before You Start Provisioning, page 7-18• Network Configuration Checklist, page 7-19• Equipment Configuration Checklist, page 7-20• TDM Service Creation Checklist, page 7-21• Ethernet Service Creation Checklist, page 7-22

Successfully completing each checklist assumes that the tasks in the previous checklist are complete.

Each step references the related detail-level procedure for additional information. All provisioning detail-level procedure references are to the Traverse Provisioning Guide.


TraverseEdge 100 User Guide, Section 7: AppendicesBefore You Start Provisioning

Before You Start Provisioning

Complete the following tasks before you start provisioning your network.

Wherever possible, a table listing requirements and guidelines precedes each procedure. See each topic for specific requirements to the task on which you are working.



Hardware


Chapter 4—“Protected Network Topologies,” page 5-33Section 2—Platform Specifications, Chapter 9—“Network Topologies,” page 2-43


Chapter 1—“Installation and Commissioning Overview,” page 1-1 Section 3—Installation and Configuration, Chapter 1—“Installation Overview,” page 3-1

Software

The TransNav Primary management server is constructed and the management software is installed. The server is initialized and started.


The TransNav Secondary server(s) is constructed and the management software is installed. The server(s) is/are initialized and started.



Commissioning,” page 11-1Section 3—Installation and Configuration, Chapter 10—“Node Start-up and Initial Configuration,” page 3-69

You are logged into the graphical user interface. TransNav Management System GUI Guide, Chapter 3—“Starting the Graphical User Interface,” page 2-17


Appendix B Provisioning ChecklistsNetwork Configuration Checklist


Network Configuration Checklist

Use this checklist as a guide to more detailed procedures. Each step references the relevant detailed procedure.

Table 7-11 Network Configuration Checklist


1 Review the information in Before You Start Provisioning, page 7-18 before you start with this checklist.

2 Arrange Node(s) in Map View. The GUI opens in Map View. TE-100 node(s) and optical links are autodiscovered and displayed in the upper left corner of Map View. Click and drag the node(s) to the correct area(s) on the map to best represent your network.

From the File menu, click Save User Preferences.

3 Go to Shelf View. Double-click a node to go to Shelf View. The GUI auto discovers all modules. Shelf View displays the node and modules exactly like the physical installation in the central office.

The node is already commissioned.

4 Configure the Node. In Shelf View, click the Config tab to display the Node Configuration dialog box.

See Section 4—Configuring the Network, Chapter 1—“Configuring the Network,” Configure Node Parameters, page 4-6.

5 Configure External Timing. Set the BITS interface sources for the head-end node.

See Section 4—Configuring the Network, Configure External Timing, page 4-12.

6 Configure Line Timing. Set the timing options in other network nodes.

See Section 4—Configuring the Network, Configure Line Timing, page 4-14.

7 Configure Protection Groups. See one of the following chapters in Section 4—Configuring the Network:• Chapter 3—“Creating a UPSR/SNCP Protection Group,”

page 4-17• Chapter 4—“Creating 1+1APS/MSP Protection Groups,”

page 4-23• Chapter 5—“Creating a 1+1 Optimized Protection Group,”

page 4-27

8 Repeat Steps 3 to Steps 8 for each node in the network.

9 All Network Configuration Checklist steps are complete.

Continue to the Equipment Configuration Checklist, page 7-20.

TraverseEdge 100 User Guide, Section 7: AppendicesEquipment Configuration Checklist

Equipment Configuration Checklist

Use this checklist as a guide to more detailed procedures. Each step references the relevant detailed procedure.

Table 7-12 Module Configuration Checklist


1 Complete the Network Configuration Checklist, page 7-19.

2 Go to Shelf View and Select a Module. Double-click a node to go to Shelf View. The GUI auto discovers all modules. Shelf View displays the node and modules exactly like the physical installation in the central office. Click a module from Shelf View.

3 Configure the Module. In Shelf View, click the system module, then click the Config tab to display the Card Configuration screen.

4 Repeat Step 3 for the interface module.

5 Repeat Steps 2 and 4 for each node in the network.

6 All Module Configuration Checklist steps are complete.

Continue to the TDM Service Creation Checklist, page 7-21.


Appendix B Provisioning ChecklistsTDM Service Creation Checklist

TDM Service Creation Checklist

See Section 5—Creating TDM Services, page 5-1 for detailed information on creating specific services.

Table 7-13 Service Creation Checklist


1 Add the Service. On the Service tab, select the service type and click Add

2 Configure Service Parameters. Enter the name of the service and configure other general parameters.

3 Select the Service Endpoints. Set the endpoints for this service. Click the Source row in the Endpoint column to display the Choose an Endpoint dialog box. Select the source and click Done to close the dialog box.

Click the Destination row, select the endpoint in the dialog box and click Done.

4 Configure Service Protection. Click the Protection parameter field to display the Protection dialog box. Select the type of protection for the service by clicking on the tabs in the dialog box.

Configure any applicable parameters.

Click Done to close the dialog box and return to the Create Service tab.

5 Configure Other Service Characteristics. Click the Advanced button to display the Advanced Parameters dialog box.

Configure the characteristics of the service.

If this is an end-to-end service, configure the characteristics of the connection throughout the network.

6 Select the Path for End-to-End Services. If Strict= , explicitly select the service route between defined endpoints.

Click the plus sign in the Add column to add another hop to the service.

Click the minus sign in the Remove column to remove a hop.

Click Apply to add the provisioned service to the service list and return to the Service tab.

7 Activate the Service. On the Service tab, click the service to select it, right-click for the menu, and click Activate.


TraverseEdge 100 User Guide, Section 7: AppendicesEthernet Service Creation Checklist

Ethernet Service Creation Checklist

See Section 6—Creating Ethernet Services, page 6-1 for detailed information on creating specific services.

Table 7-14 Service Creation Checklist


1 Install and connect equipment. Make sure the equipment is installed and connected according to the network plan. See• Equipment Configuration Checklist, page 7-20• Network Configuration Checklist, page 7-19

2 Configure optical equipment and protection groups.See Section 4—Configuring the Network:• Chapter 3—“Creating a UPSR/SNCP Protection Group,”

page 4-17• Chapter 4—“Creating 1+1APS/MSP Protection Groups,”

page 4-23• Chapter 5—“Creating a 1+1 Optimized Protection Group,”

page 4-27

3 Configure Ethernet equipment. See Section 6—Creating Ethernet Services, Chapter 2—“Configuring Ethernet Equipment,” page 6-5.

4 Optionally, configure Ethernet features. See Section 6—Creating Ethernet Services, Chapter 2—“Configuring Ethernet Equipment,” page 6-5.

5 Configure Ethernet equipment. See Section 6—Creating Ethernet Services, Chapter 2—“Configuring Ethernet Equipment,” page 6-5.

6 Optionally, configure Ethernet features. See Section 6—Creating Ethernet Services, Chapter 2—“Configuring Ethernet Equipment,” page 6-5

7 Create and activate Ethernet transport services. See Section 6—Creating Ethernet Services, Chapter 3—“Ethernet Over SONET or SDH (EOS),” EOS Definition, page 6-25

8 Create EOS ports. Section 6—Creating Ethernet Services, Chapter 3—“Ethernet Over SONET or SDH (EOS),” EOS Definition, page 6-25.

9 Optionally, configure EOS features. See Section 2—Creating Ethernet Services, Chapter 4—“Link Capacity Adjustment Scheme,” page 2-37.


Appendix B Provisioning ChecklistsEthernet Service Creation Checklist

10 Configure Ethernet Services. See Section 6—Creating Ethernet Services, Chapter 6—“Ethernet Services,” page 6-57.

11 Configure Ethernet Traffic Management. See Section 6—Configuring Ethernet, Chapter 7—“Ethernet Traffic Management on the TE-100,” page 6-71.

Table 7-14 Service Creation Checklist (continued)



TraverseEdge 100 User Guide, Section 7: AppendicesEthernet Service Creation Checklist


SECTION 7APPENDICES

Appendix C Acronyms and Abbreviations

Acronyms and Abbreviations

Acronyms are formed from the initial letter or letters of each of the successive parts or major parts of a compound term. Force10 Networks uses the following set of acronyms and abbreviations in product literature and documentation.

AAcronym Description

AAL ATM Adaptation Layer

ABR Available Bit Rate

ACL Access Control list

ACO Alarm Cut-Off

ACR Actual Cell Rate

ADM Add-Drop Multiplexer

ADP Actual Departure Potential

ADT Actual Departure Time

AINI ATM Internetworking Interface

AID Access Identifier

AIS Alarm Indication Signal

ALS Automatic Laser Shutdown

AMI Alternate Mark Inversion

APS Automatic Protection Switching

APSBF Automatic Protection Switching Byte Failure

APSCM Automatic Protection Switching Channel Mismatch

APSMM Automatic Protection Switching Mode Mismatch

ARP Address Resolution Protocol (Proxy ARP)

ASIC Application-Specific Integrated Circuit

ASP Applications Service Provider


TraverseEdge 100 User Guide, Section 7: AppendicesB

B

C

ATM Asynchronous Transfer Mode

AU Administrative Unit

AWG American Wire Gauge

Acronym Description

B3ZS Bipolar 3 Zero Substitution

B8ZS Bipolar 8 Zero Substitution

BBE Background Block Errors

B-DCS Broadband Digital Cross-connect System

BDFB Battery Distribution Fuse Bay

BER Bit Error Rate

BERT Bit Error Rate Tester

BGP4 Broadband Gateway Protocol, version 4

B-ICI B-ISDN Inter-carrier Interface

BIP Bit Interleaved Parity

BITS Building Integrated Timing Supply

BLSR Bi-directional Line Switching Ring

BML Business Management Layer

BNC Bayonet Neill Concelman (BNC Connector)

BPV Bipolar Violation

B-RAS Broadband Remote Access Server

Acronym Description

C Celsius

C2O Cable to Optic

CAC Call Admission Control or Connection Admission Control

CAM Content Addressable Memory

CBR Constant Bit Rate

CBS Committed Burst Size

CC Clear Channel

CCAT Contiguous Concatenation

CDP Contracted Deadline Potential


Appendix C Acronyms and AbbreviationsC

CDV Cell Delay Variation

CDVT Cell Delay Variation Tolerance

CEP Carrier Ethernet Protection

CEPP CEP Pair

CES Circuit Emulation Service

CEV Controlled Environmental Vault

CIR Committed Information Rate

CLE Customer Located Equipment

CLEC Competitive Local Exchange Carrier

CLEI Common Language Equipment Identifier

CLFI Common Language Facility Identification

CLI Command Line Interface

CLLI Common Language Location Identifier

CLR Cell Loss Ratio

cm Centimeter

CO Central Office Environment

COBRA Copper and Optical Broadband Remote Access

COE Central Office or Connection Oriented

CBN Common Bonding Network

CORBA Common Object Request Broker Architecture

CoS Class of Service

COT Central Office Terminal

CP Call Processing

CPE Customer Premise Equipment

C-Plane Control Plane

CPU Central Processing Unit

CRC Cyclic Redundancy Check

CR-LDP Constraint-based Routing Label Distribution Protocol

CSU Channel Service Unit

CTD Cell Transfer Delay

CTP Connection Termination Point

CV Code Violation


TraverseEdge 100 User Guide, Section 7: AppendicesD

D

E

C-VLAN Customer Virtual Area Network

CWDM Coarse Wavelength Division Multiplexing

Acronym Description

dB Decibel

dBm Decibels relative to milliwatt

D Depth

DCC Data Communications Channel

DCE Data Circuit-terminating Equipment

DCN Data Communications Network

DCS Digital Cross-connect System

DFAD Dual Facility Access Digroup

DHCP Dynamic Host Configuration Protocol

DLC Digital Loop Carrier

DM Degraded Minute

DQ Degraded Quality Level

DS Digital Signal

DS0 Digital Signal Zero (64 Kbps data/voice channel)

DS1 Digital Signal Level 1 (T1 equivalent)

DS3 Digital Signal Level 3 (T3 equivalent)

DSLAM Digital Subscriber Line Access Multiplexer

DSX-1 Digital Signal Level 1 cross connect

DSX-3 Digital Signal Level 3 cross connect

DTE Data Terminal Equipment

DVC Dynamic Virtual Concatenation

DWDM Dense Wavelength Division Multiplexing

DXC Digital Cross Connect

Acronym Description

EAI Enterprise Application Integration


Appendix C Acronyms and AbbreviationsF

F

EAM Environmental Alarm Card

EC-1 Electrical Carrier Level 1 (STS1 equivalent)

ECC Ethernet Control Channel

ECCI Ethernet Control Channel Interface. The IP interface on a single node to which ECCs can be connected.

ECC-UNI Ethernet Control Channel - User to Network Interface. Typically used to manage CPEs.

ECM Electrical Connector Cards

EDFA Erbium-Doped Fiber Amplifiers

EEE Electronic Equipment Enclosure

E-LAN Ethernet Local Area Network

EMI Electromagnetic Interference

EML Element Management Layer

EMS Element Management System

EOC Embedded Operations Channel

EoPDH Ethernet over PDH (Plesiochronous Digital Hierarchy)

EOS Ethernet over SONET

EPL Ethernet Private Line

ERDI Enhanced Remote Defect Indicator

ES Errored Second

ESCON Enterprise Systems Connection

ESD Electrostatic Discharge

ESF Extended Super Frame

ETSI European Telecommunications Standards Institute

EVC Ethernet Virtual Circuit, Ethernet Virtual Connection

EVPL Ethernet Virtual Private Line

EXZ Excessive Zeros

Acronym Description

FAD Facility Access Digroup

FC Failure Count

FCAPS Fault, Configuration, Accounting, Performance, and Security

FCS Frame Check Sequence


TraverseEdge 100 User Guide, Section 7: AppendicesG

G

FDDI Fiber Distributed Data Interface

FDL Facilities Data Link

FDM Frequency Division Multiplexing

FE Far-End or Fast Ethernet

FEBE Far-End Block Error

FEC Forward Error Correction

FEP Far-End Protection

FERF Far-End Receiver Failure

FIB Forwarding Information Base

FIFO First In First Out

FITB Fiber in the Building

FITL Fiber in the Loop

FITR Fiber in the Riser

FPGA Field Programmable Gate Array

FPM Feet per Minute

FPP Fast Pattern Processor

FR Frame Relay

FSAN Full Services Access Network (consortium)

ft Feet

FTP File Transfer Protocol

FTTB Fiber to the Building

FTTC Fiber to the Curb

FTTH Fiber to the Home

Acronym Description

Gb Gigabit

GB Gigabyte

GbE Gigabit Ethernet

Gbps Gigabits per second

GCM General Control Card

GCRA Generic Cell Rate Algorithm

GDLC High-speed Data Link Controller


Appendix C Acronyms and AbbreviationsI

H

I

GFP Generic Framing Procedure

GFR Guaranteed Frame Rate

GHz Gigahertz

GMPLS Generalized Multiprotocol Label Switching

GND Ground (electrical)

GR Generic Requirement

GUI Graphical User Interface

Acronym Description

H Height

HAF High Availability Framework

HALT Highly Accelerated Life Testing

HDB3 High Density Bipolar 3

HEC Header Error Control

HOVC Higher Order Virtual Concatenation

Acronym Description

IAD Interface Access Device

IAS Internet Access Service

ICI ITU-T compliant International Common Identifier of a hardware card

ID Identifier

IDT Inter-DXC Trunk

IEC InterExchange Carrier

IEEE Institute of Electrical and Electronic Engineers

IETF Internet Engineering Task Force

ILEC Incumbent Local Exchange Carrier

I/O Input/Output

in Inches

IP Internet Protocol

IPC InterProcess Control or InterProcessor Control


TraverseEdge 100 User Guide, Section 7: AppendicesJ

J

K

L

IP QoS Internet Protocol Quality of Service

IPTV Internet Protocol Television

IR Intermediate Reach

ISD Idle Signal Detection

ISO International Organization for Standardization

ISP Internet Service Provider

ITU International Telecommunication Union

IWF Interworking Function

Acronym Description

JDK Java Development Kit

JDMK Java Dynamic Management Kit

JRE Java Runtime Environment

Acronym Description

Kb Kilo bit

KB Kilo byte

Kbps Kilo bits per second

kg Kilograms

kHz Kilohertz

km Kilometer

Acronym Description

LAG Link Aggregation Group, also called an Etherchannel

LAN Local Area Network

LBC Laser Bias Current

LBO Line Build Out

lbs Pounds

LC Line Card


Appendix C Acronyms and AbbreviationsM

M

LCAS Link Capacity Adjustment Scheme

LCN Local Communications Network

LEC Local Exchange Carrier

LED Light Emitting Diode

LI Link Integrity

LIU Line Interface Unit

LMI Local Management Interface

LOF Loss of Frame

LOM Loss of Multiframe

LOP Loss of Pointer

LOS Loss of Signal

LOSS Loss of Signal Seconds

LR Long Reach (fiber)

LSM Loss of Sync Message

LSP Label Switch Path

LSR Label Switch Router

LTE Line Terminating Equipment

Acronym Description

m Meter

mm Millimeter

MAC Media Access Control

MAN Metropolitan Area Network

Mb Mega bit

MB Mega byte

Mbps Mega bits per second

MBS Maximum Burst Size

MCP Management Control Processor

MCR Minimum Cost Routing or Minimum Cell Rate

MDF Main Distribution Frame

MDI Medium Dependent Interface

MDI-X MDI Crossover


TraverseEdge 100 User Guide, Section 7: AppendicesN

N

MDU Multiple Dwelling Unit

MGCP / MEGACO Media Gateway Control Protocol / MEdia GAteway COntrol protocol

MGN Management Gateway Node

MHz Megahertz

mi Mile

MIR Maximum Information Rate

MMF Multimode Fiber

MLPPP Multi-Link Point-to-Point Protocol

M-Plane Management Plane

MPLS MultiProtocol Label Switching

MPOA MultiProtocol Over ATM

MPX Multiplex/Multiplexer

ms Millisecond

MSF Multiservice Switching Forum

MSP Multiplex Section Protection

MSPP Multiservice Provisioning Platform

MS-SPRing Multiplex Section Shared Protection Ring

MTBF Mean Time Between Failure

MTTR Mean Time to Repair

MTU Maximum Transmission Unit or Multiple Tenant Units

Multi-port ECCI A numbered IP interface with one or more member ports, each of which can be connected to an ECC.

mV Millivolt

Acronym Description

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

NGE Next Generation Ethernet


Appendix C Acronyms and AbbreviationsO

O

NIC Network Interface Card

NID Network Interface Device

nm Nanometer

NMF Node-level Management Function

NML Network Management Layer

NMS Network Management System

NNI Network to Network Interface

NO Normally Open (contacts)

NRT Non-Real Time

ns nanosecond

NSA Non-Service Affecting

NTP Network Time Protocol

NUT Non-preemptive Unprotected Traffic

Acronym Description

OAM&P Operations, Administration, Maintenance, & Provisioning

OC Optical Carrier

OC-1 Optical Carrier 1 (51.84 Mbps)


OC-192 Optical Carrier 192 (9.953 Gbps)


OC-48 Optical Carrier 48 (2.488 Gbps)

OC-N Optical Carrier-number

ODF Optical Distribution Frame

OLT Optical Line Termination/Terminal

ONT Optical Network Terminal

ONU Optical Network Unit

OOB Out Of Band

OOF Out Of Frame

OPR Optical Power Receive

OPT Optical Power Transmit

OS Operating System


TraverseEdge 100 User Guide, Section 7: AppendicesP

P

OSI Open System Interconnection

OSP OutSide Plant

OSPF Open Shortest Path First

OSS Operations Support System

OSSAN Operations Support System Access Nodes

Acronym Description

PBS Peak Burst Size

PC Personal Computer

PCA Protection Channel Access

PCR Peak Cell Rate

PDAP Power Distribution and Alarm Panel

PDH Plesiochronous Digital Hierarchy

PDI Payload Defect Indication

PDU Power Distribution Unit

PG Protection Group

PIR Peak Information Rate

PLC Partial Loss of Capacity

PLCR Partial Loss of Capacity, Receive

PLCT Partial Loss of Capacity, Transmit

PLCP Physical Layer Convergence Protocol

PLM Payload Label Mismatch

PM Performance Management or Performance Monitoring

PNNI Private Network-to-Network Interface

POH Path Overhead

PON Passive Optical Network

POP Point of Presence

POS Packet Over SDH or Packet Over SONET

POST Power On Self Test

POTS Plain Old Telephone Service

PPM Parts per Minute

PPP Point-to-Point Protocol


Appendix C Acronyms and AbbreviationsR

Q

R

PQ Priority Queuing

PRC Primary Reference Clock

PRS Primary Reference Source (timing)

ps Picosecond

PSC Protection Switching Count

PSD Protection Switching Duration

PTE Path Terminating Equipment

PTP Physical Termination Point

ptp A ’ptp’ PM template indicates a port or subport performance monitoring template

PVC Permanent Virtual Circuit

Acronym Description

Q-in-Q VLAN stacking

QoS Quality of Service

Acronym Description

RAI Remote Alarm Indication

RAS Reliability, Availability, and Serviceability

RBOC Regional Bell Operating Companies

RDI Remote Defect Indicator

RED Random Early Discard

REI Remote Error Indication

RES Reserved for network synchronization use. This is a user-defined SONET synchronization status message.

RFI Remote Failure Indication

RIB Routing Information Base

RMI Remote Method Invocation

RRO Record Route Object

RSTP Rapid Spanning Tree Protocol

RSVP Resource Reservation Protocol


TraverseEdge 100 User Guide, Section 7: AppendicesS

S

RT Remote Terminal

RTN Return (voltage return)

RTU Remote Test Unit

RU Rack Unit

RX Receive

Acronym Description

s Second

SA Service Affecting

SAN Storage Area Network

SC Shelf Controller

SCM SFP Connector Card

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

SFP Small Form-factor Pluggable transceiver

SIM Service Interface Card

SLA Service Level Agreement

SMF Singlemode Fiber

SML Service Management Layer

SMM Service Mediation Card

SNCP Subnetwork Control protocol Ring

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


Appendix C Acronyms and AbbreviationsT

T

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-16 Synchronous Transfer Mode - Level 16 (2.488 Gbps)

STM-4 Synchronous Transfer Mode - Level 4 (622.08 Mbps)

STM-64 Synchronous Transfer Mode - Level 64 (9.953 Gbps)

STS-1 Synchronous Transmission Signal Level 1

STS-3 Synchronous Transmission Signal Level 3

STS-3c Synchronous Transmission Signal Level 3, concatenated

SVC Switched Virtual Circuit

S-VLAN Service Virtual Area Network

Acronym Description

TAC Technical Assistance Center or Test Access Connection

TAD Test Access Digroup

TAP Technician Access Port or Test Access Point

TC Transmission Convergence

TCA Threshold Crossing Alert

TCP/IP Transmission Control Protocol/Internet Protocol

TDM Time Division Multiplexing

TE Terminal Equipment

TED Traffic Engineering Database

TID Target Identifier

TIM Trace Identifier Mismatch

TLS Transparent LAN Services

TMN Telecommunications Management Network

TOH Transport Overhead

TP Termination Point, also called Connection Termination Point


TraverseEdge 100 User Guide, Section 7: AppendicesU

U

V

TSC Test System Controller

TSI Time Slot Interchange

TSN Traverse Services Network

TU Tributary Unit

TUG Tributary Unit Group

TX Transmit

Acronym Description

UAS Unavailable Second

UBR Unspecified Bit Rate

UGC Universal Gateway Carrier

UL Underwriters Laboratories

UNEQ Unequipped

UNI User to Network Interface

UPC Universal Packet Carrier or Usage Parameter Control

UPSR Unidirectional Path Switched Ring

UTC Universal Transport Carrier or Universal Time Coordinated

UVC Universal Voice Carrier or Universal Video Carrier

Acronym Description

V Volt

VAP Virtual Access Partitioning

VBR Variable Bit Rate

VC Virtual Container or Virtual Circuit or Virtual Concatenation

VCAT Virtual Concatenation

VCC Virtual Channel Connection

VCG Virtual Concatenation Group

VCI Virtual Channel Identifier

VCSEL Vertical Cavity Surface Emitting Laser

VCX Virtual Tributary/Container Cross-connect


Appendix C Acronyms and AbbreviationsX

W

X

VDC Volts Direct Current

VLAN Virtual Local Area Network

VLR Very Long Reach

VOM Volt Ohm Meter

VOP Virtual Optical Port

VP Virtual Path

VP Virtual Path Connection

VPI Virtual Path Identifier

VPI/VCI Combined, VPI and VCI identify a connection on an ATM network

VPN Virtual Private Network

VRB Virtual RSTP Bridge

VRSTP Virtual Rapid Spanning Tree Protocol

VSA Virtual-Scheduling Algorithm

VT Virtual Tributary

VTG Virtual Tributary Group

V-UNI Virtual User Network Interface

Acronym Description

W Watt or Weight

WAC Wiretap Access Connection

WAN Wide Area Network

WDCS Wideband DCS

WDM Wave Division Multiplex

WFQ Weighted Fair Queueing

WTR Wait to Restore

Acronym Description

XFP 10 Gigabit Small Form Factor Pluggable Optical Transceiver


TraverseEdge 100 User Guide, Section 7: AppendicesX

For a compendium of telecommunications terms, see Newton’s Telecom Dictionary by Harry Newton, published by CMP Books, New York, NY. See http://www.harrynewton.com for more information.


http://www.harrynewton.com

Appendix C Acronyms and AbbreviationsSDH Containers

SONET/SDH Channel Capacities

Table 7-15 SONET/SDH Digital Hierarchy

Non - Synchronous Digital Hierarchies

Table 7-16 Non-Synchronous Digital Hierarchies

SDH Containers

Table 7-17 SDH Containers

Optical

Rate

Electrical

Equivalent

Level of Concatenat

ion

Line Rate

(Mbps)

Maximum

Payload Rate

(Mbps)

Maximum

Overhead Rate (Mbps)

SDH Equivale

nt

OC-1 STS-1 – 51.840 50.112 1.728 STM-0

OC-3 STS-3 3 x STS-1 155.520 150.336 5.184 STM-1

OC-9 STS-9 3 x STS-3 466.560 451.008 15.552 STM-3

OC-12 STS-12 4 x STS-3 622.080 601.344 20.736 STM-4

OC-18 STS-18 6 x STS-3 933.120 902.016 31.104 STM-6

OC-24 STS-24 8 x STS-3 244.160 1202.688 41.472 STM-8

OC-36 STS-36 12 x STS-3 1866.240 1804.032 62.208 STM-13

OC-48 STS-48 26 x STS-3 2488.320 2405.376 82.944 STM-16

OC-96 STS-96 32 x STS-3 4976.640 4810.752 165.588 STM-32

OC-192 STS-192 64 x STS-3 9953.280 9621.504 331.776 STM-64

ANSI ITU

Signal Type Bit Rate Channels Signal

Type Bit Rate Channels

DS0 64 Kbps 1 DS0 E0 64 Kbps 64 Kbps

DS1 1.544 Mbps 24 DS0 E1 2.048 Mbps 32 E0

DS2 6.312 Mbps 96 DS0 E2 8.448 Mbps 128 E0

DS3 44.736 Mbps 28 DS1 E3 34.368 Mbps 16 E1

E4 139.264 Mbps 64 E1

SDH Order

Signal(Mbps)

Payload Container

SDH Virtual Container

Tributary Unit

Capacity (Mbps)

Low DS1 – 1.544 C-11 VC-11 1.728

Low DS1 – 1.544E1 – 2.048

C-12 VC-12 2.304

Low DS2 – 6.312 C-2 VC-2 6.912

High E3 – 34.368DS3 – 44.736

C-3 VC-3 48.960

High E4 – 139.264 C-4 VC-4 150.336


TraverseEdge 100 User Guide, Section 7: AppendicesVT Hierarchy

VT Hierarchy Table 7-18 Virtual Tributary Hierarchy

VT Type

Bit Rate (Mbps)

Payload Capacity (Mbps)

Signal / Service

VTs Per VT Group

VTs Per STS-1

VT1.5 1.728 1.544 DS1 4 28

VT2 2.403 2.048 E1 3 21

VT3 3.456 3.152 DS1C 2 14

VT6 6.912 6.312 DS2 2 7


INDEX

Symbols, 2-26

Numerics10/100BaseTX

Fast Ethernet cabling, 3-832MHz clock timing, see Timing

AAccess

systemmethods, 4-2

ACO see Alarms, TE-100 cut-off

Airfilter

TE-100, 3-22AIS

formatDS3 port, 5-23

insertionE1 port, 5-48

maskDS1 port, 5-21DS3 port, 5-23E1 port, 5-48E3 port, 5-49SDH port, 5-54SONET port, 5-28

Alarmsconnections

audible output, 3-33PDAP fuse alarm, 3-37PDAP visual input, 3-38power alarm, 3-36visual output, 3-32

profileDS1 port, 5-21DS3 port, 5-24E1 port, 5-48E3 port, 5-50Ethernet port, 6-14SDH port, 5-57SONET port, 5-31

TE-100contact summary, 2-30cut-off button, 2-30

environmental, 2-28fail-safe, 2-28general description, 2-27input wire-wrap posts, 2-29LEDs, 2-30normally-open contacts, 2-28output wire-wrap posts, 2-29

Alternate VLAN ethertypeEthernet, 6-8

ANSI compliance, 2-10Application

for wireline and wireless carriers, 1-5multiservice access and transport, 1-6wireless backhaul, 1-7

APS, 4-3example, 4-24protection groups, 4-23

ArchitectureTE-100 shelf

multi-service optimized, 1-2Asymmetric LCAS, 6-39Automatic protection switching

see APSAuto-negotiation

parametersadvertise 1000M full duplex, 6-21advertise 1000M half duplex, 6-21advertise 100M full duplex, 6-20advertise 100M half duplex, 6-20advertise 10M full duplex, 6-20advertise 10M half duplex, 6-20advertise PAUSE, 6-20advertise PAUSE RX, 6-21advertise PAUSE TX, 6-21setting, 6-19

BBack covers, see Shelf and PDAPBackplane, 2-6

timing references, input and output, 2-31Battery

distributioncabling, 3-47

distribution cabling, 3-58return supply cabling, 3-54supply cabling, 3-53

Blank faceplate, installTE-100, 3-13

Release TE3.2.x Force10 Networks 1

CCabling

10/100Base TX Fast Ethernet, 3-8310/100BaseTX Fast Ethernet, 3-83battery

distribution, 3-47, 3-58return supply, 3-54supply cabling, 3-53

checklistalarm, 7-4network, 7-16power, 3-59, 7-7, 7-10timing, Ethernet RS-232, 7-12

DS1, 3-81DS3, 3-82fiber optic, 3-84front panel

power, 3-60management requirements, 3-87network

requirements, 3-80power requirements, 3-46power supply

central office, 3-55requirements

management interface, 3-64power, 3-58

routing management, 3-87strain-relief bar, 3-88

Cardstart-up

visual status, 3-77Central office

power supply, 3-55Change

BER thresholds, 5-24DS1 mapping, 5-18, 6-7

Checklistcabling

alarm, 7-4network, 7-16power, 7-7, 7-10

equipment configuration, 7-21installation

hardware, 7-3power system, 7-2

network configuration, 7-19node

start-up, 7-13power

cabling, 3-59timing

Ethernet, RS-232 cabling, 7-12

Class of serviceEthernet, 6-78

Classifiertemplates

creating, 6-79overview, 6-78

CLIcommands

descriptions, 3-70initial configuration, 3-75

Commissioningnode-id, 3-71node-ip, 3-71standard, 3-71

Common proceduresrequirements

TE-100, 3-9Compliance

ANSI, 2-10environmental, 2-10ETSI, 2-10eye safety, 2-10IEEE, 2-10ITU-T, 2-10NEBS, 2-10safety, 2-10Telcordia, 2-10

Config tabtributary module, 5-45

ConfigurationBER thresholds

STM path, 5-51CLI commands, 3-75initial

TE-100 shelf, 3-69process

TE-100, 4-1Connections

alarmaudible output, 3-33fuse, PDAP, 3-37PDAP visual relay input, 3-38power, 3-36visual output, 3-32

timinginputs and outputs, 4-10

Control dataSDH port, 5-56SONET port, 5-30

Current transmitter stateSTM

port, 5-55Customer

2 Force10 Networks Release TE3.2.x

DS1 port, 5-21DS3 port, 5-24E1 port, 5-48E3 port, 5-50Ethernet port, 6-14SDH port, 5-57SONET port, 5-31tag

DS1 port, 5-21DS3 port, 5-24E3 port, 5-50Ethernet port, 6-14SDH port, 5-57

tagged, 6-14Ethernet, 6-11

DData communications

equipment interfaceDB-9 pinouts, 2-38RS-232, 2-38RS-232 pinouts, 2-38

Data rateDS1, 2-12, 2-14DS3 clear channel, 2-13, 2-15

DCE interface see Data communications

equipment interfaceDCN

Ethernet interface, 2-36pinouts, 2-36

interface, 3-66Derived

references configuration, 4-15timing, 4-10

Do not use for synchronization see DUS

DS1connector pinouts, 3-81data rate, 2-12, 2-14mapping

change, 6-7port

configure, 5-20ports, 2-12, 2-14

DS1 portAIS mask, 5-21alarm profile, 5-21customer, 5-21customer tag, 5-21line build out, 5-21line coding, 5-21line format, 5-21

performance monitoring template, 5-21DS3

line formatport, 5-23

portAIS format, 5-23AIS mask, 5-23alarm profile, 5-24change parameters, 5-22customer, 5-24customer tag, 5-24in band loopback, 5-23line build out, 5-23performance monitoring template,

5-24remote defect indicator, 5-49

DS3 clear channeldata rate, 2-13, 2-15ports, 2-13, 2-15specifications, 2-13, 2-15

DTE interface, 2-37, 3-67see also RS-232 DTE interface

DUSSDH port, 5-54SONET port, 5-28

EE1

timing, see Timingcard

configure, 5-45port

AIS insertion, 5-48AIS mask, 5-48alarm profile, 5-48configure, 5-47customer, 5-48line build out, 5-48line format, 5-48performance monitoring template,

5-48E3

portAIS mask, 5-49alarm profile, 5-50customer, 5-50customer tag, 5-50line build out, 5-49line format, 5-49performance monitoring template,

5-50Electrical

precautions, 3-4


Electrostatic dischargejack location, 3-8precautions, 3-8

EndpointSTS services, 5-35

Environmentalprecautions, 3-4specifications, 2-10TE-100

alarms, 2-28EOS

definition, 6-25port

configuring, 6-31description, 6-25members, 6-26threshold, 6-46

Equipmentconfiguration checklist, 7-21protection, 4-3

1:1, 2-6ESD, see Electrostatic dischargeETH100TX port

crossover, 6-22manual duplex, 6-22manual pause, 6-22manual speed, 6-22

Ethernetalternate VLAN ethertype

configure, 6-8class of service, 6-78classifier templates, 6-78, 6-79configuration process flow, 6-2configuring, 6-3features

LCAS, 6-37LCAS operation, 6-38virtual concatenation, 6-26

line service, 6-58over SONET/SDH

required connections, 6-25port

alarm profile, 6-14customer, 6-14customer tag, 6-14customer-tagged, 6-11, 6-14FIFO queuing policy, 6-17insert alternate VLAN ethertype,

6-16jumbo frame support, 6-13link integrity, 6-59manual duplex, 6-22manual pause, 6-22

manual speed, 6-22Max info rate, 6-16performance monitoring template,

6-14port-based tagging, 6-11port-tagged, 6-11, 6-14priority queuing policy, 6-17queuing policy, 6-17service-tagged, 6-11shape enable, 6-17shaping rate, 6-17tagging, 6-14transmitter state, 6-14untagged, 6-12, 6-14WFQ CoS 1 to 4 weight, 6-17WFQ queuing policy, 6-17

port-based tagging, 6-14requirements, 6-4transport services

configuring, 6-30Ethernet port, 6-14

WFQ queuing policy, 6-35ETSI

compliance, 2-10Eye safety

compliance, 2-10

FFacility

protectionoptical interface, 2-25

Fail-safeTE-100 alarm, 2-28

Fanassembly

definition, 2-9specifications, 2-9TE-100 air filter, 3-22

Fast Ethernetcabling, 3-83connector pinouts, 3-83ports, 2-19

Fiber opticcabling, 3-84precautions

cabling, 3-5testing, 3-85

FIFOqueuing policy

Ethernet port, 6-17Forward

section traceSDH port, 5-56


SONET port, 5-29section trace format

SDH port, 5-56SONET port, 5-29

Frontpanel

power cabling, 3-50, 3-60

GG.747

servicesstandard, 5-44

Generic framing procedure, 1-3Grounding

shelf, 3-30Guidelines

create SNCP ring protection group, 4-20create UPSR protection group, 4-20network timing configuration, 4-10

HHardware

checklistinstallation, 7-3

precautionsinstall, 3-4

Hop-by-hopservice, 5-2service model, 5-8, 5-9, 5-10, 5-11

IIEEE

compliance, 2-10In band loopback, 5-23Insert alternate VLAN ethertype

Ethernet port, 6-16Install

checklisthardware, 7-3power system, 7-2

hardwarerequirements, 3-25

rack adapter, 3-30Interface module, 2-8

config tab, 5-45ITU-T

compliance, 2-10

JJumbo frame

support

Ethernet port, 6-13

LLCAS

asymmetric, 6-39feature description, 6-37interworking, 6-40operation, 6-38protection groups, 6-39

LEDsGCM

power and standby, 3-19Line

build outDS1 port, 5-21DS3 port, 5-23E1 port, 5-48E3 port, 5-49

codingDS1 port, 5-21

formatDS1 port, 5-21DS3 port, 5-23E1 port, 5-48E3 port, 5-49

protection, 4-3service

definition, 6-58timing

configuration, 4-14Link Capacity Adjustment Scheme, see

LCAS

MMax info rate (Mbps), 6-16Module

insertTE-100, 3-11

interface, 2-8system, 2-6

MSP, 4-3example, 4-24protection groups, 4-23

Multicast connections, 5-2Multiplex section protection

see MSPMultiservice

access and transport application example, 1-6

optimized architecture, 1-2


NNEBS

compliance, 2-10Network

configuration checklist, 7-19configuration process, 4-1, 6-3Time Protocol, 4-7topology

example, 2-44point-to-point, 2-43ring, 2-44

NodeID

commissioning, 3-71IP

commissioning, 3-71startup

TE-100, 3-74NTP IP, see Network Time ProtocolNutdriver, 1/4-inch

shelf power connections, 3-26

OOC-12

port specifications, 2-23SFP ports, 2-23VT path protection

service application, 5-10OC-192

cardconfiguration, 5-25

OC-3port specifications, 2-22SFP ports, 2-22VT path protection

service application, 5-10OC-48

port specifications, 2-24SFP ports, 2-24STS UPSR service application, 5-8

OC-n facility protection, 2-25Optical

specificationsinterface summary, 2-26

PPath protection, 4-3PDAP, 2-39

19-inch rack installation, 3-27back cover

remove on TE-100, 3-23power, fuse and visual alarm wire-wrap

posts, 3-35specifications, 2-40

Performance monitoring templateDS1 port, 5-21DS3 port, 5-24E1 port, 5-48E3 port, 5-50Ethernet port, 6-14SDH port, 5-57SONET port, 5-31

Pinouts10/100BaseTX Fast Ethernet, 3-83DS1 connector, 3-81

PLCT ThresholdEOS port

advanced, 6-46Polarity

verify, 3-56Port-based tagging

Ethernet, 6-11, 6-14Ports

DS1, 2-12, 2-14DS3 clear channel, 2-13, 2-15EOS description, 6-25fast Ethernet, 2-19OC-12, 2-23OC-3, 2-22OC-48, 2-24

Powercabling

front panel, 3-50fuse and visual alarm

PDAP wire-wrap posts, 3-35optional PDAP description, 2-39PDAP specifications, 2-40supply

central office, 3-55Power Distribution and Alarm Panel, see

PDAPPrecautions

electrical, 3-4electrostatic discharge, 3-8environmental, 3-4fiber optic cabling, 3-5hardware

install, 3-4module, 3-7

Primary reference, 4-10Priority queuing policy

Ethernet port, 6-17Protection groups

LCAS, 6-39Protection switching


1+1 optimized, 4-271:1 equipment, 4-3APSline, 4-3MSPpath, 4-3

Provisioningchecklists, 4-3

QQueuing policy

Ethernet port, 6-17

RRack configuration, 2-8RDI, see Remote defect indicatorRear

viewshelf, 2-6

Recovery pulse widthSTM port, 5-55

Regulatory compliance, 2-10Remote defect indicator

DS3, 5-49Replacing GCM

power and standby LEDs, 3-19Requirements

common proceduresTE-100, 3-9

Resource advisory, 5-2Reverse

section traceSDH port, 5-56SONET port, 5-29

section trace formatSDH port, 5-56SONET port, 5-29

Ring topology, 2-44RS-232 DCE interface, 2-38

connection, 3-64RS-232 DTE interface

connection, 3-67DB-25 pinouts, 3-68DB-9 pinouts, 3-68

RS-232 interfaceserial port, 2-37

SSafety compliance, 2-10SD BER

line, 5-28SONET port, 5-28

SDHport

AIS mask, 5-54alarm profile, 5-57control data, 5-56customer, 5-57customer tag, 5-57DUS, 5-54forward section trace, 5-56forward section trace format, 5-56performance monitoring template,

5-57reverse section trace, 5-56reverse section trace format, 5-56SF BER

line, 5-54terminate DCC, 5-56transmitter state, 5-54

Serviceapplications

OC-3/ and OC-12 STS UPSR, 5-10OC-48 STS UPSR, 5-8path protection, STM-1 and STM-4,

5-11STM-16 SNCP ring, 5-9

definitionCN-3605, 5-1TE-100, 5-1

duplicate, 5-15features supported, 5-2hop-by-hop, 5-2multicast connections, 5-2resource advisory, 5-2SONET

requirements, 5-34VT switching, 5-2

Service-taggedEthernet, 6-14

SF BERline, 5-28, 5-54SDH port, 5-54SONET port, 5-28

SFPs see also Small Form-Factor Pluggableinsert and remove

TE-100, 3-15latches, 3-15OC-12, 2-23OC-3, 2-22OC-48, 2-24

Shapeenable

Ethernet port, 6-17


Shapingrate

Ethernet port, 6-17Shelf

back covers, removing and replacing, 3-10

blank faceplate, install TE-100, 3-13carrier-class reliability, 1-4comprehensive management, 1-4dimensions summary table, 2-4front view, 2-5general description, 1-1grounding, 3-30rack adapter installation, 3-30rear view, 2-6specifications, 2-2TE-100

alarm interface wire-wrap posts, 2-27

initial configuration, 3-69timing interface wire-wrap posts, 2-33versatile configuration, 1-4

Small Form-Factor Pluggable transceivers, 2-7

SNCP ringcreate protection group, 4-20example, 4-18guidelines, 4-20

SONETport

AIS mask, 5-28alarm profile, 5-31change parameters, 5-27control data, 5-30customer, 5-31DUS, 5-28forward section trace, 5-29forward section trace format, 5-29performance monitoring template,

5-31reverse section trace, 5-29reverse section trace format, 5-29SD BER line, 5-28SF BER line, 5-28terminate DCC, 5-30transmitter auto shutdown, 5-29transmitter state, 5-28

servicesrequirements, 5-60

Specifications, 2-12, 2-14DS1 ports, 2-12DS3 clear channel ports, 2-13, 2-15fan assembly, 2-9

fast Ethernet ports, 2-19Gigabit Ethernet ports, 2-18OC-12 port, 2-23OC-3 port, 2-22OC-48 port, 2-24shelf, 2-2

Standardcommissioning, 3-71

Start-upchecklist

initial node configuration, 7-13TE-100 node

initial configuration, 3-69STM

portcurrent transmitter state, 5-55recovery pulse width, 5-55transmit auto shutdown, 5-55

STM-1path protection service application, 5-11

STM-16SNCP ring

service application, 5-9STM-4 path protection service application,

5-11STS services

endpoints, 5-35System access methods, 4-2System module, 2-6

TT1

timing, see TimingTagging

Ethernet port, 6-14Telcordia

compliance, 2-10Temperature

operational, 2-10storage, 2-10

Terminate DCCSDH port, 5-56SONET port, 5-30

Timing2MHz output connections, 3-42connections, 4-10example, 4-10external input connections, 3-40external output connections, 3-41global option, 4-11interface wire-wrap posts, 2-33

Topologyexample, 2-44


point-to-point, 2-43ring, 2-44

Transmitterauto shutdown

STM-N port, 5-55current state

STM port, 5-55state

Ethernet port, 6-14SDH port, 5-54SONET port, 5-28

Transmuxstandard

G.747 services, 5-44

UUntagged

Ethernetport, 6-14

UPSRcreate protection group, 4-20example, 4-18guidelines, 4-20

VVCAT, see Virtual concatenationVerify

polarity, 3-56Virtual

concatenation, 1-3description, 6-26

Voltageverify, 3-56

VT switching, 5-2

WWFQ

Ethernet portCoS 1 to 4 weight, 6-17queuing policy, 6-17

queuing policy, 6-35Wireless backhaul application example, 1-7Wire-wrap posts

TE-100alarm input, 2-29alarm output, 2-29

timing interface, 2-33



Visit our website at:www.force10networks.com

Release TE3.2.x TraverseEdge 100 System Documentation800-0010-TE322

www.turinnetworks.com