Volume 3 - Provisioning Release 1.4 Rev A

Turin Networks Inc.
Traverse System
SONET Documentation
Volume 3
Provisioning
Release 1.4
Publication Date: December 2003
Document Number: 800-0103-04 Rev. A
FCC Compliance
This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to
Part 15 of the FCC Rules. This equipment generates, uses, and can radiate radio frequency energy and, if not
installed and used in accordance with the installation instructions may cause harmful interference to radio
communications.
Canadian Compliance
This Class B digital apparatus meets all requirements of the Canadian Interference-Causing Equipment
Regulations. Cet appareil numérique de la classe B respects toutes les exigences du Règlement sur le
matériel brouilleur du Canada.
International Declaration of Conformity
We, Turin Networks, Inc. declare under our sole responsibility that the Traverse platform (models: Traverse
2000, Traverse 1600, and Traverse 600) to which this declaration relates, is in conformity with the following
standards:
EMC Standards
EN55022 EN55024 CISPR-22
Safety Standards
EN60950 CSA 22.2 No. 60950, ASINZS 3260
IEC 60950 Third Edition. Compliant with all CB scheme member country deviations.
Following the provisions of the EMC Directive 89/336/EEC of the Council of the European Union.
Copyright © 2003 Turin Networks, Inc.
All rights reserved. This document contains proprietary and confidential information of Turin Networks,
Inc., and may not be used, reproduced, or distributed except as authorized by Turin Networks. No part of this
publication may be reproduced in any form or by any means or used to make any derivative work (such as
translation, transformation or adaptation) without written permission from Turin Networks Inc.
Turin Networks Trademarks
Turin Networks, the Turin Networks logo, Traverse, Traverse 2000, Traverse 1600, Traverse 600,
TransAccess 100, TransNav, and Creating The Broadband Edge are trademarks of Turin Networks, Inc. or
its affiliates in the United States and other countries. All other trademarks, service marks, product names, or
brand names mentioned in this document are the property of their respective owners.
Government Use
Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in FAR 12.212
(Commercial Computer Software-Restricted Rights) and DFAR 227.7202 (Rights in Technical Data and
Computer Software), as applicable.
V OLUME 3 P ROVISIONING
Contents
Volume 3 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii
Section 1 Configuring Equipment

Chapter 1
Provisioning Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Chapter 2
Node and Timing Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Chapter 3
Module Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-17
Chapter 4
Port Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-23
Chapter 5
TransAccess 100 Mux Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-47
Chapter 6
DCC Tunnel Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-57
Section 2 Creating Protection Groups

Chapter 1
Overview of Protection Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Chapter 2
Create an Equipment Protection Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
Chapter 3
Create a 1+1 APS Protection Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
Chapter 4
Create a BLSR Protection Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13
Chapter 5
Create a 1+1 Path Protection Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-21
Chapter 6
Create a UPSR Protection Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-27
Section 3 Creating Services

Chapter 1
Service Provisioning Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
Chapter 2
Procedures Common to All Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11
Chapter 3
Creating DS1 Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-19
Chapter 4
Creating DS3 Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-35
Chapter 5
Creating SONET Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-53
Release 1.4 Turin Networks Page i

Volume 3 Provisioning
Section 4 Creating Ethernet Services

Chapter 1
Ethernet Services Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
Chapter 2
Creating Ethernet Transport Paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11
Chapter 3
Creating VC-Bundle Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-17
Chapter 4
Creating Point-to-Point Dedicated Services . . . . . . . . . . . . . . . . . . . . . . . . . 4-25
Chapter 5
Creating Point-to-Point Shared Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-31
Chapter 6
Creating Ethernet IAS Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-37
Chapter 7
Creating Ethernet TLS Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-45
Section 5 Provisioning Service Applications

Chapter 1
Creating 1+1 Path-Protected Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
Chapter 2
Creating Drop-and-Continue Services Procedures . . . . . . . . . . . . . . . . . . . . 5-11
Chapter 3
Creating Optical Transmux Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-23
Chapter 4
Creating Services on Overlapping UPSRs . . . . . . . . . . . . . . . . . . . . . . . . . . 5-33
Chapter 5
Creating Transparent Services Procedures. . . . . . . . . . . . . . . . . . . . . . . . . . 5-45
Section 6 Appendices
Appendix A
Provisioning Checklists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1
Appendix B
Services Sources and Destination. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-9
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Index-1
Page ii Turin Networks Release 1.4

Volume 3 Description
Introduction This description contains the following documentation topics:

■ What’s New?, page iii.
■ Documentation Set Description, page iv.
■ Information Mapping, page v.
■ If You Need Help, page v.
■ Calling for Repairs, page v.
What’s New? Volume 3, Provisioning includes the following enhancements with respect to the new
Release 1.4 feature set.
Release Feature Volume Reference
1+1 Path Protection. Section 5—Provisioning Service Applications, Chapter

1—“Creating 1+1 Path-Protected Services,” page 5-1.
1:2 equipment protection. Section 2—Creating Protection Groups, Chapter 2—“Create

an Equipment Protection Group,” page 2-3.
Ethernet transport enhancements. Section 4—Creating Ethernet Services, page 4-1.
Optical Transmux. Section 5—Provisioning Service Applications, Chapter

3—“Creating Optical Transmux Services,” page 5-23.
Overlapping Interconnecting Rings. Section 5—Provisioning Service Applications, Chapter

4—“Creating Services on Overlapping UPSRs,” page 5-33.
Resource Advisory. Section 3—Creating Services, Chapter 2—“Procedures

Common to All Services,” page 3-11.
Transparent services over OC-192 Section 5—Provisioning Service Applications, Chapter

linear chain. 5—“Creating Transparent Services Procedures,” page 5-45.
Release 1.4 Turin Networks Page iii

Documentation Set Description
Documentation The Traverse™ system documentation set is comprised of five volumes and is written
Set Description to meet users’ needs as described in the table below.
The documentation set meets Telcordia™ Generic Requirements for Supplier-Provided
Documentation GR–454 requirements.
Volume Description Target Audience
Volume 1, This volume provides a detailed overview of the Anyone with the need
General Traverse system. It also includes engineering and to understand the
Information planning information. Traverse system and
its applications.
Volume 2, This volume provides required equipment and Installers, Field and
Installation tools, and step-by-step procedures for: Network Engineers.
and ■ Hardware installation.
Configuration ■ Power cabling.
■ Network cabling.
■ Power-up.
■ Configuration.
Volume 3, This volume provides provisioning concepts Network Engineers,
Provisioning related to the Traverse system. Step-by-step Provisioning and
procedures for provisioning using the TransNav Network Operations
Management System are provided. Center (NOC)
personnel.
Volume 4, This volume provides required equipment and Field and Network
Maintenance tools, and step-by-step procedures for: Engineers.
and Testing ■ Routine maintenance.
■ Module replacement.
■ Alarms and recommended actions.
■ Troubleshooting.
■ Performance monitoring.
■ Loopback tests.
■ Traverse system software upgrade.
Volume 5, This volume provides an overview of the Field and Network
TransNav TransNav™ Management System. It also includes: Engineers,
Management ■ Hardware requirements and third party Provisioning, and
System software requirements. Network Operations
■ Installation instructions for client/server, third Center (NOC)
party, and management system software. personnel.
■ Complete descriptions of management system
menus and windows along with reporting,
provisioning, fault management, performance
management, and system administration
functions.
■ Command Line Interface user’s guide.
Page iv Turin Networks Release 1.4

Information Mapping
Information Traverse system documentation uses Information Mapping format. Information

Mapping Mapping presents information in small units or blocks. The beginning of an
information block is identified by a subject label in the left margin. The end of an
information block is identified by a horizontal line. Subject labels allow the reader to
scan the document and find a specific subject. Its objective is to make information easy
for the reader to access, use and remember.
Each procedure lists the equipment and tools, and provides step-by-step instructions
required to perform each task. Graphics are integrated into the procedures whenever
possible.
If You Need If you need assistance while working with Traverse products, contact the Turin
Help Networks Technical Assistance Center (TAC):
■ Inside the U.S.: 1-866-TURINET (866-887-4638)
■ Outside the U.S.: 707-665-4400
■ Online: www.turinnetworks.com/technical.htm
TAC is available 6:00AM to 6:00PM Pacific Time, Monday through Friday (business
hours). When the TAC is closed, emergency service only is available on a call-back
basis. E-mail support (24-hour response) is also available through at:
support@turinnetworks.com.
Calling for If repair is necessary, call the Turin Repair Facility at 1-866-TURINET (866-887-4638)
Repairs for a Return Material Authorization (RMA) number before sending the unit.The RMA
number must be prominently displayed on all equipment cartons. The Repair Facility is
open from 6:00AM to 6:00PM Pacific Time, Monday through Friday.
When calling outside the United States, use the appropriate international access code,
and then call 707-665-4400 to contact the Repair Facility.
When shipping equipment for repair, follow these steps:
1. Pack the unit securely.
2. Enclose a note describing the exact problem.
3. Enclose a copy of the invoice that verifies the warranty status.
4. Ship the unit PREPAID to the following address:
Turin Networks, Inc.
Turin Repair Facility
Attn: RMA # ________
1415 North McDowell Blvd.
Petaluma, CA 94954 USA
Release 1.4 Turin Networks Page v

Page vi Turin Networks Release 1.4
S ECTION 1 C ONFIGURING E QUIPMENT
S ECTION 2CONFIGURING EQUIPMENT
Contents
Chapter 1
Provisioning Overview
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Configuration Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
TransNav System Access Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Before You Start Provisioning Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Provisioning Checklists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Chapter 2
Node and Timing Configuration
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Configure Node Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Timing Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
Network Timing Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7
Guidelines to Configuring Network Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8
Configure Global Timing Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8
Configure External Timing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10
Configure Line Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14
Configure Derived References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15
Chapter 3
Module Configuration
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-17
Protection Groups and Card Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-17
Change Module (Card) Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-18
Change DS1 Mapping Formats. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-19
Change the BER Thresholds for an STS Path . . . . . . . . . . . . . . . . . . . . . . . . 1-21
Chapter 4
Port Configuration
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-23
Before You Change DS1 Port Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-24
Change DS1 Port Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-25
Before You Change DS3 Port Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-27
Change DS3 Clear Channel Port Parameters. . . . . . . . . . . . . . . . . . . . . . . . . 1-28
Before You Change DS3TMX Port Parameters . . . . . . . . . . . . . . . . . . . . . . . 1-30
Change DS3 Transmux Port Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-31
Before You Change EC1 Port Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-34
Change EC1 Port Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-35
Before You Change Ethernet Port Parameters . . . . . . . . . . . . . . . . . . . . . . . . 1-38
Release 1.4 Turin Networks Page vii

Volume 3 Section 1 Configuring Equipment
Change Ethernet Port Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-39

Before You Change SONET Port Parameters. . . . . . . . . . . . . . . . . . . . . . . . . 1-42
Change SONET Port Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-43
Chapter 5
TransAccess 100 Mux Configuration
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-47
Before You Configure a TransAccess 100 Mux. . . . . . . . . . . . . . . . . . . . . . . . 1-47
Switch to EC-1 and Port Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-48
Add TransAccess 100 Mux to the User Interface . . . . . . . . . . . . . . . . . . . . . . 1-49
Change TransAccess 100 Mux Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . 1-51
Configure TransAccess 100 Mux DS1 Channels . . . . . . . . . . . . . . . . . . . . . . 1-54
Chapter 6
DCC Tunnel Configuration
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-57
DCC Tunnel Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-58
Before You Tunnel a DCC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-59
Tunneling a DCC Through a Traverse Network . . . . . . . . . . . . . . . . . . . . . . . 1-61
List of Figures
Figure 1-1 Node Configuration Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Figure 1-2 Network Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7
Figure 1-3 Shelf View, Timing Tab, Main Subtab . . . . . . . . . . . . . . . . . . . . . . 1-8
Figure 1-4 Shelf View, Timing tab, EXT Subtab . . . . . . . . . . . . . . . . . . . . . . . 1-10
Figure 1-5 Timing Tab, EXT Subtab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12
Figure 1-6 Timing Tab, Main Subtab, Reference Priority . . . . . . . . . . . . . . . . 1-13
Figure 1-7 Line Timing, Timing Tab, Main Subtab . . . . . . . . . . . . . . . . . . . . . 1-14
Figure 1-8 Shelf View, Timing Tab, Derived Timing Options . . . . . . . . . . . . . 1-15
Figure 1-9 Card Configuration Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-18
Figure 1-10 DS1 Card, Config Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-19
Figure 1-11 OC-192 Card, Config Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-21
Figure 1-12 DS1 Port Configuration Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-25
Figure 1-13 DS3 Clear Channel Port Configuration Screen . . . . . . . . . . . . . . . 1-28
Figure 1-14 DS3 Transmux Port Configuration Screen . . . . . . . . . . . . . . . . . . 1-31
Figure 1-15 EC1 Port Configuration Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-35
Figure 1-16 Switch to EC1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-35
Figure 1-17 Confirm Switch to EC1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-36
Figure 1-18 EC1 Port Configuration Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-36
Figure 1-19 Ethernet Port Configuration Screen. . . . . . . . . . . . . . . . . . . . . . . . 1-39
Figure 1-20 SONET Port Configuration Screen . . . . . . . . . . . . . . . . . . . . . . . . 1-43
Figure 1-21 Provision new T100 Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . 1-49
Figure 1-22 T100 Mux. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-49
Figure 1-23 T100 Configuration Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-51
Figure 1-24 T100 Configuration Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-54
Page viii Turin Networks Release 1.4

Figure 1-25 Tunneling 3rd Party DCC through a Traverse Network . . . . . . . . 1-58
Figure 1-26 DCC Tunnel Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-61
Figure 1-27 Click a Row . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-61
List of Tables
Table 1-1 Traverse Network Configuration Process and References . . . . . . 1-1
Table 1-2 Accessing the TransNav Management System . . . . . . . . . . . . . . 1-2
Table 1-3 Before Provisioning Your Network Requirements. . . . . . . . . . . . . 1-2
Table 1-4 Configure Node Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Table 1-5 Configure Global Timing Options . . . . . . . . . . . . . . . . . . . . . . . . . 1-8
Table 1-6 Configure External Timing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10
Table 1-7 Configure Line Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14
Table 1-8 Configure Derived References . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-15
Table 1-9 Change Module Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-18
Table 1-10 Change DS1 Mapping Formats. . . . . . . . . . . . . . . . . . . . . . . . . . . 1-19
Table 1-11 Change the BER Thresholds for an STS Path . . . . . . . . . . . . . . . 1-21
Table 1-12 DS1 Port Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-24
Table 1-13 Change DS1 Port Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-25
Table 1-14 DS3CC Port Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-27
Table 1-15 Change DS3CC Port Parameters . . . . . . . . . . . . . . . . . . . . . . . . . 1-28
Table 1-16 DS3TMX Port Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-30
Table 1-17 Change DS3TMX Port Parameters. . . . . . . . . . . . . . . . . . . . . . . . 1-31
Table 1-18 EC1 Port Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-34
Table 1-19 Change EC1 Port Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-35
Table 1-20 Ethernet Port Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-38
Table 1-21 Change Ethernet Port Parameters . . . . . . . . . . . . . . . . . . . . . . . . 1-39
Table 1-22 SONET Port Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-42
Table 1-23 Change SONET Port Parameters . . . . . . . . . . . . . . . . . . . . . . . . . 1-43
Table 1-24 TransAccess 100 Mux Requirements . . . . . . . . . . . . . . . . . . . . . . 1-47
Table 1-25 Add TransAccess 100 Mux to the User Interface . . . . . . . . . . . . . 1-49
Table 1-26 Configure a TransAccess 100 Mux . . . . . . . . . . . . . . . . . . . . . . . . 1-51
Table 1-27 Configure TransAccess 100 Mux DS1 Channels . . . . . . . . . . . . . 1-54
Table 1-28 DCC Tunnels Hop-by-Hop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-58
Table 1-29 DCC Tunnel Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-59
Table 1-30 DCC Tunnel Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-61
Release 1.4 Turin Networks Page ix

Page x Turin Networks Release 1.4

Chapter 1
Provisioning Overview
Introduction This chapter describes the following topics on provisioning a Traverse network.
■ Configuration Process, page 1-1.
■ TransNav System Access Methods, page 1-2.
■ Before You Start Provisioning Procedures, page 1-2.
■ Provisioning Checklists, page 1-2.
Configuration The process to start configuring the Traverse network starts with installing and
Process commissioning each node.
Table 1-1 Traverse Network Configuration Process and References
Step Procedure Reference
1 Nodes are installed, connected, and Volume 2, Installation and Configuration.

commissioned.
2 Configure timing options for the Volume 3, Provisioning Section 1—Configuring

network. Equipment, Chapter 2—“Node and Timing
Configuration,” Timing Configuration, page 1-6.
3 Create protection groups. Volume 3, Provisioning Section 2—Creating

Protection Groups.
4 If necessary, change the default Volume 3, Provisioning Section 1—Configuring

parameters on the module. Equipment, Chapter 3—“Module Configuration,”
page 1-17.
5 Configure each physical interface Volume 3, Provisioning Section 1—Configuring

type. Equipment, Chapter 4—“Port Configuration,”
page 1-23.
6 Add external equipment to the user Volume 3, Provisioning Section 1—Configuring

interface and configure the equipment. Equipment, Chapter 5—“TransAccess 100 Mux
Configuration,” page 1-47.
7 Create services. Volume 3, Provisioning Section 3—Creating

Services.
Release 1.4 Turin Networks Page 1-1

Volume 3, Section 1: Configuring Equipment
TransNav System Access Methods
TransNav The following table lists the different access methods you can use to connect to the
System Access TransNav management server.
Methods Table 1-2 Accessing the TransNav Management System
Management System
Access Method
Interface
Domain-level GUI. ■ Installed client application (recommended).

■ Local connection to node and remote connection (DCC bytes) to
management server.
■ Installed application on a Citrix server.
Domain-level CLI. ■ Telnet to management server.

■ Local connection to node and remote login to management server.
Node-level CLI. ■ Local connection to node.

■ Local connection to node and remote login to a different node in
the domain.
Before You Before you start provisioning your network, the following tasks need to be complete.
Start
Provisioning Table 1-3 Before Provisioning Your Network Requirements
Procedures
Requirement Reference
Hardware
You have the correct hardware according to your Volume 1, General Information
network plan. Section 2—Hardware Descriptions.
Software
Nodes are commissioned. Volume 2, Installation and Configuration

Section 7—Start-up and Module Placement.
TransNav server software is installed. The server Volume 5, TransNav Management System
is initialized and started. Section 1—Overview, Installation and
Administration.
You are logged into the graphical user interface. Volume 5, TransNav Management System
Section 2—GUI Overview, Start Up, and
Administration, Chapter 1—“Starting the Graphical
User Interface,” page 2-1.
Wherever possible, a table listing requirements and guidelines precedes each

procedure. See each topic for requirements specific to the task.
Provisioning See Section 6—Appendices, Appendix A—“Provisioning Checklists” for a quick

Checklists reference on provisioning procedures.
Page 1-2 Turin Networks Release 1.4

Chapter 2
Node and Timing Configuration
Introduction This chapter provides the following configuration procedures for the Traverse system:
■ Configure Node Parameters, page 1-3.
■ Timing Configuration, page 1-6.
■ Network Timing Example, page 1-7.
■ Configure Global Timing Options, page 1-8.
■ Configure External Timing, page 1-10.
■ Configure Line Timing, page 1-14.
■ Configure Derived References, page 1-15.
Configure After a node is commissioned, you can configure the following type of information at
Node each node: node location description, alarm profiles and NTP server IP addresses.
Parameters 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 1-4 Configure Node Parameters
Step Procedure
1 In Map View, click and drag nodes to an area on the map to best represent
your network.
2 From the File menu, select Save User Preferences to save the placement
of the nodes.
3 Double-click a node to display Shelf View.

Configure Node Parameters
Table 1-4 Configure Node Parameters (continued)
Step Procedure
4 Click the Config tab to display the Node Configuration dialog box.
Figure 1-1 Node Configuration Dialog Box

5 In the Location field, type a descriptive location for the node. (For
example: Node1 Central Office)
Use alpha-numeric characters and spaces only. Do not use punctuation or
any other special characters in the Location field.
6 Alarm Profile (default=default). Select an Alarm Profile from the list if
additional profiles have been created.
(Alarm Profiles can be viewed or created from the Admin menu using the
Alarm Profiles dialog box.)

Chapter 2 Node and Timing Configuration
Configure Node Parameters
Table 1-4 Configure Node Parameters (continued)
Step Procedure
7 Values are displayed in the following fields. These values were set during
initial start-up procedures1 using the CLI:
■ Node ID.
■ Node IP.
■ BP DCN IP.
■ BP DCN Mask.
■ BP DCN Gateway.
■ GCM A IP and GCM B IP.
■ GCM A Mask and GCM B Mask.
■ GCM A Gateway and GCM B Gateway.
■ EMS IP.
■ EMS Mask.
■ EMS Gateway.
8 You can enter values for the NTP IP 1 and NTP IP 2 fields if they were
not set during initial start-up procedures. The Network Time Protocol
(NTP) server IP address is used by the node to derive Time of Day which
is used for performance monitoring, alarm and event logging2.
NTP IP 1
Type: the IP address of the primary NTP server.
(For example: aaa.bbb.ccc.ddd)
NTP IP 2
Type: the IP address of the secondary NTP server.
(For example: aaa.bbb.ccc.ddd)
9 External Alarm 1–4 fields display a default value of UNKWN. You can
select one of the following External Alarm input alarm types (based on the
environmental alarms input cabling completed during installation of the
node): HIGHTEMP, LOWTEMP, DOOROPEN, HIGHHMD,
LOWHMD, BATTDIS, BATTFAIL, or BATTLOW.
10 Click Apply.
11 Repeat Steps 1 through 10 for additional nodes.
12 The Configure Node Parameters procedure is complete.
1
See Volume 2, Installation and Configuration, Section 6, Chapter 1—“Start-up and Initial Configuration”
for detailed information.
2
Turin recommends using the TransNav server as the primary NTP source if you do not already have a
NTP source defined. Refer to Volume 5, TransNav Management System, Section 1, Chapter
8—“TransNav Server Administration Procedures” for information on how to activate NTP server on the
management server.

Timing Configuration
Timing Configure the timing source for each node in a domain. For each node, you can
Configuration configure either external timing from BITS (Building Integrated Timing Supply) or line
timing from OC interfaces.
Typically, one node in the central office receives redundant timing signals from an
external source (BITS reference). This node becomes the primary timing source for the
network. The other nodes receive the timing reference from optical interfaces. The
primary reference will be the shortest route to the primary timing source.
Synchronized primary and secondary timing inputs from the central office external
timing source are connected at the Traverse main backplane and bridged to the General
Control Modules (GCM).
Use the following procedures to configure timing options for the node.
■ Configure Global Timing Options, page 1-8.
■ Configure External Timing, page 1-10.
■ Configure Line Timing, page 1-14.
■ Configure Derived References, page 1-15.

Network Timing Example
Network In this example, the network is already connected and configured as a ring. The West
Timing Ports are the optical ports on the GCM in Slot 15 on all the nodes. The East Ports are
Example the optical ports on the GCM in Slot 16. Node 1 receives a timing signal from the
external clock. The primary line reference at Node 2 is Slot 15, the interface physically
connected to Node 1. The primary line reference at Node 4 is Slot 16, the interface
physically connected to Node 1. Node 3 can time off of either Slot 15 or Slot 16
because it is equal distance from Node 1.
EXT-A EXT-B
Timing Mode: External

Priority 1 Ref: EXT-A
Priority 2 Ref: EXT-B
Node 1
Ring Configuration
West port = Slot 15
East port = Slot 16
Node 4 Timing Mode: Line Node 2 Timing Mode: Line

Reference 1: Slot 16 Reference 1: Slot 15
Reference 2: Slot 15 Reference 2: Slot 16
Timing Mode: Line

Reference 1: Slot 15 or Slot 16
Reference 2: Slot 15 or Slot 16
Node 3
Figure 1-2 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
Guidelines to Use the following guidelines to configure timing in a Traverse network.

Configuring ■ Configure line timing in such a way that the primary reference is the shortest route
Network to the primary timing source.
Timing ■ For derived timing, the Traverse can generate a timing signal to an DS1
multi-frame, a T1 ESF or a 2 MHz external reference.
For information on pinouts for each timing interface, instructions on how to connect
timing inputs from the central office external timing source, and how to connect timing
outputs from a node to the external clock, see Volume 2, Installation and Configuration,
Section 4, Chapter 2—“Traverse System Timing Interface”.
This section contains information on configurable timing parameters. For an
explanation of all timing parameters, states, and messaging, see VVolume 5, TransNav
Management System, Section 3, Chapter 2—“Timing”.
Configure Configure the timing options at each node in the domain. Use this procedure to
Global Timing configure the global settings for system timing.
Options Table 1-5 Configure Global Timing Options
Step Procedure
1 In Shelf View, click the Timing tab to display the Main timing screen
(Main subtab).
Step 2
Step 3
Step 4
Step 6 Step 5 Step 7
Figure 1-3 Shelf View, Timing Tab, Main Subtab

2 From the Standard list, select the timing standard for the shelf:
■ Select ANSI for North American operation.
■ Select ITU (default) for operations outside of North America.

Configure Global Timing Options
Table 1-5 Configure Global Timing Options (continued)
Step Procedure
3 From Timing Mode list:

■ Select External to receive timing from a building integrated timing
supply (BITS) reference.
■ Select Line to derive timing from an OC interface.
4 Select the Revertive check box 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) is
selected. That is, the node will use provisioned priorities to select the best
timing reference.
Clear the box 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 Timing Mode is External, continue to Configure External Timing,
page 1-10.
If Timing Mode is Line, continue to Configure Line Timing, page 1-14.

Configure External Timing
Configure There are two external references for each node: EXT-A and EXT-B. For redundancy,
External they both have the same configuration. If both references fail, the node maintains
Timing timing from the internal stratum 3 oscillator.
Use this procedure to configure external timing interfaces for a node.
Table 1-6 Configure External Timing
Step Procedure
1 Complete the procedure Configure Global Timing Options, page 1-8.

2 In Shelf View, click the Timing tab, then click the EXT subtab.
EXT
subtab
Step 3
Figure 1-4 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.

Table 1-6 Configure External Timing (continued)
Step Procedure
4 Set the interface parameters for the DS1 timing references:

■ Line Coding: Defines the DS1 transmission coding type.
Select HDB3: High Density Bipolar Order 3 (default).
Select AMI for Alternate Mark Inversion.
■ Framing:
Select Basic Frame so that 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.
Select Multi-Frame so that 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:
Bit_SA4, Bit_SA5, Bit_SA6, Bit_SA7, or Bit_SA8.
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. Legacy networks that don’t
support SSM are considered DUS.
■ Signal Fail Present.
■ None.

Step Procedure
6 For each reference, unlock the administrative state to enable the external
timing. Click the lock icon next to each reference.
Step 6 Step 7
Figure 1-5 Timing Tab, EXT Subtab

7 Click Apply to save the external interface settings.

Step Procedure
8 Click the Main subtab to return to the Main timing screen.
Step 8
Step 9
Indicates active reference Step 10
Figure 1-6 Timing Tab, Main Subtab, Reference Priority

9 Select Priority 1 and Priority 2 external timing references.
A check mark indicates the active reference.
10 Click Apply to save the reference list settings.
11 The Configure External Timing procedure is complete.

Configure Line Timing
Configure Line You can establish up to four line timing sources based on your network requirements
Timing and the number of OC 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.
Use this procedure to configure line timing from an OC interface for a node.
Table 1-7 Configure Line Timing
Step Procedure
1 Complete the procedure Configure Global Timing Options, page 1-8.

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.
Line Time
Mode
Line Facility
Options
(Step 3)
Reference
Priorities
(Step 4)
Indicates active reference Step 5
Figure 1-7 Line Timing, Timing Tab, Main Subtab

3 For each line reference, select an STM port for the timing reference. The
port needs to be enabled (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 check mark indicates the active reference.
5 Click Apply to save the settings.
6 The Configure Line Timing procedure is complete.

Configure Derived References
Configure Derived timing is the process of providing a timing reference from a line interface and
Derived sending it to an external clock. Use this procedure to configure a derived timing
References references on a node.
The Traverse can generate a timing signal to an DS1 multi-frame, a T1 ESF or a 2 MHz
external reference.
Table 1-8 Configure Derived References
Step Procedure
1 In Shelf View, click the Timing tab to display the Main timing screen
(Main subtab).
Step 2
Step 4
Step 5
Figure 1-8 Shelf View, Timing Tab, Derived Timing Options

2 Select the External Out Enabled check box. Line Facility and Reference
List options appear on the screen.
3 Select the SSM quality for Squelch/AIS Threshold. If the quality of the
received SSM is lower than the value in this parameter, the system sends
an AIS to the external clock. If the external clock does not support AIS, the
system squelches (cuts-off) the signal to the clock.
■ 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. Legacy networks that don’t
support SSM are considered DUS.
■ Signal Fail Present.
■ None.

Configure Derived References
Table 1-8 Configure Derived References (continued)
Step Procedure
4 For each line reference, select an OC port for the timing reference. The
port needs to be enabled (unlocked administrative state).
5 Select a priority for each reference. If there is a failure on the first
references, 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.

Chapter 3
Module Configuration
Introduction You can customize certain parameters on each module (card) in a Traverse shelf. There
are parameters common to all modules as well as parameters specific to each module.
This chapter explains the following information for the cards supported in this release:
■ Protection Groups and Card Configuration, page 1-17.
■ Change Module (Card) Parameters, page 1-18.
■ Change DS1 Mapping Formats, page 1-19.
■ Change the BER Thresholds for an STS Path, page 1-21.
These procedures describe how to change configurable parameters only. See Volume 5,
TransNav Management System, Section 3—Configuring Equipment, Chapter
3—“Modules (Card)” 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.
Protection If you have configured a card as part of an equipment protection group, you can only
Groups and configure parameters on the working card. Down arrows on selections are grayed out
Card for parameters on the protecting card.
Configuration Parameters on a port on a protecting card are automatically set to those configured for
the same port on the working card. For example, if Line Format is set to M23 for port 1,
slot 2 (the working card), Line Format will also be set to M23 for port 1, slot 1 (the
protecting card).
For information on creating equipment protection groups, see Section 2—Creating
Protection Groups, Chapter 2—“Create an Equipment Protection Group,” page 2-3.

Change Module (Card) Parameters
Change The following procedure describes the common steps for all modules.
Module (Card)
Parameters Table 1-9 Change Module Parameters
Step Procedure
1 In Shelf View, click any card.

2 Click the Config tab to display the Card Configuration screen.
Figure 1-9 Card Configuration Screen
3 In the Customer Tag field, enter an alphanumeric character string to

identify the card to a customer.
4 Click Apply.
5 The Change Module Parameters procedure is complete.

Chapter 3 Module Configuration
Change DS1 Mapping Formats
Change DS1 The parameters on the DS1 module control how the DS1 channels on the module map
Mapping to a VT payload or multiplexed to an STS path. .
Formats
Important: Changing these parameters on the DS1 card is service
affecting. You cannot complete this procedure if the card is carrying traffic
(if there are services activated).
Table 1-10 Change DS1 Mapping Formats
Step Procedure
1 In Shelf View, click a DS1 module.

Step 3 Step 4
Figure 1-10 DS1 Card, Config Tab
3 Select how the DS1 channels on this module map to a VT payload. From
the DS1 Numbering list:
■ Select Non-sequential (default) maps per GR-253-CORE.
■ Select Sequential.
See Volume 5, TransNav Management System, Table 3-1 GR-253 and
Sequential VT Mapping Formats, page 3-29 for the specific mapping
format.
4 Select how the DS1 channels on this module are multiplexed into an STS.
From the DS1 Mapping list:
■ Select VC/VT-structured (default) to multiplex the signal into a
VT-mapped STS.
■ Select DS3-mapped to multiplex the signal into a DS3-mapped STS.

Change DS1 Mapping Formats
Table 1-10 Change DS1 Mapping Formats (continued)
Step Procedure
5 Click Apply.
6 The Change DS1 Mapping Formats procedure is complete.

Chapter 3 Module Configuration
Change the BER Thresholds for an STS Path
Change the Configure the thresholds for the path-level signal failed bit error ratio (SFBER) and
BER signal degrade bit error ration (SDBER) on the OC-N module. When the thresholds are
Thresholds for exceeded, the system raises an SFBER-P or SDBER-P alarm.
an STS Path
Table 1-11 Change the BER Thresholds for an STS Path
Step Procedure
1 In Shelf View, click an OC module. This module can be any one of the
following modules:
■ OC-3/STM-1.
■ OC-12/STM-4.
■ OC-48/STM-16.
■ OC-192/STM-64.
■ GCM with 1-port OC-12/STM-4.
■ GCM with 1-port OC-48/STM-16.
Step 3 Step 4
Figure 1-11 OC-192 Card, Config Tab
These parameters appear depending on the speed of the SONET interface

and apply to all the paths on the module.

Change the BER Thresholds for an STS Path
Table 1-11 Change the BER Thresholds for an STS Path (continued)
Step Procedure
3 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.
4 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.
5 Click Apply.
6 The Change the BER Thresholds for an STS Path procedure is complete.

Chapter 4
Port Configuration
Introduction This chapter explains how to change configurable parameters for the following types of
ports in a Traverse shelf:
■ Change DS1 Port Parameters, page 1-25.
■ Change DS3 Clear Channel Port Parameters, page 1-28.
■ Change DS3 Transmux Port Parameters, page 1-31.
■ Change EC1 Port Parameters, page 1-35.
■ Change Ethernet Port Parameters, page 1-39.
■ Change SONET Port Parameters, page 1-43.

Before You Change DS1 Port Parameters
Before You Review this information before you change any parameters on a DS1 port.
Change DS1
Port Table 1-12 DS1 Port Requirements
Parameters
Read the information in Section 1, Chapter 1—“Provisioning Overview,” page 1-1.
Hardware
You can change the DS1 interface parameters on Volume 1, General Information,
the following hardware: Section 2—Hardware Descriptions.
■ DS1 To configure a TransAccess 100 Mux, see Volume
■ TransAccess 100 Mux 3, Provisioning, Section 1, Chapter
5—“TransAccess 100 Mux Configuration,”
page 1-47.
Software
Timing is configured. Volume 3, Provisioning, Section 1, Chapter 2,”

Timing Configuration, page 1-6.
Protection groups are configured. Volume 3, Provisioning, Volume 3, Provisioning

Configure parameters only on working modules Section 2—Creating Protection Groups.
when a module is configured as part of a
protection group. Parameters on a protection
module are automatically set to those configured
for the same port on the working module.
DS1 mapping formats are correct. Volume 3, Provisioning, Section 1, Chapter 3,”
Change DS1 Mapping Formats, page 1-19.
These procedures describe the steps to create Volume 5, TransNav Management System,
change configurable parameters only. See Volume Section 3, Chapter 4,” DS1 Port Configuration,
5, TransNav Management System for descriptions page 3-34.
of other fields on screen.
To monitor performance on a DS1 port, know Volume 5, TransNav Management System,

how to use the performance monitoring Section 6, Chapter 1—“Performance Monitoring,”
templates. page 6-1.
Volume 4, Maintenance and Testing, Section 1,
Chapter 1—“Performance Monitoring,” page 1-1.
To customize service-affecting and Volume 5, TransNav Management System,

non-service-affecting alarm severities, know how Section 6, Chapter 3,” , page 6-37.
to use alarm profiles. Volume 4, Maintenance and Testing, Section 1,
Chapter 3—“Alarms, Events, and Recommended
Actions,” page 1-53.

Chapter 4 Port Configuration
Change DS1 Port Parameters
Change DS1 Use this procedure to customize behavior of a DS1 interface.

Port
Parameters Table 1-13 Change DS1 Port Parameters
Step Procedure
1 Review the information in Before You Change DS1 Port Parameters,

page 1-24 before you start this procedure.
2 In Shelf View, click a port (1 through 28) in a working DS1 module.
3 Click the Config tab to display the DS1 Port Configuration screen.
Step 2
Step 3
Step 4
Step 5
Step 6 Step 7
Figure 1-12 DS1 Port Configuration Screen

Change DS1 Port Parameters
Table 1-13 Change DS1 Port Parameters (continued)
Step Procedure
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.
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.
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.
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: Generate an AIS when the DS1 signal is degraded.
■ Disabled (default): Do not generate an AIS when the DS1 signal is
degraded
5 Change any of the following general parameters for the interface:
Customer: Select from the list of defined customers.
PM Template: Select from the list of defined performance monitoring
templates (of type ds1_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 ds1_ptp alarm profile.
6 Click the Lock icon , located in the lower left corner of the screen, to
unlock the port and be able to monitor potential problems.
7 Click Apply.
8 The Change DS1 Port Parameters procedure is complete.

Before You Change DS3 Port Parameters
Before You Review this information before you change any parameters on a DS3 port
Change DS3
Port Table 1-14 DS3CC Port Requirements
Parameters
Hardware
■ DS3/EC1 Clear Channel.
■ DS3 Transmux module (DS3-CC port).
Software
Timing is configured. Volume 3, Provisioning, Section 1, Chapter

2—“Node and Timing Configuration,” page 1-6.

change configurable parameters only. See Volume Section 3, Chapter 4,” DS3-CC and DS3-TMX
5, TransNav Management System for descriptions Port Configuration, page 3-36.

how to use the performance monitoring Section 6, Chapter 1—“Performance
templates. Monitoring,” page 6-1.

non-service-affecting alarm severities, know how Section 6, Chapter 3—“Alarms,” page 6-37.

Change DS3 Clear Channel Port Parameters
Change DS3 Use this procedure to customize behavior of a DS3 interface.

Clear Channel
Port Table 1-15 Change DS3CC Port Parameters
Parameters
Step Procedure
1 Review the information in Before You Change DS3 Port Parameters,

2 In Shelf View, click a port (1 through 12) on a working DS3 module.
3 Click the Config tab to display the DS3 Clear Channel Port
Configuration screen.
Step 2
Step 3
Step 4
Step 5
Step 6 Step 7
Figure 1-13 DS3 Clear Channel Port Configuration Screen

Change DS3 Clear Channel Port Parameters
Table 1-15 Change DS3CC Port Parameters (continued)
Step Procedure

■ 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.
■ Unchannelized: A payload of 44.210 Mbps is supported with M, F, P,
X, and C bits preserved to ensure compatibility.
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:
■ 255–450 ft.
templates (of type ds_ptp_pm). Default value is default, which contains
for DS1 ports.
ds_ptp) to customize service-affecting and non-service-affecting alarm
severities. Default is the default ds_ptp alarm profile.
7 Click Apply.
8 The Change DS3CC Port Parameters procedure is complete.

Before You Change DS3TMX Port Parameters
Before You Review this information before you change any parameters on a DS3TMX port
Change
DS3TMX Port Table 1-16 DS3TMX Port Requirements
Parameters
Hardware
■ DS3 Transmux module (DS3-TMX port).
Software
Node is commissioned. Volume 2, Installation and Configuration,



change configurable parameters only. See Volume Section 3, Chapter 4,” DS3-CC and DS3-TMX
5, TransNav Management System for descriptions Port Configuration, page 3-36.



Change DS3 Transmux Port Parameters
Change DS3 Use this procedure to customize behavior of a DS3TMX interface.

Transmux Port
Parameters Table 1-17 Change DS3TMX Port Parameters
Step Procedure
1 Review the information in Before You Change DS3TMX Port

Parameters, page 1-30 before you start this procedure.
2 In Shelf View, click a port (1 through 12) on a working DS3TMX module.
3 Click the Config tab to display the DS3 Transmux Port Configuration
screen.
Step 2
Step 3
Step 4
Step 5
Figure 1-14 DS3 Transmux Port Configuration Screen

Table 1-17 Change DS3TMX Port Parameters (continued)
Step Procedure

■ M23: Seven DS2 signals asynchronously multiplexed into the DS3
signal.
■ CBIT (default): 28 DS-1 signals are multiplexed into the DS3 signal,
with the C-bit used as control bit.
DS1 to VT Map: Select how the DS1 signals map into a VT payload on
this port. See Table 3-1 GR-253 and Sequential VT Mapping Formats,
page 3-29 for the list of mapping formats. If this port is part of a protection
group, this parameter must be the same on both modules. Select one of the
following values:
■ Non-Sequential (default).
■ Sequential.
Line Build Out: Select the length of cable between the node and the
intermediate patch panel:
■ 255–450 ft.
templates (of type ds_ptp_pm). Default value is default, which contains
for DS3 ports.
ds_ptp) to customize service-affecting and non-service-affecting alarm
severities. Default is the default ds_ptp alarm profile.
unlock and enable the port.

Table 1-17 Change DS3TMX Port Parameters (continued)
Step Procedure
7 Click Apply.
8 The Change DS3TMX Port Parameters procedure is complete.

Before You Change EC1 Port Parameters
Before You Review this information before you change any parameters on an EC1 port.
Change EC1
Port Table 1-18 EC1 Port Requirements
Parameters
Hardware
You can change the EC1 interface parameters on Volume 1, General Information,
■ DS3/EC1 Clear Channel (EC1 interface).
■ DS3 Transmux module (EC1 interface).
Software

These procedures describe the steps to change Volume 5, TransNav Management System,
configurable parameters only. See Volume 5, Section 3, Chapter 4,” EC1 Port Configuration,
TransNav Management System for descriptions page 3-43.
To monitor performance on an EC1 port, know Volume 5, TransNav Management System,



Change EC1 Port Parameters
Change EC1 Use this procedure to customize behavior of an EC1 interface.

Port
Parameters Table 1-19 Change EC1 Port Parameters
Step Procedure
1 Review the information in Before You Change EC1 Port Parameters,

2 In Shelf View, click a port (1 through 12) in a working DS3 Clear Channel
or DS3 Transmux module.
3 Click the Config tab to display the DS3 Port Configuration screen.
Step 2
Step 3
Step 4
Figure 1-15 EC1 Port Configuration Screen
4 If the port is unlocked, lock the port. Click the Lock icon , located in the
lower left corner of the screen.
5 Switch the port from a DS3 port to an EC1 port. Select EC1 and click
Switch.
Figure 1-16 Switch to EC1

Table 1-19 Change EC1 Port Parameters (continued)
Step Procedure
6 Click Yes to confirm the switch.
Figure 1-17 Confirm Switch to EC1
7 The EC1 Port Configuration screen appears.
Step 8
Step 9
Step 10 Step 11
Figure 1-18 EC1 Port Configuration Screen

Table 1-19 Change EC1 Port Parameters (continued)
Step Procedure
8 Change any of the following parameters for the EC1 interface:

AIS Mask (Alarm Indication Signal Mask): Select one of the following:
Line Build Out: The cable length from the node to the other end of the
EC-1 connection. Select one of the following:
■ 225–450 ft.
SfBer-L: Measures the transmission quality (bit error ratio) of failed
signals on the line. 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.
SdBer-L: Measures the transmission quality (bit error ratio) of degraded
signals on the line. 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:
templates (of type ec1_ptp_pm). Default value is default, which contains
for EC1 ports.
ec1_ptp) to customize service-affecting and non-service-affecting alarm
severities. Default is the default ec1_ptp alarm profile.
11 Click Apply.
12 The Change EC1 Port Parameters procedure is complete.

Before You Change Ethernet Port Parameters
Before You Review this information before you change any parameters on an Ethernet port.
Change
Ethernet Port Table 1-20 Ethernet Port Requirements
Parameters
Hardware
You can change the Ethernet interface parameters Volume 1, General Information,
on the following hardware: Section 2—Hardware Descriptions.
■ GbE LX -VC.
■ 2-port GbE LX-VC plus 8-port
100BaseFX-VC.
■ 2-port GbE LX-VC plus 16-port
10/100BaseTX-VC.
■ 2-port GbE SX-VC plus 16-port
10/100BaseTX-VC.
■ 10/100BaseTX-VC.
Software

configurable parameters only. See Volume 5, Section 3, Chapter 4,” Ethernet Port
TransNav Management System for descriptions Configuration, page 3-46.
To monitor performance on an Ethernet port, Volume 5, TransNav Management System,

know how to use the performance monitoring Section 6, Chapter 1—“Performance


Change Ethernet Port Parameters
Change Use this procedure to customize behavior of an Ethernet interface.

Ethernet Port
Parameters Table 1-21 Change Ethernet Port Parameters
Step Procedure
1 Review the information in Before You Change Ethernet Port

2 In Shelf View, click an Ethernet port.
3 Click the Config tab to display the Ethernet Port Configuration dialog
box.
Steps 5
and 6
Step 8
Figure 1-19 Ethernet Port Configuration Screen
4 If this is an ETH100TX port, go to Step 5.

If this is an ETHGBE or ETH100FX port, go to Step 6.
5 If this link is not auto-negotiated (Auto-negotiation = OFF), change any
of the following parameters for the ETH100TX interface:
Duplex (read-only in GUI, but configurable in CLI. Use the set interface
eth-tx command in the CLI.): 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.
Speed: Set the data rate of the link. 100Mps (default) or 10Mbps.

Table 1-21 Change Ethernet Port Parameters (continued)
Step Procedure
6 Change any of the following parameters for any Ethernet interface:

Auto-negotiation (ETH100TX and GBE ports only): Auto-negotiation is
a link startup and initialization procedure.
■ On (default): Negotiate the speed, pause frame, and duplex attributes
of the link. See Volume 5, TransNav Management System, Table 3-2
Auto-negotiation actions, page 3-47 to determine how the link
behaves based on the negotiated actions between the two ends of the
link.
■ Off: Link starts up and initializes with the values in the Speed and
Duplex fields. Pause frame is always disabled.
Transmitter State: Displays whether the laser on a GBE or an ETH100FX
port is turned on or off.
■ On (default).
■ Off.
Integrity Control (ports with dedicated point-to-point Ethernet services
only): Monitors the status of Ethernet ports and the associated transport
connection. Applies when the dedicated point-to-point service connects
two Ethernet ports on different nodes (not the same node) and must be
enabled on both ports to operate.
■ Disable (default): Link Integrity is not used on this port.
■ Enabled: A failure on this port causes the remote port to be signaled to
shut down. A failure on the transport paths between the local and
remote port causes this port to be shut down. A failure on the remote
port (if enabled as well) causes this port to be shut down.
Jumbo Frame Supt: Indicates whether jumbo frames are supported.
Select one of the following:
■ Enabled (default): Jumbo frame support is enabled.
■ Disabled: Jumbo frame support is disabled. Received jumbo frames
will be dropped and no jumbo frames will be transmitted.
Jumbo Frame Size: Enter the jumbo frame size (available only when
Jumbo Frame Supt is Enabled). Range is 1522–9600 bytes. Default is
9600 bytes.

Table 1-21 Change Ethernet Port Parameters (continued)
Step Procedure

templates (of type ethernet_ptp_pm). Default value is default, which
contains default thresholds for performance monitoring parameters and
thresholds for Ethernet ports.
ethernet_ptp) to customize service-affecting and non-service-affecting
alarm severities. Default is the default ethernet_ptp alarm profile.
9 Click Apply.
10 The Change Ethernet Port Parameters procedure is complete.

Before You Change SONET Port Parameters
Before You Review this information before you change any parameters on a SONET port.
Change
SONET Port Table 1-22 SONET Port Requirements
Parameters
Hardware
You can change the SONET interface parameters on Volume 1, General Information,
■ OC-3/STM-1.
■ OC-12/STM-4.
■ OC-48/STM-16.
■ OC-192/STM-64.
■ GCM with 1-port OC-12/STM-4 (optical
interface).
interface).
Software


Configure parameters only on working ports when a Section 2—Creating Protection Groups.
port is configured as part of a protection group.
Parameters on a protection port are automatically
set to those configured for the same port on the
working module.
configurable parameters only. See Volume 5, Section 3, Chapter 4,” SONET Port
TransNav Management System for descriptions of Configuration, page 3-50.
other fields on screen.
To monitor performance on an STM port, know Volume 5, TransNav Management System,

how to use the performance monitoring templates. Section 6, Chapter 1—“Performance Monitoring,”
IMPORTANT!: Default threshold values in the page 6-1.
sonet_ptp_pm template are based on performance Volume 4, Maintenance and Testing, Section 1,
monitoring for OC-3. Turin recommends Chapter 1—“Performance Monitoring,” page 1-1.
customizing these templates for rates other than
OC-3.

non-service-affecting alarm severities, know how to Section 6, Chapter 3—“Alarms,” page 6-37.
use alarm profiles. Volume 4, Maintenance and Testing, Section 1,

Change SONET Port Parameters
Change Use this procedure to customize behavior of a SONET interface.

SONET Port
Parameters Table 1-23 Change SONET Port Parameters
Step Procedure
1 Review the information in Before You Change SONET Port

2 In Shelf View, click the working port on any one of the following modules:
■ OC-3/STM-1.
■ OC-12/STM-4.
■ OC-48/STM-16.
■ OC-192/STM-64.
■ GCM with 1-port OC-12/STM-4 (optical interface).
■ GCM with 1-port OC-48/STM-16 (optical interface).
3 Click the Config tab to display the SONET Port Configuration screen.
Step 4
Steps 5
and 6
Step 7
Step 8 Step 9
Figure 1-20 SONET Port Configuration Screen

Table 1-23 Change SONET Port Parameters (continued)
Step Procedure
4 Change any one of the following parameters for the SONET interface:
AIS Mask (Alarm Indication Signal Mask):
SFBER-L: Measures the transmission quality (bit error ratio) of failed
signals on the optical 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:
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:
5 If this is an OC-12, OC-48, or OC-192 interface, 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.

Table 1-23 Change SONET Port Parameters (continued)
Step Procedure
6 If this is an OC-12, OC-48, or OC-192 interface AND the system uses the
DCC bytes to communicate with other nodes in this network, specify
which DCC bytes are processed. You can only change the value in this
parameter if the value in Control Data is Disabled.
In the Terminate DCC parameter, specify one of the following values:
■ Section: specifies that the interface use the D1-D3 bytes (192 Kbps) of
the first STS on this interface for management traffic.
■ Line (default): specifies that the interface use the D4-D12 bytes (576
Kbps) of the first STS on this interface for management traffic.
■ Line&Section: specifies that the interface use the combined section
DCC and line DCC bytes from the first, second, and third STS on the
interface (2.3 Mbps) for management traffic.
templates (of type sonet_ptp_pm). Default value is default, which
contains default thresholds for performance monitoring parameters and
thresholds for SONET ports.
sonet_ptp) to customize service-affecting and non-service-affecting alarm
severities. Default is the default sonet_ptp alarm profile.
9 Click Apply.
10 The Change SONET Port Parameters procedure is complete.


Chapter 5
TransAccess 100 Mux Configuration
Introduction The TransAccess 100 Mux (T100) connects to the Traverse shelf through a
10/100BaseT port to an Ethernet hub connected to the Traverse system itself. Use the
TransNav management system to remotely manage the configuration and status of the
TransAccess 100 Mux.
This chapter contains the following information:
■ Before You Configure a TransAccess 100 Mux, page 1-47.
■ Switch to EC-1 and Port Configuration, page 1-48.
■ Add TransAccess 100 Mux to the User Interface, page 1-49.
■ Change TransAccess 100 Mux Parameters, page 1-51.
■ Configure TransAccess 100 Mux DS1 Channels, page 1-54.
Before You Review this information before you create a TransAccess 100 Mux on the user
Configure a interface.
TransAccess
100 Mux Table 1-24 TransAccess 100 Mux Requirements
Hardware
A node must have the following hardware Volume 1, General Information,

components: Section 2—Hardware Descriptions.
■ DS3/EC1 Clear Channel (EC1 interface).
■ DS3 Transmux module (EC1 interface).
■ TransAccess 100 Mux.
The TransAccess 100 Mux is physically n/a

connected to the Traverse.
The TransAccess 100 Mux connected to the EC-1
ports are not initially autodiscovered by the
TransNav management system.

Switch to EC-1 and Port Configuration
Table 1-24 TransAccess 100 Mux Requirements (continued)
Software
Timing is configured. Volume 3, Provisioning Section 1, Chapter

2—“Node and Timing Configuration”.

Add a TransAccess 100 Mux only to a working Section 2—Creating Protection Groups.
port when a module is configured as part of a pro-
tection group. Parameters on a protection module
are automatically set to those configured for the
same port on the working module.
EC1 port is configured. Volume 3, Provisioning Section 1, Chapter 4,”

Change EC1 Port Parameters.
These procedures describe the steps to change Volume 5, TransNav Management System
configurable parameters only. See Volume 5, Section 3, Chapter 4,” TransAccess 100 Mux
TransNav Management System for descriptions (T100) Configuration.
To monitor performance on a TransAccess 100 Volume 5, TransNav Management System

Mux, know how to use the performance monitor- Section 6, Chapter 1—“Performance Monitor-
ing templates. ing”.
Volume 4, Maintenance and Testing Section 1,
Chapter 1—“Performance Monitoring”.
To customize service-affecting and non-ser- Volume 5, TransNav Management System

vice-affecting alarm severities, know how to use Section 6, Chapter 3—“Alarms”.
alarm profiles. Volume 4, Maintenance and Testing Section 1,
Actions”.
Switch to EC-1 The DS3 ports connected to TransAccess 100 Muxes must be converted or “switched”
and Port from a digital signal to a SONET electrical carrier signal (DS3 to EC-1) for transport
Configuration over the SONET network. See Chapter 4—“Port Configuration,” Change EC1 Port
Parameters, page 1-35 for procedure details.

Chapter 5 TransAccess 100 Mux Configuration
Add TransAccess 100 Mux to the User Interface
Add The TransAccess 100 Mux connected to the EC-1 ports are not initially autodiscovered
TransAccess by the TransNav management system. Use this procedure to add a TransAccess 100
100 Mux to the Mux to the user interface.
User Interface
Table 1-25 Add TransAccess 100 Mux to the User Interface
Step Procedure
1 Review the information in Before You Configure a TransAccess 100

Mux, page 1-47 before you start this procedure.
2 Complete the procedure Change EC1 Port Parameters, page 1-35.
3 If the module is in a protection group, right-click the EC-1 port on the
working module.
4 Click Add T100 to display the PreProvision new T100 dialog box.
Figure 1-21 Provision new T100 Dialog Box
5 In the Name field, type a name for the for the T100.
any other special characters in the Name field.
6 Click Add. A T100 is displayed next to the EC-1 port in Shelf View.
T100
Figure 1-22 T100 Mux

Add TransAccess 100 Mux to the User Interface
Table 1-25 Add TransAccess 100 Mux to the User Interface (continued)
Step Procedure
7 Repeat Steps 1 through 5 for each new TransAccess 100 Mux.

8 The Add TransAccess 100 Mux to the User Interface procedure is
complete.
Continue to the next procedure Change TransAccess 100 Mux
Parameters, page 1-51.

Change TransAccess 100 Mux Parameters
Change Use this procedure to change default attributes for the TransAccess 100 Mux.
TransAccess
100 Mux Table 1-26 Configure a TransAccess 100 Mux
Parameters
Step Procedure
1 Complete the procedure Add TransAccess 100 Mux to the User

Interface, page 1-49.
2 In Shelf View, click the T100 displayed next to the EC-1 port.
3 Click the Config tab to display the T100 Configuration dialog box.
Figure 1-23 T100 Configuration Dialog Box
4 Enter the IP address that was set for the TransAccess 100 Mux using its
craft interface.
Ethernet IP Address
Type: aaa.bbb.ccc.ddd
5 Click Apply.
Important: The management system “discovers” the TransAccess 100
Mux based on its IP address. The management system overrides any
TransAccess 100 Mux parameters with its default parameters. The default
parameters are displayed in the T100 Configuration dialog box.
6 EC1 Port is set to slot #-port #. This is the TransAccess 100 Mux slot and
port number assignment.

Table 1-26 Configure a TransAccess 100 Mux (continued)
Step Procedure
7 Default values are displayed for the following fields:

■ PM Template (default=default). You can select any Performance
Monitoring Template of type ds3_ptp_pm previously established.
Other selections are listed if additional performance monitoring
templates were created.
■ Alarm Profile (default=default). You can select any Alarm Profile of
type ds_ptp previously established. Other selections are listed if
additional Alarm Profiles were created.
■ BER Threshold (default=10-6). Selections from the BER list are:
10-5, 10-6, 10-7, 10-8 and 10-9.
8 Protection Mode is set to Protected; no action is required.
9 Current TX Timing displays the current timing source (Looped, Local,
ExtA or ExtB); no action is required.
10 Default values are displayed for the following fields:
■ Automatic Switching (default-Enabled). An Enabled setting will
automatically switch traffic to the standby card if the active card fails.
A Disabled setting does not switch traffic to the standby card in case
of a active card failure.
■ Active Card (default=CardA). Card A is the active card in the
TransAccess 100 Mux 1:1 protection scheme. Changing this selection
to CardB will force a switch to the protection card.DS1 Frame Mode
(default=ds1SuperFrameMode). Selections are:
ds1ExtSuperFrameMode and ds1UnFrameMode.
■ Line Build Out (default=0to225ft). The other selection is 225to450ft.
Line Build Out is the length of the cable between the TransAccess 100
Mux and the node.
■ Manual TX Timing (default=None). You may override the default
timing priority by selecting a manual TX timing source Looped
(timing derived from the incoming EC-1 signal), or Local (internally
generated clock) as the primary TransAccess 100 Mux timing source.
■ Ext Timing Ref (default=None). Selections are: ProvisionExtA
(External BITS A), ProvisionExtB (External BITS B),
ProvisionExtAandB (External BITS A and B), ClearExtA (manually
revert to the primary timing source after a timing switch to external
BITS A) and ClearExtB (manually revert to the primary timing
source after a timing switch to external BITS B).
■ Timing Mode (default=Revertive). The other selection is
NonRevertive.
11 Select InService from the Service Mode list to put the TransAccess 100
Mux in service.

Table 1-26 Configure a TransAccess 100 Mux (continued)
Step Procedure
12 Click Apply if you have changed any of the T100 default parameter
settings. These configuration parameters are applied to the TransAccess
100 Mux.
13 Click Synchronize to synchronize alarms between the TransAccess 100
Mux and management system.
14 The Configure a TransAccess 100 Mux procedure is complete.
Continue to the next procedure, Configure TransAccess 100 Mux DS1
Channels, page 1-54, to complete DS1 channel configuration fields.

Configure TransAccess 100 Mux DS1 Channels
Configure Use this procedure to change default attributes for the DS1 channels on the
TransAccess TransAccess 100 Mux.
100 Mux DS1
Channels Table 1-27 Configure TransAccess 100 Mux DS1 Channels
Step Procedure
1 Complete the procedure Change TransAccess 100 Mux Parameters,

page 1-51.
2 In Shelf View, click the T100 displayed next to the EC-1 port.
3 Click the Config tab to display the T100 Configuration dialog box.
4 The DS1 table located at the bottom of the T100 Configuration dialog
box allows you to configure information for the 28 DS1 channels (ports).
Note: Resize the DS1 table and use the scroll bar to view all 28 channels.
Figure 1-24 T100 Configuration Dialog Box

Table 1-27 Configure TransAccess 100 Mux DS1 Channels (continued)
Step Procedure
5 The following default values are displayed for the DS1 channels 1-28:
■ Ch #. This is the channel number, range is 1–28.
■ Ch Name (default=PTP-1 through PTP-28). To change the channel
name, click the Ch Name field and type the name of the channel.
■ Line Code (default=AMI) Alternate Mark Inversion. The other
available selection is B8ZS (Bipolar with Eight Zero Substitution).
■ Line Build Out (default=0to133ft). Other selections are: 133to266ft,
266to399ft, 399to533ft and 533to665ft. Line Build Out is the length
of the cable from the TransAccess 100 Mux to the next piece of
terminating equipment on the customer (tributary) side; for example, a
DS1 patch panel.
■ Customer (default=No Customer Selected). Select your Customer
from the list of defined customers.
6 Select InService from the Service Mode list to place the channel in
service.
7 Select Equipped from the Interface Equipped list.
8 Repeat Steps 4 through 7 for each DS1 channel (port).
9 Click Apply if you have changed any of the T100 default parameter
settings. These configuration parameters are applied to the TransAccess
100 Mux.
10 Click Synchronize to synchronize alarms between the TransAccess 100
Mux and the management system.
11 Repeat the Configure TransAccess 100 Mux DS1 Channels procedure for
each TransAccess 100 Mux.
12 The Configure TransAccess 100 Mux DS1 Channels procedures is
complete.


Chapter 6
DCC Tunnel Configuration
Introduction The data communications channel (DCC) carries operations, administration,

maintenance, and provisioning information between nodes in a network. You can use
the section DCC of any SONET interface to connect third-party equipment
transparently over a Traverse network. You tunnel a third-party DCC through the
network using the section DCC bytes of the associated SONET interface.
This chapter contains the following information.
■ DCC Tunnel Example, page 1-58.
■ Before You Tunnel a DCC, page 1-59.
■ Tunneling a DCC Through a Traverse Network, page 1-61.

DCC Tunnel Example
DCC Tunnel For example, a third party vendor uses section bytes of the first STS to carry OAM&P
Example information in their network. In order to tunnel the DCC bytes through a Traverse
network, you have to create a DCC tunnel at each node in the network.
Tunnel 1 = Tunnel 5 =
Source N1-S1-STS#-1 Source N5-S13-STS#-4
Dest. N1-S14-STS#-4 OC-48 Ring Dest. N5-S1-STS#-1
DCC Tunnels = STS#4
3rd Party 3rd Party

Equipment 2 3 Equipment
OC-12 OC-12
Node 1 4 Node 5
Figure 1-25 Tunneling 3rd Party DCC through a Traverse Network
In a Traverse network, the Control Plane uses the DCC bytes of the first, second, and
third STSs on all trunk interfaces to provide a data communication link between
directly connected Traverse nodes. Therefore, you have to create a DCC tunnel from
the first STS on the interface connected to the external equipment to the STS on the
trunk of the first and last node. The following table lists each DCC tunnel you would
configure in the above example.
Table 1-28 DCC Tunnels Hop-by-Hop
Node Source Destination
Type Number Type Number
Node 1 OC-12 tributary STS #1 OC-48 trunk STS #4
Node 2 OC-48 trunk STS #4 OC-48 trunk STS #4
Node 5 OC-48 trunk STS #4 OC-12 tributary STS #1

Chapter 6 DCC Tunnel Configuration
Before You Tunnel a DCC
Before You Review this information before you tunnel DCC bytes through a Traverse network.
Tunnel a DCC
Table 1-29 DCC Tunnel Requirements
Hardware
Create a DCC tunnel between two SONET Volume 1, General Information, Section 2,
interfaces on the same node. You can use any of Chapter 3—“SONET/SDH Modules”.
the following hardware components:
■ OC-3/STM-1.
■ OC-12/STM-4.
■ OC-48/STM-16.
■ OC-48/STM-16 VCX (optical interface).
■ OC-192/STM-64.
interface).
interface).
Interface Types. The interfaces can be of the n/a

same or different types. For example, you can cre-
ate a tunnel between an STS on an OC-3 interface
and a STS on an OC-12 interface.
Interworking. You can create a DCC tunnel n/a

between an SDH interface and a SONET inter-
face. The interfaces can be the same or different
types.
Software

DCC bytes. Volume 3, Provisioning, Section 1, Chapter 4,”

For OC-3 interfaces, you can use the section bytes Change SONET Port Parameters, page 1-43.
of any STS.
If the Control Data parameter is enabled on the
interface, you can use the section bytes of these
STSs to tunnel DCC traffic:
■ OC-12: STSs 4–12
■ OC-48 and OC-192: STSs 4–48
If the Control Data parameter is disabled on the
interface, you can use the section bytes of these
STSs to tunnel DCC traffic:
■ OC-12: STSs 1–12
■ OC-48 and OC-192: STSs 1–48

Before You Tunnel a DCC
Table 1-29 DCC Tunnel Requirements (continued)
Number of DCC tunnels supported:

■ OC-3: up to 3.
■ OC-12: 9 if Control Data is enabled. 12 if
Control Data is disabled.
■ OC-48 and OC-192: 45 if Control Data is
enabled. 48 if Control Data is disabled.
The originating STS number must match the des- n/a

tination STS number. That is, if you use OC num-
ber 7 on the source interface. You must use STS
number 7 on the destination interface.
Fault management. n/a

A DCC tunnel is not protected from any network
failure.
There are no alarms on a node if a DCC tunnel
connection fails. The third-party terminating
equipment should detect any tunnel failure.
Provisioning model. Hop-by-hop. Volume 3, Provisioning, Section 3, Chapter

1—“Service Provisioning Concepts,” page 3-1.
These procedures describe how to tunnel DCC Volume 5, TransNav Management System,
bytes through a network. See Volume 5, TransNav Section 3, Chapter 5—“DCC Tunnels,”
Management System for descriptions of other page 3-59.
fields on screen.

Chapter 6 DCC Tunnel Configuration
Tunneling a DCC Through a Traverse Network
Tunneling a Review the information in Before You Tunnel a DCC, page 1-59 before you start this
DCC Through a procedure. Use this procedure to help you tunnel a third party section DCC bytes
Traverse through a Traverse network.
Network
Table 1-30 DCC Tunnel Configuration
Step Procedure
1 In Shelf View, click the DCC Tunnel tab, then click New. A row appears
on the screen.
Click DCC
Tunnel tab.
Click New.
Figure 1-26 DCC Tunnel Tab
2 In each column, click the row to make the list of options appear.
Figure 1-27 Click a Row
■ From the SourcePort column, select the port that is connected to the
third party equipment.
■ From the Source list, select an STS number.
■ From the DestinationPort list, click the trunk port for the network.
■ From the Destination list, select an STS number.

Tunneling a DCC Through a Traverse Network
Table 1-30 DCC Tunnel Configuration (continued)
Step Procedure
3 Click Add All New to add the DCC tunnel to the node.
4 Repeat Steps 1–3 at each intermediate node in the network.
5 On the last node, create a DCC tunnel (see Steps 1–3 of this procedure).
The destination STS number must match the originating STS number. That
is, if you use STS #7 on the source interface. You must use STS #7 on the
destination interface.
6 The DCC Tunnel Configuration procedure is complete.

S ECTION 2 C REATING P ROTECTION G ROUPS
S ECTION 2CREATING PROTECTION GROUPS
Contents
Chapter 1
Overview of Protection Groups
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Equipment Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Line Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Path Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Chapter 2
Create an Equipment Protection Group
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
Before You Configure Equipment Protection . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
Guidelines to Create an Equipment Protection Group . . . . . . . . . . . . . . . . . . 2-4
Create an Equipment Protection Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
Chapter 3
Create a 1+1 APS Protection Group
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
Example of 1+1 APS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
Before you Create a 1+1 APS Protection Group. . . . . . . . . . . . . . . . . . . . . . . 2-8
Create a 1+1 APS Protection Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9
Chapter 4
Create a BLSR Protection Group
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13
Example of a BLSR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14
Squelching. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14
Before You Create a BLSR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15
Guidelines to Create a BLSR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16
Create a BLSR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16
Chapter 5
Create a 1+1 Path Protection Group
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-21
Example of a 1+1 Path Protection Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22
Before you Create a 1+1 Path Protection Group . . . . . . . . . . . . . . . . . . . . . . 2-23
Guidelines to Create a 1+1 Path Protection Group. . . . . . . . . . . . . . . . . . . . . 2-24
Create a 1+1 Path Protection Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-24

Volume 3 Section 2 Creating Protection Groups
Chapter 6
Create a UPSR Protection Group
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-27
Example of a UPSR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-28
Before You Create a UPSR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-29
Guidelines to Create a UPSR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-30
Create a UPSR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-30
List of Figures
Figure 2-1 Select a 1:1 Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
Figure 2-2 Add Equipment Protection Group Screen . . . . . . . . . . . . . . . . . . . 2-5
Figure 2-3 Select Protecting and Working Cards . . . . . . . . . . . . . . . . . . . . . . 2-6
Figure 2-4 Protection Groups Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
Figure 2-5 1+1 APS in a Linear Chain Topology . . . . . . . . . . . . . . . . . . . . . . 2-7
Figure 2-6 Select 1+1 APS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9
Figure 2-7 Add 1+1 Protection Group Screen. . . . . . . . . . . . . . . . . . . . . . . . . 2-9
Figure 2-8 Select Protecting and Working Ports . . . . . . . . . . . . . . . . . . . . . . . 2-10
Figure 2-10 OC-192 2F BLSR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14
Figure 2-11 Select BLSR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16
Figure 2-12 Add BLSR Ring Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17
Figure 2-13 West and East Ports for BSLR . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-18
Figure 2-14 Synchronize Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-18
Figure 2-15 Protection Rings Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19
Figure 2-16 Creating 1+1 Path Protection with a Protection Group . . . . . . . . . 2-22
Figure 2-17 Select 1+1 Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-24
Figure 2-18 Add 1 Plus 1 Protection Group Screen . . . . . . . . . . . . . . . . . . . . . 2-25
Figure 2-20 Bridging and Selecting Signals in a UPSR . . . . . . . . . . . . . . . . . . 2-28
Figure 2-21 Select UPSR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-30
Figure 2-22 Add UPSR Ring Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-31
Figure 2-23 West and East Ports for SNCP/UPSR Ring . . . . . . . . . . . . . . . . . 2-31
Figure 2-24 Synchronize Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-32
Figure 2-25 Protection Rings Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-32

List of Tables
Table 2-1 Equipment Protection Requirements . . . . . . . . . . . . . . . . . . . . . . 2-3
Table 2-2 Create an Equipment Protection Group . . . . . . . . . . . . . . . . . . . . 2-4
Table 2-3 1+1 APS Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
Table 2-4 Create a 1+1 APS Protection Group . . . . . . . . . . . . . . . . . . . . . . . 2-9
Table 2-5 BLSR Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15
Table 2-6 Create a BLSR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16
Table 2-7 1+1 Path Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-23
Table 2-8 Create a 1+1 Path Protection Group. . . . . . . . . . . . . . . . . . . . . . . 2-24
Table 2-9 UPSR Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-29
Table 2-10 Create a UPSR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-30


Chapter 1
Overview of Protection Groups
Introduction Depending on the network requirements, the Traverse supports a selection of methods
to protect traffic.
This chapter includes the following topics:
■ Equipment Protection, page 2-1.
■ Equipment Protection, page 2-1.
■ Line Protection, page 2-1.
■ Path Protection, page 2-2.
All system components including are easily accessible and hot-swappable.
Additionally, both hardware and software upgrades can be performed “in-service”
without interruption to existing network traffic. This capability allows the transport
network to expand gracefully as new customers and service requirements are added.
Equipment Equipment protection groups use one piece of equipment to provide redundancy for
Protection another. The Traverse supports the following types of equipment protection:
■ 1:1 equipment protection. This protection scheme uses one piece of equipment to
physically protect another.
■ 1:2 equipment protection.This protection scheme uses one piece of equipment to
protect up to two others.
To create equipment protection groups, see Chapter 2—“Create an Equipment
Protection Group,” page 2-3.
Line Protection Line protection switching is a traffic protection mechanism based on SONET line level
indications. A line is the transmission medium and the associated equipment that
transports information between two network elements: one which originates the line
signal and one that terminates it. Line protection switching is a protection mechanism
coordinated by the nodes on either side of the failure condition using the automatic
protection switching (APS) signaling protocol.

Volume 3, Section 2: Creating Protection Groups
Path Protection
APS 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.
1+1 APS
1+1 APS 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.
To create a 1+1 APS protection group, see Chapter 3—“Create a 1+1 APS Protection
Group,” page 2-7.
BLSR
Bi-directional Line Switched Ring (BLSR) provides geographically diverse paths for
each service using a self-healing closed loop technology to protect against fiber cuts
and node failures. Protection switching is performed at the Line layer of the SONET
frame.
To create a BLSR protection group, see Chapter 4—“Create a BLSR Protection
Group,” page 2-13.
Path Path protection switching is a traffic protection mechanism based on SONET path level
Protection indications. Path protection the logical end-to-end path of traffic through a network.
1+1 path protection.

This protection mechanism uses one SONET path of any bandwidth to protect another
of the same bandwidth. In a Traverse network, use a 1+1 path protection group to
protect the transport of DS1 and VT services.
To create 1+1 path protection groups, see Chapter 5—“Create a 1+1 Path Protection
Group,” page 2-21.
UPSR
A Unidirectional Path Switched Ring (UPSR) 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. Path selection at the destination chooses
the best quality signal (working or protecting) before dropping it from the ring.
To create UPSR protection groups, see Chapter 6—“Create a UPSR Protection Group,”
page 2-27.

Chapter 2
Introduction This chapter provides configuration procedures for network link (trunk) and tributary
protection groups in a Traverse network:
■ Before You Configure Equipment Protection, page 2-3.
■ Guidelines to Create an Equipment Protection Group, page 2-4.
■ Create an Equipment Protection Group, page 2-4.
Before You Review this information before you create an equipment protection group.
Configure
Equipment Table 2-1 Equipment Protection Requirements
Protection
Read the information in Section 1, Chapter 1—“Provisioning Overview”.
Hardware
The Traverse supports equipment protection for Volume 1, General Information,

the following hardware components: Section 2—Hardware Descriptions.
■ DS1.
■ DS3/EC1 Clear Channel.
■ DS3 Transmux.
■ VT Switch.
The correct ECMs are installed. Volume 2, Installation and Configuration,

Section 3—Network Interface Cabling.
The modules must be in the correct slots. Volume 2, Installation and Configuration,
Volume 2, Installation and Configuration,
Section 7, Appendix A—“Module Placement
Planning and Guidelines,” page 7-1.
Software

Guidelines to Create an Equipment Protection Group
Table 2-1 Equipment Protection Requirements (continued)

These procedures describe the steps to create pro- Volume 5, TransNav Management System,
tection groups only. See Volume 5, TransNav Section 4, Chapter 3—“Equipment Protection
Management System for descriptions of other Switching,” page 4-13.
fields on screen.
Guidelines to For 1:1 equipment protection, the protecting slots are located in left-most slots. Each
Create an protection slot protects the next consecutive slot in the shelf.
Equipment In a 1:2 protection scheme, the middle module in a group of three modules protects the
Protection adjacent two working modules. The protection group can start in any odd or
Group even-numbered slot.
Create an Use this procedure to create an equipment protection group.

Equipment
Protection Table 2-2 Create an Equipment Protection Group
Group
Step Procedure
1 Review the information in Before You Configure Equipment Protection,

2 In Shelf View, click the Protection tab to display the Protection Groups
screen.
3 From the New list, select 1_for_N equipment.
Step 4
Figure 2-1 Select a 1:1 Equipment

Chapter 2 Create an Equipment Protection Group
Table 2-2 Create an Equipment Protection Group (continued)
Step Procedure
4 Click Add to display the Protection Group Creation tab, Add

Equipment Protection Group screen.
Step 5
Step 6
Step 7 Step 9
Figure 2-2 Add Equipment Protection Group Screen
5 In the Name field, type a name for the protection group.

any other special characters in this field.
6 Set the reversion options:
■ Select the Revertive check box to switch traffic back to the working
card when the working card 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 before switching back to the working card.
Enter a number between 1 and 60. The default value is 5.

Table 2-2 Create an Equipment Protection Group (continued)
Step Procedure
7 Select the protecting card for the protection group. On the Protecting row,
click the Card field and select the protecting card.
Figure 2-3 Select Protecting and Working Cards
8 Select the working cards for the protection group. On each Working row,
click the Card field and select the working card.
9 Click Create to create the protection group and return to the Protection
Groups screen on the Protection tab.
Figure 2-4 Protection Groups Screen
The system assigns an ID to the new protection group.

10 The Create an Equipment Protection Group procedure is complete.

Chapter 3
Introduction Use 1+1 automatic protection switch (APS) on simple point-to-point and linear chain
topologies.
This chapter contains information on creating a 1+1 APS protection group.
■ Example of 1+1 APS, page 2-7
■ Before you Create a 1+1 APS Protection Group, page 2-8.
■ Create a 1+1 APS Protection Group, page 2-9.
Example of 1+1 1+1 APS uses both the working and the protect fibers to send traffic simultaneously to
APS 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 channels at intermediate sites along a fiber route, without
unnecessary multiplexing and demultiplexing of pass-through traffic. The Traverse
platform supports simple point-to-point and linear chain topologies.
OC-N Links OC-N Links
Node1 Node2 Node 3

Tributaries
Figure 2-5 1+1 APS in a Linear Chain Topology
Configure 1+1 APS protection at for each facility connected to the next node. In this
example, configure one 1+1 APS protection group at Node 1 and Node 3. Configure
two protection groups at Node 2.

Before you Create a 1+1 APS Protection Group
Before you Review this information before you create a 1+1 automatic protection switch (APS)
Create a 1+1 group. The Traverse supports 1+1 unidirectional and bi-directional protection
APS Protection switching.
Group
Table 2-3 1+1 APS Requirements
Hardware
Each node requires at least two modules of Volume 1, General Information, Section 2—Hardware
the same data rate: Descriptions.
■ OC-3/STM-1.
■ OC-12/STM-4.
■ OC-48/STM-16.
■ OC-48/STM-16 VCX (optical
interface).
■ OC-192/STM-64.
■ GCM with 1-port OC-12/STM-4
(optical interface).
You can use the following combination of Volume 1, General Information, Section 2—Hardware
modules in a 1+1 APS protection group: Descriptions.
■ OC-12/STM-4 and a GCM with 1-port
STM-4/OC-12.
OC-48/STM-16.
Each pair of modules must be in the correct Volume 2, Installation and Configuration,
slots. Section 7—Start-up and Module Placement.
Volume 2, Installation and Configuration, Section 7,
Appendix A—“Module Placement Planning and Guide-
lines,” page 7-1.
Software
Timing is configured. Volume 3, Provisioning, Section 1, Chapter 2—“Node

and Timing Configuration,” page 1-6.
There are no line-level alarms (LOS, LOF, Click the port, click the Alarms tab, and verify no alarms
AIS-L, SF-BER-L) present on the interfaces are present.
you are using to configure the protection Volume 4, Maintenance and Testing, Section 1—System
group. Monitoring.
These procedures describe the steps to create Volume 5, TransNav Management System, Section 4,
protection groups only. See Volume 5, Tran- Chapter 4—“Facility Protection Switching,” page 4-19.
sNav Management System for descriptions

Chapter 3 Create a 1+1 APS Protection Group
Create a 1+1 Use this procedure to create a 1+1 APS protection group.
APS Protection
Group Table 2-4 Create a 1+1 APS Protection Group
Step Procedure
1 Review the information in Before you Create a 1+1 APS Protection

Group, page 2-8 before you start this procedure.
screen.
3 Add an 1+1 APS protection group. From the New list, select 1+1
MPS/APS.
Step 4
Figure 2-6 Select 1+1 APS
4 Click Add to display the Protection Group Creation tab,

Add 1+1 Protection Group screen.
Figure 2-7 Add 1+1 Protection Group Screen

Table 2-4 Create a 1+1 APS Protection Group (continued)
Step Procedure

card when the working port has recovered from the original failure
after a protection switch before switching back to the working port.
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 either 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 2-8 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.

Chapter 3 Create a 1+1 APS Protection Group
Table 2-4 Create a 1+1 APS Protection Group (continued)
Step Procedure
10 Click Add to return to the Protection Groups screen on the Protection

tab.

11 Repeat Steps 1 to 11 at the other end of the fiber link.
12 The Create a 1+1 APS Protection Group procedure is complete.


Chapter 4
Create a BLSR Protection Group
Introduction Bi-directional Line Switched Ring (BLSR) provides geographically diverse paths for
each service using a self-healing closed loop technology to protect against fiber cuts
and node failures. Protection switching is performed at the Line layer of the SONET
frame.
The Traverse supports for 2-fiber (2F) BLSR. 2F BLSR offers substantial capacity
advantages in interoffice and access networks that have distributed mesh traffic
patterns because of its ability to reuse bandwidth, as traffic is added and dropped at
various locations around the ring.
■ Example of a BLSR, page 2-14.
■ Squelching, page 2-14.
■ Before You Create a BLSR, page 2-15.
■ Guidelines to Create a BLSR, page 2-16.
■ Create a BLSR, page 2-16.

Example of a BLSR
Example of a BLSR also provides the ability to reuse bandwidth. When traffic is dropped at one node
BLSR in a BLSR configuration, the remaining capacity is then available for traffic at that
node. BLSR assigns half of the bandwidth to working traffic and the other half is
reserved as a protection route. For example, in an OC-48 BLSR, the first 24STS-1s
carry the working traffic the other 24STS-1s are assigned as protection.
In the event of a single failure or a failure in a segment in a ring, the Traverse system
restores all protected traffic.
STS Channels
Tributaries 1 to 24: Working
25 to 48: Protection
Node 1
Tributaries Tributaries
Node 4 Node 2
Node 3 Tributaries
Figure 2-10 OC-192 2F BLSR
Squelching The Traverse supports BLSR squelching. Nodes adjacent to a ring failure replace
non-restorable traffic with a path layer alarm indication signal (AIS) to notify the
far-end node of the interruption in service. The squelching feature automatically
generates squelch tables, no manual record keeping is required.
The squelch table first source node ID of the traffic entering the node and the last
destination node ID of the traffic exiting the node for each time slot that the node is
terminating (adding/dropping) or passing through.
Provisioning a squelch table occurs during the service provisioning.
For information on squelching and the squelch table, see Volume 5, TransNav
Management System, Section 4, Chapter 1—“BLSRs”.

Chapter 4 Create a BLSR Protection Group
Before You Create a BLSR
Before You Review this information before you create a BLSR.

Create a BLSR
Table 2-5 BLSR Requirements
Hardware
There can be up to 16 nodes in a one ring. n/a
Each node requires at least two OC modules of Volume 1, General Information,

the same data rate: Section 2—Planning and Engineering.
■ OC-48/STM-16.
■ OC-192/STM-64.
interface).
You can use an OC-48/STM-16 and a GCM with

1-port OC-48/STM-16 in a a BLSR protection
group.
The nodes are physically connected. The East Volume 2, Installation and Configuration.
module on one node is physically connected to
the West module on the next.
Software

There are no line-level alarms (LOS, LOF, AIS-L, Click the port, click the Alarms tab, and verify no
SF-BER-L) present on the interfaces you are alarms are present.
using to configure the ring. Volume 4, Maintenance and Testing,
Section 1—System Monitoring.
The Control Data parameter is Enabled on each In Shelf View, click the port, click the Config tab,
interface you are using to configure the ring. and verify Control Data = Enabled.
Volume 3, Provisioning, Section 1, Chapter
4—“Port Configuration”.
The link is in the Enabled state. If the link is dis- In Map View, click the link, click the Config tab
abled (or is preprovisioned), you cannot synchro- and verify the Operational State is Enabled.
nize the ring. Volume 5, TransNav Management System,
Section 3, Chapter 1—“Creating and Deleting
Equipment Using Preprovisioning,” page 3-1.
tection groups only. See Volume 5, TransNav Section 4, Chapter 1—“BLSRs,” page 4-1.
Management System for descriptions of other
fields on screen.

Guidelines to Create a BLSR
Guidelines to A single Traverse 2000 node supports up to four (4) OC-192 or up to nine (9) OC-48 2F
Create a BLSR BLSR protection groups.
A single Traverse 1600 node supports up to three (3) OC-192 or up to seven (7) OC-48
2F BLSR protection groups.
There can be up to 16 nodes in a 2F BLSR.
The ports that are in the BLSR protection group can only be part of the BLSR
protection group.
The East module on one node is physically connected to the West port on the next.
Create a BLSR Use this procedure to create a BLSR.
Table 2-6 Create a BLSR
Step Procedure
1 Review the information in Before You Create a BLSR, page 2-15 before
you start this procedure.
2 In Map View, click the Protection tab to display the Protection Rings
screen.
3 From the New list, select BLSR.
Step 4
Figure 2-11 Select BLSR

Create a BLSR
Table 2-6 Create a BLSR (continued)
Step Procedure
4 Click Add to display the Protection Group Creation tab, Add BLSR
Ring screen.
Step 5
Step 6
Step 7
Step 8
Step 9 Step 10 Step 11 Step 12
Figure 2-12 Add BLSR Ring Screen

line when the working line has recovered from the original failure
after a protection switch before switching back to the working line.
7 Card Type (default=OC-48).
■ Select OC-48 for OC-48 interfaces
■ Select OC-192 for OC-192 interfaces.

Create a BLSR
Step Procedure
8 Add nodes to the ring. In Map View, click a node to add it to the ring. The
nodes are displayed on screen as you select them from Map View.
Step 8
Figure 2-13 West and East Ports for BSLR
9 The system automatically assigns IDs consecutively beginning with “0”

for the first node assigned to the ring. You can manually assign a node ID
by selecting a number (0–15) from the ID list. Node IDs are not required to
be consecutive, but a node ID can only be used once in a ring.
From the ID list, select a node identification number.
10 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.
11 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 modules in the shelf.
12 Click Add.
13 In Synchronize Protection Group dialog box, click Yes to propagate
protection group information to all nodes in the ring.
Figure 2-14 Synchronize Confirmation

Create a BLSR
Step Procedure
14 The protection group is listed in the Protection Rings screen and is

assigned a 4-digit Ring ID.
Figure 2-15 Protection Rings Screen
15 The Create a BLSR procedure is complete.

Create a BLSR

Chapter 5
Introduction 1+1 path protection is a protection mechanism that uses one SONET path of any
bandwidth to protect another of the same bandwidth. In a Traverse network, use a 1+1
path protection group to protect the transport of DS1 and VT services.
This chapter contains information on creating a 1+1 path protection group.
■ Example of a 1+1 Path Protection Group, page 2-22.
■ Before you Create a 1+1 Path Protection Group, page 2-23.
■ Guidelines to Create a 1+1 Path Protection Group, page 2-24.
■ Create a 1+1 Path Protection Group, page 2-24.

Example of a 1+1 Path Protection Group
Example of a Use 1+1 path protection groups to configure path protection for the following service
1+1 Path types:
Protection ■ DS1.
Group ■ DS1-Mux.
■ DS3-TMX.
■ SONET-VT.
In the following example, first create and activate the sequence of unprotected services
(Steps 1, 2, 3, and 4). Then create the 1+1 path protection group at the Add and Drop
nodes (Steps 5 and 6). The pass through services at the intermediate nodes can be on
any available path.
1. Service Type: DS1-Mux 2. Service Type: SONET-STS (Pass Through) 4. Service Type: SONET-VT
Src: Node 1/slot-1/all ports Src: Node 2/slot 15/port-1/sts-4 Src: Node 1/slot 15/port-1/sts-4/vtg1-vt1
Dest: Node 4/slot-15/port-1/sts-4 Dest: Node 2/slot-16/port-1/sts-4 Dest: Node 4/slot-1/port-1/sts-1/vtg1-vt1
Protection Type: Unprotected Protection Type: Unprotected Protection Type: Unprotected
5. STS Path Protection Group 6. STS Path Protection Group

Working: Node 1/slot-15/port-1/sts-4 Working: Node 6/slot-15/port-1/sts-4
Protecting: Node 1/slot-16/port-1/sts-35 Protecting: Node 6/slot-16/port-1/sts-35
2
W P
5 6
W P
1 2 Node 3 2
Unprotected Unprotected
OC-48 3 3 OC-48
Node 2 3 Node 5
DS1 OC48 OC48 OC12 OC48 OC48

VT
Slot 1 Slot 15 Slot 16 Slot 1 Slot 8 Slot 15 Slot 16
Node 1 (Source node) Node 4 Node 6 (Drop node)
3. Service Type: SONET-STS (Pass Through)

Src: Node 2/slot 15/port-1/sts-35
Dest: Node 2/slot-16/port-1/sts-35
Protection Type: Unprotected
Figure 2-16 Creating 1+1 Path Protection with a Protection Group

Chapter 5 Create a 1+1 Path Protection Group
Before you Create a 1+1 Path Protection Group
Before you Use a 1+1 path protection group to protect the transport of DS1 and VT services in a
Create a 1+1 Traverse network. Review this information before you create a 1+1 path protection
Path group.
Protection
Group Table 2-7 1+1 Path Requirements
Hardware
Create 1+1 path protection on trunk modules Volume 1, General Information, Section 2—Hardware
of the same data rate: Descriptions.
■ OC-3/STM-1.
■ OC-12/STM-4.
■ OC-48/STM-16.
■ OC-48/STM-16 VCX (optical
interface).
■ OC-192/STM-64.
You can use the following combination of Volume 1, General Information, Section 2—Hardware
modules in a 1+1 path protection group: Descriptions.
STM-4/OC-12.
OC-48/STM-16.
Each pair of modules must be in the correct Volume 2, Installation and Configuration,
slots. Section 7—Start-up and Module Placement.
Volume 2, Installation and Configuration, Section 7,
Appendix A—“Module Placement Planning and Guide-
lines,” page 7-1.
Software
Timing is configured. Volume 3, Provisioning, Section 1, Chapter 2—“Node

and Timing Configuration,” page 1-6.
There are no path-level alarms (LOS, LOF, Click the port, click the Alarms tab, and verify no alarms
AIS-P, SF-BER-P) present on the interfaces are present.
you are using to configure the protection Volume 4, Maintenance and Testing, Section 1—System
group. Monitoring.
These procedures describe the steps to create Volume 5, TransNav Management System, Section 4,
a 1+1 path protection group only. See Vol- Chapter 4—“Facility Protection Switching,” page 4-19.
ume 5, TransNav Management System for
descriptions of other fields on screen.

Guidelines to Create a 1+1 Path Protection Group
Guidelines to The guidelines to create a 1+1 path protection group are:

Create a 1+1 ■ Use the protection group model to create path protection for the following service
Path types:
Protection – DS1.
Group – DS1-Mux.
– DS3-TMX.
– SONET-VT.
See Section 5, Chapter 1—“Creating 1+1 Path-Protected Services” for the
complete procedure to create path protection for these services.
■ The network interfaces at the source and drop nodes cannot be part of a 1+1 APS
or BLSR protection group. However, the interfaces can be part of a UPSR or
unprotected.
■ Provision the protection group after the initial service is provisioned. This
sequence allows for in-service upgrades of any already activated service.
Create a 1+1 Use a 1+1 path protection group to protect the transport of DS1 and VT services in a
Path Traverse network. Review this information before you create a 1+1 path protection
Protection group. Use this procedure to create a 1+1 path protection group.
Group
Table 2-8 Create a 1+1 Path Protection Group
Step Procedure
1 Review the information in Before you Create a 1+1 Path Protection

Group, page 2-23 before you start this procedure.
screen.
3 Add a 1+1 path protection group. From the New list, select 1+1_path.
Step 4
Figure 2-17 Select 1+1 Path

Chapter 5 Create a 1+1 Path Protection Group
Table 2-8 Create a 1+1 Path Protection Group (continued)
Step Procedure
4 Click Add to display the Protection Group Creation tab,

Add 1+1 Protection Group screen.
Figure 2-18 Add 1 Plus 1 Protection Group Screen

6 Select the bandwidth of the paths. From the Concatenation parameter,
select the total bandwidth of the path:
■ STS-1 (default).
■ STS-3c.
■ STS-12c (for OC-12 and greater interfaces only).
7 Select the protecting information.
■ Select the Protecting Port for this protection group. Click the
Protecting Port field and select the protecting port.
■ Select the Protection Path for this protection group. Click the
Protection Path field and select the protection path.

Table 2-8 Create a 1+1 Path Protection Group (continued)
Step Procedure
8 Select the working information.

■ Select the Working Port for this protection group. Click the Working
Port field and select the protecting port.
■ Select the Working Path for this protection group. Click the Working
Path field and select the protection path.
9 Click Create to create the protection group and return to the Protection
Groups screen on the Protection tab.

10 The Create a 1+1 Path Protection Group procedure is complete.

Chapter 6
Create a UPSR Protection Group
Introduction A Uni-directional Path Switched Ring (UPSR) is a self-healing closed loop topology
that protects against fiber cuts and node failures by providing duplicate, geographically
diverse paths for each service.
This chapter contains information on creating a UPSR protection group.
■ Example of a UPSR, page 2-28.
■ Before You Create a UPSR, page 2-29.
■ Guidelines to Create a UPSR, page 2-30.
■ Create a UPSR, page 2-30.

Example of a UPSR
Example of a A UPSR is a protection configuration that provides path protection in a unidirectional

UPSR ring topology. In a ring, there are source nodes (Node 1, destination nodes (Node 4),
and intermediate nodes (Node 2 and Node 3). Traffic enters the ring at the source node,
travels through the intermediate nodes, and exits the ring at the destination node.
Node 2
Bridging
Node 1 Node 3
Node 4
Path selection
Figure 2-20 Bridging and Selecting Signals in a UPSR
In a UPSR configuration in a Traverse network, the East module always transmits the
working signal clockwise around the ring. The West module always receives the
working signal. The East module on one node is physically connected to the West port
on the next.
UPSR in normal operation. 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. UPSR 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.

Chapter 6 Create a UPSR Protection Group
Before You Create a UPSR
Before You Review this information before you create a UPSR.

Create a UPSR
Table 2-9 UPSR Requirements
Hardware
Each node requires at least two modules of the Volume 1, General Information,
same data rate: Section 2—Hardware Descriptions.
■ OC-3/STM-1.
■ OC-12/STM-4.
■ OC-48/STM-16.
■ OC-192/STM-64.
interface).
interface).
You can use the following combination of mod- Volume 1, General Information,
ules in a protection group: Section 2—Hardware Descriptions.
OC-12/STM-4.
OC-48/STM-16.
Nodes are physically connected. The East module Volume 2, Installation and Configuration.
on one node is physically connected to the West
port on the next.
Software

There are no path-level alarms (LOS, LOF, AIS-P, Click the port, click the Alarms tab, and verify no
SF-BER-P) present on the interfaces you are alarms are present.
using to configure the ring. Volume 4, Maintenance and Testing,
Section 1—System Monitoring.
tection groups only. See Volume 5, TransNav Section 4, Chapter 2—“UPSR,” page 4-9.
fields on screen.

Guidelines to Create a UPSR
Guidelines to A single Traverse 2000 node supports up to four (4) OC-192 or up to nine (9) OC-48
Create a UPSR UPSR protection groups.
A single Traverse 1600 node supports up to three (3) OC-192 or up to seven (7) OC-48
UPSR protection groups.
There can be up to 16 nodes in a UPSR.
working signal.
The East module on one node is physically connected to the West port on the next.
Create a UPSR Use this procedure to create a UPSR.
Table 2-10 Create a UPSR
Step Procedure
1 Review the information in Before You Create a UPSR, page 2-29 before
2 In Map View, click the Protection tab to display the Protection Rings
screen.
3 Add a UPSR protection group. From the New list, select SNCP/UPSR.
Step 4
Figure 2-21 Select UPSR

Chapter 6 Create a UPSR Protection Group
Create a UPSR
Table 2-10 Create a UPSR (continued)
Step Procedure
4 Click Add to display the Protection Group Creation tab, Add UPSR
Ring screen.
Step 5
Figure 2-22 Add UPSR Ring Screen

6 Add nodes to the ring. In Map View, click a node to add it to the ring. The
nodes are displayed on screen as you select them from Map View.
Figure 2-23 West and East Ports for SNCP/UPSR Ring

Create a UPSR
Table 2-10 Create a UPSR (continued)
Step Procedure
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 modules in the shelf.
9 Click Add.
10 In Synchronize Protection Group dialog box, click Yes to propagate
protection group information to all nodes in the ring.
Figure 2-24 Synchronize Confirmation
11 The protection group is listed in the Protection Rings screen and is

assigned a 4-digit Ring ID.
Figure 2-25 Protection Rings Screen
12 The Create a UPSR procedure is complete.

S ECTION 3 C REATING S ERVICES
S ECTION 3CREATING SERVICES
Contents
Chapter 1
Service Provisioning Concepts
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
Traverse Services Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
Supported Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
ETSI to ANSI Interworking. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Multicast Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Multiplexing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
VT Switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Transmultiplexing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Resource Advisory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Transport Capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Switching Hierarchies and Service Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
Traverse Service Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
Service Creation Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7
Service Creation Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
1. Add the Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
2. Configure General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
3. Configure the Service Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . 3-8
4. Configure the Attributes of the Transport Path . . . . . . . . . . . . . . . . . . 3-9
5. Set the Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
6. Activate the Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
Before You Start Creating Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
Chapter 2
Procedures Common to All Services
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11
Add a Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
Configure General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13
Set Constraints for a Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15
Activate a Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-17
Activate Multiple Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18
Chapter 3
Creating DS1 Services
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-19
Example of DS1 Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-20
Modules Required to Create DS1 Services. . . . . . . . . . . . . . . . . . . . . . . . . . . 3-21
Before You Create DS1 Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-21

Volume 3 Section 3 Creating Services
Sources and Destinations for DS1 Services . . . . . . . . . . . . . . . . . . . . . . . . . . 3-22

Create a DS1 Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-23
Create a DS1-Mux Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-28
Chapter 4
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-35
Example of DS3 Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-36
Modules Required to Create DS3 Services . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-37
Before You Create DS3 Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-37
Sources and Destinations for DS3 Services . . . . . . . . . . . . . . . . . . . . . . . . . . 3-38
Create a DS3-CC Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-39
Create a DS3-TMX Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-46
Chapter 5
Creating SONET Services
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-53
Examples of SONET Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-54
Other SONET Services and Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-55
Modules Required to Create SONET Services . . . . . . . . . . . . . . . . . . . . . . . . 3-55
Before You Create SONET Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-55
Source and Destinations for SONET Services . . . . . . . . . . . . . . . . . . . . . . . . 3-56
Starting STS Numbers for SONET Services . . . . . . . . . . . . . . . . . . . . . . . . . . 3-57
Create a SONET-STS Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-58
Create a SONET-VT1.5 Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-66
List of Figures
Figure 3-1 End-to-End Services Creation Model . . . . . . . . . . . . . . . . . . . . . . 3-7
Figure 3-2 Hop-by-Hop Services Creation Model . . . . . . . . . . . . . . . . . . . . . . 3-7
Figure 3-3 Map View—Service Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
Figure 3-4 Define Service—General Info Screen . . . . . . . . . . . . . . . . . . . . . . 3-13
Figure 3-5 Define Service—Constraints Screen . . . . . . . . . . . . . . . . . . . . . . . 3-15
Figure 3-6 Service Tab—Activate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-17
Figure 3-7 Service Tab—Activate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18
Figure 3-8 DS1 Lease Line Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-20
Figure 3-9 DS1 Service Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-23
Figure 3-10 DS1 Service Level Agreement Screen . . . . . . . . . . . . . . . . . . . . . 3-24
Figure 3-11 DS1 Service Transport Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-25
Figure 3-12 DS1 Service Constraints Screen . . . . . . . . . . . . . . . . . . . . . . . . . . 3-27
Figure 3-13 DS1-Mux Service Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-28
Figure 3-14 DS1-Mux Service Level Agreement Screen . . . . . . . . . . . . . . . . . 3-29
Figure 3-15 DS1-Mux Service Transport Screen . . . . . . . . . . . . . . . . . . . . . . . 3-30
Figure 3-16 DS1-Mux Service Constraints Screen . . . . . . . . . . . . . . . . . . . . . . 3-33
Figure 3-17 Channelized DS3 and DS3 Services . . . . . . . . . . . . . . . . . . . . . . . 3-36
Figure 3-18 DS3-CC Service Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-39

Figure 3-19 DS3-CC Service Level Agreement Screen . . . . . . . . . . . . . . . . . . 3-40

Figure 3-20 DS3-CC Service Transport Screen . . . . . . . . . . . . . . . . . . . . . . . . 3-41
Figure 3-21 DS3-CC Service Constraints Screen . . . . . . . . . . . . . . . . . . . . . . 3-44
Figure 3-22 DS3-TMX Service Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-46
Figure 3-23 DS3-TMX Service Level Agreement Screen. . . . . . . . . . . . . . . . . 3-47
Figure 3-24 DS3-TMX Service Transport Screen. . . . . . . . . . . . . . . . . . . . . . . 3-48
Figure 3-25 DS3-TMX Service Constraints Screen . . . . . . . . . . . . . . . . . . . . . 3-51
Figure 3-26 SONET-STS and SONET-VT Services. . . . . . . . . . . . . . . . . . . . . 3-54
Figure 3-27 SONET-STS Service Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-58
Figure 3-28 SONET-STS Service Level Agreement Screen . . . . . . . . . . . . . . 3-59
Figure 3-29 SONET-STS Service Transport Screen . . . . . . . . . . . . . . . . . . . . 3-61
Figure 3-30 SONET-STS Service Constraints Screen . . . . . . . . . . . . . . . . . . . 3-65
Figure 3-31 SONET-VT1.5 Service Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-66
Figure 3-32 SONET-VT1.5 Service Level Agreement Screen . . . . . . . . . . . . . 3-67
Figure 3-33 SONET-VT1.5 Service Transport Screen . . . . . . . . . . . . . . . . . . . 3-68
Figure 3-34 SONET-VT1.5 Service Constraints Screen . . . . . . . . . . . . . . . . . 3-71
List of Tables
Table 3-1 SONET Transport Capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Table 3-2 Switching Hierarchies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
Table 3-3 DS1 Service Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
Table 3-4 DS3 Service Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
Table 3-5 SONET Service Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
Table 3-6 Ethernet Service Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
Table 3-8 Add a Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
Table 3-9 Configure General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13
Table 3-10 Set Constraints for a Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15
Table 3-11 Activate a Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-17
Table 3-12 Activate Multiple Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18
Table 3-13 Modules Required to Create DS1 Services . . . . . . . . . . . . . . . . . 3-21
Table 3-14 DS1 Service Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-21
Table 3-15 Sources, and Destinations for DS1 Services . . . . . . . . . . . . . . . . 3-22
Table 3-16 Create a DS1 Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-23
Table 3-17 Create a DS1-Mux Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-28
Table 3-18 Modules Required for DS3 Services . . . . . . . . . . . . . . . . . . . . . . . 3-37
Table 3-19 DS3 Service Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-37
Table 3-21 Create an DS3-CC Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-39
Table 3-22 Create an DS3-TMX Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-46
Table 3-23 Modules Required for SONET Services . . . . . . . . . . . . . . . . . . . . 3-55
Table 3-24 SONET Service Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-55
Table 3-25 Sources, and Destinations for SONET Services. . . . . . . . . . . . . . 3-56
Table 3-26 Valid Starting STS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-57

Table 3-27 Create a SONET-STS Service . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-58

Table 3-28 Create a SONET-VT1.5 Service . . . . . . . . . . . . . . . . . . . . . . . . . . 3-66

Chapter 1
Service Provisioning Concepts
Introduction Creating services in a Traverse network requires that you first identify switching
requirements, bandwidth requirements, and service types. This chapter explains the
particulars of services on a Traverse platform:
■ Traverse Services Definition, page 3-1.
■ Transport Capacity, page 3-3.
■ Switching Hierarchies and Service Types, page 3-4.
■ Traverse Service Types, page 3-5.
■ Service Creation Models, page 3-7.
■ Service Creation Process, page 3-8.
■ Before You Start Creating Services, page 3-10.
Traverse A service in a Traverse network connects traffic from a source to a destination. The
Services source can be a port, subport, or channel. The source can originate on any module and
Definition can be either a tributary module (service endpoint) or a trunk module (between nodes in
a network).
In general, the originating traffic type defines the type of service that you need to
provision. For example, if the traffic originates from an optical port, create an optical
service. If the traffic originates from an Ethernet port, create an Ethernet service.
The destination of the service varies depending on the connection you are creating. The
destination can be a compatible module, port, subport, or another service. Additionally,
the destination can be on the same node (node service) or on a separate node (domain
service).

Volume 3, Section 3: Creating Services
Supported Features
Supported ETSI to ANSI Interworking

Features The Traverse platform supports ETSI to ANSI interworking capabilities. That is, you
can connect an ETSI signal to an ANSI signal.
The Traverse supports the following gateway services:
■ DS1 over SDH
■ E1 over SONET
■ SDH to SONET
■ SONET to SDH
Multicast Connections
Multicast connections are connections made from one source to multiple destinations.
The Traverse system supports multicast connections for the following services:
■ SONET-STS.
■ Ethernet.
Use multicast connections to create drop-and-continue services in a Traverse network.
Multiplexing
Multiplexing is the ability to transmit two or more signals over a single channel.
Use the DS1-Mux service to map 28 DS1 ports to a VT-packed STS.
VT Switching
The Traverse system cross connects at the VT-1.5 layer. Switching at this level of
granularity requires less multiplexing and demultiplexing between STS terminations.
Also, the Traverse provides important groom-and-fill capabilities. These capabilities
mean as many lower-speed channels as possible are packed into a circuit. This packing
makes the network more efficient and enables faster service provisioning.
Multiple VT Switches can be deployed to create a larger non-blocking cross connect
fabric. These can be added in the same Traverse shelf and distributed across a network.
Transmultiplexing
Transmultiplexing is the ability to take a number of voice analog phone conversations,
convert them to digital signals, and then bundle them up into a 1.544 Mbps bit stream.
Use the DS3-Tmx service to convert a channelized DS3 into a VT-packed STS.
Resource Advisory
If this feature is enabled, the system displays only available resources. Ports, Paths, and
other resources assigned to activated services do not appear.

Chapter 1 Service Provisioning Concepts
Transport Capacity
Transport Use the following table as a reference for the transport requirements of each supported
Capacity service.
Table 3-1 SONET Transport Capacity
Transport STS-1 OC-3 OC-12 OC-48 OC-192

Payload
Mbps 51.84 155.52 622.08 2488.32 9953.28
DS1 1.544 28 84 336 1344 5376
DS3 44.736 1 3 12 48 192
VT 1.728 28 84 336 1344 5376
STS-1 48.960 1 3 12 48 192
STS-3c 150.336 — 1 4 16 64
STS-12c 599.040 — — 1 4 16
STS-48c 2,396.160 — — — 1 4
Ethernet 100 or 1000 481 Mbps 1492 Mbps 599 Mbps 1000 Mbps 1000 Mbps
1
On a virtually concatenated VC-3 (VC-3-nv), n times 48 but no greater than 1000.
2
On a virtually concatenated VC-4 (VC-4-nv), n times 149, but no greater than 1000.

Switching Hierarchies and Service Types
Switching In a Traverse network, you can switch traffic at different levels of the optical hierarchy.
Hierarchies ■ In SONET, you can switch traffic at the VT layer, at the STS layer, or the
and Service concatenated STS layers.
Types On a Traverse platform, the combination of switching requirements and the type of
source port (the port from which the service originates) determines the types of services
you need to create. Use the following table to help you determine service types. You
will need to create multiple services at each node to move traffic in your network.
Table 3-2 Switching Hierarchies
Switching Level
Source Port Type Traverse Service Type1
SONET
VT DS1 DS1
OC-N SONET-VT1.5
STS all ports on a DS1 card DS1-Mux
(DS1MUX)
DS3-CC DS3-CC
DS3-TMX DS3-Tmx
OC-N SONET- STS
ETH100TX Ethernet
ETH100FX
GBE
Concatenated STS OC-N SONET- STS
VC-Bundle
ETH100TX Ethernet
ETH100FX
GBE
1
See the next topic for a description and references for each Traverse service type.

Traverse Service Types
Traverse Use the following tables as a reference to help you define which Traverse service type
Service Types for your network:
■ DS1 Service Types, page 5.
■ DS3 Service Types, page 5.
■ SONET Service Types, page 5.
■ Ethernet Service Types, page 6.
Table 3-3 DS1 Service Types
Service Type Definition
See Chapter 3—“Creating DS1 Services,” page 3-19 for details on the following ser-
vices types:
DS1 Use this service to switch individual DS1 channels through the
network.
DS1-Mux Use this service to multiplex all 28 ports on a DS1 card onto a
transport path.
Table 3-4 DS3 Service Types
See Chapter 4—“Creating DS3 Services,” page 3-35 for details on the following ser-
vices types:
DS3-CC Use this service to transport clear channel DS3 signals.
DS3-TMX Use this service to convert a channelized DS3 into a
VT-mapped STS for transport across the network.
Table 3-5 SONET Service Types
See Chapter 5—“Creating SONET Services,” page 3-53 for details on the following
services types:
SONET-STS Use this service to transport synchronous traffic through the
network.
SONET-VT1.5 Use this service to switch individual SONET VT1.5 payloads
through the network.

Traverse Service Types
Table 3-6 Ethernet Service Types
See Section 4—Creating Ethernet Services for details on the following services types:
VC-Bundle Use this service to create non-standard concatenated signals to
transport Ethernet traffic. See Section 4, Chapter 3—“Creating
VC-Bundle Services,” page 4-17.
P2PDedicated Point-to-Point Dedicated. Use this service to extend a private
LAN network across a network. Bandwidth is dedicated to one
Ethernet (10/100 or GbE) port and data is transported over the
network using a “dedicated” transport path.
P2PShared Point-to-Point Shared. Use this service to extend a LAN
network across a network using a “shared” transport path.
IAS Internet Access Service. Use this service to aggregate Internet
traffic from multiple subscriber-side Ethernet ports (10/100 or
GbE) to one provider-side Ethernet port (10/100 or GbE)
connected to an ISP router.
TLS Transparent LAN Service (TLS). Use this service to allow
multiple Ethernet devices in multiple locations to appear as a
single private LAN (virtual LAN or VLAN).

Service Creation Models
Service You can create services in a Traverse network either end-to-end or hop-by-hop.
Creation An end-to-end service is a service you can set up between nodes. You select the source
Models of a service on one node and the destination on another. The system sets up the path
(including the alternate path if the service is protected) through the domain.
Constraints
(optional)
Source Destination
Tributary Card
Tributary Card
Trunk Card
Trunk Card
Trunk Card
Trunk Card
Endpoint Intermediate Endpoint
node node node
Figure 3-1 End-to-End Services Creation Model
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.
Source Destination Source Destination Source Destination

Tributary Card
Tributary Card
Trunk Card
Trunk Card
Trunk Card
Trunk Card
Endpoint Intermediate Endpoint
node node node
Figure 3-2 Hop-by-Hop Services Creation Model
If you create a transport path end-to-end through the network, you can monitor only the
end points. If you create a transport path hop-by-hop through the network, you can add
or drop traffic, monitor performance, and alarms at each hop.

Service Creation Process
Service Configuring services on a node or through a network is a process of provisioning

Creation attributes of the service in four screens then activating the service.
Process 1. Add the Service. On
the Service tab, click Add.
2. Configure General
Information. Select the
service type from the
drop-down menu and
configure the general
information parameters.
Click Next to go to the next
screen.
3. Configure the Service

Characteristics. Set
service characteristics for
this service. The primary
requirement is to select the
source (where the service
originates) and the
destination (where the
service terminates).
Click Next to go to the next
screen.

Service Creation Process
4. Configure the
Attributes of the
Transport Path. Set the
attributes of the transport
path for the service in the
transport screen. On this
screen, the primary
requirement is to set the
protection attributes. Click
Next to go to the next
screen.
5. Set the Constraints. If

the value in the Setup Type
parameter on the General
Information screen for the
service is Strict, explicitly
select the service route
between defined endpoints.
Click Finish to add the
provisioned service to the
service list.
6. Activate the Service.

On the Service tab, click the
service to select it and click
Activate.

Before You Start Creating Services
Start Creating
Services Table 3-7 Before Provisioning Your Network Requirements
Hardware
Software

is initialized and started. Section 1—Overview, Installation and Administra-
tion.
Section 2, Chapter 1—“Starting the Graphical User
Interface,” page 2-1.


Chapter 2
Procedures Common to All Services
Introduction You provision a service by completing a series of screens on the graphical user
interface called:
■ General Information.
■ Service Level Agreement.
■ Transport.
■ Constraints.
This chapter contains procedures common to all service types.
Use the following procedures to begin service creation:
■ Add a Service, page 3-12.
■ Configure General Information, page 3-13.
To explicitly define the route for end-to-end services, see
■ Set Constraints for a Service, page 3-15.
To activate services after you have completed provisioning:
■ Activate a Service, page 3-17.
■ Activate Multiple Services, page 3-18.

Add a Service
Add a Service The following procedure provides step-by-step procedures for beginning service
creation.
Table 3-8 Add a Service
Step Procedure
1 From Map View click the Service tab to display the Service List screen.
Step 2
Figure 3-3 Map View—Service Tab
2 Click Add to start service creation and display the Define Service–General
Information screen.
3 The Add a Service procedure is complete.
Continue to the next procedure: Configure General Information.

Chapter 2 Procedures Common to All Services
Configure General Information
Configure The following procedure provides step-by-step instructions for completing the Define
General Service -General Information screen.
Information
Table 3-9 Configure General Information
Step Procedure
1 Complete the Add a Service, page 3-12.

2 Set the general information of the service in the Define Service - General
Information screen (Steps 3 to 7).
Figure 3-4 Define Service—General Info Screen
By default, the last service type you provisioned displays.

3 In the Name field, type a name for the service.
Use alpha-numeric characters only. Do not use punctuation or special
characters in the Name field.
4 In the Description field, type a description for the service.
This is an optional field. Use alpha-numeric characters only. Do not use
punctuation or special characters in the Description field.
5 From the Service Type list, select a type of service. See Chapter
1—“Service Provisioning Concepts,” Traverse Service Types, page 3-5
for a detailed list of Traverse service types.

Configure General Information
Table 3-9 Configure General Information (continued)
Step Procedure
6 If this is an end-to-end service, select how you are going to configure the
service this service:
From the Setup Type list, select
■ Strict (default): Explicitly define the service route through all nodes,
using the Constraints screen.
■ Loose: Allow the Control Plane to determine the optimum service
route through additional nodes.
7 Resource Advisory: System displays only available resources in the
Service Level Agreement screen, Source and Destination fields. Ports and
other resources assigned to activated services do not appear.
■ On: Display only ports or paths that have not been allocated to
activated services while provisioning this service.
■ Off: Display all ports or paths during provisioning of this service.
8 Click Next> to display the Service Level Agreement screen.
9 The Configure General Information procedure is complete.
Continue to the service provisioning procedure chapter for the service
type:
■ Chapter 3—“Creating DS1 Services,” page 3-19.
■ Chapter 4—“Creating DS3 Services,” page 3-35.
■ Chapter 5—“Creating SONET Services,” page 3-53.
■ Section 4—Creating Ethernet Services.

Set Constraints for a Service
Set The Constraints screen is only valid for these service types provisioned end-to-end
Constraints for with a Setup Type=Strict in the General Information screen.
a Service
Table 3-10 Set Constraints for a Service
Step Procedure
1 Complete one of the following procedures to configure this service:

■ Create an DS3-CC Service, page 39.
■ Create a SONET-STS Service, page 58.
2 On the Constraints screen, complete Steps 3 to 8.
Figure 3-5 Define Service—Constraints Screen
3 On the first row of the Constraints screen, verify that ingress Node,
Ingress Port, Ingress Ring ID (if this service is part of a BLSR or UPSR),
and Ingress Path are the originating points to this service.
4 In the Node column, click the blank row and select an intermediate Node
name.
5 Select the Ingress Port, Ingress Ring ID (if this service is part of a BLSR
or UPSR), Ingress Path, Egress Port, Egress Ring ID, and Egress Path
for the intermediate node.
6 Repeat Steps 3, 4, and 5 for each hop in the network.
7 On the last row, verify that the Egress Port, Egress Ring ID (if this
service is part of a BLSR or UPSR), and Egress Path are the terminating
points for this service.

Set Constraints for a Service
Table 3-10 Set Constraints for a Service (continued)
Step Procedure
8 Click Finish to provision this service and return to the service list on the
Service tab.
9 The Set Constraints for a Service procedure is complete.
Return to the originating procedure.

Activate a Service
Activate a Use this procedure activate a single service.

Service
Table 3-11 Activate a Service
Step Procedure
1 Complete the procedure: Configure General Information, page 13

including the resulting procedures based on the service type.
2 On the Service tab, complete Steps 3 and 4.
Step 3
Step 4
Figure 3-6 Service Tab—Activate
3 Click the Service from the list to activate the command buttons.
4 Click Activate to activate the service.
5 The Activate a Service procedure is complete.

Activate Multiple Services
Activate Use this procedure activate multiple services at once.

Multiple
Services Table 3-12 Activate Multiple Service
Step Procedure
1 Complete the procedure: Configure General Information, page 13

including the resulting procedures based on the service type.
2 On the Service tab, complete Steps 3 and 4.
Step 3
Step 4
Figure 3-7 Service Tab—Activate
3 Hold the Ctrl key and click individual services. OR

Hold the Shift key and click a range of services.
4 Click Activate to activate the services.
5 The Activate a Service procedure is complete.

Chapter 3
Introduction This chapter explains how to create the following service types on a Traverse system:
■ DS1. Use this service to switch individual DS1 channels through the network.
■ DS1-Mux. Use this service to multiplex all 28 ports on a DS1 card onto a transport
path.
■ Example of DS1 Services, page 3-20.
■ Modules Required to Create DS1 Services, page 3-21.
■ Before You Create DS1 Services, page 3-21.
■ Sources and Destinations for DS1 Services, page 3-22.
■ Create a DS1 Service, page 3-23.
■ Create a DS1-Mux Service, page 3-28.

Example of DS1 Services
Example of Use a combination of service types to create and transport DS1 services in a Traverse
DS1 Services network:
■ DS1-Mux. This service aggregates 28 DS-1 tributaries and adapts each channel to
a VT-mapped STS for transport over the SONET network.
■ SONET-STS. This service connects the VT-mapped STS from Node 1 to
Node 3.
■ DS1. This service provides digital cross-connect (DCS) to switch the VT-mapped
STS (aggregated DS-1 channels) to dedicated lease lines.
DS1 Service:
DS1-Mux-VT Service:
Switch VT-structured STS-1
Map 28-port DS1
to DS1 Ports
to VT-structured STS-1
(via required VT Switch module)
for Integrated Transport
SONET-STS
OC48 Link OC48 Link

(STS Path) (STS Path)
1
1 1
2
2 2
(x12)
(x24)
(x12)
27 27 27
28 VT 28 28
DS1 OC48 OC48 OC48 Switch
OC48 DS1 DS1
Node 1 Node 2 Node 3
28-port DS1 Tributaries 28-port DS1 Tributaries
Customer's Main Office

Customer's Branch Office
Customer's
Customer's Branch
Branch OfficeOffices
(x24)

Figure 3-8 DS1 Lease Line Service

Chapter 3 Creating DS1 Services
Before You Create DS1 Services
Modules This table lists the Traverse modules required to create DS1 services.
Required to
Create DS1 Table 3-13 Modules Required to Create DS1 Services
Services
Service Type Source Card Destination Card
DS1 DS1 DS1

DS3TMX DS3TMX
OC-48 VCX
DS1-Mux DS1 DS1

DS3TMX
OC-N
OC-N
Before You Review the information in this topic before you create DS1 services.
Create DS1
Services Table 3-14 DS1 Service Requirements
Hardware
You need a combination of the modules to create Volume 1, General Information,

DS1 services. See Modules Required to Create Section 2—Hardware Descriptions.
DS1 Services, page 3-21 for a breakdown of
required modules for specific services.
Software

Protection groups are configured. Volume 3, Provisioning, Section 2—Creating

Configure parameters only on working modules if Protection Groups.
a module is configured as part of a protection
group. Parameters on a protecting module are
automatically set to the same values as the
working module.
DS1 mapping formats are correct. Volume 3, Provisioning, Section 1, Chapter 3,”
Change DS1 Mapping Formats, page 1-19.
Source (tributary) and destination (transport) Volume 3, Provisioning, Section 1, Chapter

interfaces are configured correctly. 4—“Port Configuration,” page 1-23.
These procedures describe the steps to create a Volume 5, TransNav Management System,
specific service and change only configurable Section 5, Chapter 2—“DS1 Services,” page 5-11.
parameters. See Volume 5, TransNav
fields on the screen.

Sources and Destinations for DS1 Services
Table 3-14 DS1 Service Requirements (continued)
Provisioning model. Volume 3, Provisioning, Section 3, Chapter 1,”

■ DS1: hop-by-hop only. Service Creation Models, page 3-7.
■ DS1-Mux: hop-by-hop only.
Bandwidth requirements. Volume 3, Provisioning, Section 3, Chapter 1,”

■ DS1: 1.544 Mbps. Transport Capacity, page 3-3.
■ DS1-Mux: 43.322 Mbps or one STS-1.
Sources and The following table lists service types and valid source and destination port types and
Destinations mapping information for creating DS1 services. For each service type, any one source
for DS1 can connect to any one destination. Your network may require creating multiple
Services services at multiple nodes.
Table 3-15 Sources, and Destinations for DS1 Services
Sources Destinations
Service Type
Port Type or
Port Type Mapping Mapping
Service Type
DS1 DS1 n/a DS1 n/a

DS3TMX SubPort# DS3TMX SubPort
EC1 STS-1/VTG-VT
OC-N STS/VTG-VT
DS1-Mux all ports DS1MUX n/a all ports DS1MUX n/a

DS3TMX n/a
OC-N STS

Create a DS1 Service
Create a DS1 Use this procedure to create a DS1 service.

Service
Table 3-16 Create a DS1 Service
Step Procedure
1 Review the information in Before You Create DS1 Services, page 3-21
before you start this procedure.
2 Complete the procedure: Configure General Information, page 3-13 for
this service.
Figure 3-9 DS1 Service Type
3 Click Next to continue to the DS1 service level agreement screen.

Table 3-16 Create a DS1 Service (continued)
Step Procedure
4 On the Define DS1 Service - Service Level Agreement screen, enter the
port originating the service and terminating the service on the node.
Figure 3-10 DS1 Service Level Agreement Screen
5 Enter the source information. See Sources and Destinations for DS1
Services, page 3-22 for a list of valid sources for a DS1 service.
■ From the Source Node list, select the node where this service
originates.
■ From the Source Port list, select the port where this service
originates. If the source of this service is in an equipment protection
group, select the source on the working module.
■ If the Source Port is a DS3TMX port, select the subport from the
Source Starting Sts list.
6 Enter the destination information. See Sources and Destinations for DS1
Services, page 3-22 for a list of valid sources for a DS1 service.
■ From the Destination Node list, select the same node as you selected
in Step 5.
■ From the Destination Port list, select the destination port. If the
destination of this service is in a protection group, select the
destination on the working module or port.
■ From the Destination Path list, select a destination path if the
Destination Port is an optical port.
■ From the Dest. PM Template list, select a performance monitoring
template to monitor performance on the path.

Step Procedure
7 Click Next to continue to the DS1 service transport screen.

8 On the Define DS1 Service - Transport screen, set the characteristics for
the transport of this service.
Figure 3-11 DS1 Service Transport Screen
9 Set the characteristics of the transport path:

Directionality: Select one of the following:
■ Uni-Directional: The traffic can only travel in one direction (from
source to destination).
■ Bi-Directional (default): Traffic travels in both directions. Within a
UPSR ring, a path may take one link for forward traffic and another
link for backward traffic. For topologies other than UPSR, the forward
traffic and backward traffic travel across exactly the same links.
Redline Circuit. Use this parameter to prevent the accidental deactivation
of this service. Select one of the following:
■ Yes: Service is a redline circuit and cannot be deactivated.
■ No (default): Service is not a redline circuit and can be deactivated.

Step Procedure
10 Set the quality attributes of the transport path.

Protection Type. Indicates the protection type to use to protect the service.
■ BLSR Protected. If the service is protected on a BLSR.
■ Unprotected/Default Protection (default). If the service is unprotected.
■ UPSR Protected. If the service is protected on a UPSR.
■ 1+1 Path Protected. Not available for DS1 services.
Max SD-BER-V: Measures the transmission quality (bit error ratio) of
degraded signals in the VT path. When the error rate crosses the value
specified in this parameter, the system raises a signal degraded bit error
rate (BERSD-V) alarm. Select one of the following values:
Max SF-BER-V: Measures the transmission quality (bit error ratio) of
failed signals in the VT path. When the error rate crosses the value
specified in this parameter, the system raises a signal failed bit error rate
(BERSF-V) alarm. Select one of the following values:
11 If MSSPRING/BLSR Protected is selected in Step 10, select the protection
attributes for the following fields:
■ 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.
12 If SNCP/UPSR Protected is selected in Step 10, select the protection
■ Revertive (default=notselected): Select the check box to switch traffic
back to the original port or path once the failure condition no longer
exists.
■ WTR (Wait To Restore) Time (default=5): Configurable only if the
check box for Revertive is selected. Specifies the amount of time (in
minutes) for the system to wait before restoring traffic to the original
port or path once the failure condition no longer exists. Specify a value
between 1 and 60 minutes.

Step Procedure
13 Click Next to continue to the DS1 service constraints screen.

14 Because you can only provision a DS1 service between two modules on
the same node only, you cannot set the constraints of the service through
the network
Figure 3-12 DS1 Service Constraints Screen
However, you can verify the service you have just provisioned:
■ Verify that the ingress node, port and starting path are the originating
■ Verify that the egress node, port and starting path are the terminating
■ If this service is provisioned on a protection ring, verify the ring ID of
the ingress and egress endpoints.
Service tab.
16 The Create a DS1 Service procedure is complete.
Continue to the procedure to activate the service. See Activate a Service,
page 3-17.

Create a DS1-Mux Service
Create a Use this procedure to create an DS1-Mux service.

DS1-Mux
Service Table 3-17 Create a DS1-Mux Service
Step Procedure
this service
Figure 3-13 DS1-Mux Service Type
3 Click Next to continue to the DS1-Mux service level agreement screen.

Table 3-17 Create a DS1-Mux Service (continued)
Step Procedure
4 On the Define DS1-Mux Service - Service Level Agreement screen,

enter the characteristics of the service for the service.
Figure 3-14 DS1-Mux Service Level Agreement Screen
Services, page 3-22 for a list of valid sources for a DS1-Mux service.
originates.
■ From the Source Port list, click the module where this service
originates. This field reads: all ports DS1MUX.
If the source of this service is in an equipment protection group, select
the source on the working module.
■ If the Source Port is a DS3TMX port, select the subport from the
Source Starting Sts list.

Step Procedure
Services, page 3-22 for a list of valid sources for a DS1-Mux service.
in Step 5.
■ From the Destination Path list, select a destination path if the
Destination Port is an optical port.
7 Click Next to continue to the DS1-Mux service transport screen.
8 On the Define DS1-Mux Service - Transport screen, set the
characteristics for the transport of this service.
Figure 3-15 DS1-Mux Service Transport Screen

Step Procedure

No (default): Service is not a redline circuit and can be deactivated.
10 Set the path overhead attributes in the forward direction.
Fwd Signal Label: The path signal label (C2 byte in the STS path
overhead) in the forward direction of the LSP. Select one of the following:
■ Unequipped (00)
■ Eqp-Nonspecific (01) (default): Equipped, non-specific payload.
■ TUG-Structured(02): TUG-structured STS SPE.
■ Locked TUG(03): Locked mode.
■ E3 or DS3 Async(04): asynchronous mapping for DS3.
■ E4 or DS4NA Async(12): asynchronous mapping for DS4NA.
■ ATM Map(13): mapping for ATM.
■ DQDB Map(14): mapping for DQDB.
■ FDDI Async(15): asynchronous mapping for FDDI.
■ HDLC-SONET(16): HDLC-Over-SONET mapping.
■ POS Scramble (18).
■ POS No-Scramble (CF).
Fwd Path Format: This port transmits a path trace identifier in the J1 byte
of the SONET frame so that the path receiver can verify its continued
connection.
■ 16 byte (default).
■ 64 byte.
Fwd Path Trace: Enter the path trace value (J1 byte in the STS path
overhead) in the forward direction of the LSP.

Step Procedure
11 If Directionality is Bi-Directional, set the path overhead attributes in the

backward direction.
Rev Signal Label: The path signal label (C2 byte in the STS path
overhead) in the reverse direction of the LSP. Select one of the following:
■ Unequipped (00)
Rev Path Format: This port receives a path trace identifier in the J1 byte
of the SONET frame so that the path transmitter can verify its continued
connection.
■ 64 byte.
Rev Path Trace: Enter the path trace value (J1 byte in the STS path
overhead) in the reverse direction of the LSP.
■ BLSR Protected. If the service is protected on a BLSR. Go to Step 13.
■ Unprotected/Default Protection (default). If the service is unprotected
or is protected by facility or equipment protection.
■ UPSR Protected. If the service is protected on a UPSR. Go to Step 14.
■ 1+1 Path Protected. Not available for DS1-Mux services.

Step Procedure

exists.
15 Click Next to continue to the DS1-Mux service constraints screen.
16 Because you can only provision a DS1-Mux service between two modules
on the same node only, you cannot set the constraints of the service
Figure 3-16 DS1-Mux Service Constraints Screen

Step Procedure
Service tab.
18 The Create a DS1-Mux Service procedure is complete.
page 3-17.

Chapter 4
Introduction This chapter explains how to create the following service types on a Traverse system:
■ DS3-CC. Use this service to transport clear channel DS3 signals.
■ DS3-Tmx. Use this service to convert a channelized DS3 into a VT-mapped STS
for transport across the network.
■ Example of DS3 Services, page 3-36.
■ Modules Required to Create DS3 Services, page 3-37.
■ Before You Create DS3 Services, page 3-37.
■ Sources and Destinations for DS3 Services, page 3-38.
■ Create a DS3-CC Service, page 3-39.
■ Create a DS3-TMX Service, page 3-46.

Example of DS3 Services
Example of Use a combination of service types to create and transport DS3 traffic in a Traverse
DS3 Services network. Depending on the network requirements and configurations, the Traverse can
transport DS3 signals or channelized DS3 signals.
The following example uses a combination of service types to move traffic:
■ DS3-Tmx. This service adapts channelized DS3 traffic into a VT-mapped STS for
transport over a SONET network to a far end TransAccess 100 Mux.
■ SONET-STS. This service cross-connects the VT-mapped STS from Node 1 to
Node 3.
■ SONET-VT 1.5. This service connects a VT (channelized DS3 from Node 1) to an
EC1 port that has a TransAccess 100 Mux connected.
■ DS3-CC. This service connects a clear channel DS3 to a digital cross-connect
system for switching into the network.
SONET-STS End-to-End (STS-3c)
OC48 Link SONET-STS OC48 Link
DS3-Tmx
DS3-CC
SONET-VT 1.5
VT
OC3 TMX OC48 OC48 DS3 OC48 OC48 Switch TMX OC12
Slot 4 Slot 8 Slot 14 Slot 2 Slot 8 Slot 14 Slot 2 Slot 3 Slot 6 Slot 8
Service Type: DS3-Tmx (HOP 1) Service Type: SONET-STS (HOP 2) Service Type: SONET-VT 1.5 (HOP3)
Src: Node 1- slot 8-port 6-DS3TMX Src: Node 2- slot 2-port 1-OC48-STS 3 Src: slot 2-port 1-OC48-STS 3-VTG1-VT1
Dest: Node 1-slot 14-port 1-OC48-STS 3 Dest: Node 2-slot 14-port 1-OC48-STS 3 Dest: slot 6-port 5-EC1-STS 1-VTG5-VT2
M13 TA100
Service Type: DS3-CC
Src: Node 1- slot 8-port 9-DS3CC
Dest: Node 2-slot 8-port 9-DS3CC
M13
Service Type: SONET-STS
Setup Type: Loose
Src: Node 1- slot 4-port 1-OC3-STS 1
Dest: Node 3-slot 8-port 1-OC12-STS 1
ATM MUX
Figure 3-17 Channelized DS3 and DS3 Services

Before You Create DS3 Services
Modules This table lists the Traverse modules required to create DS3 services.
Required to
Create DS3 Table 3-18 Modules Required for DS3 Services
Services
DS3-CC DS3 clear channel DS3 clear channel

DS3TMX DS3TMX
OC-N
DS3-Tmx DS3TMX DS3TMX

OC-N
Before You Review the information in this topic before you create DS3 services.
Create DS3
Services Table 3-19 DS3 Service Requirements
Hardware

DS3 services. See Modules Required to Create Section 2—Hardware Descriptions.
DS3 Services, page 3-37 for a breakdown of
required modules for specific services.
Software


Configure parameters only on working modules if Protection Groups.
a module is configured as part of a protection
group. Parameters on a protecting module are
automatically set to the same values as the
working module.

These procedures describe how to create a Volume 5, TransNav Management System,

specific service and change only configurable Section 5, Chapter 3—“DS3 Services,”
parameters. See Volume 5, TransNav page 5-19.
fields on screen.

Sources and Destinations for DS3 Services
Table 3-19 DS3 Service Requirements (continued)

■ DS3-CC: end-to-end or hop-by-hop Service Creation Models, page 3-7.
■ DS3-TMX: Hop-by-hop.

■ DS3-CC. 44.736 Mbps. Transport Capacity, page 3-3.
■ DS3-TMX. 44.736 Mbps
Destinations mapping information for creating DS3 services. For each service type, any one source
for DS3 can connect to any one destination. Your network may require creating multiple
Services services at multiple nodes.
Service
Type Port Type or
Service Type
DS3-CC DS3CC n/a DS3CC n/a

EC1 n/a
OC-N STS
DS3-TMX DS3TMX n/a all ports n/a

DS1MUX n/a
DS3TMX STS
OC-N

Create a DS3-CC Service
Create a Use this procedure to create an DS3-CC service.

DS3-CC
Service Table 3-21 Create an DS3-CC Service
Step Procedure
1 Review the information in Modules Required to Create DS3 Services,

this service
Figure 3-18 DS3-CC Service Type
From the Service Type list, select DS3-CC.

From the Setup Type list, select one of the following:
■ Strict (default): Explicitly define the service route through all nodes,
using the Constraints screen.
■ Loose: Allow the Control Plane to determine the optimum service
route through additional nodes.
3 Click Next to continue to the DS3-CC service level agreement screen.

Table 3-21 Create an DS3-CC Service (continued)
Step Procedure
4 On the Define DS3-CC Service - Service Level Agreement screen, enter

the characteristics of the service.
Figure 3-19 DS3-CC Service Level Agreement Screen
Services, page 3-38 for a list of valid sources for a DS3-CC service.
originates.
Services, page 3-38 for a list of valid sources for a DS3-CC service.
■ From the Destination Node list, select a node.
For end-to-end services, select another node in the domain.
For hop-by-hop services, select the same node as you selected in
Step 5.
■ If the Destination Port is an optical port, from the Destination Path
list, select a path.
■ If the Destination Port is an optical port, from the Dest. PM
Template list, select a performance monitoring template to monitor
performance on the path.

Step Procedure
7 If the destination node in Step 6 is different than the source node, default
values are displayed for the following fields:
■ Setup Retry Count (default=3). The number of times the system tries
to activate a service before declaring a service activation failure. Other
selections are in increments of 3; range is 3–30.
■ Failure Retry Count (default=3). The number of times the system
tries to reestablish a service before declaring a service retry failure.
Other selections are in increments of 3; range is 3–30.
8 Click Next to continue to the DS3-CC service transport screen.
9 On the Define DS3-CC Service - Transport screen, set the characteristics
for the transport of this service
Figure 3-20 DS3-CC Service Transport Screen

Step Procedure

■ Unequipped (00)
of the SDH frame so that the path receiver can verify its continued
connection.
■ 64 byte.

Step Procedure

backward direction.
■ Unequipped (00)
of the SDH frame so that the path transmitter can verify its continued
connection.
■ 64 byte.
■ MSSPRING/BLSR Protected. If the service is protected on an MS-SP
ring.
■ SNCP/UPSR Protected. If the service is protected on an SNCP ring.
■ 1+1 Path Protected. If this service is protected by another path in the
network.

Step Procedure
15 If UPSR Protected or 1+1 Path Protected is selected in Step 13, select the
protection attributes for the following fields:
exists.
16 Click Next to continue to the DS3-CC service constraints screen.
17 This screen appears regardless of the Setup Type you selected on the
General Information screen.
Figure 3-21 DS3-CC Service Constraints Screen
To explicitly set the route of the service through the network (Setup
Type=Strict), complete the procedure: Set Constraints for a Service,
page 3-15.
If Setup Type=Loose, go to Step 18.

Step Procedure
Service tab.
19 The Create an DS3-CC Service procedure is complete.
page 3-17.

Create a DS3-TMX Service
Create a Use this procedure to create an DS3-TMX service.

DS3-TMX
Service Table 3-22 Create an DS3-TMX Service
Step Procedure
this service.
Figure 3-22 DS3-TMX Service Type
3 Click Next to continue to the DS3-TMX service level agreement screen.

Table 3-22 Create an DS3-TMX Service (continued)
Step Procedure
4 On the Define DS3-TMX Service - Service Level Agreement screen,

enter the characteristics of the service.
Figure 3-23 DS3-TMX Service Level Agreement Screen
Services, page 3-38 for a list of valid sources for a DS3-TMX service.
originates.
Services, page 3-38 for a list of valid sources for a DS3-TMX service.
Step 5.
■ If the Destination Port is an optical port, from the Destination Path
list, select a path.
■ If the Destination Port is an optical port, from the Dest. PM
Template list, select a performance monitoring template to monitor
performance on the path.

Step Procedure
7 If the destination node in Step 6 is different than the source node, default
values are displayed for the following fields:
■ Setup Retry Count (default=3). The number of times the system tries
to activate a service before declaring a service activation failure. Other
selections are in increments of 3; range is 3–30.
■ Failure Retry Count (default=3). The number of times the system
tries to reestablish a service before declaring a service retry failure.
Other selections are in increments of 3; range is 3–30.
8 Click Next to continue to the DS3-TMX service transport screen.
9 On the Define DS3-TMX Service - Transport screen, set the
characteristics for the transport of this service.
Figure 3-24 DS3-TMX Service Transport Screen

Step Procedure

■ Unequipped(000).
■ Eqp-Nonspecific(001) (default): Equipped - Nonspecific Payload.
■ Async(010): asynchronous mapping for E3 or DS3.
■ Bit-Sync (011)
■ Byte-Sync (100)
■ Extended (101)
■ Test (110)
■ VC AIS (111): virtual container alarm indication signal mapping.
connection.
■ 64 byte.

Step Procedure

backward direction.
■ Unequipped(000).
■ Async(010): asynchronous mapping for E3 or DS3.
■ Bit-Sync (011)
■ Byte-Sync (100)
■ Extended (101)
■ Test (110)
■ VC AIS (111): virtual container alarm indication signal mapping.
■ Test Signal (FE): O.181 Test Signal (TSS1 to TSS3) mapping.
connection.
■ 64 byte.
ring.
■ 1+1 Path Protected. Not available for DS3-TMX services.

Step Procedure

15 If SNCP/UPSR Protected or 1+1 Path Protected is selected in Step 13,
select the protection attributes for the following fields:
exists.
16 Click Next to continue to the DS3-TMX service constraints screen.
Figure 3-25 DS3-TMX Service Constraints Screen

Step Procedure
Service tab.
19 The Create an DS3-TMX Service procedure is complete.
page 3-17.

Chapter 5
Creating SONET Services
Introduction This chapter explains how to create the following service types in a Traverse network:
■ SONET-STS. Use this service to transport synchronous or Ethernet traffic through
the network.
■ SONET-VT1.5. Use this service to switch individual SONET VT1.5 payloads
■ Examples of SONET Services, page 3-54.
■ Modules Required to Create SONET Services, page 3-55.
■ Before You Create SONET Services, page 3-55.
■ Source and Destinations for SONET Services, page 3-56.
■ Starting STS Numbers for SONET Services, page 3-57.
■ Create a SONET-STS Service, page 3-58.
■ Create a SONET-VT1.5 Service, page 3-66.

Examples of SONET Services
Examples of Use a combination of service types to create end-to-end SONET services or switch
SONET individual VT1.5 payloads in a Traverse network.
Services ■ DS3-Tmx. This service adapts channelized DS3 traffic into a VT-mapped STS for
transport over a SONET network to a far end TransAccess 100 Mux.
■ SONET-STS. This service cross-connects the VT-mapped STS from Node 1 to
Node 3.
■ SONET-VT 1.5. This service connects a VT (channelized DS3 from Node 1) to an
EC1 port that has a TransAccess 100 Mux connected.
■ DS3-CC. This service connects a clear channel DS3 to a digital cross-connect
system for switching into the network.
■ SONET-STS. This service transports ATM traffic (STS-3c) from an ATM
multiplexer to an ATM switch on the far end.
SONET-STS End-to-End (STS-3c)
OC48 Link SONET-STS OC48 Link
DS3-Tmx
DS3-CC
SONET-VT 1.5
VT
OC3 TMX OC48 OC48 DS3 OC48 OC48 Switch TMX OC12
Service Type: DS3-Tmx (HOP 1) Service Type: SONET-STS (HOP 2) Service Type: SONET-VT 1.5 (HOP3)
Src: Node 1- slot 8-port 6-DS3TMX Src: Node 2- slot 2-port 1-OC48-STS 3 Src: slot 2-port 1-OC48-STS 3-VTG1-VT1
Dest: Node 1-slot 14-port 1-OC48-STS 3 Dest: Node 2-slot 14-port 1-OC48-STS 3 Dest: slot 6-port 5-EC1-STS 1-VTG5-VT2
M13 TA100
Service Type: DS3-CC
Src: Node 1- slot 8-port 9-DS3CC
Dest: Node 2-slot 8-port 9-DS3CC
M13
Setup Type: Loose
Src: Node 1- slot 4-port 1-OC3-STS 1
Dest: Node 3-slot 8-port 1-OC12-STS 1
ATM MUX
Figure 3-26 SONET-STS and SONET-VT Services

Chapter 5 Creating SONET Services
Before You Create SONET Services
Other SONET Use the procedures in the following chapters to configure other SONET services or
Services and applications:
Applications ■ Section 4, Chapter 2—“Creating Ethernet Transport Paths,” page 4-11.
■ Section 5, Chapter 1—“Creating 1+1 Path-Protected Services,” page 5-1.
■ Section 5, Chapter 2—“Creating Drop-and-Continue Services Procedures,”
page 5-11.
■ Section 5, Chapter 3—“Creating Optical Transmux Services,” page 5-23.
■ Section 5, Chapter 4—“Creating Services on Overlapping UPSRs,” page 5-33.
■ Section 5, Chapter 5—“Creating Transparent Services Procedures,” page 5-45.
Modules This table lists the Traverse modules required to create SONET services.
Required to
Create SONET Table 3-23 Modules Required for SONET Services
Services
SONET-STS OC-N STM-N

OC-N
SONET-VT1.51 OC-N STM-N

OC-N
1
There must be a VT Switch module in the same node to create SONET-VT1.5 services.
Before You Review the information in this topic before you create any SONET services.
Create SONET
Services Table 3-24 SONET Service Requirements
Hardware

SONET services. See Modules Required to Section 2—Hardware Descriptions.
Create SONET Services, page 3-55 for a
breakdown of required modules for specific
services.
Software


Configure parameters only on the working port if Protection Groups.
the port is part of a protection group. Parameters
on a protecting port are automatically set to the
same values as the working port.

Source and Destinations for SONET Services
Table 3-24 SONET Service Requirements (continued)
Source (tributary) and destination (transport) Volume 3, Provisioning, Section 1, Chapter 4—“Port
interfaces are configured correctly. Configuration,” page 1-23.

specific service and change only configurable Section 5, Chapter 4—“SONET Services,”
fields on screen.
Interworking. Support for ETSI to ANSI Volume 3, Provisioning, Section 3, Chapter 5,”
interworking: Modules Required to Create SONET Services,
■ SDH to SONET. page 3-55.
■ SONET to SDH.

■ SONET-STS: end-to-end OR hop-by-hop. Service Creation Models, page 3-7.
■ SONET-VT1.5: hop-by-hop only.

■ STS-1: 48.960 Mbps. Transport Capacity, page 3-3.
■ STS-3c: 150.336 Mbps.
■ STS-12c: 599.040 Mbps.
■ STS-48c: 2, 396.160 Mbps.
■ SONET VT: 1.728 Mbps.
Source and The following table lists service types and valid source and destination port types and
Destinations mapping information for creating SONET services. For each service type, any one
for SONET source can connect to any one destination. Your network may require creating multiple
services at multiple nodes.
Services
Table 3-25 Sources, and Destinations for SONET Services
Service Type
Port Type or
Service Type
SONET-STS1 EC1 n/a EC1 n/a

OC-N STS OC-N STS
SONET-VT1.52 EC1 STS-1/ VTG-VT DS1 (test access) n/a

OC-N STS/ VTG-VT EC1 STS-1/ VTG-VT
OC-N STS/ VTG-VT
1
Supports multicast connections for drop-and-continue applications. Also supports Ethernet over SONET
(EOS) transport.
2

Starting STS Numbers for SONET Services
Starting STS The starting STS number for any SONET service depends on the required bandwidth.
Numbers for For example, an OC-48 interface has a Src. Starting STS range of 1–48 if you select
SONET STS-1 in the Bandwidth parameter. If you select STS- 12c in the Bandwidth
Services 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 3-26 Valid Starting STS
Starting STS
Bandwidth
OC-3 OC-12 OC-48 OC-192
STS-1 1, 2, 3 1, 2, 3, 4,..., 12 1, 2, 3, 4,..., 48 1, 2, 3, 4,..., 192

STS-3c 1 1, 4, 7, 10 1, 4, 7, 10, 16, 1, 4, 7, 10, 16,
19,... 48 19,... 190
STS-12c — 1 1, 13, 25, 37 1, 13, 25, 37,
49,..., 181
STS-48c — — 1 1, 49, 97, 145
For SONET service between OC192 ports, the Src. Starting Sts and the Dest. Starting
Sts must in the same range when the range is between 1 and 48 or 49 and 192. For
example, the if Src. Starting Sts 12, the Dest. Starting Sts must be between STS
number 1 and 48. If the Src. Starting Sts is 105, the Dest. Starting Sts must be
between STS number 49 and 192.

Create a SONET-STS Service
Create a Review the information in Before You Create SONET Services, page 3-55 before you
SONET-STS start this procedure.
Service
Table 3-27 Create a SONET-STS Service
Step Procedure

this service.
Figure 3-27 SONET-STS Service Type
2 Click Next to continue to the SONET-STS service level agreement screen.

Table 3-27 Create a SONET-STS Service (continued)
Step Procedure
3 On the Define SONET-STS Service - Service Level Agreement screen,

enter the characteristics of the service (Steps 4 to 7).
Figure 3-28 SONET-STS Service Level Agreement Screen
4 From the Bandwidth parameter, select the total bandwidth for the service:
■ STS-1 (default).
■ STS-3c.
5 Enter the source information. See Source and Destinations for SONET
Services, page 3-56 for a list of valid sources for a SONET-STS service.
originates.
originates. If the source of this service is in a protection group, select
the source that is considered the working port.
■ From the Source Path list, select the starting STS number where this
service originates. See Starting STS Numbers for SONET Services,
page 3-57 for a complete list.
■ From the Src. PM Template list, select a performance monitoring

Step Procedure
6 Enter the destination information. See Source and Destinations for

SONET Services, page 3-56 for a list of valid sources for a SONET-STS
service.
Step 5.
destination that is considered the working port.
■ From the Destination Path list, select the starting AUG1 number and
the VC-3 path where this service originates. See Starting STS
Numbers for SONET Services, page 3-57 for a complete list.
7 For end-to-end services, (if the destination node in Step 6 is different than
the source node in Step 5), specify the values for the following parameters:
Setup Retry Count: The number of times the system retries a service
activation request before declaring that activation failed. Select 0–30.
Default is 3.
Failure Retry Count: The number of times the system tries to reestablish
the service before declaring it failed. Select 0–30. Default is 3.
8 Click Next to continue to the SONET-STS service transport screen.

Step Procedure
9 On the Define SONET-STS Service - Transport screen, set the

characteristics for the transport of this service (Steps 10 to 15).
Figure 3-29 SONET-STS Service Transport Screen


Step Procedure

■ Unequipped(00).
■ TUG-Structured(02): TUG-structured VC-3.
■ Locked TU(03): Locked Tributary unit (TU) mode.
■ E3 or DS3 Async(04): asynchronous mapping for E3 or DS3.
(Planned for future release.)
■ E4 or DS4NA Async(12): asynchronous mapping for DS4NA or
E4.(Planned for future release.)
■ HDLC-PPP(16): HDLC-Over-SONET mapping.
■ X.86(18).
■ GFP (1B).
connection.
■ 64 byte.

Step Procedure
12 If Directionality is Bi-Directional (Step 10), set the path overhead

attributes in the backward direction.
■ Unequipped(00).
■ X.86(18).
■ GFP (1B).
connection.
■ 64 byte.
ring.
■ 1+1 Path Protected. If this service is protected by another path in the
network.

Step Procedure

15 If SNCP/UPSR Protected or 1+1 Path Protected is selected in Step 13,
select the protection attributes for the following fields:
exists.
16 Click Next to continue to the SONET-STS service constraints screen.

Step Procedure
Figure 3-30 SONET-STS Service Constraints Screen
To explicitly set the route of the service through the network (Setup
Type=Strict), complete the procedure: Set Constraints for a Service,
page 3-15.
If Setup Type=Loose, go to Step 18.
Service tab.
19 The Create a SONET-STS Service procedure is complete.
page 3-17.

Create a SONET-VT1.5 Service
Create a Review the information in Before You Create SONET Services, page 3-55 before you
SONET-VT1.5 start this procedure.
Service
Table 3-28 Create a SONET-VT1.5 Service
Step Procedure

this service.
Figure 3-31 SONET-VT1.5 Service Type
2 Click Next to continue to the SONET-VT1.5 service level agreement

screen.

Table 3-28 Create a SONET-VT1.5 Service (continued)
Step Procedure
3 On the Define SONET-VT1.5 Service - Service Level Agreement

screen, enter the characteristics of the service (Steps 5 and 6).
Figure 3-32 SONET-VT1.5 Service Level Agreement Screen
4 Enter the source information. See Source and Destinations for SONET
Services, page 3-56 for a list of valid sources for a SONET-VT1.5 service.
originates.
originates. If the source of this service is in a protection group, select
the source that is considered the working port.
■ From the Source Path list, select the starting STS path number where
this service originates. See Starting STS Numbers for SONET
Services, page 3-57 for a complete list.
■ From the Source VT list, select the VT group and VT number where
this service originates.

Step Procedure
5 Enter the destination information. See Source and Destinations for

SONET Services, page 3-56 for a list of valid sources for a
SONET-VT1.5 service.
in Step 4.
destination that is considered the working port.
■ From the Destination Path list, select the starting STS number where
this service terminates. See Starting STS Numbers for SONET
Services, page 3-57 for a complete list.
■ From the Destination VT list, select the VT group and VT number
where this service originates.
6 Click Next to continue to the SONET-VT1.5 service transport screen.
7 On the Define SONET-VT1.5 Service - Transport screen, set the
characteristics for the transport of this service (Steps 10 to 15).
Figure 3-33 SONET-VT1.5 Service Transport Screen

Step Procedure

■ Unequipped(00).
■ X.86(18).
connection.
■ 64 byte.

Step Procedure
10 Set the path overhead attributes in the backward direction.

connection.
■ 64 byte.
ring.
■ 1+1 Path Protected. If the service is protected by another path.
Max SD-BER-V: Maximum signal degrade bit error rate for VT path.
Measures the transmission quality (bit error ratio) of degraded signals in
the VT path. When the error rate crosses the value specified in this
parameter, the system raises a signal degraded bit error rate (BERSD-V)
alarm. Select one of the following values:
Max SF-BER-V: Measures the transmission quality (bit error ratio) of
failed signals in the VT path. When the error rate crosses the value
specified in this parameter, the system raises a signal failed bit error rate
(BERSF-V) alarm. Select one of the following values:

Step Procedure

exists.
14 Click Next to continue to the SONET-VT1.5 service constraints screen.
15 Because you can only provision a SONET-VT1.5 service between two
modules on the same node only, you cannot set the constraints of the
service through the network.
Figure 3-34 SONET-VT1.5 Service Constraints Screen

Step Procedure
Service tab.
17 The Create a SONET-VT1.5 Service procedure is complete.
Continue to the procedure Activate a Service, page 3-17 to activate the
service.

S ECTION 4 C REATING E THERNET S ERVICES
S ECTION 4CREATING ETHERNET SERVICES
Contents
Chapter 1
Ethernet Services Overview
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
Ethernet Services in a Traverse Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
Point-to-Point Dedicated (P2PD). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
Point-to-Point Shared (P2PS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
Internet Access Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Transparent LAN Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Ethernet Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Link Integrity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Virtual Concatenation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
Encapsulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
LCAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
LCAS Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
LCAS and 1+1 Path Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
LCAS Group Identifiers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
Asymmetric LCAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
LCAS Interworking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
Ethernet Transport Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6
Modules Required to Create Ethernet Services . . . . . . . . . . . . . . . . . . . . . . . 4-6
Sources and Destinations for Ethernet Services. . . . . . . . . . . . . . . . . . . . . . . 4-7
Guaranteed Data Rates and Ethernet Services . . . . . . . . . . . . . . . . . . . . . . . 4-8
Procedures Required to Create Ethernet Services . . . . . . . . . . . . . . . . . . . . . 4-9
Chapter 2
Creating Ethernet Transport Paths
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11
Modules Required to Create Transport Paths. . . . . . . . . . . . . . . . . . . . . . . . . 4-11
Before You Create Transport Paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12
Guidelines to Create Transport Paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13
Other Transport Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14
Create a Transport Path End-to-End. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14
Create a Transport Path Hop-by-Hop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15
Chapter 3
Creating VC-Bundle Services
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-17
Example of a VC-Bundle Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-18
Before You Create VC-Bundle Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-19

Volume 3 Section 4 Creating Ethernet Services
Guidelines to Provision a VC-Bundle Service . . . . . . . . . . . . . . . . . . . . . . . . . 4-20

Create a VC-Bundle Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21
Change the Encapsulation Format on a Standard Concatenated Signal . . . . 4-23
Chapter 4
Creating Point-to-Point Dedicated Services
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-25
Example of a Point-to-Point Dedicated Service. . . . . . . . . . . . . . . . . . . . . . . . 4-26
Before You Create Point-to-Point Dedicated Services . . . . . . . . . . . . . . . . . . 4-26
Guidelines to Create a Point-to-Point Dedicated Service . . . . . . . . . . . . . . . . 4-28
Create a Point-to-Point Dedicated Service . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-28
Chapter 5
Creating Point-to-Point Shared Services
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-31
Example of a Point-to-Point Shared Service . . . . . . . . . . . . . . . . . . . . . . . . . . 4-32
Before You Create Point-to-Point Shared Services. . . . . . . . . . . . . . . . . . . . . 4-33
Guidelines to Create a Point-to-Point Shared Service. . . . . . . . . . . . . . . . . . . 4-34
Create an Ethernet Point-to-Point Shared Service . . . . . . . . . . . . . . . . . . . . . 4-35
Chapter 6
Creating Ethernet IAS Services
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-37
Example of an IAS Ethernet Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-37
Before You Create an IAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-39
Guidelines to Create an IAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-40
Create an IAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-41
Chapter 7
Creating Ethernet TLS Services
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-45
Example of a TLS Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-45
Guidelines to Create TLS Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-47
Before You Create TLS Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-47
Create a Transparent LAN Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-49

List of Figures
Figure 4-1 VC-Bundle Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-18
Figure 4-2 VC-Bundle Service—Service Level Agreement . . . . . . . . . . . . . . 4-21
Figure 4-3 VC-Bundle Service—Service Level Agreement . . . . . . . . . . . . . . 4-23
Figure 4-4 Dedicated Ethernet Private Line Service . . . . . . . . . . . . . . . . . . . 4-26
Figure 4-5 Define Ethernet Service—Service Level Agreement . . . . . . . . . . 4-28
Figure 4-6 Point-to-Point Shared Services . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-32
Figure 4-8 Ethernet Internet Access Services . . . . . . . . . . . . . . . . . . . . . . . . 4-38
Figure 4-10 Transparent LAN Services over SONET Transport Paths . . . . . . 4-46
Figure 4-12 Service Level Agreement—TDM Endpoint . . . . . . . . . . . . . . . . . . 4-50
Figure 4-13 Service Level Agreement—ETH100TX or GbE Port. . . . . . . . . . . 4-50
List of Tables
Table 4-1 LCAS Interworking and System Behavior . . . . . . . . . . . . . . . . . . . 4-5
Table 4-2 Modules Required to Transport Ethernet Services . . . . . . . . . . . . 4-6
Table 4-3 Sources, and Destinations for Ethernet Services . . . . . . . . . . . . . 4-7
Table 4-4 CAC Limits for Sum of All Guar. Data Rates Sharing a Port. . . . . 4-8
Table 4-5 Modules Required to Transport Ethernet Services . . . . . . . . . . . . 4-11
Table 4-6 Ethernet Transport Paths Requirements. . . . . . . . . . . . . . . . . . . . 4-12
Table 4-7 Ethernet Cards and Total Number of Terminations . . . . . . . . . . . 4-13
Table 4-8 Create an Ethernet Transport Path End-to-End . . . . . . . . . . . . . . 4-14
Table 4-9 Create an Ethernet Transport Path Hop-by-Hop. . . . . . . . . . . . . . 4-15
Table 4-10 VC-Bundle Service Requirements . . . . . . . . . . . . . . . . . . . . . . . . 4-19
Table 4-11 Create a VC-Bundle Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21
Table 4-12 Change the Encapsulation Format . . . . . . . . . . . . . . . . . . . . . . . . 4-23
Table 4-13 Point-to-Point Dedicated Service Requirements. . . . . . . . . . . . . . 4-26
Table 4-14 Create an Ethernet Point-to-Point Dedicated Service. . . . . . . . . . 4-28
Table 4-15 Point-to-Point Shared Service Requirements . . . . . . . . . . . . . . . . 4-33
Table 4-16 Create an Ethernet Point-to-Point Shared Service . . . . . . . . . . . . 4-35
Table 4-17 IAS Service Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-39
Table 4-18 Create an IAS Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-41
Table 4-19 TLS Service Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-47
Table 4-20 Create an Ethernet Transparent LAN Service (TLS) . . . . . . . . . . 4-49


Chapter 1
Ethernet Services Overview
Introduction This chapter includes the following topics:

■ Ethernet Services in a Traverse Network, page 4-1.
■ Ethernet Features, page 4-2.
■ Ethernet Transport Features, page 4-6.
■ Modules Required to Create Ethernet Services, page 4-6.
■ Sources and Destinations for Ethernet Services, page 4-7.
■ Guaranteed Data Rates and Ethernet Services, page 4-8.
■ Procedures Required to Create Ethernet Services, page 4-9.
Ethernet You can configure the following Ethernet services on the Traverse platform.
Services in a
Traverse Point-to-Point Dedicated (P2PD)
Network A point-to-point dedicated service maps Ethernet traffic into one transport path and
transports the traffic to another Ethernet interface on the far end. There is no
aggregation at either side of the network. Alternatively, you can map the Ethernet
traffic from one port on a module to another. Use the P2PD service to offer dedicated
Ethernet private line services.
For information how to configure this service, see Chapter 4—“Creating Point-to-Point
Dedicated Services,” page 4-25.
Point-to-Point Shared (P2PS)

A point-to-point shared service maps Ethernet traffic from up to 24 Ethernet interfaces
on one Ethernet module into one transport path and transports the traffic across the
network to another Ethernet module. Use the P2PS service to offer “shared Ethernet
private line” services.
For information on how to configure this service, see Chapter 5—“Creating
Point-to-Point Shared Services,” page 4-31.

Volume 3, Section 4: Creating Ethernet Services
Ethernet Features
Internet Access Service

An Internet access service allows multiple subscribers access the hub site router for
Internet access. This service aggregates traffic in two locations: at the subscriber side
and at the hub site. On the subscriber site, the node statistically multiplexes Ethernet
traffic from multiple Ethernet ports on the same card onto a transport path. At the hub
site, the node statistically multiplexes traffic from multiple transport paths onto one
single Ethernet interface. Use the IAS service to offer shared Ethernet access to Internet
services.
For information on how to configure this service, see Chapter 6—“Creating Ethernet
IAS Services,” page 4-37.
Transparent LAN Service.

A transparent LAN service allows multiple Ethernet devices in multiple locations to
appear as a single private LAN (virtual LAN or VLAN). Each device attaches to an
Ethernet port on an individual node. Each node connects to another node in a
point-to-point or linear chain topology. Each Ethernet device can exchange data with
any other device on the LAN with the same virtual identifier (VLAN). You can
configure transparent LAN services for individual customers (separate Ethernet
devices) but share the trunk bandwidth between nodes.
For information on how to configure this service, see Chapter 7—“Creating Ethernet
TLS Services,” page 4-45.
Ethernet The Traverse system supports the following Ethernet features:

Features ■ Link Integrity, page 4-2.
■ Virtual Concatenation, page 4-3.
■ Encapsulation, page 4-3.
■ LCAS, page 4-3.
Link Integrity Link integrity is a feature that applies when the dedicated point-to-point service
connects two Ethernet ports on different nodes (not the same node) and must be
enabled on both ports to operate. This feature monitors the status of Ethernet ports and
the associated transport connection.
If the link integrity feature is enabled, the link is shut down if one of the following
failures occur:
■ A failure on the local port causes the remote port to be signaled to shut down.
■ A failure on the transport paths between the local and remote port causes the near
end port to shut down.
■ A failure on the remote port (if this feature is enabled as well) causes the local port
to shut down.
This feature is configurable through the Integrity Control and Integrity Status
parameters on the Ethernet port.

Chapter 1 Ethernet Services Overview
LCAS
Virtual Virtual concatenation (VCAT) is an inverse multiplexing technique based on ITU-T

Concatenation G.707/Y.1322 and G.783 standards, that supports the bundling of multiple independent
lower-rate channels into a higher rate channel. VCAT enables efficient mapping of
Ethernet frames directly into a payload of separate STS-1 or STS-3c path signals,
known as a virtual concatenation group (VCG). For example, an STS-6c is a virtually
concatenated path multiplexed onto six STS-1 paths. Its bandwidth is six times that of a
STS-1.
This mapping technique eliminates the rigid hierarchies of the common SONET
containers and enables service providers to provision and transport data services more
efficiently.
On a Traverse system, the VC-bundle services also controls how an Ethernet frame is
encapsulated into a SONET frame (either GFP or X.86).
For information on how to configure virtual concatenation, see Chapter 3—“Creating
VC-Bundle Services,” page 4-17.
Encapsulation Creating Ethernet services in a Traverse network requires first creating the transport
paths for the services through the network. Use the SONET-STS service type to create
a transport path.
The Traverse supports two types of encapsulation format for Ethernet over SONET
(EOS) transport:
■ X.86. The system default for EOS when a SONET-STS service is used to create a
transport path.
■ GFP. Generic framing procedure (GFP) encapsulation is a procedure defined in
ITU G.7041, “Generic framing procedure (GFP)”. This procedure is a standard
method for adapting higher-layer data for transport over a SONET or other (e.g.
pure optical) network. Ethernet frames are encapsulated one-for-one into GFP
frames and become a GFP payload.
To change the encapsulation format from the default X.86, you have to add the
contiguously-concatenated SONET-STS service to a VC bundle. See Chapter
3—“Creating VC-Bundle Services,” page 4-17 for detailed information.
LCAS 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 VC bundle use this protocol to manage the bundle. Specifically, a system can
adjust the bundle membership in response to autonomic events (member fail or
recover) or operator requests (add or remove member). LCAS signaling between peers
is carried in the SONET path overhead as outlined in G.7042 and G.707.
See the following topics for a complete description of LCAS capabilities on the
Traverse system.
■ LCAS Operation, page 4-4.
■ LCAS and 1+1 Path Protection, page 4-4.
■ LCAS Group Identifiers, page 4-5.
■ Asymmetric LCAS, page 4-5.
■ LCAS Interworking, page 4-5.

LCAS Operation
LCAS The Traverse considers a member (unprotected or protected) service of a VC bundle to

Operation be failed if there is a critical alarm associated with that member.
The Traverse considers a failed member of a VC bundle to have recovered when the
critical alarm has cleared.
The system generates an LCAS event whenever a member fails or recovers. The event
identifies the VC bundle, the event type (failure or recovery), and the number of
currently active members in the bundle.
Failed Member Services

If a member of an LCAS-enabled VC bundle fails, the system automatically removes
the failed member from the VC bundle. However, the bundle continues to transfer data
on the remaining members. There may be a short period during which data transmitted
on the VC-bundle service is discarded.
The system raises a SONET path alarm when a member fails, identifying both the
failure and the member. The system clears the SONET path alarm when the member
recovers.
If LCAS has removed failed members, and as long as at least one member remains,
Ethernet data continues to flow on any services that are activated on the VC bundle.
The system raises a Server Signal Fail alarm for the VC bundle as well as SONET path
alarms for the individual members when there are no members left in the bundle. The
alarms clear when at least one member returns to health and is added back to the VC
bundle operation.
Restored Member Services

When a previously failed member recovers, then the system automatically uses LCAS
to add the recovered member to the VC bundle. No data drops when the member is
added back into operation.
LCAS and 1+1 Members of a VC bundle can be either unprotected or 1+1 path protected. An
Path unprotected member has a single SONET path. A protected member has two SONET
Protection paths that operate as a path protection group.
When a member is 1+1 path protected and has two paths, failure of one path will not
cause a critical alarm, but failure of both paths will. When both paths are failed,
recovery of the one path removes the critical alarm.
See Section 5, Chapter 1—“Creating 1+1 Path-Protected Services,” page 5-1 for
information on creating protected Ethernet services.

LCAS Interworking
LCAS Group The LCAS protocol uses a group identifier (GID) to identify all members of the bundle
Identifiers in the LCAS messages. The GID is a pseudo-random value selected by each peer to
include in the transmit direction for all members of a particular bundle. The receiving
peer confirms that all members in the bundle contain the same GID value.
If a node receives different GID values for members of the same group, it generates an
LCAS GID Error alarm. This alarm indicates a mismatch of group composition on the
two peers (for example, a member added to the wrong bundle on one node). To correct
this condition, the operator must deactivate the bundle, remove the incorrect member,
add the correct member, and then re-activate the bundle.
Asymmetric Asymmetric LCAS arises when an LCAS-enabled VC bundle is configured with

LCAS different bandwidth in each direction.
The Traverse system correctly transmits and receives Ethernet data when some (but not
all) of the members of the bundle are unidirectional paths.
In addition, the Traverse system correctly transmits and receives Ethernet data when
some (but not all) of the members of the bundle are bi-directional paths that have failed
in only one direction.
LCAS When two nodes use virtual concatenation for a network connection, it is possible that
Interworking 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 on a VC bundle (LCAS
Configuration=Enabled), 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 4-1 LCAS Interworking and System Behavior
Traverse Peer Node System Behavior
Disabled Disabled If a member of a bundle fails, the entire bundle stops

carrying traffic.
The system raises a Server Signal Fail alarm for the
bundle in addition to a SONET path alarm for the
individual member.
The alarms clear when all members are restored and the
bundle starts to carry traffic again.
Disabled Enabled The Traverse ignores and drops all received LCAS
control messages that arrive on the member services.
The Traverse operates as if LCAS is disabled.
Enabled Disabled Traverse operates as is LCAS is disabled.
The Traverse raises a No Remote LCAS alarm on the
Bundle Service. If a member fails, the entire bundle
stops carrying traffic.

Ethernet Transport Features
Table 4-1 LCAS Interworking and System Behavior (continued)
Traverse Peer Node System Behavior
Enabled Enabled If a member of a bundle fails, the bundle continues to

operate at reduced capacity.
The system removes the failed member from the bundle
until it is able to carry traffic again.
When the member is restored, the system automatically
adds it to the bundle again and increases the capacity.
Enabled Disabled The system activates LCAS operation and clears the No
initially, Remote LCAS alarm.
but
becomes
enabled
Ethernet Creating Ethernet services in a Traverse network requires first creating the transport
Transport paths for the services through the network. The Traverse system supports Ethernet over
Features SONET (EOS) transport.
■ Encapsulation. See Encapsulation, page 4-3.
■ 1+1 path protection for Ethernet services. See Section 5, Chapter 1—“Creating
1+1 Path-Protected Services,” page 5-1.
■ Drop-and-continue (multicast). See Section 5, Chapter 2—“Creating
Drop-and-Continue Services Procedures,” page 5-11.
Modules This table lists the Traverse modules required to transport Ethernet services.
Required to Table 4-2 Modules Required to Transport Ethernet Services
Create
Ethernet Service Type Card Type
Services
Point-to-Point Dedicated Any Ethernet module:
■ 8-Port GbE LX
Point-to-Point Shared
■ 8-Port GbE SX
Internet Access Service ■ 24-Port 10/100BaseTX
■ 2-port GbE LX plus 8-port 100BaseFX
Transparent LAN Service ■ 2-port GbE LX plus 16-port 10/100BaseTX
■ 2-port GbE SX plus 16-port 10/100BaseTX

Sources and Destinations for Ethernet Services
Destinations mapping information for creating Ethernet services on a node. For each service type,
for Ethernet any one source can connect to any one destination.
Services
Table 4-3 Sources, and Destinations for Ethernet Services
Service Type Sources Destinations
SONET-STS (EOS) ETH100FX module ETH100FX module

ETH100TX module ETH100TX module
GBE module GBE module
GE2FE16T module GE2FE16T module
GE2FE16F module GE2FE16F module
OC-N ports OC-N ports
VC-Bundle (EOS) ETH100FX module n/a

ETH100TX module
GBE module
GE2FE16T module
GE2FE16F module
Ethernet P2PDedicated ETH100FX port ETH100FX port

ETH100TX port ETH100TX port
GBE port GBE port
SONET-STS service
VC-Bundle service
Ethernet P2PShared ETH100FX port SONET-STS service

ETH100TX port VC-Bundle service
GBE port
Ethernet IAS ETH100FX port ETH100FX port

GBE port GBE port
SONET-STS service
VC-Bundle service
Ethernet TLS ETH100FX port n/a

ETH100TX port
GBE port
SONET-STS service
VC-Bundle service

Guaranteed Data Rates and Ethernet Services
Guaranteed The Guaranteed Data Rate is the total rate of Ethernet data including both the data
Data Rates and packets themselves and the per-packet Ethernet line overhead: 8-byte preamble,
Ethernet 12-byte inter-packet gap.
Services The sum of all guaranteed data rates for all services sharing the destination port must be
less than or equal to the maximum capacity of the transport path or the backplane
connection (see EOS Tagging). The table below shows these maximum capacities.
These are the limits used by Connection Admission Control (CAC) that, when
exceeded, cause the system to reject a new service.
Table 4-4 CAC Limits for Sum of All Guar. Data Rates Sharing a Port
Port Type CAC limits in Mbps
STS-1 48
STS-3c 149
STS-12c 599
STS-43c 1000
STS-1-nv n times 48 but no greater than 1000.
STS-3c-nv n times 149, but no greater than 1000
ETH100FX, ETH100TX 100
GBE 1000
For example, for three P2PS services sharing a path with a Bandwidth of STS-3c, the
sum of the Guar. Data Rates for these three services must not exceed 149 Mbps.
If those three P2PS services share an endpoint with a Bandwidth of STS-48c, the sum
of the Guar. Data Rates for those three services must not exceed 1000.
However, for twenty IAS services sharing a VC-Bundle that contains six STS-1s (that
is, an STS-1-6v), the sum of the Guar. Data Rates for those twenty services must not
exceed 288.
If the system uses X.86 Ethernet over LAPS mapping to carry Ethernet frames over the
SONET transport. LAPS is the type of HDLC used to carry data frames over SONET
transport. The capacity limits in the table above assume a negligible effect from
HDLCs addition of escape characters during the Ethernet-over-SONET encapsulation
process. It is possible that Ethernet data that conforming to the service’s Guar. Data
Rate may contain a high proportion of characters requiring escaping, causing SONET
path congestion and resulting packet loss.

Procedures Required to Create Ethernet Services
Procedures You require a series of procedures to create Ethernet services in a Traverse network.
Required to To create a path to transport the Ethernet traffic, see:
Create ■ Chapter 2—“Creating Ethernet Transport Paths,” , page 4-11.
Ethernet
Services To create a transport path of non-standard concatenated bandwidth, see:
■ Chapter 3—“Creating VC-Bundle Services,” page 4-17.
To actually create an Ethernet service, use the following information:
■ Chapter 4—“Creating Point-to-Point Dedicated Services,” , page 4-25.
■ Chapter 5—“Creating Point-to-Point Shared Services,” , page 4-31.
■ Chapter 6—“Creating Ethernet IAS Services,” , page 4-37.
■ Chapter 7—“Creating Ethernet TLS Services,” , page 4-45.

Procedures Required to Create Ethernet Services

Chapter 2
Creating Ethernet Transport Paths
Introduction Creating Ethernet services in a Traverse network requires first creating the transport
paths for the services through the network. Use the SONET-STS service type to create
a transport path. Create the transport path either hop-by-hop or end-to-end.
The transport paths can be grouped together into non-standard a virtually concatenated
signals. For information on VC-bundles, see Chapter 3—“Creating VC-Bundle
Services,” page 4-17.
This chapter include information on the following topics:
■ Modules Required to Create Transport Paths, page 4-11.
■ Before You Create Transport Paths, page 4-12.
■ Guidelines to Create Transport Paths, page 4-13.
■ Other Transport Applications, page 4-14.
■ Create a Transport Path End-to-End, page 4-14.
■ Create a Transport Path Hop-by-Hop, page 4-15.
Modules This table lists the Traverse modules required to transport Ethernet services.
Required to
Create Table 4-5 Modules Required to Transport Ethernet Services
Transport
Service Type Card Type
Paths
SONET-STS Any Ethernet module AND OC-N modules.
(hop-by-hop) The underlying SONET topology must be connected and configured.
SONET-STS Any Ethernet module.

(end-to-end)
VC-Bundles

Before You Create Transport Paths
Before You Review these requirements before you create transport paths for Ethernet services.
Create Table 4-6 Ethernet Transport Paths Requirements
Transport
Paths Requirement Reference
Read the information in Section 4, Chapter 1—“Ethernet Services Overview”.
Hardware
You need a combination of the modules to create See Modules Required to Create Transport Paths,
transport paths for Ethernet services. page 4-11 in this chapter.
Volume 1, General Information,
Section 2—Hardware Descriptions.
Software

The physical network is connected and Volume 3, Provisioning, Section 2—Configuring

configured. Equipment.

Protection Groups
Ethernet interfaces are configured correctly. Volume 3, Provisioning, Section 1, Chapter 4,”
Change Ethernet Port Parameters, page 1-39.
If necessary, path protection is configured. Volume 3, Provisioning, Section 5, Chapter

1—“Creating 1+1 Path-Protected Services,”
page 5-1.
You are aware of the valid sources and Volume 3, Provisioning, Section 4, Chapter 1,”
destinations for this service. Sources and Destinations for Ethernet Services,
page 4-7.

specific service and change only configurable Section 5, Chapter 6—“Ethernet Services”.
fields on screen.

■ End-to-end. OR Service Creation Models.
■ Hop-by-hop.

The bandwidth must be sufficient to carry the Transport Capacity.
guaranteed data rate for the intended Ethernet Volume 3, Provisioning, Section 4, Chapter 1,”
services. Guaranteed Data Rates and Ethernet Services,
page 4-8.
Guidelines. See Guidelines to Create Transport Paths,

page 4-13 in this chapter.

Chapter 2 Creating Ethernet Transport Paths
Guidelines to Create Transport Paths
Guidelines to General guidelines for provisioning Ethernet transport are as follows:

Create ■ Use the SONET-STS service type to create a transport path for Ethernet services.
Transport See Section 3, Chapter 5—“Creating SONET Services,” page 3-53 for complete
Paths information.
■ If you create a transport path hop-by-hop, the bandwidth of each service must be
the same at each node in the network.
■ The system default for Ethernet over SONET (EOS) transport is X.86. To change
the encapsulation format, see Chapter 3—“Creating VC-Bundle Services,”
Change the Encapsulation Format on a Standard Concatenated Signal,
page 4-23.
■ A transport path can be a termination point for up to eight (Gbe module) or 24
(10/100Base TX module) P2PD or P2PS Ethernet services (this is the number of
ports on a Ethernet module).
■ A shared transport path can be a termination point for up to 243 IAS Ethernet
services.
■ When a transport path is a termination point for multiple Ethernet services, all of
the services must be “shared” services of the same type (P2PS, IAS or TLS).
■ A transport path that is a termination point for a P2PD service can not be a
termination point for any other type of Ethernet service or another P2PD service.
■ A transport path that is part of a VC-Bundle must be created and activated before
the VC-Bundle is activated.
Table 4-7 Ethernet Cards and Total Number of Terminations
Card Type
GbE LX -VC 8
2-port GbE LX-VC plus 8-port 100BaseFX-VC 24
2-port GbE LX-VC plus 16-port 10/100BaseTX-VC 24
2-port GbE SX-VC plus 16-port 10/100BaseTX-VC 24
10/100BaseTX-VC 24

Other Transport Applications
Other Use the procedures in the following chapters to configure transport paths in different
Transport applications:
Applications ■ Section 4, Chapter 3—“Creating VC-Bundle Services,” page 4-17.
■ Section 5, Chapter 1—“Creating 1+1 Path-Protected Services,” page 5-1.
■ Section 5, Chapter 2—“Creating Drop-and-Continue Services Procedures,”
page 5-11.
Create a Use a single SONET-STS service to create a transport path end-to-end through the
Transport Path network. If you create a path end-to-end, you can only add and drop traffic or monitor
End-to-End each end. If you create a transport path hop-by-hop, you can monitor performance and
alarms at each hop in the network.
Table 4-8 Create an Ethernet Transport Path End-to-End
Step Procedure
1 Create an end-to-end SONET-STS service between two nodes. See the

procedure: Create a SONET-STS Service, page 3-58.
The Source Card is the Ethernet module on the node that add traffic to the
network.
For any SONET-STS service created with an Ethernet card as the source
card, the Source in the Service screen shows Port-0 which references the
OC-48 interface on the backplane.
The Source Starting STS references the OC-48 interface on the
backplane.
The Destination Card is the Ethernet module on the node that drops
traffic from the network. If the trunk module is in a protection group,
select the module that transmits working traffic.
2 The Create an Ethernet Transport Path End-to-End, page 4-14 procedure is
complete.

Chapter 2 Creating Ethernet Transport Paths
Create a Transport Path Hop-by-Hop
Create a Use a sequence of SONET-STS services to create a transport path hop-by-hop through
Transport Path the network. If you create a transport path hop-by-hop through the network, you can
Hop-by-Hop add and drop traffic or monitor performance and alarms at each hop. If you create a
transport path end-to-end, you can only monitor each end.
Table 4-9 Create an Ethernet Transport Path Hop-by-Hop
Step Procedure
1 Create a SONET-STS service at the first node. See the procedure: Create a
SONET-STS Service, page 3-58.
The Source Card is the Ethernet module.
The Destination Card is the trunk module. If the trunk module is in a
protection group, select the module that transmits working traffic.
2 Create a SONET-STS service at the drop node. See the procedure: Create a
SONET-STS Service, page 3-58.
The Source Card is the trunk module. If the trunk module is in a
protection group, select the module that receives the working traffic.
The Destination Card is the Ethernet module.
3 At each intermediate node, create a SONET-STS service to between the
ingress and egress trunk cards. See the procedure: Create a SONET-STS
Service, page 3-58.
4 The Create an Ethernet Transport Path Hop-by-Hop, page 4-15 procedure
is complete.

Create a Transport Path Hop-by-Hop

Chapter 3
Creating VC-Bundle Services
Introduction Virtual concatenation (VCAT) is an inverse multiplexing technique based on ITU-T

G.707/Y.1322 and G.783 standards, that supports the bundling of multiple independent
lower-rate channels into a higher rate channel. VCAT enables efficient mapping of
Ethernet frames directly into a payload of separate STS-1 or STS-3c path signals,
known as a virtual concatenation group (VCG). For example, an STS-6c is a virtually
concatenated path multiplexed onto six STS-1 paths. Its bandwidth is six times that of a
STS-1.
This mapping technique eliminates the rigid hierarchies of the common SONET
containers and enables service providers to provision and transport data services more
efficiently.
On a Traverse system, the VC-bundle services also controls how an Ethernet frame is
encapsulated into a SONET frame (either GFP or X.86).
This chapter explains how to create a VC-Bundle on a Traverse system.
■ Example of a VC-Bundle Service, page 4-18.
■ Before You Create VC-Bundle Services, page 4-19.
■ Guidelines to Provision a VC-Bundle Service, page 4-20.
■ Create a VC-Bundle Service, page 4-21.
■ Change the Encapsulation Format on a Standard Concatenated Signal,
page 4-23.

Example of a VC-Bundle Service
Example of a Virtual concatenation provides a logical mesh of multiple, right-sized transport

VC-Bundle channels over an existing SONET transport network.
Service
1 2
SONET-STS Services SONET-STS Services
(Path 1 & Path 2) (Path 3 & Path 4)
3&4 5&6
VC Bundle VC Bundle
OC-48 1+1 APS OC-48 1+1 APS
GCM GCM GCM GCM GCM GCM

ETH OC48 OC48 ETH
GBE OC48 OC48 OC48 OC48 ETH OC48 OC48
Slot 1 Slot 15 Slot 16 Slot 1 Slot 13 Slot 14 Slot 15 Slot 16 Slot 1 Slot 15 Slot 16
Ethernet Port Ethernet Port Ethernet Port
Port 1: 100 Mbps Port 1: 100 Mbps Port 1: 100 Mbps
1. Service Type: SONET-STS (Path 1&2) 2. Service Type: SONET-STS (Path 3&4)
Source: Node 1/slot-1/ETH100TX card Source: Node 2/slot-1/ETH100TX card
Dest: Node 2/slot-1/ETH100TX card Dest: Node 3/slot-1/ETH100TX card
Bandwidth: STS-3c Bandwidth: STS-3c
3. Service Type: VC-Bundle 4. Service Type: VC-Bundle 6. Service Type: VC-Bundle

Source Node: Node 1 Source Node: Node 2 Source Node: Node 3
Bundle Services: P1 & P2 Services Bundle Services: P1 & P2 Services Bundle Services: P3 & P4 Services
Concatenation Type: Virtual Concatenation Type: Virtual Concatenation Type: Virtual
5. Service Type: VC-Bundle

Source Node: Node 2
Bundle Services: P3 & P4 Services
Concatenation Type: Virtual
Figure 4-1 VC-Bundle Services
To create VC-bundles, first create the standard SONET-STS service then bundle them
together.

Chapter 3 Creating VC-Bundle Services
Before You Create VC-Bundle Services
Before You Review the information in this topic before you create bundle any services.
Create Table 4-10 VC-Bundle Service Requirements
VC-Bundle
Services Requirement Reference
Hardware
You need a combination of the modules to bundle Volume 3, Provisioning, Section 4, Chapter 2,”
transport paths for Ethernet services. Modules Required to Create Transport Paths,
page 4-11.
Software



Protection Groups

page 5-1.
You are aware of the valid sources and Volume 3, Provisioning, Section 4, Chapter 1,”
destinations for this service. Sources and Destinations for Ethernet Services,
page 4-7.
You can only bundle SONET-STS services that Volume 3, Provisioning, Section 3, Chapter 1,”
originate and terminate on Ethernet modules. Traverse Service Types, page 3-5.
Volume 3, Provisioning, Section 4, Chapter
2—“Creating Ethernet Transport Paths,” page 4-11.
Member services are configured and activated. Volume 3, Provisioning, Section 4, Chapter
The bandwidth of destination services must be 2—“Creating Ethernet Transport Paths,” page 4-11.
sufficient to carry the guaranteed data rate
provisioned for the Ethernet services transported
over it.

page 5-1.

specific service and change only configurable Section 5, Chapter 3—“DS3 Services”.
fields on screen.

Guidelines to Provision a VC-Bundle Service
Table 4-10 VC-Bundle Service Requirements (continued)

■ Hop-by-hop only. Service Creation Models.

■ n times the bandwidth of the provisioned Transport Capacity.
source services. Volume 3, Provisioning, Section 4, Chapter 1,”
Guaranteed Data Rates and Ethernet Services,
page 4-8.
Guidelines. Guidelines to Provision a VC-Bundle Service,

page 4-20.
Guidelines to Before you create a VC-Bundle service, review the following guidelines:
Provision a ■ You can only bundle SONET-STS services that originate and terminate on an
VC-Bundle Ethernet modules.
Service ■ Create a bundle service at both ends of the transport path.
■ When you create a bundle, ensure the member services match on both the source
and destination nodes.
■ The member services must be the same bandwidth: STS-1 or STS-3c. A bundle
cannot contain a mixture of path sizes.
■ A bundle can contain up to 21 member STS-1 services or up to seven STS-3c
services.
■ A member service can only be in one bundled service.
■ The total Ethernet payload capacity of a bundle is based on the member services.
For example, a bundle containing four STS-1s has an Ethernet payload capacity of
192 Mbps (4 * 48 Mbps). Transport Capacity, page 5-3 shows the payload
capacity for each supported transport path.
■ The system calculates the bandwidth of the bundle when the service is activated. A
bundle containing four STS-1s is STS-1-4v, and has a bandwidth four times that of
an STS-1. A VC bundle containing four STS-3c is STS-3c-4v, and has a bandwidth
of four times that of an STS-3c.
■ Create and activate the member services before creating and activating the VC
bundle service.
■ Create and activate a bundle service before it using it to carry Ethernet services.
■ Deactivate a bundle service before making any changes (add or remove services) to
the bundle.
■ The Traverse platform supports static LCAS. Static LCAS allows an activated VC
bundle that contains multiple members to continue to operate when one or more
members have failed.
See Chapter 1—“Ethernet Services Overview,” LCAS Operation, page 4-4 for a
complete description of LCAS capabilities on the Traverse system.

Create a VC-Bundle Service
Create a Use this procedure to create a VC-Bundle service.

VC-Bundle
Important: The member services must be created before you can bundle
Service
them together. See Before You Create VC-Bundle Services, page 4-19.
Table 4-11 Create a VC-Bundle Service
Step Procedure
1 Complete the Configure General Information, page 3-13 procedure for this
service.
2 Provision the VC-Bundle by adding services in the Define VC-Bundle
Service —Service Level Agreement screen (Steps 3 to 9).
Figure 4-2 VC-Bundle Service—Service Level Agreement
3 In the LCAS Configuration parameter, select:

■ Enabled to allow the system to remove any failed members from this
service and continue to operate using a reduced capacity.
■ Disabled (default) to stop the bundle from carrying any traffic if a
member fails.
4 In the Concatenation Type parameter, select Virtual.

Create a VC-Bundle Service
Table 4-11 Create a VC-Bundle Service (continued)
Step Procedure
5 In the Encapsulation Type parameter, select:

■ GFP for generic framing procedure encapsulation.
■ X.86 (default) for X.86 encapsulation.
6 From the Source Node list, select the node to create the VC bundle.
7 From Bundle Type, select STS.
See Guidelines to Provision a VC-Bundle Service, page 4-20 for specific
information on which services you can bundle.
8 From the Services list box, select the services on this node to be bundled
together.
Hold the Control key on the keyboard and click multiple individual
services or hold the Shift key and select a range of consecutive services.
9 Click Add to add the selected services to the Bundle list box.
10 Click Finish to provision the service and return to the service list on the
Service tab.
11 Repeat Steps 1 through 10 to bundle services together at the other endpoint
node.
12 The Create a VC-Bundle Service procedure is complete.
page 3-17.

Change the Encapsulation Format on a Standard Concatenated Signal
Change the On a Traverse system, the VC-bundle services also controls how an Ethernet frame is
Encapsulation encapsulated into a SONET frame (either GFP or X.86). In this situation, first create a
Format on a standard SONET-STS service with a concatenated bandwidth. Then, add the signal to a
Standard VC-Bundle and change the encapsulation format. Use this procedure to change the
Concatenated Encapsulation format of the Ethernet frame.
Signal
Table 4-12 Change the Encapsulation Format
Step Procedure
1 Create an Ethernet transport path with a standard concatenation. See

Chapter 2—“Creating Ethernet Transport Paths,” page 4-11.
2 Add the transport service to a VC-Bundle.
Figure 4-3 VC-Bundle Service—Service Level Agreement
3 From the Source Node list, select the node to create the VC bundle.
4 From the Services list box, select the SONET-STS service with the
Bandwidth=STS-3c, STS-12c, or STS-48c.
5 Click Add to add the selected services to the Bundle list box.
6 From the Concatenation Type list, select Standard.
7 From the Encapsulation Type list, select:
■ GFP for generic framing procedure encapsulation.
■ X.86 (default) for X.86 encapsulation.

Change the Encapsulation Format on a Standard Concatenated Signal
Table 4-12 Change the Encapsulation Format (continued)
Step Procedure
Service tab.
9 Repeat Steps 1 to 8 at the other end of the SONET-STS service.
10 The Change the Encapsulation Format procedure is complete.
page 3-17.

Chapter 4
Creating Point-to-Point Dedicated Services
Introduction This chapter explains how to create a point-to-point dedicated (P2PD) Ethernet service
on a Traverse system. Use this service to extend a private LAN network across a
network. Bandwidth is dedicated to one Ethernet (10/100 or GbE) port and data is
transported over the network using a dedicated transport path.
■ Example of a Point-to-Point Dedicated Service, page 4-26.
■ Before You Create Point-to-Point Dedicated Services, page 4-26.
■ Guidelines to Create a Point-to-Point Dedicated Service, page 4-28.
■ Create a Point-to-Point Dedicated Service, page 4-28.

Example of a Point-to-Point Dedicated Service
Example of a A P2PD Ethernet service allows a customer to transport Ethernet frames from one
Point-to-Point Ethernet port over a dedicated transport path.The bandwidth of the transport path can
Dedicated be a contiguous signal (STS-1, STS-3c, STS-12c, or STS-48c) or a virtually
Service concatenated signal (VC-Bundle).
1. Service Type: SONET-STS (Path 1) 2. Service Type: SONET-STS (Path 2)

Source: Node 1/slot-1/ETH100TX card/STS-1 Source: Node 1/slot-1/ETH100TX card/STS-2
Dest: Node 2/slot-1/ETH100TX card/STS-1 Dest: Node 3/slot-1/ETH100TX card/STS-2
Bandwidth: STS-1 Bandwidth: STS-1
2
1
4 6
OC-48 1+1 APS OC-48 1+1 APS
3 5

ETH OC48 OC48 ETH
3. Service Type: Ethernet P2PD 5. Service Type: Ethernet P2PD

Source: Node 1/slot-1/port -11 Source: Node 1/slot-1/port -11
Dest: Node 1/Service STS Path 1 Dest: Node 1/Service STS Path 1
4. Service Type: Ethernet, P2PD 6. Service Type: Ethernet, P2PD

Source: Node 1/slot-1/port-1 Source: Node 1/slot-1/port-1
Figure 4-4 Dedicated Ethernet Private Line Service
Before You Review the information in this topic before you create a point-to-point dedicated
Create Ethernet service.
Point-to-Point
Dedicated Table 4-13 Point-to-Point Dedicated Service Requirements
Services
Read the information in Chapter 1—“Ethernet Services Overview,” page 4-1.
Hardware
You need a combination of the modules to create Volume 3, Provisioning, Section 4, Chapter 1,”
Ethernet services. Modules Required to Create Ethernet Services,
page 4-6 for a list of required modules for specific
services.
Software

Chapter 4 Creating Point-to-Point Dedicated Services
Before You Create Point-to-Point Dedicated Services
Table 4-13 Point-to-Point Dedicated Service Requirements (continued)



Protection Groups.
Transport for Ethernet services is correctly Volume 3, Provisioning, Section 4, Chapter

configured and activated. 2—“Creating Ethernet Transport Paths,” page 4-11.
The bandwidth of destination services must be Volume 3, Provisioning, Section 4, Chapter
sufficient to carry the guaranteed data rate 3—“Creating VC-Bundle Services,” page 4-17.
over it.

page 5-1.
You are aware of the valid sources and Volume 3, Provisioning, Chapter 1—“Ethernet
destinations for this service. Services Overview,” Sources and Destinations for
Ethernet Services, page 4-7.

specific service and change only configurable Section 5, Chapter 6—“Ethernet Services,”
fields on screen.

■ Hop-by-hop only. Service Creation Models, page 3-7.

Transport Capacity, page 3-3.
Volume 3, Provisioning, Section 4, Chapter 1,”
page 4-8.
Provisioning Guidelines. Review the information in the topic: Guidelines to

Create a Point-to-Point Dedicated Service,
page 4-28 in this chapter.

Guidelines to Create a Point-to-Point Dedicated Service
Guidelines to General guidelines for provisioning Ethernet point-to-point dedicated (P2PD) services
Create a are as follows:
Point-to-Point ■ The source of a P2PD service is always a Ethernet port.
Dedicated ■ The destination of a P2PD service may be one of:
Service – another Ethernet port.
– a SONET-STS service.
– a VC-Bundle service
■ A P2PD service can operate with third-party EOS vendor equipment when the
service.
■ The P2PD service supports asymmetrical guaranteed data rates. Guaranteed data
rates can be set to different rates at each endpoint node.
■ The bandwidth for the dedicated transport path must support the “higher”
guaranteed data rate assigned to an asymmetrical P2PD service.
Create a Use this procedure to create an Ethernet point-to-point dedicated service.

Point-to-Point
Dedicated Table 4-14 Create an Ethernet Point-to-Point Dedicated Service
Service
Step Procedure
1 Review the information in Before You Create Point-to-Point Dedicated

Services, page 4-26 before you start this procedure.
2 Complete the procedure, Configure General Information, page 3-13 for
this service.
3 Set the characteristics of the service in the Define Ethernet Service
—Service Level Agreement screen (Steps 4 to Steps 10).
Figure 4-5 Define Ethernet Service—Service Level Agreement
4 From the ETH Service Type list, select P2PDedicated.

Chapter 4 Creating Point-to-Point Dedicated Services
Create a Point-to-Point Dedicated Service
Table 4-14 Create an Ethernet Point-to-Point Dedicated Service (continued)
Step Procedure
5 From the Guar. Data Rate list select the amount of data (in Mbps) the
service can send without having any data dropped. Range is 0–1000 in
increments of 1. Default is 1. This value is applied to the data received at
the source port and submitted to the transport path.
See Guaranteed Data Rates and Ethernet Services, page 4-8 for more
information.
6 The EOS Tagging adds a proprietary tag to incoming packets and appears
on the user interface only if the destination is a transport service.
In the EOS Tagging field, specify if packets (either sent or received) on
the path have VLAN tags. This parameter must be set the same for both
Ethernet services that make up the domain Ethernet service. Select one of
the following:
■ Enabled (default): packets will have VLAN tags.
■ Disabled: packets will NOT have VLAN tags. Use Disabled only if
the Ethernet service is interworking with another vendor’s equipment.
You can set EOS tagging to Disabled for no more than 4 services per
card.
7 Enter the source information:
originates.
■ From the Source Port list, select the Ethernet port where this service
originates. See Sources and Destinations for Ethernet Services,
page 4-7 for a complete list of valid sources for this service.
8 From the Destination list, select the destination entity from the list of
available Ethernet destinations on the selected node. See Sources and
Destinations for Ethernet Services, page 4-7 for a complete list of valid
destinations for this service.
9 From the VLAN ID list, select a VLAN identification number. Range is
1–4093 in increments of 1. The VLAN ID should be the same at both
endpoints of the domain service. The same VLAN ID cannot be reused on
the same Ethernet card, but can be used on different Ethernet cards.
10 Click Finish to provision this service and return to the Service List screen.
11 The Create an Ethernet Point-to-Point Dedicated Service procedure is
complete.
page 3-17.

Create a Point-to-Point Dedicated Service

Chapter 5
Creating Point-to-Point Shared Services
Introduction A point-to-point shared service (P2PS) maps Ethernet traffic from up to 24 Ethernet
interfaces on one Ethernet module into one transport path and transports the traffic
across the network to another Ethernet module. Use the P2PS service to offer “shared
Ethernet private line” services. Or, use this service to extend a LAN network across a
network using a shared transport path.
This chapter explains how to create a point-to-point shared service on a Traverse
system and includes the following topics:
■ Example of a Point-to-Point Shared Service, page 4-32.
■ Before You Create Point-to-Point Shared Services, page 4-33.
■ Guidelines to Create a Point-to-Point Shared Service, page 4-34.
■ Create an Ethernet Point-to-Point Shared Service, page 4-35.

Example of a Point-to-Point Shared Service
Example of a A P2PS Ethernet service allows customers extend their LAN over a SONET network.
Point-to-Point However, with point-to-point shared service the service provider transports data over
Shared Service the SONET network using a shared transport path. Each Ethernet service are PCs
connected to an leased Ethernet port on the both ends of the shared transport path. The
bandwidth allocated to the shared path must be sufficient to carry the combined
guaranteed data rates assigned to the shared Ethernet services.
1. Service Type: SONET-STS (Path 1)

Source: Node 1/slot-1/ETH100TX card/STS-1
Dest: Node 2/slot-1/ETH100TX card/STS-1
Bandwidth: STS-1
2 2
OC-48 1+1 APS OC-48 1+1 APS
3 3
4 4
ETH OC48 OC48 OC48 OC48 OC48 OC48 ETH OC48 OC48
4. Service Type: Etherent P2PS 3. Service Type: Etherent P2PS


Figure 4-6 Point-to-Point Shared Services
The bandwidth of the transport path can be a contiguous signal (STS-1, STS-3c,
STS-12c, or STS-48c) or a virtually concatenated signal (VC-Bundle).

Chapter 5 Creating Point-to-Point Shared Services
Before You Create Point-to-Point Shared Services
Before You Review the information in this topic before you create a point-to-point Shared Ethernet
Create service.
Point-to-Point
Shared Table 4-15 Point-to-Point Shared Service Requirements
Services
Read the information in Chapter 1—“Ethernet Services Overview,” page 4-1.
Hardware
services.
Software



Protection Groups.

over it.

page 5-1.

fields on screen.


Guidelines to Create a Point-to-Point Shared Service
Table 4-15 Point-to-Point Shared Service Requirements (continued)

page 4-8.

Create a Point-to-Point Shared Service, page 4-34
in this chapter.
Guidelines to General guidelines for provisioning point-to-point shared (P2PS) Ethernet services are
Create a as follows:
Point-to-Point ■ The source of a P2PS service is always a Ethernet port.
Shared Service ■ The destination of a P2PS service may be one of:
– another Ethernet port.
– a SONET-STS service.
– a VC-Bundle service
■ P2PS services sharing a transport path must terminate on the same Ethernet
module.
■ P2PS services do not support interoperability with third-party EOS vendor
equipment.
■ The P2PS service supports asymmetrical guaranteed data rates. Guaranteed data
rates can be set to different rates at each endpoint node.
■ The bandwidth for the shared transport path must support the combined “higher”
guaranteed data rates assigned to asymmetrical services.

Chapter 5 Creating Point-to-Point Shared Services
Create an Ethernet Point-to-Point Shared Service
Create an Use this procedure to create an Ethernet Point-to-Point Shared service.

Ethernet
Point-to-Point Table 4-16 Create an Ethernet Point-to-Point Shared Service
Shared Service
Step Procedure
1 Review the information in Before You Create Point-to-Point Shared

Services, page 4-33 before you start this procedure.
this service.
—Service Level Agreement screen.
4 From the ETH Service Type list, select P2PShared.

5 Class of Service is Gold. Gold class of service emulates a private line
service with these characteristics: guaranteed bandwidth, no burstiness
allowed, no loss, bounded low delay and bounded low delay jitter.
See Create an Ethernet Point-to-Point Shared Service, page 4-35 for
more information.

Create an Ethernet Point-to-Point Shared Service
Table 4-16 Create an Ethernet Point-to-Point Shared Service (continued)
Step Procedure

originates.
originates.See Create an Ethernet Point-to-Point Shared Service,
available Ethernet destinations on the selected node. See Create an
Ethernet Point-to-Point Shared Service, page 4-35 for a complete list of
valid destinations for this service.
9 From the VLAN ID list, select a VLAN identification number. The range
is 1–4093 in increments of 1. The VLAN ID should be the same at both
10 Click Finish to provision the service and return to the services list on the
Service tab.
11 The Create an Ethernet Point-to-Point Shared Service procedure is
complete.
page 3-17.

Chapter 6
Creating Ethernet IAS Services
Introduction An Internet access service allows multiple subscribers access the hub site router for
Internet access. This service aggregates traffic in two locations: at the subscriber side
and at the hub site. On the subscriber side, the node statistically multiplexes Ethernet
traffic from multiple Ethernet ports on the same card onto a transport path. At the hub
site, the node statistically multiplexes traffic from multiple transport path onto one
single Ethernet interface. Use the IAS service to offer shared Ethernet access to Internet
services.
This chapter explains how to create an Ethernet Internet Access Service (IAS).
■ Example of an IAS Ethernet Service, page 4-37.
■ Before You Create an IAS, page 4-39.
■ Guidelines to Create an IAS, page 4-40.
■ Create an IAS, page 4-41.
Example of an Internet Access Service (IAS) is a multipoint-to-point service. It allows a service

IAS Ethernet provider to aggregate Internet traffic from multiple customers and provide access to an
Service ISP router (Internet) over a SONET network.
Traffic aggregated from multiple customers (multiple subscriber-side Ethernet ports)
travels over a transport path to a single provider-side Ethernet port connected to an ISP
router.
Similarly, internet traffic travels over a transport path to multiple subscriber-side
Ethernet ports. Each customer has access to the ISP router through their own Ethernet
port. The ISP router has access to each customer through a single Ethernet port. Yet
none of the customers can communicate with each other (separate VLAN IDs).
The network in the following example is an OC-48 ring. Once the ring is connected and
configured, create the transport paths for the Ethernet services. The bandwidth must be

Example of an IAS Ethernet Service
sufficient to carry the guaranteed data rate for the IAS services. Finally, for each
Ethernet tributary, configure a subscriber-side and a provider-side service.
1
1. Service Type: SONET-STS 2
Source: Node 1/ slot-1/ETH100TX card/sts-1 Internet
Dest: Node 3/slot-8/GE2FE16T card/sts-1
Protection Type: UPSR Protected
2. Service Type: SONET-STS

Source: Node 1/ slot-2/ETH100TX card/sts-2
Dest: Node 3/slot-8/GE2FE16T card/sts-2
Node 2
3 8
7
6
4
W E W E
OC-48 UPSR
5
GCM GCM GBE/
ETH ETH OC48 OC48 OC48 OC48 TX
Node 1 Node 4
5. Service Type: Ethernet IAS 6. Service Type: Ethernet IAS
Source: Node 1/ slot-2/port-22 ETH100TX Source: Node 4/slot-8/port-1 GBE
Dest: SONET-STS Service 2 Dest: SONET STS Service 2
Src. Part. Type: Subscriber, VLAN ID: 3 Src. Part. Type: Provider, VLAN ID: 3

Source: Node 1/ slot-1/port-11 ETH100TX Source: Node 4/slot-8/port-1 GBE
Dest: SONET-STS Service 1 Dest: SONET-STS Service 1

Source: Node 1/slot-1/port-1 ETH100TX Source: Node 4 slot-8/port-1 GBE
Node 3
Dest: SONET STS Service 1 Dest: SONET-STS Service 1
Figure 4-8 Ethernet Internet Access Services
To configure the Ethernet services in the above example, create the following services:
1. Create two end-to-end SONET-STS services with the Ethernet modules as the
source and destination. These services are the transport path.
2. On each tributary node (Node 1, Node 2, and Node 3), create subscriber-side IAS
Ethernet services. Each service has a negotiated service level agreement.
3. Finally, for each subscriber-side IAS service, create a provider-side IAS Ethernet
service at the hand-off node (Node 4).

Chapter 6 Creating Ethernet IAS Services
Before You Create an IAS
Before You Review the information in this topic before you create an IAS services.
Create an IAS Table 4-17 IAS Service Requirements
Hardware
services.
Software



Protection Groups.

over it.

page 5-1.


page 4-8.

Create an IAS, page 4-40 in this chapter.

Guidelines to Create an IAS
Guidelines to General guidelines for provisioning an Ethernet IAS are:

Create an IAS ■ Ethernet ports for IAS service have different roles. The provider-side port connects
to one ISP router and provides connectivity to the Internet. The subscriber-side
port(s) are connected to multiple ISP customers and provides them access to the
Internet using one ISP router.
■ IAS services sharing a transport path must terminate on one provider-side port that
is connected to an ISP router. Multiple IAS provider-side ports may share a single
transport path.
■ The transport paths can be grouped together into non-standard a virtually
concatenated signals. See Chapter 3—“Creating VC-Bundle Services,” page 4-17.
■ Multiple transport services can terminate on one IAS provider-side port. The total
guaranteed data rate of the IAS services on the provider-side port can not exceed
the Ethernet port speed (10/100 Mbps or 1 Gbps). See Guaranteed Data Rates
and Ethernet Services, page 4-8.
■ When a Ethernet port is a termination point for multiple Ethernet services all of the
services must be IAS (multipoint-to-point).
■ IAS services do not support interoperability with third-party EOS vendor
equipment.
Guaranteed Data Rates and Bandwidth
■ IAS services support asymmetrical guaranteed data rates. Guaranteed data rates
can be set to different rates at each endpoint node.
■ The bandwidth for the bandwidth for the transport path must support the combined
“higher” guaranteed data rates assigned to asymmetrical services.

Create an IAS
Create an IAS A multipoint-to-point Internet Access Service (IAS) connects a customer to an ISP
router for access to the Internet. Each customer appears to have a direct connection to
the Internet. IAS services are transported over the network using shared transport paths.
Use this procedure to create an Ethernet Internet Access Service.
Table 4-18 Create an IAS Service
Step Procedure
1 Review the information in Before You Create an IAS, page 4-39 before
this service.
—Service Level Agreement screen.
4 From the ETH Service Type list, select IAS.

Create an IAS
Table 4-18 Create an IAS Service (continued)
Step Procedure
5 From the Class of Service list, select the class of service for this service.
This value is applied to the data received from the Source port and
submitted to the transport path.
■ Premium (default). Provides guaranteed bandwidth, no burstiness, no
cell loss, low delay, and low jitter for IAS services. Establishes the
Guaranteed Data Rate (Step 8) over the shared transport path for this
service.
■ Best Effort. Provides no guaranteed bandwidth. Best Effort services
that share the same transport path compete equally for all transport
bandwidth not currently reserved for activated Premium services.
Because the services compete for bandwidth, how much of the data
actually gets through is dependent on other traffic demands on the
transport path. Any Guaranteed Data Rate setting is ignored.
When Premium and Best Effort IAS services share a transport path, the
system reserves at least 10 Mbps of path bandwidth for the Best Effort
services. That is, 10 Mbps of the path bandwidth is not available to be
allocated to Premium services.
6 From the Packet Type field, specify if the Ethernet frames transmitted to
and received from Ethernet port have VLAN tags:
■ Tagged (default): Ethernet ports must have VLAN tags. The VLAN
ID entered for this IAS service must be the same as the VLAN ID on
the incoming tagged packet. You can assign multiple VLAN IDs.
■ Untagged: Ethernet ports must not have VLAN tags. You must assign
a valid VLAN ID for the service. See Step 12 for more information.
7 ISP Class of Service (default=Best Effort).
If Src. Part. Type is Provider (Step 11), set the ISP Class of Service for the
data going over the Ethernet port connected to the ISP router. See Step 5
for Class of Service definition.
See Guaranteed Data Rates and Ethernet Services, page 4-8 for more
information.
originates.
originates.See Sources and Destinations for Ethernet Services,

Create an IAS
Table 4-18 Create an IAS Service (continued)
Step Procedure
available Ethernet destinations on the selected node. See Sources and
Destinations for Ethernet Services, page 4-7 for a complete list of valid
destinations for this service.
11 From the Src. Part. Type list, select if the source port termination point is
connected to a:
■ Subscriber. Establishes the source module/port termination point as
the subscriber side of the IAS service.
■ Provider. Establishes the source port termination point as the provider
side of the IAS service. This is the IAS endpoint connected to the ISP
router. See Step 6 regarding ISP Class of Service.
12 In the VLAN ID field, select a VLAN identification number. The range is
1–4093 in increments of 1. The VLAN ID should be the same at both
■ If the value in Packet Type (Step 6) is Tagged, assign one or more
VLAN IDs for the IAS service. Packets arriving on an Ethernet port
must be tagged with one of the VLAN IDs assigned for the IAS
service. With a Packet Type set to Tagged the node is expecting
“tagged” packets and will check the incoming packet VLAN ID
against the VLAN IDs entered in this field.
You can use up to 243 VLAN IDs for one IAS instance with Packet
Type = Tagged. An IAS instance is the set of subscriber ports that
connect to one provider port. Select the 243 VLAN IDs from the same
screen (for one service) or for multiple services. Do not use the same
VLAN ID in subscriber services on different cards that are part of the
same IAS instance.
■ If the value in Packet Type (Step 6) is Untagged, assign a valid
VLAN ID for this service.
Service tab.
14 The Create an IAS Service procedure is complete
page 3-17.

Create an IAS

Chapter 7
Creating Ethernet TLS Services
Introduction This chapter explains how to create Ethernet transparent LAN services (TLS) on the
Traverse system. Use a TLS service to allow multiple Ethernet devices in multiple
locations to appear as a single private LAN (virtual LAN or VLAN).
■ Example of a TLS Service, page 4-45.
■ Guidelines to Create TLS Services, page 4-47.
■ Before You Create TLS Services, page 4-47.
■ Create a Transparent LAN Service, page 4-49.
Example of a An Ethernet transparent LAN service (TLS) allows multiple Ethernet devices in
TLS Service multiple locations to appear as a single private LAN (virtual LAN/VLAN). An Ethernet
TLS is a collection of TLS services on the same Ethernet module that create a
multipoint-to-multipoint bridge or broadcast domain.
A VLAN ID identifies the Ethernet TLS broadcast domain. One Ethernet module can
support up to four TLS broadcast domains. All TLS services that use the same VLAN
ID are in the same Ethernet TLS instance. The TLS instance uses MAC learning to
discover MAC address to endpoint forwarding associations.
Received packets destined for a learned MAC address are forwarded to that endpoint.
Packets received at a termination point with a destination MAC address that is either a
broadcast or a multicast address, or a unicast address that has not been learned, are
flooded to all the other termination points in the TLS.
In the Traverse system, create an Ethernet TLS service using a series of termination
points. The termination point is either an Ethernet port (source termination) or a TDM
endpoint (destination termination). Ethernet ports are identified by slot number and
port number. TDM endpoints are identified by SONET-STS service IDs.

Example of a TLS Service
In the following diagram TLS services are transported over the network using STS
paths. At each node, for each VLAN ID, create a Ethernet TLS service and associate a
termination point.
1. Service Type: SONET-STS (Path 1) 2. Service Type: SONET-STS (Path 2)

Source: Node 1/slot-1/ETH100TX card Source: Node 2/slot-1/ETH100TX card
Dest: Node 2/slot-1/ETH100TX card Dest: Node 3/slot-1/ETH100TX card
1 2
5 8 11
OC-48 1+1 APS OC-48 1+1 APS
4 7 10
3 6 9

ETH OC48 OC48 ETH
3. VLAN ID 1 6. VLAN ID 1 9. VLAN ID 1
TLS Service 1: slot-1/port 21 ETH100TX TLS Service 7: slot-1/port -21 ETH100TX TLS Service 16: slot-1/port -21 ETH100TX
TLS Service 2: Service STS Path 1 TLS Service 8: Service STS Path 1 TLS Service 17: Service STS Path 2
TLS Service 9: Service STS Path 2
4. VLAN ID 2 7. VLAN ID 2 10. VLAN ID 2

TLS Service 3: slot-1/port-11 ETH100TX TLS Service 10: slot-1/port-11 ETH100TX TLS Service 18: slot-1/port-11 ETH100TX
TLS Service 12: Service STS Path 2
8. VLAN ID 3
5. VLAN ID 3 TLS Service 13: slot-1/port-1 ETH100TX 11. VLAN ID 3
TLS Service 5: slot-1/port-1 ETH100TX TLS Service 14: Service STS Path 1 TLS Service 20: slot-1/port-1 ETH100TX
Figure 4-10 Transparent LAN Services over SONET Transport Paths

Chapter 7 Creating Ethernet TLS Services
Before You Create TLS Services
Guidelines to General guidelines for provisioning a TLS service are:

Create TLS ■ An Ethernet module can use up to than two of its TDM endpoints for TLS.
Services ■ One Ethernet module can support up to four instances of TLS (identified by a
VLAN ID). All TLS instances on the module must use one or both of the same two
TDM endpoints.
■ One Ethernet port is in only one TLS instance.
■ A TLS bridge is made up of services on a single Ethernet module.
■ You can activate a new TLS service to a bridge (a service with the same VLAN ID
as other activated TLS services) without affecting traffic.
■ When you deactivate one TLS service in a bridge, that port stops forwarding
traffic, the rest of the bridge is not affected.
■ For this release, TLS is supported on loop-free topology only. TLS is not supported
on a spanning tree topology.
■ TLS services do not support interoperability with third-party EOS vendor
equipment.
■ TLS services are transported over the network using transport paths (SONET-STS
services). These paths may be grouped (groups of STS-1s or STS-3cs) together in a
virtually concatenated VC-Bundle. See Chapter 3—“Creating VC-Bundle
Services,” page 4-17.
Before You Review this information before you start to create TLS services.
Create TLS
Services Table 4-19 TLS Service Requirements
Hardware
services.
Software



Protection Groups.

Before You Create TLS Services
Table 4-19 TLS Service Requirements (continued)

over it.

page 5-1.

fields on screen.


page 4-8.

Create TLS Services, page 4-47 in this chapter.

Create a Transparent LAN Service
Create a Use this procedure to help you create an Ethernet transparent LAN service (TLS).
Transparent
LAN Service Table 4-20 Create an Ethernet Transparent LAN Service (TLS)
Step Procedure
1 Review the information in Before You Create TLS Services, page 4-47
this service.
3 Set the characteristics of the service in the Define Ethernet
Service—Service Level Agreement screen.
4 From the ETH Service Type list, select TLS.

5 From the Node list, select the node where this service originates.
6 From the Port/TDM Endpoint list, select the port or transport service
where this service originates.

Table 4-20 Create an Ethernet Transparent LAN Service (TLS) (continued)
Step Procedure
7 The Define Ethernet Service—Service Level Agreement screen display

changes depending on the type of Port/TDM Endpoint selected in Step 5:
■ If the Port/TDM Endpoint = SONET-STS service or VC-Bundle, go
to Step 8.
Figure 4-12 Service Level Agreement—TDM Endpoint
■ If the Port/TDM Endpoint = ETH100TX or GbE, go to Step 9.
Figure 4-13 Service Level Agreement—ETH100TX or GbE Port

Table 4-20 Create an Ethernet Transparent LAN Service (TLS) (continued)
Step Procedure
8 If the Port/TDM Endpoint = a SONET-STS service or VC-Bundle

service, set the following parameters:
■ From the Ethernet Card list select the card for the broadcast domain.
The broadcast domain connects an arbitrary number of ports (Ethernet
or TDM Endpoints) on the same card.
■ From the Guar. Data Rate list select the amount of data (in Mbps) the
increments of 1. Default is 1. This value is applied to the data received
at the source port and submitted to the transport path. There is no
traffic contract for a TLS service on an Ethernet port.
See Guaranteed Data Rates and Ethernet Services, page 4-8 for
more information.
9 From the VLAN ID list, select a VLAN identification number. The range
is 1–4093 in increments of 1. The VLAN ID should be the same at both
Service tab.
11 The Create an Ethernet Transparent LAN Service (TLS) procedure is
complete.
page 3-17.


S ECTION 5 P ROVISIONING S ERVICE A PPLICATIONS
S ECTION 3SERVICE PROVISIONING P ROCEDURES
Contents
Chapter 1
Creating 1+1 Path-Protected Services
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
Two Services Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
STS Protection Group Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3
Before You Create a 1+1 Path-Protected Service . . . . . . . . . . . . . . . . . . . . . 5-4
Guidelines to Provision a 1+1 Path-Protected Service . . . . . . . . . . . . . . . . . . 5-5
Procedures Required to Create a 1+1 Path-Protected Service . . . . . . . . . . . 5-6
Create a Path-Protected Service Using Two Services . . . . . . . . . . . . . . . . . . 5-6
Create a Path-Protected Service Using a 1+1 Path Protection Group . . . . . . 5-8
Chapter 2
Creating Drop-and-Continue Services Procedures
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11
Example of a Drop-and-Continue Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11
Ethernet Services and Drop-and-Continue Applications . . . . . . . . . . . . . . . . . 5-13
Modules Required to Create Drop-and-Continue Service. . . . . . . . . . . . . . . . 5-13
Before You Create a Drop-and-Continue Service . . . . . . . . . . . . . . . . . . . . . . 5-13
Guidelines to Provision Drop-and-Continue Services . . . . . . . . . . . . . . . . . . . 5-14
Parameters Required to Provision Drop-and-Continue Services . . . . . . . . . . 5-14
Procedures Required to Provision a Drop-and-Continue Service . . . . . . . . . . 5-15
Provision an Add Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16
Provision a Drop Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-18
Provision a Continue Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-20
Chapter 3
Creating Optical Transmux Services
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-23
Transforming Channelized DS3s to VT-Mapped STSs. . . . . . . . . . . . . . . . . . 5-24
Switching DS1s Inside a Channelized DS3. . . . . . . . . . . . . . . . . . . . . . . . . . . 5-25
Modules Required to Create an Optical Transmux Service . . . . . . . . . . . . . . 5-26
Before You Create an Optical Transmux Service . . . . . . . . . . . . . . . . . . . . . . 5-26
Guidelines to Provision and Optical Transmux Services. . . . . . . . . . . . . . . . . 5-27
Procedures Required to Provision an Optical Transmux Service . . . . . . . . . . 5-27
Assign and Configure Transmux Resources. . . . . . . . . . . . . . . . . . . . . . . . . . 5-28
Configure Optical Transmux Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-30

Volume 3 Section 5 Provisioning Service Applications
Chapter 4
Creating Services on Overlapping UPSRs
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-33
Services on Overlapping UPSRs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-33
Example of a Bidirectional Protected STS Path . . . . . . . . . . . . . . . . . . . . . . . 5-34
Example of Bidirectional Protected DS1 and VT Services . . . . . . . . . . . . . . . 5-35
Modules Required at Interconnecting Nodes. . . . . . . . . . . . . . . . . . . . . . . . . . 5-36
Before You Create Services on Overlapping Rings. . . . . . . . . . . . . . . . . . . . . 5-36
Guidelines to Provision Services on Overlapping Rings . . . . . . . . . . . . . . . . . 5-37
Procedures Required to Provision Services on Overlapping Rings. . . . . . . . . 5-37
Create an Add Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-38
Create a Pass Through Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-39
Create a Drop Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-40
Create a Continue Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-42
Chapter 5
Creating Transparent Services Procedures
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-45
Example of Transparent Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-46
Modules Required to Create a Transparent Service . . . . . . . . . . . . . . . . . . . . 5-47
Before You Create a Transparent Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-47
Guidelines to Provision Transparent Services. . . . . . . . . . . . . . . . . . . . . . . . . 5-48
Procedures Required to Create a Transparent Service. . . . . . . . . . . . . . . . . . 5-48
Disable Control Data Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-48
Provision the Transparent Service Procedure . . . . . . . . . . . . . . . . . . . . . . . . . 5-49
List of Figures
Figure 5-1 Creating 1+1 Path Protection with Two Services . . . . . . . . . . . . . 5-2
Figure 5-2 Creating 1+1 Path Protection with a Protection Group . . . . . . . . . 5-3
Figure 5-3 Drop-and-Continue Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12
Figure 5-4 Transforming Channelized DS3 Signals to VT-Mapped STS . . . . 5-24
Figure 5-5 Switching DS1 Signals Inside a Channelized DS3 . . . . . . . . . . . . 5-25
Figure 5-6 Click a TMX Port, Click the Config Tab . . . . . . . . . . . . . . . . . . . . . 5-28
Figure 5-7 Switch to STS1TMX Port Type . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-28
Figure 5-8 Confirm Switch Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-29
Figure 5-9 Transmux Service SLA Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-30
Figure 5-10 Bidirectional Protected STS Paths in Overlapping PRI . . . . . . . . . 5-34
Figure 5-11 Bidirectional DS1 and VT Services in Overlapping Rings . . . . . . . 5-35
Figure 5-12 Transparent SONET Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-46

List of Tables
Table 5-1 1+1 Path-Protected Service Requirements. . . . . . . . . . . . . . . . . . 5-4
Table 5-2 Create a Path-Protected Service Using Two Services . . . . . . . . . 5-6
Table 5-3 Create a Path-Protected Service Using a 1+1 Path
Protection Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8
Table 5-4 Modules Required for Drop-and-Continue Services . . . . . . . . . . . 5-13
Table 5-5 Drop-and-Continue Service Requirements . . . . . . . . . . . . . . . . . . 5-13
Table 5-6 Required Parameters for Drop-and-Continue Services . . . . . . . . 5-14
Table 5-7 Provision an Add Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16
Table 5-8 Provision a Drop Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-18
Table 5-9 Provision a Continue Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-20
Table 5-10 Modules Required for an Optical Transmux Service. . . . . . . . . . . 5-26
Table 5-11 Optical Transmux Service Requirements . . . . . . . . . . . . . . . . . . . 5-26
Table 5-12 Assign and Configure Transmux Resources. . . . . . . . . . . . . . . . . 5-28
Table 5-13 Configure Optical Transmux Services. . . . . . . . . . . . . . . . . . . . . . 5-30
Table 5-14 Modules Required at the Interconnecting Nodes . . . . . . . . . . . . . 5-36
Table 5-15 Protected Ring Interconnection in Overlapping Rings . . . . . . . . . 5-36
Table 5-16 Create an Add Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-38
Table 5-17 Create a Pass Through Service . . . . . . . . . . . . . . . . . . . . . . . . . . 5-39
Table 5-18 Create a Drop Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-40
Table 5-19 Create a Continue Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-42
Table 5-20 Modules Required for Transparent Services. . . . . . . . . . . . . . . . . 5-47
Table 5-21 Transparent Service Requirements . . . . . . . . . . . . . . . . . . . . . . . 5-47
Table 5-22 Disable the Control Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-48
Table 5-23 Provision the Transparent Services . . . . . . . . . . . . . . . . . . . . . . . 5-49


S ECTION 5PROVISIONING S ERVICE A PPLICATIONS
Chapter 1
Creating 1+1 Path-Protected Services
Introduction 1+1 path-protected services protect the entire path of one service through a network.
This feature is designed to protect paths in a mesh network. You can also use 1+1 path
protection to protect traffic traveling over unprotected facilities.
This chapter explains how to create a 1+1 path-protected service through a Traverse
network:
■ Two Services Model, page 5-1.
■ STS Protection Group Model, page 5-3.
■ Before You Create a 1+1 Path-Protected Service, page 5-4.
■ Guidelines to Provision a 1+1 Path-Protected Service, page 5-5.
■ Procedures Required to Create a 1+1 Path-Protected Service, page 5-6.
■ Create a Path-Protected Service Using Two Services, page 5-6.
■ Create a Path-Protected Service Using a 1+1 Path Protection Group, page 5-8
Two Services This model uses two services to create a protected path across a network. First
Model provision an unprotected service. Subsequently add a protected service either
immediately or at a later date. Use this method to configure the following end-to-end
service types for 1+1 path protection:
■ DS3-CC.
■ SONET-STS.
In the following example, first provision an unprotected end-to-end service. Activate
the unprotected service, then provision the protecting service to create a protecting
path.

Volume 3, Section 5: Provisioning Service Applications
Two Services Model
Notice that at the Node 1, the source for both services is identical. At the Node 4, the
destination for both services is identical. You can choose the paths at each intermediate
node using the Constraints screen of the service creation.

Protection Type = Unprotected

Resource Advisory = OFF
Src: Node 1/slot-1/port-1/sts-1
Protection Type = 1+1 Path Protected
OC-48 OC-48
OC12 OC48 OC48

OC12 OC48 OC48
Slot 1 Slot 15 Slot 16
Slot 1 Slot 15 Slot 16
Node 1 (Source node)
Node 6 (Drop node)
Figure 5-1 Creating 1+1 Path Protection with Two Services
The network interfaces at the Source and Drop nodes cannot be part of a 1+1 APS or
BLSR protection group. However, the interfaces can be part of a UPSR or unprotected.
Activate provisioned services in any order. However, the service you activate first
carries the active traffic.

Chapter 1 Creating 1+1 Path-Protected Services
STS Protection Group Model
STS Protection This model uses a 1+1 path protection group to create a protected path across the
Group Model network. First, provision the required services at each node across the network.
Subsequently, add a 1+1 path protection group either immediately, or at a later date.
Use 1+1 path protection groups to configure path protection for the following service
types:
■ DS1.
■ DS1-Mux.
■ DS3-TMX.
■ SONET-VT.
In the following example, first create and activate the sequence of unprotected services
(Steps 1, 2, 3, and 4). Then create the 1+1 path protection group at the Add and Drop
nodes (Steps 5 and 6). The pass through services at the intermediate nodes can be on
any available path.
1. Service Type: DS1-Mux 2. Service Type: SONET-STS (Pass Through) 4. Service Type: SONET-VT
Src: Node 1/slot-1/all ports Src: Node 2/slot 15/port-1/sts-4 Src: Node 1/slot 15/port-1/sts-4/vtg1-vt1
Dest: Node 4/slot-15/port-1/sts-4 Dest: Node 2/slot-16/port-1/sts-4 Dest: Node 4/slot-1/port-1/sts-1/vtg1-vt1
Protection Type: Unprotected Protection Type: Unprotected Protection Type: Unprotected
5. STS Path Protection Group 6. STS Path Protection Group

Working: Node 1/slot-15/port-1/sts-4 Working: Node 6/slot-15/port-1/sts-4
Protecting: Node 1/slot-16/port-1/sts-35 Protecting: Node 6/slot-16/port-1/sts-35
2
W P
5 6
W P
1 2 Node 3 2
OC-48 3 3 OC-48
Node 2 3 Node 5
DS1 OC48 OC48 OC12 OC48 OC48

VT
Node 1 (Source node) Node 4 Node 6 (Drop node)
3. Service Type: SONET-STS (Pass Through)

Figure 5-2 Creating 1+1 Path Protection with a Protection Group

Before You Create a 1+1 Path-Protected Service
Before You Review the information in this topic before you create a 1+1 path-protected service.
Create a 1+1
Path-Protected Table 5-1 1+1 Path-Protected Service Requirements
Service
Hardware
The hardware depends on the services you are Volume 1, General Information,
creating. See the appropriate chapter in this Section 2—Hardware Descriptions.
volume to determine the correct hardware for Volume 3, Provisioning, Section 3—Creating
each service type. Services.
Software



specific service and change relevant parameters Section 5—Creating Services.
only. See Volume 5, TransNav Management
System for descriptions of other fields on screen.
Service Types. Volume 3, Provisioning, Section 3, Chapter 1,”

■ DS1. Traverse Service Types, page 3-5.
■ DS1-Mux.
■ DS3-CC.
■ DS3-TMX
■ SONET-STS.
■ SONET-VT
■ VC-Bundle.
Provisioning model. Two service creation model

■ DS1: STS protection group. STS protection group model.
■ DS1-Mux: STS protection group.
■ DS3-CC: two services.
■ DS3-TMX: STS protection group.
■ SONET-STS: two services.
■ SONET-VT: STS protection group.
■ VC-Bundle: two services.

Guidelines to Provision a 1+1 Path-Protected Service
Guidelines to The guidelines to provision a 1+1 path-protected service are:

Provision a 1+1 ■ There are two models with which to create path-protected services:
Path-Protected – Create two services with the same endpoints.
Service – Use a 1+1 path protection group.
■ Use the two services model to create path protection for the following service
types:
– DS3-CC.
– SONET-STS. Also use a path-protected SONET-STS service to transport
Ethernet services.
■ Use the protection group model to create path protection for the following service
types:
– DS1.
– DS1-Mux.
– DS3-TMX.
– SONET-VT.
■ The network interfaces at the source and drop nodes cannot be part of a 1+1 APS
or BLSR protection group. However, the interfaces can be part of a UPSR or
unprotected.
■ Provision the unprotected services first.
■ Provision the path-protected service or the protection group second.
■ At the intermediate nodes, the path numbers can be different (Constraints screen).
■ If any part of the network has another type of protection, you must make the
cross-connection to the working facility.
■ Because the Resource Advisory function is turned OFF when you create the 1+1
path-protected service, be sure to know the available resources from your network
plan.
■ You can activate the services in any order, however, the service you activate first
carries the active traffic.

Procedures Required to Create a 1+1 Path-Protected Service
Procedures Use the following procedures to help you provision 1+1 path-protected services on a
Required to Traverse system.
Create a 1+1 1. Create a Path-Protected Service Using Two Services, page 5-6.
Path-Protected 2. Create a Path-Protected Service Using a 1+1 Path Protection Group, page 5-8.
Service 3. Section 2, Chapter 5—“Create a 1+1 Path Protection Group,” page 2-21.
4. Activate a Service, page 3-17.
These procedures reference required parameters only. See Section 3—Creating
Services to reference all configurable parameters for each service type:
Create a Use this procedure to help you provision a path-protected service using two services.
Path-Protected
Service Using Table 5-2 Create a Path-Protected Service Using Two Services
Two Services
Step Procedure
1 At originating node, click the Service tab, and click Add to add this
service to the network.
2 In the Define Service—General Information screen, specify required
parameters for this service:
■ In the Name field, type: a name for the service.
■ From the Service Type list, select one of the following services:
– DS3-CC.
– SONET-STS.
3 Click Next to display the Define Service—Service Level Agreement
screen.
■ From the Source Node list, select the node that originates the traffic.
■ From the Source Port list, select the port that originates the traffic.
■ From the Source Path list, select the select the correct path number if
this is a SONET service.
■ At the add node, the Source Path number must be same as 1+1
path-protected service.
At any intermediate nodes, the Source Path number can be different
through the network (Step 8).

Create a Path-Protected Service Using Two Services
Table 5-2 Create a Path-Protected Service Using Two Services (continued)

Step Procedure
5 Enter the destination information:

■ From the Destination Node list, select the destination node for the
service.
■ From the Destination Port list, select a trunk port on the node. If the
destination port is part of a protection group, select the port that is
receiving the working traffic.
■ From the Destination Path list, select the correct path number if this
is an SDH or SONET service.
At the drop node, the starting STS number must be the same as 1+1
At any intermediate nodes, the starting STS number can be different
through the network (Step 8).
6 Click Next to display the Define Service—Transport screen.
7 From the Protection Type list,
■ Select Unprotected for the unprotected service.
■ Select 1+1 Path Protected for the protecting service.
8 Click Next to display the Define Service—Constraints screen.
Verify the ingress and egress information is correct for this service.
At the drop node, the starting STS number must be the same as 1+1
At any intermediate nodes, the starting STS number can be different
9 Repeat Steps 1 to 8 for the second service.
Service tab.
11 The Create a Path-Protected Service Using Two Services procedure is
complete.
service. You can activate the services in any order, however, the service
you activate first carries the active traffic.

Create a Path-Protected Service Using a 1+1 Path Protection Group
Create a Use this procedure to help you provision a path-protected service using two services.
Path-Protected
Service Using Table 5-3 Create a Path-Protected Service Using a 1+1 Path Protection Group
a 1+1 Path
Protection Step Procedure
Group 1 At originating node, click the Service tab, and click Add to add this
service to the network.
– DS1.
– DS1-Mux.
– DS3-TMX.
– SONET-VT.
screen.
■ From the Source Node list, select the node that originates the traffic.
■ From the Source Port list, select the port or card that originates the
traffic.
■ From the Source Path list, select the correct path if this is a
SONET-VT service.
■ If this is a SONET-VT service, select the correct Source VT for the
service.
■ From the Destination Node list, select the same node as you did in
Step 4 for the service.
■ From the Destination Port list, select a trunk port on the node. If the
destination port is part of a protection group, select the port that is
transmitting the working traffic.
■ From the Destination Path list, select the correct path number if this
is a SONET-VT service.
7 From the Protection Type list, select Unprotected for the unprotected
service.
Service tab.
9 Repeat Steps 1 to 8 at each node in the path for the service.

Table 5-3 Create a Path-Protected Service Using a 1+1 Path Protection Group
Step Procedure
10 At the Source and Drop nodes, create a 1+1 path protection group. See
Create a 1+1 Path Protection Group, page 2-24.
11 The Create a Path-Protected Service Using a 1+1 Path Protection Group
procedure is complete.
service. You can activate the services in any order, however, the service
you activate first carries the active traffic.


Chapter 2
Creating Drop-and-Continue Services
Procedures
Introduction This chapter explains how to create a drop-and-continue service in a Traverse network.
■ Example of a Drop-and-Continue Service, page 5-11.
■ Ethernet Services and Drop-and-Continue Applications, page 5-13.
■ Modules Required to Create Drop-and-Continue Service, page 5-13.
■ Before You Create a Drop-and-Continue Service, page 5-13.
■ Parameters Required to Provision Drop-and-Continue Services, page 5-14.
■ Procedures Required to Provision a Drop-and-Continue Service, page 5-15.
Example of a Drop-and-continue applications allow you to add traffic to a UPSR, drop traffic at one
Drop-and- location, and continue the signal to another destination around the ring.
Continue To provision a drop-and-continue service, you need to provision a combination of three
Service types of services at different nodes in the network.
1. Add Service: This service adds the traffic to the ring. You provision this service at
the node where the traffic enters the ring.
2. Drop Service: This service drops traffic from the ring. You provision this service
at any node for traffic traveling in either direction around the ring.
3. Continue Service: This service carries the traffic around the ring. After you have
dropped traffic at one node, you continue the path around the network. You
provision this service at any node for traffic traveling in either direction around the
ring.
Provision all required services on one node before you move to the next. That is,
configure the services hop-by-hop through the network. Provision and activate the drop
service before you provision the continue service.
working signal.
The following example an OC-48 UPSR is already connected and configured. The
West Ports are Slot 15 on all the nodes. The East Ports are Slot 16. Traffic enters the
ring at Node and is bridged in both directions around the ring.

Example of a Drop-and- Continue Service
This example shows ONLY the services you need to create at each node to drop and
continue traffic around the ring.
4. Service Type: SONET-STS (Drop)

Src: Node 4 - slot 15 - port 1 - sts4
ALL SERVICES Dest: Node 4 - slot 2 - port 1 - sts4
y Hop-by-hop Directionality = Unidirectional
y Resource Advisory = OFF Protection Type = UPSR Video Client 1
y Bandwidth = STS-3c
3. Service Type: SONET-STS (Continue)
1. Service Type: SONET-STS (Add) 2. Service Type: SONET-STS (Continue) Src: Node 3 - slot 15 - port 1 - sts4
Src: Node 1 - slot 2 - port 1 - sts4 Src: Node 3 - slot 15 - port 1 - sts4 Dest: Node 3 - slot 16 - port 1 - sts4
Dest: Node1 - slot 16 - port 1 - sts4 Dest: Node 3 - slot 16 - port 1 - sts4 Directionality = Unidirectional
Directionality = Unidirectional Directionality = Unidirectional Protection Type = Unprotected
Protection Type = UPSR Video Server Protection Type = Unprotected

4
1 2 3
W E W E W E
OC12 OC48 OC48 OC12 OC48 OC48 OC12 OC48 OC48

Slot 2 Slot 15 Slot 16 Slot 2 Slot 15 Slot 16 Slot 2 Slot 15 Slot 16
OC-48 UPSR
y West Ports = Slot 15
y East Ports = Slot 16
6
10 7
9 8 5
W E W E W E
OC12 OC48 OC48 OC12 OC48 OC48 OC12 OC48 OC48

Slot 2 Slot 15 Slot 16 Slot 2 Slot 15 Slot 16 Slot 2 Slot 15 Slot 16
9. Service Type: SONET-STS(Continue) 8. Service Type: SONET-STS (Continue) 5. Service Type: SONET-STS (Continue)
Src: Node 2 - slot 15 - port 1- sts4 Src: Node 3 - slot 15 - port 1 - sts4 Src: Node 2 - slot 16 - port 1- sts 4
Dest: Node 2 - slot 16 - port 1 - sts4 Dest: Node 3 - slot 16 - port 1 - sts4 Dest: Node 2 - slot 15 - port 1 - sts 4
Directionality = Unidirectional Directionality = Bidirectional Directionality = Unidirectional
Protection Type = Unprotected Video Client 3 Protection Type = Unprotected Protection Type = Unprotected
10. Service Type: SONET-STS(Drop) 6. Service Type: SONET-STS (Continue)

Src: Node 2 - slot 15 - port 1 - sts4 Src: Node 3 - slot 15 - port 1 - sts4
Dest: Node 2 - slot 2 - port 1 - sts4 Dest: Node 3 - slot 16 - port 1 - sts4
Directionality = Unidirectional Directionality = Unidirectional
Protection Type = UPSR Protection Type = Unprotected
7. Service Type: SONET-STS (Drop)
Src: Node 4 - slot 15 - port 1 - sts4
Dest: Node 4 - slot 2 - port 1 - sts4
Directionality = Unidirectional
Protection Type = UPSR Video Client 2
Figure 5-3 Drop-and-Continue Service
In this example, traffic added at Node 1 is bridged around the ring. On the Traverse
system, when you create the Add Service, you can use either the East or West port as
the destination, the system creates the second connection to the other port of the ring.
For any service that has Protection Type = UPSR, the system creates the second
connection from the signal traveling in the opposite direction around the ring.

Chapter 2 Creating Drop-and-Continue Services Procedures
Before You Create a Drop-and- Continue Service
Ethernet To create Ethernet services in a drop-and-continue application, use the same example
Services and (Figure 5-3 Drop-and-Continue Service, page 5-12). However, the Add service would
Drop-and- originate on an Ethernet module. The Drop service would terminate on an Ethernet
Continue module.
Applications
Modules This table lists the Traverse modules required to create a drop-and-continue services.
Required to
Create Table 5-4 Modules Required for Drop-and-Continue Services
Drop-and-
Continue
Service SONET-STS OC-N OC-N
Before You Review the information in this topic before you create a drop-and-continue service.
Create a Table 5-5 Drop-and-Continue Service Requirements
Drop-and-
Continue Requirement Reference
Service
Hardware
See Modules Required to Create Drop-and- Volume 1, General Information,

Continue Service, page 5-13. Section 2—Hardware Descriptions.
The hardware depends on the services you are Volume 3, Provisioning, Section 3—Creating
creating. See the appropriate chapter in this Services.
volume to determine the correct hardware for
each service type.
Software



specific service and change relevant parameters Section 5, Chapter 4—“SONET Services,”
only. See Volume 5, TransNav Management page 5-29.

■ SONET-STS Traverse Service Types, page 3-5.


■ DS3-CC: 44.736 Mbps. Transport Capacity, page 3-3.
■ SONET-STS: 48.960 Mbps.

Guidelines to Provision Drop-and- Continue Services
Guidelines to The guidelines to provision a drop and continue service are:

Provision ■ The UPSR must be connected and provisioned. See Section 2, Chapter 6—“Create
Drop-and- a UPSR Protection Group,” page 2-27.
Continue ■ Provision the required service (Source, Drop, or Continue) at each hop in the
Services network.
■ Provision all required services on one node before you move to the next.
■ Provision and activate the drop service before you provision the continue service.
■ The working and protect path numbers around the ring must match. That is, if you
add an SONET-STS-3c service onto STS number 4 at the first node, you must use
STS number 4 at each node to transport that service around the ring.
■ Because the Resource Advisory function is turned OFF for these procedures, be
sure to know the available resources from your network plan.
Parameters Use the information in the following table to help you provision drop and continue
Required to services on a UPSR.
Provision
Drop-and- Table 5-6 Required Parameters for Drop-and-Continue Services
Continue
Service Parameter Value
Services
ALL SERVICES
General Information Screen Service Type ■ SONET-STS
Resource Advisory OFF
Source Service
Service Level Agreement Screen Source Port Tributary port
Destination Port Trunk (East or West) port on ring
Dest. Starting Path Must match on all nodes in ring
Transport Screen Directionality Uni-Directional
Protection Type UPSR Protected
Drop Service
Service Level Agreement Screen Source Port Trunk (East or West) port on ring
Src. Starting Path Must match Dest. Starting Sts

from Source Service.
Destination Port Drop port (tributary)
Dest. Starting Path Any available starting STS num-

ber
Transport Screen Directionality Uni-Directional
Protection Type UPSR Protected

Procedures Required to Provision a Drop-and- Continue Service
Table 5-6 Required Parameters for Drop-and-Continue Services (continued)
Service Parameter Value
Continue Service
Service Level Agreement Screen Source Port Trunk (East or West) port on ring
Src. Starting Path Must match Dest. Starting Path

Destination Port Trunk port (East or West) on ring.

Opposite of Source Port.
Dest. Starting Path Must match Dest. Starting Path

Transport Screen Directionality Uni-Directional on drop nodes.

Bi-directional on intermediate
nodes.
Protection Type Unprotected (protected by physi-

cal ring)
Procedures To fully provision a drop-and-continue service, you must provision a combination of

Required to three types of services at different points in your network. Use the following
Provision a procedures to help you provision drop-and-continue services on a Traverse system.
Drop-and- 1. Provision an Add Service, page 5-16.
Continue 2. Provision a Drop Service, page 5-18.
Service 3. Provision a Continue Service, page 5-20.
These procedures reference required parameters only. Use the following procedures to
reference all configurable parameters for each service type:
■ Section 3, Chapter 5,” Create a SONET-STS Service.

Provision an Add Service
Provision an This service adds the traffic to the ring. You provision this service at the node where the
Add Service traffic enters the ring. The source of this service is a tributary port. The destination is
either trunk port (East or West) of the ring. You create this add service as UPSR
protected and the system creates both the working and protection paths around the ring.
Table 5-7 Provision an Add Service
Step Procedure
1 In Map View, click the Service tab, then click Add to add a new service to
this network.
– SONET-STS.
■ From the Resource Advisory list, select OFF.
screen and set the service characteristics for this service (Steps 4 to 6).
4 From the Bandwidth list, select the bandwidth required to transport this
service.
If the source of this service is in an equipment protection group, select the
source on the working module.
■ From the Source Node list, select the node that adds traffic to the ring.
■ From the Source Port list, select the port that adds traffic to the ring.
■ From the Source Path list, select the path number where this service
originates.
in Step 5 as the destination of the service.
■ From the Destination Port list, select a trunk port (East or West) of
the ring configuration.
■ From the Destination Path list, select an available starting path
number. The working and protect path numbers around the ring must
match. That is, if you add an STS-3c service onto path 4 at the first
node, you must use path 4 at each node to transport that service around
the ring.

Provision an Add Service
Table 5-7 Provision an Add Service (continued)
Step Procedure
8 Specify the transport path and quality characteristics of this service:

■ From the Directionality list, select Uni-Directional to create
unidirectional paths to the trunk cards on the ring configuration.
■ From the Protection Type list, select UPSR Protected to bridge the
signal to the working and protect paths on the ring configuration.
Service tab.
11 Complete the procedure Activate a Service, page 3-17 to activate the
service.
12 The Provision an Add Service is complete. Continue to the next procedure:
Provision a Drop Service.

Provision a Drop Service
Provision a This service drops traffic from the ring. You can provision this service at any node for
Drop Service traffic travelling in either direction around the ring. The source of this service is the
trunk port (East or West) that receives the added traffic from the ring. The destination is
the port which drops the added traffic from the ring.
Table 5-8 Provision a Drop Service
Step Procedure
this network.
– SONET-STS.
■ From the Resource Advisory list, select Off.
service.
■ From the Source Node list, select the next node in the ring (either
clockwise or counter-clockwise).
■ From the Source Port list, select the port that receives the Source
Service from the ring.
■ From the Source Path list, select the path number onto which you
added the traffic in the Provision an Add Service procedure.
■ From the Destination Port list, select the port that drops the traffic
from the ring.
■ From the Destination Path list, select an available path number. This
path number can be any available path on that port.
7 Click Next to display the Define SONET-STS Service—Transport
screen.Define Transport for a Drop Service

Provision a Drop Service
Table 5-8 Provision a Drop Service (continued)
Step Procedure
8 Set the transport path and quality characteristics for this service:
■ From the Directionality list, select Uni-Directional to create
unidirectional paths from the trunk cards to the drop card.
■ From the Protection Type list, select UPSR Protected to bridge the
signals received from each direction around the ring to the drop card.
Service tab.
service.
12 The Provision a Drop Service is complete.
Continue to the next procedure: Provision a Continue Service.

Provision a Continue Service
Provision a This service carries the traffic around the ring. After you have dropped traffic at one
Continue node, you continue the path around the network. You can provision this service at any
Service node for traffic travelling in either direction. The source of this service is the trunk port
(East or West) that receives the added traffic from the ring. The destination is the other
trunk card on the node.
Table 5-9 Provision a Continue Service
Step Procedure
this network.
– SONET-STS.
■ From the Resource Advisory list, select Off.
service.
■ From the Source Node list, select the next node in the ring (either
clockwise or counterclockwise).
■ From the Source Port list, select the port that receives the Add
■ From the Source Path list, select the path number onto which you
added the traffic in the Provision an Add Service procedure.
■ From the Destination Port list, select the other trunk port. For
example, if you selected the East Port in Step 5, select the West Port
for this destination.
■ From the Destination Path list, select the path number onto which
you added the traffic in the Provision an Add Service procedure.

Table 5-9 Provision a Continue Service (continued)
Step Procedure
8 From the Directionality list,

■ Select Uni-Directional to create unidirectional path from one trunk
card to the other in the ring configuration.
■ Select Bi-Directional on an intermediate node between two drop
points.
9 From the Protection Type list, select Unprotected. The service is
protected by the physical ring configuration.
10 Click Next to display the Define Service—Constraints screen. Verify the
ingress and egress information is correct for this service.
Service tab.
service.
13 The Provision a Continue Service is complete.


Chapter 3
Creating Optical Transmux Services
Introduction The optical transmux feature transforms incoming channelized DS3 signals to
VT-mapped STS payloads on one node.
This chapter explains how to create an optical transmux service in a Traverse network.
■ Transforming Channelized DS3s to VT-Mapped STSs, page 5-24.
■ Switching DS1s Inside a Channelized DS3, page 5-25.
■ Modules Required to Create an Optical Transmux Service, page 5-26.
■ Before You Create an Optical Transmux Service, page 5-26.
■ Procedures Required to Provision an Optical Transmux Service, page 5-27.
■ Assign and Configure Transmux Resources, page 5-28.
■ Configure Optical Transmux Services, page 5-30.

Transforming Channelized DS3s to VT-Mapped STSs
Transforming In the following example, create a series of service types to transport traffic from the
Channelized M13 connected to Node 1 to the TransAccess 100 Mux connected to Node 5.
DS3s to 1. At Node 1, create a DS3-CC service and bridge it around the ring.
VT-Mapped 2. At Node 2, create a service that passes the traffic through the node.
STSs 3. and 4.
At Node 3, use the optical transmux feature to convert the channelized DS3 signal
to a VT-mapped STS and bridge it onto the second ring. Create a SONET-STS
service and indicate that the incoming signal is a channelized DS3.
5. At Node 4, create another pass through SONET-STS service.
6. At Node 5, create a SONET-STS service to connect the transformed STS traffic to
the TransAccess 100 Mux.
1. Service Type: DS3-CC

Source: Node 1/slot-2/port-3 DS3CC
Dest: Node1/slot-16/port-1/sts-1
1. Protection Type: UPSR Protected
M13
W E
Source: Node 2/slot-15/port-1/sts-1
Directionality: Bi-directional
GCM GCM
Node 2
DS3 DS3 OC48 OC48
Slot 1 Slot 2 Slot 15 Slot 16
Node 1 OC-48 UPSR
3. Port Type: STSTMX
3.
4. 4. Service Type: SONET-STS

Source DS3 Mapping:
TMX Port: slot-8/port-1/STSTMX
W E W E Dest: Node 3/slot-16/port-1/sts-1
GCM GCM
OC48 OC48 TMX TMX OC48 OC48
Slot 1 Slot 2 Slot 7 Slot 8 Slot 15 Slot 16
Node 3 OC-48 UPSR
5. Service Type: SONET-STS 6.

Node 4
W E
6. Port Type: EC1

Source: Node 5/slot-2/port-3 EC1 GCM GCM
Dest: Node 5/slot-15/port-1/sts-1 DS3 DS3 OC48 OC48
Protection Type: UPSR Protected Slot 1 Slot 2 Slot 15 Slot 16
TA100 Node 5
Figure 5-4 Transforming Channelized DS3 Signals to VT-Mapped STS

Chapter 3 Creating Optical Transmux Services
Switching DS1s Inside a Channelized DS3
Switching In the following example, create a series of services at different nodes to be able to
DS1s Inside a switch the DS1 traffic inside a channelized DS3 signal.
Channelized 1. At Node 1, create a DS3-CC service and bridge it around the ring.
DS3 2. At Node 2, create a service that passes the traffic through the node.
3. and 4.
At Node 3, use the optical transmux feature to convert the channelized DS3 signal
into a VT-mapped STS. Create a SONET-VT service and indicate that the
incoming and outgoing signals are transformed to a VT-mapped STS. Use the VT
Switch capabilities to switch traffic at the VT layer.
5. At Node 4, create another pass through SONET-STS service.
6. At Node 5, create a DS3-CC service to connect the traffic to the M13.

Source: Node 1/slot-2/port-3 DS3CC
Dest: Node1/slot-16/port-1/sts-1/
1. Protection Type: UPSR Protected
M13
W E
GCM GCM
Node 2
DS3 DS3 OC48 OC48
Node 1 OC-48 UPSR
3. Node 3/slot-6/port-1 STSTMX
3. Node 3/slot-6/port-2 STSTMX
3. 4. 4. Service Type: SONET-VT (x 28)
Source: Node 3/slot-1/port-1/sts-1/VTG1-VT1
Source DS1 Mapping:
Dest: Node 3/slot-16/port-1/sts-1/VTG4-VT3
W E W E Dest DS1 Mapping:
GCM GCM
OC48 OC48 TMX TMX VT VT OC48 OC48
Slot 1 Slot 2 Slot 5 Slot 6 Slot 7 Slot 8 Slot 15 Slot 16
Node 3 OC-48 UPSR
5. Service Type: SONET-STS 6.

Node 4
W E

Source: Node 5/slot-2/port-3 DS3CC GCM GCM
Dest: Node 5/slot-15/port-1/sts-1 DS3 DS3 OC48 OC48
Protection Type: UPSR Protected Slot 1 Slot 2 Slot 15 Slot 16
M13 Node 5
Figure 5-5 Switching DS1 Signals Inside a Channelized DS3
In the above example, if a TransAccess 100 Mux were connected to Node 5 instead of
the M13, you would only need to transform the source signal at Node 3 (Source DS1
Mapping parameter). At Node 5, you would create a SONET-STS service to the EC1
port connected to the TransAccess 100 Mux.

Modules Required to Create an Optical Transmux Service
Modules This table lists the Traverse modules required to create an optical transmux service.
Required to
Create an Table 5-10 Modules Required for an Optical Transmux Service
Optical
Transmux
Service SONET-STS DS3-CC or DS3-TMX (EC1) DS3-CC or DS3-TMX (EC1)
OC-N OC-N
SONET-VT OC-N OC-N
Other modules
DS3TMX n/a n/a
VT Switch (for SONET-VT n/a n/a

services only)
Before You Review the information in this topic before you create an optical transmux service.
Create an
Optical Table 5-11 Optical Transmux Service Requirements
Transmux
Service
Hardware
See Modules Required to Create an Optical Volume 1, General Information,

Transmux Service, page 5-26. Section 2—Hardware Descriptions.
Volume 3, Provisioning, Section 3—Creating
Services.
Software

Protection groups are configured for the Volume 3, Provisioning, Section 2—Creating
following modules: Protection Groups.
■ Trunk facilities.
■ Tributary facilities.
■ DS3TMX module.
■ VT/VC Switch module.



Procedures Required to Provision an Optical Transmux Service
Table 5-11 Optical Transmux Service Requirements (continued)

■ SONET-STS. Traverse Service Types, page 3-5.
■ SONET-VT
Guidelines to The guidelines to provision an optical transmux service are:

Provision and ■ There must be at least one DS3TMX module in the same node. This module can be
Optical in a 1:1 or 1:2 equipment protection group.
Transmux ■ Each Transmux card can support up to 12 transmux instances (one STS per port).
Services ■ Reserve one STSTMX port for each incoming STS carrying a channelized DS3.
■ There must be at least one VT Switch module in the same node to be able to switch
DS1s inside the channelized DS3 that have been transformed into a VT-mapped
STS (SONET-VT service).
Procedures To provision an optical transmux service, you must provision a combination of services
Required to at different points in your network. Use the following procedures to help you provision
Provision an an optical transmux feature on a Traverse system.
Optical 1. Section 3, Chapter 2,” Add a Service, page 3-12.
Transmux 2. Section 3, Chapter 2,” Configure General Information, page 3-13.
Service 3. Section 3, Chapter 2,” Activate a Service, page 3-17.
■ Section 3, Chapter 5,” Create a SONET-STS Service, page 3-58.
■ Section 3, Chapter 5,” Create a SONET-VT1.5 Service, page 3-66.

Assign and Configure Transmux Resources
Assign and Use this procedure to assign and configure transmux resources on the DS3TMX card.
Configure
Transmux Table 5-12 Assign and Configure Transmux Resources
Resources
Step Procedure
1 Review the information in Before You Create an Optical Transmux

Service, page 5-26.
2 In Map View, double click the node that is performing the optical transmux
functions.
3 In Shelf View, assign transmux resources for each STS requiring
transformation.
Step 4
Figure 5-6 Click a TMX Port, Click the Config Tab
4 Click a TMX port, click the Config tab.

5 Select STS1TMX, then click Switch.
Figure 5-7 Switch to STS1TMX Port Type

Assign and Configure Transmux Resources
Table 5-12 Assign and Configure Transmux Resources (continued)
Step Procedure
6 In the confirmation dialog box, click Yes to confirm the change.
Figure 5-8 Confirm Switch Dialog Box
7 Configure the interface parameters for the STS1TMX port type:

■ 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.
DS1 to VT Map: Select how the DS1 signals map into a VT payload on
this port. See Table 3-1 GR-253 and Sequential VT Mapping Formats,
page 3-29 for the list of mapping formats. If this port is part of a protection
group, this parameter must be the same on both modules. Select one of the
following values:
■ Non-Sequential (default).
■ Sequential.
8 Repeat Steps 3–7 for each STS carrying a channelized DS3 payload.
9 The Assign and Configure Transmux Resources procedure is complete.
Continue to the next procedure: Configure Optical Transmux Services,
page 5-30.

Configure Optical Transmux Services
Configure Use this procedure to configure the optical transmux capabilities

Optical
Transmux Table 5-13 Configure Optical Transmux Services
Services
Step Procedure
1 Complete the procedure: Assign and Configure Transmux Resources,

page 5-28.
2 In Map View, double click the node that is performing optical transmux
functions.
3 Click the Service tab, then click Add to add a transmux service.
– Select SONET-STS to transform a channelized DS3 to a
VT-mapped STS.
– Select SONET-VT to be able to switch the DS1 traffic inside the
channelized DS3.
Steps 6
and 7
Steps 8
and 9
Figure 5-9 Transmux Service SLA Screen

Table 5-13 Configure Optical Transmux Services (continued)
Step Procedure

■ From the Source Node list, select the node that is transforming the
traffic.
■ From the Source Port list, select the port that originates the traffic on
the node.
■ From the Source Path list, select the correct path number.
■ From the Destination Port list, select the port terminates the traffic on
the node.
■ From the Destination Path list, select an available starting path
number.
8 If this is a SONET-STS service, enter the transmux information for the
service:
■ Source DS3 Mapping: Select this parameter if the source STS carries
a channelized DS3 payload.
■ TMX Port: Select the port you designated as the STS1TMX resource.
■ Destination DS3 Mapping: Select this parameter if the destination
STS carries a channelized DS3 payload.
9 If this is a SONET-VT service, enter the transmux information for the
service:
■ Source DS1 Mapping: Select this parameter if the source STS carries
a channelized DS3 payload.
■ Destination DS1 Mapping: Select this parameter if the destination
STS carries a channelized DS3 payload.
10 Repeat Steps 2–9 for each optical transmux service
services.
12 The Configure Optical Transmux Services procedure is complete.


Chapter 4
Creating Services on Overlapping UPSRs
Introduction This chapter explains how to create path-protected bidirectional services in a 2-node
overlapping ring configuration.
■ Services on Overlapping UPSRs, page 5-33.
■ Example of a Bidirectional Protected STS Path, page 5-34.
■ Example of Bidirectional Protected DS1 and VT Services, page 5-35.
■ Modules Required at Interconnecting Nodes, page 5-36.
■ Before You Create Services on Overlapping Rings, page 5-36.
■ Guidelines to Provision Services on Overlapping Rings, page 5-37.
■ Procedures Required to Provision Services on Overlapping Rings, page 5-37.
Services on Overlapping ring configurations use the same two or more nodes in separate ring
Overlapping topologies.
UPSRs To provision services in an overlapping ring configuration, create a combination of the
following services at different nodes in the network.
■ Add Service: This service can be any one of the supported service types. Create
this type of service at each node that adds traffic to both of the overlapping rings.
■ Pass Through Service: This service is a SONET-STS service that passes the
traffic though the node. Create this type of service at all intermediate nodes in the
overlapping ring configuration that do not add or drop traffic.
■ Drop Service: This service drops traffic from one ring to the other. Create this
service at each interconnecting node (a node that is a member of both ring
configurations).
■ Continue Service: This service carries the traffic to the next interconnecting node.
After you have dropped traffic at the first interconnecting node, continue the signal
around to the next interconnecting node to create an alternative path for the traffic.
Create this service at each interconnecting node.

Example of a Bidirectional Protected STS Path
Example of a To create a protected bidirectional STS path across two overlapping rings, you have to
Bidirectional create a series of SONET-STS services at each node. In the following example, traffic
Protected STS enters each ring at Node A and Node D and is bridged in both directions around each
Path ring.
working signal.
In this example, the traffic from Node A (working) travels to the interconnecting node
(INCT Node 1) in the clockwise direction. The traffic added at Node D also travels in
the clockwise direction to INCT Node 2.
8
7
10
At Node A (1) and Node D (2):

Service Type: SONET-STS (Add) 9 6
Directionality: Bidirectional 5
Working Protect
At Node B (3) and Node C (4) W E W E
1 4
Service Type: SONET-STS (Pass Through)
E W
Directionality: Bidirectional
Protection Type: Unprotected W E
At PRI Node 1 (5, 6, 7, and 8) GCM GCM

5. Service Type: SONET-STS (Drop) W OC48 OC48 OC48 OC48 E
Node A Node C
Resource Advisory: OFF Slot 1 Slot 2 Slot 15 Slot 16
Directionality: Unidirectional E INCT Node 1 W
At PRI Node 1 (9 and 10) Ring 1 Ring 2

Service Type: SONET-STS (Continue) OC-48 UPSR OC-48 UPSR
Resource Advisory: OFF
14
Directionality: Unidirectional
13
Protection Type: 1+1 Path Protected W E 16
At PRI Node 2 (11, 12, 13, and 14) 3 2

E 12 W
5. Service Type: SONET-STS (Drop) 15
Resource Advisory: OFF 11
Directionality: Unidirectional E W
W E
At PRI Node 2 (15 and 16) Node B
W E W E Node D
Protect Working
Service Type: SONET-STS (Continue)
Protection Type: 1+1 Path Protected
GCM GCM
OC48 OC48 OC48 OC48
INCT Node 2
Figure 5-10 Bidirectional Protected STS Paths in Overlapping PRI
In this example, use a series of SONET-STS services at each node to create a

bidirectional protected path for STS traffic across both rings.
At Node A and Node D, create a service that adds traffic to both rings. Tag the services
as UPSR protected to bridge the signal in both directions around the ring.
At every intermediate node, create a pass through service that simply passes the traffic
through the node.
At each of the interconnecting nodes, create a series of unidirectional services to drop
the traffic from one ring to the other. Bridge each signal (forward working and forward
protect) to both the East and West ports of the other ring to create alternate paths.

Chapter 4 Creating Services on Overlapping UPSRs
Example of Bidirectional Protected DS1 and VT Services
Example of In the following example, DS1 traffic enters each ring at Node A and Node D and is
Bidirectional bridged in both directions around each ring. The traffic from Node A (working) travels
Protected DS1 to INCT Node 1 in the clockwise direction. The traffic added at Node D travels in the
and VT clockwise direction to INCT Node 2.
Services
8
7 10
At Node A (1) and Node D (2):

Service Type: DS1-Mux-VT (Add) 9 6
Directionality: Bidirectional 5
Working Protect
At Node B (3) and Node C (4): 1 4
W E W E
Service Type: SONET-STS (Pass Through)
E
Directionality: Bidirectional W E W
At PRI Node 1 (5, 6, 7, and 8)

W Node A VT VT GCM GCM Node C E
Service Type: SONET-VT (x 28) (Drop)
OC12 OC12 Switch Switch OC48 OC48
Protection Type: UPSR Ingress E INCT Node 1 W
At PRI NODE 1 (9 and 10): Ring 1 Ring 2
Service Type: SONET-STS (Continue) OC-48 UPSR OC-48 UPSR
Directionality: Unidirectional 14
Protection Type: Unprotected 13 16
W E
At PRI Node 2 (11, 12, 13, and 14) E 3 2 W
Service Type: SONET-VT (x 28) (Drop)
12
Resource Advisory: OFF 15
Directionality: Unidirectional 11
Protection Type: UPSR Ingress E W E
W
Node B Node D
At PRI NODE 2 (15 and 16): W E W E
Service Type: SONET-STS (Continue) Protect Working
VT VT GCM GCM
OC12 OC12 Switch Switch OC48 OC48
INCT Node 2
Figure 5-11 Bidirectional DS1 and VT Services in Overlapping Rings
In this example, create a combination of DS1-Mux-VT services, SONET-STS services,

and SONET-VT services to create a bidirectional path for DS1 channels across the
rings. At Node A and Node D, create a DS1-Mux service that adds traffic to both rings.
Tag the services as UPSR protected to bridge the signal in both directions around the
ring.
At every intermediate node, create a pass through service that simply passes the traffic
through the node.
At each of the interconnecting nodes, create a series of unidirectional services to drop
the traffic from one ring to the other. The incoming signal is a VT-mapped STS. Use a
SONET-VT service to drop VTs to the second ring. Use a SONET-STS service to
continue the VT-mapped STS to the next node to create an alternate path for the DS1
traffic.

Modules Required at Interconnecting Nodes
Modules This table lists the Traverse modules required at the interconnecting nodes. Other nodes
Required at require modules depending on tributary services.
Interconnecting
Nodes Table 5-14 Modules Required at the Interconnecting Nodes
SONET-STS OC-N OC-N
SONET-VT OC-N OC-N
Other modules
VT Switch (for SONET-VT n/a n/a

services only)
Before You Review the information in this topic before you create services on overlapping rings.
Create Table 5-15 Protected Ring Interconnection in Overlapping Rings
Services on
Overlapping Requirement Reference
Rings
Hardware
See Modules Required at Interconnecting Volume 1, General Information,

Nodes, page 5-36. Section 2—Hardware Descriptions.
Hardware is installed in an overlapping ring n/a

configuration.
Software


■ Each ring in the configuration is configured Protection Groups.
as a UPSR.
■ Electrical tributary modules are configured in
an equipment protection group.
■ VT/VC Switch modules are configured in an
equipment protection group.
■ Tributary facilities are configured in a 1+1
APS protection group.
All source and destination interfaces are Volume 3, Provisioning, Section 1, Chapter
configured correctly. 4—“Port Configuration,” page 1-23.
These procedures describe how to create See Volume 3, Provisioning, Section 3—Creating
bidirectional paths over overlapping rings. These Services for detailed procedures on all service types.
procedures address relevant parameters only. See Volume 5, TransNav Management System,
Section 5—Services for descriptions of other fields
on screen.

Procedures Required to Provision Services on Overlapping Rings
Table 5-15 Protected Ring Interconnection in Overlapping Rings (continued)

■ All Traverse Service Types, page 3-5.

Guidelines to The guidelines to create services in an overlapping ring configuration are:

Provision ■ Create and activate all services on one node before you move to the next.
Services on ■ At the interconnecting nodes, create the Drop services first, then create the
Overlapping Continue services.
Rings ■ Turin recommends that the bidirectional path use the same path number at each
node in both rings.
■ Because the Resource Advisory function is turned OFF for the Drop and
Continue procedures, be sure to know the available resources from your network
plan.
Procedures To provision services across overlapping rings, you must create a combination of
Required to service types at different nodes in the network. Use the following procedures to help
Provision you provision services in an overlapping ring configuration:
Services on 1. Create an Add Service, page 5-38. This service can be any one of the supported
Overlapping service types. See Section 3—Creating Services for detailed procedures on
Rings creating a Traverse service. Create this type of service at each node that adds
services to both of the overlapping rings.
2. Create a Pass Through Service, page 5-39. This service is a SONET-STS service
that passes the traffic though the node. Create this type of service at all
intermediate nodes in the overlapping ring configuration that do not add or drop
traffic.
3. Create a Drop Service, page 5-40. This service drops traffic from one ring to the
other. Create this service for each forward working and forward protecting signal at
each interconnecting node (a node that is a member of both ring configurations).
4. Create a Continue Service, page 5-42. This service carries the traffic to the next
interconnecting node. After you have dropped traffic at the first interconnecting
node, continue the signal around to the next interconnecting node to create an
alternative path for the traffic. Create this service for each forward working and
forward protecting signal at each interconnecting node.
5. Activate a Service, page 3-17. Create and activate services at one node before you
move on to the next.

Create an Add Service
Create an Add Perform this procedure at each node that adds traffic to each ring.
Service
Table 5-16 Create an Add Service
Step Procedure
1 Review the information in Before You Create Services on Overlapping

Rings, page 5-36.
2 Complete the procedure: Configure General Information, page 3-13.
This service can be any one of the supported service types. See
Section 3—Creating Services for detailed procedures on creating a
Traverse service.
3 Click Next to continue to the Service Level Agreement screen and enter
the characteristics of the service (Steps 4 and 5).
4 The source information (Source Node, Source Port, etc.) depends on the
service type. See Section 3—Creating Services for detailed procedures on
provisioning different service types in a Traverse network.
in Step 4.
■ From the Destination Port list, select the East port of UPSR ring.
■ From the Destination Path: Turin recommends that the path is
consistent across each node in the configuration.
Select the remaining destination information as required by the service
type. See Section 3—Creating Services for detailed procedures.
6 Click Next to continue to the Transport screen and set the characteristics
for the transport of this service (Steps 7 to 8).
7 In the Directionality parameter, select Bi-Directional to create a
bidirectional path for this service.
8 From the Protection Type list, select UPSR Protected to bridge the traffic
in both directions around the ring.
9 Click Finish to return to the service list on the Service tab.
10 Complete the procedure: Activate a Service, page 3-17 for this service.
11 Repeat Steps 2 to 10 at each node that adds services to each ring.
12 The Create an Add Service procedure is complete.
Continue to the procedure: Create a Pass Through Service, page 5-39.

Create a Pass Through Service
Create a Pass Perform this procedure at each intermediate node in the overlapping ring configuration.
Through
Service Table 5-17 Create a Pass Through Service
Step Procedure
1 Complete the procedure: Create an Add Service, page 5-38.

this service.
Select SONET-STS as the service type.
3 Click Next to continue to the service level agreement screen and enter the
characteristics of the service (Steps 4 and 5).
4 Enter the source information.
■ From the Source Node list, select an intermediate node in the ring.
■ From the Source Path list, select the same path number onto which
you added the traffic in the Create an Add Service procedure.
5 Enter the destination information.
in Step 4.
■ From the Destination Port list, select the other trunk port. For
example, if you selected the East Port in Step 4, select the West Port
for this destination.
■ From the Destination Port list, From the Destination Path list, select
the path number onto which you added the traffic in the Create an Add
Service procedure.
6 Click Next to continue to the transport screen.
7 In the Directionality parameter, select Bi-Directional to create a
bidirectional path for this service.
10 Repeat Steps 2 to 9 at each intermediate node on each ring.
11 The Create a Pass Through Service procedure is complete.
Continue to the procedure: Create a Drop Service, page 5-40.

Create a Drop Service
Create a Drop Perform this procedure for each forward working and forward protecting signal at each
Service interconnecting node.
Table 5-18 Create a Drop Service
Step Procedure
1 Complete the procedure: Create a Pass Through Service, page 5-39.

this network.
– Select SONET-STS to create a bidirectional STS path across the
overlapping rings.
– Select SONET-VT to create a bidirectional VT path across the
overlapping rings.
characteristics of the service (Steps 5 to 9).
5 Enter the source and destination information for this service.
■ If this is a SONET-STS service, see Figure 5-10 Bidirectional
Protected STS Paths in Overlapping PRI, page 5-34 for clarification of
the sources and destinations of this service. Go to Step 6.
■ If this is a SONET-VT service, see Figure 5-11 Bidirectional DS1 and
VT Services in Overlapping Rings, page 5-35 for clarifications of
sources and destinations of this service. Go to Step 8.
6 If this is a SONET-STS service, drop the forward working and forward
protecting signals from one ring to the other.
■ From the Source Node list, select an interconnecting node.
Service from the ring. In the forward working direction, this port is the
West port. In the forward protecting direction, this port is the East
port.
Remember that you must create two separate services to drop the
signal from one ring to the other. Use the same source for both
services.

Create a Drop Service
Table 5-18 Create a Drop Service (continued)
Step Procedure
7 For this SONET-STS service, enter the destination information for this
service:
in Step 6.
■ From the Destination Port list, select a trunk port on the second ring.
Remember that you must create two separate services to drop the
signal from one ring to the other: From the same source to both the
East and West ports on the second ring.
8 If this is a SONET-VT service, drop the forward working and the forward
protecting signals from one ring to the other.
Service from the ring. For the forward working signal, select the West
port. For the forward protecting signal, select the East port.
■ From the Source VT list, select the correct VT.
9 For this SONET-VT service, enter the destination information.
in Step 8.
■ From the Destination Port list, select the correct West or East port for
the each ring. See Figure 5-11, page 35.
■ From the Source VT list, select the correct VT.
for the transport of this service (Steps 11 to Steps 12).
11 In the Directionality parameter, select Unidirectional to create a
unidirectional path for this service. You create four unidirectional paths for
both the Forward Working and Forward Protect signals from both rings.
12 Set the protection attributes for this service.
■ If this is a SONET-STS service, select Unprotected from the
Protection Type list.
■ If this is a SONET-VT service, select UPSR Ingress from the
Protection type list.

Create a Continue Service
Table 5-18 Create a Drop Service (continued)
Step Procedure
15 Repeat Steps 2 to 14 for each Drop service required for this configuration.
16 The Create a Drop Service procedure is complete.
Continue to the procedure: Create a Continue Service, page 5-42.
Create a Perform this procedure for each forward working and forward protecting signal at each
Continue interconnecting node.
Service
Table 5-19 Create a Continue Service
Step Procedure
1 Complete the procedure: Create a Drop Service, page 5-40.

this network.
■ From the Service Type list, select SONET-STS.
characteristics of the service (Steps 5 to 8).
5 For a bidirectional SONET-STS path across the interconnecting rings,
continue the dropped signal around the second ring (Figure 5-10, page 34):
■ From the Source Port list, select the port that receives signal from the
first ring. In the forward working direction, this port is the East port. In
the forward protecting direction, this port is the West port.
6 For a bidirectional SONET-STS path, enter the destination information:
in Step 5.
■ From the Destination Port list, select the other trunk port on the same
ring to continue the signal around the ring.

Table 5-19 Create a Continue Service (continued)
Step Procedure
7 For a VT-mapped SONET-STS signal, enter the source information for this
service (Figure 5-11, page 35):
Service from the ring. In the forward working direction, this port is the
West port. In the forward protecting direction, this port is the East
port.
8 For this VT-mapped SONET-STS signal, enter the destination information
for this service:
in Step 7.
■ From the Destination Port list, select the other trunk port on the same
ring to continue the signal to the next interconnecting node.
for the transport of this service (Steps 11 to Steps 12).
10 In the Directionality parameter, select Unidirectional to create a
unidirectional path for this service. You create four unidirectional paths for
both the Forward Working and Forward Protect signals from both rings.
11 Set the protection attributes for this service.
■ If this is a SONET-STS service, select 1+1 Path Protection from the
Protection Type list.
■ If this is a VT-mapped STS service, select Unprotected from the
Protection type list.
14 Repeat Steps 2 to 13 for each Continue service required for this
configuration.
15 The Create a Continue Service procedure is complete.


Chapter 5
Creating Transparent Services Procedures
Introduction This chapter explains how to create a transparent service in a Traverse network.
■ Example of Transparent Services, page 5-46.
■ Modules Required to Create a Transparent Service, page 5-47.
■ Before You Create a Transparent Service, page 5-47.
■ Guidelines to Provision Transparent Services, page 5-48.
■ Procedures Required to Create a Transparent Service, page 5-48.
■ Disable Control Data Procedure, page 5-48.
■ Provision the Transparent Service Procedure, page 5-49.

Example of Transparent Services
Example of A transparent service transports incoming SONET payload and the transport overhead
Transparent through the Traverse system. In the transparent multiplexing application, the tributary
Services connections and fiber span between the Traverse nodes are unprotected. The
subtending third party vendor equipment provides all protection switching and
bandwidth management.
Create a service from each port connected to the third party equipment.
Control Data = Disabled Control Data = Disabled
1. 3. 5.
2. 4. 6.
OC48 OC48 OC192 OC192 OC192 OC192 OC192 OC192 OC192 OC192 OC48 OC48
Slot 1 Slot 2 Slot 11 Slot 13 Slot 1 Slot 3 Slot 11 Slot 13 Slot 1 Slot 3 Slot 13 Slot 14
Node 1 Node 2
1. Service Type = SONET-STS 3. Service Type = SONET-STS 4. Service Type = SONET-STS
Src: Node 1/slot-2/port-1/sts-1 Src: Node 1/slot-3/port-1/sts-1 Src: Node 2/slot-3/port-1/sts-1
Dest: Node 1/slot-11/port-1/sts-1 Dest: Node 1/slot-11/port-1/sts-1 Dest: Node 2/slot-13/port-1/sts-1
Bandwidth = 48c Bandwidth = 48c Bandwidth = 48c
Transparency = ON Transparency = ON Transparency = ON
3rd party vendor equipment 3rd party vendor equipment
OC-48 (working) OC-48 (working)
2. Service Type = SONET-STS 4. Service Type = SONET-STS 3. Service Type = SONET-STS

Src: Node 1/slot-1/port-1/sts-1 Src: Node 1/slot-1/port-1/sts-1 Src: Node 2/slot-1/port-1/sts-1
Dest: Node 1/slot-13/port-1/sts-1 Dest: Node 1/slot-13/port-1/sts-1 Dest: Node 2/slot-14/port-1/sts-1
Bandwidth = 48c Bandwidth = 48c Bandwidth = 48c
Transparency = ON Transparency = ON Transparency = ON
3rd party vendor equipment 3rd party vendor equipment
OC-48 (protecting) OC-48 (protecting)
Figure 5-12 Transparent SONET Service
In the above example, create a series of SONET-STS services, two at each node. The
Control Data parameter is disabled at any SONET port connected to third party
equipment. The transparency flag is turned ON for each SONET-STS service. The
remaining bandwidth on the OC-192 can be used for additional tributary services such
as DS3-CC, DS3-TMX, other SONET-STS, or Ethernet.

Chapter 5 Creating Transparent Services Procedures
Before You Create a Transparent Service
Modules This table lists the Traverse modules required to create a transparent services.
Required to
Create a Table 5-20 Modules Required for Transparent Services
Transparent
Service
SONET-STS OC-12 OC-48
OC-48 OC-192
Before You Review the information in this topic before you create a transparent service.
Create a
Transparent Table 5-21 Transparent Service Requirements
Service
Hardware
See Modules Required to Create a Transparent Volume 1, General Information,

Service, page 5-47. Section 2—Hardware Descriptions.
Volume 3, Provisioning, Section 3—Creating
Services.
Software




■ SONET-STS Traverse Service Types, page 3-5.


■ SONET-STS: 48.960 Mbps. Transport Capacity, page 3-3.
Guidelines. See Guidelines to Provision Transparent

Services, page 5-48 in this chapter.

Guidelines to Provision Transparent Services
Guidelines to The guidelines to provision a transparent service are:

Provision ■ For protected configurations, there must be two tributary and two trunk modules on
Transparent each node transporting the transparent service.
Services ■ You can use the following combinations interfaces in a transparent service:
– OC-12 tributary and OC-48 trunks.
– OC-48 tributary and OC-192 trunks.
■ The Traverse supports transparent services over a OC-192 linear chain.
■ There can be no other services provisioned on the tributary card.
■ The remaining bandwidth on the OC-192 can be used for additional services such
as DS3-CC, DS3-TMX, other SONET-STS, or Ethernet.
■ The tributary connections and fiber span between the Traverse nodes are
unprotected. The subtending third party equipment provides all protection
switching and bandwidth management.
Procedures Use the following procedures to help you provision transparent services on a Traverse
Required to system.
Create a 1. Disable Control Data Procedure, page 5-48.
Transparent 2. Configure General Information, page 3-13.
Service 3. Provision the Transparent Service Procedure, page 5-49.
■ Section 3, Chapter 5,” Create a SONET-STS Service.
Disable Use the following procedure to disable the Control Data parameter on the SONET
Control Data interface.
Procedure
Table 5-22 Disable the Control Data
Step Procedure
1 Double-click the first node to display Shelf View.

2 Click the port that is connected to third party equipment, then click the
Config tab to display the Port Configuration screen.
3 From the Control Data parameter, select Disabled.
4 Click Apply to save the changes.
5 Repeat Steps 1 to 4 at the second node.
6 The Disable the Control Data procedure is complete.
Continue to the next procedure, Provision the Transparent Services.

Chapter 5 Creating Transparent Services Procedures
Provision the Transparent Service Procedure
Provision the Use this procedure to provision a transparent service.

Transparent
Service Table 5-23 Provision the Transparent Services
Procedure
Step Procedure
1 Complete the procedure, Disable the Control Data, page 5-48.

this service.
3 On the Define Service—Service Level Agreement Screen set the
characteristics of this service (Steps 4 to 6).
4 From the Bandwidth parameter:
■ Select STS-3c if this is an OC-12 interface.
■ Select STS-48c if this is an OC-48 interface.
originates.
■ From the Source Port list, select the port that is connected to the third
party equipment.
■ From the Source Path list, select 1.
in Step 5. (For transparent services, the source and destination ports
are on the same node.)
■ From the Destination Port list, select the correct trunk card on the
node.
■ From the Destination Path list, select the destination path for this
service.
8 Select ON from the Transparency list to turn on the transparency flag.
Service tab.
11 Repeat Steps 1–10 for each service in the transparent application.
12 The Provision the Transparent Services procedure is complete.
service.

Provision the Transparent Service Procedure

S ECTION 6 A PPENDICES
S ECTION 6APPENDICES
Contents
Appendix A
Provisioning Checklists
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1
Before You Start Provisioning Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
Node and Timing Configuration Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3
Module Configuration Checklist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4
Protection Group Configuration Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5
Port Configuration Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6
Service Creation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7
Appendix B
Services Sources and Destination
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-9
DS1 Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-10
DS3 Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-11
Ethernet Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-12
SONET Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-13
List of Tables
Table 6-2 Node and Timing Configuration Checklist. . . . . . . . . . . . . . . . . . . 6-3
Table 6-3 Module Configuration Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4
Table 6-4 Protection Group Configuration Checklist . . . . . . . . . . . . . . . . . . . 6-5
Table 6-5 Port Configuration Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6
Table 6-6 Service Creation Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7
Table 6-9 Sources, and Destinations for Ethernet Services . . . . . . . . . . . . . 6-12
Table 6-10 Sources, and Destinations for SONET Services. . . . . . . . . . . . . . 6-13

Volume 3 Section 6 Appendices

Appendix A
Provisioning Checklists
Introduction Use the checklists in this appendix to bring a Traverse network into service and to
create services for transport over the network using the TransNav management system
graphical user interface (GUI).
■ Node and Timing Configuration Checklist, page 6-3.
■ Module Configuration Checklist, page 6-4.
■ Protection Group Configuration Checklist, page 6-5.
■ Port Configuration Checklist, page 6-6.
■ Service Creation Checklist, page 6-7.
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 Volume 3, Provisioning.

Volume 3, Section 6: Appendices
Before You Start Provisioning Procedures
Start
Provisioning Table 6-1 Before Provisioning Your Network Requirements
Procedures
Hardware
Software

is initialized and started. Section 1—Overview, Installation and
Administration.
Section 2—GUI Overview, Start Up, and
Administration, Chapter 1—“Starting the Graphical
User Interface,” page 2-1.


Appendix A Provisioning Checklists
Node and Timing Configuration Checklist
Node and Use this checklist as a guide to more detailed procedures. Each step references the
Timing relevant detailed procedure.
Configuration
Checklist Table 6-2 Node and Timing Configuration Checklist
Step Description and Procedure Reference ✔

1 Review the information in Before You Start Provisioning
Procedures, page 6-2 before you start with this checklist.
2 Arrange Node(s) in Map View. The GUI opens in Map View.
Traverse 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 Configure Node Parameters, page 1-3.
5 Configure External Timing. Set the BITS interface sources for
the head-end node.
See Configure External Timing, page 1-10.
6 Configure Line Timing. Set the timing options in other
network nodes.
See Configure Line Timing, page 1-14.
7 Configure Derived References (optional). Provide a timing
reference from a line interface and send it to an external clock.
See Configure Derived References, page 1-15.
8 Repeat Steps 3 to Steps 7for each node in the network.
9 All Node and Timing Configuration Checklist steps are complete.
Continue to the Module Configuration Checklist, page 4 checklist.

Module Configuration Checklist
Module Use this checklist as a guide to more detailed procedures. Each step references the
Configuration relevant detailed procedure.
Checklist
Table 6-3 Module Configuration Checklist

1 Complete the Node and Timing Configuration Checklist, page 3.
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 module, then
click the Config tab to display the Module Configuration screen.
See Section 1, Chapter 3—“Module Configuration” for details on
specific modules.
4 Repeat Step 3 for each module in the node.
5 Repeat Steps 2 and 4 for each node in the network.
6 All Module Configuration Checklist steps are complete.
Continue to the Protection Group Configuration Checklist, page 5.

Protection Group Configuration Checklist
Protection Use this checklist as a guide to more detailed procedures. Each step references the
Group relevant detailed procedure. Complete each item as required for your network
Configuration configuration.
Checklist
Table 6-4 Protection Group Configuration Checklist

1 Complete the Module Configuration Checklist, page 4.
2 Create Equipment Protection Groups for Tributary
Modules. For each tributary card, create an equipment protection
group.
See Section 2, Chapter 2—“Create an Equipment Protection
Group”.
3 Create 1+1 APS Groups for Tributary OC-N Modules. For
each tributary OC-N port, create a facility protection group.
See Section 2, Chapter 3—“Create a 1+1 APS Protection Group”.
4 Create 1+1 Protection Group for Trunk Modules. For a
point-to-point network, create a 1+1 APS protection groups for
trunk links.
See Section 2, Chapter 3—“Create a 1+1 APS Protection Group”.
5 Create UPSR Topology. For a path-protected ring network,
create a UPSR ring topology.
See Section 2, Chapter 6—“Create a UPSR Protection Group”.
6 Create a BLSR Topology. For a line-protected ring network,
create a BLSR topology.
See Section 2, Chapter 4—“Create a BLSR Protection Group”
7 All Protection Group Configuration Checklist steps are complete.
Continue to Port Configuration Checklist, page 6.

Port Configuration Checklist
Port Use this checklist as a guide to more detailed procedures. Each step references the
Configuration relevant detailed procedure. Complete the steps as required based on the modules
Checklist installed in and TransAccess 100 Mux connected to the node.
Table 6-5 Port Configuration Checklist

1 Complete the Protection Group Configuration Checklist, page 5.
2 In Shelf View, click any port, then click the Config tab.
3 On the Port Configuration screen, change any default values for
any configurable parameter.
See Section 1, Chapter 4—“Port Configuration” for details on all
configurable port parameters.
If this is a SONET interface, configure parameters only on the
working port if the port is part of a protection group. Parameters on
a protecting port are automatically set to the same values as the
working port.
If this is an electrical interface, Configure parameters only on
working modules if a module is configured as part of a protection
group. Parameters on a protecting module are automatically set to
the same values as the working module.
4 Add TransAccess 100 Mux. The management system does not
autodiscover TransAccess 100 Mux connected to EC-1 ports.
Complete the following steps to add a TransAccess 100 Mux to the
user interface:
■ Switch a DS3 port to EC-1
■ Configure the EC1 port.
■ Add TransAccess 100 Mux to the user interface
■ Change TransAccess 100 Mux parameters.
■ Configure TransAccess 100 Mux DS1 channels.
See Section 1, Chapter 5—“TransAccess 100 Mux Configuration”
for complete information on the TransAccess 100 Mux.
5 Click the Lock icon, located in the lower left corner of the screen, to
unlock the port and monitor potential problems.
6 Click Apply to save the changes.
7 Repeat Steps 1 to 6 at each node in the network.
8 All Port Configuration Checklist steps are complete.
Continue to Service Creation Checklist, page 7.

Service Creation Checklist
Service Configuring services on a node or through a network is a process of provisioning

Creation attributes of the service in four screens then activating the service. The Traverse
Checklist supports a number of service types.
See Section 3—Creating Services for detailed information on creating specific
services.
Table 6-6 Service Creation Checklist

1 Add the Service. On the Service tab, click Add.
2 Configure General Information. Select the service type from
the drop-down menu and configure the general information
parameters. Click Next to go to the Service Level Agreement
screen.
3 Configure the Service Characteristics. Set service
characteristics for this service. The primary requirement is to
select the source (where the service originates) and the destination
(where the service terminates).
Click Next to go to the Transport screen.
4 Configure the Attributes of the Transport Path. Set the
attributes of the transport path for the service in the transport
screen. On this screen, the primary requirement is to set the
protection attributes.
Click Next to go to the Constraints screen.
5 Set the Constraints. If the value in the Setup Type parameter
on the General Information screen for the service is Strict,
explicitly select the service route between defined endpoints.
Click Finish to add the provisioned service to the service list and
return to the service tab.
6 Activate the Service. On the Service tab, click the service to
select it and click Activate.

Service Creation Checklist

Appendix B
Services Sources and Destination
Introduction This appendix summarizes the valid source and destination information for each
supported service type on the Traverse:
■ DS1 Services, page 6-10.
■ DS3 Services, page 6-10.
■ Ethernet Services, page 6-11.
■ SONET Services, page 6-12.

DS1 Services
DS1 Services The following table lists service types and valid source and destination port types and
mapping information for creating DS1 services. For each service type, any one source
can connect to any one destination. Your network may require creating multiple
Service Type
Port Type or
Service Type
DS1 DS1 n/a DS1 n/a

DS3TMX SubPort# DS3TMX SubPort
EC1 STS-1/VTG-VT
OC-N STS/VTG-VT
DS1-Mux all ports DS1MUX n/a all ports DS1MUX n/a

DS3TMX n/a
OC-N STS
DS3 Services The following table lists service types and valid source and destination port types and
mapping information for creating DS3 services. For each service type, any one source
can connect to any one destination. Your network may require creating multiple
Service
Type Port Type or
Service Type
DS3-CC DS3CC n/a DS3CC n/a

EC1 n/a
OC-N STS
DS3-TMX DS3TMX n/a all ports n/a

DS1MUX n/a
DS3TMX STS
OC-N

Appendix B Services Sources and Destination
Ethernet Services
Ethernet The following table lists service types and valid source and destination port types and
Services mapping information for creating Ethernet services on a node. For each service type,
any one source can connect to any one destination.
Table 6-9 Sources, and Destinations for Ethernet Services
Service Type Sources Destinations
SONET-STS (EOS) ETH100FX module ETH100FX module

ETH100TX module ETH100TX module
GBE module GBE module
GE2FE16T module GE2FE16T module
GE2FE16F module GE2FE16F module
OC-N ports OC-N ports
VC-Bundle (EOS) ETH100FX module n/a

ETH100TX module
GBE module
GE2FE16T module
GE2FE16F module
Ethernet P2PDedicated ETH100FX port ETH100FX port

GBE port GBE port
SONET-STS service
VC-Bundle service
Ethernet P2PShared ETH100FX port SONET-STS service

ETH100TX port VC-Bundle service
GBE port
Ethernet IAS ETH100FX port ETH100FX port

GBE port GBE port
SONET-STS service
VC-Bundle service
Ethernet TLS ETH100FX port n/a

ETH100TX port
GBE port
SONET-STS service
VC-Bundle service

SONET Services
SONET The following table lists service types and valid source and destination port types and
Services mapping information for creating SONET services. For each service type, any one
source can connect to any one destination. Your network may require creating multiple
Table 6-10 Sources, and Destinations for SONET Services
Service Type
Port Type or
Service Type
SONET-STS1 EC1 n/a EC1 n/a

OC-N STS OC-N STS
SONET-VT1.52 EC1 STS-1/ VTG-VT DS1 (test access) n/a

OC-N STS/ VTG-VT EC1 STS-1/ VTG-VT
OC-N STS/ VTG-VT
1
Supports multicast connections for drop-and-continue applications. Also supports Ethernet over SONET
(EOS) transport.
2

I NDEX
Numerics CBIT
DS3 line format, 1-29, 5-29
1+1 path-protected
DS3T-MX line format, 1-32
create service, 5-4
Change
required procedures, 5-6
BER thesholds, 1-21
service requirements, 5-4
DCC tunnel, 1-59
DS1 mapping, 1-19
A
DS1 port parameters, 1-24
Access methods, 1-2 DS3 port parameters, 1-27
Active card, 1-52 DS3-TMX port parameters, 1-30
Add EC1 port parameters, 1-34
TransAccess 100 mux, 1-49 Ethernet port parameters, 1-38
AIS (Alarm Indication Signal) format module parameters, 1-18
DS3 port, 1-29, 5-29 port parameters, 1-34
AIS format port parameters SONET, 1-42
DS3-TMX port, 1-32 Channel, 1-55
AIS insertion Channel name, 1-55
DS1 port, 1-26 Checklist
AIS mask module configuration, 6-4
DS1 port, 1-26 node and timing configuration, 6-3
DS3 port, 1-29, 5-29 port configuration, 6-6
DS3-TMX port, 1-32 protection group configuration, 6-5
EC1 port, 1-37 provisioning, 6-1
SONET port, 1-44 service creation, 6-7
Alarm profile, 1-4, 1-52 ClearExtA, 1-52
DS1 port, 1-26 ClearExtB, 1-52
DS3 port, 1-29 Config tab
DS3-TMX port, 1-32 node, 1-4
EC1 port, 1-37 Configuration process, 1-1
Ethernet port, 1-41 Configure, 1-54
SONET port, 1-46 a TransAccess 100 mux, 1-51
Automatic switching, 1-52 derived references, 1-15
Auto-negotiation, Ethernet port, 1-40 external timing, 1-10
line timing, 1-14
B network timing guidelines, 1-8
BER node parameters, 1-3
threshold, 1-52 timing options global, 1-8
BLSR TransAccess 100 mux DS1 channels, 1-54
requirements, 2-15 Connection Admission Control (CAC), Ethernet, 4-8
BP DCN Connections timing inputs and outputs, 1-8
gateway, 1-5 Continue service provision, 5-20
IP, 1-5 Control data
mask, 1-5 disable procedure, 5-48
SONET port, 1-45
C Create
BLSR, 2-16
CAC, Ethernet, 4-8 service, 3-66
Card configuration screen, 1-18 service 1+1 path-protected, 5-4
OC-192, 1-21 service SONET-VT1.5, 3-66
Release 1.4 Turin Networks Index-1

Index
Create (continued) DS1 port

transparent service, 5-47 AIS (Alarm Indication Signal) mask, 1-26
transparent service required procedures, 5-48 AIS insertion, 1-26
transparent services, 5-45 alarm profile, 1-26
UPSR, 2-30 customer, 1-26
VC-bundle service, 4-21 line build out, 1-26
Customer line coding, 1-26
DS1 port, 1-26 line format, 1-26
DS3 port, 1-29 performance monitoring template, 1-26
DS3-TMX port, 1-32 DS1 to VT Map
EC1 port, 1-37 DS3-TMX port, 1-32, 5-29
Ethernet port, 1-41 DS1-Mux
profile, 1-55 create a service, 3-28
SONET port, 1-46 DS1-Mux-VT
service, 3-20
D DS3
DCC tunnel change port parameters, 1-27, 1-28
change, 1-59 create a service, 3-39
configuration, 1-61 port configuration screen, 1-28
example, 1-58 port requirements, 1-27
requirements, 1-59 DS3 line format
tab, 1-61 CBIT, 1-29, 5-29
DCS, 3-20 M23, 1-29, 5-29
Derived unchannelized, 1-29
references configuration, 1-15 DS3 port
timing, 1-8 AIS (Alarm Indication Signal) format, 1-29, 5-29
timing options, 1-15 AIS (Alarm Indication Signal) mask, 1-29, 5-29
Dialog boxes alarm profile, 1-29
DS port configuration, 1-18, 1-31 customer, 1-29
Ethernet port configuration, 1-39 line build out, 1-29
node configuration, 1-4 line format, 1-29, 5-29
protection rings, 2-16, 2-19, 2-32 performance monitoring template, 1-29
provision new T100, 1-49 DS3-TMX
T100 configuration, 1-51, 1-54 change port parameters, 1-30, 1-31
Do not use for synchronization (DUS) create a service, 3-46
SONET port, 1-44 port requirements, 1-30
Drop and continue service service, 3-20
DS3-TMX line format
required parameters, 5-14
CBIT, 1-32
required procedures, 5-15, 5-27, 5-37
M23, 1-32
requirements, 5-13, 5-26
DS3-TMX port
Drop service
AIS (Alarm Indication Signal) format, 1-32
provision, 5-18
AIS (Alarm Indication Signal) mask, 1-32
DS port configuration dialog box, 1-18, 1-31
alarm profile, 1-32
DS1
customer, 1-32
card configuration screen, 1-19
DS1 to VT Map, 1-32, 5-29
change port parameters, 1-25
line build out, 1-32
channel, 1-55
line format, 1-32
channel name, 1-55
performance monitoring template, 1-32
create a service, 3-23
Duplex
frame mode, 1-52
Ethernet port, 1-39
port configuration screen, 1-25
port requirements, 1-24
service, 3-20
Index-2 Turin Networks Release 1.4

Index
E Fwd Section Trc Fmt

SONET port, 1-45
EC1, 1-34
change port parameters, 1-35
G
port configuration screen, 1-35
EC1 port GCM A and GCM B
AIS (Alarm Indication Signal) mask, 1-37 gateway, 1-5
alarm profile, 1-37 IP, 1-5
customer, 1-37 mask, 1-5
line build out, 1-37 Guidelines
performance monitoring template, 1-37 network timing configuration, 1-8
requirements, 1-34 provision drop and continue service, 5-14, 5-27, 5-
SD BER (Signal Degrade Bit Error Rate), 1-37 37
SF BER (Signal Fail Bit Error Rate), 1-37
EMS I
gateway, 1-5 Integrity control
IP, 1-5 Ethernet port, 1-40
mask, 1-5
Equipped, 1-55 J
Ethernet
change port parameters, 1-38, 1-39 Jumbo frame size
create P2PD service, 4-28 Ethernet port, 1-40
create P2PS service, 4-35 Jumbo frame support
create TLS service, 4-49 Ethernet port, 1-40
IP address, 1-51
port configuration dialog box, 1-39 L
port requirements, 1-38 Line build out, 1-52, 1-55
service sources and destinations, 6-11 DS1 port, 1-26
Ethernet port DS3 port, 1-29
alarm profile, 1-41 DS3-TMX port, 1-32
auto-negotiation, 1-40 EC1 port, 1-37
customer, 1-41 Line code, 1-55
duplex, 1-39 Line coding
integrity control, 1-40 DS1 port, 1-26
jumbo frame size, 1-40 Line format
jumbo frame support, 1-40 DS1 port, 1-26
performance monitoring template, 1-41 DS3 port, 1-29, 5-29
speed, 1-39 DS3-TMX port, 1-32
transmitter state, 1-40 Line timing
Ethernet service configuration, 1-14
CAC, 4-8 timing screen, 1-14
connection admission control (CAC), 4-8 Local, 1-52
Example Location, 1-4
transparent services, 5-46 Lock icon, 1-26, 1-29, 1-32, 1-35, 1-37, 1-41, 1-46, 6-6
Ext timing ref, 1-52 Looped, 1-52
EXT timing screen, 1-10
ExtA, 1-52 M
ExtB, 1-52
M23
External timing configuration, 1-10
DS3 line format, 1-29, 5-29
F DS3-TMX line format, 1-32
Manual TX timing, 1-52
Fwd Section Trace Module configuration
SONET port, 1-45 checklist, 6-4

Index
N Procedures (continued)
change SONET port parameters, 1-43
Name, 1-49
configure a TransAccess 100 mux, 1-51
NAS (North America Standard)
configure derived references, 1-15
AIS (Alarm Indication Standard) format, 1-29, 1-32,
configure external timing, 1-10
5-29
configure general information, 3-13
Network
configure global timing options, 1-8
configuration process, 1-1
configure line timing, 1-14
Network Time Protocol IP, see NTP IP
configure node parameters, 1-3
Node
configure TransAccess 100 mux DS1 channels, 1-54
and timing configuration checklist, 6-3
control data disable, 5-48
config tab, 1-4
create a DS1 service, 3-23
configuration dialog box, 1-4
create a DS1-Mux service, 3-28
ID, 1-5
create a DS3 service, 3-39
IP, 1-5
create a DS3-TMX service, 3-46
NTP IP, 1-5
create a SONET-STS service, 3-58
create a SONET-VT1.5 service, 3-66
O
create a UPSR, 2-30
OC-192 card configuration, 1-21 create an Ethernet P2PD, 4-28
ONES AIS (Alarm Indication Signal) format, 1-29, 1-32, create an Ethernet P2PS, 4-35
5-29 create an Ethernet TLS, 4-49
create BLSR, 2-16
P create transparent service, 5-48
Parameters create transparent services, 5-45
required for drop and continue service, 5-14 create VC-bundle service, 4-21
Performance monitoring template, 1-52 DCC tunnel configuration, 1-61
DS1 port, 1-26 multiple services, 3-18
DS3 port, 1-29 provision a continue service, 5-20
DS3-TMX port, 1-32 provision a drop service, 5-18
EC1 port, 1-37 provision a source service, 5-16
Ethernet port, 1-41 provision transparent service, 5-49
SONET port, 1-46 required for drop and continue service, 5-15, 5-27,
Port configuration 5-37
checklist, 6-6 required to create 1+1 path-protected service, 5-6
screen SONET, 1-43 set constraints, 3-15
Port requirements timing configuration, 1-6
DS3-TMX, 1-30 Protection
EC1, 1-34 mode, 1-52
SONET, 1-42 rings dialog box, 2-16
Primary reference, 1-8 Protection group configuration
Procedures checklist, 6-5
activate a service, 3-17 Protection rings dialog box, 2-19, 2-32
add a service, 3-12 Provision
add TransAccess 100 mux, 1-49 a continue service, 5-20
before you start provisioning, 1-2 drop and continue service guidelines, 5-14, 5-27, 5-
change BER thesholds, 1-21 37
change DS1 mapping formats, 1-19 drop service, 5-18
change DS1 port parameters, 1-25 new T100 dialog box, 1-49
change DS3 port parameters, 1-28 source service, 5-16
change DS3-TMX port parameters, 1-31 ProvisionExtA, 1-52
change EC1 port parameters, 1-35 ProvisionExtAandB, 1-52
change Ethernet port parameter, 1-39 ProvisionExtB, 1-52
change module parameters, 1-18
Index-4 Turin Networks Release 1.4

Index
Provisioning SONET port (continued)

checklists, 1-2, 6-1 terminate DCC, 1-45
procedures before you start, 1-2 transmitter state, 1-44
PTP, 1-55 SONET service
sources and destinations, 6-12
R SONET-STS create a service, 3-58
Requirements SONET-VT1.5, 3-66
drop and continue service, 5-13, 5-26 Source service provisioning, 5-16
Rev Section Trace Sources and destinations
SONET port, 1-45 Ethernet service, 6-11
Rev Section Trc Fmt SONET service, 6-12
SONET port, 1-45 summary, 6-9
Speed Ethernet port, 1-39
S Summary
services sources and destinations, 6-9
SD BER (Signal Degrade Bit Error Rate) System access methods, 1-2
EC1 port, 1-37
line, 1-44 T
SONET port, 1-44
T100
Service
configuration dialog box, 1-51, 1-54
drop-and-continue services, 5-11
provision new dialog box, 1-49
DS1, 3-20
Terminate DCC
DS1-Mux-VT, 3-20
SONET port, 1-45
DS3-TMX, 3-20
Thresholds BER, 1-52
mode, 1-52, 1-55
Timing
sources and destinations, 6-9
configuration, 1-6
transparent service, 5-46
connections, 1-8
Service creation
example, 1-7
checklist, 6-7
global option, 1-8
Service descriptions
main timing screen, 1-13
drop-and-continue, 5-11
mode, 1-52
transparent, 5-46
screen, 1-14
SF BER (Signal Fail Bit Error Rate)
Timing tab
EC1 port, 1-37
derived timing options, 1-15
line, 1-44
EXT subtab, 1-10
SONET port, 1-44
main timing screen, 1-13
SONET
Transmitter state
change port parameters, 1-42, 1-43
port configuration screen, 1-43 Ethernet port, 1-40
port requirements, 1-42 SONET port, 1-44
SONET port Transparent service
AIS (Alarm Indication Signal) mask, 1-44 create, 5-47
alarm profile, 1-46 example, 5-46
control data, 1-45 guidelines, 5-48
customer, 1-46 provision, 5-49
Do not use for synchronization (DUS), 1-44 Tx timing, 1-52
Fwd Section Trace, 1-45
Fwd Section Trc Fmt, 1-45
U
performance monitoring template, 1-46 Unchannelized, DS3 line format, 1-29
Rev Section Trace, 1-45
Rev Section Trc Fmt, 1-45 V
SD BER (Signal Degrade Bit Error Rate), line, 1-44
VC-bundle service
SF BER (Signal Fail Bit Error Rate), line, 1-44
create, 4-21

Volume 3 - Provisioning Release 1.4 Rev A

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Volume 3 - Provisioning Release 1.4 Rev A

Uploaded by

Copyright:

Available Formats

Turin Networks Inc.

Section 1 Configuring Equipment

Section 2 Creating Protection Groups

Section 3 Creating Services

Release 1.4 Turin Networks Page i

Section 4 Creating Ethernet Services

Section 5 Provisioning Service Applications

Page ii Turin Networks Release 1.4

Introduction This description contains the following documentation topics:

Release Feature Volume Reference

1+1 Path Protection. Section 5—Provisioning Service Applications, Chapter

1:2 equipment protection. Section 2—Creating Protection Groups, Chapter 2—“Create

Ethernet transport enhancements. Section 4—Creating Ethernet Services, page 4-1.

Optical Transmux. Section 5—Provisioning Service Applications, Chapter

Overlapping Interconnecting Rings. Section 5—Provisioning Service Applications, Chapter

Resource Advisory. Section 3—Creating Services, Chapter 2—“Procedures

Transparent services over OC-192 Section 5—Provisioning Service Applications, Chapter

Release 1.4 Turin Networks Page iii

Volume Description Target Audience

Page iv Turin Networks Release 1.4

Information Traverse system documentation uses Information Mapping format. Information

Release 1.4 Turin Networks Page v

Release 1.4 Turin Networks Page vii

Change Ethernet Port Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-39

Page viii Turin Networks Release 1.4

Release 1.4 Turin Networks Page ix

Page x Turin Networks Release 1.4

Step Procedure Reference

1 Nodes are installed, connected, and Volume 2, Installation and Configuration.

2 Configure timing options for the Volume 3, Provisioning Section 1—Configuring

3 Create protection groups. Volume 3, Provisioning Section 2—Creating

4 If necessary, change the default Volume 3, Provisioning Section 1—Configuring

5 Configure each physical interface Volume 3, Provisioning Section 1—Configuring

6 Add external equipment to the user Volume 3, Provisioning Section 1—Configuring

7 Create services. Volume 3, Provisioning Section 3—Creating

Release 1.4 Turin Networks Page 1-1

Domain-level GUI. ■ Installed client application (recommended).

Domain-level CLI. ■ Telnet to management server.

Node-level CLI. ■ Local connection to node.

Nodes are commissioned. Volume 2, Installation and Configuration

Wherever possible, a table listing requirements and guidelines precedes each

Provisioning See Section 6—Appendices, Appendix A—“Provisioning Checklists” for a quick

Page 1-2 Turin Networks Release 1.4

Release 1.4 Turin Networks Page 1-3

Table 1-4 Configure Node Parameters (continued)

Figure 1-1 Node Configuration Dialog Box

Page 1-4 Turin Networks Release 1.4

Table 1-4 Configure Node Parameters (continued)

Release 1.4 Turin Networks Page 1-5

Page 1-6 Turin Networks Release 1.4

Timing Mode: External

Node 4 Timing Mode: Line Node 2 Timing Mode: Line

Timing Mode: Line

Figure 1-2 Network Timing

Release 1.4 Turin Networks Page 1-7

Guidelines to Use the following guidelines to configure timing in a Traverse network.

Step 6 Step 5 Step 7

Figure 1-3 Shelf View, Timing Tab, Main Subtab

Page 1-8 Turin Networks Release 1.4

Table 1-5 Configure Global Timing Options (continued)

3 From Timing Mode list:

Release 1.4 Turin Networks Page 1-9

1 Complete the procedure Configure Global Timing Options, page 1-8.