TransNav Management System Documentation. Graphical User Interface Reference Guide

Turin Networks Inc. TransNav Management System Documentation Graphical User Interface Reference Guide Release TN4.0.x Publication Date: January 2008 Document Number: 800-0007-TN40 Rev. B

FCC Compliance This equipment has been tested and found to comply with the limits for a Class A 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 A digital apparatus meets all requirements of the Canadian Interference-Causing Equipment Regulations. Cet appareil numérique de la classe A respects toutes les exigences du Règlement sur le matériel brouilleur du Canada. Japanese Compliance This is a Class A product based on the standard of the Voluntary Control Council for Interference by Information Technology Equipment (VCCI). If this equipment is used in a domestic environment, radio disturbance may occur, in which case, the user may be required to take corrective actions. 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 2008 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 reserves the right to revise this publication and to make changes in content from time to time without obligation on the part of Turin Networks to provide notification of such revision or change. Turin Networks may make improvements or changes in the product(s) described in this manual at any time. Turin Networks Trademarks Turin Networks, the Turin Networks logo, Traverse, TraverseEdge, TransAccess, 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.

TRANSNAV MANAGEMENT SYSTEM GUI REFERENCE GUIDE Contents About this Document........................................... v Section 1 Installation and Overview Chapter 1 Installation for Windows Workstations.............................. 1-1 Chapter 2 Installation for Solaris Workstations............................... 1-9 Chapter 3 Starting the Graphical User Interface.............................. 1-17 Chapter 4 Graphical User Interface General Description........................ 1-35 Section 2 Administrative Tasks Chapter 1 Managing Server Security....................................... 2-1 Chapter 2 Managing Node Security........................................ 2-11 Chapter 3 User Preferences............................................. 2-15 Chapter 4 Administrative Tasks........................................... 2-25 Section 3 Network Chapter 1 Creating and Deleting Equipment Using Preprovisioning............... 3-1 Chapter 2 Network Auto Discovery........................................ 3-19 Chapter 3 Node Timing................................................. 3-21 Chapter 4 DCC Tunnels................................................. 3-33 Chapter 5 Configuring IP Quality of Service................................. 3-35 Section 4 Protection Switching Chapter 1 BLSR and MS-SPRing Protection Groups.......................... 4-1 Chapter 2 UPSR and SNCP Ring Protection Groups.......................... 4-9 Chapter 3 Equipment Protection Groups.................................... 4-15 Release TN4.0.x Turin Networks Page i DRAFT

Chapter 4 1+1 MSP/APS Protection Groups................................. 4-21 Chapter 5 1+1 Path Protection Groups..................................... 4-27 Chapter 6 Carrier Ethernet Protection Pair.................................. 4-29 Chapter 7 1+1 Optimized Protection Groups................................. 4-33 Section 5 Equipment Chapter 1 Common Equipment........................................... 5-1 Chapter 2 SONET Equipment............................................ 5-7 Chapter 3 SDH Equipment............................................... 5-31 Chapter 4 Ethernet Equipment............................................ 5-49 Chapter 5 TransAccess 200 Mux.......................................... 5-73 Chapter 6 TraverseEdge 50 (TE-50)....................................... 5-79 Section 6 Services Chapter 1 Service Creation Concepts...................................... 6-1 Chapter 2 SONET Services.............................................. 6-13 Chapter 3 SDH Services................................................ 6-27 Chapter 4 Ethernet Services............................................. 6-41 Chapter 5 VC-Bundles.................................................. 6-53 Chapter 6 Service Groups............................................... 6-57 Chapter 7 Managing Services............................................ 6-61 Chapter 8 Managing Service Paths........................................ 6-71 Section 7 DCS Applications Chapter 1 DCS-384 Matrix Shelf.......................................... 7-1 Chapter 2 DCS-IO Shelf................................................. 7-15 Chapter 3 DCS-96 Shelf................................................. 7-23 Page ii Turin Networks Release TN4.0.x DRAFT

Section 8 Maintenance and Testing Chapter 1 Performance Monitoring........................................ 8-1 Chapter 2 Alarms...................................................... 8-11 Chapter 3 Events...................................................... 8-25 Chapter 4 Diagnostics.................................................. 8-37 Chapter 5 Test Access.................................................. 8-41 Chapter 6 Software Upgrades............................................ 8-47 Section 9 Appendices Appendix A Service Endpoints............................................. 9-1 Index......................................................... Index-1 Release TN4.0.x Turin Networks Page iii DRAFT

Page iv Turin Networks Release TN4.0.x DRAFT

GUI Guide [TN4.0.x] Document Description About this Document Introduction This description contains the following documentation topics: Traverse System Product Documentation, page v TraverseEdge System Product Documentation, page vi TransNav Management System Product Documentation, page vii Operations Documentation, page viii Information Mapping, page viii If You Need Help, page viii Calling for Repairs, page viii Refer to to review the new and changed features for this release. Traverse System Product Documentation The Traverse system product documentation set includes the documents described in the table below. Table 1 Traverse System Product Documentation Document Description Target Audience Traverse Product Overview Traverse Installation and Configuration Traverse Provisioning This document provides a detailed overview of the Traverse system. It also includes engineering and planning information. This document provides required equipment, tools, and step-by-step procedures for: Hardware installation Power cabling Network cabling Node power up Node start-up This document provides step-by-step procedures for provisioning a network of Traverse nodes using the TransNav management system. See the TransNav Management System Product Documentation. Anyone who wants to understand the Traverse system and its applications. Installers, field, and network engineers Network engineers, provisioning, and network operations center (NOC) personnel Release TN4.0.x Turin Networks Page v

TraverseEdge System Product Documentation TraverseEdge System Product Documentation The TraverseEdge 100 User Guide includes the sections described in the table below. Table 2 TraverseEdge 100 System Product Documentation Section Description Target Audience Product Overview Description and Specifications Installation and Configuration Provisioning the Network Configuring Equipment Creating TDM Services Creating Ethernet Services Appendices This section provides a detailed overview of the TraverseEdge system. This section includes engineering and planning information. This document identifies required equipment and tools and provides step-by-step procedures for: Hardware installation Power cabling Network cabling Node power up Node start-up This section provides step-by-step procedures for provisioning a TraverseEdge network using the TransNav management system. Also see the TransNav Management System Product Documentation. This section provides step-by-step procedures for configuring module and interface parameters of a TraverseEdge using the TransNav management system. Also see the TransNav Management System Product Documentation. This section provides step-by-step procedures for provisioning a TraverseEdge network using the TransNav management system. Also see the TransNav Management System Product Documentation. This section provides step-by-step procedures for provisioning a TraverseEdge network using the TransNav management system. See the TransNav Management System Product Documentation. This section provides installation and provisioning checklists, compliance information, and acronym descriptions. Anyone who wants to understand the TraverseEdge system and its applications Field and network engineers Installers, field, and network engineers Network engineers, provisioning, and network operations center (NOC) personnel Network engineers, provisioning, and network operations center (NOC) personnel Network engineers, provisioning, and network operations center (NOC) personnel Network engineers, provisioning, and network operations center (NOC) personnel Installers and anyone who wants reference information. Page vi Turin Networks Release TN4.0.x

TransNav Management System Product Documentation TransNav Management System Product Documentation The TransNav management system product documentation set includes the documents described in the table below. Table 3 TransNav Management System Product Documentation Document Description Target Audience TransNav Management System Product Overview TransNav Management System Server Guide TransNav Management System GUI Guide TransNav Management System CLI Guide TransNav Management System TL1 Guide This document provides a detailed overview of the TransNav management system. This document includes hardware and software requirements for the management system. It also includes network management planning information. This document describes the management server component of the management system and provides procedures and troubleshooting information for the server. This document describes the graphical user interface including installation instructions and logon procedures. This document describes every menu, window, and screen a user sees in the graphical user interface. This document includes a quick reference to the command line interface (CLI). Also included are comprehensive lists of both the node-level and domain-level CLI commands. This document describes the syntax of the TL1 language in the TransNav environment. This document also defines all input commands and expected responses for retrieval commands as well as autonomous messages that the system outputs due to internal system events. Anyone who wants to understand the TransNav management system Field and network engineers, provisioning, and network operations center (NOC) personnel Release TN4.0.x Turin Networks Page vii

Operations Documentation Operations Documentation The document below provides operations and maintenance information for Turin s TransNav managed products. Table 4 Operations Documentation Document Description Target Audience Node Operations and Maintenance This document identifies required equipment and tools. It also provides step-by-step procedures for: Alarms and recommended actions Performance monitoring Equipment LED and status Diagnostics Test access (SONET network only) Routine maintenance Node software upgrades Node hardware upgrades Field and network engineers Information Mapping If You Need Help Calling for Repairs Traverse, TransNav, and TraverseEdge 100 system documentation uses the Information Mapping format which presents information in small units or blocks. The beginning of an information block is identified by a subject label in the left margin; the end is identified by a horizontal line. Subject labels allow the reader to scan the document and 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 assistance while working with Traverse products, contact the Turin Networks Technical Assistance Center (TAC): Inside the U.S., toll-free: 1-866-TURINET (1-866-887-4638) Outside the U.S.: 916-348-2105 Online: www.turinnetworks.com/html/support_overview.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 callback basis. E-mail support (24-hour response) is also available through: support@turinnetworks.com. If repair is necessary, call the Turin Repair Facility at 1-866-TURINET (866-887-4638) for a Return Material Authorization (RMA) number before sending the unit. The RMA number must be prominently displayed on all equipment cartons. The Repair Facility is open from 6:00AM to 6:00PM Pacific Time, Monday through Friday. When calling from outside the United States, use the appropriate international access code, and then call 916-348-2105 to contact the Repair Facility. Page viii Turin Networks Release TN4.0.x

Calling for Repairs 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 TN4.0.x Turin Networks Page ix

Calling for Repairs Page x Turin Networks Release TN4.0.x

SECTION 1OVERVIEW, INSTALLATION AND ADMINISTRATION SECTION 1 INSTALLATION AND OVERVIEW Contents Chapter 1 Installation for Windows Workstations Before You Install the GUI Application.............................. 1-1 Configure Web Browser Settings for Internet Explorer.................. 1-2 Install the GUI Application on a Windows Workstation.................. 1-5 Uninstall the GUI from Windows Workstation......................... 1-7 Chapter 2 Installation for Solaris Workstations Before You Install the GUI Application.............................. 1-9 Configure Web Browser Settings for Netscape Navigator............... 1-10 Configure Window Manager Settings for Solaris....................... 1-11 Install the GUI Application on a Solaris Workstation.................... 1-12 Uninstall the GUI from a Solaris Workstation......................... 1-15 Chapter 3 Starting the Graphical User Interface Starting the GUI from the Management Server........................ 1-18 Starting the GUI Application on a Windows Platform................... 1-19 Starting the GUI Application on a Solaris Platform..................... 1-21 User Login.................................................... 1-22 Chapter 4 Graphical User Interface General Description Map View..................................................... 1-36 Shortcut Menus for Map View..................................... 1-37 Traverse Shelf View............................................ 1-39 Shortcut Menu for Shelf View..................................... 1-40 TE-100 Shelf View.............................................. 1-43 Shortcut Menu for Shelf View..................................... 1-44 GUI Menus................................................... 1-45 File Menu..................................................... 1-46 View Menu.................................................... 1-46 Alarm Menu................................................... 1-47 Events Menu.................................................. 1-47 Services Menu................................................. 1-48 Service Groups Menu........................................... 1-49 Admin Menu.................................................. 1-49 Provisioning Menu.............................................. 1-51 Help Menu.................................................... 1-51 Release TN4.0.x Turin Networks Page xv

TransNav GUI Guide, Section 1 Installation and Overview GUI Conventions............................................... 1-51 Scroll Bars.................................................... 1-51 Resizing Capabilities............................................ 1-52 List of Figures Figure 2-1 Internet Options Dialog Box, Advanced Tab................. 1-2 Figure 2-2 Internet Options Dialog Box, Security Tab.................. 1-3 Figure 2-3 Internet Explorer Security Settings........................ 1-4 Figure 2-4 TransNav GUI Splash Screen............................ 1-5 Figure 2-5 Shelf Icon on Splash Screen............................. 1-6 Figure 2-6 Windows GUI Install Wizard............................. 1-6 Figure 2-7 Windows GUI Uninstall Wizard........................... 1-7 Figure 1-8 Netscape Navigator Preferences Dialog Box................ 1-10 Figure 1-9 Solaris Style Manager Window Dialog Box................ 1-11 Figure 1-10 TransNav Management System Splash Screen.............. 1-12 Figure 1-11 Shelf Icon on Splash Screen............................. 1-13 Figure 1-12 Solaris Client Save As Dialog Box....................... 1-13 Figure 1-13 Solaris Client Download Dialog Box...................... 1-13 Figure 1-14 Solaris GUI Install Wizard............................... 1-14 Figure 1-15 Server Admin Application Start GUI...................... 1-18 Figure 1-16 GUI Login Dialog Box.................................. 1-18 Figure 1-17 Start Menu........................................... 1-19 Figure 1-18 GUI Login Dialog Box.................................. 1-20 Figure 1-19 GUI Login Dialog Box.................................. 1-21 Figure 1-20 Login Dialog Box...................................... 1-22 Figure 1-21 Login Dialog Box - Advanced Settings..................... 1-23 Figure 1-22 Map View............................................ 1-36 Figure 1-23 Map View Shortcut Menu #1............................. 1-37 Figure 1-24 Map View Shortcut Menu #2............................. 1-38 Figure 1-25 Shelf View........................................... 1-39 Figure 1-26 Shelf View Shortcut Menu #1............................ 1-41 Figure 1-27 Shelf View Shortcut Menu #2............................ 1-42 Figure 1-28 TraverseEdge 100 Shelf View............................ 1-43 Figure 1-29 Shelf View Shortcut Menu #1............................ 1-44 Figure 1-30 Shelf View Shortcut Menu #2............................ 1-45 Figure 1-31 File Menu............................................ 1-46 Figure 1-32 View Menu........................................... 1-46 Figure 1-33 Alarm Menu.......................................... 1-47 Figure 1-34 Events Menu......................................... 1-47 Figure 1-35 Services Menu........................................ 1-48 Figure 1-36 Services Groups Menu................................. 1-49 Figure 1-37 Admin Menu......................................... 1-49 Figure 1-38 Provisioning Menu..................................... 1-51 Figure 1-39 Help Menu........................................... 1-51 SECTION 1 Page xvi Turin Networks Release TN4.0.x

TransNav GUI Guide, Section 1 Installation and Overview List of Tables Table 2-1 Before You Install the GUI application (Windows)............ 1-1 Table 2-2 Set Web Browser Settings for Internet Explorer.............. 1-2 Table 2-3 Install GUI on a Windows Workstation..................... 1-5 Table 2-4 Uninstall GUI from Windows Workstation................... 1-7 Table 1-5 Before You Install the GUI application (Solaris).............. 1-9 Table 1-6 Set Web Browser Settings for Netscape Navigator........... 1-10 Table 1-7 Install GUI on a Solaris Workstation....................... 1-12 Table 1-8 Uninstall GUI from Solaris Workstation..................... 1-15 Table 1-9 Start the GUI Application from the Management Server........ 1-18 Table 1-10 Start the GUI Application on a Windows Platform............. 1-19 Table 1-11 Start the GUI Application on a Solaris Platform.............. 1-21 Release TN4.0.x Turin Networks Page xvii

TransNav GUI Guide, Section 1 Installation and Overview Page xviii Turin Networks Release TN4.0.x

SECTION 1 INSTALLATION AND OVERVIEW Chapter 1 Installation for Windows Workstations Introduction Before You Install the GUI Application You can manage a network of Traverse and TraverseEdge 100 nodes using either a Solaris or a Windows 2000 Professional platform. This chapter includes the following procedures on how to install the graphical user interface (GUI) on a Windows platform: Before You Install the GUI Application, page 1-1 Install the GUI Application on a Windows Workstation, page 1-6 Uninstall the GUI from Windows Workstation, page 1-8 See Chapter 2 Installation for Solaris Workstations, page 1-9 for the procedures to install the GUI application on a Sun Solaris workstation. To access the GUI on a computer other than the management server, install the GUI application onto the remote computer. Turin recommends installing the application directly onto the client workstation for faster initialization and operation and response time. Before you install the management server software, understand the following requirements: Table 1-1 Before You Install the GUI application (Windows) Requirement GUI application requirements Windows configuration requirements for GUI application. Support for Citrix server. Starting the GUI application Reference See the TransNav Management System Product Overview Guide, Section 2 Management System Planning, Chapter 1 TransNav Management System Requirements, page 2-1 If this is the first time you are installing the TransNav system on the workstation, use the procedure Configure Web Browser Settings for Internet Explorer, page 1-2 to configure the environment. Turin supports using the GUI application on a Citrix server. See Section 1 Installation and Overview, Chapter 3 Starting the Graphical User Interface, page 1-17 for detailed procedures on starting the GUI application Release TN4.0.x Turin Networks Page 1-1

TransNav GUI Guide, Section 1: Installation and Overview Configure Web Browser Settings for Internet Explorer Configure Web Browser Settings for Internet Explorer Before installing the GUI application or launching the applet interface, your Web browser must have the correct settings in order for the application to work properly. Use this procedure configure the browser settings for Internet Explorer. Table 1-2 Set Web Browser Settings for Internet Explorer Step Procedure 1 Open Internet Explorer. 2 From the main menu, select Tools, then Internet Options. 3 Click the Advanced tab. a. In Internet Explorer version 6.0 Update version SP1 and earlier, the following Internet Options dialog box displays. Under Microsoft VM or Java VM, ensure that Java console enabled is selected. Figure 1-1 Internet Options v6 SP1 Dialog Box, Advanced Tab In Internet Explorer version 6.0 Update version SP2 and later, in the Internet Options dialog box under Java (Sun) verify that Use JRE <release number> for <applet> (requires restart) is selected. Page 1-2 Turin Networks Release TN4.0.x

Chapter 1 Installation for Windows Workstations Configure Web Browser Settings for Internet Explorer Table 1-2 Set Web Browser Settings for Internet Explorer (continued) Step Procedure 4 On the Internet Options dialog box, click the Security tab to display the security options. Figure 1-2 Internet Options Dialog Box, Security Tab Release TN4.0.x Turin Networks Page 1-3

TransNav GUI Guide, Section 1: Installation and Overview Configure Web Browser Settings for Internet Explorer Table 1-2 Set Web Browser Settings for Internet Explorer (continued) Step Procedure 5 Select Internet or Local intranet (depending on how you are accessing the management server) and click Custom Level. The Security Settings dialog box displays. Figure 1-3 Internet Explorer Security Settings Ensure that the following options are selected: Downloads File download Enable Microsoft VM (or Java) Java permissions Custom, High safety, Low safety, or Medium safety (i.e., any setting except Disable Java) Scripting Active scripting Enable Scripting of Java applets Enable Click OK. Page 1-4 Turin Networks Release TN4.0.x

Chapter 1 Installation for Windows Workstations Configure Web Browser Settings for Internet Explorer Table 1-2 Set Web Browser Settings for Internet Explorer (continued) Step Procedure 6 Restart your computer. 7 The Set Web Browser Settings for Internet Explorer procedure is complete. Continue to the procedure Install GUI on a Windows Workstation, page 1-6. Release TN4.0.x Turin Networks Page 1-5

TransNav GUI Guide, Section 1: Installation and Overview Install the GUI Application on a Windows Workstation Install the GUI Application on a Windows Workstation Use this procedure to help you install the GUI application on a remote Windows workstation. Table 1-3 Install GUI on a Windows Workstation Step Procedure 1 Review the section Before You Install the GUI Application, page 1-1 before you start this procedure. 2 Verify that the management server is started. See Start the Server, page 2-25. 3 If this is the first time you are installing the application on this computer, complete the procedure Set Web Browser Settings for Internet Explorer, page 1-2. 4 Open your Web browser and connect to the server by entering the following address into the address window: http://server:9090 where: server is the name or IP address of the TransNav management server. The TransNav management system splash screen displays. Figure 1-4 TransNav GUI Splash Screen Page 1-6 Turin Networks Release TN4.0.x

Chapter 1 Installation for Windows Workstations Install the GUI Application on a Windows Workstation Table 1-3 Install GUI on a Windows Workstation (continued) Step Procedure 5 Click the shelf icon to start the installation of the GUI application. Figure 1-5 Shelf Icon on Splash Screen 6 The Installer Wizard displays. Figure 1-6 Windows GUI Install Wizard Follow the directions on the screen until the GUI application is installed on your computer. 7 The Install GUI on a Windows Workstation procedure is complete. Continue to the one of the procedures in Section 1 Installation and Overview, Chapter 3 Starting the Graphical User Interface, page 1-17. Release TN4.0.x Turin Networks Page 1-7

TransNav GUI Guide, Section 1: Installation and Overview Uninstall the GUI from Windows Workstation Uninstall the GUI from Windows Workstation Before installing a new version of the GUI application, you must remove the old version. On a Windows 2000 Professional platform, the uninstallation process uses a wizard similar to the Install Wizard. After you have opened the Uninstaller Wizard, follow the directions on the screen to remove the GUI application from your computer. Table 1-4 Uninstall GUI from Windows Workstation Step Procedure 1 From the Start menu, select Programs, then Turin Networks, and then Uninstall TransNav GUI. 2 The Uninstaller Wizard appears. Follow the directions on screen until the GUI application is removed from your computer. Figure 1-7 Windows GUI Uninstall Wizard 3 In an Explorer window, navigate to the directory where the application was installed. Remove the remaining files. 4 The Uninstall GUI from Windows Workstation procedure is complete. If you are in the process of a node upgrade, return to Step 3 of the procedure Upgrade Server Software, page 2-38. Page 1-8 Turin Networks Release TN4.0.x

SECTION 1INSTALLATION AND OVERVIEW Chapter 2 Installation for Solaris Workstations Introduction Before You Install the GUI Application You can manage a network of Traverse and TraverseEdge 100 nodes using either a Solaris or a Windows 2000 Professional platform. This chapter includes procedures on how to install the graphical user interface (GUI) on a Solaris platform. Before You Install the GUI Application, page 1-9 Install the GUI Application on a Solaris Workstation, page 1-12 Uninstall the GUI from a Solaris Workstation, page 1-15 See Chapter 1 Installation for Windows Workstations, page 1-1 for the procedures to install the GUI application on a Windows workstation. To access the GUI on a computer other than the management server, install the GUI application onto the remote computer. Turin recommends installing the application directly onto the client workstation for faster initialization, operation, and response time. Before you install the management server software, understand the following requirements. Table 1-5 Before You Install the GUI application (Solaris) Requirement GUI application requirements Solaris configuration requirements for GUI application. Starting the GUI application Reference See the TransNav Management System Product Overview Guide, Section 2 Management System Planning, Chapter 1 TransNav Management System Requirements, page 2-1 If this is the first time you are installing the TransNav system on the workstation, use the following procedures to configure the environment: Configure Web Browser Settings for Netscape Navigator, page 1-10 Configure Window Manager Settings for Solaris, page 1-11 See Section 1 Installation and Overview, Chapter 3 Starting the Graphical User Interface, page 1-17 for detailed procedures on starting the GUI application Release TN4.0.x Turin Networks Page 1-9

TransNav GUI Guide, Section 1: Installation and Overview Configure Web Browser Settings for Netscape Navigator Configure Web Browser Settings for Netscape Navigator Before installing the GUI application or launching the applet interface, your Web browser must have the correct settings for the application to work properly. Use this procedure to configure the browser settings for Netscape Navigator. Table 1-6 Set Web Browser Settings for Netscape Navigator Step Procedure 1 Open Netscape. 2 From the main menu, select Edit, then Preferences. 3 Click Advanced. The Preferences dialog box displays. Figure 1-8 Netscape Navigator Preferences Dialog Box Ensure that the Enable Java, Enable JavaScript, and Enable style sheets check boxes are selected. Click OK. 4 The Set Web Browser Settings for Netscape Navigator procedure is complete. Page 1-10 Turin Networks Release TN4.0.x

Chapter 2 Installation for Solaris Workstations Configure Window Manager Settings for Solaris Configure Window Manager Settings for Solaris If you are using the GUI application on a Sun Solaris workstation, the window manager settings must be properly configured to ensure that error dialog boxes pop up in front of all other windows. From your Sun workstation, select Style Manager, and then select Window to display the Style Manager Window dialog box: Clear box Figure 1-9 Solaris Style Manager Window Dialog Box Clear the Raise Window When Made Active dialog box to ensure that error dialog boxes always pop to the front of the screen. Release TN4.0.x Turin Networks Page 1-11

TransNav GUI Guide, Section 1: Installation and Overview Install the GUI Application on a Solaris Workstation Install the GUI Application on a Solaris Workstation To access the management software on a computer other than the management server, you should install the GUI application onto the remote computer. Use this procedure to help you install the GUI application on a remote Solaris workstation. Table 1-7 Install GUI on a Solaris Workstation Step Procedure 1 Review the section Before You Install the GUI Application, page 1-9 before you start this procedure. 2 Verify that the management server is started. See Start the Server, page 2-25. 3 If this is the first time you are installing the application, complete the appropriate procedure: Configure Web Browser Settings for Netscape Navigator, page 1-10 Configure Window Manager Settings for Solaris, page 1-11 4 Open a terminal window and change to the directory where you want to install the GUI application. 5 Open Netscape Navigator and connect to the management server by entering the following address into the address window: http://server:9090 where: server is the name or IP address of the TransNav management server. The TransNav management system splash screen displays. Figure 1-10 TransNav Management System Splash Screen Page 1-12 Turin Networks Release TN4.0.x

Chapter 2 Installation for Solaris Workstations Install the GUI Application on a Solaris Workstation Table 1-7 Install GUI on a Solaris Workstation (continued) Step Procedure 6 Click the shelf icon to start the installation of the GUI application. Figure 1-11 Shelf Icon on Splash Screen 7 Select the correct directory as the file location and click OK. Figure 1-12 Solaris Client Save As Dialog Box 8 The following dialog box displays indicating the download progress: Figure 1-13 Solaris Client Download Dialog Box The dialog box closes when the download is complete. 9 From a terminal window, change to the directory where you installed the setup file. Release TN4.0.x Turin Networks Page 1-13

TransNav GUI Guide, Section 1: Installation and Overview Install the GUI Application on a Solaris Workstation Table 1-7 Install GUI on a Solaris Workstation (continued) Step Procedure 10 Change the file permissions to make the installation file executable: $ chmod +x NMSGUISetup.bin 11 Execute the installation: $./NMSGUISetup.bin 12 Follow the directions on the Installer Wizard until the GUI application is installed on your computer. Figure 1-14 Solaris GUI Install Wizard 13 The Install GUI on a Solaris Workstation procedure is complete. Continue to the one of the procedures in Section 1 Installation and Overview, Chapter 3 Starting the Graphical User Interface, page 1-17. Page 1-14 Turin Networks Release TN4.0.x

Chapter 2 Installation for Solaris Workstations Uninstall the GUI from a Solaris Workstation Uninstall the GUI from a Solaris Workstation Before installing a new version of the GUI application, you must remove the old version. On a Solaris platform, the uninstallation process uses a wizard similar to the Install Wizard. After you have opened the Uninstaller Wizard, follow the directions on screen to remove the GUI application from your computer. Table 1-8 Uninstall GUI from Solaris Workstation Step Procedure 1 From a terminal window, change directories to the directory above the directory above which the GUI was installed. 2 Remove the directory and contents: rm -rf DirectoryName where: DirectoryName is the name of the directory where you installed the management system software. 3 The Uninstall GUI from Solaris Workstation procedure is complete. If you are in the process of a node upgrade, return to Step 3 of the procedure Upgrade Server Software, page 2-38. Release TN4.0.x Turin Networks Page 1-15

TransNav GUI Guide, Section 1: Installation and Overview Uninstall the GUI from a Solaris Workstation Page 1-16 Turin Networks Release TN4.0.x

SECTION 1INSTALLATION AND OVERVIEW Chapter 3 Starting the Graphical User Interface Introduction This chapter contains procedures on how to start the graphical user interface (GUI) for the TransNav management system. Starting the GUI from the Management Server, page 1-18 Starting the GUI Application on a Windows Platform, page 1-19 Starting the GUI Application on a Solaris Platform, page 1-21 User Login, page 1-22 Turin recommends using the GUI application directly on the client workstation for faster initialization, operation, and response time. For Windows workstations, see Chapter 1 Installation for Windows Workstations, page 1-1. For Solaris workstations, see Chapter 2 Installation for Solaris Workstations, page 1-9. Release TN4.0.x Turin Networks Page 1-17

TransNav GUI Guide, Section 1: Installation and Overview Starting the GUI from the Management Server Starting the GUI from the Management Server If you are going to use the GUI on the same computer you are using as a management server, the user interface applications install at the same time you install the server software. Use this procedure to start the GUI on the same computer (Windows or Solaris) that the management server is running. Table 1-9 Start the GUI Application from the Management Server Step Procedure 1 Verify the management server is started. See the TransNav Management System Server Guide, Start the Server, page 2-25. 2 In the Server Admin application, click Execution, then click Start GUI. Figure 1-15 Server Admin Application Start GUI 3 The Login dialog box displays. Figure 1-16 GUI Login Dialog Box a. Enter the correct information in the following fields: User Name: Your user name assigned by the system administrator. Default is admin. Password: Your user password assigned by the system administrator. Default is admin. Host Name: Name of the management system host. If you are running the server and client on the same system, enter localhost. b. Click Login. 4 The Start the GUI Application from the Management Server procedure is complete. Continue to the procedure Password Changes, page 2-3. Page 1-18 Turin Networks Release TN4.0.x

Chapter 3 Starting the Graphical User Interface Starting the GUI Application on a Windows Platform Starting the GUI Application on a Windows Platform To access the management software on a Windows workstation other than the management server, install the GUI application onto the remote computer (See Chapter 1 Installation for Windows Workstations, page 1-1). Use this procedure to start the GUI application on a remote computer. Table 1-10 Start the GUI Application on a Windows Platform Step Procedure 1 Verify the management server is started. See the TransNav Management System Server Guide, Start the Server, page 2-25. 2 Verify the GUI application is installed. See the procedure, Install GUI on a Windows Workstation, page 1-6. 3 From the Start menu, click Programs, Turin_Networks, then click TransNav (TM) GUI. Figure 1-17 Start Menu Release TN4.0.x Turin Networks Page 1-19

TransNav GUI Guide, Section 1: Installation and Overview Starting the GUI Application on a Windows Platform Table 1-10 Start the GUI Application on a Windows Platform (continued) Step Procedure 4 The Login dialog box displays. Figure 1-18 GUI Login Dialog Box a. Enter the correct information in the following fields: User Name: Your user name assigned by the system administrator. Default is admin. Password: Your user password assigned by the system administrator. Default is admin. Host Name: Name of the management system host. If you are running the server and client on the same system, enter localhost. b. Click Login. 5 The Start the GUI Application from the Management Server procedure is complete. Continue to the procedure, Password Changes, page 2-3. Page 1-20 Turin Networks Release TN4.0.x

Chapter 3 Starting the Graphical User Interface Starting the GUI Application on a Solaris Platform Starting the GUI Application on a Solaris Platform To access the management software on a Solaris workstation other than the management server, install the GUI application onto the remote computer. (See Chapter 2 Installation for Solaris Workstations, page 1-9.) Use this procedure to start the GUI application on a remote computer Table 1-11 Start the GUI Application on a Solaris Platform Step Procedure 1 Verify the management server is started. See the TransNav Management System Server Guide, Start the Server, page 2-25. 2 Verify the GUI application is installed. See the procedure, Install GUI on a Solaris Workstation, page 1-12. 3 In a terminal window, change to the directory where you installed the GUI application. 4 Enter the following command: $./ems_gui.sh 5 The Login dialog box displays. Figure 1-19 GUI Login Dialog Box a. Enter the correct information in the following fields: User Name: Your user name assigned by the system administrator. Default is admin. Password: Your user password assigned by the system administrator. Default is admin. Host Name: Name of the management system host. If you are running the server and client on the same system, enter localhost. b. Click Login. 6 The Start the GUI Application from the Management Server procedure is complete. Continue to the procedure Password Changes, page 2-3. Release TN4.0.x Turin Networks Page 1-21

TransNav GUI Guide, Section 1: Installation and Overview User Login User Login Turin recommends using the GUI application directly on the client workstation for faster initialization, operation, and response time. When you start the GUI, the Login dialog box displays. Figure 1-20 Login Dialog Box Enter the following information in the Login dialog box: User Name: Your user name assigned by the system administrator. Default is admin. Password: Your user password assigned by the system administrator. Default is admin. Host Name: Name of the management system host. If you are running the server and client on the same system, enter localhost. Important: For security reasons, Turin recommends that you change the default User Name and/or Password. To create a new user account, see Domain Users, page 2-6 or Node User, page 2-13. To change the Password only, see Password Changes, page 2-3. Page 1-22 Turin Networks Release TN4.0.x

Chapter 3 Starting the Graphical User Interface User Login Advanced: When this check box is selected, the advanced settings display. Figure 1-21 Login Dialog Box - Advanced Settings When the Advanced check box is selected, you can view and change the following parameters: Protocol: Select one of the following protocols: RMI (Remote Method Invocation) HTTP (Hyper Text Transfer Protocol) HTTPS (Hyper Text Transfer Protocol Secure) Port Number: Enter a port number. Notification: A notification is any change to the server database, such as new alarms or changes to configuration information. Select one of the following options: PUSH: The server automatically forwards notifications to the GUI. PULL: The GUI queries the server for new notifications every couple of seconds. Select this option if the client is located behind a firewall. Command buttons are as follows: Login: The User Name and Password combination is authenticated by the management system. Upon successful authentication, the system opens the main application window and closes the Login box. If authentication fails, you are denied access. Exit: Cancel the login attempt and close the Login box. Release TN4.0.x Turin Networks Page 1-23

TransNav GUI Guide, Section 1: Installation and Overview User Login Page 1-24 Turin Networks Release TN4.0.x

Chapter 3 Starting the Graphical User Interface User Login Release TN4.0.x Turin Networks Page 1-25

TransNav GUI Guide, Section 1: Installation and Overview User Login Page 1-26 Turin Networks Release TN4.0.x

Chapter 3 Starting the Graphical User Interface User Login Release TN4.0.x Turin Networks Page 1-27

TransNav GUI Guide, Section 1: Installation and Overview User Login Page 1-28 Turin Networks Release TN4.0.x

Chapter 3 Starting the Graphical User Interface User Login Release TN4.0.x Turin Networks Page 1-29

TransNav GUI Guide, Section 1: Installation and Overview User Login Page 1-30 Turin Networks Release TN4.0.x

Chapter 3 Starting the Graphical User Interface User Login Release TN4.0.x Turin Networks Page 1-31

TransNav GUI Guide, Section 1: Installation and Overview User Login Page 1-32 Turin Networks Release TN4.0.x

Chapter 3 Starting the Graphical User Interface User Login Release TN4.0.x Turin Networks Page 1-33

TransNav GUI Guide, Section 1: Installation and Overview User Login Page 1-34 Turin Networks Release TN4.0.x

SECTION 1INSTALLATION AND OVERVIEW Chapter 4 Graphical User Interface General Description Introduction This chapter provides a description of the navigational components of the TransNav graphical user interface (GUI). Using the GUI, you can view the network or domains you are managing (Map View) or any particular shelf (Shelf View). Context-sensitive tabs are available for the view selected. The Map View (page 1-36) displays all the nodes in a network and is the initial display when you start the GUI. The Traverse Shelf View (page 1-39) displays all the cards (modules) in a node and their associated ports. The TE-100 Shelf View (page 1-42) displays the shelf view for the TE-100. This chapter also describes the following GUI features: GUI Menus, page 1-44 GUI Conventions, page 1-51 Resizing Capabilities, page 1-52 Scroll Bars, page 1-51 Resizing Capabilities, page 1-52 Release TN4.0.x Turin Networks Page 1-35

TransNav GUI Guide, Section 1: Installation and Overview Map View Map View Map View displays all of the node groups and discovered nodes for a server when you first start the GUI from that server. From Map View, you can see and manage all the nodes, node groups, links between the nodes, and network services. The graphic area displays a background image (usually a map of physical locations of the nodes) and icons representing the nodes. This initial background image is the Network Map view. Each node group can have a different background image associated with it; this is the Group Map. Each user can group the nodes to which they have access in order to more easily manage their areas of responsibility. They can also add node groups within existing node groups. The node groups appear in the server network navigation tree. Menu bar Alarm summary tree Network navigation tree Currently selected object Contextsensitive tabs Figure 1-22 Map View The menu bar is context-sensitive. Commands display as available (highlighted) or unavailable (grayed out), depending on the selected object. The server network alarm summary tree gives you visibility at a glance to network alarms. If you select a node group, only alarms associated with that node group display. The network navigation tree shows you the node groups and node networks attached to the server in an outline format in alphanumeric order. Node groups display first, then nodes. In Map View, clicking a node group or a node displays the node group or node name on the top and bottom bars of the window. To view the nodes in a node group, double-click the Group icon in Map View or expand the node group in the navigation tree. In Shelf View, right-clicking a node in the navigation tree or double-clicking the node in Map View to display a graphical representation of the node and related information; you can see which object (card or port) you have selected by the white rectangle around the object and the name that displays on the top and bottom bars of the window. The context-sensitive tabs provide server, node group, or node information on alarms, events, configuration information, protection, services, and service groups. Page 1-36 Turin Networks Release TN4.0.x

Chapter 4 Graphical User Interface General Description Shortcut Menus for Map View Double-click a node group to display the node groups and nodes associated with it. Click a node to display node-specific information. Click anywhere on the map to display network information specific to the server. The tabs allow you to view and change the following information: Alarms: Alarms on nodes in the domain. See Section 8 Maintenance and Testing, Chapter 2 Alarms. Events: Events on nodes in the domain. See Section 8 Maintenance and Testing, Chapter 3 Events. Config: Configuration information for the selected piece of equipment. See Section 5 Equipment Configuration. Protection: Define protected rings. See Section 4 Protection Switching Performance: Monitor performance and VT/TU capacity data. See Section 8 Maintenance and Testing, Chapter 1 Performance Monitoring. Service: Define services between nodes in a domain. See Section 6 Services. Shortcut Menus for Map View Two shortcut menus are available in Map View: Right-click a node Right-click the background image When you right-click a node, the following menu displays. Note: This menu also appears if you right-click the node name in the navigation tree. Figure 1-23 Map View Shortcut Menu #1 Menu selections are: Show Shelf View: View the selected shelf (node). Delete Node: Delete the selected node (shelf). Synchronize Node: Synchronize the node with the management server so the server contains the most recent node configuration and alarms information. Release TN4.0.x Turin Networks Page 1-37

TransNav GUI Guide, Section 1: Installation and Overview Shortcut Menus for Map View Alarm Audit: Clears alarms on the node that do not exist and raises alarms that are present but not shown at the management layer. Sub Shelf: Select to access the Attach Sub Shelf menu selection, then choose to attach a TA200 or a TE50 sub shelf. When you right-click the background image, the following menu displays: Figure 1-24 Map View Shortcut Menu #2 Menu selections are: Show Network Map: Show the background map selected for the network. This option appears if node groups within the network have different background maps. Add Node: Add a node. For details, see Section 3 Network, Chapter 1 Creating and Deleting Equipment Using Preprovisioning, Add a Node. Add Link: Add a physical link between ports. See Section 3 Network, Chapter 1 Creating and Deleting Equipment Using Preprovisioning, Add a Link, page 3-15. Add Group: Create a new group of nodes or add a node to a group. Change Background: Select to change the background map. Zoom In: Zoom in on the current view. Zoom Out: Zoom out on the current view. Restore: Restore the original view. Page 1-38 Turin Networks Release TN4.0.x

Chapter 4 Graphical User Interface General Description Traverse Shelf View Traverse Shelf View Shelf View displays all of the cards in a node and their associated ports. You can navigate to Shelf View in the following ways: Click the node in Map View, then select Show Shelf View from the View menu. Double-click the node in Map View. Right-click a node in Map View and select Show Shelf View. Right-click a node name in the Navigation Tree and select Show Shelf View. Menu bar BITS clock Alarm indicators Contextsensitive tab screen Currently selected object Figure 1-25 Shelf View The menu bar is context-sensitive. Commands are displayed as available (highlighted) or unavailable (grayed out), depending on the selected object. You can see which object you have selected by the white rectangle around the object in the graphic and the name displayed on the top and bottom bars of the window. Context-sensitive tabs (in the bottom half of the screen) provide information on alarms, events, configuration information, protection, and services. In Shelf View, these tabs provide single node, card, or port information. Click a card to display card-specific information. Click a port to display port-specific information. Click an external clock to display external clock timing information. Context-sensitive tabs allow you to view and change the following information: Alarms: Alarms on the selected card or port. See Section 8 Maintenance and Testing, Chapter 2 Alarms, page 8-11. Release TN4.0.x Turin Networks Page 1-39

TransNav GUI Guide, Section 1: Installation and Overview Shortcut Menu for Shelf View Events: Events on the selected card or port. See Section 8 Maintenance and Testing, Chapter 3 Events, page 8-25. Config: Configuration information on the selected card or port. See Section 5 Equipment, page 5-1. Diagnostic: Diagnostics tests on the selected port. See Section 8 Maintenance and Testing, Chapter 4 Diagnostics, page 8-37. Timing: Timing information on the selected card or port. See Section 3 Network, Chapter 3 Node Timing, page 3-21. DCC Tunnel: Configure DCC tunnels on the node. See Section 3 Network, Chapter 4 DCC Tunnels, page 3-33. Protection: Protection groups for the node. See Section 4 Protection Switching, page 4-1. Performance: Performance monitoring data for the selected card or port and capacity monitoring data for selected VT/TU cards. See Section 8 Maintenance and Testing, Chapter 1 Performance Monitoring, page 8-1. Ethernet: Configure EOS, LAG, and Policer on the node. See Section 5 Equipment, Chapter 4 Ethernet Equipment, page 5-49. Test Access: Provides non-intrusive monitoring and intrusive split testing on digital cross-connect and add-drop multiplexer systems. See Section 8 Maintenance and Testing, Chapter 5 Test Access. Service: Services provided from the node. See Section 6 Services. You can see which object you have selected by the white rectangle around the object and the name displayed on the top and bottom bars of the window. Shortcut Menu for Shelf View Two shortcut menus are available in Shelf View. Right-click a slot not occupied by a card Right-click a slot occupied by a card When you right-click a slot not occupied by a card, the following menu displays: Figure 1-26 Shelf View Shortcut Menu #1 Page 1-40 Turin Networks Release TN4.0.x

Chapter 4 Graphical User Interface General Description Shortcut Menu for Shelf View Menu selections are: Show (Node Group) map: Show the node group (i.e., parent) map if this node is part of a node group. Show Network map: Show the map for the entire domain. Show Other Shelf View: Select another node to view in Shelf View. Add [card type] Card: Add a card to the shelf in the selected slot. Zoom In: Zoom in on the current view. Zoom Out: Zoom out on the current view. Restore: Restore the original view. When you right-click a slot occupied by a card, a different menu displays. Figure 1-27 Shelf View Shortcut Menu #2 Menu selections are: Show (Node Group) map: Show the node group (i.e., parent) map if this node is part of a node group. Show Network map: Show the map for the entire domain. Show Other Shelf View: Select another node to view in Shelf View. Delete Card: Delete the selected card. Restart Card Warm: Restart the processor on the selected card (hitless). Restart Card Cold: Restart the selected card. Replace with [card type] Cards: Replace the card selected in Shelf View with the card type selected on the shortcut menu. Zoom In: Zoom in on the current view. Zoom Out: Zoom out on the current view. Restore: Restore the original view. Release TN4.0.x Turin Networks Page 1-41

TransNav GUI Guide, Section 1: Installation and Overview TE-100 Shelf View TE-100 Shelf View When you double-click a node, you see the Shelf View which includes a network alarm summary and navigation tree on the left, a graphical version of the shelf at the top right, and context-sensitive tab screens at the bottom right. Alarm summary tree Network navigation tree Context-sensitive tab screen External Synchronization References A and B Optical Ports 1 and 2 (click for port configuration) and SFP Ports (click for SFP information) Tributary Card Ports (6 FE, 2 GbE, 3 DS3, 28 DS1) Figure 1-28 TraverseEdge 100 Shelf View See the TraverseEdge 100 User Guide for detailed information about installing and commissioning the TE-100. Page 1-42 Turin Networks Release TN4.0.x

Chapter 4 Graphical User Interface General Description Shortcut Menu for Shelf View Shortcut Menu for Shelf View Two shortcut menus are available in Shelf View: Right-click a slot not occupied by a card Right-click a slot occupied by a card When you right-click a slot not occupied by a card, the following menu displays: Figure 1-29 Shelf View Shortcut Menu #1 Menu selections are: Show (Node Group) map: Show the node group (i.e., parent) map if this node is part of a node group. Show Network map: Show the map for the entire domain. Show Other Shelf View: Select another node to view in Shelf View. Add [card type] Cards: Add a card to the shelf in the selected slot with the card type selected on the shortcut menu. Zoom In: Zoom in on the current view. Zoom Out: Zoom out on the current view. Restore: Restore the original view. Release TN4.0.x Turin Networks Page 1-43

TransNav GUI Guide, Section 1: Installation and Overview GUI Menus When you right-click a slot occupied by a card, a different menu displays. Figure 1-30 Shelf View Shortcut Menu #2 Menu selections are: Show (Node Group) map: Show the node group (i.e., parent) map if this node is part of a node group. Show Network map: Show the map for the entire domain. Show Other Shelf View: Select another node to view in Shelf View. Delete Card: Delete the selected card. Restart Card Warm: Restart the processor on the selected card (hitless). Restart Card Cold: Restart the selected card. Replace with [card type] Card: Replace the card selected in Shelf View with the card type selected on the shortcut menu. Zoom In: Zoom in on the current view. Zoom Out: Zoom out on the current view. Restore: Restore the original view. GUI Menus Each menu in the menu bar is context-sensitive. Items can be displayed as available (highlighted) or unavailable (grayed out) depending on the currently active object. The following sections summarize the available menu options: File Menu, page 1-45 View Menu, page 1-45 Alarm Menu, page 1-46 Events Menu, page 1-46 Services Menu, page 1-47 Service Groups Menu, page 1-48 Admin Menu, page 1-48 Page 1-44 Turin Networks Release TN4.0.x

Chapter 4 Graphical User Interface General Description View Menu Provisioning Menu, page 1-51 Help Menu, page 1-51 File Menu 1. 2. 3. Use the commands on the File menu to manage user preferences. See Section 2 Administrative Tasks, Chapter 3 User Preferences, page 2-15 for detailed information about these commands. 1. Import User Preferences. Import Alarms and Events sorting and filter settings saved under the user name. 2. Save User Preferences. Save Alarms and Events sorting and filter settings and Map View background image under the current user name. Figure 1-31 File Menu 3. Exit. Exit the application and close the main window. View Menu Use the commands on the View menu to set your screen to your required dimensions. 1. 2. 3. 4. 5. 6. 1. Show Parent Map: Display the map of the nodes and links one level above the present Map View. 2. Show Network Map: Display the map of nodes and links within the domain. 3. Show Shelf View: Display the Shelf View of a selected node. 4. Zoom In - CTRL-I: Zoom in on the current view. Figure 1-32 View Menu 5. Zoom Out - CTRL-O: Zoom out on the current view. 6. Restore - CTRL-C: Restore the view to the default setting. Release TN4.0.x Turin Networks Page 1-45

TransNav GUI Guide, Section 1: Installation and Overview Alarm Menu Alarm Menu Use the commands on the Alarm menu to help you manage information on the Alarms tab. See Section 8 Maintenance and Testing, Chapter 2 Alarms, page 8-11 for detailed information about the Alarm tab. 1. 2. 3. 4. 1. Set Filters: Open the Alarm Filter (View Main) dialog box. Allows you to filter displayed alarms by source, probable cause, time, or severity. 2. New Window: Open an independent Alarm View dialog box that inherits the alarm filters set for the Alarms tab. Figure 1-33 Alarm Menu 3. Acknowledge: Acknowledge the selected alarm. 4. Detail View: Display selected alarm details through the Alert Detail (View Main) dialog box. Events Menu 1. 2. 3. 4. 5. Use commands on the Events menu to help you manage the information on the Events tab. See Section 8 Maintenance and Testing, Chapter 3 Events, page 8-25 for detailed information about the Events tab. 1. Set Filters: Open the Event Filter (View Main) dialog box. Allows you to filter displayed events by source, probable cause, time, or severity. 2. New Window: Open an independent Event View dialog box that inherits the event filters set for the Events tab. 3. Settings: Open the Event Retrieval Settings (View Main) dialog box and change how often events are retrieved and refreshed. Figure 1-34 Events Menu 4. Refresh: Display events that have occurred since the last time Refresh was clicked. 5. Detail View: Display selected event details through the Event Detail (View Main) dialog box. Page 1-46 Turin Networks Release TN4.0.x

Chapter 4 Graphical User Interface General Description Services Menu Services Menu Use the commands on the Services menu to help you manage information on the Service tab. See Section 6 Services for detailed information on services. 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. Figure 1-35 Services Menu 1. Show TxRx Path: Display the active and standby paths for a selected service in the forward and reverse directions. 2. Show RSTP Port Info: Shows the RSTP port information for TLS services. 3. Show Last Error: Display the last error for the selected service. 4. Abort: Abort in-progress service activation, deactivation, or deletion. 5. Activate: Activate the selected service. 6. Deactivate: Deactivate the selected service. 7. Roll: Transfer traffic from one facility to another without interrupting service. Create all the bridge services individually first, then roll and commit multiple services. See the Traverse Provisioning Guide, Section 5 Creating Service Applications, Chapter 2 Bridging and Rolling Services, page 5-13 for detailed procedures on bridging and rolling services. 8. Unroll: An undo command. 9. Commit Rolled: After you roll traffic to a new facility, commit the transfer and delete the original service. 10. Edit: Edit a selected service. 11. Delete: Delete a selected service. 12. Duplicate: Duplicate the selected service. Release TN4.0.x Turin Networks Page 1-47

TransNav GUI Guide, Section 1: Installation and Overview Service Groups Menu Service Groups Menu Use commands on the Service Groups menu to help you manage information on the Service Group tab. See Section 6 Services, Chapter 6 Service Groups for detailed information about the Service Group tab. 1. 2. 3. 4. 5. Figure 1-36 Services Groups Menu 1. Synchronize: Synchronize services created on the server with the nodes in the network. 2. Activate: Activate the selected service group. 3. Deactivate: Deactivate the selected service group. 4. Edit: Edit the selected service group. 5. Delete: Delete the selected service group. Admin Menu Use the commands on the Admin menu to perform administrative functions in the network. The following descriptions for each command lists the appropriate cross-references to specific topics in the documentation for detailed information. 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 14. 15. 16. 17. 18. 19. 20. 21. 22. Figure 1-37 Admin Menu 1. Performance Templates: Define performance monitoring and capacity monitoring (VT/TU only) templates. See Section 8 Maintenance and Testing, Chapter 1 Performance Monitoring, page 8-1. 2. Bandwidth Profiles: Create Ethernet bandwidth profiles on the TransNav management server. 3. Classifiers: Create Ethernet traffic management classifiers for the Traverse on the TransNav management server. 4. TE100Classifiers: Create Ethernet traffic management classifiers for the TE-100 on the TransNav management server. 5. Alarm Profiles: Set alarm profiles, including severities, for non-service-affecting and service-affecting alarms; also for disabling and enabling alarms. See Section 8 Maintenance and Testing, Chapter 2 Alarms, page 8-11. 6. Reports: Generate and define reports. See Section 2 Administrative Tasks, Chapter 4 Administrative Tasks, page 2-25. 7. Customer: Define customer information. See Section 2 Administrative Tasks, Chapter 4 Administrative Tasks, page 2-25. Page 1-48 Turin Networks Release TN4.0.x

Chapter 4 Graphical User Interface General Description Admin Menu 8. Functional Groups: Define, change, or delete functional groups for domain user security using pre-defined roles and node access. See Section 2 Administrative Tasks, Chapter 1 Managing Server Security, page 2-1. 9. Domain User: Define, change, or delete a domain user through pre-defined roles. See Section 2 Administrative Tasks, Chapter 1 Managing Server Security, page 2-1. 10. Node User: Define, change, or delete a node user through pre-defined access groups. See Section 2 Administrative Tasks, Chapter 2 Managing Node Security, page 2-11. 11. Current User: Display the current user name and change the password. See Section 2 Administrative Tasks, Chapter 1 Managing Server Security, page 2-1. 12. Session List: Display the current users on the management system. 13. Discovery: Enter the name or IP address of the Management Gateway Node(s). See Section 3 Network, Chapter 2 Network Auto Discovery, page 3-19. 14. SW Upgrade: Perform a software upgrade. See Section 8 Maintenance and Testing, Chapter 6 Software Upgrades, page 8-47. 15. SW Activation: Activate the software. 16. IP Static Route Configuration: Add static routes to a node for management IP traffic. 17. OSI Static Route Configuration: Add static routes to a node for OSI (open system interconnection). (Planned for future release.) 18. OSI Parameters Configuration: Configure a node to be an OSI gateway node. (Planned for future release.) 19. IP QOS Configuration: Set up a control list to allow or block traffic from certain IP hosts or networks. Outgoing messages can be prioritized as High Priority or Best Effort. See Section 3 Network, Chapter 5 Configuring IP Quality of Service, page 3-35. 20. Options: Turn the audible alarm on or off or set time zone and date format options. 21. SNMP Configuration: Set the Traverse node SNMP agent read and write community strings, four trap destination IP addresses, ports, and trap community strings. 22. Attached Devices SNMP Parameters: Set the SNMP sub-shelf devices polling and synchronization intervals for the management server. Release TN4.0.x Turin Networks Page 1-49

TransNav GUI Guide, Section 1: Installation and Overview Admin Menu Page 1-50 Turin Networks Release TN4.0.x

Chapter 4 Graphical User Interface General Description Scroll Bars Provisioning Menu Use the commands on the Provisioning menu to pre-provision equipment in the management system. See Section 3 Network, Chapter 1 Creating and Deleting Equipment Using Preprovisioning, page 3-1 for detailed information on creating and configuring equipment in the network. 1. 2. 3. Figure 1-38 Provisioning Menu 1. Add Node: Preprovision a node to the domain. 2. Add Link: Preprovision a virtual link between nodes in a domain. 3. Add TA200: Add a TransAccess 200 Mux to the management interface. To add a TransAccess 200 Mux sub-shelf device, see the TransNav Management System GUI Guide, Section 5 Equipment, Chapter 5 TransAccess 200 Mux, page 5-73. Help Menu Use the commands on the Help menu to display the online help information for the graphical user interface. 1. On Application: Display help on the user interface application. 1. 2. 3. 2. Tooltip Settings: (Planned for future release.) 3. About: Display the management system version number. Figure 1-39 Help Menu GUI Conventions The following conventions are used in dialog boxes: A gray box indicates a read-only field: A white box indicates a configurable field: A black down-arrow indicates additional selections are available: A gray down-arrow indicates no additional selections are available: Scroll Bars The user interface (Map View, Shelf View, and any dialog box), display scroll bars (two scroll arrows and a scroll box) when the total contents in the pane are not visible to the user. The scroll bars allow you to view the total contents in the pane. Release TN4.0.x Turin Networks Page 1-51

TransNav GUI Guide, Section 1: Installation and Overview Resizing Capabilities Resizing Capabilities You can resize the Map View, Shelf View, and Tab screen area for both views. Move the mouse until you see a double arrow at an outer perimeter point of the main window or in the area between the Shelf View and Tab screen area. Hold down the left mouse button, move the mouse until the window is in the desired position, and release the left mouse button. Page 1-52 Turin Networks Release TN4.0.x

SECTION 2ADMINISTRATIVE TASKS SECTION 2 ADMINISTRATIVE TASKS Contents Chapter 1 Managing Server Security Definitions.................................................... 2-1 Security Management........................................... 2-1 Password Changes............................................. 2-3 Guidelines to Managing Server Security............................. 2-4 Access Roles.................................................. 2-5 Domain Users................................................. 2-6 Functional Groups.............................................. 2-7 Session List................................................... 2-10 Chapter 2 Managing Node Security Definitions.................................................... 2-11 Security Management........................................... 2-11 Access Roles.................................................. 2-12 Node User.................................................... 2-13 Chapter 3 User Preferences Select Background Image for Map View............................. 2-15 Saving and Importing User Preferences............................. 2-16 Customize System Options....................................... 2-17 Grouping Nodes............................................... 2-18 Chapter 4 Administrative Tasks Generating Reports............................................. 2-25 Report Schedulers.......................................... 2-26 Report List................................................ 2-27 Using the Report Scheduler...................................... 2-27 Example Report Output.......................................... 2-30 Adding Customer Information..................................... 2-31 List of Figures Figure 2-1 Functional Group Access Example........................ 2-2 Figure 2-2 User Information Dialog Box............................. 2-3 Figure 2-3 Domain Users Dialog Box............................... 2-6 Figure 2-4 Functional Group Configuration Dialog Box................. 2-7 Release TN4.0.x Turin Networks Page i

TransNav GUI Guide, Section 2 Administrative Tasks Figure 2-5 Tiling the Domain User and Functional Group Dialog Boxes.... 2-9 Figure 2-6 Session List Dialog Box................................. 2-10 Figure 2-7 Node Users Dialog Box................................. 2-13 Figure 2-8 Load Background Image Dialog Box....................... 2-15 Figure 2-9 Import User Preferences Dialog Box....................... 2-16 Figure 2-10 Options Dialog Box.................................... 2-17 Figure 2-11 Add Group - Network Level.............................. 2-18 Figure 2-12 Group Icon........................................... 2-18 Figure 2-13 Group Configuration................................... 2-19 Figure 2-14 Add an Existing Node to a Group......................... 2-20 Figure 2-15 Add a Group to Another Group........................... 2-21 Figure 2-16 Navigation Tree and Group Icon.......................... 2-22 Figure 2-17 Expanded Group...................................... 2-22 Figure 2-18 Remove Node or Group from a Group..................... 2-23 Figure 2-19 Reports Dialog Box.................................... 2-26 Figure 2-20 Report Scheduler Dialog Box............................ 2-27 Figure 2-21 Example Event Report.................................. 2-30 Figure 2-22 Customer Information View Dialog Box..................... 2-31 List of Tables Table 2-1 Roles and Access Rights for Server Security................ 2-5 Table 2-2 Access Groups and Access Rights for Node Security.......... 2-12 Table 2-3 Select Background Image for Map View.................... 2-15 Table 2-4 Grouping Nodes...................................... 2-18 Page ii Turin Networks Release TN4.0.x

SECTION 2 ADMINISTRATIVE TASKS Chapter 1 Managing Server Security Introduction Definitions Security Management Security management enables the network operator to create and manage user accounts with specific access privileges. Security management also tracks user account activity to assist in identifying and preventing security breaches. This chapter explains changing a password, roles, functional groups, and assigning access rights to domain users: Security Management, page 2-1 Password Changes, page 2-3 Guidelines to Managing Server Security, page 2-4 Access Roles, page 2-5 Domain Users, page 2-6 Functional Groups, page 2-7 Session List, page 2-10 A domain refers to an entire Traverse network. The terms domain and management domain are used interchangeably. A management plane domain is a set of Traverse nodes managed by a common TransNav system. A Functional Group is a user-defined combination of access roles enabling domain users access to assigned Traverse nodes. A Role is based on the responsibilities that network operation personnel have in their network; for example, Equipment Configuration Manager. On the TransNav management system, there are two categories of users: A Domain User uses the management system to access system resources either through the graphical user interface (GUI) or the command line interface (CLI). Domain operators can be given multiple user accounts with different roles. A Node User manages any node in a domain to which the user has access through the CLI. Users can be assigned to one or more nodes in the network. The ability to create, delete, and modify user accounts is available only to users in the Administrator role. Release TN4.0.x Turin Networks Page 2-1

TransNav GUI Guide, Section 2: Administrative Tasks Security Management For the built-in primary administrator account, the password may be changed (and should be, for security reasons), but the account itself may not be deleted nor the groups changed. The management system uses this account to manage the node; deleting the account or reducing its privileges would make it impossible for the management system to manage the node. Domain administrators can control user access using roles and Functional Groups for domain users on the Traverse management (EMS) server. The Traverse has several pre-defined roles. Domain users in a Functional Group who have Administrator roles can access all of the system resources. They can limit access privileges of other domain users to a set of system features and resources with user-defined Functional Groups, known as Role-based Access Control (RBAC). A domain user can only belong to one Functional Group at a time. In the following example, Joe and Jeff are members of functional Group A and have Administrator role privileges to all nodes; Bob and Tim are members of Group B and have Fault Manager and Equipment Configuration Manager roles for Nodes 2 through 5; John and Sally are members of Group C and have Equipment Configuration Manager and Report Manager roles for Nodes 4 and 5. Figure 2-1 Functional Group Access Example A domain administrative user can use the Session List to see who is currently logged into the system. If necessary, an administrator can choose to terminate a user s current session. Page 2-2 Turin Networks Release TN4.0.x

Chapter 1 Managing Server Security Password Changes Password Changes Individuals can change their password through the User Information dialog box. From the Admin menu, select Current User to display the User Information dialog box. Figure 2-2 User Information Dialog Box The User Information dialog box allows individuals to view and enter the following information: Username: Displays the name of the current user. Group name: Indicates the name of the functional group of which this user is a member, if any. Roles: Indicates the roles associated to the functional group; for example, Equipment Manager. Old Password: Enter your old password. New Password: Enter your new password. Confirm New: Re-enter your new password. Command buttons are as follows: OK: Save new password and close the dialog box. Cancel: Cancel password change attempt and close the dialog box. Release TN4.0.x Turin Networks Page 2-3

TransNav GUI Guide, Section 2: Administrative Tasks Guidelines to Managing Server Security Guidelines to Managing Server Security The guidelines to managing server security are: For security reasons, only Administrators can add new users at the domain level. The User Manager role is available at the node-level only. If you do not specify a role when you create a user account, by default the user has only viewing privileges. The Viewer role is not directly provisionable. Domain users can only be assigned to one Functional Group per logon username and password. A separate logon username and password is required if access is needed to another functional group. If All Nodes is selected for a functional group, the users in that functional group will have access to all nodes in the network. This is required for roles, such as Equipment Configuration Managers, who must have All Nodes assigned to display protection ring information for the network. It is also required for provisioning end-to-end services. Page 2-4 Turin Networks Release TN4.0.x

Chapter 1 Managing Server Security Access Roles Access Roles Network operations personnel have different roles and responsibilities in the Operations, Administration, and Management (OAM) of their networks. Roles enable the network administrator to permit or restrict user access to various network operations. The TransNav management system has the following built-in roles whose allowable operations are defined below for Domain users: Table 2-1 Roles and Access Rights for Server Security Roles Administrator Equipment Configuration Manager Service Configuration Manager Report Manager Fault Manager (Viewer) Allowable Operations Provision and view everything in the system, including all user account data and security logs. Provision and view all node, card, port, and control plane parameters. Provision and view all services. Create, schedule, and view reports. Provision alarm severities; view alarm and event logs. Default. View everything; cannot perform any operations. You can access the Functional Groups Configuration dialog box from either the Domain User (Groups button) or Functional Groups selections on the Admin menu. Release TN4.0.x Turin Networks Page 2-5

TransNav GUI Guide, Section 2: Administrative Tasks Domain Users Domain Users A Domain User uses the management system to manage a domain of nodes through the server, either through the GUI or the CLI. Select Domain User from the Admin menu to display the Domain Users dialog box. Figure 2-3 Domain Users Dialog Box The Domain Users dialog box allows you to enter the following information: Username: Enter the user name. User names are case sensitive. They must be alphanumeric, 2 to 32 characters in length, and contain no special characters such as @$%*&. Hyphens (-) and spaces are allowed. Password: Enter the password. Passwords must be alphanumeric and 4 to 10 characters in length. They can contain spaces, hyphens (-), and/or special characters (such as @$%*&). If alphanumeric, they are also case-sensitive. Confirm: Re-enter the password. Timeout (min): Number of minutes after which an unused session will be closed. Valid values are: 0. Disables the feature. The session will never time out. 5 minutes, in 1 minute increments. A warning message appears two minutes before the session times out. Important: For security reasons, Turin recommends using the value 0 with extreme caution. Command buttons are as follows: Add: Add the new domain user name to the Username list. Update: Update the selected domain user s name with new information. Groups: Access the Functional Group Configuration dialog box. Clear: Clears current selections. Page 2-6 Turin Networks Release TN4.0.x

Chapter 1 Managing Server Security Functional Groups Delete: Delete the domain user highlighted in the Username box. A Confirm Delete dialog box displays reading Are you sure you would like to delete [Username]? Click Yes to delete or No to cancel. Done: Save the changes and close the dialog box. Turin recommends adding new domain users to a functional group as the user s profile is added to allow them access to nodes. Domain users with no roles or assigned nodes can log on to the TransNav management server, but will have only the Viewer role. Functional Groups A Functional Group is a user-defined combination of roles enabling domain users access to nodes to which they have been assigned access. Functional Groups can be defined to best match the network operator s security requirements for role-based access control. For example, a functional group called CentralCraft is created. Two users in the CentralCraft functional group, jsmith and mwesley, have the Report Manager role for NodeA. Both users will have access to all reports for only NodeA in the CentralCraft functional group; they cannot access reports for the any other nodes in the CentralCraft functional group. If you are a domain user with Administrator role rights, you can create and maintain functional groups from the Admin menu by selecting Functional Groups or the Domain User, Groups command button. Figure 2-4 Functional Group Configuration Dialog Box Release TN4.0.x Turin Networks Page 2-7

TransNav GUI Guide, Section 2: Administrative Tasks Functional Groups The Functional Group Configuration dialog box allows you to enter the following information: Functional Group Name: Click the field to enter the name of the functional group. The name must be alphanumeric and contain no spaces. Hyphens (-) are allowed. Note: The administrators functional group is built-in; it cannot be changed or deleted. The password for this functional group may be changed (and should be for security reasons). Roles: Select the roles to be included in the functional group. The roles are: Administrator Service Configuration Manager Fault Manager Equipment Configuration Manager Report Manager All Nodes: Select to assign all nodes to the functional group. Users whose roles require end-to-end provisioning must have All Nodes selected. Node List: Select a node from the list below and click the right arrow to assign the node to the functional group. User List: Select the username from the list below and click the right arrow to assign the user to the functional group. Command buttons are as follows: Add: Add the functional group to the Functional Groups list. Delete: Delete the functional group highlighted in the Functional Groups list. A Confirm Delete dialog box displays reading Are you sure you would like to delete [FunctionalGroup]? Click Yes to delete or No to cancel. Update: Update the selected functional group with new information. Clear: Clear all information from the boxes. Done: Save the changes and close the dialog box. If you clicked the Groups command button on the Domain Users dialog box, you return to that dialog box. Note: To quickly add domain users to functional groups, Turin suggests tiling the Domain Users dialog box next to the Functional Group Configuration dialog box as shown in Figure 2-5 Tiling the Domain User and Functional Group Dialog Boxes. Page 2-8 Turin Networks Release TN4.0.x

Chapter 1 Managing Server Security Functional Groups As new domain users are added, their names display on the Functional Group Configuration dialog box. Figure 2-5 Tiling the Domain User and Functional Group Dialog Boxes Changes made to a functional group will not affect domain users currently logged onto the Traverse management (EMS) server. The changes take effect the next time the user accesses the system. Before deleting a functional group, you must remove the attached domain users. Domain users with no assigned Roles and Nodes can log on to the TransNav management server, but will have only the default Viewer role. Release TN4.0.x Turin Networks Page 2-9

TransNav GUI Guide, Section 2: Administrative Tasks Session List Session List A domain administrator can use the Session List to see the active domain users logged into the system. A session is any connection started from any user interface: GUI, CLI, or TL1. From the Admin menu, click Session List to display the Session List dialog box. Figure 2-6 Session List Dialog Box The Session List dialog box allows you to view information about domain users currently logged into the management server. User Name: The identification of the user currently logged in. Client Type: Displays one of the following user interface types: GUI: graphical user interface CLI: command line interface TL1: TL1 interface IP Address (HostName): Displays the IP address of the workstation where the domain user is logged in. Time Logged In: Displays the time the domain user logged into the session. Command buttons are as follows: Terminate: A domain administrator can choose to terminate a selected domain user s session. Cancel: Close the dialog box. Page 2-10 Turin Networks Release TN4.0.x

SECTION 2 ADMINISTRATIVE TASKS Chapter 2 Managing Node Security Introduction Definitions Security Management Security management establishes and manages user accounts with specific access privileges. Security management also tracks account activity to assist in identifying and preventing potential security breaches. This chapter explains security management, access groups, and assigning access rights to node users: Security Management, page 2-11 Access Roles, page 2-12 Node User, page 2-13 A domain refers to an entire Traverse network. The terms domain and management domain are used interchangeably. A management plane domain is a set of Traverse and TraverseEdge nodes managed by a common TransNav management system. On the TransNav management system, there are two categories of users: A Domain User uses the management system to access system resources either through the graphical user interface (GUI) or the command line interface (CLI). Domain operators can be given multiple user accounts with different roles. A Node User manages any node in a domain to which the user has access through the CLI. Users can be assigned to one or more nodes in the network. The ability to create, delete and modify accounts is available only to users with Admin (administrator) privileges. For the built-in primary administrator account, the password may be changed (and should be, for security reasons), but the account itself may not be deleted nor the groups changed. The management system uses this account to manage the node; deleting the account or reducing its privileges would make it impossible for the management system to manage the node. You can control node user access using Access Roles. The Traverse has several pre-defined access groups. Release TN4.0.x Turin Networks Page 2-11

TransNav GUI Guide, Section 2: Administrative Tasks Access Roles Any node user can be assigned one or more access roles. Access is cumulative; for example, a node user who is in two access groups has the privileges of both access groups. Node users can access and manage the nodes to which they are assigned. Access Roles The TransNav management system has the following built-in access roles whose allowable operations are defined below for Node users: Table 2-2 Access Groups and Access Rights for Node Security Access Role Names Administrator Equipment Configuration Manager Service Configuration Manager User Manager Fault Manager Report Manager (Viewer) Allowable Operations Provision and view everything. Administrators are the only users who can assign users to Administrator role. Provision and view all node, card, port, and control plane parameters. Provision and view all services. Provision and view all user account data and security logs except Administrator role. Provision alarm severities; view alarm and event logs. Create, schedule, and view reports. Default. Can view everything, but cannot make any changes. If you do not specify an access group when you create the account, by default the user has only viewing privileges. The Viewer group is not directly provisionable through the Node Users dialog box. Each node user account is a member of one or more access groups. A user s allowable operations are the sum of all the rights of all access groups in which the user is a member. Node users are assigned access groups by the node administrator from the Node User selection on the Admin menu. Page 2-12 Turin Networks Release TN4.0.x

Chapter 2 Managing Node Security Node User Node User A Node User manages any single node in a domain using the node-level CLI. A node user s session will end (timeout) after 120 minutes of no activity. Select Node User from the Admin menu to display the Node Users dialog box. Figure 2-7 Node Users Dialog Box The Node Users dialog box allows you to view defined node users and their corresponding sync status in the Username and Sync Status columns, respectively, in the upper box. You can define a new node user by entering the following data: Username: Enter the user name. User names are case sensitive. They must be alphanumeric, 2 to 32 characters in length, and contain no special characters such as @$%*&. Hyphens (-) and spaces are allowed. Password: Enter the password. Passwords must be alphanumeric and 4 to 10 characters in length. They can contain spaces, hyphens (-), and/or special characters (such as @$%*&). If alphanumeric, they are also case-sensitive. Confirm: Re-enter the password. Roles: Select one or more access roles from the list and click the right arrow to assign the role to the user: Administrator Equipment Config Manager Service Config Manager User Manager Fault Manager Report Manager Release TN4.0.x Turin Networks Page 2-13

TransNav GUI Guide, Section 2: Administrative Tasks Node User Nodes: Select a node from the list of nodes in the domain and click the right arrow to allow the user to manage that node. Command buttons are as follows: Add: Add the node user to the Username list. Update: Update the changes for the selected node user. Sync: Synchronize all node users. For additional information on synchronization, see Chapter 4 Graphical User Interface General Description, Scroll Bars, page 1-51. Sync All: Synchronize all node users, allowing all node users access to any of the nodes in the domain. Clear: Clear all information that has not been saved. Delete: Select a Username and click Delete to remove the node user selected. Done: Save the changes and close the dialog box. Page 2-14 Turin Networks Release TN4.0.x

SECTION 2 ADMINISTRATIVE TASKS Chapter 3 User Preferences Introduction Select Background Image for Map View This chapter describes the following GUI features: Select Background Image for Map View, page 2-15 Saving and Importing User Preferences, page 2-16 Customize System Options, page 2-17 Grouping Nodes, page 2-18 Use this procedure to import a saved image file for the background image for the network or for any group in Map View. For information on adding background images, see the TransNav Management System Server Guide, Section 2 Management Server Procedures, Chapter 3 Server Administration Procedures, Customizing Background Images. Table 2-3 Select Background Image for Map View Step Procedure 1 In Map View, right-click the background map and select Change Background. 2 The Load Background Image dialog box displays. Figure 2-8 Load Background Image Dialog Box Release TN4.0.x Turin Networks Page 2-15

TransNav GUI Guide, Section 2: Administrative Tasks Saving and Importing User Preferences Table 2-3 Select Background Image for Map View Step Procedure 3 Select the image file name to be displayed in Map View from the selections in the Available Images box. Click Set. 4 The map background in Map View changes to display the new background and the image file name appears in the Current Image field of the Load Background Image dialog box. Click Done to close the dialog box. 5 To save the background image, select File, then Save User Preferences. For further information, see Saving and Importing User Preferences, page 2-16. 6 To view the map for the group one level above, click View, then Show Parent Map. 7 To view the network map, click View, then select Show Network map. 8 The Select Background Image for Map View procedure is complete. Saving and Importing User Preferences You can save and import the following user preferences: Alarm and event filter and sort settings The graphical locations of the nodes and links in Map View Map View background images in Map View To save user preferences, select Save User Preferences from the File menu. After logging out of the system and then logging back in, these settings are retained. To import user preferences, select Import User Preferences from the File menu. The Import User Preferences dialog box displays. From the Available list, select the name of the user whose preferences you want to import. Figure 2-9 Import User Preferences Dialog Box The name appears in the Import field. Click Import to import the preferences into your profile. Upon exiting the TransNav GUI, the system prompts you to save your user preferences. Click Yes to save the changes. Page 2-16 Turin Networks Release TN4.0.x

Chapter 3 User Preferences Customize System Options Command buttons are as follows: Refresh List: Refresh the Available list with all user IDs. Import: Import user preferences from the user ID selected in the Available box. Cancel: Cancel import and close the dialog box. Customize System Options Customize the sound, time, and date options in the TransNav user interface. From the Admin menu, select Options to display the Options dialog box. Figure 2-10 Options Dialog Box The Options dialog box allows you to customize the following options: Sound Options: Turn ON or OFF audible alarms. Selected (default): Allow the sound for alarms. Unselected: Turn OFF the sound for alarms. Time Options: Use Local Time Zone: Select this option to use the local time zone from the client computer. Date Format: Select one of the following options: MM/DD/YY 12h: month/day/year twelve hour clock MM/DD/YY 24h: month/day/year twenty-four hour clock DD/MM/YY 12h: day/month/year twelve hour clock DD/MM/YY 24h: day/month/year twenty-four hour clock YYYY/MM/DD 12h: year/month/day twelve hour clock YYYY/MM/DD 24h: year/month/day twenty-four hour clock MMM/DD/YY 12h: month/day/year twelve hour clock MMM/DD/YY 24h: month/day/year twenty-four hour clock DD/MMM/YY 12h: day/month/year twelve hour clock DD/MMM/YY 24h: day/month/year twenty-four hour clock To save changes to these user preferences, select File, then Save User Preferences. The changes will be effective the next time the GUI is restarted. Command buttons are as follows: Close: Close the dialog box and return to the main menu. Release TN4.0.x Turin Networks Page 2-17

TransNav GUI Guide, Section 2: Administrative Tasks Grouping Nodes Grouping Nodes In a network containing multiple nodes, use the grouping feature to collapse nodes into groups to make the network easier to manage. Groups are user defined, allowing each user to group nodes and group individually. Groups and nodes display in the navigation tree alphanumerically; groups display first, then the nodes. The groups can be expanded to display the nodes and other groups within that group. While the number of groups that can be put into a hierarchy is unlimited, Turin recommends using a maximum hierarchy of 10 groups for manageability. When a new node is added, it displays at the network level allowing all users to view and select the nodes for their individual groups. New groups appear on the map where they are added. Nodes and groups can be added to groups that are on the same level in the navigation tree. Each node group can have a unique background image. For details, see Select Background Image for Map View, page 2-15. Table 2-4 Grouping Nodes Step Procedure 1 In Map View, right-click the background image and select Add Group from the menu. Figure 2-11 Add Group - Network Level 2 A Group icon appears in the upper left corner of the Map View. Group icon Figure 2-12 Group Icon Page 2-18 Turin Networks Release TN4.0.x

Chapter 3 User Preferences Grouping Nodes Table 2-4 Grouping Nodes (continued) Step Procedure 3 Change the group name by selecting the group name in the navigation tree at the left of the Map View or by clicking the group icon in Map View. Click the Config tab. Figure 2-13 Group Configuration The Group Configuration screen displays. Change the name in the Group Name field. Click Apply. 4 To create a new node, in Map View, right-click any background map and select Add node or select Provisioning from the menu bar and select Add node. The Preprovision New Node dialog box displays. For details, see Section 3 Network, Chapter 1 Creating and Deleting Equipment Using Preprovisioning. Repeat Step a for all nodes to be created. The nodes appear at the network level. To add a new or existing node to a group, go to Step 5. To move a group of nodes or groups into a group, go to Step 6. Release TN4.0.x Turin Networks Page 2-19

TransNav GUI Guide, Section 2: Administrative Tasks Grouping Nodes Table 2-4 Grouping Nodes (continued) Step Procedure 5 To add a node to a group on the same level, right-click the Group icon in Map View and select Add a node. A list of the available nodes displays. Select the node name to add to the group. Group icon Figure 2-14 Add an Existing Node to a Group Note: If the shortcut menu does not display the Add a node option, no nodes exist at that level in the hierarchy. To move a group of nodes or groups into a group, go to Step 6. Page 2-20 Turin Networks Release TN4.0.x

Chapter 3 User Preferences Grouping Nodes Table 2-4 Grouping Nodes (continued) Step Procedure 6 To add a node or a group to another group, use either of the following steps: Figure 2-15 Add a Group to Another Group a. From Map View, right-click the Group icon and select Add a (Node or Group). A list of nodes and groups at the same level displays. Select the node or group to be added. b. From the navigation tree, select the group to which you want to add a node or group, then click the Config tab. The Group Configuration screen displays. Select the node or group in the left pane and click Add. The node or group is added to the group. To add a range of nodes and/or groups, click the first node, hold down the Shift key, then click the last node. Click Add. The nodes are added to the group. To add specific nodes in a list, hold down the CNTL key, select the nodes to add, then click Add. c. Click Apply to save the changes. Note: A node can only exist in one group at a time. Release TN4.0.x Turin Networks Page 2-21

TransNav GUI Guide, Section 2: Administrative Tasks Grouping Nodes Table 2-4 Grouping Nodes (continued) Step Procedure 7 The navigation tree displays the groups and nodes. Each group can be collapsed or expanded. Figure 2-16 Navigation Tree and Group Icon 8 Expand a group to display the nodes and groups it contains, Figure 2-17 Expanded Group a. In Map View, double-click the Group icon. b. From the navigation tree or in Map View, right-click the group and select Show <group name> map. Page 2-22 Turin Networks Release TN4.0.x

Chapter 3 User Preferences Grouping Nodes Table 2-4 Grouping Nodes (continued) Step Procedure 9 To remove a node or a group from a group, use one of the following methods: Figure 2-18 Remove Node or Group from a Group a. From the navigation tree, select the group for which you want to remove a node or group, then click the Config tab. The Group Configuration screen displays. In the right pane, a list of groups and nodes currently in the group displays. Select the node or group to remove, then click Remove. Repeat removing nodes or groups until all of the desired node groups and nodes are removed. Click Apply to save your changes. b. From the navigation tree, right-click the group for which you want to remove a node or group. Select Remove a (node or group). A list of nodes or groups displays. Select the node or group to be removed. c. In Map View, right-click the Group icon for which you want to remove a node or group. Select Remove a (node or group). The nodes or groups are removed from the group, but are not deleted. They display at the same level as the group from which they were removed. Release TN4.0.x Turin Networks Page 2-23

TransNav GUI Guide, Section 2: Administrative Tasks Grouping Nodes Table 2-4 Grouping Nodes (continued) Step Procedure 10 To delete a group and all nodes and groups attached to it, use one of the following steps: a. From the navigation tree, right-click the group to delete, then select Delete group. b. From Map View, right-click the group to delete. Select Delete group. A confirmation message displays. Click Yes to continue the deletion. 11 From the File menu, click Save User Preferences to save the grouping. 12 The Grouping Nodes procedure is complete. Page 2-24 Turin Networks Release TN4.0.x

SECTION 2ADMINISTRATIVE TASKS Chapter 4 Administrative Tasks Introduction Generating Reports This chapter describes the following administrative functions selected through the Admin menu on the TransNav management system graphical user interface (GUI): Generating Reports, page 2-25 Using the Report Scheduler, page 2-27 Example Report Output, page 2-30 Adding Customer Information, page 2-31 Generate a set of data in a particular format at specified intervals. The following reports can be generated for all nodes in the domain or for a specific node: Historical alarm Node inventory Historical event Performance monitoring Resource availability Domain service Service availability Additionally, capacity monitoring of switching capacity on VT/TU cards is available to assist in planning resource usage on these cards. Note: If you have multiple servers set up in your Traverse system and want long-term access to statistics for all of the servers, Turin recommends performing regular backups of the files on each server. One way to accomplish this is to use the Report Scheduler and set up a regularly-generated report. The report output can then be saved to a server that is accessible to all interested parties. You first create a Report Scheduler to specify: A SQL script, which is run against the database in order to extract the requested information The report generation frequency (none, once, hourly, daily, weekly, or monthly) and next generation time The number of hours the report covers The node the report covers (optional) Release TN4.0.x Turin Networks Page 2-25

TransNav GUI Guide, Section 2: Administrative Tasks Generating Reports Select Reports from the Admin menu to display the Reports dialog box. Figure 2-19 Reports Dialog Box The Reports dialog box has two main areas: Report Schedulers, page 2-26 Report List, page 2-27 Report Schedulers Lists all the reports that you have scheduled. Column headings are as follows: Name: Name of scheduled report. Next Generation: Displays the next generation time set in the Report Scheduler dialog box. Generation Period: Displays the generation period set in the Report Scheduler dialog box. Comment: Displays comments set in the Report Scheduler dialog box. Command buttons are as follows: Generate Now: Generates a report using the report currently selected in the Report Schedulers box. The report name is added to the Report List. Add: Add a new report to the schedule. Displays the Report Scheduler dialog box. Edit: Edit the report selected in the Name column. Delete: Delete the selected scheduled report name. Displays a dialog box that reads Are you sure you would like to delete [scheduled report name]? Click Yes to proceed with the Delete request or No to cancel the request. Page 2-26 Turin Networks Release TN4.0.x

Chapter 4 Administrative Tasks Using the Report Scheduler Report List Lists all the reports you have generated. Command buttons are as follows: List All: List all generated reports. View Report: View report selected in the Report List box. An example event report is shown in Example Report Output, page 2-30. Done: Close the dialog box. Using the Report Scheduler The Report Scheduler is a template that can be run again and again, producing a different file each time. From the Admin menu, click Reports. On the Reports dialog box, Report Schedulers area, click Add. The Report Scheduler dialog box displays. Figure 2-20 Report Scheduler Dialog Box The Report Scheduler dialog box allows you to view and change the following information: Name: Enter the name of the report. Once a name is given to a report, it cannot be changed. Generation Period: Select one of the following options: None: Do not regularly generate a report. Once: Generate one report at the time specified in the Next Generation box. After the report is generated once, the Generation Period changes to None. Hourly: Generate the report hourly starting with the time specified in the Next Generation box, and hourly thereafter. Daily: Generate the report daily starting with the time specified in the Next Generation box, and daily thereafter. Weekly: Generate the report weekly starting with the time specified in the Next Generation box, and weekly thereafter. Monthly: Generate the report monthly starting with the time specified in the Next Generation box, and monthly thereafter. Next Generation: Select the first time the report is to be generated. Use the up arrow to go forward in time and the down arrow to go back in time. Comment: Enter comments about the report. Release TN4.0.x Turin Networks Page 2-27

TransNav GUI Guide, Section 2: Administrative Tasks Using the Report Scheduler Report Script: The SQL script file to be executed against the server database to generate the report. Generate reports for resources specified in the Report Source Filter field over the time period specified in the Report Period field. Select from the following list of defined script files: alert.sql: Historical alarm report. Displays a record of alarm information, including alarm duration and clearing time. event.sql: Historical event report. Displays a record of event information. inventory.sql: Node inventory report. Displays a snapshot of the current hardware and software inventory of a specified set of nodes, including provisioning parameters and current state parameters. resource_availability.sql: Resource availability report. Displays the amount and percentage of time that the resources (e.g., cards and ports) spent in the Enabled vs. Disabled state. service.sql: Domain service report. Displays a snapshot of all the services currently provisioned in the domain, including the current state for each service. servicectps.sql: Service endpoints report. Generates a report for service endpoints. service_availability.sql: Service availability report. Displays the amount and percentage of time that the service spent in the Enabled vs. Disabled state. ds1_facility_performance 1.sql: DS1 port performance monitoring report. Generates a performance monitoring report for DS1 ports. ds3_facility_performance.sql: DS3 port performance monitoring report. Generates a performance monitoring report for DS3 ports. e1_facility_performance.sql: E1 port performance monitoring report. Generates a performance monitoring report for E1 ports. e3_facility_performance.sql: E3 port performance monitoring report. Generates a performance monitoring report for E3 ports. ec1_facility_performance.sql: EC1 port performance monitoring report. Generates a performance monitoring report for EC1 ports. eos_performance.sql: EOS (Ethernet over SONET/SDH) port performance monitoring report. Generates performance monitoring report for an EOS port. ethernet_10ge_eq_performance.sql: Equipment monitoring performance report for 1-port 10GbE and 10-port GbE. Note: Equipment monitoring events are events that cannot be attributed to a specific port or service. For example, excessive traffic on a service or a count of discarded frames where the discards may be the result of improper service configuration. ethernet_eq_performance.sql: Equipment monitoring performance report for NGE cards. ethernet_facility_performance.sql: Ethernet port performance monitoring report. Generates a performance monitoring report for Ethernet ports. ethernet_svcport_performance.sql: Ethernet service port performance monitoring report. 1 To monitor performance on any resource, know how to use the performance monitoring templates. See Section 8 Maintenance and Testing, Chapter 1 Performance Monitoring, page 8-1. Page 2-28 Turin Networks Release TN4.0.x

Chapter 4 Administrative Tasks Using the Report Scheduler sdh_facility_performance.sql: SDH port performance monitoring report. sdh_vc11path_performance.sql: SDH VC-11 path performance monitoring report. sdh_vc12path_performance.sql: SDH VC-12 path performance monitoring report. sdh_vc_capacity_performance.sql: VC capacity performance report for SDH services. Generates a capacity monitoring report. sonet_facility_performance.sql: SONET port performance monitoring report. Generates a performance monitoring report for SONET ports. sonet_stspath_performance.sql: STS path performance monitoring report. Generates a performance monitoring report for STS paths. sonet_vtpath_performance.sql: VT path performance monitoring report. Generates a performance monitoring report for VT paths. sonet_vt_capacity_performance.sql: VT capacity performance report for SONET services. Generates a capacity monitoring report. t100_performance.sql: T100 performance monitoring report. Generates a performance monitoring report for T100 equipment. ta200_performance.sql: TransAccess 200 Mux performance monitoring report. Generates a performance monitoring report for TransAccess 200 Mux equipment. Note: To monitor performance on any resource, know how to use the performance monitoring templates. See Section 8 Maintenance and Testing, Chapter 1 Performance Monitoring, page 8-1. Report Source Filter: The system can filter reports based on the syntax entered in this field. If this field is left blank, the report will cover all nodes in the domain. For progressively specific reports, use the following syntax: NodeId/slotNumber where: NodeId is the user-defined name of the node. slotnumber is the slot number of the card in the shelf (e.g., s-12 for slot 12). For example, to filter reports on a specific slot of a specific node, enter only the NodeId and the slot number in this field (e.g., Node1). Report Period (hours): Time over which the report is generated, e.g., enter 4 to specify the report covers the last 4 hours. Used for the following reports: alert.sql event.sql performance.sql resource_availability.sql service_availability.sql Report Parameter 1: Used to specify the interval for the performance.sql report. Enter 0 to specify 15 minutes; enter 1 to specify 24 hours. Report Parameter 2: (Planned for future release.) Release TN4.0.x Turin Networks Page 2-29

TransNav GUI Guide, Section 2: Administrative Tasks Example Report Output Example Report Output An example event report is shown below. Figure 2-21 Example Event Report Command buttons are as follows: Print: Print the report. Save: Save the report to a comma-delimited text file. This can be opened with a spreadsheet program. Done: Close the report and return to the dialog box. Page 2-30 Turin Networks Release TN4.0.x

Chapter 4 Administrative Tasks Adding Customer Information Adding Customer Information Define customer profiles to associate with specific equipment, links, or services. You can associate a specific customer with specific equipment, links, or services using the Config tab for that resource. You can also associate a specific customer with a specific service by using the Service tab. You define a specific customer by clicking Add Customer or selecting Customer from the Admin menu. The Customer Information View dialog box displays. Figure 2-22 Customer Information View Dialog Box The Customer Information View dialog box allows you to enter the following customer-specific information: Customer Name Description: Use alphanumeric characters only. Do not use any other punctuation or special characters. Street City State Zip Phone Fax Contact Name Contact Phone Command buttons are as follows: Add: Add the customer to the Customer List box. Clear: Clear all information from the boxes. Done: Close the dialog box. Release TN4.0.x Turin Networks Page 2-31

TransNav GUI Guide, Section 2: Administrative Tasks Adding Customer Information Page 2-32 Turin Networks Release TN4.0.x

SECTION 2NETWORK SECTION 3 NETWORK Contents Chapter 1 Creating and Deleting Equipment Using Preprovisioning Auto-discovery and Preprovisioning................................ 3-1 Add a Node................................................... 3-3 Node Parameters.............................................. 3-4 Configure the Traverse SNMP Agent Parameters..................... 3-8 Delete a Node................................................. 3-11 Card (Module) Placement........................................ 3-11 Creating, Replacing, or Deleting a Card............................. 3-11 Add a Card................................................... 3-12 Delete a Card................................................. 3-13 Replace a Card................................................ 3-14 Creating or Deleting Links........................................ 3-16 Add a Link.................................................... 3-16 View Available Resources on a Link................................ 3-18 Delete a Link.................................................. 3-19 Chapter 2 Network Auto Discovery Network Auto Discovery......................................... 3-21 Static Route Information List...................................... 3-22 Chapter 3 Node Timing Pinouts................................................... 3-23 Provisioning Timing......................................... 3-23 Global Timing Options........................................... 3-24 External Timing................................................ 3-26 Line Timing................................................... 3-29 Line Facility Data............................................... 3-30 Reference List Options.......................................... 3-31 Derived Timing................................................ 3-32 Protection Switching External Timing References..................... 3-33 Protection Switching Line Timing References......................... 3-34 Chapter 4 DCC Tunnels DCC Tunnel Tab............................................... 3-35 Chapter 5 Configuring IP Quality of Service Release TN4.0.x Turin Networks Page i

TransNav GUI Guide, Section 3 Network Global Parameters Tab.......................................... 3-38 Static Classifier Tab............................................. 3-39 Dynamic Classifier Tab.......................................... 3-40 ACL Tab...................................................... 3-41 Statistics Tab.................................................. 3-43 List of Figures Figure 3-1 PreProvision New Node Dialog Box....................... 3-3 Figure 3-2 Node Configuration Screen.............................. 3-4 Figure 3-3 Admin Menu SNMP Configuration....................... 3-9 Figure 3-4 Node SNMP Configuration Screen........................ 3-9 Figure 3-5 Shelf View Add Card.................................. 3-12 Figure 3-6 Delete or Replace a Card............................... 3-13 Figure 3-7 Delete Failed Dialog Box................................ 3-14 Figure 3-8 Replace Card Failed Dialog Box.......................... 3-14 Figure 3-9 Provision New Link Dialog Box........................... 3-16 Figure 3-10 Map View Config Tab, Physical Links Screen.............. 3-17 Figure 3-11 Available Resources (SONET)........................... 3-18 Figure 3-12 Available Resources (SDH).............................. 3-19 Figure 3-13 Discovery Sources View Dialog Box....................... 3-21 Figure 3-14 Static Route Information List Dialog Box.................... 3-22 Figure 3-15 Node Global Timing Options............................. 3-24 Figure 3-16 Timing Tab, EXT Subtab................................ 3-26 Figure 3-17 Timing Tab Line Timing............................... 3-29 Figure 3-18 Derived DS1 References for Line Timing................... 3-32 Figure 3-19 Protection Switch External Timing References............... 3-33 Figure 3-20 Protection Switch Line Timing References.................. 3-34 Figure 3-21 DCC Tunnel Tab...................................... 3-35 Figure 3-22 IP QOS Configuration Panel Global Parameters Tab......... 3-38 Figure 3-23 IP QOS Configuration Panel Static Classifier Tab........... 3-39 Figure 3-24 IP QOS Configuration Panel Dynamic Classifier Tab......... 3-40 Figure 3-25 IP QOS Configuration Panel ACL Tab.................... 3-41 Figure 3-26 IP QOS Configuration Panel Statistics Tab................ 3-43 Page ii Turin Networks Release TN4.0.x

SECTION 3 NETWORK Chapter 1 Creating and Deleting Equipment Using Preprovisioning Introduction Auto-discovery and Preprovisioning Equipment in a network includes nodes, links, cards (modules), ports and external devices. This chapter describes how to create and delete equipment during the preprovisioning process. Auto-discovery and Preprovisioning, page 3-1 Add a Node, page 3-3 Node Parameters, page 3-4 Configure the Traverse SNMP Agent Parameters, page 3-8 Creating, Replacing, or Deleting a Card, page 3-10 Creating or Deleting Links, page 3-15 View Available Resources on a Link, page 3-17 Preprovisioning allows you to perform all configuration functions independent of service activation. Preprovisioning a network or network elements lets you plan for future configurations, facilitating rapid turn-up of new nodes and node expansions. Preprovision nodes on the Primary server. When the Primary server database is imported to the Secondary server, the preprovisioned node appears on the Secondary server. Using the TransNav management system, you connect directly to a Management Gateway Node (MGN). The management system communicates to the other nodes in the domain through the MGN using a data communications channel (DCC) between the nodes. Each node uses a process called auto-discovery to learn the addresses of all other nodes in its server domain. After you have commissioned a node with a name and an IP address, the management system discovers and manages all the nodes in the server domain without requiring any other preprovisioned information. Upon discovery of the equipment, the TransNav management server downloads the preprovisioned data to the node and builds the graphical representation of the equipment in Map View and Shelf View. If a piece of equipment has not been preprovisioned, it is assigned default parameters. To change parameters from the default values, see Section 5 Equipment Configuration. Release <IMPORT UNIQUE CHAPTER VARIABLES>Turin Networks Page 3-1

<IMPORT UNIQUE CHAPTER VARIABLES> Auto-discovery and Preprovisioning Page 3-2 Turin Networks Release <IMPORT UNIQUE CHAPTER VARIABLES>

Chapter 1 Creating and Deleting Equipment Using Preprovisioning Add a Node Add a Node In Map View, you can create or delete any node in the server domain. Use this information to help you create a node in or delete a node from the server domain. Nodes can later be grouped to make the network easier to manage. For more information, see Section 2 Administrative Tasks, Chapter 3 User Preferences, Grouping Nodes, page 2-18. Note: Turin recommends adding nodes on the Primary server. When the Primary server database is imported to the Secondary server, the preprovisioned node appears on the Secondary server. You can add a node in two ways: In Map View or Shelf View, select Add node from the Provisioning menu. In Map View, right-click the background image. Select Add node. The PreProvision New Node dialog box displays. Figure 3-1 PreProvision New Node Dialog Box Node Name: Enter the name of the node (maximum 50 characters; recommended maximum of 15 characters). Use alphanumeric characters or hyphens only. Do not use punctuation or any other special character in this field. Additionally, the node name is case sensitive. Verify the node name is identical to the node-id CLI parameter configured during node commissioning. Node Type: Click the arrow to display the options. Select one of the following options: 20 slots node (default) for the Traverse 2000 shelf 16 slots node for the Traverse 1600 shelf 6 slots node for the Traverse 600 shelf TE-100 for the TraverseEdge 100 shelf Operation Mode: Click the arrow to display the options. Select how the node functions in the network. ADM (default) if the node acts as an add-drop multiplexer (ADM) DCS-96 if the node is a single-shelf DCS application DCS-384 if the node is the matrix shelf in a DCS application DCS-IO if the node is an input/output shelf in a DCS application DCS-UPGR-96-IO if the node is being upgraded from a DCS-96 network element to a DCS-IO network element. MSAid Format: If this node is part of a DCS application, choose the MSAID format (preprovisioning only). No-MSAid MSAid-VT-Seq Release <IMPORT UNIQUE CHAPTER VARIABLES>Turin Networks Page 3-3

<IMPORT UNIQUE CHAPTER VARIABLES> Node Parameters MSAid-VT-GR253 MSAid-VTG-VT Command buttons are as follows: Add: Add the new node to the GUI. The new node displays in Map View in the upper left corner. Left-click the node, hold the mouse button down, drag it to the desired location and release the mouse button. Cancel: Cancel provisioning information and close the dialog box. Node Parameters You set the IP addresses, gateways, and mask on a node using the Command Line Interface (CLI) during the commissioning process. For details on setting these IP addresses, see one of the following references: Traverse Installation and Commissioning Guide, Section 11 Node Start-up and Commissioning Procedures. TraverseEdge 100 User Guide, Section 3 Installation and Configuration, Chapter 10 Node Start-up and Initial Configuration, page 3-69. To change the node attributes (other than the IP information), click the node in Map View and click the Config tab to display the Node Configuration screen. Figure 3-2 Node Configuration Screen The Node Configuration screen allows you to view and/or change the following node configuration information: Node ID 1 : A user-defined name of the node entered during node commissioning (CLI node-id parameter). This value can be alphanumeric characters only. Do not use punctuation, spaces, or special characters in this field. Additionally, the Node ID is case sensitive. This parameter is required to commission the node. Page 3-4 Turin Networks Release <IMPORT UNIQUE CHAPTER VARIABLES>

Chapter 1 Creating and Deleting Equipment Using Preprovisioning Node Parameters Node IP 1 : Displays the IP address of the node. This address is internal to a TransNav managed network and must be on a separate IP network from any other IP address provisioned on the node (BP DCN IP, EMS IP, and GCM {A B} IP). This address is required to commission the node. This address is also known as the Router ID in a data network environment. Turin recommends using 10.100.100.x where x is between 1 and 254. Use a unique number for each network node. Turin recommends that all Node IPs for all nodes in one network be on the same IP network for easier route management. Type: Displays one of the following options: 20 slots node for the Traverse 2000 shelf 16 slots node for the Traverse 1600 shelf 6 slots node for the Traverse 600 shelf TE-100 for the TraverseEdge 100 shelf Alarm Profile: Select from the list of defined alarm profiles (of type shelf). Default is default. Standard: Indicates the standard for this network element: ANSI_only, ITU_default, or ANSI_default. Location: Enter the location of the node. DCS: If this is part of a DCS application, this field displays the type of network element (set during node commissioning or preprovisioning) and how the MSAIDs are mapped on the network element. DCS-96 if the node is a single-shelf DCS application. DCS-384 if the node is the matrix shelf in a multi-shelf DCS application. DCS-IO if the node is an input/output shelf in a multi-shelf DCS application. DCS-UPGR-96-IO if the node is being upgraded from a DCS-96 network element to a DCS-IO network element. For explanations of the MSAID and MSAID formats, see Section 6 Creating DCS Applications. BP DCN IP 2 : Displays the IP address assigned to the Ethernet interface on the back of the Traverse shelf. This IP address must be on a separate network from any other IP address provisioned on the node (Node IP, EMS IP, and GCM {A B} IP). Enter an IP address if this node is connected to a management server (either directly or through a router). This address is required on each node that is connected or routed to a management server or on any node with a subtended device. 1 Set through the CLI during node commissioning. 2 Set through the CLI during network commissioning. For details on assigning these IP addresses, see the TransNav Management System Product Overview Guide, Section 2 Management System Planning, Chapter 3 IP Address Planning. Release <IMPORT UNIQUE CHAPTER VARIABLES>Turin Networks Page 3-5

<IMPORT UNIQUE CHAPTER VARIABLES> Node Parameters Turin recommends using a different subnet for each site. BP DCN Mask 2 : Displays the mask IP address for the node BP DCN IP. The value depends on site practices. BP DCN Gateway 2 : If the node is connected directly to a management server, this field is the address is the IP gateway of the management server. If there is a router between the management server and this node, this address is the IP address of the port on the router connected to the Ethernet interface on the back of the Traverse shelf. This parameter is required for each provisioned BP DCN IP. BP DCN MAC: Displays the MAC address of the BP DCN IP. GCM A IP: Displays the IP address of the GCM A Ethernet interface. GCM A Mask: Displays the mask IP address for the GCM A IP. GCM A Gateway: Displays the gateway IP address for the GCM A IP. GCM A MAC: Displays the MAC address of the GCM A IP. GCM B IP: Displays the IP address of the GCM B Ethernet interface. GCM B Mask: Displays the mask IP address for the GCM B IP. GCM B Gateway: Displays the gateway IP address for the GCM B IP. GCM B MAC: Displays the MAC address of the GCM B IP. EMS IP 2 : Displays the address that is the IP address of the TransNav management server to which this node is connected. This IP address must be on a separate network from any Node IP and GCM {A B} IP addresses. For in-band management, this address must be on or routed to the same network as the BP DCN IP of the management gateway node (the node with the physical connection to the management server). For out-of-band management, this address must be connected or routed to all BP DCN IP addresses. The value of this parameter depends on site practices. EMS Mask 2 : Displays the mask IP address for the TransNav management server to which this node is connected. EMS Gateway 2 : Displays the IP address of the port on the router connected to the Ethernet interface on the back of the Traverse shelf. This address is the same address as BP DCN Gateway. The above parameter is required for each EMS IP; the value depends on site practices. Remote ACO: Select to acknowledge an external alarm on the selected node. NTP (Network Time Protocol) IP 1 3 : Enter the IP address of the Primary server from which the node Time of Day is derived. Time of Day is used for performance monitoring and alarm and event logging. Page 3-6 Turin Networks Release <IMPORT UNIQUE CHAPTER VARIABLES>

Chapter 1 Creating and Deleting Equipment Using Preprovisioning Node Parameters NTP (Network Time Protocol) IP 2 3 : Enter the IP address of the Secondary server from which the node Time of Day is derived. Time of Day is used for performance monitoring and alarm and event logging. External Alarm 1 to External Alarm 16: The Power Distribution and Alarm Panel (PDAP) provides 16 environmental alarm inputs to report various environmental alarms to the General Control Module (GCM) card. Select from the list of environmental alarms: HITEMP: High temperature LWTEMP: Low temperature OPENDR: Door is open HIGHHUM: High humidity LOWHUM: Low humidity BATDSCHRG: Battery BATTERY: Battery failure LWBAVG: Battery power low POWER: Power failure GEN: Generator failure RECT: Rectifier failure RECTHI: Rectifier high temperature RECTLO: Rectifier low temperature CLFAIL: Cooling failure VENTN: Ventilation failure FIRE: Fire in the shelf! FLOOD SMOKE TOXICGAS LEAK PUMP: Pump failure Part Number: Displays the part number assigned to the node backplane. CLEI: Displays the Telcordia Common Language Equipment Identifier (CLEI) for the node backplane. Serial Number: Displays the unique serial number assigned to the node backplane. Time Zone: Sets the time and date stamp on alarms and events. Select from a list of time zones. There are five valid time zone locales for the United States: America/LosAngeles America/Phoenix America/Denver 3 For instructions on setting the management server as the primary NTP source, see the TransNav Management System Server Guide, Section 2 Management Server Procedures, Chapter 1 Creating the Management Servers, Set the Primary Management Server as the Primary NTP Source, page 2-5. Release <IMPORT UNIQUE CHAPTER VARIABLES>Turin Networks Page 3-7

<IMPORT UNIQUE CHAPTER VARIABLES> Configure the Traverse SNMP Agent Parameters America/Chicago America/New-York A complete listing of time zone locales world-wide is available at the following Web address www.bsdi.com/xdate. Customer Tag: Displays the Node-ID. ICI: Displays the ITU-T compliant International Common Identifier (ICI) of the node backplane. Module ID: An identifier assigned that designates the function of the node backplane. Proxy ARP: Select to make the node act as a proxy server for the IP subnet. Valid values are: Disabled, Enabled. Command buttons are as follows: Apply: Apply node configuration information. Cancel: Cancel the node configuration information and refresh the tab with the previously configured information. Configure the Traverse SNMP Agent Parameters Turin supports an SNMP agent directly on the Traverse system. The Traverse SNMP agent access is available on a physical node only; pre-provisioned support for the SNMP agent is unavailable. The Traverse SNMP agent port 161 sends and receives management data to the SNMP management stations. Note: There is no relationship between the TransNav management server and Traverse system SNMP agents. The configuration of the Traverse system SNMP agent (community strings and trap destinations) is not coordinated in any way. From Map View, select a node. From the Admin menu, click SNMP Configuration. Figure 3-3 Admin Menu SNMP Configuration Page 3-8 Turin Networks Release <IMPORT UNIQUE CHAPTER VARIABLES>

Chapter 1 Creating and Deleting Equipment Using Preprovisioning Configure the Traverse SNMP Agent Parameters The Node SNMP Configuration screen displays: Figure 3-4 Node SNMP Configuration Screen The Node SNMP Configuration screen allows you to view and change the following Traverse node SNMP configuration information: Node ID 4 : Displays the user-defined node name entered during node commissioning. Node IP 4 : Displays the node IP address entered during node commissioning. Read Community: An alphanumeric character string that provides an SNMP management station with read-only access to the Traverse SNMP agent. Public is the default string. Note: For each of the alphanumeric character string parameters, there is a corresponding Confirm parameter to check for matching string entry. Write Community: An alphanumeric character string that provides an SNMP management station with read and write access to the Traverse SNMP agent. Public is the default string. Trap Destination [1 through 4]: Enter the unique IP address assigned by a network administrator of the SNMP management station to receive management data. There are up to four possible trap destinations. Trap Destination [1 through 4] Community: An alphanumeric character string (corresponding to the Read or Write Community string) that provides the Trap Destination Community with specific access rights to the Traverse SNMP agent. Public is the default string. Trap Destination [1 through 4] Port Number: The SNMP management station port that receives management data from the Traverse SNMP agent. The default is 162. The command buttons are as follows: Apply: Click Apply to save changes and return to the main screen. Done: Click Done to cancel any changes and return to the main screen. 4 Set through the CLI during node commissioning. Release <IMPORT UNIQUE CHAPTER VARIABLES>Turin Networks Page 3-9

<IMPORT UNIQUE CHAPTER VARIABLES> Delete a Node Delete a Node Card (Module) Placement Creating, Replacing, or Deleting a Card Nodes can be deleted from the network in two ways: in Map View, right-click the node and select Delete Node; in the navigation tree, right-click the node and select Delete Node. A dialog box displays which reads Are you sure you would like to delete Node [node name]? Click Yes to proceed with the delete command or No to cancel the request. If you delete a preprovisioned node from a Secondary server GUI, it remains on the Primary server. The node is rediscovered by the management system during the auto-discovery process and appears on the Secondary server the next time the Primary server database is imported. To completely delete the preprovisioned node, you must also delete it from the Primary server. In Shelf View, you can add a card to a slot and configure interfaces for a card that is not physically inserted into the shelf. Review the guidelines listed in the Traverse Installation and Commissioning Guide, Section 12 Appendices, Appendix A Card Placement Planning and Guidelines, page 12-1 before you add a card to, or replace a card in, a shelf. Use the information in this topic to help you add, delete, or replace a card. Add a Card (Module), page 3-11 Delete a Card (Module), page 3-12 Replace a Card, page 3-13 Page 3-10 Turin Networks Release <IMPORT UNIQUE CHAPTER VARIABLES>

Chapter 1 Creating and Deleting Equipment Using Preprovisioning Add a Card (Module) Add a Card (Module) From Shelf View, right-click the slot into which you want to add a card. Figure 3-5 Shelf View Add Card Select a card name. The card, with its associated ports, displays in the selected slot. Release <IMPORT UNIQUE CHAPTER VARIABLES>Turin Networks Page 3-11

<IMPORT UNIQUE CHAPTER VARIABLES> Delete a Card (Module) Delete a Card (Module) You can delete a card from the user interface. The management system rediscovers a card physically installed in a shelf during the auto-discovery process. 1. Select the card. 2. Click the lock icon in the bottom left corner to lock the administrative state. 3. Click Apply. 4. Right-click the card and click Delete Card. 1 4 2 3 Figure 3-6 Delete or Replace a Card A dialog box displays which reads Are you sure you would like to delete slot (number)-[card type]? Click Yes to proceed with the delete command or No to cancel the request. Page 3-12 Turin Networks Release <IMPORT UNIQUE CHAPTER VARIABLES>

Chapter 1 Creating and Deleting Equipment Using Preprovisioning Replace a Card A card can only be deleted if its administrative state is Locked. If its administrative state is Unlocked, a Delete Failed dialog box displays. Figure 3-7 Delete Failed Dialog Box Follow the instructions in the dialog box to lock the administrative state, then reselect Delete Card. Replace a Card To replace a card, use the following steps: 1. Select the card. 2. Click the lock icon in the bottom left corner to lock the administrative state. 3. Click Apply. 4. Right-click the card and click Select Replace with [card type] Cards, then select Replace with [specific card type]. See Figure 3-6 Delete or Replace a Card, page 3-12. If the administrative state of a card is Unlocked, a Replace Card Failed dialog box displays. Figure 3-8 Replace Card Failed Dialog Box Follow the instructions in the dialog box to lock the administrative state, then reselect Replace with [card type] Cards. Release <IMPORT UNIQUE CHAPTER VARIABLES>Turin Networks Page 3-13

<IMPORT UNIQUE CHAPTER VARIABLES> Replace a Card Page 3-14 Turin Networks Release <IMPORT UNIQUE CHAPTER VARIABLES>

Chapter 1 Creating and Deleting Equipment Using Preprovisioning Add a Link Creating or Deleting Links Add a Link A link represents a fiber optic connection between two nodes. As a visual aid to preprovisioning services, use the Add Link command to add a physical (transport) link from one node to another. Links must be between ports of the same type; for example, link an OC-48 port in one shelf to an OC-48 port in another shelf. Use the information in the topics (Add a Link, Delete a Link) to add or delete transport links in the network. To review available resources on a link, see View Available Resources on a Link, page 3-17. You can add a link in three ways: In Map View or Shelf View, click the Provisioning menu, then click Add Link. In Map View, click Config tab, click a link, and then click Add. In Map View, right-click in an area not occupied by a node. Click Add Link on the shortcut menu. The Provision New Link dialog box displays. Figure 3-9 Provision New Link Dialog Box The Provision New Link dialog box allows you to configure the following information: Type: Select one of the following: OC OC3 OC12 OC48 OC192 STM STM1 STM4 STM16 STM64 Use this field during preprovisioning or when DCC is not used to discover the network to set the Type of link to be used to create the link. Source: Node: Select the source node from the list of nodes in the domain. Port: Select from the list of ports in the source node corresponding to the Type selected above. Remember that the East port on one node is physically connected to the West port of the next node. Release <IMPORT UNIQUE CHAPTER VARIABLES>Turin Networks Page 3-15

<IMPORT UNIQUE CHAPTER VARIABLES> Add a Link Destination: Node: Select the destination node from the list of nodes in the domain. Port: Select from the list of ports in the destination node corresponding to the Type selected above. Remember that the East port on one node is physically connected to the West port of the next node. Customer Tag. See Section 2 Administrative Tasks, Chapter 4 Administrative Tasks, Adding Customer Information, page 2-31. Click Add. Links for nodes in the same group display in Map View as a gray line. Links between nodes and groups at a different level or with a different background image display as going off the page; the group name and a small Group image (called an off page connector) display: Off page connector Figure 3-10 Map View Config Tab, Physical Links Screen Click the gray line, then click the Config tab. The link appears in the Physical Links screen with its Source, Destination, Type, Operational State, and Customer Tag listed. The Physical Links screen allows you to view the following information: Source: Displays the source of the link in the format [NodeName]-[slot number]-[port number]. Destination: Displays the destination of the link in the format [NodeName]-[slot number]-[port number]. Type: Displays one of the following as the data rate of the link: OC-3/STM-1 OC-12/STM-4 OC-48/STM-16 OC-192/STM-64 Page 3-16 Turin Networks Release <IMPORT UNIQUE CHAPTER VARIABLES>

Chapter 1 Creating and Deleting Equipment Using Preprovisioning View Available Resources on a Link Operational State: Displays whether the link physically exists. Enabled. Active physical fiber Disabled. Preprovisioned link Command buttons are as follows: Add: Preprovision a new link to the network. Bandwidth: Select a link in the list, then click Bandwidth to see the available bandwidth on this link. The Available Resource dialog box displays. See View Available Resources on a Link, page 3-17. Services: Select a link in the list, then click Services to see a list of activated services currently using the link. Delete: Delete a preprovisioned link in the network. View Available Resources on a Link In Map View, click a link, then click the Config tab. Select a link from the link list, then click Bandwidth. The Available Resources dialog box displays. Figure 3-11 Available Resources (SONET) Release <IMPORT UNIQUE CHAPTER VARIABLES>Turin Networks Page 3-17

<IMPORT UNIQUE CHAPTER VARIABLES> Delete a Link. Figure 3-12 Available Resources (SDH) This box is a graphical representation of the available resources on the link. The colors mean the following: Magenta: The resource is unavailable. Purple: Currently selected resource. Light yellow: The STS or STM resource is available. Dark yellow: The VT or low order VC resource is available. OK: Click OK to close the dialog box and return to the main screen. Delete a Link To delete a link from Map View, click the Config tab and select the physical link to be removed. Click Delete. A link which physically exists in the domain is rediscovered by the management system during the auto-discovery process. Page 3-18 Turin Networks Release <IMPORT UNIQUE CHAPTER VARIABLES>

SECTION 3NETWORK Chapter 2 Network Auto Discovery Introduction Network Auto Discovery This chapter describes the following administrative functions selected through the Admin menu on the TransNav management system graphical user interface (GUI): Network Auto Discovery, page 3-19: Define the gateway node(s) in a domain. Static Route Information List, page 3-20: Add static routes to a node for management IP traffic. Select Discovery from the Admin menu to display the Discovery Sources View dialog box. Figure 3-13 Discovery Sources View Dialog Box Enter the node IP address (node-ip) of the management gateway node in the Host Name box. You can enter the node-ip of multiple nodes. For out-of-band management, each node must be set as a gateway node. For more information on in-band and out-of-band management, see the TransNav Management System Product Overview Guide, Section 2 Management System Planning, Chapter 3 IP Address Planning. Command buttons are as follows: Add: Add the node-ip in the Host Name box to the Discovery List box. Clear: Clear entry in Host Name box. Delete: Delete Host Name selected in the Discovery List box. Done: Close the Discovery Sources View dialog box. Release TN4.0.x Turin Networks Page 3-19

TransNav GUI Guide, Section 3: Network Static Route Information List Static Route Information List The IP Static Route Information List dialog box allows you to add static routes to a node for management of IP traffic. Click a node in Map View. Select IP Static Route Information from the Admin menu to display the Static Route Information List dialog box. Figure 3-14 Static Route Information List Dialog Box Destination: Enter the destination IP address for this node. Gateway: Enter the gateway IP address for this node. Mask: Enter the mask IP address for this node. Export: Select to export the IP information to all nodes in the domain. Route parameters will automatically be adjusted on all other nodes. Command buttons are as follows: Add: Add the information in the dialog box to the database. Update: Update the database with newly entered information. Clear: Clear entries in Destination, Gateway, Mask, and Export boxes. Delete: Delete the static route selected in the upper box. Done: Close the Static Route Information List dialog box. Page 3-20 Turin Networks Release TN4.0.x

SECTION 3NETWORK Chapter 3 Node Timing Introduction Configure the timing source for each node in a server domain. For each node, you can configure either external timing or line timing from OC, EC3, or STM interfaces. Typically, one node in the central office receives redundant timing signals from an external source. This node becomes the primary timing source for the network. The other nodes receive the timing reference from optical interfaces. The primary reference is the shortest route to the primary timing source. Synchronized primary and secondary timing inputs from the external timing source are connected at the main backplane and bridged to the shelf s system control cards. This chapter describes the following information: Global Timing Options, page 3-22 External Timing, page 3-24 Line Timing, page 3-27 Derived Timing, page 3-30 Protection Switching External Timing References, page 3-31 Protection Switching Line Timing References, page 3-32 Pinouts 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 the Traverse Installation and Commissioning Guide or TraverseEdge 100 User Guide. Provisioning Timing For detailed procedures to configure timing, see one of the following references: Traverse Provisioning Guide, Section 1 Configuring the Network, Chapter 4 Configuring Network Timing, page 1-13. TraverseEdge 100 User Guide, Section 4 Configuring the Network, Chapter 2 Configuring Network Timing, page 4-9. Release TN4.0.x Turin Networks Page 3-21

TransNav GUI Guide, Section 3: Network Global Timing Options Global Timing Options Configure global timing options at each node in the server domain. From Shelf View, click the Timing tab to configure global timing options for a node. Timing tab Subtabs Global options Figure 3-15 Node Global Timing Options The Timing tab allows you to view and set the following information: Standard: Displays the timing standard for the shelf: This value is set during node commissioning through the CLI (exec node commission standard). ANSI. For North American operations. ITU. For operations outside of North America. You must unprovision all currently provisioned timing references before you can switch between the ANSI and ITU standards. 1. Apply a lockout command to each reference on the reference list. (See Protection Switching External Timing References, page 3-31.) 2. Clear the reference source priority. Note: All currently provisioned references must be unprovisioned before changing the timing standard between ITU and ANSI. Unprovisioning a reference involves two separate steps: 1. Apply a lockout to each reference on the reference list, then 2. Clear the reference source priority and press Apply (in the case of line timing, also clear the line facility reference number). Timing Mode: External Time (default): Receive timing from standalone synchronization equipment (SASE) or a building integrated timing supply (BITS) reference. To configure external timing interfaces, see External Timing, page 3-24. Line Time: Receive timing signal from an OC line interfaces. To configure line timing, see Line Timing, page 3-27. Quality of RES (available if Standard is ANSI): Assigns a quality level for the RES message. Select one of the following options: PRS: Primary reference source. Equivalent to Stratum 1. Sync-Trace Unknown: Synchronization traceability unknown. Page 3-22 Turin Networks Release TN4.0.x

Chapter 3 Node Timing Global Timing Options Stratum 2 Transit Node Stratum 3E Stratum 3 SONET Min Clock Stratum 4E Stratum 4 Don t Use for Sync (default) Revertive: Select for revertive timing. Clear for non-revertive timing. In revertive timing, if the timing signal is lost from the highest priority timing source, the signal is received from the second priority timing source. If the highest priority timing source then becomes available, revertive timing switches back to the highest priority timing source. In non-revertive timing, timing does not switch back to the highest priority timing source when it becomes available. External Out Enable: Enables or disable derived references. Derived timing is the process of providing a timing reference from a line interface and sending it to an external clock. Select: This node generates a timing signal to an external clock. Clear (default): This node does not generate a timing signal to an external clock. Ignore SSMR: Ignore the synchronization status message received. Select (default): The node will use provisioned priorities to select the best timing reference Clear: The node will use SSM level to prioritize timing references. Clock Mode: Displays the state of the timing sub-system. Free Run: Used after a power-on-reset before network synchronization is achieved. PreLock: After a valid reference is found, the timing sub-system enters this state for a maximum of 100 seconds. If the system cannot lock to a reference within 100 seconds, it reverts to Free Run mode until another source is selected. Locked: Used when an input reference source has been selected and the system locks onto the reference as a primary source. Holdover: Used when the system has acquired a stable frequency, but the selected sources are unavailable. Holdover Quality: Displays the clock quality (Stratum 3) of the local oscillator on the GCM cards. WTR Time: Time, in minutes, the system will wait before considering the primary timing source as valid again. This time ensures that a previously failed synchronization source is fault-free before it is considered available. Enter a value between 1 and 12. The value 0 disables this function. The Reference List section depends on the value in the Timing Mode parameter. If Timing Mode is External, see External Timing, page 3-24. If Timing Mode is Line, see Line Timing, page 3-27. Release TN4.0.x Turin Networks Page 3-23

TransNav GUI Guide, Section 3: Network External Timing Ext. Command: Displays any commands performed on timing source (Cleared, Lockout, Forced, or Manual). See Protection Switching External Timing References, page 3-31. The check box beside the Ext. Command column indicates the active reference. External Timing There are two external references for each node: EXT-A and EXT-B. For redundancy, they both have the same configuration. If both references fail, the node maintains timing from the internal Stratum 3 oscillator. In Shelf View, click the Timing tab, then click the EXT subtab. 1. Click the Timing tab 2. Click the EXT subtab Figure 3-16 Timing Tab, EXT Subtab The EXT subtab allows you to view and configure the following parameters: Mode: Select one of the following external timing modes: T1 (default if Standard is ANSI): The external clock is a dedicated DS1 port. E1 (default if Standard is ITU): The external clock is a dedicated E1 port. 2 MHz Clock 64 KHz Composite Clock Line Coding (available if Mode is T1): Defines the line coding technique used for performance monitoring at the line layer. Select one of the following options: AMI (default): Alternate Mark Inversion. HDB3: High Density Bipolar 3 (default). B8ZS: bipolar 8-zero substitution. 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. If Mode is T1, select one of the following options: PRC: Primary reference clock Synch-Trace Unknown Stratum 2 Transit Node Page 3-24 Turin Networks Release TN4.0.x

Chapter 3 Node Timing External Timing Stratum 3E Stratum 3 SONET Minimum Clock (default). 2 ppm clock Stratum 4e Stratum 4 Don t use for sync If Mode is E1, select one of the following options: SSUA (available if Mode is E1): Synchronization supply unit type A. Transit. SSUB (available if Mode is E1): Synchronization supply unit type B. Local. SEC (available if Mode is E1): SDH equipment clock. DUS (available if Mode is E1): Do not use for synchronization. Legacy networks that don t support SSM are considered DUS. Don t use for sync. SSM Not Supported by ESF (if Framing is Esf): Check the box if the synchronize status message is not supported by the ESF framing format. Framing: The framing format used by the external clock. If Mode is T1, select one of the following values: Esf (default): Extended super frame. Sf: Superframe If Mode is E1, select one of the following values: Basic Frame (default): The timing interface detects and generates the Basic frame format per ITU-T Rec G.704/2.3 and G.706/4.1.2. This format does not support the SSM. Multi-Frame: The timing interface detects and generates CRC-4 Multi-frame format per ITU-T Rec G.706/4.2. This format supports the SSM. LineBuildOut: Line build out is based on the attenuation required for the circuit. If Mode is T1, select one of the following: Long Haul 0dB Long Haul 7.5dB Long Haul 15dB Long Haul 22.5dB Long Haul Tr62411 0dB Short Haul 110ft (default) Short Haul 220ft Short Haul 330ft Short Haul 440ft Short Haul 550ft Short Haul 660ft Short Haul Tr62411 110ft Short Haul Tr62411 220ft Short Haul Tr62411 330ft Short Haul Tr62411 440ft Release TN4.0.x Turin Networks Page 3-25

TransNav GUI Guide, Section 3: Network External Timing Short Haul Tr62411 550ft Short Haul Tr62411 660ft Read only if Mode is T1: 120 Ohm Ignore LOF (available if Mode is T1): Select (default) to ignore LOF (Loss of Frame) alarms. Clear to receive LOF alarms. SSM Sa Bit (available if Mode is E1): Select one of the following: BIT_SA4 (default) BIT_SA5 BIT_SA6 BIT_SA7 BIT_SA8 EXT-A Assigned SSMR, EXT-B Assigned SSMR: 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. Auto (default). Reference: External references are listed as Ext-A and Ext-B. Adm. State: Click the lock icon to change the administrative state of the timing source: Timing signal is unlocked and available for use. When Apply is clicked, the operational state is enabled. Timing signal is locked and unavailable for use (default). When Apply is clicked, the operational state is disabled. Status: Indicates status of external reference signal: Valid, OOB (Out of Band), or NOACT (Not active/out of Band). SSMR: Displays synchronization status messages received by this external reference. SSMT: Displays synchronization status messages transmitted by this external reference. WTR CLR. Click this button so the system immediately considers a source as a valid source (instead of waiting for the time specified in WTR Time parameter). Command buttons are as follows: Apply: Apply timing source information. After timing source information is applied, button turns gray. Cancel: Do not apply timing source information. Page 3-26 Turin Networks Release TN4.0.x

Chapter 3 Node Timing Line Timing Line Timing You can establish up to four line timing sources based on your network requirements 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. Note: Timing is restricted to a single port at any time for OC3 or STM1 cards. The node uses the priority 1 reference unless there is a failure on that reference. If there is a failure, the node switches to the next priority. If all of the references fail, the node maintains timing from the internal Stratum 3 oscillator. You can configure line timing sources (from OC-N ports only) and perform switch commands on the Timing tab. Line Time Mode Line Facility Data Reference List Options Check mark indicates active reference Figure 3-17 Timing Tab Line Timing The timing screen dynamically changes when you select Line Time in the Timing Mode parameter. Line Facility Data, page 3-28 explains the information in the Line Facility area. Reference List Options, page 3-29 explains the information in the Reference List area. Release TN4.0.x Turin Networks Page 3-27

TransNav GUI Guide, Section 3: Network Line Facility Data Line Facility Data The Line Facility area on the Timing screen allows you to view or configure the following information: Reference: You can provision up to four line timing references per node depending on your network requirements and number of OC interfaces per node. Label the sources as Reference 1, Reference 2, Reference 3, and Reference 4. Note: Timing is restricted to a single port at any time for OC3 or STM1 cards. Source: Select from the list of available ports (SONET or STM interfaces only). Status (read only): Indicates status of timing signal. Displays one of the following states: Valid: Valid source and system can use this reference. OOB: Out-of-Band alarm. The frequency is not within expected range. NOACT: No activity alarm. The system cannot detect a signal. PLL: Phase lock alarm. The system cannot lock to this reference. SSMR (read only): Synchronization status messages received by this interface. Displays one of the following messages: 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. Synch-Trace Unknown Stratum 2 Transit Node Stratum 3E Stratum 3 SONET Minimum Clock (2 ppm clock) Stratum 4/4e Stratum 4/4e Don t use for sync (default) Signal Fail Present None SSMT (read only): Synchronization status messages transmitted by this interface. Displays one of the following messages: PRC: Primary reference clock. SSUA: Synchronization supply unit type A. Transit. SSUB: 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. Synch-Trace Unknown Stratum 2 Page 3-28 Turin Networks Release TN4.0.x

Chapter 3 Node Timing Reference List Options Transit Node Stratum 3E Stratum 3 SONET Minimum Clock (2 ppm clock) Stratum 4/4e Stratum 4/4e Don t use for sync (default) Signal Fail Present None WTR CLR (command button): Click this button so the system immediately starts to qualify a source as a valid source (instead of waiting for the time specified in WTR Time parameter). Reference List Options The Reference List area on the Timing screen allows you to view and configure the following information: Priority 1, Priority 2, Priority 3, Priority 4: Select the line timing priority for this interface from one of the following options: no_reference (default) Reference 1 (highest) Reference 2 Reference 3 Reference 4 (lowest) Ext. Command: Displays any commands performed on line timing signal. See Protection Switching Line Timing References, page 3-32. The check box beside the Ext. Command column indicates the active reference. Command buttons are as follows: Apply: Apply timing source information. After timing source information is applied, the button turns gray, Cancel: Do not apply timing source information. Release TN4.0.x Turin Networks Page 3-29

TransNav GUI Guide, Section 3: Network Derived Timing Derived Timing Derived timing is the process of providing a timing reference from a line interface and sending it to an external clock. The Traverse can generate a timing signal to a DS1 multi-frame, a T1 ESF, or a 2 MHz external reference. In Shelf View, click the Timing tab. Select External Out Enabled Figure 3-18 Derived DS1 References for Line Timing Select the External Out Enabled check box to enable derived timing. Line Facility and Reference List options appear on the screen. Under Line Facility, select up to four OC interfaces as timing references. The port needs to be enabled (unlocked administrative state). See Line Facility Data, page 3-28 for details on this area. Under Reference List, select the priority for each line reference, then select a reference in order of priority to generate a signal to EXT-A and EXT-B: no_reference (default): reference is not used. Reference 1 (highest) Reference 2 Reference 3 Reference 4 (lowest) Ext. Command: Displays any commands performed on the references. See Protection Switching Line Timing References, page 3-32. Page 3-30 Turin Networks Release TN4.0.x

Chapter 3 Node Timing Protection Switching External Timing References Protection Switching External Timing References In Shelf View, click the Timing tab. Select an external command from the drop down menu beside each line reference. Figure 3-19 Protection Switch External Timing References Select one of the following commands: Lockout: Lock out timing source. Force: Perform a forced switch to this timing source. Manual: Perform a manual switch to this timing source. Cleared: Clear command. Release TN4.0.x Turin Networks Page 3-31

TransNav GUI Guide, Section 3: Network Protection Switching Line Timing References Protection Switching Line Timing References In Shelf View, click the Timing tab. Select an external command from the drop down menu beside each line reference. Figure 3-20 Protection Switch Line Timing References Select one of the following commands: Lockout: Lock out timing source. Force: Perform a forced switch to this timing source. Manual: Perform a manual switch to this timing source. Clear: Clear command. Page 3-32 Turin Networks Release TN4.0.x

SECTION 3NETWORK Chapter 4 DCC Tunnels Introduction DCC Tunnel Tab 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 or STM interface to connect third-party equipment transparently over a network of Traverse nodes. Tunnel a third-party DCC through the network using the section DCC bytes of the associated optical interface. See Traverse Provisioning Guide, Section 1 Configuring the Network, Chapter 5 Creating DCC Tunnels, page 1-23 for the procedures and guidelines to tunnel third-party DCC bytes. In a Traverse Shelf View, click the DCC Tunnel tab to display a list of DCC tunnels configured on the node. Figure 3-21 DCC Tunnel Tab The column headings on the DCC Tunnel tab are: TunnelId: The system-assigned identification for the DCC tunnel. Source Port: The source port for the DCC tunnel. Source: The source path for the DCC tunnel. If Control Data is enabled for this interface, the available paths for DCC tunnelling start at 4. If Control Data is disabled for this interface, the available paths start at 1. Destination Port: The destination port for the DCC tunnel. Destination: The destination path for the DCC tunnel. The available paths start at 4. Release TN4.0.x Turin Networks Page 3-33

TransNav GUI Guide, Section 3: Network DCC Tunnel Tab Status: Can be one of the following values: Provisioned: The DCC tunnel is provisioned on this node, but not activated. Activated: The DCC tunnel is provisioned and is carrying DCC traffic. Act Failed: The activation failed. The reason displays in the Last Error column. De Act Failed: The deactivation failed. The reason displays in the Last Error column. Last Error: Displays the reason for a failure. If there are no failures, the field is blank. Command buttons are as follows: New: Add a new DCC tunnel to the node. Clear all new: Clear the DCC tunnels you have just provisioned. Add all new: Add the DCC tunnels you have just provisioned to the list of DCC tunnels on the node. Delete: Delete selected DCC tunnel from the node. Activate: Activate the selected tunnel on the node to carry third-party DCC traffic. Deactivate: De-activate the selected the tunnel on the node. This port will stop carrying third-party DCC traffic. Page 3-34 Turin Networks Release TN4.0.x

SECTION 3NETWORK Chapter 5 Configuring IP Quality of Service Introduction Use IP QoS (IP Quality of Service) to allow or block traffic from certain IP hosts or networks based on entries made in an access control list (ACL). The ACL is searched when IP packets are received from a DCC or backplane DCN. IP packets are dropped or forwarded based on the ACL conditions set. Outgoing messages are maintained in a classifier table and can be prioritized as High Priority or Best Effort. IP packets originating from the TransNav management server or other Traverse/TE-100 nodes are given High Priority status. IP packets originating from third-party vendor equipment are prioritized as Best Effort unless determined to be High Priority in the Classifier list. Important: Use extreme caution when making ACL entries. The TransNav management system uses the multicast address 224.0.0.5 for OSPF messaging. Any ACL entry that blocks this multicast address or the IP addresses of the TransNav management server(s) or the Traverse nodes will cause link failure between the Traverse nodes and/or the TransNav server(s). Turin strongly recommends that this IP address not be blocked. For more information on internet multicast addresses, see http://www.iana.org/assignments/multicast-addresses. This chapter contains the following topics: Global Parameters Tab, page 3-36 Static Classifier Tab, page 3-37 Dynamic Classifier Tab, page 3-38 ACL Tab, page 3-39 Statistics Tab, page 3-41 See the TransNav Management System Product Overview Guide, Section 2 Management System Planning, Chapter 3 IP Address Planning, page 2-11 for information and procedures on provisioning IP Quality of Service. Release TN4.0.x Turin Networks Page 3-35

TransNav GUI Guide, Section 3: Network Global Parameters Tab Global Parameters Tab Use the Global Parameters tab to enable IP Quality of Service, set the percentage of available bandwidth for the High Priority and Best Effort queues, and set the weighted value of the High Priority queue. In Traverse Map View, click a node. From the Admin menu, select IP QOS Configuration. The IP QoS configuration panel dialog box appears. Figure 3-22 IP QOS Configuration Panel Global Parameters Tab The Global Parameters tab allows the user to enter the following parameters: IPQOS Feature Enable: Select to enable IP QoS. High Priority Q Size [1...100]: Define the percentage of available bandwidth for the queue size of high priority packets. The default is 100%. Best Effort Priority Q Size [1...100]: Define the percentage of available bandwidth for queue size of best effort priority packets. The default is 100%. High Priority Q Weight [51...100]: Define the weighted fair queuing value of the high priority queue. The default is 80%. This indicates that 80% of the bandwidth will be reserved for the high priority queue. Command buttons are as follows: Apply: Click to save the changes. Cancel: Click to clear the fields and replace the default values. Done: Click to save the changes and close the dialog box. Page 3-36 Turin Networks Release TN4.0.x

Chapter 5 Configuring IP Quality of Service Static Classifier Tab Static Classifier Tab Use the Static Classifier tab to add and maintain individual IP addresses and corresponding subnet masks of third-party vendor equipment in your network. By default, these entries have a Best Effort service level. In the IP QOS configuration panel dialog box, click the Static Classifier tab. Figure 3-23 IP QOS Configuration Panel Static Classifier Tab This tab allows the user to view and configure the following parameters: IP Address: Enter a single static IP address. Subnet Mask: Enter the corresponding Subnet Mask for the IP address. Service Level: Click this field to enter the service level of the IP address. Select one of the following values: HiPriority BestEffort (default) Command buttons are as follows: New: Click to enter a new static IP Address. Enter the IP Address and corresponding Subnet Mask in the fields that appear. Add: Click to save the changes and add the IP Address and Subnet Mask to the list. Delete: Select an IP Address and click Delete to remove the IP Address from the list. Cancel: Click to clear the fields. Done: Click to save the changes and close the dialog box. Release TN4.0.x Turin Networks Page 3-37

TransNav GUI Guide, Section 3: Network Dynamic Classifier Tab Dynamic Classifier Tab The Dynamic Classifier tab contains the individual IP addresses and corresponding subnet masks of provisioned equipment, such as the TransNav management server. The list is automatically updated when nodes are inserted or removed from the network, and is the same for every Traverse node in the network. By default, these entries have a High Priority service level. In the IP QOS configuration panel dialog box, click the Dynamic Classifier tab. Figure 3-24 IP QOS Configuration Panel Dynamic Classifier Tab Command buttons are as follows: Refresh: Refreshes the list of existing dynamic IP addresses. Done: Close the dialog box and return to the main screen. Page 3-38 Turin Networks Release TN4.0.x

Chapter 5 Configuring IP Quality of Service ACL Tab ACL Tab This tab allows users to set the IP forwarding action based on the access control list (ACL) thus allowing traffic from specific IP hosts or networks to be permitted or blocked. The ACL can contain 100 entries. Important: When enabling the IP QoS feature, Turin strongly recommends creating the following ACL entries before any other ACL entries are created. 1. Create one Permit ACL entry for each EMS server. 2. Create one (or more, as needed) Permit ACL entry to cover the entire IP address range of Traverse nodes. 3. Create one Permit ACL entry for the OSPF multicast address (224.0.0.5). These ACL entries will guard against subsequent ACL range entries from possibly interfering with normal operation. In the IP QOS configuration panel dialog box, click the ACL tab. Figure 3-25 IP QOS Configuration Panel ACL Tab The user can view and configure the following parameters: IP Address: Enter the IP Address to be added to the access control list. Wildcard Mask: Enter the wildcard (ACL) mask for the IP address. Control: Double-click this field to enter the ACL control permission for the IP Address. Select one of the following values: Deny Permit Release TN4.0.x Turin Networks Page 3-39

TransNav GUI Guide, Section 3: Network ACL Tab Command buttons are as follows: New: Click to add a new IP address to the access control list. Edit the fields that appear. Add: Click Add to add the new IP address and corresponding wildcard (ACL) mask to the access control list. Delete: Remove the selected IP address from the list. Cancel: Cancel any changes and return to the main screen. Page 3-40 Turin Networks Release TN4.0.x

Chapter 5 Configuring IP Quality of Service Statistics Tab Statistics Tab This tab allows users to see statistical information for the amount of High Priority and Best Effort traffic handled and traffic dropped from the queues based on the current settings in the Global Parameters tab. In the IP QOS configuration panel dialog box, click the Statistics tab. Figure 3-26 IP QOS Configuration Panel Statistics Tab The user can view the following parameters: IP HPQ Usage: The number of packets in the High Priority IP queue. IP BEQ Usage: The number of packets in the Best Effort IP queue. IP ACLPKT Drop: The number of packets dropped from the IP ACL packet. IP HPQPKT Drop: The number of packets dropped from the IP High Priority queue. IP BEQPKT Drop: The number of packets dropped from the IP Best Effort queue. Command buttons are as follows: Reset: Reset the current statistics to zero. Refresh: Refresh the current information. Done: Close the dialog box and return to the main screen. Release TN4.0.x Turin Networks Page 3-41

TransNav GUI Guide, Section 3: Network Statistics Tab Page 3-42 Turin Networks Release TN4.0.x

SECTION 4PROTECTION SWITCHING SECTION 4 PROTECTION SWITCHING SECTION 4 Contents Chapter 1 BLSR and MS-SPRing Protection Groups Create a BLSR or MS-SPRing Protection Group...................... 4-1 Synchronize Status............................................. 4-4 Operations Menu............................................... 4-4 Protection Switch Commands..................................... 4-5 Protection Switch Request Priorities................................ 4-5 Squelch Table................................................. 4-6 Updating a Topology (Adding a Node).............................. 4-7 Chapter 2 UPSR and SNCP Ring Protection Groups Create a UPSR or SNCP Ring.................................... 4-9 Ring Synchronize Status......................................... 4-11 SNCP/UPSR Protection Switch Commands.......................... 4-11 Synchronizing, Editing, and Deleting Configured Protection Rings......... 4-12 Updating a Topology (Adding a Node).............................. 4-13 Chapter 3 Equipment Protection Groups Create an Equipment Protection Group............................. 4-15 Equipment Protection Switch Commands............................ 4-18 Protecting Card Commands...................................... 4-18 Working Card Commands........................................ 4-18 Request Priorities for Equipment Protection.......................... 4-19 Chapter 4 1+1 MSP/APS Protection Groups Create a 1+1 MSP/APS Protection Group........................... 4-21 Switching 1+1 APS Protection Group............................... 4-24 Protecting Port Commands....................................... 4-24 Working Port Commands........................................ 4-25 Request Priorities for 1+1 APS Protection........................... 4-25 Chapter 5 1+1 Path Protection Groups Create a 1+1 Path Protection Group................................ 4-27 Protection Switching Path Protected Services........................ 4-28 Release TN4.0.x Turin Networks Page i

TransNav GUI Guide, Section 4 Protection Switching Chapter 6 Carrier Ethernet Protection Pair Ethernet Equipment............................................. 4-29 Carrier Ethernet Protection Pair.................................... 4-30 Inter-card Link Aggregation Groups................................. 4-30 Creating a Carrier Ethernet Protection Pair........................... 4-31 Chapter 7 1+1 Optimized Protection Groups Create a 1+1 Optimized Protection Group............................ 4-34 Protection Switch Commands..................................... 4-35 Primary State Commands........................................ 4-36 Secondary State Commands...................................... 4-36 Request Priorities for 1+1 Optimized Protection....................... 4-36 List of Figures Figure 4-1 Add BLSR or MS-SPRing Protection Group................. 4-1 Figure 4-2 BLSR Ring Configuration Screen......................... 4-2 Figure 4-3 Synchronize Status.................................... 4-4 Figure 4-4 Operations Menu...................................... 4-4 Figure 4-5 Squelch Table Menu Option............................. 4-6 Figure 4-6 Squelch Table Dialog Box............................... 4-6 Figure 4-7 Add SNCP/UPSR Protection Ring......................... 4-9 Figure 4-8 SNCP/UPSR Ring Configuration Screen................... 4-10 Figure 4-9 SNCP/UPSR Synchronize Status......................... 4-11 Figure 4-10 Protection Rings Shortcut Menu.......................... 4-12 Figure 4-11 Topology Update Menu................................. 4-13 Figure 4-12 Add an Equipment Protection Group....................... 4-15 Figure 4-13 Add Equipment Protection Group Screen................... 4-16 Figure 4-14 Equipment Protection Group Configuration Screen........... 4-18 Figure 4-15 Create a 1+1 APS Protection Group....................... 4-21 Figure 4-16 Add 1+1 Protection Group Screen......................... 4-22 Figure 4-17 1+1 Protection Group Configuration....................... 4-24 Figure 4-18 Create a 1+1 Path Protection Group....................... 4-27 Figure 4-19 1+1 Path Protection Group Screen........................ 4-28 Figure 4-20 Add a Carrier Ethernet Protection Pair..................... 4-31 Figure 4-21 Carrier Ethernet Protection Pair Screen.................... 4-31 Figure 4-22 Create a 1+1 Optimized Protection Group.................. 4-34 Figure 4-23 1+1 Optimized Protection Group Screen.................... 4-34 Figure 4-24 1+1 Optimized Protection Group Configuration Screen........ 4-35 List of Tables Table 4-1 1+1 APS Protection Groups on a DCS-384 Node............. 4-23 Page ii Turin Networks Release TN4.0.x

TransNav GUI Guide, Section 4 Protection Switching Release TN4.0.x Turin Networks Page iii

TransNav GUI Guide, Section 4 Protection Switching Page iv Turin Networks Release TN4.0.x

SECTION 4PROTECTION SWITCHING Chapter 1 BLSR and MS-SPRing Protection Groups Introduction Create a BLSR or MS-SPRing Protection Group The Traverse system supports up to 16 nodes in a BLSR or MS-SPRing protection group. This section contains information on the following topics: Create a BLSR or MS-SPRing Protection Group, page 4-1 Synchronize Status, page 4-4 Operations Menu, page 4-4 Protection Switch Commands, page 4-5 Protection Switch Request Priorities, page 4-5 Squelch Table, page 4-6 Updating a Topology (Adding a Node), page 4-7 For guidelines and procedures to provision a BLSR or MS-SPRing, see Traverse Provisioning Guide, Section 3 Creating Protection Groups, Chapter 2 Creating a BLSR/MS-SPRing Protection Group, page 3-7. In Map View, click the Protection tab. The Protection Rings screen displays. The Protection Rings screen allows you to configure new or view existing protected rings. From the New menu beside the command buttons, click BLSR or MSSPRing to configure a protection ring, then click Add. Figure 4-1 Add BLSR or MS-SPRing Protection Group Release TN4.0.x Turin Networks Page 4-1

TransNav GUI Guide, Section 4: Protection Switching Create a BLSR or MS-SPRing Protection Group The Create Protection Group tab screen displays. Figure 4-2 BLSR Ring Configuration Screen The Add {BLSR MSSP Ring} Configuration screen allows you to view and set the following configuration information: Name: Enter the name of the ring. Enter the name of the node (maximum 43 characters). Use alphanumeric characters only. Do not use punctuation, spaces, or any other special characters in this field. Revertive (selected, read-only): Protection switching is revertive. When the condition that initiated a protection switch no longer exists, the traffic is switched back to the working channels. Card Type: Select one of the following optical links: OC-48 OC-192 STM-16 STM-64 Note: BLSR rings cannot be configured on 2-port OC-48/STM-16 optical links. Ring ID: After the ring is created, the management system assigns and displays a ring identification number from 0 to 15. WTR Time (min): Enter the Wait to Restore time in minutes. The range is 5 to 12; default is 5. If the problem that caused the protection switch clears before the time specified in this parameter, you can restore the traffic to the working port immediately. Column headings in the protection ring table are: Node: Node name that is part of this protection group. Click the first row beneath the column heading and select the node in Map View. ID: Identification number of the node in the ring. Select 0 through 15. The default is sequential order. This ID is used to squelch services in the ring. Page 4-2 Turin Networks Release TN4.0.x

Chapter 1 BLSR and MS-SPRing Protection Groups Create a BLSR or MS-SPRing Protection Group West Port: Port for westbound traffic on the selected node. After selecting the node, click the first row beneath the West Port column heading. Select the West Port from the drop-down list box. Status: Displays the current switch request on the West Port: FS_R: Forced Switch (ring) LOP_R: Lockout of Protection channels (ring) MS_R: Manual Switch (ring) SD_R: Signal Degrade (ring) SF_R: Signal Fail (ring) WTR: Wait to Restore Protection: Displays the status of the protection channels for the West Port. NORMAL indicates the working channels are carrying traffic. SWTD (switched) or PATHD (pass-through) indicates that protection channels are carrying traffic. The status can be one of the following values: NORMAL. Indicates that the working channels are carrying traffic. SWTD. Indicates that the protection channels are carrying traffic. PATHD. Indicates that the protection channels are carrying traffic. NOT INIT. Indicates there is an outstanding external command or stuck condition on the ring. Click Init to re-initialize all kilobytes. East Port: Port for eastbound traffic on the selected node. After selecting the node, click the first row beneath the East Port column heading. Select the East Port from the drop-down list box. Status: Displays the current switch request on the East Port. These are the same as for the West Port Status, described above. Protection: See the definition for the West Port Protection, described above. Command buttons are as follows: Add: Add the protection group to the network configuration. A dialog box displays that reads, Would you like to synchronize the new Protection Group? Click Yes to propagate the new protection group information to all nodes in the ring, or click No. The protection group is listed on the Protection tab. Note: If your system has multiple servers, synchronization must be done from the Primary server only. Cancel: Cancel the protection group information. Synchronize: If the second box displays Not Synchronized, click Synchronize to propagate the information so that all nodes know they belong to a protection group. Init: Re-initializes the kilobytes on all the facilities involved in the protection group. Click Init to clear any pending external commands or stuck conditions. Add Node: Add a new node to the existing ring. See Traverse Provisioning Guide for procedures on adding a node. Remove Node: Remove a node from the existing ring. Release TN4.0.x Turin Networks Page 4-3

TransNav GUI Guide, Section 4: Protection Switching Synchronize Status Synchronize Status The second box in the lower left corner displays the synchronization status of the protection ring. Synchronized indicates that all nodes in the ring know that they belong to a protection group. If the second box displays Not Synchronized, click Synchronize to propagate the information to the ring. Figure 4-3 Synchronize Status Operations Menu In the {BLSR MS-SP Ring} Configuration screen, right-click a row to display commands specific to a BLSR or MS-SP ring. Figure 4-4 Operations Menu Menu selections are as follows: Remove: Remove the selected node from the ring. Squelch Table: At each node, use the squelch table to specify the source and destination points of every provisioned path in the ring. See Squelch Table, page 4-6. Clear. See Protection Switch Commands, page 4-5. Lockout Protecting Ring. See Protection Switch Commands, page 4-5. Forced (FS_R). See Protection Switch Commands, page 4-5. Manual (MS_R). See Protection Switch Commands, page 4-5. Page 4-4 Turin Networks Release TN4.0.x

Chapter 1 BLSR and MS-SPRing Protection Groups Protection Switch Request Priorities Protection Switch Commands Protection Switch Request Priorities In the protection group Configuration screen, right-click a row to display the operations menu. The following switch commands are available for BLSR or MS-SP ring protection switching: Clear: Clear user-initiated switch commands from the selected port. This also clears the Wait to Restore state of the selected node. Lockout Protecting Ring: Prevent protection switches anywhere in the ring. If any working traffic is using the protection channels on any span, this command causes traffic to switch back to the working channels regardless of the condition of the working channels. Forced Switch Ring: Perform the ring switch from the working channels to the protection channels for the span between the node where the command is initiated and the adjacent node to which the command is destined. This switch occurs regardless of the state of the protection channels, unless the protection channels are satisfying a higher priority request. Manual Switch Ring: Perform the ring switch from the working channels to the protection channels for the span between the node where the command is initiated and the node to which the command is destined. This switch occurs if the protection channels to be used are operating at a BER better than the signal degrade threshold and are not satisfying an equal or higher priority request (including failure of the protection channels). Switching request priorities (from highest to lowest) for BLSR or MS-SP ring protection are: Clear: User-initiated action. Lockout of Protection: User-initiated action. Forced Switch (ring): User-initiated protection switch. Signal Fail (ring): System-initiated protection switch. An SF is defined as a hard failure caused by a Loss of Signal (LOS), a line BER exceeding a preselected threshold, a line AIS, or some other hard failure. Signal Degrade (ring): System-initiated protection switch. An SD is defined as a soft failure caused by a BER exceeding a preselected threshold. Manual Switch (ring): User-initiated protection switch. Wait to Restore (WTR): User-configurable setting. This request is issued when working channels meet the restore threshold after an SD or SF condition. Exerciser (ring): This command exercises ring protection switching of the requested channel without completing the actual bridge and switch. The command is issued and the responses are checked, but no working traffic or extra traffic is affected. No Request. Release TN4.0.x Turin Networks Page 4-5

TransNav GUI Guide, Section 4: Protection Switching Squelch Table Squelch Table The squelch table displays the source and destination points of every provisioned path in the ring. That is, for each STS or STM, this table identifies the node where the traffic enters the ring and the node where the traffic exits the ring. The squelch table is automatically populated for services provisioned end-to-end over the protected ring. For services provisioned hop-by-hop, the squelch table is populated using the {BLSR MS-SP Ring} Source Node ID and {BLSR MS-SP Ring} Destination Node ID parameters during the service provisioning process. See Section 6 Services for parameter descriptions. From the Configuration screen, right-click the West port and select Squelch Table from the menu. Figure 4-5 Squelch Table Menu Option The squelch table for the selected node displays. Figure 4-6 Squelch Table Dialog Box The Squelch Table dialog box displays the following information: Node Name: Displays the name of the selected node. Node ID: Displays the BLSR or MS-SPRing node identification of the selected node. The Node ID is assigned by the system when you create the protection group (ID column on the Configuration screen). Page 4-6 Turin Networks Release TN4.0.x

Chapter 1 BLSR and MS-SPRing Protection Groups Updating a Topology (Adding a Node) West Port: Displays the West port on the selected node for the protection group. East Port: Displays the East port on the selected node for the protection group. For each path (system-specified based on bandwidth of the fiber) entering and exiting that node, this table identifies: East Source Tx: Displays the {BLSR MS-SP Ring} Node ID where the traffic on this path enters the ring. Unidirectional services display only the transmit direction. East Source Rx: For bidirectional services, displays the {BLSR MS-SP Ring} Node ID where the traffic on this path exits the ring. East Destination Tx: Displays the {BLSR MS-SP Ring} Node ID where the traffic on this path enters the ring. Unidirectional services display only the transmit direction. East Destination Rx: For bidirectional services, displays the {BLSR MS-SP Ring} Node ID where the traffic on this path exits the ring. West Source Tx: For bidirectional services, displays the {BLSR MS-SP Ring} Node ID where the traffic on this path enters the ring. Unidirectional services display only the transmit direction. West Source Rx: Displays the {BLSR MS-SP Ring} Node ID where the traffic on this path exits the ring. West Destination Tx: For bidirectional services, displays the {BLSR MS-SP Ring} Node ID: Indicates where the traffic on this path enters the ring. Unidirectional services display only the transmit direction. West Destination Rx: Displays the {BLSR MS-SP Ring} Node ID where the traffic on this path exits the ring. Command buttons are as follows: Refresh: Refresh the data in the dialog box. Apply: Apply changes. Done: Close the dialog box. Updating a Topology (Adding a Node) See Section 4 Protection Switching, Chapter 2 UPSR and SNCP Ring Protection Groups, Updating a Topology (Adding a Node), page 4-13. Release TN4.0.x Turin Networks Page 4-7

TransNav GUI Guide, Section 4: Protection Switching Updating a Topology (Adding a Node) Page 4-8 Turin Networks Release TN4.0.x

SECTION 4PROTECTION SWITCHING Chapter 2 UPSR and SNCP Ring Protection Groups Introduction Create a UPSR or SNCP Ring The Traverse system supports up to 16 nodes in a UPSR or SNCP ring. This chapter contains information on the following topics: Create a UPSR or SNCP Ring, page 4-9 Ring Synchronize Status, page 4-11 SNCP/UPSR Protection Switch Commands, page 4-11 Synchronizing, Editing, and Deleting Configured Protection Rings, page 4-12 Updating a Topology (Adding a Node), page 4-13 For guidelines and procedures to provision a UPSR or SNCP ring, see either the Traverse Provisioning Guide or TraverseEdge 100 User Guide. In Map View, click the Protection tab. The Protection Rings screen displays. The Protection Rings screen allows you to configure new or view existing protected rings. From the New menu beside the command buttons, select SNCP/UPSR, then click Add. Figure 4-7 Add SNCP/UPSR Protection Ring Release TN4.0.x Turin Networks Page 4-9

TransNav GUI Guide, Section 4: Protection Switching Create a UPSR or SNCP Ring The Create Protection Group tab, SNCP/UPSR Ring Configuration screen displays. Figure 4-8 SNCP/UPSR Ring Configuration Screen The SNCP/UPSR Ring Configuration screen allows you to view and set the following configuration information: Name: Enter the name of the ring. Enter the name of the node (maximum of 43 characters). Use alphanumeric characters only. Do not use punctuation, spaces, or any other special characters in this field. Ring ID: After the ring is created, the management system assigns and displays a ring identification number. Column headings are as follows: Node: Node name that is part of the ring. Click the first row beneath the column heading and select the node in Map View. West Port: Ingress port for the working path. After selecting the node, click the first row beneath the West Port column heading. Select the ingress port from the drop-down list box. East Port: Egress port for the working path. After selecting the node, click the first row beneath the East Port column heading. Select the egress port from the drop-down list box. Remember that the East port on one node is physically connected to the West port on the next node. Command buttons are as follows: Add: Add the protection group to the network configuration. A dialog box displays which reads, Would you like to synchronize the new Protection Group? Click Yes to propagate protection group information to all nodes in the ring, or click No. The protection group is listed on the Protection tab. Cancel: Cancel the protection group information. Synchronize (available for existing rings only). Add Node (available for existing rings only): Add a new node to the existing ring. See the procedures in Traverse Provisioning Guide. Remove Node (available for existing rings only): Remove a node from the existing ring. Apply (available for existing rings only): Apply changes. Page 4-10 Turin Networks Release TN4.0.x

Chapter 2 UPSR and SNCP Ring Protection Groups SNCP/UPSR Protection Switch Commands Ring Synchronize Status The second box in the lower left corner displays the synchronization status of the protection group. Synchronized indicates that the protection group has been synchronized. If this box displays Not Synchronized, click Synchronize to synchronize the ring. Figure 4-9 SNCP/UPSR Synchronize Status SNCP/UPSR Protection Switch Commands Switch commands on rings are performed by selecting a specific service from the Service tab, right-clicking and selecting Show TxRx Path. For more information, see Section 6 Services, Chapter 8 Managing Service Paths,, page 6-71. Release TN4.0.x Turin Networks Page 4-11

TransNav GUI Guide, Section 4: Protection Switching Synchronizing, Editing, and Deleting Configured Protection Rings Synchronizing, Editing, and Deleting Configured Protection Rings In Map View, on the Protection tab, right-click any row. A shortcut menu displays. Figure 4-10 Protection Rings Shortcut Menu Menu selections are as follows: Synchronize: Propagate protection group information to all nodes in the ring. Edit: Edit the selected protection group. Depending on the type of protection scheme you select, the GUI displays either: BLSR Configuration dialog box. See Chapter 1 BLSR and MS-SPRing Protection Groups, page 4-1. UPSR Ring Configuration dialog box. See Create a UPSR or SNCP Ring, page 4-9. Delete: Delete the selected protection group. A dialog box displays which reads, Are you sure you would like to delete [protection group name]? Click Yes to delete the protection group or No. Page 4-12 Turin Networks Release TN4.0.x

Chapter 2 UPSR and SNCP Ring Protection Groups Updating a Topology (Adding a Node) Updating a Topology (Adding a Node) Once a topology for end-to-end services is configured and running, adding a new node requires stopping the end-to-end services signalling. (See Traverse Provisioning Guide Section 2 Changing Network Configurations, Chapter 1 Adding a Node to a Protected Ring Configuration, Add a Node to the Ring, page 2-2 for step-by-step instructions.) To stop the end-to-end signalling, in Map View, click the Config tab, then click the link, and then click the Services button. Click Topology Update. A short menu displays. Figure 4-11 Topology Update Menu Menu selections are as follows: Start: Start the node addition process and stop the end-to-end signalling. Cancel: Interrupt the node addition process and restart the end-to-end signalling without adding a node. Complete: Complete the node addition process and restart the end-to-end signalling. Release TN4.0.x Turin Networks Page 4-13

TransNav GUI Guide, Section 4: Protection Switching Updating a Topology (Adding a Node) Page 4-14 Turin Networks Release TN4.0.x

SECTION 4PROTECTION SWITCHING Chapter 3 Equipment Protection Groups Introduction Create an Equipment Protection Group Use equipment protection switching to create redundancy for the electrical interface cards, the VT/TU 5G Switch card, or for the VTX/VCX hardware on the cards with the integrated switching component. Ensure that no services are activated on either the working or protecting card before creating an equipment protection group. This chapter contains information on the following topics: Create an Equipment Protection Group, page 4-15 Equipment Protection Switch Commands, page 4-18 Protecting Card Commands, page 4-18 Working Card Commands, page 4-18 Request Priorities for Equipment Protection, page 4-19 Only the Traverse system supports configurable equipment protection switching. For guidelines and procedures to provision an equipment protection group, see the Traverse Provisioning Guide, Section 3 Creating Protection Groups, Chapter 4 Creating Equipment Protection Groups, page 3-21. For an explanation of how the TE-100 supports equipment protection switching, see the TraverseEdge 100 User Guide, Section 2 Platform Specifications. From the Shelf View, click the Protection tab, select 1 for N equipment, and click Add. Figure 4-12 Add an Equipment Protection Group Release TN4.0.x Turin Networks Page 4-15

TransNav GUI Guide, Section 4: Protection Switching Create an Equipment Protection Group The Create Protection Group tab, Equipment Protection Group screen displays. Figure 4-13 Add Equipment Protection Group Screen The Equipment Protection Group screen allows you to view and set the following configuration information: Name: Enter the name of the protection group. Enter the name of the node (maximum of 43 characters). Use alphanumeric characters only. Do not use punctuation, spaces, or any special characters in this field. Revertive: Select for revertive switching. Traffic is switched back to the working card when the working card has recovered from the failure or the external command is cleared. Clear for non-revertive switching (default). A switch to the protection card is maintained even after the working card has recovered from the failure that caused the switch, or the external switch command is cleared. ID: After the protection group is created, the management system assigns and displays an identification number. WTR (Wait to Restore) Time (min): When the Revertive option is selected, this box turns from grayed out (unavailable) to white (available). WTR specifies the amount of time (in minutes) for the system to wait after the failure clears before restoring traffic to the working card. Enter a number in the range of 1 to 60; the default is 5. Column headings are as follows: Role: Protecting: The protecting card Working: The working card Card: Click the Protecting row, Card column. Select from the allowable protecting cards. For 1:1 protection, the protecting card must be in an odd-numbered slot and must be directly to the left of the working card in an even-numbered slot. Allowable protecting card-working card slot combinations are: 1-2, 3-4, 5-6, 7-8, 9-10, and 11-12. Page 4-16 Turin Networks Release TN4.0.x

Chapter 3 Equipment Protection Groups Create an Equipment Protection Group For Ethernet 1:1 equipment protection, the lower slot number is the protecting card. The higher slot number is the working card. For 1:2 protection, the middle card in a group of three cards protects the adjacent two working cards. The protection group can start in any odd- or even-numbered slot. For 1 for N protection using the DS3TMX card for the optical transmux application, Turin has the following recommendations: Place the DS3TMX cards starting in slot 1. Use the card in the left-most slot of the group of cards as the protecting card. Click a Working row, Card column. Select from the allowable working cards. For 1:2 and 1 for N protection, the order in which you add cards to this list is the order of protection priority. Specifically, the card that you select for Working 1 has priority over the card you select for Working 12. Status: Displays a blank field or one of the following switch commands (see Equipment Protection Switch Commands, page 4-18 for descriptions): Clear Lockout Forced Manual Wait to restore Protection: Displays Standby for the standby card and Active for the active card. When an NGE or NGE Plus card transitions from Active to Standby, the PM counts restart at 0 to display information for the newly Active card. Consequently, PM polling is disabled until the card becomes Active. Command buttons are as follows: Add: Add the protection group to the Protection tab. Cancel: Cancel the protection group information. Release TN4.0.x Turin Networks Page 4-17

TransNav GUI Guide, Section 4: Protection Switching Equipment Protection Switch Commands Equipment Protection Switch Commands You can edit the equipment protection group from the Protection tab in two ways: Highlight the protection group and right-click; select Edit. Double-click the protection group. The Equipment Protection Group screen displays. Figure 4-14 Equipment Protection Group Configuration Screen The switch commands differ between the protecting and working cards. See Protecting Card Commands, page 4-18. See Working Card Commands, page 4-18. When an NGE or NGE Plus card transitions from Active to Standby, the PM counts restart at 0 to display information for the newly Active card. Consequently, PM polling is disabled until the card becomes Active. Protecting Card Commands Working Card Commands Right-click the protecting card to display the switch commands. See Request Priorities for Equipment Protection, page 4-19 for switch command hierarchy. Clear: Clears all switch commands from the card. Lockout: Prevents protecting card from becoming active for any of the working cards. Forced: Forces all traffic from protecting card unless a request of equal or higher priority is in effect. Manual: Manually switch traffic from the protecting card to the working card unless a request of equal or higher priority is in effect. Right-click the working card to display the switch commands. For switching request priorities, see Request Priorities for Equipment Protection, page 4-19. Clear: Clears all switch commands from the card. Lockout: Prevents traffic on this working card from switching to the protecting card. Forced: Forces traffic from working card to protecting card unless a request of equal or higher priority is in effect. Manual: Manually switch traffic from working card to protecting card unless a request of equal or higher priority is in effect. Page 4-18 Turin Networks Release TN4.0.x

Chapter 3 Equipment Protection Groups Request Priorities for Equipment Protection Request Priorities for Equipment Protection Protection switching request priorities (from highest to lowest) for equipment protection are: Clear: User-initiated action Lockout: User-initiated action. A lockout of working and protecting can coexist Forced switch: User-initiated protection switch Card Failure (automatic) Manual switch: User-initiated protection switch Wait to Restore Release TN4.0.x Turin Networks Page 4-19

TransNav GUI Guide, Section 4: Protection Switching Request Priorities for Equipment Protection Page 4-20 Turin Networks Release TN4.0.x

SECTION 4PROTECTION SWITCHING Chapter 4 1+1 MSP/APS Protection Groups Introduction Create a 1+1 MSP/APS Protection Group This chapter contains information on the following topics: Create a 1+1 MSP/APS Protection Group, page 4-21 Switching 1+1 APS Protection Group, page 4-24 Protecting Port Commands, page 4-24 Working Port Commands, page 4-25 Request Priorities for 1+1 APS Protection, page 4-25 For guidelines and procedures to provision a facility protection group, see the Traverse Provisioning Guide or the TraverseEdge 100 User Guide. From the Shelf View, click the Protection tab, select 1+1 MSP/APS and click Add. Figure 4-15 Create a 1+1 APS Protection Group Release TN4.0.x Turin Networks Page 4-21

TransNav GUI Guide, Section 4: Protection Switching Create a 1+1 MSP/APS Protection Group The Add 1+1 Protection Group screen displays. Figure 4-16 Add 1+1 Protection Group Screen The Add 1+1 Protection Group screen allows you to set the following configuration information: Name: Enter the name of the protection group. Enter the name of the node (maximum of 43 characters). Use alphanumeric characters only. Do not use punctuation, spaces, or any special characters in this field. Revertive: Select for revertive switching. Traffic is switched back to the working port when the working port has recovered from the failure or the external command is cleared. Clear for non-revertive switching (default). A switch to the protection port is maintained even after the working port has recovered from the failure that caused the switch, or the external switch command is cleared. Switch Mode: Uni-directional: When the receive fiber on an active link fails, the system switches the traffic from that link to the standby link. Bidirectional: When either the transmit or receive fibers on an active link fails, the system switches both directions to the standby links. ID: After the protection group is created, the management system assigns and displays an identification number. WTR Time (min): If Revertive is selected, this box turns from grayed out (unavailable) to white (available). Time (in minutes) after the condition that caused a switch clears and traffic is restored to the working line. Enter a number between 1 and 60; default is 5. Protecting Port: Select the port protecting the active traffic. Working Port: Select the port carrying active traffic. Page 4-22 Turin Networks Release TN4.0.x

Chapter 4 1+1 MSP/APS Protection Groups Create a 1+1 MSP/APS Protection Group In a DCS-384 node, the protection groups are pre-provisioned for the 2-port OC-48 cards using the following scheme for each pair of cards; the working port is port 1 and the protecting port is port 2 of the adjacent card. Table 4-1 1+1 APS Protection Groups on a DCS-384 Node Protection Group Working Port Protecting Port PG1 slot 11-port 1 slot 12-port 2 PG2 slot 12-port 1 slot 11-port 2 PG3 slot 13-port 1 slot 14-port 2 PG4 slot 14-port 1 slot 13-port 2 PG5 slot 15-port 1 slot 16-port 2 PG6 slot 16-port 1 slot 15-port 2 PG7 slot 17-port 1 slot 18-port 2 PG8 slot 18-port 1 slot 17-port 2 Status: Displays a blank field or one of the following switch commands (see Switching 1+1 APS Protection Group, page 4-24 for definitions): Clear Lockout Forced Signal Failed Signal Degraded Manual Wait to restore Protection: Displays Standby for the standby port and Active for the active port. Command buttons are as follows: Add: Add the protection group to the Protection tab. Cancel: Cancel the protection group information. Release TN4.0.x Turin Networks Page 4-23

TransNav GUI Guide, Section 4: Protection Switching Switching 1+1 APS Protection Group Switching 1+1 APS Protection Group To perform a protection switch on a 1+1 APS protection group, double-click the protection group to display the 1+1 Protection Group Configuration screen. Figure 4-17 1+1 Protection Group Configuration The switch commands differ between the protecting and working ports. Protecting Port Commands, page 4-24 Working Port Commands, page 4-25 When an NGE or NGE Plus card transitions from Active to Standby, the PM counts restart at 0 to display information for the newly Active card. Consequently, PM polling is disabled until the card becomes Active. Protecting Port Commands Right-click the protecting port to display the switch commands. See Request Priorities for 1+1 APS Protection, page 4-25 for the switch command priorities. Clear: Clear all switch commands from the port. Displays a dialog box which reads Are you sure you would like to release [Node name.slot number:type=,ptp=]? Click Yes to proceed with the Release command or No. If you click Yes, the Status column clears. Lockout: Prevent the working channel from switching to the protecting line, unless a request of equal priority is already in effect. Displays a dialog box which reads Are you sure you would like to lockout [Node name.slot number:type=,ptp=]? Click Yes to proceed with the Lockout command or No. If you click Yes, the Status column displays Lockout. Forced: Force switch traffic from protecting facility to working facility. Switch the working channel back from the protecting line to the working line, unless a request of equal or higher priority is in effect. Displays a dialog box which reads Are you sure you would like to force switch [Node name.slot number:type=,ptp=]? Click Yes to proceed with the Forced switch command or No. If you click Yes, the Status column displays Forced. Manual: Manually switch traffic from the protecting facility to the working facility. Switch the working channel back from the protecting line to the working line, unless a request of equal or higher priority is in effect. Displays a dialog box which reads Are you sure you would like to manual switch [Node name.slot number:type=,ptp=]? Click Yes to proceed with the Manual switch command or No. If you click Yes, the Status column displays Manual. Page 4-24 Turin Networks Release TN4.0.x

Chapter 4 1+1 MSP/APS Protection Groups Request Priorities for 1+1 APS Protection Exercise (bidirectional protection only): This command exercises protection switching of the requested channel without completing the actual bridge and switch. The command is issued and the responses are checked, but no working traffic or extra traffic is affected. When an NGE or NGE Plus card transitions from Active to Standby, the PM counts restart at 0 to display information for the newly Active card. Consequently, PM polling is disabled until the card becomes Active. Working Port Commands Request Priorities for 1+1 APS Protection Right-click the working port to display the switch commands. See Request Priorities for 1+1 APS Protection, page 4-25 for the switch command priorities. Clear: Clear all switch commands from the port. Displays a dialog box which reads Are you sure you would like to release [Node name.slot number:type=,ptp=]? Click Yes to proceed with the Release command or No. If you click Yes, the Status column clears. Forced: Switch of Working (to Protecting). Switch the working channel to the protecting line, unless a request of equal or higher priority is in effect. Displays a dialog box which reads Are you sure you would like to force switch [Node name.slot number:type=,ptp=]? Click Yes to proceed with the Forced switch command or No. If you click Yes, the Status column displays Forced. Manual: Switch of Working (to Protecting). Switch the working channel to the protecting line, unless a request of equal or higher priority is in effect. Displays a dialog box which reads Are you sure you would like to manual switch [Node name.slot number:type=,ptp=]? Click Yes to proceed with the Manual switch command or No. If you click Yes, the Status column displays Manual. Exercise (bidirectional protection only): This command exercises protection switching of the requested channel without completing the actual bridge and switch. The command is issued and the responses are checked, but no working traffic or extra traffic is affected. When an NGE or NGE Plus card transitions from Active to Standby, the PM counts restart at 0 to display information for the newly Active card. Consequently, PM polling is disabled until the card becomes Active. Request priorities (from highest to lowest) for 1+1 APS are: Clear: User-initiated action Lockout (of protection): User-initiated action Forced switch. User-initiated protection switch Signal Failure (SF): System-initiated protection switch. Automatic SF switch initiation criteria for a APS are: Loss of Signal, Loss of Frame, AIS-L (Alarm Indication Signal-Line), and SF BER (exceeding threshold) on an incoming OC. Signal Degrade (SD): System-initiated protection switch. Automatic SD switch initiation criteria for a APS is SD BER exceeding threshold on an incoming OC. Manual switch: User-initiated protection switch. Wait to Restore (WTR used if revertive switching is selected): User-configurable option Reverse Request (applies to bidirectional switch mode) No Request (applies to 1+1 nonrevertive) Release TN4.0.x Turin Networks Page 4-25

TransNav GUI Guide, Section 4: Protection Switching Request Priorities for 1+1 APS Protection Page 4-26 Turin Networks Release TN4.0.x

SECTION 4PROTECTION SWITCHING Chapter 5 1+1 Path Protection Groups Introduction Create a 1+1 Path Protection Group 1+1 path protection is a protection mechanism that uses one path of any bandwidth to protect another of the same bandwidth. This chapter contains information on the following topics: Create a 1+1 Path Protection Group, page 4-27 Protection Switching Path Protected Services, page 4-28 Only the Traverse system supports 1+1 path protection groups. For guidelines and procedures to provision a 1+1 path protection group, see the Traverse Provisioning Guide, Section 3 Creating Protection Groups, Chapter 7 Creating a 1+1 Path Protection Group, page 3-41. From the Shelf View, Protection tab, select 1+1 Path, and click Add. Figure 4-18 Create a 1+1 Path Protection Group Release TN4.0.x Turin Networks Page 4-27

TransNav GUI Guide, Section 4: Protection Switching Protection Switching Path Protected Services The 1+1 Path Protection Group screen displays. Figure 4-19 1+1 Path Protection Group Screen The 1+1 Path Protection Group screen allows you to set the following configuration information: Name: Enter the name of the protection group. Enter the name of the node (maximum of 43 characters). Use alphanumeric characters only. Do not use punctuation, spaces, or any other special characters in this field. ID: After the protection group is created, the management system assigns and displays an identification number. Protecting Port: Select the protecting port for this protection group. Working Port: Select the working port for this protection group. Concatenation: Select the bandwidth of the path: STS-1 (default if endpoints are SONET) STS-3c STS-12c (for OC-12 and greater interfaces only) STS-48c (OC-48 and greater interfaces only) VC-3 (default if endpoints are SDH) VC-4 VC-4-4c (for STM-4 and greater interfaces only) VC-4-16c (STM-16 and greater interfaces only) Protecting Path: Select the protecting path for this protection group. Working Path: Select the working path for this protection group. Command buttons are as follows: Add: Add the protection group to the Protection tab. Cancel: Cancel the protection group information. Protection Switching Path Protected Services See Section 6 Services, Chapter 8 Managing Service Paths, Protection Switching Path-Protected Services for information on performing protection switching. Page 4-28 Turin Networks Release TN4.0.x

SECTION 4PROTECTION SWITCHING Chapter 6 Carrier Ethernet Protection Pair Introduction Ethernet Equipment Use a Carrier Ethernet Protection Pair (CEPP) with NGE Plus cards to create inter-card link aggregation groups and aggregate data from Ethernet ports on two cards to a single EOS link. Ensure that no services are activated on either the working or protecting card before creating a CEPP. This chapter contains information on the following topics: Ethernet Equipment, page 4-29 Carrier Ethernet Protection Pair, page 4-30 Inter-card Link Aggregation Groups, page 4-30 Creating a Carrier Ethernet Protection Pair, page 4-31 Important: The information in this section strictly pertains to the Traverse Next Generation Ethernet Plus (NGE Plus) cards: GBE4-FE16-TX / CEP and GBE2T-GBE2F-FE16-TX / CEP. Release TN4.0.x Turin Networks Page 4-29

TransNav GUI Guide, Section 4: Protection Switching Carrier Ethernet Protection Pair Carrier Ethernet Protection Pair Inter-card Link Aggregation Groups Similar to other Traverse equipment protection groups, each CEPP has two cards that are designated as the Working and Protecting cards. In each group, the cards alternate the active and standby roles, with only the active cards sending and receiving data on the backplane. Unlike other equipment protection groups, a CEPP effectively doubles the number of physical Ethernet ports of a single NGE Plus card. All line-side ports on both cards connect to the CEPP and carry independent traffic. When both cards are up, CEPP behaves like a single card with 40 physical Ethernet and 64 EOS ports. An inter-card Link Aggregation Group (LAG) allows you to set up a LAG for protection in a CEPP by allowing you to link either two ports on the same card or to link two ports on two compatible cards, thus sharing the capacity of a single port. If a link or a card goes down, all of the traffic will be carried on the remaining link, offering both facility and equipment protection for a single Ethernet signal. Each inter-card LAG in a CEPP can contain up to 8 ports and each CEPP can support up to 20 LAGs. For a CEPP LAG, the ports can be on the same card or spread across two cards. If the ports are on two separate cards, the cards must have the same type of port configuration: either both are 4-port optical or both are 2-port electrical / 2-port optical cards. An NGE Plus card can only be in one CEPP at a time. Page 4-30 Turin Networks Release TN4.0.x

Chapter 6 Carrier Ethernet Protection Pair Creating a Carrier Ethernet Protection Pair Creating a Carrier Ethernet Protection Pair From the Shelf view, click the Protection tab, select CEPP and click Add. Figure 4-20 Add a Carrier Ethernet Protection Pair The Create Protection Group tab, Carrier Ethernet Protection Pair screen displays. Figure 4-21 Carrier Ethernet Protection Pair Screen The Carrier Ethernet Protection Pair screen allows you to view and set the following configuration information: Name: Enter the name of the protection group. Enter the name of the node (maximum of 43 characters). Use alphanumeric characters only. Do not use punctuation, spaces, or any other special characters in this field. ID: After the protection group is created, the management system assigns and displays an identification number. Revertive: Select for revertive switching. Traffic is switched back to the working port when the working port has recovered from the failure or the external command is cleared. Clear for non-revertive switching (default). A switch to the protection port is maintained even after the working port has recovered from the failure that caused the switch, or the external switch command is cleared. WTR Time (1..60 min): If Revertive is selected, this box turns from grayed-out (unavailable) to white (available). Time (in minutes) after the condition that caused a switch clears and traffic is restored to the working line. Enter a number between 1 and 60; default is 5. Role: Indicates the role of the port. Valid values are: Protecting: Select the port protecting the active traffic. Working: Select the port carrying active traffic. Release TN4.0.x Turin Networks Page 4-31

TransNav GUI Guide, Section 4: Protection Switching Creating a Carrier Ethernet Protection Pair Card: Indicates the slot and NGE Plus card that is in either the protecting or working role. Status: Displays a blank field or one of the following switch commands (see Switching 1+1 APS Protection Group, page 4-24 for definitions): Clear Lockout Forced Signal Failed Signal Degraded Manual Wait to restore Protection: Displays Standby for the standby port and Active for the active port. Command buttons are as follows: Create: Create the carrier ethernet protection pair. Cancel: Cancel the protection pair information. Page 4-32 Turin Networks Release TN4.0.x

SECTION 4PROTECTION SWITCHING Chapter 7 1+1 Optimized Protection Groups Introduction 1+1 optimized protection bridges traffic simultaneously over two lines: section 1 and section 2. There is a primary section and a secondary section. In normal operation, the system selects traffic from the primary section (active traffic). All switch requests (automatic or forced) are from the primary section to the secondary section. Once a switch request clears, the traffic selector stays on the section to which it was switched. That section then becomes the primary section if there are no further switch requests. If a failure occurs on the secondary section, the traffic selector remains on traffic from the primary section. If a failure occurs on the secondary section during a protection switch, the initial switch request is abandoned. This chapter contains information on the following topics: Create a 1+1 Optimized Protection Group, page 4-34 Primary State Commands, page 4-36 Secondary State Commands, page 4-36 Request Priorities for 1+1 Optimized Protection, page 4-36 For guidelines and procedures to provision an optimized protection group, see either the Traverse Provisioning Guide or TraverseEdge 100 User Guide. Release TN4.0.x Turin Networks Page 4-33

TransNav GUI Guide, Section 4: Protection Switching Create a 1+1 Optimized Protection Group Create a 1+1 Optimized Protection Group From the Shelf View, Protection tab, select 1+1_optimized and click Add. Figure 4-22 Create a 1+1 Optimized Protection Group The Add 1+1 Optimized Protection Group screen displays. Figure 4-23 1+1 Optimized Protection Group Screen The Add 1+1 Optimized Protection Group screen allows you to set the following configuration information: Name: Enter the name of the protection group. Enter the name of the node (maximum of 43 characters). Use alphanumeric characters only. Do not use punctuation, spaces, or any other special characters in this field. Locked Out: Selected if there is a lockout command applied on either the primary or secondary sections. ID: After the protection group is created, the management system assigns and displays an identification number. WTR (Wait to Restore) Time: The time (in minutes) after a protection switch that the section carrying active traffic becomes the primary section. Enter a number in the range of 1 to 60; the default is 5. Column headings are as follows: Role: Section 1: working channel 1 Section 2: working channel 2 Page 4-34 Turin Networks Release TN4.0.x

Chapter 7 1+1 Optimized Protection Groups Protection Switch Commands Port: Select a port from the drop-down menu or click a port in Shelf View. Status: Displays a blank field or one of the following switch commands (see Protection Switch Commands, page 4-35): Clear Lockout Forced Protection: Displays one of the following: Primary/Active: Normal operation. No outstanding switch requests. Secondary/Standby: Normal operation. No outstanding switch requests. Primary/Standby: There is an outstanding switch request in the system. Secondary/Active: There is an outstanding switch request in the system. Command buttons are as follows: Add: Add the protection group to the Protection tab. Cancel: Cancel the protection group information. Protection Switch Commands You can edit the protection group from the Protection tab in two ways: Highlight the protection group and right-click; select Edit. Double-click the protection group. The 1+1 Optimized Protection Group Configuration screen displays. Figure 4-24 1+1 Optimized Protection Group Configuration Screen The switch commands differ between the protecting and working ports. Primary State Commands, page 4-36 Secondary State Commands, page 4-36 Release TN4.0.x Turin Networks Page 4-35

TransNav GUI Guide, Section 4: Protection Switching Primary State Commands Primary State Commands Secondary State Commands Request Priorities for 1+1 Optimized Protection Right-click the primary facility to display the switch commands. See Request Priorities for 1+1 Optimized Protection, page 4-36 for the switch command priorities. Clear: Clear all switch commands from the port. Lockout: Local request that freezes the selector position and the transmission of kilobytes on the current position until this request is cleared. Forced: Force the system to select traffic from the secondary section, unless a local lockout is in effect, an equal or higher priority request is in effect, or the secondary section has failed. Right-click the secondary state port to display the switch commands. See Request Priorities for 1+1 Optimized Protection, page 4-36 for the switch command priorities. Clear: Clear all switch commands from the port. Lockout: Local request that freezes the selector position and the transmission of kilobytes on the current position until this request is cleared. Request priorities (from highest to lowest) for 1+1 optimized protection switching are: Forced (near end or far end) Signal Fail (near end or far end) Signal Degrade (near end or far end) Wait-to-Restore (near end or far end) Page 4-36 Turin Networks Release TN4.0.x

SECTION 5EQUIPMENT CONFIGURATION SECTION 5EQUIPMENT SECTION 5 EQUIPMENT Contents Chapter 1 Common Equipment When to Change Card Parameters................................. 5-1 Protection Groups and Card Configuration........................... 5-1 Equipment States.............................................. 5-2 Parameters Common to All Card Types............................. 5-3 GCM Card Parameters.......................................... 5-5 Chapter 2 SONET Equipment DS1 Card Parameters........................................... 5-8 DS1 Numbering................................................ 5-9 DS1 Mapping.................................................. 5-10 DS3 Framing Format............................................ 5-10 DS1 Port Parameters........................................... 5-10 DS3 Card Parameters........................................... 5-12 DS3CC Port Parameters......................................... 5-13 DS3TMX and STS1TMX Port Parameters........................... 5-15 Subport Parameters............................................ 5-17 EC1 Port Parameters........................................... 5-19 SONET (OC-N) Card Parameters.................................. 5-22 SONET Port Parameters......................................... 5-23 SFP Port Parameters........................................... 5-28 Chapter 3 SDH Equipment E1 Card Parameters............................................ 5-31 E1 Numbering (Traverse only).................................... 5-32 E1 Mapping................................................... 5-33 E1 Mapping and Patch Panel Ports (Traverse only).................... 5-34 TE-100 Interface Card Parameters................................. 5-35 E1 Port Parameters............................................. 5-36 E3 Card Parameters............................................ 5-38 E3 Port Parameters............................................. 5-38 Release TN4.0.x Turin Networks Page i

TransNav GUI Guide, Section 5 Equipment SDH (STM) Card Parameters..................................... 5-40 STM Port Parameters........................................... 5-41 SFP Port Parameters............................................ 5-46 Chapter 4 Ethernet Equipment Ethernet Equipment............................................. 5-49 Ethernet Card Parameters........................................ 5-50 MAC Address Table............................................. 5-52 Ethernet Port Parameters........................................ 5-53 SFP / XFP Port Parameters....................................... 5-56 Ethernet Port Advanced Parameters................................ 5-58 EOS Port Parameters........................................... 5-63 EOS Port Advanced Parameters................................... 5-64 Ethernet or EOS Port Queues..................................... 5-66 EOS Port Status............................................... 5-69 Link Aggregation Group.......................................... 5-71 LAG Advanced Parameters....................................... 5-72 Chapter 5 TransAccess 200 Mux Add a TransAccess 200 Mux...................................... 5-73 Delete a TransAccess 200 Mux.................................... 5-75 TransNav System Parameters..................................... 5-75 Navigate to a TransAccess 200 Mux................................ 5-76 Menu Options on the Sub Shelf Menu............................... 5-76 Chapter 6 TraverseEdge 50 (TE-50) Add a TE-50................................................... 5-79 Delete a TE-50................................................. 5-81 TransNav System Parameters..................................... 5-81 Navigate to the TE-50 Menu Options............................... 5-81 List of Figures Figure 5-1 Equipment States..................................... 5-2 Figure 5-2 GBE Card Configuration Tab............................. 5-3 Figure 5-3 GCM Card Configuration Tab............................ 5-5 Figure 5-4 DS1 Card Configuration Tab............................. 5-8 Figure 5-5 DS1 Port Configuration Screen........................... 5-10 Figure 5-6 DS3 Card Configuration Screen.......................... 5-12 Figure 5-7 DS3 Clear Channel Port Configuration Screen............... 5-13 Figure 5-8 DS3TMX Port Config Tab............................... 5-15 Figure 5-9 Subports on a DS3TMX or an STS1TMX Port............... 5-17 Figure 5-10 EC1 Port Configuration Screen........................... 5-19 Figure 5-11 OC-192 Card Parameters............................... 5-22 Page ii Turin Networks Release TN4.0.x

TransNav GUI Guide, Section 5 Equipment Figure 5-12 SONET Port Configuration Screen........................ 5-23 Figure 5-13 SFP Fields on Port Configuration Screen................... 5-28 Figure 5-14 Diagnostic Parameters Dialog Box........................ 5-29 Figure 5-15 E1 Card Card Configuration Tab.......................... 5-31 Figure 5-16 TE-100 Interface Card Parameters........................ 5-35 Figure 5-17 E1 Port Configuration Screen............................ 5-36 Figure 5-18 E3 Card Configuration Screen........................... 5-38 Figure 5-19 E3 Port Configuration Screen............................ 5-38 Figure 5-20 STM-64 Card Parameters............................... 5-40 Figure 5-21 SDH Port Configuration Screen.......................... 5-41 Figure 5-22 SFP Port Configuration Screen........................... 5-46 Figure 5-23 Diagnostic Parameters Dialog Box........................ 5-47 Figure 5-24 Ethernet Card, Configuration Tab......................... 5-50 Figure 5-25 MAC Address Queries Dialog Box........................ 5-52 Figure 5-26 Ethernet Port Configuration Screen....................... 5-53 Figure 5-27 Pluggable Transceiver Fields on Port Configuration Screen.... 5-56 Figure 5-28 Diagnostic Parameters Dialog Box........................ 5-57 Figure 5-29 Traverse GBE Advanced Parameters...................... 5-58 Figure 5-30 Ethernet Tab, EOS Subtab.............................. 5-63 Figure 5-31 Create EOS Tab...................................... 5-63 Figure 5-32 Edit EOS Tab........................................ 5-66 Figure 5-33 Traverse EOS Queue Status Dialog Box................... 5-67 Figure 5-34 EOS Port Status...................................... 5-69 Figure 5-35 EOS Port Status with Normal Relative Differential Delay....... 5-70 Figure 5-36 EOS Port Status with Excessive Relative Differential Delay..... 5-71 Figure 5-37 Create LAG Tab...................................... 5-71 Figure 5-38 Attach Sub Shelf...................................... 5-73 Figure 5-39 Attach TA200 Shelf Dialog Box........................... 5-74 Figure 5-40 TransAccess 200 Mux in Map View....................... 5-75 Figure 5-41 System Parameters for TransAccess 200 Mux............... 5-75 Figure 5-42 Launch TransAccess 200 Mux User Interface............... 5-76 Figure 5-43 TA200 Sub Shelf Configuration........................... 5-76 Figure 5-44 Attach Sub Shelf...................................... 5-79 Figure 5-45 Attach TE50 Shelf Dialog Box............................ 5-80 Figure 5-46 TE-50 in Map View.................................... 5-80 Figure 5-47 System Parameters for TE-50............................ 5-81 Figure 5-48 TE-50 Sub Shelf Menu Options.......................... 5-81 Figure 5-49 TE-50 Sub Shelf Configuration........................... 5-82 List of Tables Table 5-1 GR-253 and Sequential VT Mapping Formats............... 5-9 Table 5-2 E1 Sequential and Non-Sequential Mapping Formats......... 5-32 Table 5-3 DS3-structured VC3-mapped E1 channels.................. 5-33 Table 5-4 E1 Mapping and Patch Panel Ports....................... 5-34 Release TN4.0.x Turin Networks Page iii

TransNav GUI Guide, Section 5 Equipment Table 5-5 System Defaults for RED Thresholds...................... 5-68 Page iv Turin Networks Release TN4.0.x

SECTION 5EQUIPMENT Chapter 1 Common Equipment Introduction When to Change Card Parameters Protection Groups and Card Configuration Equipment in a TransNav managed network includes nodes, links, cards (modules), ports, and other external equipment. This chapter explains the following information for the cards supported in this release: When to Change Card Parameters, page 5-1 Protection Groups and Card Configuration, page 5-1 Equipment States, page 5-2 This chapter also explains all the parameters that appear on each card. See the following sections for specific details: Equipment States, page 5-2 To create and delete equipment during the preprovisioning process, see Chapter 1 Creating and Deleting Equipment Using Preprovisioning. 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 is assigned default parameters. Change the default values on the Config tab. If you have configured a card as part of a protection group, you can only configure parameters on the working card. Down arrows on selections are grayed out (unavailable) for parameters on the protecting card. 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 setting up protection groups, see Section 4 Protection Switching. Release TN4.0.x Turin Networks Page 5-1

TransNav GUI Guide, Section 5: Equipment Equipment States Equipment States Icons in the bottom left-hand corner of the Config tab indicate the state of the card or port. Equipped state Operational state Administrative state Figure 5-1 Equipment States Equipped State: Displays one of the following: Equipped: The equipped state of the card or port is Equipped. The equipment is present in the system. Non-Equipped: The equipped state of the card or port is Non-Equipped. The equipment is not present in the system. Operational State: Displays one of the following: Enabled: The administrative state of the card or port is Unlocked. Disabled: The administrative state of the card or port is Locked. Administrative State: Click the icon until one of the following displays: Lock (default for ports): Do not allow the card or port to operate. Changes the operational state to Disabled. Initiates protection switching, if applicable. Unlock (default for cards): Allow the card or port to operate. Page 5-2 Turin Networks Release TN4.0.x

Chapter 1 Common Equipment Parameters Common to All Card Types Parameters Common to All Card Types There are parameters common to all cards on the Config tab as well as parameters specific to each card, depending on the type. This topic describes the parameters common to all supported cards. In Shelf View, right-click an empty slot and select the type of card to insert. Click the Config tab. The Card Configuration screen displays. Figure 5-2 GBE Card Configuration Tab The Card Configuration screen allows you to view and enter the following card configuration information on all supported cards: Label: Displays the Node ID. Type: Displays the type of card in the slot. Slot Number. Displays the number of the slot in which the card is inserted. HW Description: Displays a character string that clarifies the Type of card. Use alphanumeric characters only. Do not use any other punctuation or special characters. Part Number: The part number assigned to this type and specific revision of hardware card. CLEI: The Telcordia Common Language Equipment Identifier for this type of hardware card. Serial Number: The unique serial number assigned to this individual hardware card. Current SW Version: The current software version of this card. Customer Tag: Enter the display name of this card. ICI: The ITU-T compliant International Common Identifier of this type of hardware card. Module ID: An assigned identifier that designates the function of this type of hardware module (card). Command buttons are as follows: Apply: Click to apply changes to any default values. Cancel: Click to return to default values. Release TN4.0.x Turin Networks Page 5-3

TransNav GUI Guide, Section 5: Equipment Parameters Common to All Card Types Page 5-4 Turin Networks Release TN4.0.x

Chapter 1 Common Equipment GCM Card Parameters GCM Card Parameters See Equipment States, page 5-2 for a description of the parameters that apply to every card. The GCM displays one additional parameter: Protection Status: Displays one of the following status types: Active Unprotected Active Protected Standby Additional parameter Figure 5-3 GCM Card Configuration Tab For GCM cards with integrated optics, you configure the point at which the system raises a signal failed bit error rate (SFBER) or signal degraded bit error rate (SDBER) alarm. These parameters appear depending on the speed of the optical interface on the card. For SONET interfaces, see Chapter 2 SONET Equipment, page 5-7 For STM interfaces, see Chapter 3 SDH Equipment, page 5-31 Release TN4.0.x Turin Networks Page 5-5

TransNav GUI Guide, Section 5: Equipment GCM Card Parameters Page 5-6 Turin Networks Release TN4.0.x

SECTION 5EQUIPMENT Chapter 2 SONET Equipment Introduction This chapter describes all the parameters that appear for each SONET card and port. DS1 Card Parameters, page 5-8 DS1 Port Parameters, page 5-10 DS3 Card Parameters, page 5-12 DS3CC Port Parameters, page 5-13 DS3TMX and STS1TMX Port Parameters, page 5-15 Subport Parameters, page 5-17 EC1 Port Parameters, page 5-19 SONET (OC-N) Card Parameters, page 5-22 SONET Port Parameters, page 5-23 See Chapter 1 Common Equipment, page 5-2 for a description of the parameters that apply to every card. Release TN4.0.x Turin Networks Page 5-7

TransNav GUI Guide, Section 5: Equipment DS1 Card Parameters DS1 Card Parameters On the Config tab for a DS1 card, configure how the DS1 signal maps to a VC- or a VT-structured payload and to a DS3 channelized signal. Configurable parameters Figure 5-4 DS1 Card Configuration Tab The DS1 card has three additional parameters to configure: DS1 Numbering, page 5-9 DS1 Mapping, page 5-10 DS3 Framing Format, page 5-10 Page 5-8 Turin Networks Release TN4.0.x

Chapter 2 SONET Equipment DS1 Numbering DS1 Numbering Select how the DS1 signals map into a VC- or a VT-structured payload on this card. See Table 5-1 GR-253 and Sequential VT Mapping Formats for the list of mapping formats. If this DS1 card is part of a protection group, this parameter must be the same on both cards. Select one of the following values: GR-253: Non-sequential Sequential (default) Table 5-1 GR-253 and Sequential VT Mapping Formats DS1 Port Non-Sequential (VT Group#, VT#) Sequential (VT Group#, VT#) 1 VTG1, VT1 VTG1-VT1 2 VTG2, VT1 VTG1-VT2 3 VTG3, VT1 VTG1-VT3 4 VTG4, VT1 VTG1-VT4 5 VTG5, VT1 VTG2-VT1 6 VTG6, VT1 VTG2, VT2 7 VTG7, VT1 VTG2, VT3 8 VTG1, VT2 VTG2, VT4 9 VTG2, VT2 VTG3, VT1 10 VTG3, VT2 VTG3, VT2 11 VTG4, VT2 VTG3, VT3 12 VTG5, VT2 VTG3, VT4 13 VTG6, VT2 VTG4, VT1 14 VTG7, VT2 VTG4, VT2 15 VTG1, VT3 VTG4, VT3 16 VTG2, VT3 VTG4, VT4 17 VTG3, VT3 VTG5, VT1 18 VTG4, VT3 VTG5, VT2 19 VTG5, VT3 VTG5, VT3 20 VTG6, VT3 VTG5, VT4 21 VTG7, VT3 VTG6, VT1 22 VTG1, VT4 VTG6, VT2 23 VTG2, VT4 VTG6, VT3 24 VTG3, VT4 VTG6, VT4 25 VTG4, VT4 VTG7, VT1 26 VTG5, VT4 VTG7, VT2 27 VTG6, VT4 VTG7, VT3 28 VTG7, VT4 VTG7, VT4 Release TN4.0.x Turin Networks Page 5-9

TransNav GUI Guide, Section 5: Equipment DS1 Mapping DS1 Mapping DS3 Framing Format DS1 Port Parameters Specifies how the DS1 channels on this card are multiplexed into an STS path or TU container. Select one of the following values: Select VT2/VC12 (default) to multiplex the DS1 channels into a VT2-mapped STS or a VC11-mapped TU-12. Only the first 21 ports are available. Select VT15/VC11 to multiplex the DS1 channels into a VT1.5-mapped STS or a VC11-mapped TU-11. All 28 ports are available. Select DS3-mapped to multiplex the signal into a DS3-mapped STS. All 28 ports are available. Specifies how the signals will be multiplexed into the DS3 signal. Select one of the following values: M23 (default): Seven DS2 signals are asynchronously multiplexed into the DS3 signal. CBIT: 28 DS-1 signals are multiplexed into the DS3 signal with the C-bit used as the control bit. In Shelf View, click a DS1 port, then click the Config tab. The DS1 Port Configuration screen displays. Figure 5-5 DS1 Port Configuration Screen The DS1 Port Configuration screen allows you to view and set the following configuration information: Label: Displays node name Type: Displays port type (DS1) Slot Number: Displays the slot number Port Number: Displays the port number Line Format: Select one of the following formats: ESF (default): Extended superframe format SF: Superframe format Unframed: Upon detecting an LOF condition (in Unframed mode), the system does not: Raise an LOF alarm Page 5-10 Turin Networks Release TN4.0.x

Chapter 2 SONET Equipment DS1 Port Parameters Propagate an AIS Insert an RAI Count OOF and SEF framing errors Line Coding: Displays the line coding technique used for performance monitoring at the line layer. Select one of the following options: 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 distances: 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 options: Yes: Mask AIS/alarm for unused direction No (default): Do not mask AIS/alarm for any direction AIS Insertion: Select one of the following options: Enabled: Generate an AIS when the DS1 signal is degraded. Disabled (default): Do not generate an AIS when the DS1 signal is degraded. Valid Signal Time (Read-only): Displays the number of minutes since the last detection of valid incoming DS1 signal. Customer: Select from the list of defined customers. Default is No Customer Selected. For details, see Adding Customer Information, page 2-31. 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 for DS1 ports. The system default for performance monitoring thresholds is disabled for all parameters. Use the performance monitoring templates to set default thresholds or to customize threshold values. See Section 8 Maintenance and Testing, Chapter 1 Performance Monitoring, page 8-1 for information on how to use performance monitoring templates. See the Node Operations and Maintenance Guide for details on performance monitoring parameters for DS1 ports. Customer Tag: Enter an alphanumeric character string to identify the port to a customer. Alarm Profile: Select from the list of defined alarm profiles (of type ds1_ptp). Default is the default ds1_ptp alarm profile. Release TN4.0.x Turin Networks Page 5-11

TransNav GUI Guide, Section 5: Equipment DS3 Card Parameters Command buttons are as follows: Apply: Apply the configuration information to the selected port. If no configuration information has changed since the last time Apply was clicked, the button is grayed out. Cancel: Cancel the configuration information and refresh the screen with the previously configured information. DS3 Card Parameters On the Config tab for the DS3-12 or DS3-24 cards, change the card type to an E3 card. Figure 5-6 DS3 Card Configuration Screen Use the following command buttons to change this card from a DS3 card to an E3 card. Switch to E3: Switches the mode of all the ports on the card to receive E3 signals. The card must be in the locked administrative state. Apply: After you click the Switch to E3 button, click Apply. The card graphic in the shelf changes to an E3 card. Page 5-12 Turin Networks Release TN4.0.x

Chapter 2 SONET Equipment DS3CC Port Parameters DS3CC Port Parameters The parameters in this section apply to DS3 Clear Channel ports. From Shelf View, click a DS3 port and click the Config tab. The DS3 Port Configuration screen displays. Figure 5-7 DS3 Clear Channel Port Configuration Screen The DS3 Clear Channel Port Configuration screen allows you to view and set the following configuration information: Label: Displays node name Type: Displays port type (DS3CC) Slot Number: Displays the slot number Port Number: Displays the port number Line Format: Select one of the following formats: M23 (default): Seven DS2 signals asynchronously multiplexed into the DS3 signal CBIT: 28 DS-1 signals are multiplexed into the DS3 signal, with the C-bit used as control bit Unframed: Upon detecting an LOF condition (in Unframed mode), the system does not: Raise an LOF alarm Propagate an AIS Insert an RAI Count OOF and SEF framing errors Signal Level (Read-only): Displays DSX-3 RDI: Enables the system to send an RDI (remote defect indicator) signal as soon as it cannot identify valid framing or when it determines it is receiving an AIS. Enabled: Select to allow the system to send an RDI signal. Disabled: Select so the system does not send an RDI. C-Bit Processing (Read-only): No. indicates that the system does not process C-bits as shown in GR-499-CORE Table 10-14. AIS Mask (Alarm Indication Signal Mask): Select one of the following options: Yes: Mask AIS/alarm for unused direction No (default): Do not mask AIS/alarm for any direction Release TN4.0.x Turin Networks Page 5-13

TransNav GUI Guide, Section 5: Equipment DS3CC Port Parameters AIS Format: Select one of the following formats: 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 Coding (Read-only): B3ZS (Bipolar with Three Zero Substitution) Line Build Out: Select the length of cable between the node and the intermediate DS3 patch panel: 0 225 ft (default) 255 450 ft Customer: Select from the list of defined customers. Default is No Customer Selected. For details see Adding Customer Information, page 2-31. PM Template: Select from the list of defined performance monitoring templates (of type ds3_ptp_pm). Default is default, which contains default thresholds for performance monitoring parameters. The system default for performance monitoring thresholds is disabled for all parameters. Use the performance monitoring templates to set default thresholds or to customize threshold values. See Section 8 Maintenance and Testing, Chapter 1 Performance Monitoring, page 8-1 for information on how to use performance monitoring templates. See the Node Operations and Maintenance Guide for details on performance monitoring parameters for DS3 ports. Customer Tag: Enter an alphanumeric character string to identify the port to a customer. Alarm Profile: Select from the list of defined alarm profiles (of type ds_ptp). Default is default. Command buttons are as follows: Switch to EC1 (DS3CC only): Switch port to EC-1. Note: The port administrative state must be Locked before switching to EC-1. To lock the port, click the lock icon in the bottom left of the screen and click Apply. Apply: Apply the configuration information to the selected port. If no configuration information has changed since the last time Apply was clicked, button is grayed out. Cancel: Cancel the configuration information and refresh the screen with the previously configured information. Page 5-14 Turin Networks Release TN4.0.x

Chapter 2 SONET Equipment DS3TMX and STS1TMX Port Parameters DS3TMX and STS1TMX Port Parameters The parameters in this section apply to DS3TMX and STS1TMX ports. From Shelf View, click a port on the DS3TMX card. Click the Config tab to display the Port Configuration screen. Figure 5-8 DS3TMX Port Config Tab Label: Displays node name Type: Displays port type (DS3TMX or STS1TMX) Slot Number: Displays the slot number Port Number: Displays the port number Line Format: Select one of the following formats: M23 (default for STS1TMX): Seven DS2 signals asynchronously multiplexed into the DS3 signal CBIT (default for DS3TMX): 28 DS-1 signals are multiplexed into the DS3 signal, with the C-bit used as control bit Signal Level (Read-only. DS3TMX only): Displays DSX-3 DS3 Mapping: Select the payload of the DS3 channelized signal: DS1 E1 Subport Numbering: Select how the DS1 signals map into a VT payload on this port. See Table 5-1 GR-253 and Sequential VT Mapping Formats, page 5-9 for the list of mapping formats. If this port is part of a protection group, this parameter must be the same on both cards. Select one of the following values: Non-Sequential (default) Sequential Subport Mapping (Read-only if DS3 Mapping is E1): Select how the DS1 channels are multiplexed into an STS or a TU container. Configurable only if DS3 Mapping is DS1. VT1.5/VC11 (default): The DS1 channel is carried in a VT1.5-mapped STS or a TU-11 container. All 28 subports are available. Release TN4.0.x Turin Networks Page 5-15

TransNav GUI Guide, Section 5: Equipment DS3TMX and STS1TMX Port Parameters VT2/VC12: The DS1 channel is carried in a VT2-mapped STS or a TU-12 container. Only the first 21 subports are available. AIS Mask (Alarm Indication Signal Mask): Select one of the following options: Yes: Mask AIS/alarm for unused direction No (default): Do not mask AIS/alarm for any direction AIS Format: Select one of the following formats: 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 Coding (Read-only for DS3TMX): B3ZS (Bipolar with Three Zero Substitution) Line Build Out (DS3TMX only): Select the length of cable between the node and the intermediate DS3 patch panel: 0 225 ft (default) 255 450 ft Customer: Select from the list of defined customers. Default is No Customer Selected. For details see Adding Customer Information, page 2-31. PM Template (DS3TMX only): Select from the list of defined performance monitoring templates (of type ds3_ptp_pm). Default is default, which contains default thresholds for performance monitoring parameters. The system default for performance monitoring thresholds is disabled for all parameters. Use the performance monitoring templates to set default thresholds or to customize threshold values. See Section 8 Maintenance and Testing, Chapter 1 Performance Monitoring, page 8-1 for information on how to use performance monitoring templates. See the Node Operations and Maintenance Guide for details on performance monitoring parameters for DS3 ports. Customer Tag: Enter an alphanumeric character string to identify the port to a customer. Alarm Profile (DS3TMX only): Select from the list of defined alarm profiles (of type ds_ptp). Default is default. Command buttons are as follows: Switch: Switch the port mode to one of the following modes: DS3CC: Changes this port to a DS3 clear channel port EC1: Changes this port to an EC1 port DS3TMX (default): Changes this port to a DS3TMX port STS1TMX: This port is used as an optical transmux resource Apply: Apply the configuration information to the selected port. If no configuration information has changed since the last time Apply was clicked, the button is grayed out. Cancel: Cancel the configuration information and refresh the screen with the previously configured information. Page 5-16 Turin Networks Release TN4.0.x

Chapter 2 SONET Equipment Subport Parameters Subport Parameters The parameters in this section apply to DS3TMX and STS1TMX ports. From Shelf View, click a port on the DS3TMX card. Click the Config tab to display the Port Configuration screen. Figure 5-9 Subports on a DS3TMX or an STS1TMX Port At the bottom of the Port Configuration screen, the subports appear in a table format. The columns in this table are as follows: Subport #: Displays the subport numbers in the DS3. Displays 28 subports if DS3 Mapping is DS1. Displays 21 subports if DS3 Mapping is E1. Op. State: Displays the operational state of the subport. Disabled (default): Adm. State is locked Enabled: Indicates the Adm. State is unlocked Adm. State: Displays the administrative state of the subport Lock (default): Disable the subport and suppresses alarms Unlock: Enable the subport and monitor performance If DS3 Mapping on the parent TMX port is DS1, select one of the following values in the Line Format column: ESF (default): Extended superframe format SF: Superframe format Unframed: Upon detecting an LOF condition (in Unframed mode), the system does not: Raise an LOF alarm Propagate an AIS Insert an RAI Count OOF and SEF framing errors Release TN4.0.x Turin Networks Page 5-17

TransNav GUI Guide, Section 5: Equipment Subport Parameters If the DS3 Mapping on the parent TMX port is E1, select one of the following values in the Line Format column: Basic Frame: Select 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. Multi-Frame (default): Select 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. Unframed: Select so that upon detecting a LOF condition (in Unframed mode), the system does not: Raise a LOF alarm Propagate an AIS Insert a RAI Count OOF and SEF framing errors Loopback: Select the type of loopback to apply to this subport. Clear (default): Clear loopback command Facility: Perform a facility loopback on this port Terminal: Perform a terminal loopback on this port PM Template: Select from the list of defined performance monitoring templates (of type ds1_ptp_pm or e1_ptp_pm). Default is default, which contains default thresholds for performance monitoring parameters. The system default for performance monitoring thresholds is disabled for all parameters. Use the performance monitoring templates to set default thresholds or to customize threshold values. See Section 8 Maintenance and Testing, Chapter 1 Performance Monitoring, page 8-1 for information on how to use performance monitoring templates. See the Node Operations and Maintenance Guide for details on performance monitoring parameters. Alarm Profile: Select from the list of defined alarm profiles (of type ds1_ptp). Default is default. Page 5-18 Turin Networks Release TN4.0.x

Chapter 2 SONET Equipment EC1 Port Parameters EC1 Port Parameters Click a DS3 port, then click Switch to EC1. The EC1 Port Configuration screen displays. Figure 5-10 EC1 Port Configuration Screen The EC1 Port Configuration screen allows you to view and set the following configuration information: Label: Displays node name Type: Displays port type (EC1) Slot Number: Displays the slot number Port Number: Displays the port number Line Format: Displays SONET Signal Level: Displays DSX-3 AIS Mask (Alarm Indication Signal Mask): Select one of the following options: Yes: Mask AIS/alarm for unused direction No (default): Do not mask AIS/alarm for any direction Line Coding (Read-only): B3ZS (Bipolar with Three Zero Substitution). Sync Source: Displays the timing source priority for this port. For details on selecting this port as a timing source, see Chapter 2 Timing, Line Timing, page 3-23. Displays one of the following options: Not used: This port has not been set as a timing source. Primary (default): This port has been set as the primary timing source. Secondary: This port has been set as the secondary timing source. Third: This port has been set as the third timing source. Fourth: This port has been set as the fourth timing source. Input Sync Msgs: Displays the receiving SSM (synchronization status messages) value for this port. Possible values are: Stratum 1: Stratum 1 Traceable Synch-Trace Unknown: Synchronized - Traceability Unknown Stratum 2: Stratum 2 Traceable Release TN4.0.x Turin Networks Page 5-19

TransNav GUI Guide, Section 5: Equipment EC1 Port Parameters Transit Node: Transit Node Clock Traceable Stratum 3E: Stratum 3E Traceable Stratum 3: Stratum 3 Traceable SONET Minimum Clock: SONET Minimum Clock Traceable (20 ppm clock) Stratum 4/4e: Stratum 4/4E Traceable Don t use for synch: Don t use for synchronization User s Provisionable: Provisionable by network operator Idle pattern: An idle pattern is being transmitted/received Output Sync Msgs: Displays the transmitting SSM (synchronization status messages) value for this port. Possible values are: Stratum 1: Stratum 1 Traceable Synch-Trace Unknown: Synchronized - Traceability Unknown Stratum 2: Stratum 2 Traceable Transit Node: Transit Node Clock Traceable Stratum 3E: Stratum 3E Traceable Stratum 3: Stratum 3 Traceable SONET Minimum Clock: SONET Minimum Clock Traceable (20 ppm clock) Stratum 4/4e: Stratum 4/4E Traceable Don t use for synch: Don t use for synchronization User s Provisionable: Provisionable by network operator Idle pattern: An idle pattern is being transmitted/received Valid Signal Timer (min): Displays 120. Line Build Out: The cable length from the node to the other end of the EC-1 connection. Select one of the following distances: 0 225 ft (default) 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 1E-4: Value equals 1 x 10-4 1E-5: Value equals 1 x 10-5 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: 1E-9: Value equals 1 x 10-9 1E-8: Value equals 1 x 10-8 1E-7: Value equals 1 x 10-7 1E-6 (default): Value equals 1 x 10-6 1E-5: Value equals 1 x 10-5 Page 5-20 Turin Networks Release TN4.0.x

Chapter 2 SONET Equipment EC1 Port Parameters Customer: Select from the list of defined customer profiles. Default is No Customer Selected. For details on creating customer profiles, see Adding Customer Information, page 2-31. PM Template: Select from the list of defined performance monitoring templates (of type ec1_ptp_pm). Default is default, which contains default thresholds for performance monitoring parameters. The system default for performance monitoring thresholds is disabled for all parameters. Use the performance monitoring templates to set default thresholds or to customize threshold values. See Section 8 Maintenance and Testing, Chapter 1 Performance Monitoring, page 8-1 for information on how to use performance monitoring templates. See the Node Operations and Maintenance Guide for details on performance monitoring parameters for EC1 ports. Customer Tag: Enter an alphanumeric character string to identify the port to a customer. Alarm Profile: Select from the list of defined alarm profiles (of type ds_ptp). Default is default. Command buttons are as follows: Switch to DS3: Switch port to DS3. Note: The port administrative state must be Locked before switching to DS3. To lock the port, click the lock icon in the bottom left of the screen and click Apply. Apply: Apply the configuration information to the selected port. If no configuration information has changed since the last time Apply was clicked, the button is grayed out. Cancel: Cancel the configuration information and refresh the screen with the previously configured information. Icons in the bottom left-hand corner indicate the operational and administrative state of a card or port. For details, see Chapter 1 Common Equipment, Equipment States, page 5-2. Release TN4.0.x Turin Networks Page 5-21

TransNav GUI Guide, Section 5: Equipment SONET (OC-N) Card Parameters SONET (OC-N) Card Parameters On the Config tab for any SONET card, configure the point at which the system raises a path-level signal failed bit error rate (SFBER) or signal degraded bit error rate (SDBER) alarm. Configurable parameters Figure 5-11 OC-192 Card Parameters These parameters appear depending on the speed of the SONET interface and apply to all the paths on the card. STS-1 SF BER, STS-3c SF BER, STS-12c SF BER, and STS-48c SF BER: Measures the transmission quality 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 1 x 10-4 1E-5 (default for STS-48c SF BER): Value equals 1 x 10-5 STS-1 SD BER, STS-3c SD BER, STS-12c SD BER, and STS-48c SD BER: Measures the transmission quality of degraded signals 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-5: Value equals 1 x 10-5 1E-6 (default for STS-1 SD BER): Value equals 1 x 10-6 1E-7 (default for STS-3c and STS-12c SD BER): Value equals 1 x 10-7 1E-8 (default for STS-48c SD BER): Value equals 1 x 10-8 1E-9: Value equals 1 x 10-9 1E-10: Value equals 1 x 10-10 1E-11: Value equals 1 x 10-11 FEC (OC-192 only): Forward error correction. Improves the link budget of this signal approximately 3 db. The resulting signal is no longer SONET/SDH compliant. Both ends of this link must have the same value in this parameter or the link will fail. Enabled. Select to activate the FEC feature Disabled (default) Page 5-22 Turin Networks Release TN4.0.x

Chapter 2 SONET Equipment SONET Port Parameters SONET Port Parameters From Shelf View, click a SONET port and click the Config tab. The SONET Port Configuration screen displays. Figure 5-12 SONET Port Configuration Screen The SONET Port Configuration screen allows you to view and set the following configuration information: Label: Displays the node name Type: Displays the port type (OC3, OC12, OC48, OC192, or EC3) Slot Number: Displays the slot number Port Number: Displays the port number Line Format: Displays SONET AIS Mask (Alarm Indication Signal Mask): Yes: Mask AIS/alarm for unused direction No (default): Do not mask AIS/alarm for any direction Sync Source: Displays the timing source priority for this port. For details on selecting this port as a timing source, see Chapter 2 Timing, Line Timing, page 3-23. Displays one of the following options: Not used (default): This port has not been set as a timing source Primary: This port has been set as the primary timing source Secondary: This port has been set as the secondary timing source Third: This port has been set as the third timing source Fourth: This port has been set as the fourth timing source Note: Timing is restricted to a single port at any time for OC3 or STM1 cards. SfBer-L: Measures the transmission quality (bit error ratio) of failed signals on the link. When the error rate crosses the value specified in this parameter, the system raises a signal failed bit error rate (BERSF-L) alarm and performs a protection switch. Release TN4.0.x Turin Networks Page 5-23

TransNav GUI Guide, Section 5: Equipment SONET Port Parameters Select one of the following values: 1E-3 (default): Value equals 1 x 10-3 1E-4: Value equals 1 x 10-4 1E-5: Value equals 1 x 10-5 Transmitter State (Does not apply to EC3): Select one of the following: On (default): Laser is turned on Off: Laser is turned off Transmitter Auto Shutdown (Does not apply to EC3): Automatically shut down the transmit laser on optical interfaces when the system detects a receive LOS for 500 ms. The system turns the transmit laser off after detecting a receive LOS for 800 ms. The system raises the ALS alarm against the optical facility when the transmitter has been turned off automatically. Disabled (default): The ALS feature is turned off. Manual: The operator initiates a single laser pulse from the transmitter for the amount of time specified in the Recovery Pulse Width parameter. To send the single laser pulse, click the Current Transmitter State button, then click Manual Restart. Automatic: The system turns off the transmit laser for a random time between 100 and 300 seconds. The transmit laser turns on if one of the following conditions occur: The user manually sends a single laser pulse (Current Transmitter State button). If the system receives a valid signal for more than 800 ms. After the random timer expires, the system sends periodic laser pulses from the transmitter for the amount of time specified in the Recovery Pulse Width parameter. Recovery Pulse Width (Does not apply to EC3): The system enables the transmitter for the amount of time specified in this parameter. Valid only if the value in Transmitter Auto Shutdown is Manual or Automatic. Enter a time between 2 and 10 seconds; default is 5 seconds. Input Sync Msgs: Displays the receiving synchronization status messages (SSM) value for this port. Possible values are: Stratum 1: Stratum 1 Traceable Synch-Trace Unknown: Synchronized - Traceability Unknown Stratum 2: Stratum 2 Traceable Transit Node: Transit Node Clock Traceable Stratum 3E: Stratum 3E Traceable Stratum 3: Stratum 3 Traceable SONET/SDH Minimum Clock: SONET Minimum Clock Traceable (20 ppm clock) Stratum 4/4e: Stratum 4/4E Traceable Don t use for synch: Don t use for synchronization User s Provisionable: Provisionable by network operator Idle pattern: An idle pattern is being transmitted/received Page 5-24 Turin Networks Release TN4.0.x

Chapter 2 SONET Equipment SONET Port Parameters Output Sync Msgs: Displays the transmitting SSM (synchronization status messages) value for this port. Possible values are: Stratum 1: Stratum 1 Traceable Synch-Trace Unknown: Synchronized - Traceability Unknown Stratum 2: Stratum 2 Traceable Transit Node: Transit Node Clock Traceable Stratum 3E: Stratum 3E Traceable Stratum 3: Stratum 3 Traceable SONET/SDH Minimum Clock: SONET Minimum Clock Traceable (20 ppm clock) Stratum 4/4e: Stratum 4/4E Traceable Don t use for synch: Don t use for synchronization User s Provisionable: Provisionable by network operator Idle pattern: An idle pattern is being transmitted/received Forced DUS (Do not Use for Synchronization): Select for this port to transmit the SSM (synchronization status message) DUS. This prevents the remote node that receives this signal from using the line as a timing reference. SdBer-L: Measures the transmission quality (bit error ratio) of degraded signals on the optical link. When the error rate crosses the value specified in this parameter, the system raises a signal degraded bit error rate (BERSD-L) alarm and performs a protection switch. Select one of the following values: 1E-9: Value equals 1 x 10-9 1E-8: Value equals 1 x 10-8 1E-7: Value equals 1 x 10-7 1E-6 (default): Value equals 1 x 10-6 1E-5: Value equals 1 x 10-5 Current Transmitter State (Does not apply to EC3): Click this button to display the current state of the optical transmitter. See the Transmitter Auto Shutdown parameter above for details. Fwd Section Trc Fmt (Forward Section Trace Format): This port transmits an access point identifier in the J0 byte of the SONET frame so the section receiver can verify its continued connection. 16 bytes (default): Select this value if the receiver is an SDH port 64 bytes: Select this value if the receiver is another SONET port Fwd Section Trace: The access point identifier transmitted in the J0 byte. Enter an alphanumeric character string. SS Bit Transmit: Select the SS Bit value that this interface is transmitting: 00 (default): This interface is transmitting SONET frames 10: This interface is transmitting STM frames Rev Section Trc Fmt (Reverse Section Trace Format): This port expects an access point identifier in the J0 byte of the SONET frame to verify its continued connection with the transmitter. If this port receives an incorrect identifier, the system raises an S-TIM (Section - Trace Identifier Mismatch alarm). Release TN4.0.x Turin Networks Page 5-25

TransNav GUI Guide, Section 5: Equipment SONET Port Parameters 16 bytes (default): Select this value if the transmitter is a SDH port. 64 bytes: Select this value if the transmitter is another SONET port. Rev Section Trace: The expected access point identifier to be received in the J0 byte. Enter an alphanumeric character string. SS Bit Receive: Indicates the SS bit value that this interface is receiving. Current Received Section Trace: Indicates the section trace currently being received. Customer: Select from the list of defined customer profiles. Default is No Customer Selected. For details on creating customer profiles, see Adding Customer Information, page 2-31. PM Template: Select from the list of defined performance monitoring templates. Default is default, which contains default thresholds for performance monitoring parameters. The system default for performance monitoring thresholds is disabled for all parameters. Use the performance monitoring templates to set default thresholds or to customize threshold values. See Section 8 Maintenance and Testing, Chapter 1 Performance Monitoring, page 8-1 for information on how to use performance monitoring templates. See the Node Operations and Maintenance Guide for details on performance monitoring parameters for SONET ports. Customer Tag: Enter an alphanumeric character string to identify the port to a customer. Alarm Profile: Select from the list of defined alarm profiles. Default is default. Control Data (Does not apply to EC3): Indicates whether the management system uses the data communications channel (DCC) bytes on this SONET interface to communicate with other nodes. Select one of the following options: Enabled (default for OC-12 and OC-48 ports): The management system uses this interface for management traffic. Enabled is not an option for OC-3 ports. Disabled (Read-only for OC-3 ports): The management system does not use this interface for management traffic. Note: The data control channel (DCC) is unavailable over an EC-3/STM-1E link. Terminate DCC (Does not apply to EC3): This parameter is specific to each SONET interface and specifies which DCC bytes to process. You can only change the value in this parameter if the value in Control Data is Disabled. 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 uses the combined section DCC and line DCC bytes from the first, second, and third STS on the interface (2.3 Mbps) for management traffic. This selection is available for Traverse to Traverse interworking only. It is unsupported for Traverse to TE-100 interworking. Page 5-26 Turin Networks Release TN4.0.x

Chapter 2 SONET Equipment SONET Port Parameters Path (TE-100 OC-3 and OC-12 interfaces only): Specifies that the interface uses the F2 byte (64 Kbps) of the selected STS for management traffic. Click the Path DCC Configuration button to select the STS. Path DCC Configuration (TE-100 OC-3, and OC-12 interfaces only. Does not apply to EC3): Click this button to configure the SONET paths to carry management traffic. L2 Protocol (Does not apply to EC3): Determines the Layer 2 (L2) protocol for this port. PPP (default): Point-to-point protocol. Use PPP if this port is connected to another Traverse platform. LAPD: Link access procedure D-channel. Select LAPD if this port is connected to legacy third-party ADM equipment and this node is used as an OSI DCC gateway node. LAPD Role (Does not apply to EC3): Select the role of this node in the OSI DCC gateway application: Network User DWDM wl supp value (Does not apply to EC3): The DWDM wavelength supplied value. LAPD Mode (Does not apply to EC3): Select the mode of this node in the OSI DCC gateway application. AITS: Acknowledge information transfer service. Use this value if the value in L2 Protocol is LAPD. UITS (default): Unacknowledge information transfer service. Use this value if the value in L2 Protocol is PPP. LAPD MTU (Does not apply to EC3): Indicates the maximum transmission unit for this node if the value in L2 Protocol is PPP. Default is 512. DWDM wl (Does not apply to EC3): Select from the list of defined wavelength frequencies. For frequency to wavelength data, see the Traverse Product Overview Guide, Section 3 Card (Module) Descriptions, Chapter 4 SONET/SDH Cards, page 3-25. Command buttons are as follows: Apply: Apply the configuration information to the selected port. If no configuration information has changed since the last time Apply was clicked, the button is grayed-out. Cancel: Cancel the configuration information and refresh the screen with the previously configured information. Release TN4.0.x Turin Networks Page 5-27

TransNav GUI Guide, Section 5: Equipment SFP Port Parameters SFP Port Parameters On a Turin Node in Shelf View, click an SFP or an optical port, then click the Config tab to display the Port Configuration screen. If a pluggable transceiver is in use on a card, the SFP information displays. Note: Turin does not support swapping of transceivers Figure 5-13 SFP Fields on Port Configuration Screen The Port Configuration screen displays the following information: Label: Displays the name of the node. Type: Displays the type of port where the transceiver is located. The port can be an SFP (small form pluggable), XFP (10 Gbps small form pluggable), or an optical port. Alarm Profile: Displays the alarm profile (of type shelf) used to monitor this SFP or XFP. The default is the default shelf profile. Slot Number: Displays the slot number on the shelf where the card with the SFP or XFP port exists. Port Number: Displays the port number on the card where the SFP or XFP exists. Identifier: Identifies the transceiver type. For example, Small Form-factor Pluggable Transceiver. Wavelength (nm): Displays the laser wavelength of the transceiver in nanometers. Diag Monitoring Type: Displays the type of diagnostic monitoring that is implemented (if any) in the transceiver. Vendor Name: Displays the name of the hardware vendor. Vendor Rev: Displays the vendor s hardware revision number. Date Code: Displays the date the hardware was manufactured. SFP Refresh (SFP Transceiver only): Select this button to refresh information for the SFP transceiver information a few minutes after the card is rebooted. XFP Refresh (XFP Transceiver only): Select this button to refresh the information for the XFP transceiver a few minutes after the card is rebooted. BR,Nominal (100MBs): Displays the nominal bit rate in increments of 100 Mbps. Vendor PN: Displays the part number of the vendor of the hardware. Vendor SN: Displays the serial number of the vendor of the hardware. Page 5-28 Turin Networks Release TN4.0.x

Chapter 2 SONET Equipment SFP Port Parameters Diagnostic Parameters: Click this button to display diagnostic information on the SFP or XFP hardware. Figure 5-14 Diagnostic Parameters Dialog Box The Diagnostic Parameters dialog box displays the following information: Measured Temperature: Indicates the current temperature of the transceiver. Measured in degrees Celsius ( C). Displays -128 to + 128 ± < 3 C. Measured Supply Voltage: Indicates the current voltage the hardware is using. Measured in 100µ volts (micro volts). Displays 0 to 6.55 ± < 3%. Measured TX Bias Current: Displays 0 to 131 ma ± <10%. Measured in 2µA. Measured TX Output Power: Displays 0 to 6.55 mw (-40 to +8.2 dbm ± <3dB) in units of 0.1µW. This value should be consistent among ports of the same transceiver type. Measured in 10 log [(read value x 10-6)/(10-3)] dbm. Measured RX Input Power: Displays 0 to 6.55 mw (-40 to +8.2 dbm ± <3dB) in units of 0.1µW. This value will vary from port to port because of received optical signal power differences. Measured in 10 log [(read value x 10-6)/(10-3)] dbm. Command buttons are as follows: Refresh: Renew the data in the display. Done: Close the dialog box and return to the main configuration screen. Release TN4.0.x Turin Networks Page 5-29

TransNav GUI Guide, Section 5: Equipment SFP Port Parameters Page 5-30 Turin Networks Release TN4.0.x

SECTION 5EQUIPMENT Chapter 3 SDH Equipment Introduction E1 Card Parameters This chapter explains all the parameters that appear on each card (card). E1 Card Parameters, page 5-31 E1 Mapping and Patch Panel Ports (Traverse only), page 5-34 TE-100 Interface Card Parameters, page 5-35 E1 Port Parameters, page 5-36 E3 Card Parameters, page 5-38 E3 Port Parameters, page 5-38 SDH (STM) Card Parameters, page 5-40 STM Port Parameters, page 5-41 See Chapter 1 Common Equipment, page 5-1 for a description of the parameters that apply to every card. On a Traverse node in Shelf View, click an E1 card, then click the Config tab. Configure how the E1 signal maps to a VC-structured payload and to a channelized DS3 signal. Configurable parameters Figure 5-15 E1 Card Card Configuration Tab The E1 card has two parameters to configure: E1 Numbering (Traverse only), page 5-32 E1 Mapping, page 5-33 Important: It is important to know how the E1 ports physically map to the patch panel. See E1 Mapping and Patch Panel Ports (Traverse only), page 5-34. Release TN4.0.x Turin Networks Page 5-31

TransNav GUI Guide, Section 5: Equipment E1 Numbering (Traverse only) E1 Numbering (Traverse only) Select how the E1 channels map into a VC-structured payload. If this E1 card is part of a protection group, this parameter must be the same on both cards. Select one of the following values: Sequential: See Table 5-2 E1 Sequential and Non-Sequential Mapping Formats, page 5-32 Non-Sequential: See Table 5-2 E1 Sequential and Non-Sequential Mapping Formats, page 5-32 Table 5-2 E1 Sequential and Non-Sequential Mapping Formats E1 Port Sequential (TUG2#,TU12#) Non-Sequential (TUG2#,TU12#) 1 1, 1 1, 1 2 1, 2 2, 1 3 1, 3 3, 1 4 2, 1 4, 1 5 2, 2 5, 1 6 2, 3 6, 1 7 3, 1 7, 1 8 3, 2 1, 2 9 3, 3 2, 2 10 4, 1 3, 2 11 4, 2 4, 2 12 4, 3 5, 2 13 5, 1 6, 2 14 5, 2 7, 2 15 5, 3 1, 3 16 6, 1 2, 3 17 6, 2 3, 3 18 6, 3 4, 3 19 7, 1 5, 3 20 7, 2 6, 3 21 7, 3 7, 3 Page 5-32 Turin Networks Release TN4.0.x

Chapter 3 SDH Equipment E1 Mapping E1 Mapping Specifies how the E1 signal is multiplexed into the virtual container. Select one of the following values: VC12 (default): Signal is multiplexed into a VC12 container DS3-mapped VC3: Signal is multiplexed into a DS3 which is then mapped to a VC3. E1 ports are mapped according to the following table: Table 5-3 DS3-structured VC3-mapped E1 channels E1 port 6312 Kbps signal #, E1 channel # 1 1, 1 2 1, 2 3 1, 3 4 2, 1 5 2, 2 6 2, 3 7 3, 1 8 3, 2 9 3, 3 10 4, 1 11 4, 2 12 4, 3 13 5, 1 14 5, 2 15 5, 3 16 6, 1 17 6, 2 18 6, 3 19 7, 1 20 7, 2 21 7, 3 Release TN4.0.x Turin Networks Page 5-33

TransNav GUI Guide, Section 5: Equipment E1 Mapping and Patch Panel Ports (Traverse only) E1 Mapping and Patch Panel Ports (Traverse only) This table lists the relationship between the physical E1 port and the patch panel for E1 Mapping modes. Table 5-4 E1 Mapping and Patch Panel Ports EI Ports DS3-Mapped Patch Panel Ports VC12-Mapped 1 1 1 2 2 2 3 3 3 4 5 4 5 6 5 6 7 6 7 9 7 8 10 8 9 11 9 10 13 10 11 14 11 12 15 12 13 17 13 14 18 14 15 19 15 16 21 16 17 22 17 18 23 18 19 25 19 20 26 20 21 27 21 Page 5-34 Turin Networks Release TN4.0.x

Chapter 3 SDH Equipment TE-100 Interface Card Parameters TE-100 Interface Card Parameters On a Traverse node in Shelf View, click the interface card, then click the Config tab. The Card Configuration screen displays. Figure 5-16 TE-100 Interface Card Parameters See Chapter 1 Common Equipment, page 5-1 for a description of the parameters that apply to every card. VC3 Mode: This parameter is valid only when the node is commissioned in ITU mode. Select the multiplex structure for VC3 paths for the entire shelf. All TE-100 nodes in the same ring must have the same value in this parameter. TU3/VC3 (default): Sets the multiplex structure for VC3 paths to AUG-1/AU-4/TU-3/VC-3 AU3/VC3: Set the multiplex structure for VC3 paths to AUG-1/AU-3/VC-3 E1 Mapping: See E1 Mapping, page 5-33. Important: See the TraverseEdge 100 User Guide, Section 5 Creating TDM Services, Chapter 7 Creating SDH Services, page 5-61 for guidelines on creating SDH services on a TE-100 system. For all other parameters on the Interface Card, see Chapter 4 Ethernet Equipment, page 5-49. Command buttons are as follows: Switch to DS3: Switches all E3 ports on this shelf to DS3 mode. Lock the administrative state of the card. Click Apply. Click the Switch to DS3 button, then click Apply again. The button then changes to read Switch to E3. Apply: Apply the configuration information to the selected port. If no configuration information has changed since the last time Apply was clicked, button is grayed out. Cancel: Cancel the configuration information and refresh the screen with the previously configured information. Release TN4.0.x Turin Networks Page 5-35

TransNav GUI Guide, Section 5: Equipment E1 Port Parameters E1 Port Parameters On a Traverse node Shelf View, click an E1 port, then click the Config tab. The E1 Port Configuration screen displays. Figure 5-17 E1 Port Configuration Screen The E1 Port Configuration screen allows you to view and set the following configuration information: Label: Displays node name. Type: Displays port type (E1). Slot Number: Displays the slot number. Port Number: Displays the port number. Line Format: Select one of the following: Basic Frame: Select 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. Multi-Frame: Select 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. Unframed: Select so that upon detecting an LOF condition (in Unframed mode), the system does not: Raise an LOF alarm Propagate an AIS Insert an RAI Count OOF and SEF framing errors Line Coding: Displays the line coding technique used for performance monitoring at the line layer. HDB3 (default): High Density Bipolar of order 3 Line Build Out: Displays the distance from the subscriber interface to the physical port on the node. Select one of the following: Short Haul (default) Gain Mode AIS Mask (Alarm Indication Signal Mask): Select one of the following: Yes: Mask AIS alarm for unused direction No (default): Do not mask AIS alarm for any direction Page 5-36 Turin Networks Release TN4.0.x

Chapter 3 SDH Equipment E1 Port Parameters AIS Insertion: Select one of the following: Enabled (default): Generate an AIS when VC12 signal is degraded. Disabled: Do not generate an AIS when VC12 signal is degraded Valid Signal Timer (Read-only): Displays the number of minutes since the last detection of valid incoming E1 signal. Customer: Select from the list of defined customers. The default is No Customer Selected. For details see Adding Customer Information, page 2-31. Customer Tag: Enter an alphanumeric character string to identify the port to a customer. PM Template: Select from the list of defined performance monitoring templates for E1 ports (e1_ptp_pm). Default value is default, which means the system-default e1_ptp_pm template. The system default for performance monitoring thresholds is disabled for all parameters. Use the performance monitoring templates to set default thresholds or to customize threshold values. See Section 8 Maintenance and Testing, Chapter 1 Performance Monitoring, page 8-1 for information on how to use performance monitoring templates. See the Node Operations and Maintenance Guide for details on performance monitoring parameters for E1 ports. Alarm Profile: Select from the list of defined alarm profiles for E1 ports. Default is the default e1_ptp alarm profile. Command buttons are as follows: Apply: Apply the configuration information to the selected port. If no configuration information has changed since the last time Apply was clicked, button is grayed out. Cancel: Cancel the configuration information and refresh the screen with the previously configured information. Release TN4.0.x Turin Networks Page 5-37

TransNav GUI Guide, Section 5: Equipment E3 Card Parameters E3 Card Parameters On the Traverse shelf, it is possible to change the E3-CC cards to DS3-CC cards. Additionally, on the TE-100 shelf, it is possible to change the E3-CC ports to DS3-CC ports. On a Traverse node in Shelf View, click an E3 card, then click the Config tab. On a TE-100 shelf, click the interface card in slot 3, then click the Config tab. Figure 5-18 E3 Card Configuration Screen The following command buttons on this screen exist to change this card from an E3 card to a DS3 card. Switch to DS3: Switches the mode of all the ports on the card to receive DS3 signals. The card must be in the locked administrative state. Apply: After you click the Switch to DS3 button, click Apply. The card graphic in the shelf changes to a DS3 card. E3 Port Parameters On a Traverse node in Shelf View, click an E3 port and click the Config tab. The E3 Clear Channel Port Configuration screen displays. Figure 5-19 E3 Port Configuration Screen The E3 Clear Channel Port Configuration screen allows you to view and set the following configuration information: Label: Displays node name. Type: Displays port type (E3CC). Slot Number: Displays the slot number. Page 5-38 Turin Networks Release TN4.0.x

Chapter 3 SDH Equipment E3 Port Parameters Port Number: Displays the port number. Line Format: Select one of the following: Unframed (default TE-100) G.751 (default Traverse) G.832 Line Coding (Read-only): HDB3. High density bipolar 3. Line Build Out: Select one of the following: 0 225 ft (default) 255 450 ft AIS Mask (Alarm Indication Signal Mask). Select one of the following: Yes: Mask AIS/alarm for unused direction. No (default): Do not mask AIS/alarm for any direction. Customer: Select from the list of defined customers. Default is No Customer Selected. For details see Adding Customer Information, page 2-31. PM Template: Select from the list of defined performance monitoring templates (of type e3_ptp_pm). Default is default, which contains default thresholds for performance monitoring parameters. The system default for performance monitoring thresholds is disabled for all parameters. Use the performance monitoring templates to set default thresholds or to customize threshold values. See Section 8 Maintenance and Testing, Chapter 1 Performance Monitoring, page 8-1 for information on how to use performance monitoring templates. See the Node Operations and Maintenance Guide for details on performance monitoring parameters for E3 ports. Customer Tag: Enter an alphanumeric character string to identify the port to a customer. Alarm Profile: Select from the list of defined alarm profiles (of type ds_ptp). Default is default. Command buttons are as follows: Apply: Apply the configuration information to the selected port. If no configuration information has changed since the last time Apply was clicked, button is grayed out. Cancel: Cancel the configuration information and refresh the screen with the previously configured information. Release TN4.0.x Turin Networks Page 5-39

TransNav GUI Guide, Section 5: Equipment SDH (STM) Card Parameters SDH (STM) Card Parameters Configure any STM card to indicate the point at which the system raises a path-level signal failed bit error rate (SFBER) or signal degraded bit error rate (SDBER) alarm. On a Traverse node in Shelf View for any STM card, click the Config tab. The Card Configuration screen displays. Configurable parameters Figure 5-20 STM-64 Card Parameters These parameters appear depending on the speed of the SDH interface and apply to all the paths on the card. VC-3 SF BER, VC-4 SF BER, VC-4-4c SF BER, and VC-4-16c SF BER: Measures the transmission quality of failed signals in the High Order path. When the error rate crosses the value specified in this parameter, the system raises a signal failed bit error rate (BERSF-P) alarm. Select one of the following values: 1E-3 (default for VC-3 SF BER): Value equals 1 x 10-3 1E-4 (default for VC-4 and VC-4-4c SF BER): Value equals 1 x 10-4 1E-5 (default for VC-4-16c SF BER): Value equals 1 x 10-5 VC-3 SD BER, VC-4 SD BER, VC-4-4c SD BER, and VC-4-16c SD BER: Measures the transmission quality of degraded signals in the High Order path. When the error rate crosses the value specified in this parameter, the system raises a signal degraded bit error rate (BERSD-P) alarm. Select one of the following values: 1E-4: Value equals 1 x 10-4 1E-5: Value equals 1 x 10-5 1E-6 (default for VC-3 SD BER): Value equals 1 x 10-6 1E-7 (default for VC-4 and VC-4-4c SD BER): Value equals 1 x 10-7 1E-8 (default for VC-4-16c SD BER): Value equals 1 x 10-8 1E-9: Value equals 1 x 10-9 FEC (STM-64 only): Forward error correction. Improves the link budget of this signal approximately 3 db. The resulting signal is no longer SONET/SDH compliant. Both ends of this link must have the same value in this parameter or the link will fail. Enabled: Select to activate the FEC feature Disabled (default) Page 5-40 Turin Networks Release TN4.0.x

Chapter 3 SDH Equipment STM Port Parameters STM Port Parameters On a Traverse node from Shelf View, click a SDH port and click the Config tab. The SDH Port Configuration screen displays. Figure 5-21 SDH Port Configuration Screen The SDH Port Configuration screen allows you to view and set the following configuration information: Label: Displays the node name. Type: Displays the port type (STM1, STM4, STM16, or STM64). Slot Number: Displays the slot number of the card where the SDH port is located. Port Number: Displays the port number of the SDH port. Line Format: Displays SDH. AIS Mask (Alarm Indication Signal Mask): Yes: Mask AIS/alarm for unused direction No (default): Do not mask AIS/alarm for any direction Sync Source: Displays the timing source priority for this port. For details on selecting this port as a timing source, see Chapter 2 Timing, Line Timing, page 3-23. Displays one of the following: Not used (default): This port has not been set as a timing source. Primary: This port has been set as the primary timing source. Secondary: This port has been set as the secondary timing source. Third: This port has been set as the third timing source. Fourth: This port has been set as the fourth timing source. Note: Timing is restricted to a single port at any time for OC3 or STM1 cards. Release TN4.0.x Turin Networks Page 5-41

TransNav GUI Guide, Section 5: Equipment STM Port Parameters SF BER: Measures the transmission quality (bit error ratio) of failed signals on the link. When the error rate crosses the value specified in this parameter, the system raises a signal failed bit error rate (BERSF-L) alarm and performs a protection switch. Select one of the following values: 1E-3 (default): Value equals 1 x 10-3 1E-4: Value equals 1 x 10-4 1E-5: Value equals 1 x 10-5 Transmitter State (Does not apply to STM-1ESTM-1E): Select one of the following: On (default): Transmit laser is turned on. Off: Transmit laser is turned off. Transmitter Auto Shutdown (Does not apply to STM-1E): Automatically shut down the transmit laser on optical interfaces when the system detects a receive LOS for 500 ms. The system turns the transmit laser off after detecting a receive LOS for 800 ms. The system raises the ALS alarm against the optical facility when the transmitter has been turned off automatically. Disabled (default): The ALS feature is turned off. Manual: The operator initiates a single laser pulse from the transmitter for the amount of time specified in the Recovery Pulse Width parameter. To send the single laser pulse, click the Current Transmitter State button, then click Manual Restart. Automatic: The system turns off the transmit laser for a random time between 100 and 300 seconds. The transmit laser turns on if one of the following conditions occur: The user manually sends a single laser pulse (Current Transmitter State button) If the system receives a valid signal for more than 800 ms After the random timer expires, the system sends periodic laser pulses from the transmitter for the amount of time specified in the Recovery Pulse Width parameter Recovery Pulse Width (Does not apply to STM-1E): The system enables the transmitter for the amount of time specified in this parameter. Valid only if the value in Transmitter Auto Shutdown is Manual or Automatic. Enter a time between 2 and 10 seconds; the default is 5 seconds. Input Sync Msgs: Displays the receiving synchronization status messages (SSM) value for this port. Possible values are: Stratum 1: Stratum 1 Traceable Synch-Trace Unknown: Synchronized - Traceability Unknown Stratum 2: Stratum 2 Traceable Transit Node: Transit Node Clock Traceable Stratum 3E: Stratum 3E Traceable Stratum 3: Stratum 3 Traceable SONET/SDH Minimum Clock: SONET Minimum Clock Traceable (20 ppm clock) Stratum 4/4e: Stratum 4/4E Traceable Page 5-42 Turin Networks Release TN4.0.x

Chapter 3 SDH Equipment STM Port Parameters Don t use for synch: Don t use for synchronization User s Provisionable: Provisionable by network operator Idle pattern: An idle pattern is being transmitted/received Output Sync Msgs: Displays the transmitting SSM (synchronization status messages) value for this port. Possible values are: Stratum 1: Stratum 1 Traceable Synch-Trace Unknown: Synchronized - Traceability Unknown Stratum 2: Stratum 2 Traceable Transit Node: Transit Node Clock Traceable Stratum 3E: Stratum 3E Traceable Stratum 3: Stratum 3 Traceable SONET/SDH Minimum Clock: SONET Minimum Clock Traceable (20 ppm clock) Stratum 4/4e: Stratum 4/4E Traceable Don t use for synch: Don t use for synchronization User s Provisionable: Provisionable by network operator Idle pattern: An idle pattern is being transmitted/received 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. SD BER: Measures the transmission quality (bit error ratio) of degraded signals on the optical link. When the error rate crosses the value specified in this parameter, the system raises a signal degraded bit error rate (BERSD-L) alarm and performs a protection switch. Select one of the following values: 1E-9: Value equals 1 x 10-9 1E-8: Value equals 1 x 10-8 1E-7: Value equals 1 x 10-7 1E-6 (default): Value equals 1 x 10-6 1E-5: Value equals 1 x 10-5 Current Transmitter State (Does not apply to STM-1E): Click this button to display the current state of the optical transmitter. See the Transmitter Auto Shutdown parameter for details. Fwd Section Trc Fmt (Forward Section Trace Format): This port transmits an access point identifier in the J0 byte of the SDH frame so that the section receiver can verify its continued connection. 16 bytes (default): Select this value if the receiver is another SDH port. 64 bytes: Select this value if the receiver is a SONET port. Fwd Section Trace: The access point identifier transmitted in the J0 byte. Enter an alphanumeric character string. SS Bit Transmit: Select the SS bit value that this interface is transmitting: 00: This interface is transmitting SONET frames. 10 (default): This interface is transmitting STM frames. Release TN4.0.x Turin Networks Page 5-43

TransNav GUI Guide, Section 5: Equipment STM Port Parameters Rev Section Trc Fmt (Reverse Section Trace Format): This port expects an access point identifier in the J0 byte of the SDH frame to verify its continued connection with the transmitter. If this port receives an incorrect identifier, the system raises an RS-TIM (Regenerator Section - Trace Identifier Mismatch alarm). 16 bytes (default): Select this value if the transmitter is another SDH port. 64 bytes: Select this value if the transmitter is a SONET port. Rev Section Trace: The expected access point identifier to be received in the J0 byte. Enter an alphanumeric character string. SS Bit Receive: Indicates the SS bit value that this interface is receiving. Current Received Section Trace: Indicates the section trace currently being received. Customer: Select from the list of defined customer profiles. Default is No Customer Selected. For details on creating customer profiles, see Adding Customer Information, page 2-31. PM Template: Select from the list of defined performance monitoring templates. Default is default, which contains default thresholds for performance monitoring parameters. The system default for performance monitoring thresholds is disabled for all parameters. Use the performance monitoring templates to set default thresholds or to customize threshold values. See Section 8 Maintenance and Testing, Chapter 1 Performance Monitoring, page 8-1 for information on how to use performance monitoring templates. See the Node Operations and Maintenance Guide for details on performance monitoring parameters for STM ports. Customer Tag: Enter an alphanumeric character string to identify the port to a customer. Alarm Profile: Select from the list of defined alarm profiles. Default is default (of type sdh_ptp). Control Data (Does not apply to STM-1E): Indicates whether the management system uses the data communications channel (DCC) bytes on this SONET interface to communicate with other nodes. Select one of the following: Enabled (default for OC-12 and OC-48 ports): The management system uses this interface for management traffic. Enabled is not an option for OC-3 ports. Disabled (Read-only for OC-3 ports): The management system does not use this interface for management traffic. Note: The data control channel (DCC) is unavailable over an EC-3/STM-1E link. Terminate DCC (Does not apply to STM-1E):This parameter is specific to each STM interface and specifies which DCC bytes to process. You can only change the value in this parameter if the value in Control Data is Disabled. Specify one of the following values: Regenerator: Specifies that the interface use the D1-D3 bytes (192 Kbps) of the first AUG-1 on this interface for management traffic. Page 5-44 Turin Networks Release TN4.0.x

Chapter 3 SDH Equipment STM Port Parameters Multiplexer (default): Specifies that the interface use the D4-D12 bytes (576 Kbps) of the first AUG-1 on this interface for management traffic. Regenerator&Multiplexer: Specifies that the interface use the combined section DCC and line DCC bytes from the first, second, and third AUG-1 on the interface (2.3 Mbps) for management traffic. This selection is available for Traverse to Traverse interworking only. It is unsupported for Traverse to TE-100 interworking. Path (TE-100 OC-3 and OC-12 and Traverse STM-1E interfaces only): Specifies that the interface uses the F2 byte (64 Kbps) of the selected STS for management traffic. Click the Path DCC Configuration button to selected the STS. Path DCC Configuration (TE-100 STM-1 and STM-4 interfaces only. Does not apply to STM-1E): Click this button to configure the STM paths that carries management traffic. L2 Protocol (Does not apply to STM-1E): Determines the Layer 2 (L2) protocol for this port. PPP (default): Point-to-point protocol. Use PPP if this port is connected to another Traverse platform. LAPD: Link access procedure D-channel. Select LAPD if this port is connected to legacy third-party ADM equipment and this node is used as an OSI DCC gateway node. LAPD Role (Does not apply to STM-1E): Select the role of this node in the OSI DCC gateway application: Network User DWDM wl supp value (Does not apply to STM-1E): The DWDM wavelength supplied value. LAPD Mode (Does not apply to STM-1E): Select the mode of this node in the OSI DCC gateway application. AITS: Acknowledge information transfer service. Use this value if the L2 Protocol value is LAPD. UITS (default): Unacknowledge information transfer service. Use this value if the L2 Protocol value is PPP. LAPD MTU (Does not apply to STM-1E): Indicates the maximum transmission unit for this node if the L2 Protocol value is PPP; default is 512. DWDM wl (Does not apply to STM-1E): Select from the list of defined wavelength frequencies. For frequency to wavelength data, see the Traverse Product Overview Guide, Section 3 Card (Module) Descriptions, Chapter 4 SONET/SDH Cards, page 3-25. Command buttons are as follows: Apply: Apply the configuration information to the selected port. If no configuration information has changed since the last time Apply was clicked, the button is grayed out. Cancel: Cancel the configuration information and refresh the screen with the previously configured information. Release TN4.0.x Turin Networks Page 5-45

TransNav GUI Guide, Section 5: Equipment SFP Port Parameters SFP Port Parameters On a Traverse Node in Shelf View click an SFP port, then click the Config tab to display the SFP Port Configuration screen. Figure 5-22 SFP Port Configuration Screen TThe Port Configuration screen displays the following information: Label: Displays the name of the node. Type: Displays the type of port where the transceiver is located. The port can be an SFP (small form pluggable), XFP (10 Gbps small form pluggable), or an optical port. Alarm Profile: Displays the alarm profile (of type shelf) used to monitor this SFP or XFP. The default is the default shelf profile. Slot Number: Displays the slot number on the shelf where the card with the SFP or XFP port exists. Port Number: Displays the port number on the card where the SFP or XFP exists. Identifier: Identifies the transceiver type. For example, Small Form-factor Pluggable Transceiver. Wavelength (nm): Displays the laser wavelength of the transceiver in nanometers. Diag Monitoring Type: Displays the type of diagnostic monitoring that is implemented (if any) in the transceiver. Vendor Name: Displays the name of the hardware vendor. Vendor Rev: Displays the vendor s hardware revision number. Date Code: Displays the date the hardware was manufactured. SFP Refresh (SFP Transceiver only): Select this button to refresh information for the SFP transceiver information a few minutes after the card is rebooted. XFP Refresh (XFP Transceiver only): Select this button to refresh the information for the XFP transceiver a few minutes after the card is rebooted. BR,Nominal (100MBs): Displays the nominal bit rate in increments of 100 Mbps. Vendor PN: Displays the part number of the vendor of the hardware. Vendor SN: Displays the serial number of the vendor of the hardware. Page 5-46 Turin Networks Release TN4.0.x

Chapter 3 SDH Equipment SFP Port Parameters Diagnostic Parameters: Click this button to display diagnostic information on the SFP or XFP hardware. Figure 5-23 Diagnostic Parameters Dialog Box The Diagnostic Parameters dialog box displays the following information: Measured Temperature: Indicates the current temperature of the transceiver. Measured in degrees Celsius ( C). Displays -128 to + 128 ± < 3 C. Measured Supply Voltage: Indicates the current voltage the hardware is using. Measured in 100µ volts (micro volts). Displays 0 to 6.55 ± < 3%. Measured TX Bias Current: Displays 0 to 131 ma ± <10%. Measured in 2µA. Measured TX Output Power: Displays 0 to 6.55 mw (-40 to +8.2 dbm ± <3dB) in units of 0.1µW. This value should be consistent among ports of the same transceiver type. Measured in 10 log [(read value x 10-6)/(10-3)] dbm. Measured RX Input Power: Displays 0 to 6.55 mw (-40 to +8.2 dbm ± <3dB) in units of 0.1µW. This value will vary from port to port because of received optical signal power differences. Measured in 10 log [(read value x 10-6)/(10-3)] dbm. Command buttons are as follows: Refresh: Renew the data in the display. Done: Close the dialog box and return to the main configuration screen. Release TN4.0.x Turin Networks Page 5-47

TransNav GUI Guide, Section 5: Equipment SFP Port Parameters Page 5-48 Turin Networks Release TN4.0.x

SECTION 5EQUIPMENT Chapter 4 Ethernet Equipment Introduction Ethernet Equipment This chapter contains the following topics: Ethernet Equipment, page 5-49 Ethernet Card Parameters, page 5-50 MAC Address Table, page 5-52 Ethernet Port Parameters, page 5-53 Ethernet Port Advanced Parameters, page 5-58 EOS Port Parameters, page 5-63 EOS Port Advanced Parameters, page 5-64 Ethernet or EOS Port Queues, page 5-66 EOS Port Status, page 5-69 Link Aggregation Group, page 5-71 LAG Advanced Parameters, page 5-72 Important: The information in this section strictly pertains to the following Traverse Next Generation Ethernet (NGE), Next Generation Ethernet Plus (NGE Plus), 10GbE (1-port 10GbE), and GbE-10 (10-port GbE) modules: NGE Modules NGE Plus Modules GE Modules GBE4-FE16-TX GBE4-FE16-TX / CEP 10GbE (1-port 10GbE) GbE-10 (10-port GbE) GBE2T-GBE2F-FE16-TX GBE2T-GBE2F-FE16-TX / CEP This information also pertains to the Ethernet parameters on the TE-100 shelf. For information about pre-release TR2.1 Legacy Ethernet modules, refer to the Release 2.0 documentation on the Turin website at www.turinnetworks.com. User registration is required. To register for the Turin Infocenter, contact your sales account team. Release TN4.0.x Turin Networks Page 5-49

TransNav GUI Guide, Section 5: Equipment Ethernet Card Parameters Ethernet Card Parameters In a Traverse node Shelf View, click an Ethernet card, then click the Config tab. If this card is in a 1:1 equipment protection group, click the working card. Note: All ports on the 10GbE and GbE-10 cards are optical ports. In a TE-100 Shelf View, click the interface card, then click the Config tab. Figure 5-24 Ethernet Card, Configuration Tab MAC Address Aging (sec): The time (in seconds) after which the system removes a learned entry from the MAC forwarding database. The range is from 10 to 1,000,000 seconds; default is 300 seconds. MAC Address table: For Ethernet bridge and aggregation bridge services, this table allows a user to view and edit the learned MAC addresses for this card. See MAC Address Table, page 5-52. Standard (Traverse only): Select the technology standard for the EOS ports on this card: ANSI: For North American operations ITU: For operations outside of North America LO Mapping (NGE and NGE Plus cards only): Select a default LO mapping for the EOS port members for this NGE card when the value in the Standard parameter is ITU. Select one of the following values: VT15/VC11 (Traverse only): Select to multiplex the data into a VC11. If the value in the Standard parameter is ANSI, the only LO mapping for EOS ports is VT1.5. VC12 (default): Select to multiplex the data into VC12. Configure the LCAS timers for EOS ports on this card. When LCAS detects an Active EOS port member has failed, it waits for the period defined by the hold-off timer parameters before removing the sink member from the active group. LCAS LO Holdoff (100 ms) (NGE and NGE Plus cards only): The time, in milliseconds, LCAS waits before removing a member from the LO VCAT groups on the card. Enter a value between 0 to 10 seconds, in increments of 100 milliseconds. The default is 1, indicating 100 milliseconds. Page 5-50 Turin Networks Release TN4.0.x

Chapter 4 Ethernet Equipment Ethernet Card Parameters Configure the LCAS wait-to-restore times for the EOS ports on this card (Traverse only). When LCAS detects a member has recovered from a failure, it waits for the period defined by the Wait-to-Restore (WTR) timer before including the sink member in the active group. LCAS LO WTR (min) (NGE and NGE Plus cards only): The time, in minutes, before the system restores members of the LO VCAT group. Enter a value between 1 to 60 minutes, in increments of 1 minute; default is 5 minutes. LCAS HO WTR (min): The time, in minutes, before the system restores members of the HO VCAT group. Enter a value between 1 to 60 minutes, in increments of 1 minute; default is 5 minutes. Insert Alternate VLAN Ethertype: Select to indicate the Alternate VLAN Ethertype should be used for outgoing packets with VLAN tags for a specific port. Enable this parameter if one or more ports are connected to devices that require this alternate value. In addition, enable the Insert Alternate VLAN Ethertype parameter on those ports. On NGE and NGE Plus cards, the alternate value is used in all VLAN tags in a packet. On 10GbE or GbE-10 cards, the system distinguishes between inner (customer) and outer (service) tags. Inner tags must have 0x8100 Ethertype; outer tags must match the setting of this parameter. For example, if 0x9100 is selected then only service tags with 0x9100 will be recognized. If only one tag exists, the outer tag and the statements made for service tags apply. 8100 (default): The system uses this standard Ethertype value. 9100: The system also accepts packets with the Ethertype value of 9100 in the VLAN tag. FE Insert Alternate VLAN Ethertype and FE EOS Insert Alternate VLAN Ethertype (TE-100 only): If the Alternative VLAN Ethertype parameter is configured for this card, the system also accepts packets with the Ethertype value of 9100 in the VLAN tag. Enable this parameter if one or more ports on this card are connected to devices that require this alternative value. Egress Priority CoS{1 2 3}: Whenever the TE-100 system creates a new VLAN tag (either a Customer tag or a Service tag) for an Ethernet packet, it inserts a value into the Priority field of the new VLAN tag. The Priority value inserted in the new tag is called the Egress Priority and is derived from the internal CoS that the TE-100 assigned to the packet when it arrived. Instruct the TE-100 to use a specific Egress Priority (a number between 0 and 7) for each value of internal CoS (a value from 1 to 3) by provisioning the three Egress Priority parameters. Egress Priority CoS1 for class of service 1 Egress Priority CoS2 for class of service 2 Egress Priority CoS3 for class of service 3 By default, all three parameters are 0 which means that an Egress Priority of 0 will be inserted into every added tag, regardless of the internal CoS. By industry convention, Priority 0 is highest priority and Priority 7 is lowest priority. To override the default for any CoS (i.e., packets classified into CoS 1 have a non-zero Egress Priority), provision the appropriate Egress Priority parameter to the desired Egress Priority value for that class of service. Command buttons are as follows: Release TN4.0.x Turin Networks Page 5-51

TransNav GUI Guide, Section 5: Equipment MAC Address Table Switch to SDH (Traverse only): Switch the mode of the card to SDH. Change the mode when the EOS ports need to contain STM paths. Switch to SONET (Traverse only): Switch the mode of the card to SONET. Change the mode when the EOS ports need to contain STS paths. Apply: Click to apply changed settings. Cancel: Click to cancel any changes and reset the parameters to the configured state. MAC Address Table The MAC Address Queries dialog box allows a user to query all MAC addresses in the system. In a Traverse node Shelf View, click an Ethernet card (with bridge services configured), then click the Config tab. Click MAC Address table to display the MAC Address Queries dialog box. Figure 5-25 MAC Address Queries Dialog Box Filter MAC addresses using all or any of the following options: MAC Address: All (default) Define: Enter a specific MAC address. Service: Select a service identification number (SID). The values are: All (default): Queries all services. Define: Enter a specific SID. Port ID: Select the port number from the drop-down menu; default is All. Available when the Port Type field value is EOS, ETH, GBE, or LAG. Slot ID: Indicates the slot number of the selected card for this MAC address query. Port Type: Select one of the following values to filter the list based on the type of port: None (default) EOS: EOS ports ETH: ETH100TX interfaces GBE: GbE ports Page 5-52 Turin Networks Release TN4.0.x

Chapter 4 Ethernet Equipment Ethernet Port Parameters LAG (Traverse only): Link aggregation group ports Command buttons are as follows: Count: Click to count all the MAC addresses learned on this card. Delete All: Removes all MAC addresses recorded in the forwarding table. Query: Query on the MAC addresses in any of the filters. Delete: Delete MAC Addresses highlighted in the MAC Address list. Close: Close the dialog box and return to the main screen. Ethernet Port Parameters In Shelf View, click an Ethernet port. For Traverse nodes, if the card is in a 1:1 equipment protection group, click the port on the working card. Click the Config tab to display the Ethernet Port Configuration screen. Figure 5-26 Ethernet Port Configuration Screen Manual Duplex: See Ethernet Port Advanced Parameters, page 5-58. Auto-negotiation (All TE-100 ports and Traverse cards except 10GbE): Specifies if the Auto-negotiation feature is enabled. Important: By default, the Auto-negotiation feature is always enabled. However, the Traverse system allows the operator to disable auto-negotiation for both ETH100TX and optical GbE ports but always performs auto-negotiation on copper GbE ports. Turin recommends that if the peer device is IEEE 802.3 compliant, the operator leave the Auto-negotiation feature enabled. Select one of the following values: On (default for all port types except 10GbE): Negotiate the speed, pause frame, and duplex attributes of the link based on the values in the Advanced parameters (as applicable to the port type). See Ethernet Port Advanced Parameters, page 5-58 for explanations of these parameters. Release TN4.0.x Turin Networks Page 5-53

TransNav GUI Guide, Section 5: Equipment Ethernet Port Parameters Off (Available for ETH100TX and optical GBE ports; always OFF for 10GbE cards): The link starts up and initializes with the values in the Manual Speed, Manual Duplex, and Manual PAUSE fields (as applicable to the port type). See Ethernet Port Advanced Parameters, page 5-58 for explanations of these parameters. Transmitter State (GBE, 10GbE, and GbE-10 only): Determines if the laser on a GBE or 10GBE optical port is turned on or off. On (default): The laser is on. Off: The laser is off. Transmitter Auto Shutdown (Traverse, GBE, 10GbE, and GbE-10 optical ports): Automatically shut down the transmit laser on optical interfaces when the system detects a receive LOS for 500 ms. The system turns the transmit laser off after detecting a receive LOS for 800 ms based on ITU-T standard G.664. The system raises the ALS (automatic laser shutdown) alarm against the optical facility when the transmitter has been turned off automatically. Disabled (default): The ALS feature is turned off. Manual: The operator initiates a single laser pulse from the transmitter for the amount of time specified in the Recovery Pulse Width parameter. To send the single laser pulse, click Current Transmitter State, then click Manual Restart. Automatic: The system turns off the transmit laser for a random time between 100 and 300 seconds. The transmit laser turns on if one of the following conditions occur: The user manually sends a single laser pulse (click Current Transmitter State). If the system receives a valid signal for more than 800 ms. After the random timer expires, the system sends periodic laser pulses from the transmitter for the amount of time specified in the Recovery Pulse Width parameter. Recovery Pulse Width (sec) (Traverse, GBE only): The system enables the transmitter for the amount of time, in seconds, specified in this parameter. Valid only if the value in the Transmitter Auto Shutdown parameter is Manual or Automatic. Enter a time between 2 and 10 seconds; default is 5 seconds. Customer: Select from the list of defined customers. PM Template: Select from the list of defined performance monitoring templates (of type ethernet_ptp_pm). Default value is default, which contains default thresholds for performance monitoring parameters and thresholds for Ethernet ports. Manual Speed: See Ethernet Port Advanced Parameters, page 5-58. MAC Address: For Ethernet bridge and aggregation bridge services, this table allows a user to view and edit the learned MAC addresses for this card. Jumbo Frame Support (Traverse, GBE, 10GbE, and GbE-10 only): 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. Page 5-54 Turin Networks Release TN4.0.x

Chapter 4 Ethernet Equipment Ethernet Port Parameters Jumbo Frame Size (bytes) (Traverse only): Enter the jumbo frame size (available only when Jumbo Frame Support is Enabled). Range is 1522 to 9600 bytes; default is 9600 bytes. Current Transmitter State (Traverse, GBE, 10GbE, and GbE-10): Click to display the current state of the optical transmitter. See the Transmitter Auto Shutdown parameter for details. Tagging (TE-100, Ethernet port parameters, and Ethernet port advanced parameters only): Specify the expected type of VLAN tagging on this Ethernet port or EOS port. Valid values are: Port-based: Every packet on this port is considered to belong to the same service, regardless of whether or not the packet has a customer VLAN tag. Customer VLAN tags are not significant for service definition. Customer-tagged: Every packet on this port is assumed to have a VLAN tag that identifies its service in the customer network. Termed the customer VLAN tag, Traverse NGE cards collect this service information on a per-vlan basis. Untagged: Every packet on this port is considered to belong to the same service and no packet has a VLAN tag. Service-tagged: Every packet on this port is assumed to have a service provider VLAN ID that identifies its Ethernet service within the service provider network. Service provider VLAN tags are used within the service provider network and are never used on customer-facing ports. Traverse NGE cards collect this service information on a per-vlan basis. Customer Tag: Enter an alphanumeric character string to identify the port to a customer. Alarm Profile: Select from the list of defined alarm profiles (of type ethernet_ptp) to customize service-affecting and non-service-affecting alarm severities. Default is the default ethernet_ptp alarm profile. Command buttons are as follows: Advanced: Click to set advanced port parameters. See Ethernet Port Advanced Parameters, page 5-58. Status: Click to view port status. Queue (Traverse only): Click to view queue status. Renegotiate (NGE, NGE Plus, 10GbE, and GbE-10 cards only): Click to restart Auto-negotiation. Apply: Click to change the settings. Cancel: Click to cancel any changes and reset the parameters to the configured state. Refresh: Click to refresh any displayed queried data. Release TN4.0.x Turin Networks Page 5-55

TransNav GUI Guide, Section 5: Equipment SFP / XFP Port Parameters SFP / XFP Port Parameters On a Turin node in Shelf View, click a SFP (small form pluggable transceiver), XFP (10Gbps small form pluggable transceiver), or an optical port, then click the Config tab to display the Ethernet Port Configuration screen. If a pluggable transceiver is in use on a card, the SFP or XFP information displays. Important: Only use SFPs or XFPs approved by Turin or equipment damage may occur, thus voiding any warranty. Figure 5-27 Pluggable Transceiver Fields on Port Configuration Screen The Port Configuration screen displays the following information: Label: Displays the name of the node. Type: Displays the type of port where the transceiver is located. The port can be an SFP (small form pluggable), XFP (10 Gbps small form pluggable), or an optical port. Alarm Profile: Displays the alarm profile (of type shelf) used to monitor this SFP or XFP. The default is the default shelf profile. Slot Number: Displays the slot number on the shelf where the card with the SFP or XFP port exists. Port Number: Displays the port number on the card where the SFP or XFP exists. Identifier: Identifies the transceiver type. For example, Small Form-factor Pluggable Transceiver. Wavelength (nm): Displays the laser wavelength of the transceiver in nanometers. Diag Monitoring Type: Displays the type of diagnostic monitoring that is implemented (if any) in the transceiver. Vendor Name: Displays the name of the hardware vendor. Vendor Rev: Displays the vendor s hardware revision number. Date Code: Displays the date the hardware was manufactured. SFP Refresh (SFP Transceiver only): Select this button to refresh information for the SFP transceiver information a few minutes after the card is rebooted. XFP Refresh (XFP Transceiver only): Select this button to refresh the information for the XFP transceiver a few minutes after the card is rebooted. BR,Nominal (100MBs): Displays the nominal bit rate in increments of 100 Mbps. Vendor PN: Displays the part number of the vendor of the hardware. Page 5-56 Turin Networks Release TN4.0.x

Chapter 4 Ethernet Equipment SFP / XFP Port Parameters Vendor SN: Displays the serial number of the vendor of the hardware. Diagnostic Parameters: Click this button to display diagnostic information on the SFP or XFP hardware. Figure 5-28 Diagnostic Parameters Dialog Box The Diagnostic Parameters dialog box displays the following information: Measured Temperature: Indicates the current temperature of the transceiver. Measured in degrees Celsius ( C). Displays -128 to + 128 ± < 3 C. Measured Supply Voltage: Indicates the current voltage the hardware is using. Measured in 100µ volts (micro volts). Displays 0 to 6.55 ± < 3%. Measured TX Bias Current: Displays 0 to 131 ma ± <10%. Measured in 2µA. Measured TX Output Power: Displays 0 to 6.55 mw (-40 to +8.2 dbm ± <3dB) in units of 0.1µW. This value should be consistent among ports of the same transceiver type. Measured in 10 log [(read value x 10-6)/(10-3)] dbm. Measured RX Input Power: Displays 0 to 6.55 mw (-40 to +8.2 dbm ± <3dB) in units of 0.1µW. This value will vary from port to port because of received optical signal power differences. Measured in 10 log [(read value x 10-6)/(10-3)] dbm. Command buttons are as follows: Refresh: Renew the data in the display. Done: Close the dialog box and return to the main configuration screen. Release TN4.0.x Turin Networks Page 5-57

TransNav GUI Guide, Section 5: Equipment Ethernet Port Advanced Parameters Ethernet Port Advanced Parameters The parameters in this topic apply to the following Ethernet ports on NGE, NGE Plus, 10GbE, and GbE-10 cards only, unless otherwise noted: GBE, GBETX, ETH100TX, link aggregation groups (LAG), and Ethernet over SONET/SDH (EOS) ports. Figure 5-29 Traverse GBE Advanced Parameters Max Info Rate (Mbps) (TE-100, NGE, and NGE Plus only): Specify the maximum ingress data rate (in Mbps) allowed for this port. If the PAUSE feature is enabled for this port, the system sends a PAUSE frame when the ingress rate hits the rate specified in this parameter. The link partner should limit its rate of transmission to the value specified in this parameter. If the PAUSE feature is disabled for this port, or if the link partner does not respond properly to the PAUSE frame, then the link partner s transmission may exceed MIR. The incoming packets above this rate are discarded. ETH100TX ports: Enter an integer between 1 and 100; default is 100. GBE, GBETX, LAG, EOS ports: Enter an integer between 1 and 1000; default is 1000. Page 5-58 Turin Networks Release TN4.0.x

Chapter 4 Ethernet Equipment Ethernet Port Advanced Parameters MIR Burst Size (Kbytes) (TE-100, NGE, and NGE Plus only): Enter a value between of 2 and 1000 which are provisionable in increments of 1 KB; default is 64 KB. Use this parameter in conjunction with Max Info Rate (Mbps) to operate as a single token bucket that meters incoming traffic. The response of the system to incoming traffic depends on whether PAUSE is enabled on the Ethernet port. If PAUSE is enabled on the Ethernet port, then the system controls the flow by sending a PAUSE frame when the ingress traffic approaches MIR. If the peer responds correctly to the PAUSE frame, then this mechanism is lossless from a TE-100 s point of view. The system drops traffic if PAUSE is disabled on the Ethernet port or the peer does not correctly respond to the PAUSE frame. The system drops all traffic that does not conform to the token bucket traffic that arrives in excess of MIR / MBS. Default Ingress Priority (TE-100 only): Used in the classification of packets for packets that arrive untagged and therefore do not have a priority field. Set the default priority for untagged packets arriving on this port. Enter a value from 0 to 7; the default is 0. Auto-negotiation: If Auto-negotiation (port configuration) is turned ON for this port (Config tab), ETH100TX ports can advertise one or more of the following parameters: Advertise 10M Half Duplex: Enabled (default) or Disabled. Advertise half duplex and 10 Mbps speed when Auto-negotiation is turned ON. Advertise 10M Full Duplex: Enabled (default) or Disabled. Advertise full duplex and 10 Mbps speed when Auto-negotiation is turned ON. Advertise 100M Half Duplex: Enabled (default) or Disabled. Advertise half duplex and 100 Mbps speed when Auto-negotiation is turned ON. Advertise 100M Full Duplex: Enabled (default) or Disabled. Advertise full duplex and 100 Mbps speed when Auto-negotiation is turned ON. Advertise PAUSE: Enabled (default) or Disabled. Advertise that the Traverse will transmit a PAUSE frame when it detects congestion on upstream or if the traffic on this port is bursting over the value specified in the Max Info Rate (MBPS) parameter. If Auto-negotiation is turned on for this port, GBE ports can advertise one or more of the following parameters: Advertise 1000M Full Duplex: Advertise full duplex and 1000 Mbps (1 Gbps) speed. Enabled (default) or Disabled. Advertise 1000M Half Duplex (TE-100 only): Advertise half duplex and 1000 Mbps (1 Gbps) speed. Enabled or Disabled. Advertise PAUSE RX: Enabled (default) or Disabled. The Traverse commits to stop transmitting on the link when it receives a PAUSE frame from the link partner. Read-only for optical GBE ports when Auto-negotiation is turned ON. Configurable when Auto-negotiation is turned OFF. Advertise PAUSE TX: Enabled (default) or Disabled. The Traverse will send a PAUSE frame to the link partner in times of upstream congestion or if it detects this port is receiving traffic over the value specified in the Max Info Rate (MBPS) parameter. Release TN4.0.x Turin Networks Page 5-59

TransNav GUI Guide, Section 5: Equipment Ethernet Port Advanced Parameters If Auto-negotiation is turned on for this port, GBETX ports can advertise one or more of the following parameters: Advertise 1000M Half Duplex: Enabled (default) or Disabled. Advertise half duplex and 1000 Mbps (1 Gbps) speed. Advertise 1000M Full Duplex: Enabled (default) or Disabled. Advertise full duplex and 1000 Mbps (1 Gbps) speed. Advertise GBE RX PAUSE: Enabled or Disabled (default). The Traverse commits to stop transmitting on the link when it receives a PAUSE frame from the link partner. Advertise GBE TX PAUSE: Enabled (default) or Disabled. The Traverse will send a PAUSE frame to the link partner in times of upstream congestion or if it detects that this port is receiving traffic over the value specified in the Max Info Rate (MBPS) parameter. If Auto-negotiation is turned OFF for this ETH100TX port, set the following parameters: Manual Duplex (Config tab): Indicates the mode of operation for this port based on IEEE standard 802.3. Full (default): The port operates in full duplex mode and allows simultaneous transmissions on the link. Half: The port operates in half-duplex mode and uses CSMA/CD to share access to the link. Manual Speed: Configure the data rate of the link: 10 Mbps 100 Mbps (default for ETH100TX) Manual Pause: Configure if the system will send a PAUSE frame to the link partner in times of upstream congestion or if the traffic on this port is bursting over the value specified in the Max Info Rate (MBPS) parameter. Manual Crossover (Config tab): Controls the MDI/MDIX configuration of this port. Enabled: Select to reverse the transmit and receive on this port. Turns a straight-through cable into a crossover cable. Disabled (default) When Auto-negotiation is turned OFF for this optical GBE port, set the following parameters. Auto-negotiation is always off for 10GbE cards. Manual Duplex: Indicates the mode of operation for this port based on IEEE standard 802.3. Full (default): The port operates in full duplex mode and allows simultaneous transmissions on the link. 10GbE and GbE-10 ports always operate in Full Duplex mode. Half: The port operates in half-duplex mode and uses CSMA/CD to share access to the link. Manual Speed (Read-only): 1 Gbps (default). GbE-10 ports always operate at 10 Gbps. Page 5-60 Turin Networks Release TN4.0.x

Chapter 4 Ethernet Equipment Ethernet Port Advanced Parameters Manual Pause: Enabled: The system sends a PAUSE frame and commit to stopping traffic if it receives a PAUSE frame. Disabled: The system does not send or receive PAUSE frames. TX Only: The system sends a PAUSE frame to the link partner in times of upstream congestion or if the Traverse detects this port is receiving traffic over the value specified in the Max Info Rate (MBPS) parameter. RX only: The Traverse commits to stop transmitting on the link when it receives a PAUSE frame from the link partner. Insert Alternate VLAN Ethertype (all Ethernet ports on Traverse and TE-100 GBE only): Select this parameter to indicate the Alternate VLAN Ethertype should be used for outgoing packets with VLAN tags for a specific port. Enable this parameter if one or more ports are connected to devices that require this alternate value. On NGE and NGE Plus cards, the alternate value is used in all VLAN tags in a packet. For 10GE cards, the alternate value is only used for the outer VLAN tag in a packet. Tagging (Traverse only): Specify the expected type of VLAN tagging on this Ethernet port, LAG, or EOS port. Port-based (default): Every packet on this port is considered to belong to the same service, regardless of whether or not the packet has a customer VLAN tag. Customer VLAN tags are not significant for service definition. Customer-tagged: Every packet on this port is assumed to have a VLAN tag that identifies its service in the customer network. This is termed the customer VLAN tag and is significant for Traverse Ethernet service definition. Customer-tagged ports use the customer VLAN tag, meaning the service provider can have multiple Ethernet streams sharing the same port identified by a separate customer VLAN ID. Service-tagged: Every packet on this port is assumed to have a service provider VLAN ID that identifies its Ethernet service within the service provider network. Service provider VLAN tags are used within the service provider network and are never used on customer-facing ports. The service provider VLAN tag optionally carries packet class of service and drop precedence information used within the service provider network and not conveyed to the end customer. Queuing Policy: Specify how the queues are managed for this port. Select one of the following values: FIFO (default): First-in-first-out. Select this queuing policy to schedule all packets for transmission based on the FIFO algorithm. All traffic uses CoS1. Optionally, configure whether shaping should be employed using the FIFO Shaping Enable and the FIFO Shape Rate parameters. Priority: Select this queuing policy to schedule all packets for transmission based on strict priority, using three classes of service. There are three priorities: Highest priority traffic uses CoS1; medium priority traffic uses CoS2; low priority traffic uses CoS3. Release TN4.0.x Turin Networks Page 5-61

TransNav GUI Guide, Section 5: Equipment Ethernet Port Advanced Parameters WFQ: Weighted fair queuing. Select this queuing policy to guarantee a specific amount of the port s bandwidth when there is congestion on the port. WFQ uses four classes of service and the guarantees are specified as weights. If the value in this parameter is WFQ, specify the weights in the four WFQ CoS weight {1 2 3 4} parameters. If FIFO is the value in the Queuing Priority parameter, configure the following parameters: FIFO Shape Enable: If FIFO is the value in the Queuing Priority parameter, specify if the system will use the number in the FIFO Shaping Rate parameter to shape the traffic being transmitted onto the port. FIFO Shaping Rate: If the FIFO Shaping Rate is enabled, specify a number between 1 and 1000 Mbps. If WFQ is the value in the Queuing Priority parameter, configure the following parameters: WFQ CoS 1 Weight: Weighted queuing policy of CoS1. Enter a number between 1 and 100 to determine the proportion of bandwidth on this port for CoS1. The default value is 1 which means packets with the CoS1 have no priority in relation to the other classes of service. WFQ CoS 2 Weight: Weighted queuing policy of CoS2. Enter a number between 1 and 100 to determine the proportion of bandwidth on this port for CoS2. The default value is 1 which means packets with the CoS2 have no priority in relation to the other classes of service. WFQ CoS 3 Weight: Weighted queuing policy of CoS3. Enter a number between 1 and 100 to determine the proportion of bandwidth on this port for CoS3. The default value is 1 which means packets with the CoS3 have no priority in relation to the other classes of service. WFQ CoS 4 Weight (Traverse only): Weighted queuing policy of CoS4. Enter a number between 1 and 100 to determine the proportion of bandwidth on this port for CoS4. The default value is 1 which means packets with the CoS4 have no priority in relation to the other classes of service. Custom RED {CoS1 CoS2 CoS3 CoS4} (Traverse only): Select to configure the following RED thresholds for CoS1 (queue 1): RED {CoS1 CoS2 CoS3 CoS4} Yellow Min (KB): Enter a number between 0 KB and 8,000 KB, in increments of 1 KB. RED {CoS1 CoS2 CoS3 CoS4} Yellow Max (KB): Enter a number between 0 KB and 8,000 KB, in increments of 1 KB. RED {CoS1 CoS2 CoS3 CoS4} Green Min (KB): Enter a number between 0 KB and 8,000 KB, in increments of 1 KB. RED {CoS1 CoS2 CoS3 CoS4} Green Max (KB): Enter a number between 0 KB and 8,000 KB, in increments of 1 KB. Page 5-62 Turin Networks Release TN4.0.x

Chapter 4 Ethernet Equipment EOS Port Parameters EOS Port Parameters An EOS port is a port-like abstraction representing the adaptation point between Ethernet and SONET/SDH. In a Traverse node Shelf View, click the Ethernet tab, then click the EOS subtab. Figure 5-30 Ethernet Tab, EOS Subtab Click Add to add an EOS port. The Create EOS screen displays. Configure the parameters for the EOS port. Figure 5-31 Create EOS Tab The Create EOS tab allows the user to configure the following parameters: Slot: Select the correct slot number from the drop-down menu. EOS Port ID: Identifies this EOS port in the system. On a Traverse system, for an NGE card enter a number between 1 and 64 to identify this EOS port in the system. For 10GbE and GbE-10 cards, enter a number between 1 and 128. On a TE-100 system, enter a number between 1 and 6 for a 100 Mbps port. Enter either 7 or 8 for a 1000 Mbps port. Note: The maximum number of physical ports on an NGE card is 20; the maximum number of EOS ports is 64. The total maximum port counts for a bridge is 84. On a 10GbE card, the maximum number of physical ports is 1. The maximum number of physical ports on a 10GbE card is 128. the total maximum port counts for a bridge is 129. On a GbE-10 card, the maximum number of physical ports is 10; the maximum number of physical ports is 10. The maximum number of ports for a bridge is 138. All ethernet services must be on the same card. Description: Enter an alphanumeric character string to identify this EOS port in the EOS port list on the EOS subtab. Do not use any other punctuation or special characters. Release TN4.0.x Turin Networks Page 5-63

TransNav GUI Guide, Section 5: Equipment EOS Port Advanced Parameters Customer: Select the name of the customer if this EOS port is for a specific customer. Service Group: Select a service group ID number if this EOS port will use EOS services created from a Service Group. Concatenation Type: Specify if this EOS port uses contiguous concatenation or virtual concatenation. Virtual: This EOS port contains multiple endpoints of the same size creating a virtual concatenation group. Contiguous (default): The EOS port contains a single endpoint. Concatenation Size: Select the bandwidth of the transport paths that are members of this EOS port: VC-11 (Traverse only) VC-12 VC3-HO VC-4 VT1-5 (TE-100, NGE, and NGE Plus only) STS-1 STS-3c The endpoint table has the following columns: Member#: Enter a unique number between 1 and 255 for this member. When LCAS is disabled, the member number order determines the member sequence used by the VCAT group. It must be identical to the order at the remote node EOS port configuration. EndPoint: Select the endpoint for the EOS port member. Direction: Select the direction the traffic travels on the EOS port member. This parameter must match the direction of the EOS port member SONET/SDH service. Receive: Unidirectional in the receive direction only Transmit: Unidirectional in the transmit direction only Bidirectional: The traffic travels in both directions Admin State: Select control the suppression of alarms on the EOS port member. Unlock (default) Locked Alarm Profile: Assign an alarm profile to the EOS port member. Select one of the following values: useparent (default): The member inherits the alarm profile of the EOS port. default: Uses the default alarm profile (of type eos_ctp or sdh_eos_ctp) for the selected endpoint. EOS Port Advanced Parameters See Ethernet Port Advanced Parameters, page 5-58 for parameters common to all Ethernet port types. Page 5-64 Turin Networks Release TN4.0.x

Chapter 4 Ethernet Equipment EOS Port Advanced Parameters Alarm Profile: Assign an alarm profile to this EOS port. By default, the alarm profile is of type eos or sdh_eos. PM Template: Assign a PM template to this EOS port. By default, the PM template is of type eos_pm. GFP FCS Insert: Indicates whether or not the system inserts GFP Payload FCS into each frame sent over this EOS port. Payload FCS should be used only when interoperating with other vendors systems that require it. Normally it is not used on Traverse systems. Enabled: The system adds Payload FCS to each frame. Disabled (default): The system does not add Payload FCS to any frame. LCAS: Enables or disables LCAS operations for this EOS port. Select (default): The system remove any failed members from this service and continue to use this port at a reduced capacity. Clear: LCAS is disabled and the system stops carrying any traffic if a member fails or is removed from the VCG, or if the configured member sequence at the local and remote EOS ports do not match. Apply LCAS WTR (Traverse only): Select: Use the value specified in the LCAS {LO HO} WTR timers configured on the card. Clear (default): Do not use the wait-to-restore value. Apply LCAS Hold Off: Select: Use the value specified in the LCAS {LO HO} Holdoff (100ms) timers configured on the card. Clear (default) RSTP: Enables or disables RSTP for bridge services. Select Enabled to enable RSTP on this EOS port for bridge services. Select Disabled to disable RSTP for bridge services. RSTP Path Cost: Set the path cost of this link. The total cost of a path between any card and the root bridge is the sum of the costs of all the links in the path. Lower values of this parameter mean that this port is more likely to be included in the lowest cost (more desirable) path from this or any other card to the root bridge. Enter an integer between 1 and 16; default is 1. RSTP Port Priority: Used when the spanning tree algorithm has determined that several ports on the card provide paths of equal total cost to the root bridge. The port with the lowest Port Priority is chosen as the Root Port. If several ports have the same lowest Port Priority, then the port with the lowest EOS Port ID is chosen as the Root Port. Enter a number between 1 and 15; default is 8. Virtual RSTP Bridge: Indicates the virtual RSTP bridge for the EOS port if bridge services are configured for this EOS port. Enter a number from 1 through 20; the default is 1. For information on setting up Virtual RSTP, see the Traverse Provisioning Guide, Chapter 7 Rapid Spanning Tree Protocol, Virtual RSTP, page 7-80. PLCT Threshold: Partial Loss of Capacity, Transmit (PLCT) Threshold. Specify the number of provisioned EOS port source (transmit) members that should be active. When fewer than this number of EOS members are active, the system raises a PLCT alarm on the EOS port. Enter a number between 0 and 64 on an NGE card. Enter a Release TN4.0.x Turin Networks Page 5-65

TransNav GUI Guide, Section 5: Equipment Ethernet or EOS Port Queues number between 0 and 192 on a 10GbE and GbE-10 card. The default is 0, which means that the PLCT alarm will not be raised on this EOS port. Used only when the EOS port has LCAS enabled and has at least one provisioned member. Note: Set the threshold value to no more than the total number of EOS port members to prevent generating unnecessary alarms. For example, if the number of members in a particular EOS port is 8, set the threshold values for that EOS port to 8 or less. If a threshold value for that EOS port were set to 9, the condition for a threshold alarm would always be met even when all 8 members were operating correctly, and therefore an alarm would always be present. PLCR Threshold: Partial Loss of Capacity, Receive (PLCR) Threshold. Specify the number of provisioned EOS port source (receive) members that should be active. When fewer than this number are active, the system raises a PLCR alarm on the EOS port. Enter a number between 0 and 64 on an NGE card. Enter a number between 0 and 64 on a 10GbE and GbE-10 card. The default is 0, which means that the PLCT alarm will not be raised on this EOS port. Used only when the EOS port has LCAS enabled, and has at least one provisioned member. Note: Set the threshold value to no more than the total number of EOS port members to prevent generating unnecessary alarms. TE100 LCAS Compat. Mode (Traverse only): Enable (select) this parameter only if this EOS port has LCAS enabled and is connected to a TE-100 product. This parameter removes LCAS transmit members that are using failed paths from the VCG causing a resequencing of the remaining VCG members. The system adds the removed member to the end of the VCG sequence and restores the member when the path clears. Ethernet or EOS Port Queues In a Traverse node Shelf View, click the Ethernet tab, click the EOS subtab, select the correct EOS port, then click Edit. The Edit EOS tab displays. On the Edit EOS tab, click Queues. Figure 5-32 Edit EOS Tab Page 5-66 Turin Networks Release TN4.0.x

Chapter 4 Ethernet Equipment Ethernet or EOS Port Queues The EOS Queue Status dialog box displays: Figure 5-33 Traverse EOS Queue Status Dialog Box The queue occupancy parameters display the current queue length in KB for each queue on the port. Each NGE and NGE Pluscard supports up to 16 MB of buffering for packets queued for output ports; each 10GbE and GbE-10 card supports up to 72MB of buffering. The Queuing Policy parameter determines the number of queues used for each port. Queue 1 Occupancy (Read-only): Displays the length of the queue in KB for Queue 1 on the port. Queue 2 Occupancy (Read-only): Displays the length of the queue in KB for Queue 2 on the port. Queue 3 Occupancy (Read-only): Displays the length of the queue in KB for Queue 3 on the port. Queue 4 Occupancy (Read-only): Displays the length of the queue in KB for Queue 4 on the port. The following parameters show the status of the Random Early Discard (RED) feature: Custom RED {CoS1 CoS2 CoS3 CoS4}: Select to configure the following RED thresholds for CoS1 (queue 1). RED {CoS1 CoS2 CoS3 CoS4} Yellow Min (KB): Displays a number between 0 and 8,000 KB in increments of 1 KB; default is 0. RED {CoS1 CoS2 CoS3 CoS4} Yellow Max (KB): Displays a number between 0 and 8,000 KB in increments of 1 KB; default is 0. RED {CoS1 CoS2 CoS3 CoS4} Green Min (KB): Displays a number between 0 and 8,000 KB in increments of 1 KB; default is 0. Release TN4.0.x Turin Networks Page 5-67

TransNav GUI Guide, Section 5: Equipment Ethernet or EOS Port Queues RED {CoS1 CoS2 CoS3 CoS4} Green Max (KB): Displays a number between 0 and 8,000 KB in increments of 1 KB; default is 0. Automatic RED configuration is always enabled for an Ethernet port, a link aggregation group, or an EOS port. The system automatically establishes RED curves for each of the queues based on the link speed of the port, as shown in the following table: Table 5-5 System Defaults for RED Thresholds Link Speed Yellow Green Minimum Maximum Minimum Maximum < 1 Mbps 0 KB 0 KB 0 KB 0 KB 1 to < 3 Mbps 16 KB 32 KB 64 KB 128 KB 3 to < 6 Mbps 32 KB 64 KB 128 KB 256 KB 6 to < 9 Mbps 64 KB 128 KB 256 KB 384 KB 9 to < 10 Mbps 64 KB 128 KB 384 KB 512 KB 10 to < 1,000 Mbps 64 KB 128 KB 512 KB 768 KB > 1,000 Mbps 256 KB 512 KB 768 KB 1,536 KB Command buttons are as follows: Refresh: Click Refresh to refresh the displayed data. Done: Click Done to close the dialog box and return to the main screen. Page 5-68 Turin Networks Release TN4.0.x

Chapter 4 Ethernet Equipment EOS Port Status EOS Port Status In a Traverse node Shelf View click the Ethernet tab, click the EOS subtab, select an EOS port, then click Edit. The Edit EOS tab displays. On the Edit EOS tab, click Status. The EOS Port Status dialog box displays. Figure 5-34 EOS Port Status Active Src Members: Indicates the number of EOS port members that are currently transmitting SONET/SDH payloads on this EOS port as defined by ITU-T Rec G.7041. Active Sink Members: Indicates the number of EOS port members that are currently receiving SONET/SDH payloads on this EOS port as defined by ITU-T Rec G.7041. Note: LCAS must be enabled on this EOS port for this value to display. RSTP Port State (Read-only): Indicates the current activity state for this EOS port. Valid values are: Disabled: RSTP is not running on this EOS port. Reasons for this include: the EOS port may be in a failed (alarmed) state; RSTP may have been manually Disabled on this EOS port; the EOS port is not included in an activated Bridge service. Listening: This EOS port is preparing to forward frames. It is temporarily disabled to prevent loops which may occur as the active topology of the LAN changes. Learning is disabled since changes in active topology can lead to incorrect information when the topology becomes stable. Learning: This EOS port is preparing to forward frames. It is temporarily disabled to prevent loops which may occur as the active topology of the LAN changes. Learning is enabled to collect information prior to forwarding to reduce the number of frames that are unnecessarily flooded. Forwarding: This EOS port is forwarding frames. Blocking: This EOS port is not forwarding frames. It is preventing frames from looping in the active topology. RSTP Port Role (Read-only): This field reads one of the following values: Disabled: RSTP is not enabled for this EOS port. Root: This EOS port is closest to the root bridge in terms of path cost. This EOS port also forwards Ethernet frames. Designated: This EOS port forwards Ethernet frames. Alternate: This EOS port is blocked but can quickly become forwarding ports when the topology is reconfigured. Member Number: Indicates the provisioned member number. TxLcasState: Indicates the current LCAS source state of this EOS port member. Valid values are: IDLE: Member is not part of an LCAS VCG ADD: Member is joining an LCAS VCG Release TN4.0.x Turin Networks Page 5-69

TransNav GUI Guide, Section 5: Equipment EOS Port Status NORM: Member has joined an LCAS VCG and is transmitting bytes DNU: Member has joined an LCAS VCG but is not transmitting bytes because the far end sink has indicated that it is unable to receive from this member REMOVE: Member is being removed from an LCAS VCG due to management action RxLcasState (LCAS-enabled EOS ports only): Indicates the current LCAS state of this EOS port member. Valid values are: IDLE: Member is not part of an LCAS VCG OK: Member has joined an LCAS VCG and is able to receive bytes FAIL: Member has joined an LCAS VCG but is unable to receive bytes (possibly due to path failure) TxSeq: Indicates the sequence in which the bytes of the Ethernet frames are distributed across the EOS port members. RxSeq: Indicates the sequence in which the bytes of the Ethernet frames are received from the EOS port members. RelDelay: Relative differential delay. The amount of delay in milliseconds between arrival of a signal on the earliest member of the EOS port, and arrival of the correlated signal on this member, regardless of whether LCAS is enabled. Maximum possible delays are 64 ms for NGE and NGE Plus cards and 128 ms for GE cards. Last Query (Read-only): The date and time of the last query on the status of the EOS port. Command buttons are as follows: Refresh: Click Refresh to refresh the displayed data. Done: Click Done to close the dialog box and return to the main screen. The following examples show members with a normal relative differential delay (Figure 5-35) of less than 64 ms, and with excessive relative differential delay (Figure 5-36) of more than 64 ms. In Figure 5-36, the number of Active Source Members decreases and the TxLCASState value for the member(s) with excessive relative differential delay goes to DNU (do not use) status; that member is not used in the group. Figure 5-35 EOS Port Status with Normal Relative Differential Delay Page 5-70 Turin Networks Release TN4.0.x

Chapter 4 Ethernet Equipment Link Aggregation Group Figure 5-36 EOS Port Status with Excessive Relative Differential Delay Link Aggregation Group In a Traverse node Shelf View click the Ethernet tab, click the LAG subtab, then click Add to add a LAG to the Ethernet card. The Create LAG screen displays. Figure 5-37 Create LAG Tab The parameters of the LAG are: Slot: Select the slot number of the card on which to create this LAG. If this card is in a 1:1 equipment protection group or a Carrier Ethernet Protection Pair (CEPP), select the working card. LAG ID: The identification number for the LAG. Enter a numeric character string. Description: Enter an alphanumeric character string to describe this LAG in the list on the Ethernet tab. Do not use any other punctuation or special characters. Customer: Select from a list of defined customers. Link Type: Select the types of ports to be included in this LAG. Member ports must of the same type. FE (default for Ethernet cards): Select FE to create a LAG of FE ports. GBE (default for NGE, NGE Plus, 10GbE, and GbE-10): Select GBE to create a LAG of GBE ports. Release TN4.0.x Turin Networks Page 5-71

TransNav GUI Guide, Section 5: Equipment LAG Advanced Parameters LAG Advanced Parameters See Ethernet Port Advanced Parameters, page 5-58 for descriptions of Advanced parameters common to all Ethernet ports. Part Loss Threshold: Specify the number of members in the LAG that must be active. When fewer than this number are active, the system raises the partial loss of capacity (PLC) alarm. Enter a number between 1 and 8; default is 0 which means the corresponding alarm is never raised. Page 5-72 Turin Networks Release TN4.0.x

SECTION 5EQUIPMENT Chapter 5 TransAccess 200 Mux Introduction This chapter contains the following topics: Add a TransAccess 200 Mux, page 5-73 Delete a TransAccess 200 Mux, page 5-75 TransNav System Parameters, page 5-75 Navigate to a TransAccess 200 Mux, page 5-76 Menu Options on the Sub Shelf Menu, page 5-76 Important: For information about the TransAccess 100 Mux, refer to the Release 2.0 documentation on the Turin website at www.turinnetworks.com. User registration is required. To register for the Turin Infocenter, contact your sales account team. Important: Refer to the TransAccess 200 Mux documentation for parameter descriptions and procedures on how to configure this product. Important: The user MUST enable community access to READ-WRITE on the TCP/IP configuration via the TransAccess 200 Mux telnet interface for alarms to display correctly on the TransNav management system. Add a TransAccess 200 Mux Click the node with the TransAccess 200 Mux attached, then right-click to display the short-cut menu. Click Sub Shelf, then click Attach Sub Shelf, then click TA200 to add a TransAccess 200 Mux system to the user interface. Figure 5-38 Attach Sub Shelf Release TN4.0.x Turin Networks Page 5-73

TransNav GUI Guide, Section 5: Equipment Add a TransAccess 200 Mux The Attach TA200 Shelf dialog box appears. Figure 5-39 Attach TA200 Shelf Dialog Box Configure the following parameters for this TransAccess 200 Mux. Shelf Name: Enter a unique alphanumeric name for this sub shelf. IP Address: Enter a unique IP address assigned by a network administrator for the TransAccess 200 Mux. This is a mandatory user entry. Advanced or optional parameters: Port Number (read only): The SNMP management port on this device that sends and receives management data to the TransNav management system. The default is 161. Read Community: An alpha-numeric character string that provides an SNMP management station with read-only access to this device. The Read Community Name must be the same as the Read Community field of the SNMP/IP configuration of MPU. Access this configuration of the TA200 through a telnet interface. public (default) Write Community: An alpha-numeric character string that provides an SNMP management station with read and write access to this device. The Write Community Name must be the same as the Write Community field of the SNMP/IP configuration of MPU. Access this configuration of the TA200 through a telnet interface. public (default) Timeout. The period in milliseconds after which the TransNav server will disconnect a GUI session if no activity is detected. The range is 3000 to 90 000 milliseconds. The default value is 5000 milliseconds. Number of Retries.The number of times the Traverse node tries to connect to the TransAccess 200 Mux node. The default is 5. Trap Port (read only): The port on this device that receives SNMP traps. The default is 162. Page 5-74 Turin Networks Release TN4.0.x

Chapter 5 TransAccess 200 Mux TransNav System Parameters The command buttons on this dialog box are: Add. Click Add to add the TransAccess 200 Mux to the Traverse shelf. The icon for the Traverse node changes to indicate there is a TransAccess 200 Mux shelf attached to this node. Figure 5-40 TransAccess 200 Mux in Map View Cancel: Cancel provisioning information and close the dialog box. Delete a TransAccess 200 Mux TransNav System Parameters To delete a TransAccess 200 Mux, right-click the Traverse shelf icon in Map View, click Sub Shelf, click Detach Sub Shelf, then select a sub shelf to delete. This sequence displays the Confirm Detach dialog box. The Confirm Detach dialog box displays the message: Are you sure you would like to detach sub shelf <subshelfname> from Node <NodeName>?. Click Yes to confirm your request. Click No to cancel your request and return to the main screen. From the Admin menu, click Attached Devices SNMP Parameters. The System Parameters Configuration dialog box displays. Figure 5-41 System Parameters for TransAccess 200 Mux Poll Interval. Defines how often the management server polls the TransAccess 200 Mux shelves attached to that Traverse to determine if the devices are still connected. Enter an integer between 60 and 1000 seconds; default is 60 seconds. Sync Interval. (Planned for future release.) Defines how often synchronization occurs between the Traverse and the TransAccess 200 Mux shelf to ensure that the respective views of TransAccess 200 Mux configuration and alarm status are identical. Default is 21600 seconds. Release TN4.0.x Turin Networks Page 5-75

TransNav GUI Guide, Section 5: Equipment Navigate to a TransAccess 200 Mux Navigate to a TransAccess 200 Mux Click the node with the TransAccess 200 Mux attached, then right-click to display the short-cut menu. Click Sub Shelf, then click Launch Sub Shelf to start the user interface to the TransAccess 200 Mux system. Figure 5-42 Launch TransAccess 200 Mux User Interface Important: Refer to the TransAccess 200 Mux documentation for parameter descriptions and procedures on how to configure this product. Menu Options on the Sub Shelf Menu Click the node with the TransAccess 200 Mux attached, then right-click to display the short-cut menu. Click Sub Shelf to display the menu options. Attach Sub Shelf. See Add a TransAccess 200 Mux, page 5-73. Detach Sub Shelf. See Delete a TransAccess 200 Mux, page 5-75. Sync Sub Shelf Alarms: Displays the Confirm Synchronize dialog box. This box displays the message: Are you sure you would like to synchronize sub shelf Alarms <subshelfname>? Click Yes to confirm your request. Click No to cancel your request and return to the main screen. Launch Sub Shelf. Opens the user interface to the TransAccess 200 Mux. Refer to the TransAccess 200 Mux documentation for parameter descriptions and procedures on how to configure this product. Sub Shelf Configuration. Opens the Sub Shelf Configuration dialog box. Figure 5-43 TA200 Sub Shelf Configuration The Sub Shelf Configuration dialog box displays information about how the TransAccess 200 Mux is connected to the Traverse node through the TransNav management system. Page 5-76 Turin Networks Release TN4.0.x

Chapter 5 TransAccess 200 Mux Menu Options on the Sub Shelf Menu Node ID. Displays the node name of the Traverse system to which this TransAccess 200 Mux system is attached. Sub Shelf ID. Displays the user-assigned alphanumeric name for this sub shelf. Sub Shelf Type. Displays TA200 for TransAccess 200 Mux system. Node IP Address. Displays the IP address of the Traverse system to which this TransAccess 200 Mux is attached. Sub Shelf IP Address. Displays the IP address assigned by a network administrator for the TransAccess 200 Mux. Location. Enter an alphanumeric character string to describe the physical location of this system. Contact. Enter a contact name to describe who to contact regarding maintenance of this system. Management Port (read only). Displays the SNMP management port on this device that sends and receives management data to the TransNav management system. The default is 161. Read Community: An alpha-numeric character string that provides an SNMP management station with read-only access to this device. The Read Community Name must be the same as the Read Community field of the SNMP/IP configuration of MPU. Access this configuration of the TA200 through a telnet interface. public (default) Timeout. The period in milliseconds after which the TransNav server will disconnect a GUI session if no activity is detected. The range is 3000 to 90 000 milliseconds. The default is 5000 milliseconds. Alarm Profile. Select the alarm profile of type ta200 to use with this TransAccess 200 Mux system. Trap Receive Port (read only): The port on this device that receives SNMP traps. The default is 162. Write Community: An alpha-numeric character string that provides an SNMP management station with read and write access to this device. The Write Community Name must be the same as the Write Community field of the SNMP/IP configuration of MPU. Access this configuration of the TA200 through a telnet interface. public (default) Number of Retries.The number of times the Traverse node tries to connect to the TransAccess 200 Mux node. The default is 5. The command buttons are: Apply. Click Apply to save changes and return to the main screen. Done. Click Done to cancel any changes and return to the main screen. Release TN4.0.x Turin Networks Page 5-77

TransNav GUI Guide, Section 5: Equipment Menu Options on the Sub Shelf Menu Page 5-78 Turin Networks Release TN4.0.x

SECTION 5EQUIPMENT Chapter 6 TraverseEdge 50 (TE-50) Introduction This chapter contains the following topics: Add a TE-50, page 5-79 Delete a TE-50, page 5-81 TransNav System Parameters, page 5-81 Navigate to the TE-50 Menu Options, page 5-81 Important: The user MUST enable community access to READ-WRITE on the TCP/IP configuration via the TE-50 telnet interface for alarms to alarm display correctly on the TransNav management system. Important: Refer to the TraverseEdge 50 (TE-50) User Guide for parameter descriptions and procedures on how to configure this product. Add a TE-50 Click the node with the TE-50 attached, then right-click to display the short-cut menu. Click Sub Shelf, then click Attach Sub Shelf, then click TE50 to add a TE-50 system to the user interface. Figure 5-44 Attach Sub Shelf Release TN4.0.x Turin Networks Page 5-79

TransNav GUI Guide, Section 5: Equipment Add a TE-50 The Attach TE50 Shelf dialog box appears. Figure 5-45 Attach TE50 Shelf Dialog Box Configure the following parameters for the TE-50. Shelf Name: Enter a unique alphanumeric name for this sub shelf. IP Address: Enter a unique IP address assigned by a network administrator for the TE-50. This is a mandatory user entry. Advanced or optional parameters: Port Number (read only): The SNMP management port on this device that sends and receives management data to the TransNav management system. The default is 161. Read Community: An alpha-numeric character string that provides an SNMP management station with read-only access to this device. Public is the default string. The Read Community Name must be the same as the Read Community field of the SNMP/IP configuration of the sub-shelf device controller. Access this configuration of the TE50 through a telnet interface. Write Community: An alpha-numeric character string that provides an SNMP management station with read and write access to this device. Public is the default string. The Write Community Name must be the same as the Write Community field of the SNMP/IP configuration of the sub-shelf device controller. Access this configuration of the TE50 through a telnet interface. Timeout. The period in milliseconds after which the TransNav server will disconnect a GUI session if no activity is detected. The range is 3000 to 90 000 milliseconds. The default value is 5000 milliseconds. Number of Retries.The number of times the Traverse node tries to connect to the TE-50 node. The default is 5. Trap Port (read only): The sub-shelf device port receiving the SNMP traps. The default is 162. The command buttons on this dialog box are: Add. Click Add to add the TE-50 to the Traverse shelf. The icon for the Traverse node changes to indicate there is a TE-50 shelf attached to this node. Figure 5-46 TE-50 in Map View Cancel: Cancel provisioning information and close the dialog box. Page 5-80 Turin Networks Release TN4.0.x

Chapter 6 TraverseEdge 50 (TE-50) Navigate to the TE-50 Menu Options Delete a TE-50 TransNav System Parameters To delete a TE-50, right-click the Traverse shelf icon in Map View, click Sub Shelf, click Detach Sub Shelf, then select a sub shelf to delete. This sequence displays the Confirm Detach dialog box. The Confirm Detach dialog box displays the message: Are you sure you would like to detach sub shelf <subshelfname> from Node <NodeName>? Click Yes to confirm your request. Click No to cancel your request and return to the main screen. From the Admin menu, click Attached Devices SNMP Parameters. The System Parameters dialog box displays. Figure 5-47 System Parameters for TE-50 Poll Interval. Defines how often the management server polls the TE-50 shelves attached to that Traverse to determine if the devices are still connected. Enter an integer between 60 and 1000 seconds. The default is 60 seconds. Sync Interval. (Planned for future release.) Defines how often synchronization occurs between the Traverse and the TE-50 shelf to ensure that the respective views of TE-50 configuration and alarm status are identical. Default is 21600 seconds. Navigate to the TE-50 Menu Options Click the Traverse node with the TE-50 attached, then right-click to display the short-cut menu. Click Sub Shelf to display the menu options. Figure 5-48 TE-50 Sub Shelf Menu Options Attach Sub Shelf: See Add a TE-50, page 5-79. Detach Sub Shelf: See Delete a TE-50, page 5-81. Sync Sub Shelf Alarms: Displays the Confirm Synchronize dialog box. This box displays the message: Are you sure you would like to synchronize sub shelf Alarms <subshelfname>? Click Yes to confirm your request. Click No to cancel your request and return to the main screen. Release TN4.0.x Turin Networks Page 5-81

TransNav GUI Guide, Section 5: Equipment Navigate to the TE-50 Menu Options Sub Shelf Configuration. Opens the Sub Shelf Configuration dialog box. Figure 5-49 TE-50 Sub Shelf Configuration The Sub Shelf Configuration dialog box displays information about how the TE-50 is connected to the Traverse node through the TransNav management system. Node ID. Displays the node name of the Traverse system to which this TE-50 system is attached. Sub Shelf ID. Displays the user-assigned alphanumeric name for this sub shelf. Sub Shelf Type. Displays TE-50 for the TraverseEdge 50 system. Node IP Address. Displays the IP address of the Traverse system to which this TE-50 is attached. Sub Shelf IP Address. Displays the IP address assigned by a network administrator for the TE-50. Location. Enter an alphanumeric character string to describe the physical location of this system. Contact. Enter a contact name to describe who to contact regarding maintenance of this system. Management Port (read only). Displays the SNMP management port on this device that sends and receives management data to the TransNav management system. The default is 161. Read Community: An alpha-numeric character string (public is the default) that provides an SNMP management station with read-only access to this device. The Read Community Name must be the same as the Read Community field of the SNMP/IP configuration of MPU. Access this configuration of the TE-50 through a telnet interface. Timeout. The period in milliseconds after which the TransNav server will disconnect a GUI session if no activity is detected. The range is 3000 to 90000 milliseconds. The default value is 5000 milliseconds. Alarm Profile. Select the alarm profile of type te50 to use with this TE-50 system. Trap Receive Port (read only): The port on this device that receives SNMP traps. The default is 162. Write Community: An alpha-numeric character string (public is the default) that provides an SNMP management station with read and write access to this device. The Page 5-82 Turin Networks Release TN4.0.x

Chapter 6 TraverseEdge 50 (TE-50) Navigate to the TE-50 Menu Options Write Community Name must be the same as the Write Community field of the SNMP/IP configuration of MPU. Access this configuration of the TE-50 through a telnet interface. Number of Retries.The number of times the Traverse node tries to connect to the TE-50 node. The default is 5. The command buttons are: Apply. Click Apply to save changes and return to the main screen. Done. Click Done to cancel any changes and return to the main screen. Release TN4.0.x Turin Networks Page 5-83

TransNav GUI Guide, Section 5: Equipment Navigate to the TE-50 Menu Options Page 5-84 Turin Networks Release TN4.0.x

SECTION 6SERVICES SECTION 6 SERVICES Contents Chapter 1 Service Creation Concepts Traverse Services Definition...................................... 6-1 Supported Features............................................. 6-1 DS3 Transmux............................................. 6-1 Bridging and Rolling........................................ 6-1 Multicast Connections....................................... 6-2 Optical Transmux.......................................... 6-2 Resource Advisory......................................... 6-2 SDH to SONET Interworking.................................. 6-2 VT/VC Switching........................................... 6-2 Transport Capacity............................................. 6-2 Transport Capacity............................................. 6-4 Traverse Service Types......................................... 6-5 Service Creation Models......................................... 6-7 End-to-End Services Over Mixed Topologies......................... 6-7 Service Creation Process........................................ 6-8 1. Add the Service.......................................... 6-8 2. Configure Service Parameters.............................. 6-8 3. Select the Service Endpoints................................ 6-9 4. Configure Service Protection................................ 6-9 5. Configure Other Service Characteristics....................... 6-10 6. Select the Path for End-to-End Services....................... 6-10 7. Activate the Service....................................... 6-11 Chapter 2 SONET Services Create a SONET Service........................................ 6-13 Create Service Parameters....................................... 6-15 Choose Endpoints.............................................. 6-16 Endpoints for STS Services...................................... 6-17 Endpoints for VT1.5 Services..................................... 6-18 Configure Protection Parameters.................................. 6-20 Configure Advanced Parameters (Alphabetic Order)................... 6-21 Configure the Path Through the Network for End-to-End Services......... 6-25 Chapter 3 SDH Services Release TN4.0.x Turin Networks Page i

TransNav GUI Guide, Section 6 Services Create an SDH Service.......................................... 6-28 Create Service Parameters....................................... 6-29 Choose an Endpoint............................................ 6-30 Endpoints for VC3 and VC4 Services............................... 6-31 Endpoints for VC11 and VC12 Services............................. 6-32 Starting AUG1 Numbers for VC-3 Services........................... 6-34 Configure Protection Parameters.................................. 6-35 Configure Advanced Parameters (Alphabetic Order)................... 6-37 Chapter 4 Ethernet Services Ethernet Cards................................................. 6-41 Create an Ethernet Service....................................... 6-42 Ethernet Service Parameters...................................... 6-42 Advanced Parameters Ethernet Service Ports (Traverse only)............ 6-43 Advanced Parameters Ethernet Service............................. 6-44 Guaranteed Data Rate and Ethernet Services........................ 6-45 Bandwidth Profiles.............................................. 6-46 Bandwidth Profile Dialog Box..................................... 6-47 Policers...................................................... 6-48 Classifiers.................................................... 6-49 TE-100 Classifiers.............................................. 6-50 Chapter 5 VC-Bundles Create a VC-bundle............................................. 6-54 Configure VCB Parameters....................................... 6-55 Configure Advanced Parameters................................... 6-55 Chapter 6 Service Groups Create Service Group Tab........................................ 6-57 Service Group Tab.............................................. 6-59 Edit Service Group Tab.......................................... 6-59 Chapter 7 Managing Services Service Tab................................................... 6-62 Service Menu and Shortcut Menus................................. 6-64 Working with the Service List...................................... 6-65 Sorting Services............................................ 6-65 Resizing Columns.......................................... 6-65 Grouping Services.......................................... 6-65 Filtering Services........................................... 6-65 Viewing, Editing, or Deleting a Service.............................. 6-66 Setting Service Filters........................................... 6-66 Service Filters, Type Tab......................................... 6-66 Page ii Turin Networks Release TN4.0.x

TransNav GUI Guide, Section 6 Services Service Filters, Node Tab........................................ 6-67 Service Filters, Source Tab....................................... 6-68 Service Filters, Destination Tab................................... 6-69 Service Filters, Customer Tab..................................... 6-70 Chapter 8 Managing Service Paths Showing TxRx Paths............................................ 6-71 Transmit and Receive Paths for Services............................ 6-72 Refresh Status of Service........................................ 6-73 Viewing Service Alarms.......................................... 6-73 Viewing Details................................................ 6-74 Assigning or Suppressing Alarms to Path Endpoints................... 6-74 Retrieving Service Performance Data............................... 6-76 Protection Switching Path-Protected Services........................ 6-77 List of Figures Figure 6-1 End-to-End Services Creation Model...................... 6-7 Figure 6-2 Hop-by-Hop Services Creation Model...................... 6-7 Figure 6-3 Add SONET Service................................... 6-13 Figure 6-4 Create Service Tab.................................... 6-14 Figure 6-5 Choosing Endpoints for SONET Services................... 6-16 Figure 6-6 Protection Dialog Box.................................. 6-20 Figure 6-7 Advanced Parameters Dialog Box........................ 6-21 Figure 6-8 Add Hops to an End-to-End Service....................... 6-25 Figure 6-9 Add SDH Service..................................... 6-28 Figure 6-10 Create Service Tab.................................... 6-28 Figure 6-11 Selecting Sources and Destinations for SDH Services......... 6-30 Figure 6-12 Protection Dialog Box.................................. 6-35 Figure 6-13 Advanced Parameters Dialog Box........................ 6-37 Figure 6-14 Add Ethernet Service.................................. 6-42 Figure 6-15 Create Ethernet Service Screen.......................... 6-42 Figure 6-16 Advanced Parameters Ethernet Service Ports............... 6-43 Figure 6-17 Advanced Parameter Ethernet Line Service................. 6-44 Figure 6-18 Bandwidth Profiles Dialog Box........................... 6-46 Figure 6-19 Bandwidth Profiles Configuration......................... 6-47 Figure 6-20 Create Policer Tab.................................... 6-48 Figure 6-21 Current Class of Service Values Displayed................. 6-49 Figure 6-22 Classifier Configuration Dialog Box........................ 6-49 Figure 6-23 TE100 Classifier Configuration Dialog Box.................. 6-50 Figure 6-24 Add VCB Service..................................... 6-54 Figure 6-25 Create VCB Services.................................. 6-54 Figure 6-26 Advanced Parameters for VCB Service (Defaults)............ 6-55 Figure 6-27 Create Service Group Tab.............................. 6-57 Figure 6-28 Service Group Advanced Parameters Dialog Box............ 6-58 Figure 6-29 Service Group Tab.................................... 6-59 Figure 6-30 Edit Service Group.................................... 6-59 Release TN4.0.x Turin Networks Page iii

TransNav GUI Guide, Section 6 Services Figure 6-31 Service Tab.......................................... 6-62 Figure 6-32 Service Menu......................................... 6-64 Figure 6-33 Service Tab and Right-Click Menu........................ 6-64 Figure 6-34 Service List Filters Dialog Box, Type Tab................... 6-66 Figure 6-35 Service List Filters Dialog Box, Node Tab................... 6-67 Figure 6-36 Service List Filters Dialog Box, Source Tab................. 6-68 Figure 6-37 Service List Filters Dialog Box, Destination Tab.............. 6-69 Figure 6-38 Service List Filters Dialog Box, Customer Tab............... 6-70 Figure 6-39 Path Display for Service Dialog Box....................... 6-71 Figure 6-40 Alarm Tab on Path Display for Service Dialog Box............ 6-73 Figure 6-41 Details Tab on Path Display for Service Dialog Box........... 6-74 Figure 6-42 CTP Tab on Path Display for Service Dialog Box............. 6-74 Figure 6-43 Path Overhead Dialog Box.............................. 6-75 Figure 6-44 PM Tab on Path Display for Service Dialog Box.............. 6-76 Figure 6-45 Switch Tab on Path Display for Service Dialog Box........... 6-77 List of Tables Table 6-1 Transport Capacity.................................... 6-3 Table 6-2 Transport Capacity.................................... 6-4 Table 6-3 ADM Service Types.................................... 6-5 Table 6-4. Ethernet Services..................................... 6-5 Table 6-5 Endpoints for STS Services.............................. 6-17 Table 6-6 Endpoints for VT1.5 Services............................ 6-18 Table 6-7 Endpoints for VC3 and VC4 Services...................... 6-31 Table 6-8 Endpoints for VT11 and VC12 Services.................... 6-32 Table 6-9 Starting AUG1 Numbers for VC-3 Paths.................... 6-34 Table 6-10 Starting AUG1 Numbers for VC-4 Paths.................... 6-34 Table 6-11 CAC Limits for Sum of All Guaranteed Data Rates Sharing a Port6-45 Table 6-12. Maximum Bandwidth Burst Size Parameters................ 6-47 Table 6-13 Possible Service States in Response to User Actions......... 6-63 Page iv Turin Networks Release TN4.0.x

SECTION 6SERVICES Chapter 1 Service Creation Concepts Introduction Traverse Services Definition Supported Features Creating services in a TransNav managed 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 6-1 Supported Features, page 6-1 Transport Capacity, page 6-4 Traverse Service Types, page 6-5 Service Creation Process, page 6-8 End-to-End Services Over Mixed Topologies, page 6-7 For provisioning procedures and examples of supported services, see the Traverse Provisioning Guide or the TraverseEdge 100 User Guide. A service in a TransNav managed network connects traffic from a source to a destination. The source can be a port, subport, channel, or path. The source originates on any card. The destination of the service varies depending on the connection you are creating. The destination can be a compatible card, port, subport, or another service. Additionally, the destination can be on the same node or on a separate node. There are three types of services on a Traverse system: regular SONET, Ethernet, or VC-Bundle for transport of Ethernet services. DS3 Transmux. Transmultiplexing functionality is provided by the Traverse DS3/EC-1 Transmux card. This capability is important in applications where incoming traffic is channelized DS3 and the payload of the outgoing circuit needs to be VT-mapped, such as those that are handed off to the Traverse switch fabric. Bridging and Rolling. The Traverse system supports transferring services from one facility to another without dropping traffic. See the Traverse Provisioning Guide, Section 5 Creating Service Applications, Chapter 2 Bridging and Rolling Services, page 5-13. Release TN4.0.x Turin Networks Page 6-1

TransNav GUI Guide, Section 6: Services Transport Capacity 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 SONET-VT Ethernet SDH-VC4 SDH-VC3 Use multicast connections to create drop-and-continue services in a network of Traverse nodes. Optical Transmux. The Transmux component also transparently provides this transmux capability when traffic ingresses and egresses the Traverse system using an optical interface. In this case, the Transmux component receives incoming DS1/E1-mapped DS3s from the Traverse backplane and converts the outgoing signal to VT-mapped STS-1s or VC-mapped AU-3s. Resource Advisory. If this feature is enabled, the system displays only available resources. Ports, paths, and other resources assigned to activated services appear in the graphical user interface with an asterisk (*). SDH to SONET Interworking. The Traverse platform supports SDH to SONET interworking capabilities. That is, you can connect an SDH signal to a SONET signal. The Traverse supports the following gateway services: DS1 over SDH E1 over SONET SDH to SONET SONET to SDH VT/VC Switching. Turin offers two options to switch traffic at the VT/VC levels: VT/TU 5G Switch card VTX/VCX integrated cards See the Traverse Product Overview Guide, Section 3 Card (Module) Descriptions, Chapter 6 VT/VC Switching Cards for detailed descriptions of these VT/VC switching options. Transport Capacity In a TransNav managed network, you can switch traffic at different levels of the optical hierarchy. In SONET, you can switch traffic at the VT layer, at the STS layer, or at the concatenated STS layers. In SDH, you can switch traffic at the low order virtual container (LOVC) layers, at the high order VC-3, or at the concatenated VC (VC-3-nc or VC-4-nc) layers. Page 6-2 Turin Networks Release TN4.0.x

Chapter 1 Service Creation Concepts Transport Capacity Use the following table as a reference for the transport requirements of each supported service. Table 6-1 Transport Capacity Payload DS1 or VT 1.5 Transpor t STS-1 OC-3 OC-12 OC-48 OC-192 Mbps 51.84 155.52 622.08 2488.32 9953.28 1.544 28 84 336 1344 5376 DS3 44.736 1 3 12 48 192 E1 or VT 2 2.048 21 63 252 1008 4032 E3 34.368 1 3 12 48 192 VT 1.728 28 84 336 1344 5376 VC-12 2.304 21 63 252 1008 4032 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 48 1 Mbps 149 2 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. Release TN4.0.x Turin Networks Page 6-3

TransNav GUI Guide, Section 6: Services Transport Capacity Transport Capacity In a TransNav managed network, you can switch traffic at different levels of the optical hierarchy. In SONET, you can switch traffic at the VT layer, at the STS layer, or the concatenated STS layers. In SDH, you can switch traffic at the low order virtual container (LOVC) layers, at the high order VC-3, or concatenated VC (VC-3-nc or VC-4-nc) layers. Use the following table as a reference for the transport requirements of each supported service. Table 6-2 Transport Capacity Payload DS1 or VT 1.5 Transport STS-1 OC-3 OC-12 OC-48 OC-192 Mbps 51.84 155.52 622.08 2488.32 9953.28 1.544 28 84 336 1344 5376 DS3 44.736 1 3 12 48 192 E1 or VT 2 2.048 21 63 252 1008 4032 E3 34.368 1 3 12 48 192 VT 1.728 28 84 336 1344 5376 VC-12 2.304 21 63 252 1008 4032 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 48 1 Mbps 149 2 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. Page 6-4 Turin Networks Release TN4.0.x

Chapter 1 Service Creation Concepts Traverse Service Types Traverse Service Types The Traverse supports the following types of services: ADM Service Types, page 6-5 Ethernet Services, page 6-5 For information about pre-release TR2.1 Legacy Ethernet modules, refer to the Release 2.0 documentation on the Turin website at www.turinnetworks.com. User registration is required. To register for the Turin Infocenter, contact your sales account team. Table 6-3 ADM Service Types Service Type Definition and Reference See the Traverse Provisioning Guide or the TraverseEdge 100 User Guide for details on creating ADM services. SDH SDH-Endpoint SDH-Tunnel SONET Use this service to transport synchronous traffic through the network. Also, use this service as a regular cross-connect when creating a transport path hop-by-hop through the network. Use this service to create a termination point to multiplex low order traffic into the network. Also use this service to create a transport path hop-by-hop through the network. Use this service to create a transport path end-to-end through the network. Use this service to transport synchronous traffic through the network. Also, use this service as a regular cross-connect when creating a transport path hop-by-hop through the network. Table 6-4. Ethernet Services Service Type Definition and Reference For guidelines and procedures on creating Ethernet services, see one of the following references: Traverse Provisioning Guide, Section 7 Configuring Ethernet TraverseEdge 100 User Guide, Section 6 Creating Ethernet Services Line An Ethernet line service is a forwarding relationship between two endpoints on the same card. Use this service to create a dedicated point-to-point service, a shared point-to-point service, or an internet access application. Release TN4.0.x Turin Networks Page 6-5

TransNav GUI Guide, Section 6: Services Traverse Service Types Table 6-4. Ethernet Services (continued) Bridge Service Type Aggregation Bridge Definition and Reference A bridge service is a forwarding relationship between an arbitrary number of endpoints on the same card. Any of the endpoints can be shared (by VLAN ID) with other services. Within a single bridge service, a packet is forwarded to one endpoint or to all endpoints using standard MAC address forwarding rules. Use this service to create a Virtual LAN Service application in the network. An aggregation bridge service is a hybrid of a line service and a bridge service. It is a forwarding relationship between a set of endpoints on a card, where one endpoint is considered the aggregation port and the other endpoints are considered ordinary members of the service. Traffic received on the aggregation port is forwarded just as in a bridge service to one or more ordinary members based on the destination MAC address. Traffic received on the ordinary members of the service is forwarded directly to the single aggregation port. Page 6-6 Turin Networks Release TN4.0.x

Chapter 1 Service Creation Concepts End-to-End Services Over Mixed Topologies Service Creation Models You can create services in a Traverse network either end-to-end or hop-by-hop. You can create services in a TraverseEdge network hop-by-hop only. An end-to-end service is a service you can set up between nodes. You select the source 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 Endpoint node Trunk Card Trunk Card Intermediate node Trunk Card Trunk Card Endpoint node Tributary Card Figure 6-1 End-to-End Services Creation Model A hop-by-hop service is a service that you configure between two cards 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 Endpoint node Trunk Card Trunk Card Intermediate node Trunk Card Trunk Card Endpoint node Tributary Card Figure 6-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. End-to-End Services Over Mixed Topologies The TransNav management system supports creating uni- and bi-directional end-to-end services over the following topologies: Up to four single-node interconnected UPSR or SNCP rings Single-node interconnected UPSR and 1+1 APS linear chains Single-node interconnected SNCP rings and 1+1 MSP linear chains Up to three interconnected BLSR or MS-SP rings Single-node interconnected BLSR and 1+1 MSP linear chains Single-node interconnected MS-SP rings and 1+1 MSP linear chains Single-node interconnected BLSR, UPSR, and 1+1 APS linear chains Single-node interconnected MS-SP rings, SNCP rings, and 1+1 MSP linear chains See the Traverse Product Overview Guide, Section 5 Planning and Engineering, Chapter 4 Protected Network Topologies, page 5-35 for information on network topologies. Release TN4.0.x Turin Networks Page 6-7

TransNav GUI Guide, Section 6: Services Service Creation Process Service Creation Process 1. Add the Service On the Service tab, select the service type and click Add. 1 2. Configure Service Parameters Enter the name of the service and configure other general parameters. 2 Page 6-8 Turin Networks Release TN4.0.x

Chapter 1 Service Creation Concepts Service Creation Process 3. Select the Service Endpoints Set the endpoints for this service. Click the Source row in the Endpoint column to display the Choose an Endpoint dialog box. Select the source and click Done to close the dialog box. Click the Destination row, select the endpoint in the dialog box and click Done. 3 4. Configure Service Protection Click the Protection parameter field to display the Protection dialog box. Select the type of protection for the service by clicking on the tabs in the dialog box. Configure any applicable parameters. Click Done to close the dialog box and return to the Create Service tab. 4 Release TN4.0.x Turin Networks Page 6-9

TransNav GUI Guide, Section 6: Services Service Creation Process 5. Configure Other Service Characteristics Click the Advanced button to display the Advanced Parameters dialog box. Configure the characteristics of the service. If this is an end-to-end service, configure the characteristics of the connection throughout the network. 5 6. Select the Path for End-to-End Services If Strict=, explicitly select the service route between defined endpoints. Click the plus sign in the Add column to add another hop to the service. Click the minus sign in the Remove column to remove a hop. Click Apply to add the provisioned service to the service list and return to the Service tab. 6 Page 6-10 Turin Networks Release TN4.0.x

Chapter 1 Service Creation Concepts Service Creation Process 7. Activate the Service On the Service tab, click the service to select it, right-click for the menu, and click Activate. 7 Release TN4.0.x Turin Networks Page 6-11

TransNav GUI Guide, Section 6: Services Service Creation Process Page 6-12 Turin Networks Release TN4.0.x

SECTION 6SERVICES Chapter 2 SONET Services Introduction Create a SONET Service This chapter explains the following topics for SONET services: Create a SONET Service, page 6-13 Create Service Parameters, page 6-15 Choose Endpoints, page 6-16 Endpoints for STS Services, page 6-17 Endpoints for VT1.5 Services, page 6-18 Configure Protection Parameters, page 6-20 Configure Advanced Parameters (Alphabetic Order), page 6-21 Configure the Path Through the Network for End-to-End Services, page 6-25 See the Traverse Provisioning Guide or TraverseEdge 100 User Guide for guidelines and procedures to create or remove SONET services. From the Service tab, select SONET and click Add. Figure 6-3 Add SONET Service Release TN4.0.x Turin Networks Page 6-13

TransNav GUI Guide, Section 6: Services Create a SONET Service The Create Service tab displays. 1 3 2 4 5 Figure 6-4 Create Service Tab On the Create Service tab, perform the following steps in order: 1. Enter the name and configure general parameters. For more information, see Create Service Parameters, page 6-15. 2. Select the endpoints of the service. For hop-by-hop services, see Choose Endpoints, page 6-16. For end-to-end services, see Configure Advanced Parameters (Alphabetic Order), page 6-25. 3. Set the protection parameters of the service. See Configure Protection Parameters, page 6-20. 4. Configure other characteristics of the connection. For more information, see Configure Protection Parameters, page 6-21. 5. Click Apply. Page 6-14 Turin Networks Release TN4.0.x

Chapter 2 SONET Services Create Service Parameters Create Service Parameters Name: Enter a unique name for the service. Use alphanumeric characters and spaces only. Do not use any other punctuation or special characters. Description: Enter the description of the service. Use alphanumeric characters and spaces only. Do not use any other punctuation or special characters. Bandwidth: Select the total bandwidth for the service: VT1.5 STS-1 (default) STS-3c STS-12c STS-48c Strict: For end-to-end services only. Select to explicitly define the service route through all nodes in the network. See Configure Advanced Parameters (Alphabetic Order), page 6-25. Customer: Select a customer name from the drop-down list box. For details, see Adding Customer Information, page 2-31. Endpoint Table. Select the endpoints of the service. For hop-by-hop services, see Choose Endpoints, page 6-16. For end-to-end services, see Endpoints for VT1.5 Services, page 6-18. Protection. This field is context sensitive depending on the selected endpoints. Configure the protection parameters AFTER you have selected the endpoints of the service. See Configure Protection Parameters, page 6-20. Command buttons are as follows: Advanced: Configure the characteristics of the connection. See Configure Protection Parameters, page 6-21. Apply: Apply changes and return to the service list on the Service tab. Cancel: Cancel information, close the screen, and return to the Service tab. Release TN4.0.x Turin Networks Page 6-15

TransNav GUI Guide, Section 6: Services Choose Endpoints Choose Endpoints In the Create Service screen, click a row in the EndPoint column of the endpoint table. Figure 6-5 Choosing Endpoints for SONET Services The Choose an EndPoint dialog box displays in the upper left corner of the computer screen. From the navigation tree, click the node, card, and depending on the card type the port, STS, VTG, and VT. See Endpoints for STS Services, page 6-17 for valid STS sources and destinations. See Endpoints for VT1.5 Services, page 6-18 for valid VT sources and destinations. Command buttons are as follows: Done: Click after you have selected the correct endpoint for the service. Cancel: Cancel information, close the dialog box, and return to the Create Service screen. Page 6-16 Turin Networks Release TN4.0.x

Chapter 2 SONET Services Endpoints for STS Services Endpoints for STS Services The following table lists valid sources and destinations for STS services. Your network may require creating multiple services at multiple nodes. The Traverse system supports multicast STS connections for 1+1 path-protected and drop-and-continue services. Table 6-5 Endpoints for STS Services Sources Destinations Port Type Mapping Port Type Mapping OC-N 1 node/slot/port/sts STM-N (HO) STM-N (LO) all ports E1 card OC-N EC3 EC1 DS3CC DS3TMX all ports DS1 card EC3 node/slot/port/sts STM-N (HO) STM-N (LO) OC-N EC3 EC1 DS3CC EC1 node/slot/port STM-N (HO) STM-N (LO) OC-N EC3 EC1 DS3CC DS3CC node/slot/port STM-N (HO) STM-N (LO) OC-N EC3 EC1 DS3CC DS3TMX node/slot/port STM-N (HO) STM-N (LO) OC-N EC3 node/slot/port/aug1/ node/slot/port/aug1/vc3 node/slot/port/aug1/tug3/vc3 node/slot node/slot/port/sts node/slot/port/sts node/slot/port node/slot/port node/slot/port node/slot node/slot/port/aug1/ node/slot/port/aug1/vc3 node/slot/port/aug1/tug3/vc3 node/slot/port/sts node/slot/port/sts node/slot/port node/slot/port node/slot/port/aug1/ node/slot/port/aug1/vc3 node/slot/port/aug1/tug3/vc3 node/slot/port/sts node/slot/port/sts node/slot/port node/slot/port node/slot/port/aug1/ node/slot/port/aug1/vc3 node/slot/port/aug1/tug3/vc3 node/slot/port/sts node/slot/port/sts node/slot/port node/slot/port node/slot/port/aug1/ node/slot/port/aug1/vc3 node/slot/port/aug1/tug3/vc3 node/slot/port/sts node/slot/port/sts Release TN4.0.x Turin Networks Page 6-17

TransNav GUI Guide, Section 6: Services Endpoints for VT1.5 Services Table 6-5 Endpoints for STS Services (continued) Sources Destinations Port Type Mapping Port Type Mapping All ports on a DS1 card node/slot STM-N (HO) STM-N (LO) node/slot/port/aug1/ node/slot/port/aug1/vc3 node/slot/port/aug1/tug3/vc3 OC-N EC3 node/slot/port/sts node/slot/port/sts SONET port on backplane for EOS ports node/slot (Ethernet card)/sts OC-N Any Ethernet card on a different node node/slot/port/sts node/slot (Ethernet card)/sts 1 For STS services between OC-192 ports, the source STS number and the destination STS number must in the same range when the range is between 1 and 48, or 49 and 192. For example, if the source STS is STS number 12, the destination STS must be between STS number 1 and 48. If the source STS is STS number 105, the destination STS must be between STS number 49 and 192. Endpoints for VT1.5 Services The following table lists valid sources and destinations for VT1.5 services. Your network may require creating multiple services at multiple nodes. There must be a VT/TU 5G switch card or a card with an integrated VTX/VCX present in the shelf to create this service. Table 6-6 Endpoints for VT1.5 Services Sources Destinations Port Type Mapping Port Type Mapping OC-N node/slot/port/sts/vtg/vt STM (HO) 1 STM (LO) 1 E1 OC-N EC3 EC1 DS3TMX 2 DS1 EC1 node/slot/port/sts-1/vtg/vt STM (HO) 1 STM (LO) 1 E1 OC-N EC1 DS3TMX DS1 node/slot/port/aug1/tug3/tug2/vc11 node/slot/port/aug1/vc3/tug2/vc11 node/slot/port node/slot/port/sts/vtg/vt node/slot/port/sts/vtg/vt node/slot/port/sts-1/vtg/vt node/slot/port/subport node/slot/port node/slot/port/aug1/tug3/tug2/vc11 node/slot/port/aug1/vc3/tug2/vc11 node/slot/port node/slot/port/sts/vtg/vt node/slot/port/sts-1/vtg/vt node/slot/port/subport node/slot/port Page 6-18 Turin Networks Release TN4.0.x

Chapter 2 SONET Services Endpoints for VT1.5 Services Table 6-6 Endpoints for VT1.5 Services Sources Destinations Port Type Mapping Port Type Mapping DS3TMX 2 node/slot/port/subport STM (HO) 1 STM (LO) 1 E1 OC-N EC1 DS3TMX 2 DS1 DS1 node/slot/port STM (HO) 1 STM (LO) 1 E1 OC-N EC1 DS3TMX 2 DS1 node/slot/port/aug1/tug3/tug2/lo vc 3 node/slot/port/aug1/vc3/tug2/lo vc 3 node/slot/port node/slot/port/sts/vtg/vt node/slot/port/sts-1/vtg/vt node/slot/port/subport node/slot/port node/slot/port/aug1/tug3/tug2/lo vc 3 node/slot/port/aug1/vc3/tug2/lo vc 3 node/slot/port node/slot/port/sts/vtg/vt node/slot/port/sts-1/vtg/vt node/slot/port/subport node/slot/port SONET port on backplane for EOS ports node/slot (Ethernet card)/sts/vtg/vt OC-N Any Ethernet card on a different node. node/slot/port/sts/vtg/vt node/slot (Ethernet card)/sts 1 There must be an SDH-Endpoint or SDH-Tunnel service already with a Bandwidth of VC (Grooming) configured on the port. 2 Port is DS1-mapped (DS3 Mapping parameter is DS1). 3 lo vc is VC11 or VC12. Release TN4.0.x Turin Networks Page 6-19

TransNav GUI Guide, Section 6: Services Configure Protection Parameters Configure Protection Parameters On the Create Service screen, click the Protection field to display the Protection dialog box. Figure 6-6 Protection Dialog Box Select a Protection Group Type from the drop-down list. In the Protection Group Type parameter, select one of the following options: Unprotected (default): Use for services that are unprotected, 1+1 APS protected, protected with an equipment protection group, or in a 1+1 Path Protection group. Any: The system finds the best effort of protection through the network. There may be some spans of unprotected links, but the system creates the service. Full: The system only creates the service if there is full protection on every transport link in the network. 1+1 Path Protected: Select if this service is protected by another service (two services model). UPSR Ingress: Select if the service is a VT1.5 or a LO VC service and is creating a bidirectional path across two interconnected UPSRs or SNCP rings. After selecting the protection group type, click one of the tabs to configure the applicable parameters: General: WTR (Wait To Restore) Time: This parameter is configurable only if the checkbox for the Revertive parameter 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. Enter a value between 1 and 60 minutes; default is 5 minutes. Revertive: Specifies if the system switches traffic back to the original port or path once the failure condition no longer exists. Select the checkbox to switch traffic back to the original port or path once the failure condition no longer exists. Page 6-20 Turin Networks Release TN4.0.x

Chapter 2 SONET Services Configure Advanced Parameters (Alphabetic Order) Clear the checkbox for the Protect link or path to continue to carry traffic once the failure condition no longer exists. SNCP/UPSR parameters: Endpoint (read-only): Displays the endpoints of the service if it is on an UPSR or SNCP protected ring. Ring Id (read-only): Displays the ring ID number if this service is on a UPSR or SNCP ring. MSSP/BLSR parameters: Source Node ID (services provisioned hop-by-hop only): Select the BLSR Node ID where the traffic on this path enters the ring. Destination Node ID (services provisioned hop-by-hop only): Select the BLSR Node ID where the traffic on this path exits the ring. 1+1 Path Protection: HoldOffTimer: Applies only if there is also a 1+1 APS protection group. Allows line protection to switch first before the path switches. If the line switches within the specified time period, the path does not switch. The hold-off timer starts when path protection detects a path failure. The range is 0 to 1000 ms. The default is 0 which means path protection performs protection switching immediately. Configure Advanced Parameters (Alphabetic Order) On the Create Service screen, click the Advanced button. The Advanced Parameters dialog box displays. Figure 6-7 Advanced Parameters Dialog Box Important: The contents of this dialog box are context-sensitive and depend on the selected sources and destinations. The following parameter descriptions are listed in alphabetical order. Bridge and Roll (Hop-by-hop services only): Select to create a bridge service. Use this parameter to transfer traffic from one facility to another without affecting live traffic. See the Traverse Provisioning Guide, Section 5 Creating Service Applications, Release TN4.0.x Turin Networks Page 6-21

TransNav GUI Guide, Section 6: Services Configure Advanced Parameters (Alphabetic Order) Chapter 2 Bridging and Rolling Services, page 5-13 for detailed procedures on bridging and rolling services. DestDS1Mapping: For optical transmux services, select this parameter if the destination path carries a channelized DS3 payload. DestDS3Mapping: For optical transmux services, select this parameter if the destination STS carries a channelized DS3 payload. DestE1Mapping: For optical transmux services, select this parameter if the destination path carries a channelized DS3 payload. Dest PM Template: Select from the defined performance monitoring templates. The system default for performance monitoring thresholds is disabled for all parameters. Use the performance monitoring templates to set default thresholds or to customize threshold values. See Section 8 Maintenance and Testing, Chapter 1 Performance Monitoring, page 8-1 for information on how to use performance monitoring templates. Expected RTD: Enter the expected round trip delay measurement, in milliseconds, for this service. Values are 0 to 1000 milliseconds; default is 300ms. Failure Retry Count (for end-to-end services only): The number of times the system tries to reestablish the service before declaring it failed. Select 0 to 30; default is 3. Fwd Path Format: This port transmits a path trace identifier in the J1 byte of the SONET/SDH frame so that the path receiver can verify its continued connection. The values are: 16 bytes (default): Select if the receiver is an SDH port. 64 bytes: Select if the receiver is another SONET port. Fwd Path Trace: The path trace identifier transmitted in the J1 byte. Enter an alphanumeric character string. 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 options: Unequipped(00) Eqp-Nonspecific(01) (default): Equipped - Nonspecific Payload VT-Structured(02): VT-structured STS-1 SPE Locked VT(03): Locked virtual tributary (VT) mode DS3 Async(04): Asynchronous mapping for E3 or DS3. (Planned for future release.) DS4NA Async(12): Asynchronous mapping for DS4NA or E4. (Planned for future release.) ATM Map(13): Mapping for ATM DQDB Map(14): Mapping for DQDB FDDI Async(15): Asynchronous mapping for FDDI HDLC-PPP(16): HDLC-Over-SONET mapping X.86(18) GFB (1B): Generic Framing Procedure Frame format (ITU-T G.7041) POS No-Scramble (CF) Page 6-22 Turin Networks Release TN4.0.x

Chapter 2 SONET Services Configure Advanced Parameters (Alphabetic Order) Test Signal (FE): O.181 Test Signal (TSS1 to TSS3) mapping Load Balance Most-Fill (read-only): If there are two paths of equal cost, and Link1 and Link2 are the first different links between the paths, Most-Fill will use the link that is most filled between the two links. This reduces bandwidth fragmentation among links.. Max Hop Count (end-to-end services only): Displays the maximum number of hops to the timing source. 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: 1E-4: Value equals 1 x 10-4 1E-5: Value equals 1 x 10-5 1E-6 (default): Value equals 1 x 10-6 1E-7: Value equals 1 x 10-7 1E-8: Value equals 1 x 10-8 1E-9: Value equals 1 x 10-9 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: 1E-3 (default): Value equals 1 x 10-3 1E-4: Value equals 1 x 10-4 1E-5: Value equals 1 x 10-5 Monitor RTD: Select to enable the delay measurement function for this service; default is disable (cleared checkbox). Path Mapping: Maps the VC-3 payload onto a transport path. This parameter determines how to monitor alarms and performance of the service through the intermediate nodes in the network. STS: Maps the payload into an STS path AU-4/LOVC (default): Maps the payload into an AU-4 low order virtual container AU-3/HOVC: Maps the payload into an AU-3 high order path virtual container VCRedline Circuit: Use this attribute to mark a service with Do not Deactivate. A redline circuit prevents accidental deactivation of an important service. You must first reset the redline attribute, then deactivate the service. Select one of the following options: Yes: Service is a redline circuit and cannot be deactivated No (default): Service is not a redline circuit and can be deactivated Rev Path Format: This port receives a path trace identifier in the J1 byte of the SONET/SDH frame so that the path transmitter can verify its continued connection. Select one of the following options: 16 bytes (default): Select if the receiver is a SONET port 64 bytes: Select if the receiver is another SONET port Rev Path Trace: The expected path trace identifier transmitted in the J1 byte. Enter an alphanumeric character string. Not used for unidirectional connections. Release TN4.0.x Turin Networks Page 6-23

TransNav GUI Guide, Section 6: Services Configure Advanced Parameters (Alphabetic Order) Rev Signal Label: The path signal label (C2 byte in the STS path overhead) in the reverse direction of the LSP. Not used for unidirectional connections. Select one of the following values: Unequipped(00) Eqp-Nonspecific(01) (default): Equipped - Nonspecific Payload VT-Structured(02): VT-structured STS-1 SPE Locked VT(03): Locked virtual tributary (VT) mode DS3 Async(04): Asynchronous mapping for DS3 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-PPP(16): HDLC-Over-SONET mapping X.86(18) GFB (1B) POS No-Scramble (CF) Test Signal (FE): O.181 Test Signal (TSS1 to TSS3) mapping Setup Retry Count (end-to-end services only): The number of times the system retries a service activation request before declaring that activation failed. Select 0 to 30; default is 3. SourceDS1Mapping: For optical transmux services, select this parameter if the source path carries a channelized DS3 payload. SourceDS3Mapping: For optical transmux services, select this parameter if the source STS carries a channelized DS3 payload. SourceE1Mapping: For optical transmux services, select this parameter if the source path carries a channelized DS3 payload. Source PM Template: Select from the defined performance monitoring templates. The system default for performance monitoring thresholds is disabled for all parameters. Use the performance monitoring templates to set default thresholds or to customize threshold values. See Section 8 Maintenance and Testing, Chapter 1 Performance Monitoring, page 8-1 for information on how to use performance monitoring templates. See the Node Operations and Maintenance Guide section documentation for details on performance monitoring parameters for optical ports. TMX Port: For optical transmux services, select the port you designated as the STS1TMX resource. Transparency: Specifies if this service is transparently transporting payloads and overhead of legacy equipment. This service must have a STS-12c, STS-48c, VC-4-4c, or VC-4-16c bandwidth. The Control Data parameter must be Disabled on the interface. Select ON or OFF. On: This service has a bandwidth of STS-48c and is transparently transporting services between legacy equipment Off (default): This service is not a transparency service Page 6-24 Turin Networks Release TN4.0.x

Chapter 2 SONET Services Configure the Path Through the Network for End-to-End Services Unidirectional: Select for a unidirectional connection (the traffic can only travel in one direction from source to destination). The default is unselected which means that the connection is bidirectional (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. Configure the Path Through the Network for End-to-End Services On the Create Service screen, choose the path through the network for the end-to-end service you are provisioning (Strict= ). Click the plus sign to add a row to the table. Click the minus sign to remove a row from the table. Figure 6-8 Add Hops to an End-to-End Service The endpoint table has the following columns: Description: Describes the endpoint. Displays one of the following: Source: Displays originating point of the service in the network. Pass-Through: Displays the node and the endpoint of an end-to-end service as it exits the pass-through node. Destination: Displays the terminating point of the service in the network. EndPoint: Displays the endpoints of the service in the following format: NodeID/slot#(cardType)/port#(portType)/sts#/vtg#/vt# Example: Node1/s11(OC192)/p1(OC192)/sts161/vtg1/vt1 To select the endpoints, see Choose Endpoints, page 6-16. Add: Click the plus sign in the row to add another hop to the service. Remove: Click the minus sign in the row to remove the hop from the service. Release TN4.0.x Turin Networks Page 6-25

TransNav GUI Guide, Section 6: Services Configure the Path Through the Network for End-to-End Services Page 6-26 Turin Networks Release TN4.0.x

SECTION 6SERVICES Chapter 3 SDH Services Introduction This chapter explains the provisioning parameters the following service types: SDH. Use this service to transport synchronous traffic through the network. Also, use this service as a regular cross-connect when creating a transport path hop-by-hop through the network. SDH-Endpoint. Use this service to create a termination point to multiplex low order traffic into the network. Also use this service to create a transport path hop-by-hop through the network. SDH-Tunnel. Use this service to create a transport path end-to-end through the network. See Traverse Provisioning Guide for guidelines and procedures to create or remove these services. This chapter includes the following topics: Create an SDH Service, page 6-28 Create Service Parameters, page 6-29 Choose an Endpoint, page 6-30 Configure Protection Parameters, page 6-35 Configure Advanced Parameters (Alphabetic Order), page 6-37 Release TN4.0.x Turin Networks Page 6-27

TransNav GUI Guide, Section 6: Services Create an SDH Service Create an SDH Service From the Service tab, select SDH, SDH-Endpoint, or SDH-Tunnel, and click Add. The Create Service tab displays. Figure 6-9 Add SDH Service 1 3 2 4 5 Figure 6-10 Create Service Tab On the Create Service tab, perform the following steps in order: 1. Enter the name and configure general parameters. For more information, see Create Service Parameters, page 6-29. 2. Select the endpoints of the service. For hop-by-hop services, see Choose an Endpoint, page 6-30. For end-to-end services, see Chapter 2 SONET Services, Configure Advanced Parameters (Alphabetic Order), page 6-25. 3. Set the protection parameters of the service. See Configure Protection Parameters, page 6-35. 4. Configure other characteristics of the connection. For more information, see Configure Advanced Parameters (Alphabetic Order), page 6-37. 5. Click Apply. Page 6-28 Turin Networks Release TN4.0.x

Chapter 3 SDH Services Create Service Parameters Create Service Parameters Name: Enter a unique name for the service. Use alphanumeric characters and spaces only. Do not use any other punctuation or special characters. Description: Enter the description of the service. Use alphanumeric characters and spaces only. Do not use any other punctuation or special characters. Bandwidth: Select the total bandwidth for the service: For SDH services select one of the following bandwidths: VC-11 VC-12 VC-3 (default) VC-4 VC-4-4c (for STM-4 and greater interfaces only) VC-4-16c (for STM-16 and greater interfaces only) For SDH-Endpoint or SDH-Tunnel services, select one of the following bandwidths: VC-3 (Grooming) (default). This path is VC-3 bandwidth and carries low order payloads. VC-4 (Grooming). This path is VC-4 bandwidth and carries low order payloads. VC-4 (VC-3). This path is VC-4 bandwidth and carries VC-3 payloads only. Strict: For end-to-end services only. Select to explicitly define the service route through all nodes in the network. See Chapter 2 SONET Services, Configure Advanced Parameters (Alphabetic Order), page 6-25. Customer: Select a customer name from the drop-down list box. Add Customer: Click to add a Customer. For details, see Adding Customer Information, page 2-31. Endpoint Table. Select the endpoints of the service. For hop-by-hop services, see Choose an Endpoint, page 6-30. For end-to-end services, see Endpoints for VC11 and VC12 Services, page 6-32. Protection. This field is context sensitive depending on the selected endpoints. Configure the protection parameters AFTER you have selected the endpoints of the service. See Configure Protection Parameters, page 6-35. Command buttons are as follows: Advanced: Configure the characteristics of the connection. For more information, see Configure Advanced Parameters (Alphabetic Order), page 6-37. Apply: Apply changes and return to the service list on the Service tab. Cancel: Cancel information, close the screen, and return to the Service tab. Release TN4.0.x Turin Networks Page 6-29

TransNav GUI Guide, Section 6: Services Choose an Endpoint Choose an Endpoint In the Create Service tab, click a row in the EndPoint column of the endpoint table. Figure 6-11 Selecting Sources and Destinations for SDH Services The Choose an EndPoint dialog box appears in the upper left corner of the screen. From the navigation tree, click the node, card, and depending on the card type the port and path. See Endpoints for VC3 and VC4 Services, page 6-31 for valid high order sources and destinations. See Endpoints for VC11 and VC12 Services, page 6-32 for valid low order sources and destinations. Command buttons are as follows: Done: Click this button after you have selected the correct endpoint for the service. Cancel: Cancel information, close the dialog box, and return to the Create Service tab. Page 6-30 Turin Networks Release TN4.0.x

Chapter 3 SDH Services Endpoints for VC3 and VC4 Services Endpoints for VC3 and VC4 Services The following table lists valid sources and destinations for SDH services. Your network may require creating multiple services at multiple nodes. The Traverse system supports multicast SDH connections for 1+1 path-protected and drop-and-continue services. Table 6-7 Endpoints for VC3 and VC4 Services Sources Destinations Port Type Mapping Port Type Mapping STM-N 1 node/slot/port/aug1/ node/slot/port/aug1/tug3/vc3 node/slot/port/aug1/vc3 STM-N (HO) STM-N (LO) E3CC all ports E1 card node/slot/port/aug1/ node/slot/port/aug1/tug3/vc3 node/slot/port/aug1/vc3 node/slot/port node/slot OC-N EC3 EC1 DS3CC DS3TMX all ports DS1 card node/slot/port/sts node/slot/port/sts node/slot/port node/slot/port node/slot/port node/slot EC3 node/slot/port/sts STM-N (HO) STM-N (LO) E3CC all ports E1 card OC-N EC3 EC1 DS3CC DS3TMX all ports DS1 card E3CC node/slot/port STM-N (HO) STM-N (LO) E3CC OC-N EC3 EC1 DS3CC node/slot/port/aug1/ node/slot/port/aug1/tug3/vc3 node/slot/port/aug1/vc3 node/slot/port node/slot node/slot/port/sts node/slot/port/sts node/slot/port node/slot/port node/slot/port node/slot node/slot/port/aug1/tug3/vc3 node/slot/port/aug1/vc3 node/slot/port node/slot/port/sts node/slot/port/sts node/slot/port node/slot/port All ports on an E1 card node/slot STM-N (HO) STM-N (LO) node/slot/port/aug1/tug3/vc3 node/slot/port/aug1/vc3 OC-N EC3 node/slot/port/sts node/slot/port/sts Ethernet card for EOS node/slot (Ethernet card)/aug1 Any Ethernet card on a different node node/slot (Ethernet card)/aug1 Release TN4.0.x Turin Networks Page 6-31

TransNav GUI Guide, Section 6: Services Endpoints for VC11 and VC12 Services 1 For SDH services between STM-64 ports, the source AUG number and the destination AUG number must in the same range when the range is between 1 and 32, or between 33 and 64. For example, if the source AUG is AUG number 12, the destination AUG must be between AUG number 1 and 32; if the source AUG is AUG number 51, the destination AUG must be between AUG number 33 and 64. Endpoints for VC11 and VC12 Services The following table lists valid sources and destinations for VC11 and VC12 services. Your network may require creating multiple services at multiple nodes. There must be a VT/TU 5G switch card or a card with an integrated VTX/VCX present in the shelf to create these services. Table 6-8 Endpoints for VT11 and VC12 Services Sources Destinations Port Type Mapping Port Type Mapping STM-N 1 node/slot/port/aug1/tug3/tug2/lovc 2 STM (HO) 1 node/slot/port/aug1/vc3/tug2/lovc 2 STM (LO) 1 E1 OC-N EC3 EC1 DS3TMX 3 DS1 EC3 node/slot/port/aug1/tug3/tug2/lovc 4 STM (HO) 1 node/slot/port/aug1/vc3/tug2/lovc 2 STM (LO) 1 E1 OC-N EC3 EC1 DS3CC DS1 DS3TMX 3 node/slot/port/subport STM (HO) 1 STM (LO) 1 E1 OC-N EC3 EC1 DS3TMX 3 DS1 node/slot/port/aug1/tug3/tug2/lo vc 2 node/slot/port/aug1/vc3/tug2/lo vc c node/slot/port node/slot/port/sts/vtg/vt node/slot/port/sts-1/vtg/vt node/slot/port/sts-1/vtg/vt node/slot/port/subport node/slot/port node/slot/port/aug1/tug3/tug2/lo vc 2 node/slot/port/aug1/vc3/tug2/lo vc c node/slot/port node/slot/port/sts/vtg/vt node/slot/port/sts-1/vtg/vt node/slot/port/sts-1/vtg/vt node/slot/port node/slot/port node/slot/port/aug1/tug3/tug2/lo vc 2 node/slot/port/aug1/vc3/tug2/lo vc 1 node/slot/port node/slot/port/sts/vtg/vt node/slot/port/sts/vtg/vt node/slot/port/sts-1/vtg/vt node/slot/port/subport node/slot/port Page 6-32 Turin Networks Release TN4.0.x

Chapter 3 SDH Services Endpoints for VC11 and VC12 Services Table 6-8 Endpoints for VT11 and VC12 Services (continued) Sources Destinations Port Type Mapping Port Type Mapping E1 node/slot/port STM (HO) 1 STM (LO) 1 E1 OC-N EC3 EC1 DS3TMX 3 DS1 node/slot/port/aug1/tug3/tug2/lo vc 2 node/slot/port/aug1/vc3/tug2/lo vc 2 node/slot/port node/slot/port/sts/vtg/vt node/slot/port/sts/vtg/vt node/slot/port/sts-1/vtg/vt node/slot/port/subport node/slot/port DS1 node/slot/port STM node/slot/port/aug1/tug3/tug2/lo vc 2 node/slot/port/aug1/vc3/tug2/lo vc 2 1 There must be an SDH-Endpoint or SDH-Tunnel service already with a Bandwidth of VC (Grooming) configured on the port. 2 lo vc is VC11 or VC12. 3 Port is E1-mapped (DS3 Mapping parameter is E1). 4 lo vc is VC11 or VC12. Release TN4.0.x Turin Networks Page 6-33

TransNav GUI Guide, Section 6: Services Starting AUG1 Numbers for VC-3 Services Starting AUG1 Numbers for VC-3 Services The starting AUG1 number for VC-3 paths depends on the data rate of the interface Table 6-9 Starting AUG1 Numbers for VC-3 Paths Bandwidth Path STM-1 STM-4 STM-16 STM-16 VC-3 a-1 tug3-1/vc3 tug3-2/vc3 tug3-3/vc3 vc3-1 vc3-2 vc3-3 a-1 a-2 a-3 a-4 tug3-1/vc3 tug3-2/vc3 tug3-3/vc3 a-1, vc3-1 a-1, vc3-2 a-1, vc3-3 a-1 a-2 a-16 tug3-1/vc3 tug3-2/vc3 tug3-3/vc3 a-1, vc3-1 a-1, vc3-2 a-1, vc3-3 a-1 a-2 a-64 tug3-1/vc3 tug3-2/vc3 tug3-3/vc3 a-1, vc3-1 a-1, vc3-2 a-1, vc3-3 Starting AUG1 Numbers for VC-4 Services Table 6-10 Starting AUG1 Numbers for VC-4 Paths Bandwidth Path STM-1 STM-4 STM-16 STM-16 VC-4 a-1 a-1, a-2, a-3, a-4 a-1, a-2, a-3,..., a-16 a-1, a-2, a-3,..., a-64 VC-4-4c a-1 a-1, a-5, a-9, a-13 a-1, a-5, a-9,...,a-61 VC-4-16c a-1 a-1, a-17, a-33, a-49 Page 6-34 Turin Networks Release TN4.0.x

Chapter 3 SDH Services Configure Protection Parameters Configure Protection Parameters On the Create Service screen, click the Protection field to display the Protection dialog box. Figure 6-12 Protection Dialog Box Select a Protection Group Type from the drop-down list. In the Protection Group Type parameter, select one of the following options: Unprotected (default): Use for services that are unprotected, 1+1 APS protected, protected with an equipment protection group, or in a 1+1 Path Protection group. Any: The system finds the best effort of protection through the network. There may be some spans of unprotected links, but the system creates the service. Full: The system only creates the service if there is full protection on every transport link in the network. 1+1 Path Protected: Select if this service is protected by another service (two services model). UPSR Ingress: Select if the service is a VT1.5 or a LO VC service and is creating a bidirectional path across two interconnected UPSRs or SNCP rings. After selecting the protection group type, click one of the tabs to configure the applicable parameters: General: WTR (Wait To Restore) Time: This parameter is configurable only if the checkbox for the Revertive parameter 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. Enter a value between 1 and 60 minutes; default is 5 minutes. Revertive: Specifies if the system switches traffic back to the original port or path once the failure condition no longer exists. Release TN4.0.x Turin Networks Page 6-35

TransNav GUI Guide, Section 6: Services Configure Protection Parameters Select the checkbox to switch traffic back to the original port or path once the failure condition no longer exists. Clear the checkbox for the Protect link or path to continue to carry traffic once the failure condition no longer exists. SNCP/UPSR parameters: Endpoint (read-only): Displays the endpoints of the service if it is on an UPSR or SNCP protected ring. Ring Id (read-only): Displays the ring ID number if this service is on a UPSR or SNCP ring. MSSP/BLSR parameters: Source Node ID (services provisioned hop-by-hop only): Select the BLSR Node ID where the traffic on this path enters the ring. Destination Node ID (services provisioned hop-by-hop only): Select the BLSR Node ID where the traffic on this path exits the ring. 1+1 Path Protection: HoldOffTimer: Applies only if there is also a 1+1 APS protection group. Allows line protection to switch first before the path switches. If the line switches within the specified time period, the path does not switch. The hold-off timer starts when path protection detects a path failure. The range is 0 to 1000 ms. The default is 0 which means path protection performs protection switching immediately. Page 6-36 Turin Networks Release TN4.0.x

Chapter 3 SDH Services Configure Advanced Parameters (Alphabetic Order) Configure Advanced Parameters (Alphabetic Order) On the Create Service tab, click the Advanced button. The Advanced Parameters dialog box displays. Figure 6-13 Advanced Parameters Dialog Box Important: The contents of this dialog box are context-sensitive and depend on the selected sources and destinations. The following parameter descriptions are listed in alphabetical order. Bridge and Roll (Hop-by-hop services only): Select to create a bridge service. Use this parameter to transfer traffic from one facility to another without affecting live traffic. See the Traverse Provisioning Guide, Section 5 Creating Service Applications, Chapter 2 Bridging and Rolling Services, page 5-13 for detailed procedures on bridging and rolling services. DestDS1Mapping: For optical transmux services, select this parameter if the destination path carries a channelized DS3 payload. DestDS3Mapping: For optical transmux services, select this parameter if the destination STS carries a channelized DS3 payload. DestE1Mapping: For optical transmux services, select this parameter if the destination path carries a channelized DS3 payload. Dest PM Template: Select from the defined performance monitoring templates. The system default for performance monitoring thresholds is disabled for all parameters. Use the performance monitoring templates to set default thresholds or to customize threshold values. See Section 8 Maintenance and Testing, Chapter 1 Performance Monitoring, page 8-1 for information on how to use performance monitoring templates. Expected RTD: Enter the expected round trip delay measurement, in milliseconds, for this service. Values are 0 to 1000 milliseconds; default is 300ms. Failure Retry Count (for end-to-end services only): The number of times the system tries to reestablish the service before declaring it failed. Select 0 to 30; default is 3. Release TN4.0.x Turin Networks Page 6-37

TransNav GUI Guide, Section 6: Services Configure Advanced Parameters (Alphabetic Order) Fwd Path Format: This port transmits a path trace identifier in the J1 byte of the SONET/SDH frame so that the path receiver can verify its continued connection. The values are: 16 bytes (default): Select if the receiver is an SDH port. 64 bytes: Select if the receiver is another SONET port. Fwd Path Trace: The path trace identifier transmitted in the J1 byte. Enter an alphanumeric character string. 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 options: Unequipped(00) Eqp-Nonspecific(01) (default): Equipped - Nonspecific Payload VT-Structured(02): VT-structured STS-1 SPE Locked VT(03): Locked virtual tributary (VT) mode DS3 Async(04): Asynchronous mapping for E3 or DS3. (Planned for future release.) DS4NA Async(12): Asynchronous mapping for DS4NA or E4. (Planned for future release.) ATM Map(13): Mapping for ATM DQDB Map(14): Mapping for DQDB FDDI Async(15): Asynchronous mapping for FDDI HDLC-PPP(16): HDLC-Over-SONET mapping X.86(18) GFB (1B): Generic Framing Procedure Frame format (ITU-T G.7041) POS No-Scramble (CF) Test Signal (FE): O.181 Test Signal (TSS1 to TSS3) mapping Load Balance Most-Fill (read-only): If there are two paths of equal cost, and Link1 and Link2 are the first different links between the paths, Most-Fill will use the link that is most filled between the two links. This reduces bandwidth fragmentation among links.. Max Hop Count (end-to-end services only): Displays the maximum number of hops to the timing source. 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: 1E-4: Value equals 1 x 10-4 1E-5: Value equals 1 x 10-5 1E-6 (default): Value equals 1 x 10-6 1E-7: Value equals 1 x 10-7 1E-8: Value equals 1 x 10-8 1E-9: Value equals 1 x 10-9 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 Page 6-38 Turin Networks Release TN4.0.x

Chapter 3 SDH Services Configure Advanced Parameters (Alphabetic Order) system raises a signal failed bit error rate (BERSF-V) alarm. Select one of the following values: 1E-3 (default): Value equals 1 x 10-3 1E-4: Value equals 1 x 10-4 1E-5: Value equals 1 x 10-5 Monitor RTD: Select to enable the delay measurement function for this service; default is disable (cleared checkbox). Path Mapping: Maps the VC-3 payload onto a transport path. This parameter determines how to monitor alarms and performance of the service through the intermediate nodes in the network. STS: Maps the payload into an STS path AU-4/LOVC (default): Maps the payload into an AU-4 low order virtual container AU-3/HOVC: Maps the payload into an AU-3 high order path virtual container VCRedline Circuit: Use this attribute to mark a service with Do not Deactivate. A redline circuit prevents accidental deactivation of an important service. You must first reset the redline attribute, then deactivate the service. Select one of the following options: Yes: Service is a redline circuit and cannot be deactivated No (default): Service is not a redline circuit and can be deactivated Rev Path Format: This port receives a path trace identifier in the J1 byte of the SONET/SDH frame so that the path transmitter can verify its continued connection. Select one of the following options: 16 bytes (default): Select if the receiver is a SONET port 64 bytes: Select if the receiver is another SONET port Rev Path Trace: The expected path trace identifier transmitted in the J1 byte. Enter an alphanumeric character string. Not used for unidirectional connections. Rev Signal Label: The path signal label (C2 byte in the STS path overhead) in the reverse direction of the LSP. Not used for unidirectional connections. Select one of the following values: Unequipped(00) Eqp-Nonspecific(01) (default): Equipped - Nonspecific Payload VT-Structured(02): VT-structured STS-1 SPE Locked VT(03): Locked virtual tributary (VT) mode DS3 Async(04): Asynchronous mapping for DS3 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-PPP(16): HDLC-Over-SONET mapping X.86(18) GFB (1B) POS No-Scramble (CF) Release TN4.0.x Turin Networks Page 6-39

TransNav GUI Guide, Section 6: Services Configure Advanced Parameters (Alphabetic Order) Test Signal (FE): O.181 Test Signal (TSS1 to TSS3) mapping Setup Retry Count (end-to-end services only): The number of times the system retries a service activation request before declaring that activation failed. Select 0 to 30; default is 3. SourceDS1Mapping: For optical transmux services, select this parameter if the source path carries a channelized DS3 payload. SourceDS3Mapping: For optical transmux services, select this parameter if the source STS carries a channelized DS3 payload. SourceE1Mapping: For optical transmux services, select this parameter if the source path carries a channelized DS3 payload. Source PM Template: Select from the defined performance monitoring templates. The system default for performance monitoring thresholds is disabled for all parameters. Use the performance monitoring templates to set default thresholds or to customize threshold values. See Section 8 Maintenance and Testing, Chapter 1 Performance Monitoring, page 8-1 for information on how to use performance monitoring templates. See the Node Operations and Maintenance Guide section documentation for details on performance monitoring parameters for optical ports. TMX Port: For optical transmux services, select the port you designated as the STS1TMX resource. Transparency: Specifies if this service is transparently transporting payloads and overhead of legacy equipment. This service must have a STS-12c, STS-48c, VC-4-4c, or VC-4-16c bandwidth. The Control Data parameter must be Disabled on the interface. Select ON or OFF. On: This service has a bandwidth of STS-48c and is transparently transporting services between legacy equipment Off (default): This service is not a transparency service Unidirectional: Select for a unidirectional connection (the traffic can only travel in one direction from source to destination). The default is unselected which means that the connection is bidirectional (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. Page 6-40 Turin Networks Release TN4.0.x

SECTION 6SERVICES Chapter 4 Ethernet Services Introduction This chapter explains the provisioning parameters for all Ethernet service types. Important: See one of the following references for guidelines, detailed information, and procedures on how to create Ethernet services: Traverse Provisioning Guide, Section 7 Configuring Ethernet TraverseEdge 100 User Guide, Section 6 Creating Ethernet Services This chapter contains the following topics: Ethernet Cards, page 6-41 Ethernet Service Parameters, page 6-42 Advanced Parameters Ethernet Service Ports (Traverse only), page 6-43 Advanced Parameters Ethernet Service, page 6-44 Guaranteed Data Rate and Ethernet Services, page 6-45 Bandwidth Profiles, page 6-46 Bandwidth Profile Dialog Box, page 6-47 Policers, page 6-48 Classifiers, page 6-49 TE-100 Classifiers, page 6-50 For information about pre-release TR2.1 Legacy Ethernet modules, refer to the Release 2.0 documentation on the Turin website at www.turinnetworks.com. User registration is required. To register for the Turin Infocenter, contact your sales account team. Ethernet Cards Important: The information in this section strictly pertains to the following Traverse Next Generation Ethernet (NGE), Next Generation Ethernet Plus (NGE Plus), 10GbE (1-port 10GbE), and GbE-10 (10-port GbE) modules: NGE Modules NGE Plus Modules GE Modules GBE4-FE16-TX GBE4-FE16-TX / CEP 10GbE (1-port 10GbE) GbE-10 (10-port GbE) GBE2T-GBE2F-FE16-TX GBE2T-GBE2F-FE16-TX / CEP This information also pertains to the Ethernet parameters on the TE-100 shelf. Release TN4.0.x Turin Networks Page 6-41

TransNav GUI Guide, Section 6: Services Create an Ethernet Service Create an Ethernet Service From the Service tab, select Ethernet and click Add. Figure 6-14 Add Ethernet Service Ethernet Service Parameters On the Create Service tab, configure the parameters about this service. Figure 6-15 Create Ethernet Service Screen Name: Enter a unique name for the service. Use alphanumeric characters and spaces only. Do not use any other punctuation or special characters. Description: Enter the description of the service. Use alphanumeric characters and spaces only. Do not use any other punctuation or special characters. Customer: Select a customer name from the drop-down list box. In the Type parameter, select the type of Ethernet service: Line Bridge AggrBridge (aggregate bridge) Each Ethernet card can support 18 active Bridge and Aggregate Bridge services simultaneously. Each 10GbE and GbE-10 card can support 256 active Bridge and Aggregate Bridge services simultaneously. In the Endpoint table, select the correct endpoints for this service. The endpoints must be on the same Ethernet card. If required on a Traverse node, assign a configured classifier or a policer to each service port. Classifier: Select a classifier for this service port. See Classifiers, page 6-49 for more information on classifiers. Policer: Select a policer for this service port. See Policers, page 6-48 for more information on policers. Page 6-42 Turin Networks Release TN4.0.x

Chapter 4 Ethernet Services Advanced Parameters Ethernet Service Ports (Traverse only) Advanced Parameters Ethernet Service Ports (Traverse only) Configure the Advanced Parameters of each service port. These parameters override the configuration of the Advanced parameters for the Ethernet service. Click the Advanced column in the Endpoint table for each service port. Figure 6-16 Advanced Parameters Ethernet Service Ports Default Priority Bit: Used in the classification of packets for packets that arrive untagged and therefore do not have a priority field. Set the default priority for untagged packets arriving on this port that belong to this service. Enter a value from 0 to 7; default is 0. Marking Bit (Traverse only): If this port is Service-tagged, specify the system behavior regarding the priority field on packets being transmitted out this port. The valid values are: Mark (default): The system sets the priority field in the VLAN tag as a result of the classifying and policing functions. Copy: The system copies the priority value in the customer VLAN tag to the priority field in the service provider VLAN tag if the transmit. If the packet was untagged, the system uses the value specified in the Default Priority Bit parameter. VLAN Type (Traverse only): Enter the VLAN ID for this service. Valid values are: Untagged/PrtyTagged Tagged. This port uses the Override VLAN ID to determine if packets arriving on this port belong to this service. Select Tagged, then configure the Override VLAN ID parameter. ServiceVLANID (default). The system uses the Service VLAN ID to determine the VLAN ID for this service. Override VLAN ID (Traverse only): Enter the alternate VLAN ID for this service. MAC Addresses (Traverse only): Use this parameter to manually enter static MAC addresses for this service on this port. While the service is activated, these addresses are present in the MAC address table as if they had been learned on this port. These addresses do not age out of the table nor will they be re-learned on other ports in this service. Release TN4.0.x Turin Networks Page 6-43

TransNav GUI Guide, Section 6: Services Advanced Parameters Ethernet Service Advanced Parameters Ethernet Service Configure the Advanced parameters of the Ethernet service. Click the Advanced button to display the Advanced Parameters dialog box. Figure 6-17 Advanced Parameter Ethernet Line Service Configure the following Ethernet service parameters: Service VLAN ID: Enter a VLAN ID (an integer between 1 and 4093) for this service. If all ports in this service are tagged Port-based, the value in this parameter is ignored, including the default of 0. For packets arriving on Customer-tagged ports in this service, the Service VLAN ID must match the customer VLAN ID. A value of 0 means that untagged and priority-tagged packets are part of this service. For packets arriving on Service-tagged ports in this service, the Service VLAN ID must match the service provider VLAN ID for the provider network. Untagged or priority-tagged packets that arrive on Service-tagged ports are dropped. Note: VLANs marked Customer-tagged or Service-tagged represent separate service flows on the port; counts for each type are per-vlan. Conversely, port-based packets are part of the service flow and cannot be collected separately per-vlan. Link Integrity (for Ethernet line services only): Monitors the status of Ethernet ports or LAGs, and the associated transport connection. You configure link integrity on two line services that use exactly one Ethernet port and one EOS port on the ingress and egress nodes of the network. Neither the Ethernet port nor the EOS port can be in any other activated service. Disable (default): Indicates the Link Integrity feature is not used on this service. Enabled: Select this to enable the Link Integrity feature on this service whenever the service is activated. Service Port PM: Select the Service Port PM to be associated with this Ethernet service. Default is default. Service Port PMs for 1+1 Flow Protection Groups include counts for VLAN flows selected for forwarding. Allowed Port Tagging Type (TE-100 Bridge and Aggregate Bridge services only): Select the correct combination of port Tagging Type parameters from the TraverseEdge 100 User Guide, Section 6 Creating Ethernet Services, Chapter 6 Ethernet Services, Supported Combinations of VLAN Tagging Types and Ethernet Services, page 6-66. You must know the Tagging of all the ports in the service. Service VID (TE-100 only): Enter a VLAN ID between 1 and 3999 for Ethernet packets transmitted to Service-tagged ports in this service. This VLAN ID must be unique on this TE-100 system. See the TraverseEdge 100 User Guide Section 6 Creating Ethernet Services, Chapter 6 Ethernet Services, Configurable VLAN IDs, page 6-68 for valid VLAN IDs. Page 6-44 Turin Networks Release TN4.0.x

Chapter 4 Ethernet Services Guaranteed Data Rate and Ethernet Services Customer VID (TE-100 only): Enter a VLAN ID between 1 and 3999 for Ethernet packets transmitted to Customer-tagged ports in this service. This VLAN ID must be unique on the Ethernet ports in this service. If the Allowed Port Tagging Type is UT-CT, this VLAN ID must be unique on this TE-100 system. See the TraverseEdge 100 User Guide Section 6 Creating Ethernet Services, Chapter 6 Ethernet Services, Configurable VLAN IDs, page 6-68 for valid VLAN IDs. Guaranteed Data Rate and Ethernet Services The Guaranteed Data Rate is the total rate of Ethernet data including both the data packets themselves and the per-packet Ethernet line overhead: 8-byte preamble, 12-byte inter-packet gap. Note: For the 10GbE and GbE-10 modules, only the STS-1/VC-3 and STS-3c/VC-4 ports are currently supported. 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 (tunnel, endpoints, or VC-Bundle) or the backplane connection. The table below shows the maximum capacities. These are the limits used by Connection Admission Control (CAC) that, when exceeded, cause the system to reject a new service. Table 6-11 CAC Limits for Sum of All Guaranteed Data Rates Sharing a Port Port Type CAC limits in Mbps VT-1.5 or VC11 1.600 VT-2 or VC12 2.176 STS-1 or STS-1 48.384 STS-3c or STS-3c 149.760 For example, if three P2PS services share a transport path with a Bandwidth of STS-3c, the sum of the Guaranteed Data Rates for these three services must not exceed 149 Mbps. If those three P2PS services share a transport path with a Bandwidth of STS-48c, the sum of the Guaranteed Data Rates for those three services must not exceed 1000 Mbps. In a VCAT group of N members, the payload capacity is N times the maximum numbers in the above table. For example, a VCAT group of 8 VT-1.5s can carry 8 times 1.600 Mbps (12.8 Mpbs) of GFP-encapsulated Ethernet frames. Every Ethernet frame that goes over SONET has 8 bytes of GFP encapsulation. If 3000 frames per second is being sent and each frame is 256 bytes, then 6.336 Mbps is being sent. This is 3000 x (256 bytes + 8 byte GFP) x 8 bits/byte = 6.336 Mpbs. A VCG of four VT-1.5s is required to carry the traffic (6.336 Mpbs divided by 1.600 equals 3.96 VT1.5s). Release TN4.0.x Turin Networks Page 6-45

TransNav GUI Guide, Section 6: Services Bandwidth Profiles Bandwidth Profiles From the Admin menu, click Bandwidth Profiles. The Bandwidth Profiles dialog box displays. Figure 6-18 Bandwidth Profiles Dialog Box The columns in the Bandwidth Profiles dialog box are: Name: The name of the profile. Type: Indicates bandwidth_profile as the type of profile. Sync Status: Indicates if the profile is synchronized with the management server. Command buttons are as follows: Add: Select to add a new profile to the system. The Bandwidth Profile Configuration dialog box displays. See Bandwidth Profile Dialog Box, page 6-47. Copy: Select to copy an existing profile and edit it to create a new profile. Properties: Select to show the configuration of the selected profile. Sync: Synchronize the selected profile. Delete: Delete the selected profile. Done: Save the changes, close the dialog box, and return to the main screen. Page 6-46 Turin Networks Release TN4.0.x

Chapter 4 Ethernet Services Bandwidth Profile Dialog Box Bandwidth Profile Dialog Box Bandwidth profiles are used in conjunction with the policing function. Policers are created from a combination of bandwidth profiles. In the Bandwidth Profiles dialog box, click Add to add a new bandwidth profile. Figure 6-19 Bandwidth Profiles Configuration The Bandwidth Profiles Configuration dialog box displays. Enter the following parameters to create a new bandwidth profile: Name: Enter a unique name for the classifier in this field. Use alphanumeric characters and spaces only. Do not use any other punctuation or special characters. CIR (Mbps): Committed information rate. Enter a value provided in the following table; the default is 1000 Mbps. Provisionable in increments of 1 Mbps. CBS (Kbps): Committed burst size. Enter a value provided in the following table. The default (256 KB) must be changed. Provisionable in increments of 1 KB. Enter a value as determined by the values provided in the following table; the default is 1000 Mbps. Provisionable in increments of 1 Mbps. PIR (Mbps): Peak information rate. Enter a value provided in the following table; the default is 1000 Mbps. Provisionable in increments of 1 Mbps. The PIR must not be lower than the CIR. PBS (Kbps): Peak burst size. Enter a value provided in the following table. The default (256 KB) must be changed. Provisionable in increments of 1 KB. If you make changes to the default values, click OK. A message appears asking if you would like to synchronize the template. Click Yes. The maximum Committed and Peak Burst Size parameters of the Ethernet bandwidth profile depend on the associated Committed or Peak Information Rates according to the following table: Table 6-12. Maximum Bandwidth Burst Size Parameters Information Rate (IR in Mbps) Maximum Burst Size (MBS in Kb) 1 to <4 112 * IR 4 to <8 225 * (IR/4) 8 to <16 225 * (IR/8) 16 to <32 225 * (IR/16) Release TN4.0.x Turin Networks Page 6-47

TransNav GUI Guide, Section 6: Services Policers Table 6-12. Maximum Bandwidth Burst Size Parameters (continued) Information Rate (IR in Mbps) Maximum Burst Size (MBS in Kb) 32 to <64 225 * (IR/32) 64 to <128 225 * (IR/64) IR > 128 225 * (IR/128) The maximum Peak Burst Size of the NGE cards is 256 Kb. For a CIR/PIR of 1000, the maximum CBS/PBS the NGE can implement is 1759. The maximum Peak Burst Size of the 10 GbE and GbE-10 cards is unlimited. Up to 16000 Kb can be supported at all rates. If you provision a burst size (committed or peak) that is less than or equal to the calculated maximum burst size for your given information rate, the system uses the provisioned burst size. However, if you provision a burst size that is larger than the calculated maximum burst size for the given information rate, the system uses the calculated maximum burst size. Examples are as follows: If a CIR of 50 and a CBS of 256 is provisioned, the calculated maximum CBS for a CIR of 50 is 351. The provisioned value is less than 351, so the system implements the provisioned value of 256. If a PIR of 50 and a PBS of 768 are provisioned, the calculated maximum PBS for a PIR of 50 is 351. The provisioned value is greater than the calculated value, so the system ignores the provisioned value and implements the calculated value of 351. Command buttons are as follows: Synchronize: Select to synchronize the profile with the management server. OK: Select to save the configuration and close the dialog box. Cancel: Select to cancel any changes, close the dialog box, and return to the Bandwidth Profile list. Policers There must be bandwidth profiles created before you can create policers on this node. In Shelf View, click the Ethernet tab, then click the Policer subtab. Click Add to display the Create Policer tab. Enter the following parameters: Figure 6-20 Create Policer Tab Page 6-48 Turin Networks Release TN4.0.x

Chapter 4 Ethernet Services Classifiers ID: Indicates the policer ID. Enter an integer between 1 and 512. Card: Select the card in the shelf on which to configure the policer. In the Bandwidth Profile column, select the correct bandwidth profile for the corresponding class of service (queue). The system will query the card and display the current system values for the configured Class of Service of the bandwidth profile selected. Figure 6-21 Current Class of Service Values Displayed Command buttons are as follows: Apply: Select to save the changes. Cancel: Select to cancel the changes and return to the previous screen. Classifiers From the Admin menu, click Classifiers. The Classifiers dialog box appears. Click Add to add a new classifier to the classifier list. The Classifier Configuration dialog box displays. Figure 6-22 Classifier Configuration Dialog Box Release TN4.0.x Turin Networks Page 6-49

TransNav GUI Guide, Section 6: Services TE-100 Classifiers Enter the following parameters: Name: Enter a unique name for the classifier in this field. Use alphanumeric characters and spaces only. Do not use any other punctuation or special characters. Configure the class of service (CoS) and initial drop precedence (IDP) for each priority level. Priority {0 1 2 3 4 5 6 7} CoS: 1 for Queue 1 2 for Queue 2 3 for Queue 3 4 for Queue 4 Priority {0 1 2 3 4 5 6 7} IDP: Green Yellow Command buttons are as follows: Synchronize: Select to synchronize the changes with the management server. OK: Select to save the configuration and close the dialog box. Cancel: Select to cancel any changes, close the dialog box, and return to the Classifiers dialog box. TE-100 Classifiers From the Admin menu, click TE100Classifiers. The TE100Classifiers dialog box appears. Click Add to add a new classifier to the classifier list. The TE100Classifier Configuration dialog box displays. Figure 6-23 TE100 Classifier Configuration Dialog Box Enter the following parameters: Name: Enter a unique name for the classifier in this field. Use alphanumeric characters and spaces only. Do not use any other punctuation or special characters. Configure the class of service (CoS) for each priority level. Priority {0 1 2 3 4 5 6 7} CoS: 1 for CoS1 2 for CoS2 3 for CoS3 Command buttons are as follows: Page 6-50 Turin Networks Release TN4.0.x

Chapter 4 Ethernet Services TE-100 Classifiers Synchronize: Select to synchronize the changes with the management server. OK: Select to save the configuration and close the dialog box. Cancel: Select to cancel any changes, close the dialog box, and return to the TE100Classifiers dialog box. Release TN4.0.x Turin Networks Page 6-51

TransNav GUI Guide, Section 6: Services TE-100 Classifiers Page 6-52 Turin Networks Release TN4.0.x

SECTION 6SERVICES Chapter 5 VC-Bundles 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 path signals, known as a virtual concatenation group (VCG). For example, in SDH standards, a VC-3-6v is a virtually concatenated path multiplexed onto six STS-1 paths. Its bandwidth is six times that of an STS-1. In SONET standards, an STS1-6c is a virtually concatenated path multiplexed onto six STS-1 paths. Its bandwidth is six times that of an STS-1. This mapping technique eliminates the rigid hierarchies of the common SONET/SDH 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 the provisioning parameters the VC-bundle service type: Create a VC-bundle, page 6-54 Configure VCB Parameters, page 6-55 Configure Advanced Parameters, page 6-55 Release TN4.0.x Turin Networks Page 6-53

TransNav GUI Guide, Section 6: Services Create a VC-bundle Create a VC-bundle From the Service tab, select VCB and click Add. Figure 6-24 Add VCB Service The Create Service tab for VC-bundle service displays. 1 2 3 4 Figure 6-25 Create VCB Services To create a VC bundle, follow these steps: 1. Configure the Name, Description, and Customer parameters. Use alphanumeric characters only. Do not use any other punctuation or special characters. 2. Click the first row in the EndPoint column to select an already-provisioned SONET service that originates on an Ethernet card. 3. Click the plus sign in the Add column to add another row to the Endpoint table. 4. Click the Advanced button to configure the VC bundle parameters. Page 6-54 Turin Networks Release TN4.0.x

Chapter 5 VC-Bundles Configure Advanced Parameters Configure VCB Parameters Configure Advanced Parameters The Create Service tab for a VCB service has the following parameters. Enter information in the following fields as required: Name: Indicates the name of the service entered in the General Information screen. Description: Indicates the description of the service entered in the General Information screen. Customer: Select a customer name from the drop-down list box. For details, see Adding Customer Information, page 2-31. Endpoint Table: Select the provisioned services (represented as Tunnels in the user interface) as members of the VC-bundle. You can only create a VC-bundle on a node where you have already configured services. Click the plus sign in the Add column to add another row (and Tunnel) to the VC-bundle. Click the minus sign in the Remove column to remove the row or Tunnel from the VC-bundle. From the Create Service tab on a VCB service, click the Advanced button in the bottom left-hand corner to display the Advanced Parameters dialog box. Figure 6-26 Advanced Parameters for VCB Service (Defaults) The Advanced Parameters dialog box is context sensitive. The following different parameters appear based on values in other fields: LCAS Enabled: Indicates if this node is using the LCAS protocol. Select the check box to allow the system to remove any failed members from this service and continue to operate using a reduced capacity. Disabled (default): If not selected, indicates the bundle is prevented from carrying any traffic if a member fails. Encapsulation Type: Select one of the following values: GFP for generic framing procedure encapsulation X.86 (default) for X.86 encapsulation Concatenation Type: Specifies the type of paths this bundle contains. The valid values are: Virtual: Select this value if the bundle is concatenating STS paths into non-standard concatenations. Standard (default): Select this value to change the Encapsulation Type from X.86 default on standard concatenated bandwidths (STS-3c, STS-12c, and STS-48c). Release TN4.0.x Turin Networks Page 6-55

TransNav GUI Guide, Section 6: Services Configure Advanced Parameters RSTP Enabled: Enables or disables RSTP for TLS services. Select to enable RSTP for TLS services Disabled (default). If not selected, RSTP for TLS services is disabled RSTP Port Priority: If necessary, set the priority of the RSTP port to become the root port. Values are 1 to 15; default is 8. A lower number means this RSTP port has highest priority to become a root port. RSTP Path Cost. If necessary, set the path cost of the RSTP port. Values are 1 to16; default is 1. A lower value means this port is more desirable to become a root port. Command buttons are as follows: Advanced: Select to configure characteristics of the VC-bundle service. Apply: Select to add the services selected in the Services list box to the bundle. Cancel: Cancel changes, close the screen, and return to the Service tab. Page 6-56 Turin Networks Release TN4.0.x

SECTION 6SERVICES Chapter 6 Service Groups Introduction Use Service Groups to create a number of SONET or SDH services at one time. This chapter explains the parameters for service groups. Important: See the Traverse Provisioning Guide, Section 7 Configuring Ethernet for guidelines, detailed information, and procedures on how to create service groups. This chapter contains the following topics: Create Service Group Tab, page 6-57 Service Group Tab, page 6-59 Edit Service Group Tab, page 6-59 Create Service Group Tab Click the Service Group tab, then click Add. The Create Service Group tab appears. Figure 6-27 Create Service Group Tab In the Create Service Group tab, enter the general information for this group of services: Name: Use alphanumeric characters only; no special characters are allowed. Description: Use alphanumeric characters only. Do not use any other punctuation or special characters. Select the bandwidth of the services from the Concat. Size field. STS-1 STS-3c HO-VC-3 Release TN4.0.x Turin Networks Page 6-57

TransNav GUI Guide, Section 6: Services Create Service Group Tab VC-4 Routing Policy. Determines the end-to-end path through the system. Select one of the following values: Co-route so the system finds the alternative path on the same fibers throughout the network. Diverse (Planned for future release.) Service Count. Specify the number of consecutive services you want to create in the system. This number depends on the value in the Concat. Size field. If the value is STS-1 or HO-VC3, enter a number between 1 and 48. If the value is STS-3c or VC-4, enter a number between 0 and 8; default is 0. Starting Endpoint 1 and Starting Endpoint 2. Select the source and destination endpoints of the service. The endpoints can only be for NGE, NGE Plus, and 10GE cards on separate nodes. NGE Modules NGE Plus Modules 10GE Modules GBE4-FE16-TX GBE4-FE16-TX / CEP 10GBE GBE2T-GBE2F-FE16-TX GBE2T-GBE2F-FE16-TX / CEP GBE-10 On the Create Service Groups tab, click Advanced to configure more parameters of the services. These parameters are propagated to each service that is created. Figure 6-28 Service Group Advanced Parameters Dialog Box For specific definitions of these parameters, see: Section 6 Services, Chapter 2 SONET Services, Configure Protection Parameters, page 6-21. Section 6 Services, Chapter 3 SDH Services, Configure Advanced Parameters (Alphabetic Order), page 6-37. Click Done to return to the Create Service Groups tab on the main screen. Page 6-58 Turin Networks Release TN4.0.x

Chapter 6 Service Groups Edit Service Group Tab Service Group Tab Click the Service Group tab to display the list of configured Service Groups. Figure 6-29 Service Group Tab Right-click on the service group. Select one of the following options: Synchronize: Select to synchronize the services to the management server and the nodes. Activate: Select to activate the service group to carry traffic. Deactivate: Select to stop carrying traffic on this service group. Edit: Select to edit the selected service group. See Edit Service Group Tab, page 6-59. Delete: Select to delete the selected service group. Edit Service Group Tab On the Service Group tab, select the service group, right-click and select Edit from the menu. The Edit Service Group tab appears Figure 6-30 Edit Service Group You can change the following parameters: Name: Indicates the name of the group. If this parameter is changed, use alphanumeric characters only. Do not use any other punctuation or special characters. Description: Indicates the user-provisioned description for this service group. If this parameter is changed, use alphanumeric characters only. Do not use any other punctuation or special characters. Release TN4.0.x Turin Networks Page 6-59

TransNav GUI Guide, Section 6: Services Edit Service Group Tab Command buttons are as follows: Synchronize: Select to synchronize the services to the management server and the nodes. Activate: Select to activate the service group to carry traffic. Deactivate: Select to stop carrying traffic on this service group. Add Members: Select to add endpoints to this service group. Delete Members: Select to delete members from this service group. Advanced: Select to configure advanced parameters for this service group. These parameters are propagated to each service in the group. Apply: Select to apply any changes made in the screen and return to the Service Group tab. Cancel: Select to cancel any changes and return to the Service Group tab. Page 6-60 Turin Networks Release TN4.0.x

SECTION 6SERVICES Chapter 7 Managing Services Introduction This chapter includes the following topics: Service Tab, page 6-62 Service Menu and Shortcut Menus, page 6-64 Working with the Service List, page 6-65 Viewing, Editing, or Deleting a Service, page 6-66 Setting Service Filters, page 6-66 Release TN4.0.x Turin Networks Page 6-61

TransNav GUI Guide, Section 6: Services Service Tab Service Tab The Service tab displays an overview of all services in the domain and allows you to add, view, edit, delete, activate, deactivate, and abort services. Additionally, you can customize which services appear by setting service filters. Figure 6-31 Service Tab The Service tab displays a list of services in a table format using the following column headings. ID: Displays the service identifier assigned by the system in the following format: [Node name] [Unique service identification number for that node]. Name: Displays the name of the service. Source, Destination: Displays source service endpoint in the format: NodeID/slot#(cardType)/port#(portType)/sts#/vtg#/vt# Example: Node1/s11(OC192)/p1(OC192)/sts161/vtg1/vt1 For SONET-STS services with an Ethernet card as the source, the port number is zero (p0). This port refers to the OC-48 interface on the backplane. Page 6-62 Turin Networks Release TN4.0.x

Chapter 7 Managing Services Service Tab Type: Displays the type of service (and is based on legacy provisioning models). DS1: At least one DS1 port is an endpoint for the service. DS1MUX: One DS1 card is an endpoint for the service. DS3CC: One DS3CC port is an endpoint for the service. DS3TMX: One DS3TMX port is an endpoint for the service. Ethernet: Is one of the supported Ethernet service types. SONET-STS: One of the endpoints is an OC, EC3, or EC1 port. SONET-VT1.5: One of the endpoints is an OC or EC3 port. VC-Bundle: A VC-bundle service. Bandwidth: Displays the bandwidth of the service using DS1, DS3, STS, or VT terminology. For example, a VT service would have a bandwidth of 1 VT. An VC-bundle with 4 STS-1s as members would have a bandwidth of 4 STS-1. Oper State: Displays one of the following states: Enabled: The service has been activated and is capable of carrying traffic. Disabled: The service has not been activated. Admin State: You can only lock or unlock a service that is not activated. Select one of the following states: Lock: You cannot activate the service to carry traffic. Unlock (default): You can activate the service to carry traffic. Svc. State: Displays the service state of the service in response to a user action or event as shown. The following table lists and defines the values in this column. Table 6-13 Possible Service States in Response to User Actions User Action/Event Provision service Activate Deactivate Abort Delete Node restart Provisioned Possible Service States Act. (Activation) In Progress Act. (Activation) Failed Activated Deact. (Deactivation) In Progress Deact. (Deactivation) Failed Abort In Progress Abort Failed Del. (Deletion) In Progress Pump Up In Progress Pump Up Failed Customer: Displays the customer name. Description: Displays the description of the service. Release TN4.0.x Turin Networks Page 6-63

TransNav GUI Guide, Section 6: Services Service Menu and Shortcut Menus Command buttons are as follows: Options: Set filters for services to be displayed. Displays the Service List Filters screen. See Setting Service Filters, page 6-66. Add: Select to add a service. Displays the General Information screen. Edit: Select to edit the selected service. Delete: Select to delete the selected service from the system. Service Menu and Shortcut Menus Use the menu commands to perform actions on any provisioned service. You can display the service menu in two ways: From the Services menu, click a service in the service list, or Figure 6-32 Service Menu Click the Service tab, then right-click the selected service from the service list. Figure 6-33 Service Tab and Right-Click Menu You can execute the following commands from the service list. Show TxRx Path. Click Show TxRx Path to view both the active and standby paths in the transmit and receive directions. See Chapter 8 Managing Service Paths, Showing TxRx Paths, page 6-71. Page 6-64 Turin Networks Release TN4.0.x

Chapter 7 Managing Services Working with the Service List Show Prov Path. Click Show Prov Path to see the provisioned path of the service through the network. See Chapter 8 Managing Service Paths, Showing TxRx Paths, page 6-71. Show Last Error. Click Show Last Error to show the last error the service encountered. Abort: Abort in-progress service activation, deactivation, or deletion. Activate: Activate the selected service to start carrying traffic. Deactivate: Stop the selected service from carrying traffic. Roll: Transfer traffic from one facility to another without interrupting service. Create all the bridge services individually first, then roll and commit multiple services. See the Traverse Provisioning Guide, Section 5 Creating Service Applications, Chapter 2 Bridging and Rolling Services, page 5-13, for detailed procedures on bridging and rolling services. Unroll: Allows you to undo the previous command. Commit Rolled: After you roll traffic to a new facility, commit the transfer and delete the original service. Edit: Edit the selected service. Delete: Delete the selected service. Duplicate. Duplicate the service. Working with the Service List You can change the way you see the services in the services list. Sorting Services Click a column heading to sort the services list by that category. Column headings can be sorted in ascending or descending order. Click the column heading again to switch from ascending to descending order. Hold down the Shift key and click a second column heading to sort the second category within the first category. Hold down the Shift key and click the second column again to switch between ascending and descending order within the first category. Resizing Columns To change the width of a column, drag the mouse between column headings, e.g., between Name and Egress, until you see a double arrow. Click and drag to the left or right to change the column width. Grouping Services Select a service listed on the Service tab. Hold the Ctrl key down to select other services. You can now activate, deactivate, or delete a group of services. Filtering Services Sort and view the services using the Options command button. See Setting Service Filters, page 6-66. Release TN4.0.x Turin Networks Page 6-65

TransNav GUI Guide, Section 6: Services Viewing, Editing, or Deleting a Service Viewing, Editing, or Deleting a Service Setting Service Filters Service Filters, Type Tab On the Service tab, from the Services List, select a service. The background of the row turns blue. You can view, edit, or delete the service in one of three ways: Right-click the selected row and select View, Edit, or Delete. Click the View, Edit, or Delete button on the Service tab. Select View, Edit, or Delete from the Services menu. You can only edit a service that is not currently activated. If a service is activated, you must deactivate it before you can edit it. You can control which services are displayed in the service list on the Service tab by setting filters. Set filters by clicking Options on the Service tab. Service Filters, Type Tab, page 6-66 Service Filters, Node Tab, page 6-67 Service Filters, Source Tab, page 6-68 Service Filters, Destination Tab, page 6-69 Service Filters, Customer Tab, page 6-70 From the Service tab, click Options. The Type tab displays allowing you to include or exclude specific service types from being displayed in the service list on the Service tab. Active check box Figure 6-34 Service List Filters Dialog Box, Type Tab Select the Active check box to make the Type filter active. Clear the Active check box to make the Type filter inactive. To display a specific service type, click the service type in the left box and click Add>> to move it to the right box. To remove a specific service types from the service list, click the service type in the right box and click Remove<<. Click Clear to clear all service types from being displayed. Page 6-66 Turin Networks Release TN4.0.x

Chapter 7 Managing Services Service Filters, Node Tab Command buttons are as follows: Cancel: Do not save any configuration changes. Apply: Apply these service types to the filter. Done: Close the screen. Service Filters, Node Tab From the Service tab, click Options. Click the Node tab to display services on specific nodes. Figure 6-35 Service List Filters Dialog Box, Node Tab Select the Active check box to make the Node filter active. Clear the Active check box to make the Node filter inactive. Nodes are listed in the left box. To display services on a specific node, click the node in the left box and click the Add>> button to move it to the right box. To remove a services on a specific node from the service list, click the service type in the right box and click Remove<<. Click Clear to prevent all services on all nodes from being displayed. Command buttons are as follows: Cancel: Do not save any configuration changes. Apply: Apply these nodes to the filter. Done: Save the changes and close the screen. Release TN4.0.x Turin Networks Page 6-67

TransNav GUI Guide, Section 6: Services Service Filters, Source Tab Service Filters, Source Tab From the Service tab, click Options. Click the Source tab to display services with specific source nodes. Figure 6-36 Service List Filters Dialog Box, Source Tab Select the Active check box to make the Source filter active. Clear the Active check box to make the Source filter inactive. To display services with a specific source node, click the node in the left box and click the Add>> button to move it to the right box. To remove a service with a specific source node from the service list, click the service type in the right box and click Remove<<. Click Clear to prevent all services from being displayed. Command buttons are as follows: Cancel: Do not save any configuration changes. Apply: Apply these nodes to the filter. Done: Close the screen. Page 6-68 Turin Networks Release TN4.0.x

Chapter 7 Managing Services Service Filters, Destination Tab Service Filters, Destination Tab From the Service tab, click Options. Click the Destination tab to display services with specific destination nodes. Figure 6-37 Service List Filters Dialog Box, Destination Tab Select the Active check box to make the Destination filter active. Clear the Active check box to make the Destination filter inactive. To display services with a specific source node, click the node in the left box and click the Add>> button to move it to the right box. To remove a service with a specific source node from the service list, click the service type in the right box and click Remove<<. Click Clear to prevent all services from being displayed. Command buttons are as follows: Cancel: Do not save any configuration changes. Apply: Apply these nodes to the filter. Done: Close the screen. Release TN4.0.x Turin Networks Page 6-69

TransNav GUI Guide, Section 6: Services Service Filters, Customer Tab Service Filters, Customer Tab From the Service tab, click Options. Click the Customer tab to display services for specific customers. Figure 6-38 Service List Filters Dialog Box, Customer Tab You can choose to include or exclude services for specific customers from being displayed on the Service tab. Select the Active check box to make the Customer filter active. Clear the Active check box to make the Customer filter inactive. Defined customers are listed in the left box. To display services for a specific customer, highlight the customer in the left box and click Add to move it to the right box. Click the Include button. To exclude a list of sources, click the Exclude button. Command buttons are as follows: Apply: Apply these customers to the filter. Done: Close the screen. Page 6-70 Turin Networks Release TN4.0.x

SECTION 6SERVICES Chapter 8 Managing Service Paths Introduction Showing TxRx Paths This chapter describes the following topics: Showing TxRx Paths, page 6-71 Viewing Service Alarms, page 6-73 Viewing Details, page 6-74 Assigning or Suppressing Alarms to Path Endpoints, page 6-74 Retrieving Service Performance Data, page 6-76 Protection Switching Path-Protected Services, page 6-77 On the Service tab, click a service to select it. Right-click and select Show TxRx Path. The Path Display for Service dialog box displays. Transmit path Receive path Refresh status Contextsensitive tabs Figure 6-39 Path Display for Service Dialog Box The Path Display for Service dialog box displays the following information: Transmit and Receive Paths for Services, page 6-72. Refresh Status of Service, page 6-73. Service alarms, configuration, performance, and protection switching information on context-sensitive tabs. Release TN4.0.x Turin Networks Page 6-71

TransNav GUI Guide, Section 6: Services Transmit and Receive Paths for Services Viewing Service Alarms, page 6-73 Viewing Details, page 6-74 Assigning or Suppressing Alarms to Path Endpoints, page 6-74 Retrieving Service Performance Data, page 6-76 Protection Switching Path-Protected Services, page 6-77 Click the up arrow between the Transmit and Receive information on the left hand side of the screen to display the Receive direction only. Click the down arrow to display the Transmit direction only. Click the up arrow between the Refresh status and the context-sensitive tabs to display the information on the tabs only. Click the down arrow to return to the default view. Transmit and Receive Paths for Services Each row in the Path Display for Service dialog box represents an active/standby port or path for the service. You can view the following information in both the transmit and receive directions: PG: Protection group type. Revertive: Displays true for revertive switching, false for non-revertive switching. XConn Conf (Cross-connect configuration): Displays one of the following values, depending on the role of the port or path in the protection group: fac. bri (facility bridge): Bridge for 1+1 APS protection or BLSR protection. fac. sel (facility selector): Selector for 1+1 APS protection or BLSR protection. path bri (path bridge): Bridge for 1+1 path protection or SNCP/UPSR. path sel (path selector): Selector for 1+1 path protection or SNCP/UPSR. Position: Displays Source, Destination, or Pass-Through depending on the position of the port or path in the service. Active Hop: Displays the name of the active hop in the format of node-slot-port-sts-[vtg-vt]. Active Failure: Displays the alarm condition or external switch command that caused a switch on the active port or path. Active Pg Role: Displays the role of the currently active port or path: Working or Protecting. For a ring configuration, (W) or (E) is displayed after Working or Protecting to indicate whether it is the West or East port. Standby Hop: Displays the name of the standby hop in the format of node-slot-port-sts-[vtg-vt]. StandBy Failure: Displays the alarm condition or external switch command that caused a switch on the standby port or path. StandBy Pg Role: Displays the role of the currently standby port or path: Working or Protecting. For a ring configuration, (W) or (E) is displayed after Working or Protecting to indicate whether it is the West or East port. Page 6-72 Turin Networks Release TN4.0.x

Chapter 8 Managing Service Paths Viewing Service Alarms Refresh Status of Service Viewing Service Alarms You can choose to automatically refresh the information displayed in the Path Display for Service dialog box according to the following options. The status bar displays the last successful refresh date and time. Auto Refresh: Select to automatically refresh active and standby paths according to the Every setting. Clear the box to manually refresh the active and standby paths. Every: Select the refresh interval (in minutes): 2 min 5 min 10 min 30 min Command buttons are as follows: Print: Print the contents displayed in the Path Display for Service dialog box to your local printer. Refresh: Manually refresh the information on the screen. On the Service tab, click a service to select it. Right-click the selected service and select Show TxRx Paths. The Path Display for Service dialog box displays. Alarm tab Figure 6-40 Alarm Tab on Path Display for Service Dialog Box The Alarm tab in the Path Display for Service dialog box functions the same as in the main graphical user interface window. See Section 8 Maintenance and Testing, Chapter 2 Alarms, page 8-11 for a complete description of the Alarm tab. Release TN4.0.x Turin Networks Page 6-73

TransNav GUI Guide, Section 6: Services Viewing Details Viewing Details On the Service tab, click a service to select it. Right-click the selected service and select Show TxRx Paths. The Path Display for Service dialog box displays. Click the Details tab. Details tab Figure 6-41 Details Tab on Path Display for Service Dialog Box The Details tab in the Path Display for Service dialog box allows you to view information in the following fields: CTP (connectivity termination point): The endpoint of the service. VCX Card Used: The 5G VT/TU card was used to create this service. Assigning or Suppressing Alarms to Path Endpoints On the Service tab, click a service to select it. Right-click the selected service and select Show TxRx Paths. The Path Display for Service dialog box displays. Click the CTP tab. CTP tab Figure 6-42 CTP Tab on Path Display for Service Dialog Box The CTP tab in the Path Display for Service dialog box allows you to view or provision the following fields: Endpoint: Click an endpoint in the Active Hop column. Page 6-74 Turin Networks Release TN4.0.x

Chapter 8 Managing Service Paths Assigning or Suppressing Alarms to Path Endpoints Alarm Profile: Assign an alarm profile to the endpoint. Select one of the following: useparent: The endpoint inherits the alarm profile of the path or port. For example, if this endpoint is a low order path or a VT endpoint, use this value to assign the alarm profile of the high order path to which it belongs. default: Uses the default profile for the selected endpoint. This profile will be one of: sdh_ho sdh_lo sonet_sts sonet_vt See the Node Operations and Maintenance Guide, Section 1 Fault Management, Chapter 1 Managing Alarms and Events, page 1-1 for detailed descriptions about alarms and alarm profiles. Received (Transmitted) Path Overhead: Click to review the transmission path trace information to isolate faults and diagnose problems, select the active hop for the transmitting or receiving service being traced. Figure 6-43 Path Overhead Dialog Box The command buttons are as follows: Refresh: Refresh the Received Path Trace field with the most recent data. Done: Close the dialog box and return to the Path Display for Service dialog box. Click the lock icon to change the administrative state of the timing source: The endpoint is unlocked and performance monitoring is enabled. The endpoint is disabled and performance monitoring is suppressed. When you return to the Path Display for Service dialog box, the command buttons are as follows: Apply: Save configuration changes to service. Cancel: Do not save any configuration changes. Done: Close the Path Display for Service dialog box and return to the main screen. Release TN4.0.x Turin Networks Page 6-75

TransNav GUI Guide, Section 6: Services Retrieving Service Performance Data Retrieving Service Performance Data On the Service tab, click a service to select it. Right-click the selected service and select Show TxRx Paths. The Path Display for Service dialog box displays. Click the PM tab. Click a row in the Active Hop (1) column, then click Refresh (2) to view the performance monitoring data for that hop. (For protected services, click a row in the Standby Hop column.) 1 Figure 6-44 PM Tab on Path Display for Service Dialog Box The PM tab in the Path Display for Service dialog box allows you to view the following fields: Hop ID: Displays the name of the selected hop in one of the following formats: node-slot-port-sts-[vtg-vt] node-slot-port-aug1 Last Refresh Time: Displays the last time performance monitoring information was refreshed. The performance monitoring data is presented in table format with the following column headings: Counter: Displays performance monitoring data according to the performance monitoring template selected for the service during service creation. Note: The EOS Port PM byte counts include the 8-byte GFP header, allowing users to view the precise loads being handled by the EOS port. Date and Time columns: Display the date and time of the last sample performance data per counter. Samples: A node stores 8 hours of PM data. If the Interval type selected is 15 min, type a number between 0 and 32 and click Refresh; the default is 4. The value 0 displays the current PM data. The value 32 displays the past 8 hours of PM data in 15-minute intervals. Interval: Select the interval at which the node monitors performance. 2 Page 6-76 Turin Networks Release TN4.0.x

Chapter 8 Managing Service Paths Protection Switching Path-Protected Services 15 min. A 15-minute register contains the value of one PM parameter as accumulated over a 15-minute period. Each 15-minute period begins at 0, 15, 30, or 45 minutes past the hour. 24 hour. A one-day register contains the total value of one PM parameter as accumulated over a 24-hour period. Each one-day period begins at midnight, local time on the node. If the Interval is 24 hours, type a number between 0 and 1 and click Refresh. The value 0 displays the current PM data. The value 1 displays the a performance monitoring data from the previous 24 hours, as well as the current data. Command buttons are as follows: Refresh: Refresh the Counter box with the most recent performance monitoring data. Reset: Reset counters to 0. Values will be gray with an asterisk (*) if reset or if the counter started after the interval time period. Print: Print contents of the Performance tab to your local printer. Save: Save performance monitoring information to a text file on your local client workstation. Done: Save the changes and return the the previous dialog box. Protection Switching Path-Protected Services On the Service tab, click a service to select it. Right-click the selected service and select Show TxRx Paths. The Path Display for Service dialog box displays. Click the Switch tab. 1 3 2 4 Figure 6-45 Switch Tab on Path Display for Service Dialog Box To perform protection switching commands on a UPSR/SNCP ring or a 1+1 path protected service: 1. From the Tx or Rx panel, click a service in Active Hop. Release TN4.0.x Turin Networks Page 6-77

TransNav GUI Guide, Section 6: Services Protection Switching Path-Protected Services 2. On the Switch tab, select a path. 3. From the Command list, select a protection switching command (see below). 4. Click Apply to apply the protection switch command. The protection switching commands you can perform on a path protected service are: Clear Working: Clears all switch commands for the designated signal. Protecting: Clears all switch commands for the designated signal. Lockout Protecting: Prevents the selector from switching to protection for the designated signal. If the selector is currently selecting the protection path for the designated signal, it is switched back to the working path. Forced Working: Causes the selector to perform a switch to protection for the designated signal, unless the Lockout of Protection or Forced Switch to Working command is in effect for the designated signal. If the currently selected path is the protection path, then no switch is performed and an error will be returned. Protecting: Causes the selector to perform a switch to the working path for the designated signal, unless a Forced Switch to Protection is in effect for the designated signal. If the currently selected path is the working path, then no switch is performed and an error will be returned. Manual Working: Causes the selector to perform a switch to protection for the designated signal, unless a request of equal or higher priority is in effect for the designated signal. If the currently selected path is the protection path, then no switch is performed and an error will be returned. Protecting: Causes the selector to perform a switch to the working path for the designated signal, unless a request of equal or higher priority is in effect for the designated signal. If the currently selected path is the working path, then no switch is performed and an error will be returned. Note: Switch commands on a UPSR/SNCP ring automatically trigger a refresh of the screen after a two-second pause. Page 6-78 Turin Networks Release TN4.0.x

SECTION 5DCS APPLICATIONS SECTION 7 DCS APPLICATIONS Contents Chapter 1 DCS-384 Matrix Shelf DCS-384 Matrix Shelf........................................... 7-2 What is an MSAID?............................................. 7-3 MSAID Formats................................................ 7-3 Commissioned Hardware Configuration............................. 7-4 Protection Groups on a DCS-384 Matrix Shelf........................ 7-5 DCS-384 MSAID Assignments.................................... 7-6 DCS-384 MSAID Allocation....................................... 7-7 DCS-384 Services.............................................. 7-8 Endpoints for DSC-384 Services................................... 7-9 Advanced Parameters (Alphabetic Order)........................... 7-10 DCS -384 Fragmentation........................................ 7-14 Chapter 2 DCS-IO Shelf DCS-IO Shelf.................................................. 7-16 DCS-IO MSAID Allocation........................................ 7-17 DCS-IO MSAID Assignments..................................... 7-18 Assignment Details............................................. 7-19 Chapter 3 DCS-96 Shelf DCS-96 Shelf................................................. 7-23 DCS-96 Assignments........................................... 7-24 DCS Assignment Details......................................... 7-25 DCS-96 Services............................................... 7-26 Endpoints for DSC-96 Services.................................... 7-27 Advanced Parameters (Alphabetic Order)........................... 7-28 List of Figures Figure 7-1 DCS-384 Shelf Configuration............................ 7-2 Figure 7-2 Shelf View of a Commissioned DCS-384 Matrix Shelf......... 7-4 Figure 7-3 Pre-provisioned Protection Groups on a DCS-384 Matrix Shelf.. 7-5 Figure 7-4 DCS-384 MSAID Assignments........................... 7-6 Figure 7-5 Assignment Details Dialog Box........................... 7-7 Release TN4.0.x Turin Networks Page i

TransNav GUI Guide, Section 7 DCS Applications Figure 7-6 DCS-384 MSAID Allocation.............................. 7-7 Figure 7-7 Create DCS Service Tab................................ 7-8 Figure 7-8 Selecting Endpoints for DCS-384 Services.................. 7-9 Figure 7-9 Advanced Parameters Dialog Box......................... 7-10 Figure 7-10 DCS Tab, Fragmentation Subtab......................... 7-14 Figure 7-11 DCS-IO Shelf View Example............................. 7-16 Figure 7-12 DCS-IO MSACARDID Allocation.......................... 7-17 Figure 7-13 DCS-IO MSAID Assignments............................ 7-18 Figure 7-14 Choose an Endpoint and Assignment Details Dialog Boxes..... 7-19 Figure 7-15 Single-Shelf DCS-96 Application.......................... 7-23 Figure 7-16 DCS Tab, Assignments Subtab........................... 7-24 Figure 7-17 Assignment Details Dialog Box........................... 7-25 Figure 7-18 Create DCS Service Tab (DCS-96 Shelf)................... 7-26 Figure 7-19 Selecting Endpoints for DCS-96 Services................... 7-27 Figure 7-20 Advanced Parameters Dialog Box......................... 7-28 List of Tables Table 7-1 MSAID Formats....................................... 7-3 Table 7-2 Preprovisioned Protection Groups for DCS-384 Matrix Shelf.... 7-5 Table 7-3 MSAID Number Assignments in a DCS-384 Matrix Shelf....... 7-6 Table 7-4 OC-48 Interfaces on DCS-384 Matrix Shelf and MSAID Range.. 7-8 Page ii Turin Networks Release TN4.0.x

SECTION 7DCS APPLICATIONS Chapter 1 DCS-384 Matrix Shelf Introduction A DCS-384 matrix shelf is the matrix shelf in a Traverse multi-shelf DCS application. A Traverse multi-shelf consists of a DCS-384 matrix shelf and one or more DCS-IO shelves. This chapter explains the configuration of a DCS-384 matrix shelf. This chapter explains the following topics for DCS-384 matrix shelf: DCS-384 Matrix Shelf, page 7-2 What is an MSAID?, page 7-3 MSAID Formats, page 7-3 Commissioned Hardware Configuration, page 7-4 Protection Groups on a DCS-384 Matrix Shelf, page 7-5 DCS-384 MSAID Assignments, page 7-6 DCS-384 MSAID Allocation, page 7-7 DCS-384 Services, page 7-8 Endpoints for DSC-384 Services, page 7-9 Advanced Parameters (Alphabetic Order), page 7-10 DCS -384 Fragmentation, page 7-14 Release TN4.0.x Turin Networks Page 7-1

TransNav GUI Guide, Section 7: DCS Applications DCS-384 Matrix Shelf DCS-384 Matrix Shelf A DCS-384 matrix shelf is the node in a Traverse multi-shelf DCS application that performs the VT switching. The DCS-384 matrix shelves provides a non-blocking matrix able to cross-connect and groom 384 STSs worth of VT1.5s. A Traverse 2000 commissioned as a DCS-384 matrix shelf uses the following configuration: Slots 1 to 10 contain VT/TU 5G Switch cards Slots 11 to 18 contain 2-port OC-48 cards (DCS trunks) Slots 19 and 20 contain redundant shelf controllers 5 G V T S W 5 G V T S W 5 G V T S W 5 G V T S W 5 G V T S W 5 G V T S W 5 G V T S W 5 G V T S W 5 G V T S W 5 G V T S W 2 P O C 4 8 2 P O C 4 8 2 P O C 4 8 2 P O C 4 8 2 P O C 4 8 2 P O C 4 8 2 P O C 4 8 2 P O C 4 8 G C M G C M W W W W W W W W W P 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 Node1 (DCS-384) DCS-IO shelves Figure 7-1 DCS-384 Shelf Configuration The VT/TU 5G Switch cards groom the incoming and outgoing VT1.5s STSs. The minimum configuration of a DCS-384 matrix shelf requires two VT/TU 5G cards (a working and a protect) and one VT/TU 5G card for each 2-port OC-48 card. The matrix shelf connects to external shelves (called DCS-IO) shelves with protected OC-48 links. Eight pairs of OC-48 DCS trunks are required to supply 384 STSs of incoming and outgoing VT1.5s. When you commission a DCS-384 matrix shelf, it is created and preprovisioned with ten VT/TU 5G Switch cards and eight 2-port OC-48 cards. A DCS-384 matrix shelf is also automatically preprovisioned with the following protection groups: Eight 1+1 APS protection groups for the OC-48 cards One 1:N equipment protection group for the VT/TU 5G Switch cards Create the DCS-384 matrix shelf when you commission the node. See the Traverse Installation and Commissioning Guide, Section 11 Node Start-up and Commissioning Procedures for node commissioning procedures. Page 7-2 Turin Networks Release TN4.0.x

Chapter 1 DCS-384 Matrix Shelf MSAID Formats What is an MSAID? The matrix STS identifier (MSAID) is the format of the access identifier (AID) used as the reference in creating cross connects on a DCS shelf. The MSAID is a global STS identifier for the matrix. Commissioning a DCS-384 matrix shelf automatically assigns MSAID 1 to s-11/p-1/sts-1 (slot 11, port 1, sts-1). The MSAID numbers increment with each subsequent STS on the port, then move to the next working port and subsequent STS. A user cannot change the assignments on the DCS-384 matrix shelf. MSAID Formats The MSAID format specifies how the VT service maps into the payload of the SONET frame. Specify the MSAID format during node commissioning. MSAID-VTG-VT is the default and can be used even in a mixed-mapping environment. All incoming STS to the matrix shelf must have the same MSAID formats. Turin recommends that MSAID formats match on all shelves in the DCS application. To change the MSAID format on configured services, first delete all the services, change the MSAID format in the CLI [set node general msaid-format], then re-create the services. The Traverse supports the following MSAID formats. Table 7-1 MSAID Formats DS1 Channel MSAID-VT-GR253 MSAID-VT-Seq MSAID-VTG-VT Payload Mapping User Interface Payload Mapping User Interface User Interface 1 VTG1, VT1 gr253#1 VTG1, VT1 seq#1 VTG1, VT1 2 VTG2, VT1 gr253#2 VTG1, VT2 seq#2 VTG1, VT2 3 VTG3, VT1 gr253#3 VTG1, VT3 seq#3 VTG1, VT3 4 VTG4, VT1 gr253#4 VTG1, VT4 seq#4 VTG1, VT4 5 VTG5, VT1 gr253#5 VTG2, VT1 seq#5 VTG2, VT1 6 VTG6, VT1 gr253#6 VTG2, VT2 seq#6 VTG2, VT2 7 VTG7, VT1 gr253#7 VTG2, VT3 seq#7 VTG2, VT3 8 VTG1, VT2 gr253#8 VTG2, VT4 seq#8 VTG2, VT4 9 VTG2, VT2 gr253#9 VTG3, VT1 seq#9 VTG3, VT1 10 VTG3, VT2 gr253#10 VTG3, VT2 seq#10 VTG3, VT2 11 VTG4, VT2 gr253#11 VTG3, VT3 seq#11 VTG3, VT3 12 VTG5, VT2 gr253#12 VTG3, VT4 seq#12 VTG3, VT4 13 VTG6, VT2 gr253#13 VTG4, VT1 seq#13 VTG4, VT1 14 VTG7, VT2 gr253#14 VTG4, VT2 seq#14 VTG4, VT2 15 VTG1, VT3 gr253#15 VTG4, VT3 seq#15 VTG4, VT3 16 VTG2, VT3 gr253#16 VTG4, VT4 seq#16 VTG4, VT4 17 VTG3, VT3 gr253#17 VTG5, VT1 seq#17 VTG5, VT1 18 VTG4, VT3 gr253#18 VTG5, VT2 seq#18 VTG5, VT2 19 VTG5, VT3 gr253#19 VTG5, VT3 seq#19 VTG5, VT3 20 VTG6, VT3 gr253#20 VTG5, VT4 seq#20 VTG5, VT4 Release TN4.0.x Turin Networks Page 7-3

TransNav GUI Guide, Section 7: DCS Applications Commissioned Hardware Configuration Table 7-1 MSAID Formats DS1 Channel MSAID-VT-GR253 MSAID-VT-Seq MSAID-VTG-VT Payload Mapping User Interface Payload Mapping User Interface User Interface 21 VTG7, VT3 gr253#21 VTG6, VT1 seq#21 VTG6, VT1 22 VTG1, VT4 gr253#22 VTG6, VT2 seq#22 VTG6, VT2 23 VTG2, VT4 gr253#23 VTG6, VT3 seq#23 VTG6, VT3 24 VTG3, VT4 gr253#24 VTG6, VT4 seq#24 VTG6, VT4 25 VTG4, VT4 gr253#25 VTG7, VT1 seq#25 VTG7, VT1 26 VTG5, VT4 gr253#26 VTG7, VT2 seq#26 VTG7, VT2 27 VTG6, VT4 gr253#27 VTG7, VT3 seq#27 VTG7, VT3 28 VTG7, VT4 gr253#28 VTG7, VT4 seq#28 VTG7, VT4 Commissioned Hardware Configuration In Shelf View, click the DCS tab. When you commission a node to be a DCS-384 matrix shelf, the cards are preprovisioned in the shelf in the following order: Slots 1 to 10 are preprovisioned with VT/TU 5G Switch cards. Slots 11 to 18 are preprovisioned with 2-port OC-48 cards. The GCM slots are empty in a preprovisioned node, but will show the correct card if the hardware is present. Figure 7-2 Shelf View of a Commissioned DCS-384 Matrix Shelf The minimum configuration for a DCS-384 matrix shelf is three VT/TU 5G Switch cards, two 2-port OC-48 cards, and two GCM cards. Page 7-4 Turin Networks Release TN4.0.x

Chapter 1 DCS-384 Matrix Shelf Protection Groups on a DCS-384 Matrix Shelf Protection Groups on a DCS-384 Matrix Shelf A DCS-384 matrix shelf is automatically preprovisioned with the following protection groups: Eight 1+1 APS protection groups for the OC-48 cards. One 1 for N equipment protection group for the VT/TU 5G Switch cards. Figure 7-3 Pre-provisioned Protection Groups on a DCS-384 Matrix Shelf The protection groups are listed in the following table. Table 7-2 Preprovisioned Protection Groups for DCS-384 Matrix Shelf Protection Group ID PG Type Working Protecting PG1 1+1 APS slot 11-port 1 slot 12-port 2 PG2 1+1 APS slot 12-port 1 slot 11-port 2 PG3 1+1 APS slot 13-port 1 slot 14-port 2 PG4 1+1 APS slot 14-port 1 slot 13-port 2 PG5 1+1 APS slot 15-port 1 slot 16-port 2 PG6 1+1 APS slot 16-port 1 slot 15-port 2 PG7 1+1 APS slot 17-port 1 slot 18-port 2 PG8 1+1 APS slot 18-port 1 slot 17-port2 PG13 1 for N equipment slots 1, 2, 3, 4, 5, 6, 7, 8, 9 slot 10 Release TN4.0.x Turin Networks Page 7-5

TransNav GUI Guide, Section 7: DCS Applications DCS-384 MSAID Assignments DCS-384 MSAID Assignments In Shelf View for a DCS-384 matrix shelf, click the DCS tab, then click the Assignment subtab. Figure 7-4 DCS-384 MSAID Assignments Commissioning a DCS-384 matrix shelf automatically assigns MSAID 1 to s-11/p-1/sts-1 (slot 11, port 1, sts-1). The MSAID numbers increment with each subsequent STS on the port, then moves to the next working port in the next slot. A user cannot change the assignments on the DCS-384 matrix shelf. Table 7-3 MSAID Number Assignments in a DCS-384 Matrix Shelf Slot#/ port# STS numbers MSAID assignments slot 11, port 1 sts-1, sts-2, sts-3,... sts-48 1, 2, 3,... 48 slot 12, port 1 sts-1, sts-2, sts-3,... sts-48 49, 50, 51,... 96 slot 13, port 1 sts-1, sts-2, sts-3,... sts-48 97, 98, 99,... 144 slot 14, port 1 sts-1, sts-2, sts-3,... sts-48 145, 146, 147,... 192 slot 15, port 1 sts-1, sts-2, sts-3,... sts-48 193, 194, 195,... 240 slot 16, port 1 sts-1, sts-2, sts-3,...sts-48 241, 242, 243,... 288 slot 17, port 1 sts-1, sts-2, sts-3,... sts-48 289, 290, 291,... 336 slot 18, port 1 sts-1, sts-2, sts-3,... sts-48 337, 338, 339,... 384 Page 7-6 Turin Networks Release TN4.0.x

Chapter 1 DCS-384 Matrix Shelf DCS-384 MSAID Allocation Command buttons are as follows: Details: Click the Details button to display the Assignment Details dialog box. Figure 7-5 Assignment Details Dialog Box In the Description field, enter an alphanumeric character string to describe the MSAID assignments in the DCS application. No special characters are allowed in the description. DCS-384 MSAID Allocation It is important to know the range of MSAIDs associated with each port in the DCS-384 matrix shelf because you must allocate the corresponding interface on the DCS-IO shelf with the correct range of MSAIDs. Figure 7-6 DCS-384 MSAID Allocation This screen shows the range of MSAID numbers associated with each pre-provisioned port on the DCS-384 matrix shelf. A user cannot change any allocations on this screen. The port column displays the port using the following syntax: /NodeId/slot(cardType)/port(PortType) (a p). where: NodeId is the user-defined name of the node slot is the number of the slot in which the card is inserted port is the number of the port on the card PortType is the speed of the SONET interface a (allocated) represents that the port is already allocated to a resource Release TN4.0.x Turin Networks Page 7-7

TransNav GUI Guide, Section 7: DCS Applications DCS-384 Services p (protecting) represents that there is a protection switch and the port is receiving traffic from the protecting link This table lists the OC-48 interfaces and the corresponding MSAID ranges. Table 7-4 OC-48 Interfaces on DCS-384 Matrix Shelf and MSAID Range Port MSAID Range /NodeId/s11(OC-48-2)p1(OC48) (a) [ 1-48 ] /NodeId/s12(OC-48-2)p1(OC48) (a) [ 49-96 ] /NodeId/s13(OC-48-2)p1(OC48) (a) [ 97-144 ] /NodeId/s14(OC-48-2)p1(OC48) (a) [ 145-192 ] /NodeId/s15(OC-48-2)p1(OC48) (a) [ 193-240 ] /NodeId/s16(OC-48-2)p1(OC48) (a) [ 241-288 ] /NodeId/s17(OC-48-2)p1(OC48) (a) [ 289-336 ] /NodeId/s18(OC-48-2)p1(OC48) (a) [ 337-384 ] DCS-384 Services On the DCS tab, click the Services subtab, then click Add. The Create Service tab appears. Figure 7-7 Create DCS Service Tab Use this screen to create DCS services (switching one MSAID to another). Name: Enter a unique name for the service. Use alphanumeric characters and spaces only. Do not use any other punctuation or special characters. Description: Enter the description of the service. Use alphanumeric characters and spaces only. Do not use any other punctuation or special characters. Bandwidth: Select the total bandwidth for the service: VT1.5 (default) STS-1 Strict (not applicable for DCS services) Customer: Select a customer name from the drop-down list box. Page 7-8 Turin Networks Release TN4.0.x

Chapter 1 DCS-384 Matrix Shelf Endpoints for DSC-384 Services Add Customer: Click to add a customer. For details, see Adding Customer Information, page 2-31. Endpoint Table: Select the endpoints of the service. See Endpoints for DSC-384 Services, page 7-9. Protection: The only valid protection for a DCS service on a DCS-384 matrix shelf is Unprotected (default protection of 1+1 APS). Command buttons are as follows: Advanced: Configure the characteristics of the connection. See Advanced Parameters (Alphabetic Order), page 7-10. Apply: Apply changes and return to the service list on the Service tab. Cancel: Cancel information, close the screen, and return to the Service tab. Endpoints for DSC-384 Services In the Create DCS Service screen, click a row in the EndPoint column of the endpoint table. Figure 7-8 Selecting Endpoints for DCS-384 Services The Choose and EndPoint dialog box appears in the upper left corner of the computer screen. From the navigation tree, click the node, card, and MSAID. For a VT1.5 bandwidth, also select the VTG and VT. Command buttons are as follows: Done: Click to save changes and return to the previous screen. Cancel: Cancel information, close the dialog box, and return to the Create Service tab. Release TN4.0.x Turin Networks Page 7-9

TransNav GUI Guide, Section 7: DCS Applications Advanced Parameters (Alphabetic Order) Advanced Parameters (Alphabetic Order) On the Create Service tab, click the Advanced button. The Advanced Parameters dialog box displays. Figure 7-9 Advanced Parameters Dialog Box Important: The contents of this dialog box are context-sensitive and depend on the selected sources and destinations. The following parameter descriptions are listed in alphabetical order. Bridge and Roll (Hop-by-hop services only): Select to create a bridge service. Use this parameter to transfer traffic from one facility to another without affecting live traffic. See the Traverse Provisioning Guide, Section 5 Creating Service Applications, Chapter 2 Bridging and Rolling Services, page 5-13 for detailed procedures on bridging and rolling services. DestDS1Mapping: For optical transmux services, select this parameter if the destination path carries a channelized DS3 payload. DestDS3Mapping: For optical transmux services, select this parameter if the destination STS carries a channelized DS3 payload. DestE1Mapping: For optical transmux services, select this parameter if the destination path carries a channelized DS3 payload. Dest PM Template: Select from the defined performance monitoring templates. The system default for performance monitoring thresholds is disabled for all parameters. Use the performance monitoring templates to set default thresholds or to customize threshold values. See Section 8 Maintenance and Testing, Chapter 1 Performance Monitoring, page 8-1 for information on how to use performance monitoring templates. Expected RTD: Enter the expected round trip delay measurement, in milliseconds, for this service. Values are 0 to 1000 milliseconds; default is 300ms. Failure Retry Count (for end-to-end services only): The number of times the system tries to reestablish the service before declaring it failed. Select 0 to 30; default is 3. Page 7-10 Turin Networks Release TN4.0.x

Chapter 1 DCS-384 Matrix Shelf Advanced Parameters (Alphabetic Order) Fwd Path Format: This port transmits a path trace identifier in the J1 byte of the SONET/SDH frame so that the path receiver can verify its continued connection. The values are: 16 bytes (default): Select if the receiver is an SDH port. 64 bytes: Select if the receiver is another SONET port. Fwd Path Trace: The path trace identifier transmitted in the J1 byte. Enter an alphanumeric character string. 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 options: Unequipped(00) Eqp-Nonspecific(01) (default): Equipped - Nonspecific Payload VT-Structured(02): VT-structured STS-1 SPE Locked VT(03): Locked virtual tributary (VT) mode DS3 Async(04): Asynchronous mapping for E3 or DS3. (Planned for future release.) DS4NA Async(12): Asynchronous mapping for DS4NA or E4. (Planned for future release.) ATM Map(13): Mapping for ATM DQDB Map(14): Mapping for DQDB FDDI Async(15): Asynchronous mapping for FDDI HDLC-PPP(16): HDLC-Over-SONET mapping X.86(18) GFB (1B): Generic Framing Procedure Frame format (ITU-T G.7041) POS No-Scramble (CF) Test Signal (FE): O.181 Test Signal (TSS1 to TSS3) mapping Load Balance Most-Fill (read-only): If there are two paths of equal cost, and Link1 and Link2 are the first different links between the paths, Most-Fill will use the link that is most filled between the two links. This reduces bandwidth fragmentation among links.. Max Hop Count (end-to-end services only): Displays the maximum number of hops to the timing source. 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: 1E-4: Value equals 1 x 10-4 1E-5: Value equals 1 x 10-5 1E-6 (default): Value equals 1 x 10-6 1E-7: Value equals 1 x 10-7 1E-8: Value equals 1 x 10-8 1E-9: Value equals 1 x 10-9 Release TN4.0.x Turin Networks Page 7-11

TransNav GUI Guide, Section 7: DCS Applications Advanced Parameters (Alphabetic Order) 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: 1E-3 (default): Value equals 1 x 10-3 1E-4: Value equals 1 x 10-4 1E-5: Value equals 1 x 10-5 Monitor RTD: Select to enable the delay measurement function for this service; default is disable (cleared checkbox). Path Mapping: Maps the VC-3 payload onto a transport path. This parameter determines how to monitor alarms and performance of the service through the intermediate nodes in the network. STS: Maps the payload into an STS path AU-4/LOVC (default): Maps the payload into an AU-4 low order virtual container AU-3/HOVC: Maps the payload into an AU-3 high order path virtual container VCRedline Circuit: Use this attribute to mark a service with Do not Deactivate. A redline circuit prevents accidental deactivation of an important service. You must first reset the redline attribute, then deactivate the service. Select one of the following options: Yes: Service is a redline circuit and cannot be deactivated No (default): Service is not a redline circuit and can be deactivated Rev Path Format: This port receives a path trace identifier in the J1 byte of the SONET/SDH frame so that the path transmitter can verify its continued connection. Select one of the following options: 16 bytes (default): Select if the receiver is a SONET port 64 bytes: Select if the receiver is another SONET port Rev Path Trace: The expected path trace identifier transmitted in the J1 byte. Enter an alphanumeric character string. Not used for unidirectional connections. Rev Signal Label: The path signal label (C2 byte in the STS path overhead) in the reverse direction of the LSP. Not used for unidirectional connections. Select one of the following values: Unequipped(00) Eqp-Nonspecific(01) (default): Equipped - Nonspecific Payload VT-Structured(02): VT-structured STS-1 SPE Locked VT(03): Locked virtual tributary (VT) mode DS3 Async(04): Asynchronous mapping for DS3 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-PPP(16): HDLC-Over-SONET mapping X.86(18) GFB (1B) POS No-Scramble (CF) Test Signal (FE): O.181 Test Signal (TSS1 to TSS3) mapping Page 7-12 Turin Networks Release TN4.0.x

Chapter 1 DCS-384 Matrix Shelf Advanced Parameters (Alphabetic Order) Setup Retry Count (end-to-end services only): The number of times the system retries a service activation request before declaring that activation failed. Select 0 to 30; default is 3. SourceDS1Mapping: For optical transmux services, select this parameter if the source path carries a channelized DS3 payload. SourceDS3Mapping: For optical transmux services, select this parameter if the source STS carries a channelized DS3 payload. SourceE1Mapping: For optical transmux services, select this parameter if the source path carries a channelized DS3 payload. Source PM Template: Select from the defined performance monitoring templates. The system default for performance monitoring thresholds is disabled for all parameters. Use the performance monitoring templates to set default thresholds or to customize threshold values. See Section 8 Maintenance and Testing, Chapter 1 Performance Monitoring, page 8-1 for information on how to use performance monitoring templates. See the Node Operations and Maintenance Guide section documentation for details on performance monitoring parameters for optical ports. TMX Port: For optical transmux services, select the port you designated as the STS1TMX resource. Transparency: Specifies if this service is transparently transporting payloads and overhead of legacy equipment. This service must have a STS-12c, STS-48c, VC-4-4c, or VC-4-16c bandwidth. The Control Data parameter must be Disabled on the interface. Select ON or OFF. On: This service has a bandwidth of STS-48c and is transparently transporting services between legacy equipment Off (default): This service is not a transparency service Unidirectional: Select for a unidirectional connection (the traffic can only travel in one direction from source to destination). The default is unselected which means that the connection is bidirectional (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. Release TN4.0.x Turin Networks Page 7-13

TransNav GUI Guide, Section 7: DCS Applications DCS -384 Fragmentation DCS -384 Fragmentation In Shelf View for a DCS-384 matrix shelf, click the DCS tab, then click the Fragmentation subtab. Figure 7-10 DCS Tab, Fragmentation Subtab The Fragmentation subtab screen displays the following information: Slot: Displays the slot number 1, 2, 3, 4, 5, 6, 7, 8, 9. The card in slot 10 is a protection card and has no fragmentation significance. Type: Displays the type of card in the slot (VT/TU 5G). Fragmentation Level: Displays a percentage of fragmentation on the card. A high percentage means the card s resources are highly fragmented. A low percentage means that the card s resources are not very fragmented. Turin recommends performing a defragmentation operation at a threshold of 80%. Defragmentation State: Displays the state of the defragmentation process on the card. Possible values are: Fragmentation In Progress: The resources on the card in the middle of a defragmentation operation. Fragmentation Successful: The defragmentation operation was successful. Fragmentation Failed: The defragmentation operation was not successful. Command buttons are as follows: Refresh: Click to refresh the screen with the latest data from the node. Defragment: Select a card from the drop down menu, then click Defragment to start a defragment operation on a card. Page 7-14 Turin Networks Release TN4.0.x

SECTION 7DCS APPLICATIONS Chapter 2 DCS-IO Shelf Introduction A DCS-IO shelf is the input/output shelf in a Traverse multi-shelf DCS application. A Traverse multi-shelf consists of a DCS-384 matrix shelf and one or more DCS-IO shelves. This chapter explains the configuration of a DCS-IO shelf. This chapter explains the following topics for DCS-IO shelf: DCS-IO Shelf, page 7-16 DCS-IO MSAID Allocation, page 7-17 DCS-IO MSAID Assignments, page 7-18 Release TN4.0.x Turin Networks Page 7-15

TransNav GUI Guide, Section 7: DCS Applications DCS-IO Shelf Page 7-16 Turin Networks Release TN4.0.x DCS-IO Shelf A DCS-IO shelf is the input/output node in a Traverse multi-shelf DCS application. A DCS-IO shelf sends VT-mapped STS to the 384 matrix to be groomed over one or more protected OC-48 DCS trunk connections. Figure 7-11 DCS-IO Shelf View Example The DCS-IO shelf connects to the DCS-384 matrix shelf using OC-48 interfaces. The OC-48 interfaces must be in a 1+1 APS protection group. Connect the working interfaces on the DCS-IO shelf to the working interfaces of the DCS-384 matrix shelf. Connect the protecting interfaces on the DCS-IO shelf to the protecting interfaces on the DCS-384 matrix shelf. Create the DCS-IO shelf when you commission the node. See the Traverse Installation and Commissioning Guide, Section 11 Node Start-up and Commissioning Procedures for node commissioning procedures. 2 8 P D S 1 W 2 8 P D S 1 P 2 8 P D S 1 W 2 8 P D S 1 W 2 8 P D S 1 P 2 P O C 4 8 8 P O C 3 8 P O C 3 1 2 P D S 3 T M X W 1 2 P D S 3 T M X P 1 2 P D S 3 T M X W 1 2 P D S 3 T M X W 1 2 P D S 3 T M X P 1 2 P D S 3 T M X W 2 8 P D S 1 W 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 G C M + O C 1 2 G C M + O C 1 2 2 P O C 4 8 Node2 (DCS-IO) OC-12 UPSR DCS-384 Matrix Shelf

Chapter 2 DCS-IO Shelf DCS-IO MSAID Allocation DCS-IO MSAID Allocation It is important to know how the MSAIDs are allocated in the DCS-384 matrix shelf before you allocate MSAIDs on the DCS-IO shelf. See Section 7 DCS Applications, Chapter 1 DCS-384 Matrix Shelf, page 7-7 for a detailed description of MSAID allocation on the DCS-384 matrix shelf. On the DCS-IO shelf, allocate the correct range of MSAIDs to the ports (links) connected to the DCS-384 matrix shelf. If the port is in a 1+1 APS protection group, allocate the range to the working port. 1 2 3 Figure 7-12 DCS-IO MSACARDID Allocation In this example, the OC-48 interfaces in slots 17 and 18 on the DCS-IO shelf are connected to slots 13 and 14 on the DCS-384 matrix shelf. Allocate the 97 to 144 MSAID range on the DCS-IO shelf to slot 17. Allocate the 145 to 192 MSAID range on the DCS-IO shelf to slot 18. Port. Click the row to display the Choose a Port dialog box. Select working port (a). Click Done to close the dialog box and return to the DCS tab on the main window. The port column displays the port using the following syntax: /NodeId/slot <cardtype>/port <PortType> (a p). where: NodeId is the user-defined name of the node slot is the number of the slot in which the card is inserted port is the number of the port on the card PortType is the speed of the SONET interface a (active) represents the traffic on that port is receiving traffic from the working traffic p (protecting) represents that there is a protection switch and the port is receiving traffic from the protecting link. This option is invalid. MSAID Range. Select the correct MSAID range. The MSAID range for the port needs to match the MSAID allocation range on the far end of the link (on the DCS-384 matrix shelf). See Section 7 DCS Applications, Chapter 1 DCS-384 Matrix Shelf, page 7-7 for a detailed description of MSAID ranges on the DCS-384 matrix shelf. Release TN4.0.x Turin Networks Page 7-17

TransNav GUI Guide, Section 7: DCS Applications DCS-IO MSAID Assignments Select one of the following options: Unset MSAID range. Removes the row from the table. [ 1-48 ] to assign MSAIDs 1 to 48 to this OC-48 interface. [ 49-96 ] to assign MSAIDs 49 to 96 to this OC-48 interface. [ 97-144 ] to assign MSAIDs 97 to 144 to this OC-48 interface. [ 145-192 ] to assign MSAIDs 145 to 192 to this OC-48 interface. [ 193-240 ] to assign MSAIDs 193 to 240 to this OC-48 interface. [ 241-288 ] to assign MSAIDs 241 to 288 to this OC-48 interface. [ 289-336 ] to assign MSAIDs 289 to 336 to this OC-48 interface. [ 337-384 ] to assign MSAIDs 337 to 384 to this OC-48 interface. Command buttons are as follows: Apply: Click to save the MSAID allocation. Cancel: Click to cancel provisioning. DCS-IO MSAID Assignments In Shelf View for a DCS-IO shelf, click the DCS tab, then click the Assignment subtab. Figure 7-13 DCS-IO MSAID Assignments Endpoint: Displays the STS-1 equivalent endpoint. The endpoint can be one of the following STS-1 equivalents: DS1 card DS3CC port DS3TMX port EC1 port OC-N port, STS number MSAID: A number between 1 and 384 depending on the MSAID allocation on the DCS-IO shelf. See DCS-IO MSAID Allocation, page 7-17. Status: Displays the status of the assignment. Description. Displays a user-defined alphanumeric character string to describe the assignments in the DCS application. Page 7-18 Turin Networks Release TN4.0.x

Chapter 2 DCS-IO Shelf Assignment Details Command buttons are as follows: (De)Activate: Allows or stops the selected assignments from carrying traffic. This button is context-sensitive. If the selected assignment is NOT activated, clicking the button will activate the assignment. If the selected assignment IS activated, clicking the button will stop the assignment from carrying traffic. Either hold the Ctrl key and click individual assignments OR hold the Shift key and select a range of assignments. Roll: Transfer traffic from one facility to another without interrupting service. Create all of the bridge services individually first, then roll and commit multiple services. See the Traverse Provisioning Guide, Section 5 Creating Service Applications, Chapter 2 Bridging and Rolling Services, page 5-13 for detailed procedures on bridging and rolling services. Unroll: An undo command. Commit Rolled: After you roll traffic to a new facility, commit the transfer and delete the original service. Add: Add an assignment to the assignment list. See Assignment Details, page 7-19. Delete: Click to remove the selected assignments from the list. Details: Click to see the exact source and the configured parameters of the selected assignment. Last Error: Click an assignment, then click this button to see the last error on the assignment. Assignment Details On the DCS tab, Assignment subtab, click Add. The Assignment Details dialog box displays. Figure 7-14 Choose an Endpoint and Assignment Details Dialog Boxes Release TN4.0.x Turin Networks Page 7-19

TransNav GUI Guide, Section 7: DCS Applications Assignment Details Endpoint: Click the field to display the Choose an Endpoint dialog box. Navigate the tree and select the STS-1 equivalent endpoint of the assignment. MSAID: The MSAID Allotments must be provisioned before you select the MSAID assignment. See DCS-IO MSAID Allocation, page 7-17. Select one MSAID number from the available allocations for each STS-1 equivalent piece of equipment. Description. Enter an alphanumeric character string to describe the MSAID assignments in the DCS application. Do not use any other punctuation or special characters. Source and Dest PM Template: Select from the defined performance monitoring templates. The system default for performance monitoring thresholds is disabled for all parameters. Use the performance monitoring templates to set default thresholds or to customize threshold values. See Section 8 Maintenance and Testing, Chapter 1 Performance Monitoring, page 8-1 for information on how to use performance monitoring templates. Transmuxed: For optical transmux services, select the port you designated as the STS1TMX resource. Bridge and Roll: Select to create a bridge service. Use this parameter to transfer traffic from one facility to another without affecting live traffic. See the Traverse Provisioning Guide, Section 5 Creating Service Applications, Chapter 2 Bridging and Rolling Services, page 5-13 for detailed procedures on bridging and rolling services. Fwd Path Trace: The path trace identifier transmitted in the J1 byte. Enter an alphanumeric character string. 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 options: Unequipped(00) Eqp-Nonspecific(01) (default): Equipped - Nonspecific Payload VT-Structured(02): VT-structured STS-1 SPE Locked VT(03): Locked virtual tributary (VT) mode DS3 Async(04): Asynchronous mapping for E3 or DS3 (Planned for future release.) DS4NA Async(12): Asynchronous mapping for DS4NA or E4 (Planned for future release.) ATM Map(13): Mapping for ATM DQDB Map(14): Mapping for DQDB FDDI Async(15): Asynchronous mapping for FDDI HDLC-PPP(16): HDLC-Over-SONET mapping X.86(18) POS No-Scramble (CF) Test Signal (FE): O.181 Test Signal (TSS1 to TSS3) mapping Rev Path Trace: The expected path trace identifier transmitted in the J1 byte. Enter an alphanumeric character string. Not used for unidirectional connections. Page 7-20 Turin Networks Release TN4.0.x

Chapter 2 DCS-IO Shelf Assignment Details Rev Signal Label: The path signal label (C2 byte in the STS path overhead) in the reverse direction of the LSP. Not used for unidirectional connections. Select one of the following options: Unequipped(00) Eqp-Nonspecific(01) (default): Equipped - Nonspecific Payload VT-Structured(02): VT-structured STS-1 SPE Locked VT(03): Locked virtual tributary (VT) mode DS3 Async(04): Asynchronous mapping for DS3 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-PPP(16): HDLC-Over-SONET mapping X.86(18) POS No-Scramble (CF) Test Signal (FE): O.181 Test Signal (TSS1 to TSS3) mapping Protection. The only valid protection for an MSAID Allocation on a DCS-IO shelf is Unprotected (default). Release TN4.0.x Turin Networks Page 7-21

TransNav GUI Guide, Section 7: DCS Applications Assignment Details Page 7-22 Turin Networks Release TN4.0.x

Release TN4.0.x Turin Networks Page 7-23 SECTION 7 Chapter 3 DCS-96 Shelf Introduction This chapter explains the following topics for DCS-96 shelf: DCS-96 Shelf, page 7-23 DCS-96 Assignments, page 7-24 DCS Assignment Details, page 7-25 DCS-96 Services, page 7-26 Advanced Parameters (Alphabetic Order), page 7-28 DCS-96 Shelf A DCS-96 shelf is a Traverse node in a Traverse single-shelf DCS application. A DCS-96 shelf has a protected 96 STS-1 capacity. A single-shelf or DCS-96 application requires the following cards: Any combination of DS1, DS3/EC1, OC-3, OC-12, and OC-48 cards up to the equivalent of 96 STSs Two VT/TU 5G Switch cards Two GCMs with or without integrated OC-12/48 ports Figure 7-15 Single-Shelf DCS-96 Application This example of a 96 STS-equivalent VT matrix shelf has the following configuration: 1:1 protected GCM and VT/TU 5G Switch cards 1:2 protected DS1 and DS3/EC-1 ports 1+1 APS OC-3 and OCS-12 ports 2 8 P D S 1 W 2 8 P D S 1 P 2 8 P D S 1 W 2 8 P D S 1 W 2 8 P D S 1 P 5 G V T S W 5 G V T S W 8 P O C 3 8 P O C 3 1 2 P D S 3 T M X W 1 2 P D S 3 T M X P 1 2 P D S 3 T M X W 1 2 P D S 3 T M X W 1 2 P D S 3 T M X P 1 2 P D S 3 T M X W 2 8 P D S 1 W 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 G C M + O C 1 2 G C M + O C 1 2 Node1 (DCS-96) OC-12 UPSR

TransNav GUI Guide, Section 7: DCS-96 Assignments Two slots (slots 17 and 18) are reserved for expansion to a multi-shelf DCS application. Create the DCS-96 shelf when you commission the node. See the Traverse Installation and Commissioning Guide, Section 11 Node Start-up and Commissioning Procedures for node commissioning procedures. DCS-96 Assignments In Shelf View, click the DCS tab, then click the Assignments subtab to assign MSAID numbers to STS-equivalents on the DCS-96 shelf. Figure 7-16 DCS Tab, Assignments Subtab The Assignments subtab displays the following information: Endpoint: Displays the STS-1-equivalent endpoint of the assignment. MSAID: Displays the MSAID number from the available allocations for each STS-1-equivalent piece of equipment. State. Displays the state of the assignment. Description: Displays a user-defined alphanumeric character string to describe the MSAID assignments in the DCS application. Command buttons are as follows: Add: Click to assign MSAID numbers to STS-equivalents on the DCS-96 shelf. The Assignment Details dialog box displays. See DCS Assignment Details, page 7-25. Delete: Select an assignment in the list, then click Delete to remove the assignment from the user interface. Details: Displays the Assignment Details dialog box. See DCS Assignment Details, page 7-25. Page 7-24 Turin Networks Release TN4.0.x

Chapter 3 DCS-96 Shelf DCS Assignment Details DCS Assignment Details In Shelf View, click the DCS tab to display the Assignments subtab, then click Add to add MSAID assignments to this DCS-96 shelf. The Assignments Details dialog box displays. Figure 7-17 Assignment Details Dialog Box This dialog box displays the following information: Endpoint: Click the field to display the Choose an Endpoint dialog box. Navigate the tree and select the STS-1-equivalent endpoint of the assignment. MSAID: Select one MSAID number from the available allocations for each STS-1-equivalent piece of equipment. Description: Enter an alphanumeric character string to describe the MSAID assignments in the DCS application. Do not use any other punctuation or special characters. Command buttons are as follows: Show TxRx Path: Click Show TxRx Path to display the Path Display for Service screen. See Section 6 Services, Chapter 8 Managing Service Paths, page 6-71 for information on this screen. Apply: Click to save your changes and return to the Assignments subtab on the main screen. Cancel: Click to cancel any changes and return to the Assignments subtab on the main screen. Release TN4.0.x Turin Networks Page 7-25

TransNav GUI Guide, Section 7: DCS-96 Services DCS-96 Services On the DCS tab, click the Services subtab, then click Add. The Create DCS Service tab appears. Figure 7-18 Create DCS Service Tab (DCS-96 Shelf) Use this screen to create DCS services in a DCS-96 shelf. Name: Enter a unique name for the service. Use alphanumeric characters and spaces only. Do not use any other punctuation or special characters. Description: Enter the description of the service. Use alphanumeric characters and spaces only. Do not use any other punctuation or special characters. Bandwidth: Select the total bandwidth for the service: VT1.5 (default) STS-1 Strict (not applicable for DCS services) Customer: Select a customer name from the drop-down list box. Add Customer: Click to add a Customer. For details, see Adding Customer Information, page 2-31. Endpoint Table: Select the endpoints of the service. See Endpoints for DSC-96 Services, page 7-27. Protection: The only valid protection for a DCS service on a DCS-96 shelf is Unprotected (default protection of 1+1 APS). Command buttons are as follows: Advanced: Configure the characteristics of the connection. See Advanced Parameters (Alphabetic Order), page 7-28. Apply: Apply changes and return to the service list on the Service tab. Cancel: Cancel information, close the screen, and return to the Service tab. Page 7-26 Turin Networks Release TN4.0.x

Chapter 3 DCS-96 Shelf Endpoints for DSC-96 Services Endpoints for DSC-96 Services In the Create DCS Service screen, click a row in the EndPoint column of the endpoint table. The Choose an EndPoint dialog box appears in the upper left corner of the computer screen. Figure 7-19 Selecting Endpoints for DCS-96 Services From the navigation tree, click the shelf, card, and MSAID. For a VT1.5 bandwidth, also select the VTG and VT. Command buttons are as follows: Done: Click to save changes after you have selected the correct endpoint for the service. Cancel: Cancel information, close the dialog box, and return to the Create Service tab. Release TN4.0.x Turin Networks Page 7-27

TransNav GUI Guide, Section 7: Advanced Parameters (Alphabetic Order) Advanced Parameters (Alphabetic Order) On the Create DCS Service Tab, click the Advanced button. The Advanced Parameters dialog box displays. Figure 7-20 Advanced Parameters Dialog Box Important: The contents of this dialog box are context-sensitive and depend on the selected sources and destinations. The following parameter descriptions are listed in alphabetical order. Bridge and Roll (Hop-by-hop services only): Select to create a bridge service. Use this parameter to transfer traffic from one facility to another without affecting live traffic. See the Traverse Provisioning Guide, Section 5 Creating Service Applications, Chapter 2 Bridging and Rolling Services, page 5-13 for detailed procedures on bridging and rolling services. DestDS1Mapping: For optical transmux services, select this parameter if the destination path carries a channelized DS3 payload. DestDS3Mapping: For optical transmux services, select this parameter if the destination STS carries a channelized DS3 payload. DestE1Mapping: For optical transmux services, select this parameter if the destination path carries a channelized DS3 payload. Dest PM Template: Select from the defined performance monitoring templates. The system default for performance monitoring thresholds is disabled for all parameters. Use the performance monitoring templates to set default thresholds or to customize threshold values. See Section 8 Maintenance and Testing, Chapter 1 Performance Monitoring, page 8-1 for information on how to use performance monitoring templates. Expected RTD: Enter the expected round trip delay measurement, in milliseconds, for this service. Values are 0 to 1000 milliseconds; default is 300ms. Failure Retry Count (for end-to-end services only): The number of times the system tries to reestablish the service before declaring it failed. Select 0 to 30; default is 3. Fwd Path Format: This port transmits a path trace identifier in the J1 byte of the SONET/SDH frame so that the path receiver can verify its continued connection. The values are: Page 7-28 Turin Networks Release TN4.0.x

Chapter 3 DCS-96 Shelf Advanced Parameters (Alphabetic Order) 16 bytes (default): Select if the receiver is an SDH port. 64 bytes: Select if the receiver is another SONET port. Fwd Path Trace: The path trace identifier transmitted in the J1 byte. Enter an alphanumeric character string. 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 options: Unequipped(00) Eqp-Nonspecific(01) (default): Equipped - Nonspecific Payload VT-Structured(02): VT-structured STS-1 SPE Locked VT(03): Locked virtual tributary (VT) mode DS3 Async(04): Asynchronous mapping for E3 or DS3. (Planned for future release.) DS4NA Async(12): Asynchronous mapping for DS4NA or E4. (Planned for future release.) ATM Map(13): Mapping for ATM DQDB Map(14): Mapping for DQDB FDDI Async(15): Asynchronous mapping for FDDI HDLC-PPP(16): HDLC-Over-SONET mapping X.86(18) GFB (1B): Generic Framing Procedure Frame format (ITU-T G.7041) POS No-Scramble (CF) Test Signal (FE): O.181 Test Signal (TSS1 to TSS3) mapping Load Balance Most-Fill (read-only): If there are two paths of equal cost, and Link1 and Link2 are the first different links between the paths, Most-Fill will use the link that is most filled between the two links. This reduces bandwidth fragmentation among links.. Max Hop Count (end-to-end services only): Displays the maximum number of hops to the timing source. 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: 1E-4: Value equals 1 x 10-4 1E-5: Value equals 1 x 10-5 1E-6 (default): Value equals 1 x 10-6 1E-7: Value equals 1 x 10-7 1E-8: Value equals 1 x 10-8 1E-9: Value equals 1 x 10-9 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 Release TN4.0.x Turin Networks Page 7-29

TransNav GUI Guide, Section 7: Advanced Parameters (Alphabetic Order) system raises a signal failed bit error rate (BERSF-V) alarm. Select one of the following values: 1E-3 (default): Value equals 1 x 10-3 1E-4: Value equals 1 x 10-4 1E-5: Value equals 1 x 10-5 Monitor RTD: Select to enable the delay measurement function for this service; default is disable (cleared checkbox). Path Mapping: Maps the VC-3 payload onto a transport path. This parameter determines how to monitor alarms and performance of the service through the intermediate nodes in the network. STS: Maps the payload into an STS path AU-4/LOVC (default): Maps the payload into an AU-4 low order virtual container AU-3/HOVC: Maps the payload into an AU-3 high order path virtual container VCRedline Circuit: Use this attribute to mark a service with Do not Deactivate. A redline circuit prevents accidental deactivation of an important service. You must first reset the redline attribute, then deactivate the service. Select one of the following options: Yes: Service is a redline circuit and cannot be deactivated No (default): Service is not a redline circuit and can be deactivated Rev Path Format: This port receives a path trace identifier in the J1 byte of the SONET/SDH frame so that the path transmitter can verify its continued connection. Select one of the following options: 16 bytes (default): Select if the receiver is a SONET port 64 bytes: Select if the receiver is another SONET port Rev Path Trace: The expected path trace identifier transmitted in the J1 byte. Enter an alphanumeric character string. Not used for unidirectional connections. Rev Signal Label: The path signal label (C2 byte in the STS path overhead) in the reverse direction of the LSP. Not used for unidirectional connections. Select one of the following values: Unequipped(00) Eqp-Nonspecific(01) (default): Equipped - Nonspecific Payload VT-Structured(02): VT-structured STS-1 SPE Locked VT(03): Locked virtual tributary (VT) mode DS3 Async(04): Asynchronous mapping for DS3 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-PPP(16): HDLC-Over-SONET mapping X.86(18) GFB (1B) POS No-Scramble (CF) Page 7-30 Turin Networks Release TN4.0.x

Chapter 3 DCS-96 Shelf Advanced Parameters (Alphabetic Order) Test Signal (FE): O.181 Test Signal (TSS1 to TSS3) mapping Setup Retry Count (end-to-end services only): The number of times the system retries a service activation request before declaring that activation failed. Select 0 to 30; default is 3. SourceDS1Mapping: For optical transmux services, select this parameter if the source path carries a channelized DS3 payload. SourceDS3Mapping: For optical transmux services, select this parameter if the source STS carries a channelized DS3 payload. SourceE1Mapping: For optical transmux services, select this parameter if the source path carries a channelized DS3 payload. Source PM Template: Select from the defined performance monitoring templates. The system default for performance monitoring thresholds is disabled for all parameters. Use the performance monitoring templates to set default thresholds or to customize threshold values. See Section 8 Maintenance and Testing, Chapter 1 Performance Monitoring, page 8-1 for information on how to use performance monitoring templates. See the Node Operations and Maintenance Guide section documentation for details on performance monitoring parameters for optical ports. TMX Port: For optical transmux services, select the port you designated as the STS1TMX resource. Transparency: Specifies if this service is transparently transporting payloads and overhead of legacy equipment. This service must have a STS-12c, STS-48c, VC-4-4c, or VC-4-16c bandwidth. The Control Data parameter must be Disabled on the interface. Select ON or OFF. On: This service has a bandwidth of STS-48c and is transparently transporting services between legacy equipment Off (default): This service is not a transparency service Unidirectional: Select for a unidirectional connection (the traffic can only travel in one direction from source to destination). The default is unselected which means that the connection is bidirectional (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. Release TN4.0.x Turin Networks Page 7-31

TransNav GUI Guide, Section 7: Advanced Parameters (Alphabetic Order) Page 7-32 Turin Networks Release TN4.0.x

SECTION 8MAINTENANCE AND TESTING SECTION 8 MAINTENANCE AND TESTING Contents Chapter 1 Performance Monitoring Viewing PM Data for Ports and Other Equipment...................... 8-2 Viewing PM Data for Services..................................... 8-4 Viewing Capacity Monitoring Data................................. 8-5 ing Performance Monitoring Templates............................. 8-6 Setting Default PM Thresholds.................................... 8-7 Customizing Performance Thresholds.............................. 8-8 Collecting PM Data............................................. 8-9 Chapter 2 Alarms Service Affecting Status......................................... 8-12 Alarm Severity Levels........................................... 8-12 Alarm Hierarchy................................................ 8-12 Alarms Tab................................................... 8-13 Alarm List on the Alarms Tab..................................... 8-14 Change Column Order...................................... 8-14 Sorting Alarm List.......................................... 8-14 StickyMode............................................... 8-14 Viewing Alarm Details........................................... 8-15 Grouping Alarms............................................... 8-16 Setting Alarm Filters............................................ 8-17 Alarm Filters, Source Tab........................................ 8-17 Alarm Filters, Probable Cause Tab................................. 8-18 Alarm Filters, Time Tab.......................................... 8-18 Alarm Filters, Severity Tab....................................... 8-19 Alarm Filters, Acknowledged By................................... 8-19 Viewing Existing Alarm Profiles.................................... 8-20 Creating New Alarm Profiles...................................... 8-21 Sorting Alarm Profiles........................................... 8-23 Saving and Importing User Preferences............................. 8-23 Chapter 3 Events Event Types.................................................. 8-26 Provisioning events......................................... 8-26 Performance events........................................ 8-26 Release TN4.0.x Turin Networks Page i

TransNav GUI Guide, Section 8 Maintenance and Testing Security events............................................ 8-26 Normal operational events.................................... 8-26 Fault events (alarms)........................................ 8-26 Event Logs.................................................... 8-26............................................................. 8-27 Events Tab.................................................... 8-28 Event List on the Events Tab...................................... 8-29 Changing Column Order..................................... 8-29 Sorting Events List.......................................... 8-29 Changing Event Retrieval Settings................................. 8-30 Viewing Event Details........................................... 8-31 Grouping Events............................................... 8-32 Setting Event Filters............................................. 8-33 Event Filters, Source Tab........................................ 8-33 Event Filters, Probable Cause Tab................................. 8-34 Event Filters, Time Tab.......................................... 8-34 Event Filters, Severity Tab........................................ 8-35 Saving and Importing User Preferences............................. 8-35 Chapter 4 Diagnostics Facility Loopback Tests.......................................... 8-38 Terminal Loopback Tests........................................ 8-38 Before Performing Loopback Tests................................. 8-39 Performing Loopbacks from Diagnostic Tab.......................... 8-39 Chapter 5 Test Access Test Access Tab............................................... 8-41 TAP Subtab Parameters......................................... 8-42 Test Access Point List........................................... 8-42 TAP Configuration Area.......................................... 8-43 TAC Subtab Parameters......................................... 8-44 Test Access Connection List...................................... 8-44 TAC Configuration Area.......................................... 8-44 Chapter 6 Software Upgrades System Software Upgrades Download............................ 8-47 System Software Upgrades Activation............................. 8-49 Bulk Config (Upgrade Helper)..................................... 8-50 Software Upgrade and Activation Shortcut Menus..................... 8-51 List of Figures Figure 8-1 DS3 Port Performance Tab.............................. 8-2 Page ii Turin Networks Release TN4.0.x

TransNav GUI Guide, Section 8 Maintenance and Testing Figure 8-2 SDH Port Performance Tab............................. 8-2 Figure 8-3 PM Tab on Path Display for Service Dialog Box.............. 8-4 Figure 8-4 Viewing VT/TU Capacity Monitoring Data................... 8-6 Figure 8-5 Performance Templates Dialog Box....................... 8-7 Figure 8-6 Set Default Thresholds................................. 8-7 Figure 8-7 Performance Templates Dialog Box....................... 8-8 Figure 8-8 Customize PM Thresholds.............................. 8-8 Figure 8-9 Synchronize New Threshold Values....................... 8-9 Figure 8-10 Performance Templates Dialog Box....................... 8-9 Figure 8-11 Collect PM Data...................................... 8-10 Figure 8-12 Map View, Alarms Tab................................. 8-13 Figure 8-13 Alert Detail (View Main) Dialog Box....................... 8-15 Figure 8-14 Alarms Menu and Alarms Tab Shortcut Menu............... 8-16 Figure 8-15 Alarm Filter (View Main) Dialog Box, Source Tab............. 8-17 Figure 8-16 Alarm Filter (View Main) Dialog Box, Probable Cause Tab..... 8-18 Figure 8-17 Alarm Filter (View Main) Dialog Box, Time Tab.............. 8-18 Figure 8-18 Alarm Filter (View Main) Dialog Box, Severity Tab............ 8-19 Figure 8-19 Alarm Filter (View Main) Dialog Box, Acknowledged By Tab.... 8-19 Figure 8-20 Alarm Profiles Dialog Box............................... 8-20 Figure 8-21 Alarm Profiles Dialog Box............................... 8-21 Figure 8-22 Alarm Profile - Default Dialog Box......................... 8-22 Figure 8-23 Map View, Events Tab................................. 8-28 Figure 8-24 Event Retrieval Settings (View Main) Dialog Box............. 8-30 Figure 8-25 Event Detail (View Main) Dialog Box...................... 8-31 Figure 8-26 Events Menu and Events Tab Shortcut Menu................ 8-32 Figure 8-27 Event Filter (View Main) Dialog Box, Source Tab............. 8-33 Figure 8-28 Event Filter (View Main) Dialog Box, Probable Cause Tab...... 8-34 Figure 8-29 Event Filter (View Main) Dialog Box, Time Tab.............. 8-34 Figure 8-30 Event Filter (View Main) Dialog Box, Severity Tab............ 8-35 Figure 8-31 Facility Loopback..................................... 8-38 Figure 8-32 Terminal Loopback.................................... 8-38 Figure 8-33 STM Port Diagnostic Tab............................... 8-39 Figure 8-34 Test Access Tab...................................... 8-41 Figure 8-35 Test Access Point Screen............................... 8-42 Figure 8-36 Test Access Connection Screen.......................... 8-44 Figure 8-37 SW Upgrade Dialog Box................................ 8-47 Figure 8-38 SW Activation Dialog Box............................... 8-49 Figure 8-39 Upgrade Helper Dialog Box............................. 8-50 Figure 8-40 Software Upgrade Shortcut Menu......................... 8-51 Figure 8-41 Software Activation Shortcut Menu........................ 8-51 List of Tables Table 8-1 Viewing VT/TU Capacity Monitoring Data................... 8-5 Release TN4.0.x Turin Networks Page iii

TransNav GUI Guide, Section 8 Maintenance and Testing Page iv Turin Networks Release TN4.0.x

SECTION 8MAINTENANCE AND TESTING Chapter 1 Performance Monitoring Introduction A node accumulates counts of various error conditions in performance monitoring (PM) registers. Depending on the particular error condition, a register increments to track the specific error. The PM data contained in the registers are used to determine when and where problems are likely to occur. Similarly, capacity monitoring of the switching capacity on VT/TU cards (modules) allows operators to monitor available resources and plan resources accordingly. This chapter explains the following information: Viewing PM Data for Ports and Other Equipment, page 8-2 Viewing PM Data for Services, page 8-4 Viewing Capacity Monitoring Data, page 8-5 ing Performance Monitoring Templates, page 8-6 Setting Default PM Thresholds, page 8-7 Customizing Performance Thresholds, page 8-8 Collecting PM Data, page 8-9 See the Node Operations and Maintenance Guide for descriptions, ranges, default thresholds of performance monitoring and capacity monitoring parameters, and procedures on managing performance. Release TN4.0.x Turin Networks Page 8-1

TransNav GUI Guide, Section 8: Maintenance and Testing Viewing PM Data for Ports and Other Equipment Viewing PM Data for Ports and Other Equipment View performance monitoring data for any port or external device by clicking the object (e.g., port, TransAccess 100 Mux, or other external equipment) in Shelf View and then clicking the Performance tab. Figure 8-1 DS3 Port Performance Tab Figure 8-2 SDH Port Performance Tab The Performance tab allows you to view the following information: Port: Displays slot number, port number, and port type. Refresh Time: Displays the last time performance monitoring information was refreshed. Page 8-2 Turin Networks Release TN4.0.x

Chapter 1 Performance Monitoring Viewing PM Data for Ports and Other Equipment Counter: Displays performance monitoring registers for the entity. For descriptions of supported registers, see the Node Operations and Maintenance Guide. Interval: Select the interval at which the node monitors performance. 15 min. A 15-minute register contains the value of one PM parameter as accumulated over a 15-minute period. Each 15-minute period begins at 0, 15, 30, or 45 minutes past the hour. 24 hour. A one-day register contains the total value of one PM parameter as accumulated over a 24-hour period. Each one-day period begins at midnight, local time on the node. Samples: A node stores 8 hours of PM data. If the Interval is 15 min, type a number between 0 and 32 and click Refresh; default is 4. The value 0 displays the current PM data. The value 32 displays the past 8 hours of PM data in 15 minute intervals. If the Interval is 24 hour, type a number between 0 and 1 and click Refresh. The value 0 displays the current PM data. The value 1 displays the performance monitoring data from the previous 24 hours, as well as the current data. Command buttons are as follows: Refresh: Refresh the Counter box with the most recent performance monitoring data. Reset: Reset counters to 0. Values will be gray with an asterisk (*) if reset or if the counter started after the interval time period. Print: Print contents of Performance tab to your local printer. Save: Save performance monitoring information to a text file on your local client workstation. Release TN4.0.x Turin Networks Page 8-3

TransNav GUI Guide, Section 8: Maintenance and Testing Viewing PM Data for Services Viewing PM Data for Services On the Service tab, click a service to select it. Right-click the selected service and select Show TxRx Paths. The Path Display for Service dialog box displays. Click the PM tab. Click a row in the Active Hop (1) column, then click Refresh (2) to view the performance monitoring data for that hop. (For protected services, click a row in the Standby Hop column.) 1 Figure 8-3 PM Tab on Path Display for Service Dialog Box The PM tab in the Path Display for Service dialog box allows you to view the following fields: Hop ID: Displays the name of the selected hop in one of the following formats: node-slot-port-sts-[vtg-vt] node-slot-port-aug1 Last Refresh Time: Displays the last time performance monitoring information was refreshed. The performance monitoring data is presented in table format with the following column headings: Counter: Displays performance monitoring data according to the performance monitoring template selected for the service during service creation. Note: The EOS Port PM byte counts include the 8-byte GFP header, allowing users to view the precise loads being handled by the EOS port. Date and Time columns: Display the date and time of the last sample performance data per counter. Samples: A node stores 8 hours of PM data. If the Interval type selected is 15 min, type a number between 0 and 32 and click Refresh; the default is 4. The value 0 displays the current PM data. The value 32 displays the past 8 hours of PM data in 15-minute intervals. Interval: Select the interval at which the node monitors performance. 2 Page 8-4 Turin Networks Release TN4.0.x

Chapter 1 Performance Monitoring Viewing Capacity Monitoring Data 15 min. A 15-minute register contains the value of one PM parameter as accumulated over a 15-minute period. Each 15-minute period begins at 0, 15, 30, or 45 minutes past the hour. 24 hour. A one-day register contains the total value of one PM parameter as accumulated over a 24-hour period. Each one-day period begins at midnight, local time on the node. If the Interval is 24 hours, type a number between 0 and 1 and click Refresh. The value 0 displays the current PM data. The value 1 displays the a performance monitoring data from the previous 24 hours, as well as the current data. Command buttons are as follows: Refresh: Refresh the Counter box with the most recent performance monitoring data. Reset: Reset counters to 0. Values will be gray with an asterisk (*) if reset or if the counter started after the interval time period. Print: Print contents of the Performance tab to your local printer. Save: Save performance monitoring information to a text file on your local client workstation. Done: Save the changes and return the the previous dialog box. Viewing Capacity Monitoring Data The following procedure describes how to view VT or TU capacity monitoring data. The capacity monitoring data shows the numbers of paths used or available at the instant the information is captured. Unlike the performance monitoring data, the capacity monitoring data is not accumulated for each period. If the VT card where the capacity is being monitored is in a 1:n protection group, only the capacity of the working card will be collected. Table 8-1 Viewing VT/TU Capacity Monitoring Data Step Procedure 1 In Shelf View, click the Performance tab and select a VT or VT-TU module. 2 On the Interval (2a) list (see the graphic in the next step), you can select 15-minute or 24-hour intervals. You can view up to thirty-two 15-minute or two 24-hour Samples (2b) current and previous. Release TN4.0.x Turin Networks Page 8-5

TransNav GUI Guide, Section 8: Maintenance and Testing ing Performance Monitoring Templates Table 8-1 Viewing VT/TU Capacity Monitoring Data (continued) Step Procedure 3 Click Refresh to re-display updated capacity monitoring values. 2a 2b 3 4 5 6 Figure 8-4 Viewing VT/TU Capacity Monitoring Data 4 If you click Reset, the counters reset to zero. 5 Click Print to print the current screen. 6 Click Save to save the capacity monitoring data to a file. 7 The Viewing VT/TU Capacity Monitoring Data procedure is complete. ing Performance Monitoring Templates You can customize performance monitoring for a specific piece of equipment or service through the use of templates. Create these templates using options on the Admin menu and assign the template to the specific piece of equipment or service. There are three purposes for the performance monitoring templates: To set the threshold values for performance monitoring parameters viewed on the Performance tab. When the counter exceeds the threshold, the node generates a threshold crossing alert (TCA) and the management system reports it to the Events tab. See Setting Default PM Thresholds, page 8-7. To customize threshold values for performance monitoring parameters for equipment or services, see Customizing Performance Thresholds, page 8-8. To collect performance monitoring on a particular piece of equipment or service and send the data to the management server. Use this information to generate reports using the report scheduler. See Collecting PM Data, page 8-9. Page 8-6 Turin Networks Release TN4.0.x

Chapter 1 Performance Monitoring Setting Default PM Thresholds Setting Default PM Thresholds Use performance monitoring templates to set the threshold values for performance monitoring parameters viewed on the Performance tab. When the counter exceeds the threshold, the node generates a threshold crossing alert (TCA) and the management system reports it to the Events tab. From the Admin menu, click Performance Templates to display the Performance Templates dialog box. Click a template type and click Properties to open the selected template for editing. Figure 8-5 Performance Templates Dialog Box On the template dialog box, click Default Thresholds to set the default threshold values for the performance monitoring parameters. If the system detects an exceeded value, the node generates a threshold crossing alert (TCA) and the management system reports it to the Events tab. Figure 8-6 Set Default Thresholds Release TN4.0.x Turin Networks Page 8-7

TransNav GUI Guide, Section 8: Maintenance and Testing Customizing Performance Thresholds See the Node Operations and Maintenance Guide for ranges and explanations of each parameter for each template type. Click OK to close the template and return to the original Performance Templates dialog box. Synchronize any template that has changed. Customizing Performance Thresholds Use performance monitoring templates to customize threshold values for performance monitoring parameters for equipment or services. From the Admin menu, click Performance Templates to display the Performance Templates dialog box. Click a template type and click Copy to copy the selected template type and open a separate dialog box for editing. Figure 8-7 Performance Templates Dialog Box The PM Configuration dialog box appears. 1 2a 2b 2c 3 4 Figure 8-8 Customize PM Thresholds Page 8-8 Turin Networks Release TN4.0.x

Chapter 1 Performance Monitoring Collecting PM Data 1. Type a unique name for the new template. 2. Enter threshold values for 15-minute and 24-hour intervals. See the Node Operations and Maintenance Guide for ranges and explanations of each parameter for each template type. The management system does not allow you to type a value that is out of range for the parameter. Note: The system could erroneously generate Ethernet PM TCA alerts if the threshold is crossed prior to setting the level for the current 15-minute or 24-hour period. 3. Click Collect All to collect the measurements and send them to the management server. 4. Click OK when you are finished. 5. Click Yes to synchronize the template to all the nodes in the network. Figure 8-9 Synchronize New Threshold Values Collecting PM Data Use a performance monitoring template to collect performance monitoring on a particular piece of equipment or service and send the data to the management server. Use this information to generate reports using the report scheduler. From the Admin menu, click Performance Templates to display the Performance Templates dialog box. Figure 8-10 Performance Templates Dialog Box Release TN4.0.x Turin Networks Page 8-9

TransNav GUI Guide, Section 8: Maintenance and Testing Collecting PM Data Click a template type and click Properties to open the selected template for editing. See the Node Operations and Maintenance Guide for ranges and explanations of each parameter for each template type. Figure 8-11 Collect PM Data Click the Collect All button to collect performance data and send it to the server. Click OK to close the template and return to the original Performance Templates dialog box. Synchronize any template that you have changed. \ Page 8-10 Turin Networks Release TN4.0.x

SECTION 8MAINTENANCE AND TESTING Chapter 2 Alarms Introduction During normal operation of the system, various conditions can arise that require attention by network operations. Alarms alert you to system operational changes. Alarms are conditions with a state of active or cleared. The TransNav graphical user interface (GUI) provides domain-wide (in Map View) and node-specific (in Shelf View) alarm information on the context-sensitive Alarms tab. Alarm management consists of monitoring, tracking, and analyzing alarms and events. This chapter contains information on retrieving alarm information: Service Affecting Status, page 8-12 Alarm Severity Levels, page 8-12 Alarm Hierarchy, page 8-12 Alarm List on the Alarms Tab, page 8-14 Viewing Alarm Details, page 8-15 Grouping Alarms, page 8-16 Setting Alarm Filters, page 8-17 Viewing Existing Alarm Profiles, page 8-20 Creating New Alarm Profiles, page 8-21 Sorting Alarm Profiles, page 8-23 Saving and Importing User Preferences, page 8-23 See Chapter 3 Events, page 8-25 for information on events. See the Node Operations and Maintenance Guide for a detailed list of alarms and recommended actions. Release TN4.0.x Turin Networks Page 8-11

TransNav GUI Guide, Section 8: Maintenance and Testing Service Affecting Status Service Affecting Status Alarm Severity Levels Alarm Hierarchy Two levels of service affecting status are used in the alarm definitions: Service Affecting (SA): Indicates that a service affecting condition has occurred and an immediate corrective action is required. Non-Service Affecting (NSA): Indicates that a non-service affecting condition has occurred. Service affecting alarms apply when protection is not available. This same alarm is considered non-service affecting if the equipment or facility is protected. Alarms listed as non-service affecting do not affect service regardless of equipment or facility protection scheme. Some alarms are always service affecting, some are always non-service affecting, and some can be either, depending on the circumstances. An alarm on unprotected equipment or facilities may be critical, whereas, this same alarm is not considered critical if the equipment or facility is protected. Alarms listed as minor or warning are not considered service affecting regardless of the protection scheme. The following severity levels, from the most severe to the least severe, are defined and used in the alarm and event definitions: Critical (red): A severe, service affecting condition has occurred. Immediate corrective action is imperative, regardless of the time of the day or day of the week. Major (orange): A hardware or software condition has occurred that indicates a serious disruption of service or the malfunctioning or failure of important circuits. This requires the immediate attention and response of a technician to restore or maintain system capability. The urgency is less than in critical situations because of a lesser immediate or impending effect on service or system performance. Minor (yellow): Trouble has occurred that does not have a serious effect on service to customers or trouble in circuits has occurred that is not essential to node operation. Corrective action should be taken in order to prevent a more serious fault. Warning (cyan): A potential or impending service affecting event may occur; no significant effects have been felt. Action should be taken to further diagnose, if necessary, and correct the problem in order to prevent it from becoming a more serious fault. In general, severity levels of Critical, Major, Minor, and Warning are reported to the Alarms and Events tabs in the GUI. A severity level of Info is reported to the Events tab only. This system conforms to the alarm reporting hierarchy set forth in the Telcordia General Requirements GR-253, ETSI 300-417-3-1, and ITU recommendation G.783. Page 8-12 Turin Networks Release TN4.0.x

Chapter 2 Alarms Alarms Tab Alarms Tab When you open the GUI, the default view is the Alarm tab on Map View. The Alarms tab displays a list of the alarms in the domain. Click on a node to display the alarm list for that specific node. You can perform the following actions from the Alarm tab: Viewing Alarm Details, page 8-15 Grouping Alarms, page 8-16 Setting Alarm Filters, page 8-17 Viewing Existing Alarm Profiles, page 8-20 Figure 8-12 Map View, Alarms Tab Alarms display on the alarm list in the following colors: Critical: Red Major: Orange Minor: Yellow Warning: Cyan (aqua) Clear: Green A node appears in the color of the most severe alarm existing on it with a caption indicating the number and type of alarm. For example, a node with three critical alarms is colored red and has the caption 3C. The caption disappears when an alarm is acknowledged; however, the color outline remains until the alarm is cleared. Release TN4.0.x Turin Networks Page 8-13

TransNav GUI Guide, Section 8: Maintenance and Testing Alarm List on the Alarms Tab Alarm List on the Alarms Tab The alarm list is context-sensitive (see Alarms Tab, page 8-13): Click a specific node in Map View to display only alarms associated with that node. Click the map outside of a specific node to display all domain-wide alarms. The number of domain-wide alarms is listed in raised Alarms. The number of displayed alarms is displayed in displayed Alarms. Both fields appear in the lower left side of the Alarms tab. In Shelf View, click a specific card or port to display only alarms associated with that card or port. Click outside the shelf to display all alarms associated with that node. Column headings on the Alarms tab are as follows: AlarmID: Unique alarm identification number assigned by the system Source: Source of alarm ProbCause: Probable cause of alarm SA (Service Affecting): The checkbox is selected if alarm represents a service affecting condition and immediate corrective action is required. The checkbox is clear if alarm is not service affecting. Time: Time the alarm occurred Sev: Alarm severity AckBy: Name of the user who acknowledged the alarm. If alarm has not been acknowledged, the field flashes. Change Column Order To change the order in which a column displays on the Alarms tab, hold down the Shift key, then click and drag the column heading to the desired location. Sorting Alarm List Click a column heading to sort the alarms list by that category in ascending order. Click the column heading again to switch from ascending to descending order. Hold down the Shift key and click a second column heading to sort the second category within the first category. Hold down the Shift key and click the second column again to switch between ascending and descending order within the first category. StickyMode Selecting this check box freezes the current alarm display which can be useful during troubleshooting. Alarms remain in the order displayed at the time the checkbox was selected, regardless of a change in severity level. For example, if alarms are currently sorted by decreasing severity level, critical alarms would be displayed first, followed by major, minor, and so on. New alarms are not reported, but deleted alarms are removed (when a node is deleted, all of its alarms are deleted). If the StickyMode check box is clear, when a critical alarm is cleared, it is moved to the bottom of the list. If the StickyMode check box is selected, that alarm remains at the top of the list, while its severity changes from Critical to Clear. Important: Turin recommends opening a new window before selecting StickyMode so that new alarms continue to be reported. Page 8-14 Turin Networks Release TN4.0.x

Chapter 2 Alarms Viewing Alarm Details Command buttons on the Alarms tab are as follows: Detail View: View highlighted alarm details. Displays Alert Detail (View Main) dialog box. Set Filters: Set filters for alarms to be displayed. Displays the Alarm Filter (View Main) dialog box. New Window: Open an independent Alarm View dialog box, which inherits the alarm filters set for the Alarms tab. You can change the filters on this dialog box by clicking Set Filters. Print: Print contents of Alarms tab. Save: Save alarm information to a text file. Viewing Alarm Details On the Alarms tab, select an alarm from the list. Click the Detail View command button or double-click the selected alarm. The Alert Detail (View Main) dialog box displays. Figure 8-13 Alert Detail (View Main) Dialog Box On the Alert Detail (View Main) dialog box, you can view the following information about the alarm: ID: Alarm identification number Probable Cause: Describes the probable cause of the alarm Time: Time the alarm was created Description: Description of the alarm Severity: Severity of the alarm ServiceID: Service identification number Source: Source of the alarm Acknowledged By: Name of the user who acknowledged the alarm Annotations box: Enter annotations on the alarm Release TN4.0.x Turin Networks Page 8-15

TransNav GUI Guide, Section 8: Maintenance and Testing Grouping Alarms Command buttons are as follows: Clear: Clear the Annotations box. Add Annotation: Add the contents of the Annotations box to the alarm detail. This information is added to the bottom box. Acknowledge: Acknowledge the alarm. The acknowledgement is added to the bottom box. Done: Close the dialog box. Grouping Alarms Select an alarm listed on the Alarms tab. Hold down the Ctrl key and select other alarms to group them. You can now perform operations on a group of alarms. You can perform operations on selected alarms in two additional ways: Click the Alarms menu Right-click an alarm or group of alarms The following shortcut menu displays. Figure 8-14 Alarms Menu and Alarms Tab Shortcut Menu Menu selections are as follows: Set Filters: Display the Alarm Filter (View Main) dialog box. New Window: Open an independent Alarm View dialog box, which inherits the alarm filters set for the Alarms tab. You can change the filters on this dialog box by clicking Set Filters. Acknowledge: Acknowledge the alarm. Detail View: View highlighted alarm details. Displays Alert Detail (View Main) dialog box. Page 8-16 Turin Networks Release TN4.0.x

Chapter 2 Alarms Alarm Filters, Source Tab Setting Alarm Filters On the Alarms tab, click Set Filters. The Alarm Filter (View Main) dialog box displays. Figure 8-15 Alarm Filter (View Main) Dialog Box, Source Tab The Alarms Filter (View Main) dialog box displays the following tabs: Alarm Filters, Source Tab, page 8-17 Alarm Filters, Probable Cause Tab, page 8-18 Alarm Filters, Time Tab, page 8-18 Alarm Filters, Severity Tab, page 8-19 Alarm Filters, Acknowledged By, page 8-19 After you make changes to any filter, click Apply, then click Done. Click Apply to apply changes to the filter. Click Done to close the dialog box. Alarm Filters, Source Tab The default tab when you click the Set Filters command button from the Alarms tab (Figure 8-15 Alarm Filter (View Main) Dialog Box, Source Tab). You can choose to include or exclude alarms from specific sources from being displayed on the Alarms tab. Select the Active checkbox to make the Source filter active. Clear the Active check box to make the Source filter inactive. Sources of currently active alarms are listed in the left box. To display alarms from a specific source, highlight the source in the left box and click the right arrow to move it to the right box. Click Include. To exclude a list of sources, click Exclude. Use the * as a wildcard character; for example, typing Cypress* in the Available Sources box and clicking the right arrow will include all alarm sources whose name begins with Cypress. Release TN4.0.x Turin Networks Page 8-17

TransNav GUI Guide, Section 8: Maintenance and Testing Alarm Filters, Probable Cause Tab Alarm Filters, Probable Cause Tab Click the Probable Cause tab to include or exclude the display of specific alarm types on the Alarms tab. Figure 8-16 Alarm Filter (View Main) Dialog Box, Probable Cause Tab Select the Active checkbox to activate the Probable Cause filter. Clear the Active checkbox to make the Probable Cause filter inactive. To display a specific alarm type, highlight the alarm in the left box and click the right arrow to move it to the right box. Click Include. To exclude a list of alarm types from being displayed, click Exclude. Alarm Filters, Time Tab Click the Time tab to specify the time periods within which to display alarms. Figure 8-17 Alarm Filter (View Main) Dialog Box, Time Tab Select the Active checkbox to make the Time filter active. Clear the Active check box to make the Time filter inactive. Click one of the three following option buttons: Before: Display alarms which occurred before the time specified. After: Display alarms which occurred after the time specified. Between _ and _: Display alarms which occurred between the times specified. Click the up arrow to go forward in time and the down arrow to go back in time. Page 8-18 Turin Networks Release TN4.0.x

Chapter 2 Alarms Alarm Filters, Acknowledged By Alarm Filters, Severity Tab Click the Severity tab to specify the severity of alarms you want to display. Figure 8-18 Alarm Filter (View Main) Dialog Box, Severity Tab Select the Active checkbox to activate the Severity filter. Clear the Active check box to make the Severity filter inactive. Select one or more of the following alarm severities to display: Critical Major Minor Warning Clear Alarm Filters, Acknowledged By Click the Acknowledged By tab to display alarms acknowledged by specific users. Figure 8-19 Alarm Filter (View Main) Dialog Box, Acknowledged By Tab To display alarms acknowledged by a specific user, highlight the name in the left box and click the right arrow to move it to the right box. Click Include. To exclude alarms acknowledged by a list of users, click Exclude. Release TN4.0.x Turin Networks Page 8-19

TransNav GUI Guide, Section 8: Maintenance and Testing Viewing Existing Alarm Profiles Viewing Existing Alarm Profiles Alarm profiles allow you to change the severity of alarms when they are either service affecting or non-service affecting. You can enable or disable alarm generation. From the Admin menu, select Alarm Profiles to display the Alarm Profiles dialog box. Figure 8-20 Alarm Profiles Dialog Box There are default alarm profiles in the system. For a detailed list of all system alarms in alphabetical order, their default severities, service affecting status, and recommended actions, see the Node Operations and Maintenance Guide. ds1_ptp: DS1 port ds_ptp: DS3 port e1_ptp: E1 port e3_ptp: E3 port eos: EOS port eos_ctp: EOS port member lag: link aggregation group sdh_eos: SDH EOS port sdh_eos_ctp: SDH EOS port member ethernet_ptp: Ethernet port sdh_hp: SDH high order path (VC4 or VC3) sdh_lp: SDH VC3 low order path sdh_ptp: SDH port server: TransNav server platform shelf: Traverse node sonet_ptp: SONET port sonet_sts: SONET STS path sonet_vt: SONET VT path Page 8-20 Turin Networks Release TN4.0.x

Chapter 2 Alarms Creating New Alarm Profiles t100: TransAccess 100 Mux ta200: TransAccess 200 Mux te50: TraverseEdge 50 You associate a specific alarm profile with a specific resource by using the Config tab for the resource. Double-click the default alarm profile to change the severity of alarms and to disable or enable the generation of alarms. For details on alarm severity levels, see Alarm Severity Levels, page 8-12. Command buttons are: Copy: Copy the selected alarm profile and display an Alarm Profile dialog box. Properties: Display the Alarm Profile dialog box for the selected alarm profile. Sync: Synchronize the selected alarm profile, making it available to all nodes in the domain. After Sync is clicked, the Sync Status column displays Synchronizing, then Synchronized or Not Synchronized. A Not Synchronized status generates an alarm. Delete: Delete the selected alarm profile. Displays a dialog box reading, Are you sure you would like to delete [alarm profile name]? Click Yes or No. Done: Close the dialog box. Creating New Alarm Profiles You can create a new alarm profile for a specific resource. Define a specific alarm profile by selecting Alarm Profiles from the Admin menu. Associate a specific alarm profile with a specific resource by using the Config tab for the resource. For a detailed list of all system alarms in alphabetical order, their default severities, service affecting status, and recommended actions, see the Node Operations and Maintenance Guide. From the Admin menu, select Alarm Profiles. The Alarm Profiles dialog box displays. Figure 8-21 Alarm Profiles Dialog Box Release TN4.0.x Turin Networks Page 8-21

TransNav GUI Guide, Section 8: Maintenance and Testing Creating New Alarm Profiles From the Alarm Profiles dialog box, select a type of profile from the Type menu and either double-click the selected alarm type or click Add. The Alarm Profile - Default dialog box displays. Figure 8-22 Alarm Profile - Default Dialog Box The Alarm Profile dialog box allows you to view and set the following information for each alarm profile: Name: Enter the name of the alarm profile. Type: Displays the type selected. Name (column heading): Displays the name of the alarm based on the type selected. Probable Cause: Displays the probable cause of the alarm. Severity NSA (Non-Service Affecting): User-configurable severity of the alarm when it is non-service affecting. Select from the following severity levels (for details on alarm severity levels, see Alarm Severity Levels, page 8-12): Critical Major Minor Warning Clear Info Severity SA (Service Affecting): User-configurable severity of the alarm when it is service affecting. Select from the following severity levels (for details on alarm severity levels, see Alarm Severity Levels, page 8-12): Critical Major Minor Warning Clear Info Page 8-22 Turin Networks Release TN4.0.x

Chapter 2 Alarms Saving and Importing User Preferences Service Affecting: Select the box to make the alarm service affecting. Clear the check box to make the alarm non-service affecting (See Service Affecting Status, page 8-12 for definitions). Enabled: Select the box to generate alarms. Clear the check box to suppress alarm generation. Command buttons are as follows: OK: Save the alarm profile. On the Synchronize Alarm Profile dialog box, click Yes to make the alarm profile available to all nodes in the domain or No. Cancel: Cancel the alarm profile and close the dialog box. Sorting Alarm Profiles Saving and Importing User Preferences Click a column heading to sort the alarms by that category. The Name and Probable Cause columns can be sorted in alphabetical (descending) or reverse alphabetical (ascending) order. The Severity NSA and Severity SA columns can be sorted in ascending or descending severity. The ServiceAffecting and Enabled columns can be sorted by select/clear. Click the column heading again to switch from one sorting criterion to the other. You can save alarm filter and sort settings and import these settings from another user. For details, see Section 2 Administrative Tasks, Chapter 3 User Preferences, Saving and Importing User Preferences, page 2-16. Release TN4.0.x Turin Networks Page 8-23

TransNav GUI Guide, Section 8: Maintenance and Testing Saving and Importing User Preferences Page 8-24 Turin Networks Release TN4.0.x

SECTION 8MAINTENANCE AND TESTING Chapter 3 Events Introduction During normal operation of the system, various conditions can arise that require attention by network operations. Events are state-less alerts that are sent to the management system. The TransNav graphical user interface (GUI) provides domain-wide (in Map View) and node-specific (in Shelf View) event information on the context-sensitive Events tab. Fault management consists of monitoring, tracking, and analyzing alarms and events. This chapter contains information on retrieving event information: Event Types, page 8-26 Event Logs, page 8-26 Event List on the Events Tab, page 8-29 Saving and Importing User Preferences, page 8-35 See Chapter 2 Alarms, page 8-11 for information on alarms. See the Node Operations and Maintenance Guide for a detailed list of events and recommended actions. Release TN4.0.x Turin Networks Page 8-25

TransNav GUI Guide, Section 8: Maintenance and Testing Event Types Event Types Event Logs Events alert the operator to changes to the system. Each of these changes are logged and can be any one of the following event types: Provisioning events. The node has made a change to its configuration in response to a request from a management entity. Performance events. The value of a Performance Management (PM) parameter has crossed a provisioned threshold. This threshold crossing alert (TCA) may indicate service deterioration and require operator attention. Security events. A user has logged in or out of the node, an attempted login has failed, or a user has made some change to the user account database. Normal operational events. Normal and expected occurrences, such as initialization completed or control plane connection established with other nodes. They are logged for information only. Fault events (alarms). Fault conditions that may affect service and require operator attention. Fault events generate and clear alarms. The system raises an alarm when it first detects a fault condition. While the fault condition persists, the alarm is active. When the system detects that a fault condition no longer exists, it clears the alarm. The clearing may be automatic or a result of an operator action (e.g., replacing a bad card). All events (including alarm fault events) are logged on either the Traverse General Control Card (GCM) or TraverseEdge 100 System card. The events logged are not persistent reboots clear the logs. For user-accessible, longer-term secure storage, an Event Log is stored on the TransNav server. This log provides easy access to information about recent events. Included in the TransNav server Event Log is the following information: Type of event (configuration, fault, performance, and security) Timestamp Component or subsystem detecting the event Descriptive text about the event The Event Log maintains a configurable number of events for a specified length of time. The oldest events are deleted after the limit has been reached; the default is 30 days. This length of time is also configurable. Turin recommends performing regular backups of the log files. One way to accomplish this is to use the Report Scheduler and set up a regularly generated report on events. For details, see the TransNav Management System GUI Guide, Section 2 Administrative Tasks, Chapter 4 Administrative Tasks, Generating Reports, page 2-25. Page 8-26 Turin Networks Release TN4.0.x

Chapter 3 Events Release TN4.0.x Turin Networks Page 8-27

TransNav GUI Guide, Section 8: Maintenance and Testing Events Tab Events Tab From Map View, click the Events tab. The Events tab displays a list of events. You can perform the following actions from the Events tab: Changing Event Retrieval Settings, page 8-30 Viewing Event Details, page 8-31 Grouping Events, page 8-32 Setting Event Filters, page 8-33 Figure 8-23 Map View, Events Tab Column headings are as follows: EventID: Unique event identification number assigned by the system Source: Source of event ProbCause: Probable cause of event Time: Time the event occurred Sev: Event severity Desc: A description of the event. The text wraps to show the entire description if Wrap line in Description Column checkbox is selected in the Event Retrieval Settings (View Main) dialog box, shown in Figure 8-24. Page 8-28 Turin Networks Release TN4.0.x

Chapter 3 Events Event List on the Events Tab Event List on the Events Tab The event list is context-sensitive (see Events Tab, page 8-28). Click a specific node in Map View to display only events associated with that node. Click the map outside of a specific node to display all domain-wide events. The number of domain-wide events is listed in queried Events. The number of displayed events is displayed in displayed Events. Both fields appear in the lower left of the Events tab. In Shelf View, click a specific card or port to display only events associated with that card or port. Click outside the shelf to display all events associated with that node. Changing Column Order To change the order in which a column is displayed on the Events tab, hold down the Shift key and click and drag a column heading to the desired location. Sorting Events List Click a column heading to sort the events list by that category. Column headings can be sorted in ascending or descending order. Click the column heading again to switch from ascending to descending order. Hold down the Shift key and click a second column heading to sort the second category within the first category. Hold down the Shift key and click the second column again to switch between ascending and descending order within the first category. Command buttons are as follows: Settings: Specify the time period and refresh interval within which to display events. Displays Event Retrieval Settings View (Main) dialog box. See Changing Event Retrieval Settings, page 8-30. Refresh: Display events according to Event Retrieval Settings View (Main) dialog box (Figure 8-24). Detail View: View highlighted event details. Displays the Event Detail (View Main) dialog box. See Viewing Event Details, page 8-31. Set Filters: Set filters to display events. Displays the Event Filter (View Main) dialog box. See Setting Event Filters, page 8-33. New Window: Open an independent Event View dialog box, which inherits the event filters set for the Events tab. You can change the filters on this dialog box by clicking Set Filters. Print: Print contents of Events tab. Save: Save event information to a text file. Release TN4.0.x Turin Networks Page 8-29

TransNav GUI Guide, Section 8: Maintenance and Testing Changing Event Retrieval Settings Changing Event Retrieval Settings From the Events tab, click the Settings button to specify the time period and refresh interval within which to display events. The Event Retrieval Setting (View Main) dialog box displays. Figure 8-24 Event Retrieval Settings (View Main) Dialog Box The Event Retrieval Settings (View Main) dialog box allows you to set the following information: Retrieve Events up to: Select the ending time to retrieve events: Now (default) Define. When this is selected, the field is replaced with a date/time entry. Use the up and down arrows or enter the ending time to retrieve events. for: Select the amount of time to retrieve events: 1 min 5 min 15 min (default) 30 min 45 min 1 hr 2 hr 4 hr Automatic Refresh: Select to automatically retrieve events according to the Retrieve Events up to, for, and every settings. Clear the checkbox to manually retrieve events. every: Select the refresh interval. Valid values are: 1 min 5 min 15 min (default) 30 min 45 min 1 hr 2 hr 4 hr Wrap line in Description Column: Select this checkbox to show the entire description of the event in the Events tab, Desc column. Command buttons are as follows: Refresh Now: Retrieve events according to the settings in the dialog box. Ok: Close the dialog box. Page 8-30 Turin Networks Release TN4.0.x

Chapter 3 Events Viewing Event Details Viewing Event Details From the Events tab, select an event from the events list. Double-click the selected event or click the Detail View button. The Event Detail (View Main) dialog box displays. Figure 8-25 Event Detail (View Main) Dialog Box The Event Detail (View Main) dialog box allows you to view the following information about the selected event: ID: Event identification number Probable Cause: Describes the probable cause of the event Creation Time: Time the event was created Description: Description of the event Severity: Severity of the event Source: Source of the event Click Done to close the dialog box. Release TN4.0.x Turin Networks Page 8-31

TransNav GUI Guide, Section 8: Maintenance and Testing Grouping Events Grouping Events From the Events tab, select an event from the event list. Hold the Ctrl key down and select other events to add to the group. You can now perform operations on a group of events. You can perform operations on selected events in two additional ways: Click the Events menu. Right-click an event or group of events. The following shortcut menu is displayed: Figure 8-26 Events Menu and Events Tab Shortcut Menu Menu selections are as follows: Set Filters: Display the Event Filter (View Main) dialog box. New Window: Open an independent Event View dialog box, which inherits the event filters set for the Events tab. You can change the filters on this dialog box by clicking Set Filters. Detail View: View highlighted event details. Displays Event Detail (View Main) dialog box. Settings: Specify the time period and refresh interval within which to display events. Displays the Event Retrieval Settings (View Main) dialog box. Refresh: Display events according to the Event Retrieval Settings (View Main) dialog box. Page 8-32 Turin Networks Release TN4.0.x

Chapter 3 Events Event Filters, Source Tab Setting Event Filters On the Events tab, click Set Filters. The Event Filter (View Main) dialog box displays. Figure 8-27 Event Filter (View Main) Dialog Box, Source Tab The Event Filter (View Main) dialog box has the following tabs: Event Filters, Source Tab, page 8-33 Event Filters, Probable Cause Tab, page 8-34 Event Filters, Time Tab, page 8-34 Event Filters, Severity Tab, page 8-35 After you make changes to any filter, click Apply, then click Done. Click Apply to apply changes to the filter. Click Done to close the dialog box. Event Filters, Source Tab You can choose to include or exclude events from specific sources from being displayed on the Events tab. Select the Active checkbox to make the Source filter active. Clear the Active checkbox to make the Source filter inactive. To display events from a specific source, highlight the source in the left box and click the right arrow to move it to the right box. Click Include. To exclude a list of sources, click Exclude. Use the * as a wildcard character. For example, typing Cypress* in the Available Sources box and clicking the right arrow would include all event sources whose name begins with Cypress. Release TN4.0.x Turin Networks Page 8-33

TransNav GUI Guide, Section 8: Maintenance and Testing Event Filters, Probable Cause Tab Event Filters, Probable Cause Tab Click the Probable Cause tab to include or exclude specific event types from displaying on the Events tab. Figure 8-28 Event Filter (View Main) Dialog Box, Probable Cause Tab Select the Active checkbox to make the Probable Cause filter active. Clear the Active checkbox to make the Probable Cause filter inactive. To display a specific event type, highlight the event in the left box and click the right arrow to move it to the right box. Click Include. To exclude a list of event types, click Exclude. Event Filters, Time Tab Click the Time tab to specify the time periods within which to display events. Figure 8-29 Event Filter (View Main) Dialog Box, Time Tab Select the Active checkbox to make the Time filter active. Clear the Active checkbox to make the Time filter inactive. Click one of the three following option buttons: Before: Display events which occurred before the time specified. After: Display events which occurred after the time specified. Between _ and _: Display events which occurred between the times specified. Click the up arrow to go forward in time and the down arrow to go back in time. Page 8-34 Turin Networks Release TN4.0.x

Chapter 3 Events Saving and Importing User Preferences Event Filters, Severity Tab Click the Severity tab to specify the severity of events to display. Figure 8-30 Event Filter (View Main) Dialog Box, Severity Tab Select the Active checkbox to make the Severity filter active. Clear the Active checkbox to make the Severity filter inactive. Select one or more of the following event severities to display: Critical Major Minor Warning Clear Info Saving and Importing User Preferences You can save alarm and event filter and sort settings and import these settings from another user. For details, see Section 2 Administrative Tasks, Chapter 3 User Preferences, Saving and Importing User Preferences, page 2-16. Release TN4.0.x Turin Networks Page 8-35

TransNav GUI Guide, Section 8: Maintenance and Testing Saving and Importing User Preferences Page 8-36 Turin Networks Release TN4.0.x

SECTION 8MAINTENANCE AND TESTING Chapter 4 Diagnostics Introduction Perform diagnostic loopbacks to troubleshoot ports and link spans using the TransNav management system. WARNING! Loopback tests interrupt traffic flow; do not perform them on nodes providing service. This chapter describes the following information: Facility Loopback Tests, page 8-38 Terminal Loopback Tests, page 8-38 Before Performing Loopback Tests, page 8-39 Performing Loopbacks from Diagnostic Tab, page 8-39 See the Node Operations and Maintenance Guide for detailed procedures on performing diagnostics on the Traverse system. Release TN4.0.x Turin Networks Page 8-37

TransNav GUI Guide, Section 8: Maintenance and Testing Facility Loopback Tests Facility Loopback Tests In general, a facility loopback connects the incoming received signal to the associated transmitter in the return direction. Tributary module OC-N/STM-N transport module Test Set LIU AIS LIU Facility under loopback test Node Figure 8-31 Facility Loopback During a facility loopback, an alarm indication signal (AIS) is inserted and sent to the far end. A facility loopback tests the integrity of the line interface unit on the card. Terminal Loopback Tests In a terminal loopback, the signal that is about to be transmitted is connected to the associated, incoming receiver. Tributary module OC-N/STM-N transport module Bridged signal LIU LIU Test Set Facility under loopback test Node Figure 8-32 Terminal Loopback During a terminal loopback, the test signal is bridged back to the test set to verify the receiver associated with the facility and the integrity of the transmitted signal. An AIS is not inserted and sent to the far end. Before performing a terminal loopback, a service must be set up between this port and another port on the same node. Page 8-38 Turin Networks Release TN4.0.x

Chapter 4 Diagnostics Performing Loopbacks from Diagnostic Tab Before Performing Loopback Tests Performing Loopbacks from Diagnostic Tab If the facility under loopback test is an STM port, the Control Data parameter must be disabled. (Click the port, click the Config tab, select Disabled in Control Data.) If the facility under loopback test is an OC port, the Control Data parameter must be disabled. (Click the port, click the Config tab, select Disabled in Control Data.) If the facility under loopback test is an Ethernet port, it cannot be in a Link Aggregation Group or have active Ethernet services. The facility under loopback test cannot be part of an MS-SP ring or 1+1 MSP protection group. The facility under loopback test cannot be part of a BLSR or 1+1 APS protection group. The facility must be in an unlocked administrative state before performing any loopback commands. To unlock a port that is currently locked, click the Locked icon in the lower left corner to display the Unlocked icon, then click Apply. From Shelf View, click a port, then click the Diagnostic tab. The Port Diagnostic screen displays. Figure 8-33 STM Port Diagnostic Tab The Diagnostic tab allows you to view and set the following information: Label: Displays the node name, slot number, card type, and port number. Type: Displays the card type. Slot Number: Displays the slot number. Port Number: Displays the port number. Loopback: Select the type of loopback to apply to this port. Clear (default): Clear loopback command. Facility: Perform a facility loopback on this port. Terminal: Perform a terminal loopback on this port. Test Signal Type (for DS3 ports only): Select one of the following signal types: Clear (default) PRBS (Pseudo random bit sequence): 2 23-1 PRBS Fixed-24Bit: Repeating 24-bit pattern (101110111011101110111011) Release TN4.0.x Turin Networks Page 8-39

TransNav GUI Guide, Section 8: Maintenance and Testing Performing Loopbacks from Diagnostic Tab Command buttons are as follows: Apply: Change the loopback status to that specified in the Loopback parameter. A dialog box displays which reads, Are you sure you would like to change the loopback status? Changing the loopback status might cause some services to lose traffic. Click Yes to change the loopback status or No. Cancel: Cancel loopback status change request and revert to Clear. Page 8-40 Turin Networks Release TN4.0.x

SECTION 8MAINTENANCE AND TESTING Chapter 5 Test Access Introduction Test Access Tab (SONET network only) Traverse Test Access on digital cross-connect (DCS3/1) systems and Add-Drop Multiplexer (ADM) systems provides for non-intrusive monitoring and intrusive split testing of DS3/STS-1 and DS1/VT1.5 digital signals. 1 See the Node Operations and Maintenance Guide for complete information on the test access features. From the Shelf View, click the Test Access tab. The Test Access Point screen displays. Figure 8-34 Test Access Tab Select the TAP (test access point) or TAC (test access connection) subtab on the right side of the screen. See the following sections for explanations of the parameters on the screen: TAP Subtab Parameters, page 8-42 TAC Subtab Parameters, page 8-44 1 (SDH network only) Test access is planned for a future release. Release TN4.0.x Turin Networks Page 8-41

TransNav GUI Guide, Section 8: Maintenance and Testing TAP Subtab Parameters TAP Subtab Parameters In the Test Access screen in Shelf View, make sure the TAP subtab is selected. Click New to add a new test access point. List Config Area Figure 8-35 Test Access Point Screen The Test Access Point screen displays. There are two parts to this screen: Test Access Point List, page 8-42 TAP Configuration Area, page 8-43 Test Access Point List On the Test Access Point List screen, the list area at the top of the screen displays the following fields: ID: A user-assigned identifier between 1 and 128; default is 1. Type: Indicates the type of access point. Valid values are FAD (single facility access digroup) or DFAD (dual facility access digroup); default is FAD. CTP Type 1: The connection termination point type for this test access point. FAD 1: The location of the FAD in the format: slot-port-[sts]. CTP Type 2: If the Type parameter is DFAD, this is the second termination point type for the test access point. FAD 2: The location of the FAD in the format: slot-port-[sts]. State: Displays the state of the test access point. Available: Indicates the test access point is available to start testing. Connected: Indicates the test access point is connected. In-Use: Indicates the test access point is being used by a test access connection. Description: Displays the user-defined alphanumeric character string that identifies this test access point. Page 8-42 Turin Networks Release TN4.0.x

Chapter 5 Test Access TAP Configuration Area TAP Configuration Area On the Test Access Point List screen, click New to add a new test access point. The following configuration parameter fields appear at the bottom of the screen: ID: Identifies the test access point. Select a number from 1 to 128; default is 1. Type: The type of facility access group. FAD. Single facility access digroup. DFAD. Dual facility access digroup. Endpoint1: Click the field. The Choose an Endpoint dialog box displays. Select the first endpoint of the test access. Description: Enter an alphanumeric character string to describe this test access point. Do not use any other punctuation or special characters. Format: General (default) Endpoint2: If the Type parameter selected is DFAD, click the Endpoint 2 field. The Choose an Endpoint dialog box displays. Select the second endpoint for the test access point. Command buttons are as follows: New: Click New to create a new test access point. The configuration area displays. Delete: Click a row in the test access point list, then click Delete to remove the test access point from the system. A confirmation message displays. Click Yes to delete the TAP. Add: Click New, configure the test access point, then click Add to add the test access point to the test access point list. Cancel: At any point in the process, click Cancel stop the process and return to the main Test Access screen. Release TN4.0.x Turin Networks Page 8-43

TransNav GUI Guide, Section 8: Maintenance and Testing TAC Subtab Parameters TAC Subtab Parameters In Shelf View, click the Test Access tab, then click the TAC subtab. The Test Access Connection screen displays. List Config Area Figure 8-36 Test Access Connection Screen The Test Access Connection screen allows you to view and configure the following parameters: Test Access Connection List, page 8-44 TAC Configuration Area, page 8-44 Test Access Connection List TAC Configuration Area The list area at the top on the Test Access Connection screen displays the following fields: ID: A user-assigned identifier of the TAP linked to this test access connection. Name: Displays the user-defined name of the test access connection. Customer: Displays the customer selected for this test access connection. Mode: Displays the mode for this connection. See the section, TAC Configuration Area, page 8-44, for descriptions of the available modes. TAP ID: Displays the test access point identifier of this connection; default is 1. Service ID: Displays the service for this connection. CTP Type: Displays the connection termination point for this connection. Port: Select the port for the connection. State: Displays the state of the test access connection from the following selections: Available. If the test access connection is available to start testing. Connected. If the test access connection is connected. On the Test Access Connection List screen, click New to add a new test access connection. The configuration area allows you to configure the following parameters to test a service: Name: Enter an alphanumeric name for this test access connection. Description: Enter an alphanumeric description for test access connection. Do not use any other punctuation or special characters. Page 8-44 Turin Networks Release TN4.0.x

Chapter 5 Test Access TAC Configuration Area Mode: Select the mode for the test access connection: Monitor-E: Monitor unidirectional data flow from ingress to egress termination point. Monitor-F: Monitor unidirectional data flow from egress to ingress termination point. Monitor-EF: Monitor bidirectional data flow from both the ingress and egress termination points. Split-A: Series split on the ingress termination point to test data flow from the ingress toward the egress termination point. Split-B: Series split on the egress termination point to test data flow from the egress toward the ingress termination point. Split-E: Per side split on the ingress termination point to test the ingress circuit. Split-F: Per side split on the egress termination point to test the egress circuit. Split-EF: Per side split on both the ingress and egress termination points to test circuits simultaneously. ID: Select the identifier (1 to 128) of the test access point for this connection. Customer: Select a pre-defined customer from the list. The default is No Customer Selected. Format: Default is General. Endpoint: Double-click the field. The Choose an Endpoint dialog box displays. Select the endpoint for this test access connection. Command buttons are as follows: New: Click New to create a new test access connection. Delete: Click a row in the test access connection list, then click Delete to remove the test access connection from the system. Add: Click New, configure the test access connection, then click Add to add the test access connection to the TAC list. Cancel: At any point in the process, click Cancel to stop the process and return to the Test Access Connection screen. Release TN4.0.x Turin Networks Page 8-45

TransNav GUI Guide, Section 8: Maintenance and Testing TAC Configuration Area Page 8-46 Turin Networks Release TN4.0.x

SECTION 8MAINTENANCE AND TESTING Chapter 6 Software Upgrades Introduction This chapter describes the following administrative functions selected through the Admin menu on the graphical user interface (GUI): System Software Upgrades Download, page 8-47 System Software Upgrades Activation, page 8-49 Bulk Config (Upgrade Helper), page 8-50 Software Upgrade and Activation Shortcut Menus, page 8-51 Important: Software upgrade requires a specified order. You must first upgrade the management server software, followed by control cards, and then line cards. For step-by-step software upgrade procedures, refer to Node Operations and Maintenance Guide. Important: To upgrade management server software, see the TransNav Management System Server Guide. System Software Upgrades Download Click a node in Map View. From the Admin menu, select SW Upgrade to display the SW Upgrade dialog box. Figure 8-37 SW Upgrade Dialog Box The SW Upgrade dialog box allows you to enter the following information: Server IP Address: IP address of the machine where the new software resides. Release TN4.0.x Turin Networks Page 8-47

TransNav GUI Guide, Section 8: Maintenance and Testing System Software Upgrades Download Username: Name of user on the machine where the new software resides. Base Path: Path where the new software resides. Password: Password of the user name on the machine where the new software resides. The following items are listed for each card in the node: Slot #: Slot number of the card. Card Type: Type of card inserted in the slot. Relative Path: The system automatically fills in the relative path to the card for the software upgrade. Download Time: The time it takes to transfer new software from the server to the backup partition of the card. Click the box corresponding to the card. Use the up and down arrows or type in the box to specify the download time. Download Status: Displays the software download status. Valid values are: NONE INPROGRESS FAILED OK ABORTED Upgrade Type: Select one of the following upgrade types: INIT: Completely erase backup partition of card and copy all files. MERGE: Do not erase backup partition; overwrite existing files and add new files. Current SW Version: Current software version of the card Standby SW Version: Software version on standby (in the card backup partition) for the upgrade Both of these parameters are in the format A.B.C.D, where: A = major software release number B = minor software release number C = release build number D = software patch to build Command buttons are as follows: Bulk Config: Display the Bulk Config (Upgrade Helper), page 8-50 dialog box. The Upgrade Helper allows you to select the download time, activation time, and upgrade type for all of the cards in the node. Update: Update configuration information. Revert: Cancel configuration information. Done: Close dialog box. You can also view the following information on the selected card s Config tab: Slot Number. Selected card slot number Type: Selected card type ICI: Current compatibility identifier. This identifier indicates the lowest software version compatibility with that of the highlighted card s Current SW Version. Module ID: A unique module (card) identifier. Page 8-48 Turin Networks Release TN4.0.x

Chapter 6 Software Upgrades System Software Upgrades Activation System Software Upgrades Activation Click a node in Map View. From the Admin menu, select SW Activation to display the SW Activation dialog box. Figure 8-38 SW Activation Dialog Box The SW Activation dialog box allows you to enter the following information: The following items are listed for each card in the node: Slot #: Slot number of the card. Card Type: Type of card inserted in the slot. Activate Time: Click the box corresponding to the card. Use the up and down arrows or type in the box to specify the activation time. If two control cards are set to the same activation time, the standby control card will reboot first, followed by the active control card. Act (Activation) Status: Displays the software activation status. Activation refers to the reboot of the card from the backup partition (the part which contains the new software). Valid values are: NONE INPROGRESS FAILED OK Act (Activation) Type: Select one of the following: NSA (Non-Service-Affecting) (default): Do not allow activation of card if services are active on that card. SA (Service-Affecting): Activate card, even if services are active on that card. SPARE (Non-Service-Affecting): Reboot the spare control card. Warm Rbt: A hitless warm reboot function to restart the processor without affecting traffic. Ignore FPGA Upgd: A user-selectable FPGA upgrade capability. You can accept or ignore the FPGA card software change. Important: Turin recommends using this capability only after careful consideration has been taken to assure the FPGA change for the card is non-critical in nature to your deployment. Current SW Version: Current software version of the card Current SW Version: Current software version of the card Standby SW Version: Software version on standby (in the card backup partition) for the upgrade Command buttons are as follows: Release TN4.0.x Turin Networks Page 8-49

TransNav GUI Guide, Section 8: Maintenance and Testing Bulk Config (Upgrade Helper) Update: Update configuration information. Revert: Cancel configuration information. Done: Close dialog box. Bulk Config (Upgrade Helper) From the SW Upgrade dialog box, click on any row. Click the Bulk Config command button. The Upgrade Helper dialog box displays. The Upgrade Helper allows you to select the download time, activation time, and upgrade type for all of the cards in the node. Figure 8-39 Upgrade Helper Dialog Box The Upgrade Helper dialog box allows you to configure the following parameters for all of the cards in the node: Download Time: From the drop-down list, select one of the following options: Now: Start the upgrade now. Set time: Click the up and down arrows to set the specific time. Clear time: Clear the time and start over. Upgrade Type: Select one of the following options: INIT (default): Completely erase backup partition of cards and copy all files. MERGE: Do not erase backup partition; overwrite existing files and add new files. Automatically fill in rel. paths for equipped slots: The system automatically fills in the Rel Path column on the main software upgrade screen. Command buttons are as follows: OK: Update the SW Upgrade dialog box with the information in the Upgrade Helper dialog box and close Upgrade Helper dialog box. Cancel: Cancel configuration information and close dialog box. Page 8-50 Turin Networks Release TN4.0.x

Chapter 6 Software Upgrades Software Upgrade and Activation Shortcut Menus Software Upgrade and Activation Shortcut Menus Both the SW Upgrade and SW Activation dialog boxes provide a shortcut menu. From the SW Upgrade dialog box, right-click a row to display the shortcut menu. Figure 8-40 Software Upgrade Shortcut Menu The shortcut menu allows you to perform the following actions: Abort Download: Stop copying files from the server to that card. Clear Download Time: Clear the download time that has been set for that card. From the SW Activation dialog box, right-click a row to display the shortcut menu. Figure 8-41 Software Activation Shortcut Menu The shortcut menu includes: Clear Activation Time: Clear the activation time that has been set for that card. Release TN4.0.x Turin Networks Page 8-51

TransNav GUI Guide, Section 8: Maintenance and Testing Software Upgrade and Activation Shortcut Menus Page 8-52 Turin Networks Release TN4.0.x

SECTION 8APPENDICES SECTION 9 APPENDICES Contents Appendix A Service Endpoints Endpoints for Ethernet Services................................... 9-1 Endpoints for SONET-STS Services................................ 9-2 Endpoints for VT1.5 Services..................................... 9-3 Endpoints for VC3 and VC4 Services............................... 9-5 Endpoints for VC11 and VC12 Services............................. 9-6 List of Tables Table 9-1 Endpoints for Ethernet Services.......................... 9-1 Table 9-2 Endpoints for STS Services............................. 9-2 Table 9-3 Endpoints for VT1.5 Services............................ 9-4 Table 9-4 Endpoints for VC3 and VC4 Services...................... 9-5 Table 9-5 Endpoints for VT11 and VC12 Services.................... 9-6 Release TN4.0.x Turin Networks Page i

TransNav GUI Guide, Section 9 Appendices Page ii Turin Networks Release TN4.0.x

SECTION 9APPENDICES Appendix A Service Endpoints Introduction Endpoints for Ethernet Services This appendix summarizes the valid source and destination information for each supported service type on the Traverse: Endpoints for Ethernet Services, page 9-1 Endpoints for SONET-STS Services, page 9-2 Endpoints for VT1.5 Services, page 9-3 Endpoints for VC3 and VC4 Services, page 9-5 Endpoints for VC11 and VC12 Services, page 9-6 The following table lists the service types and valid endpoints for creating Ethernet services on a node. Table 9-1 Endpoints for Ethernet Services Service Type Sources Destinations SDH-VC3 (EOS) SDH-VC4 (EOS) SONET-STS (EOS) VC-Bundle (EOS) Any Ethernet card SDH-VC3 (EOS) SDH-VC4 (EOS) SONET-STS (EOS) Any Ethernet card on a different node n/a Ethernet P2PDedicated Any Ethernet port Any Ethernet port SDH-VC3 (EOS) SDH-VC4 (EOS) SONET-STS (EOS) VC-Bundle (EOS) Ethernet P2PShared Any Ethernet port SDH-VC3 (EOS) SDH-VC4 (EOS) SONET-STS (EOS) VC-Bundle (EOS) Release TN4.0.x Turin Networks Page 9-1

TransNav GUI Guide, Section 9: Appendices Endpoints for SONET-STS Services Table 9-1 Endpoints for Ethernet Services (continued) Service Type Sources Destinations Ethernet IAS Any Ethernet port Any Ethernet port SDH-VC3 (EOS) SDH-VC4 (EOS) SONET-STS (EOS) VC-Bundle (EOS) Ethernet TLS Any Ethernet port SDH-VC3 (EOS) SDH-VC4 (EOS) SONET-STS (EOS) VC-Bundle (EOS) 1 n/a 1 You must use a VC-Bundle service to use RSTP with TLS services. Endpoints for SONET-STS Services The following table lists valid sources and destinations for STS services. Your network may require creating multiple services at multiple nodes. The Traverse system supports multicast STS connections for 1+1 path-protected and drop-and-continue services. Table 9-2 Endpoints for STS Services Sources Destinations Port Type Mapping Port Type Mapping OC-N 1 node/slot/port/sts STM-N (HO) STM-N (LO) all ports E1 card OC-N EC3 EC1 DS3CC DS3TMX all ports DS1 card EC3 node/slot/port/sts STM-N (HO) STM-N (LO) OC-N EC3 EC1 DS3CC node/slot/port/aug1/ node/slot/port/aug1/vc3 node/slot/port/aug1/tug3/vc3 node/slot node/slot/port/sts node/slot/port/sts node/slot/port node/slot/port node/slot/port node/slot node/slot/port/aug1/ node/slot/port/aug1/vc3 node/slot/port/aug1/tug3/vc3 node/slot/port/sts node/slot/port/sts node/slot/port node/slot/port Page 9-2 Turin Networks Release TN4.0.x

Appendix A Service Endpoints Endpoints for VT1.5 Services Table 9-2 Endpoints for STS Services Sources Destinations Port Type Mapping Port Type Mapping EC1 node/slot/port STM-N (HO) STM-N (LO) OC-N EC3 EC1 DS3CC DS3CC node/slot/port STM-N (HO) STM-N (LO) OC-N EC3 EC1 DS3CC DS3TMX node/slot/port STM-N (HO) STM-N (LO) OC-N EC3 node/slot/port/aug1/ node/slot/port/aug1/vc3 node/slot/port/aug1/tug3/vc3 node/slot/port/sts node/slot/port/sts node/slot/port node/slot/port node/slot/port/aug1/ node/slot/port/aug1/vc3 node/slot/port/aug1/tug3/vc3 node/slot/port/sts node/slot/port/sts node/slot/port node/slot/port node/slot/port/aug1/ node/slot/port/aug1/vc3 node/slot/port/aug1/tug3/vc3 node/slot/port/sts node/slot/port/sts All ports on a DS1 card node/slot STM-N (HO) STM-N (LO) node/slot/port/aug1/ node/slot/port/aug1/vc3 node/slot/port/aug1/tug3/vc3 OC-N EC3 node/slot/port/sts node/slot/port/sts SONET port on backplane for EOS ports node/slot (Ethernet card)/sts OC-N Any Ethernet card on a different node node/slot/port/sts node/slot (Ethernet card)/sts 1 For STS services between OC-192 ports, the source STS number and the destination STS number must in the same range when the range is between 1 and 48, or 49 and 192. For example, if the source STS is STS number 12, the destination STS must be between STS number 1 and 48. If the source STS is STS number 105, the destination STS must be between STS number 49 and 192. Endpoints for VT1.5 Services The following table lists valid sources and destinations for VT1.5 services. Your network may require creating multiple services at multiple nodes. Release TN4.0.x Turin Networks Page 9-3

TransNav GUI Guide, Section 9: Appendices Endpoints for VT1.5 Services There must be a VT/TU 5G switch card or a card with an integrated VTX/VCX present in the shelf to create this service. Table 9-3 Endpoints for VT1.5 Services Sources Destinations Port Type Mapping Port Type Mapping OC-N node/slot/port/sts/vtg/vt STM (HO) 1 STM (LO) 1 E1 OC-N EC3 EC1 DS3TMX 2 DS1 EC1 node/slot/port/sts-1/vtg/vt STM (HO) 1 STM (LO) 1 E1 OC-N EC1 DS3TMX DS1 DS3TMX 2 node/slot/port/subport STM (HO) 1 STM (LO) 1 E1 OC-N EC1 DS3TMX 2 DS1 DS1 node/slot/port STM (HO) 1 STM (LO) 1 E1 OC-N EC1 DS3TMX 2 DS1 node/slot/port/aug1/tug3/tug2/vc11 node/slot/port/aug1/vc3/tug2/vc11 node/slot/port node/slot/port/sts/vtg/vt node/slot/port/sts/vtg/vt node/slot/port/sts-1/vtg/vt node/slot/port/subport node/slot/port node/slot/port/aug1/tug3/tug2/vc11 node/slot/port/aug1/vc3/tug2/vc11 node/slot/port node/slot/port/sts/vtg/vt node/slot/port/sts-1/vtg/vt node/slot/port/subport node/slot/port node/slot/port/aug1/tug3/tug2/lo vc 3 node/slot/port/aug1/vc3/tug2/lo vc 3 node/slot/port node/slot/port/sts/vtg/vt node/slot/port/sts-1/vtg/vt node/slot/port/subport node/slot/port node/slot/port/aug1/tug3/tug2/lo vc 3 node/slot/port/aug1/vc3/tug2/lo vc 3 node/slot/port node/slot/port/sts/vtg/vt node/slot/port/sts-1/vtg/vt node/slot/port/subport node/slot/port SONET port on backplane for EOS ports node/slot (Ethernet card)/sts/vtg/vt OC-N Any Ethernet card on a different node. node/slot/port/sts/vtg/vt node/slot (Ethernet card)/sts 1 There must be an SDH-Endpoint or SDH-Tunnel service already with a Bandwidth of VC (Grooming) configured on the port. 2 Port is DS1-mapped (DS3 Mapping parameter is DS1). 3 lo vc is VC11 or VC12. Page 9-4 Turin Networks Release TN4.0.x

Appendix A Service Endpoints Endpoints for VC3 and VC4 Services Endpoints for VC3 and VC4 Services The following table lists valid sources and destinations for SDH services. Your network may require creating multiple services at multiple nodes. The Traverse system supports multicast SDH connections for 1+1 path-protected and drop-and-continue services. Table 9-4 Endpoints for VC3 and VC4 Services Sources Destinations Port Type Mapping Port Type Mapping STM-N 1 node/slot/port/aug1/ node/slot/port/aug1/tug3/vc3 node/slot/port/aug1/vc3 STM-N (HO) STM-N (LO) E3CC all ports E1 card node/slot/port/aug1/ node/slot/port/aug1/tug3/vc3 node/slot/port/aug1/vc3 node/slot/port node/slot OC-N EC3 EC1 DS3CC DS3TMX all ports DS1 card node/slot/port/sts node/slot/port/sts node/slot/port node/slot/port node/slot/port node/slot EC3 node/slot/port/sts STM-N (HO) STM-N (LO) E3CC all ports E1 card OC-N EC3 EC1 DS3CC DS3TMX all ports DS1 card E3CC node/slot/port STM-N (HO) STM-N (LO) E3CC OC-N EC3 EC1 DS3CC node/slot/port/aug1/ node/slot/port/aug1/tug3/vc3 node/slot/port/aug1/vc3 node/slot/port node/slot node/slot/port/sts node/slot/port/sts node/slot/port node/slot/port node/slot/port node/slot node/slot/port/aug1/tug3/vc3 node/slot/port/aug1/vc3 node/slot/port node/slot/port/sts node/slot/port/sts node/slot/port node/slot/port All ports on an E1 card node/slot STM-N (HO) STM-N (LO) node/slot/port/aug1/tug3/vc3 node/slot/port/aug1/vc3 OC-N EC3 node/slot/port/sts node/slot/port/sts Ethernet card for EOS node/slot (Ethernet card)/aug1 Any Ethernet card on a different node node/slot (Ethernet card)/aug1 1 For SDH services between STM-64 ports, the source AUG number and the destination AUG number must in the same range when the range is between 1 and 32, or between 33 and 64. For example, if the source AUG is AUG number 12, the destination AUG must be between AUG number 1 and 32; if the source AUG is AUG number 51, the destination AUG must be between AUG number 33 and 64. Release TN4.0.x Turin Networks Page 9-5

TransNav GUI Guide, Section 9: Appendices Endpoints for VC11 and VC12 Services Endpoints for VC11 and VC12 Services The following table lists valid sources and destinations for VC11 and VC12 services. Your network may require creating multiple services at multiple nodes. There must be a VT/TU 5G switch card or a card with an integrated VTX/VCX present in the shelf to create these services. Table 9-5 Endpoints for VT11 and VC12 Services Sources Destinations Port Type Mapping Port Type Mapping STM-N 1 node/slot/port/aug1/tug3/tug2/lovc 2 STM (HO) 1 node/slot/port/aug1/vc3/tug2/lovc 2 STM (LO) 1 E1 OC-N EC3 EC1 DS3TMX 3 DS1 EC3 node/slot/port/aug1/tug3/tug2/lovc 4 STM (HO) 1 node/slot/port/aug1/vc3/tug2/lovc 2 STM (LO) 1 E1 OC-N EC3 EC1 DS3CC DS1 DS3TMX 3 node/slot/port/subport STM (HO) 1 STM (LO) 1 E1 OC-N EC3 EC1 DS3TMX 3 DS1 node/slot/port/aug1/tug3/tug2/lo vc 2 node/slot/port/aug1/vc3/tug2/lo vc c node/slot/port node/slot/port/sts/vtg/vt node/slot/port/sts-1/vtg/vt node/slot/port/sts-1/vtg/vt node/slot/port/subport node/slot/port node/slot/port/aug1/tug3/tug2/lo vc 2 node/slot/port/aug1/vc3/tug2/lo vc c node/slot/port node/slot/port/sts/vtg/vt node/slot/port/sts-1/vtg/vt node/slot/port/sts-1/vtg/vt node/slot/port node/slot/port node/slot/port/aug1/tug3/tug2/lo vc 2 node/slot/port/aug1/vc3/tug2/lo vc 1 node/slot/port node/slot/port/sts/vtg/vt node/slot/port/sts/vtg/vt node/slot/port/sts-1/vtg/vt node/slot/port/subport node/slot/port Page 9-6 Turin Networks Release TN4.0.x

Appendix A Service Endpoints Endpoints for VC11 and VC12 Services Table 9-5 Endpoints for VT11 and VC12 Services (continued) Sources Destinations Port Type Mapping Port Type Mapping E1 node/slot/port STM (HO) 1 STM (LO) 1 E1 OC-N EC3 EC1 DS3TMX 3 DS1 node/slot/port/aug1/tug3/tug2/lo vc 2 node/slot/port/aug1/vc3/tug2/lo vc 2 node/slot/port node/slot/port/sts/vtg/vt node/slot/port/sts/vtg/vt node/slot/port/sts-1/vtg/vt node/slot/port/subport node/slot/port DS1 node/slot/port STM node/slot/port/aug1/tug3/tug2/lo vc 2 node/slot/port/aug1/vc3/tug2/lo vc 2 1 There must be an SDH-Endpoint or SDH-Tunnel service already with a Bandwidth of VC (Grooming) configured on the port. 2 lo vc is VC11 or VC12. 3 Port is E1-mapped (DS3 Mapping parameter is E1). 4 lo vc is VC11 or VC12. Release TN4.0.x Turin Networks Page 9-7

TransNav GUI Guide, Section 9: Appendices Endpoints for VC11 and VC12 Services Page 9-8 Turin Networks Release TN4.0.x

INDEX Numerics 1+1 APS configuration protection, 4-23 revertive, 4-22 status, 4-23 switch mode, 4-22 WTR, 4-22, 4-31 protection group name, 4-22 protection switch commands clear, 4-24, 4-25 exercise, 4-25 forced, 4-24, 4-25 lockout, 4-24 manual, 4-24, 4-25 protection switch priorities, 4-25 switch mode, 4-22 WTR, 4-22 1+1 MSP configuration protection, 4-23 status, 4-23 switch mode, 4-22 WTR, 4-22 protection switch commands clear, 4-24, 4-25 exercise, 4-25 forced, 4-24, 4-25 lockout, 4-24 manual, 4-24, 4-25 protection switch priorities, 4-25 switch mode, 4-22 WTR, 4-22 1+1 optimized protection configuration ID, 4-34 locked out, 4-34 name, 4-34 port, 4-35 protection, 4-35 role, 4-34 status, 4-35 WTR, 4-34 protection switch commands clear, 4-36 forced, 4-36 lockout, 4-36 protection switch priorities, 4-36 1+1 path protection configuration concatenation, 4-28 ID, 4-28 name, 4-28 protecting path, 4-28 protecting port, 4-28 working path, 4-28 working port, 4-28 protection switch commands clear, 6-78 forced, 6-78 lockout, 6-78 manual, 6-78 A Access groups definition, 2-11 node-level, 2-12 rights, 2-12 server-level, 2-5 Active EOS port status sink members, 5-69 source members, 5-69 Add card, 1-41, 1-43, 3-11 group, 1-38 link, 1-38, 3-15 destination, 3-16 source, 3-15 node, 1-38 TransAccess 100 Mux, 5-73, 5-79 TransAccess 200 Mux, 5-73, 5-79 Admin menu poll interval, 5-75, 5-81 synch interval, 5-75, 5-81 Administrative state BITS timing, 3-26, 6-75 card or port lock, 5-2 unlock, 5-2 EOS port, 5-64 SDH HO path, 6-75 LO path, 6-75 STS path, 6-75 VT path, 6-75 Release TN4.0.x Turin Networks Index-1

Index Advanced parameters EOS port, 5-64 Ethernet port, 5-58 Advertise 1000M Full Duplex GBE, 5-59 GBETX, 5-60 1000M Half Duplex GBE, 5-59 GBETX, 5-60 100M Full Duplex ETH100TX, 5-59 100M Half Duplex ETH100TX, 5-59 10M Full Duplex ETH100TX, 5-59 10M Half Duplex ETH100TX, 5-59 GBE RX PAUSE, 5-60 TX PAUSE, 5-60 Pause ETH100TX, 5-59 RX GBE, 5-59 TX GBE, 5-59 AIS format DS3 port, 5-14 DS3TMX port, 5-16 STS1TMX port, 5-16 insertion E1 port, 5-11, 5-37 mask DS1 port, 5-11 DS3 port, 5-13 DS3TMX port, 5-16 E1 port, 5-36 E3 port, 5-39 EC1 port, 5-19 SONET port, 5-23 STM port, 5-41 STS1TMX port, 5-16 Alarm categories, 8-26 definitions, 8-12 path endpoints profile, 6-74 suppression, 6-74 reporting, 8-26 hierarchy, 8-12 types, 8-26 view, 8-12 Alarm profile creating, 8-20 DS1 port, 5-11, 8-20 DS3 port, 5-14, 8-20 DS3TMX port, 5-16 subport, 5-18 E1 port, 5-37, 8-20 E3 port, 5-39, 8-20 EC1 port, 5-21 EOS port, 5-64 advanced, 5-65 SDH, 8-20 SONET, 8-20 Ethernet port, 5-55, 8-20 LAG, 8-20 node parameter, 3-5 SDH port, 8-20 server, 8-20 shelf, 8-20 SONET port, 8-20 STS, 8-20 VT, 8-20 SONET port, 5-26 STM port, 5-44 STS1TMX port, 5-16 subport, 5-18 TransAccess 100 Mux, 8-21 TransAccess 200 Mux, 5-77, 5-82, 8-21 Alarms acknowledge, 8-15, 8-16 annotations, 8-15 change service-affecting, 8-23 change severity, 8-22 colors displayed, 8-13 column order, 8-14 detail view, 8-15, 8-16 grouping, 8-16 menu, 1-46 new window, 8-15, 8-16 node group, 1-36 profiles, 8-20 set filters, 8-15, 8-16, 8-17 settings, 8-23, 8-35 save and import, 2-16 severity levels, 8-13 sorting, 8-14, 8-21, 8-23 StickyMode, 8-14 tab map view, 1-37 shelf view, 1-39 tab description, 8-13 Index-2 Turin Networks Release TN4.0.x

Index Alternate VLAN ethertype, see Ethernet Apply LCAS EOS port advanced Hold Off, 5-65 WTR, 5-65 Auto-discovery, 3-1 delete link, 3-18 pre-provisioned nodes, 3-10 Automatic laser shutdown, see Ethernet Auto-negotiation, 5-53, 5-59 Available bandwidth link, 3-17 B B3ZS DS3 port, line coding, 5-14 Background images customizing, 2-15 Backups database multiple servers, 2-25 Bandwidth, 6-15, 6-29, 7-8, 7-26 profile, 6-46 profile parameters, 6-47 CBS (KB), 6-47 CIR (Mbps), 6-47 name, 6-46, 6-47 PBS (KB), 6-47 PIR (Mbps), 6-47 synch status, 6-46 type, 6-46 BITS timing administrative state, 3-26 clock quality, 3-23 config tab, 3-24 force switch command, 3-31, 3-32 line build out, 3-25 lockout switch command, 3-31, 3-32 manual switch command, 3-31, 3-32 BLSR ring configuration card type, 4-2 east port, 4-3 name, 4-2 node, 4-2 node ID, 4-2 protection, east port, 4-3 protection, west port, 4-3 revertive, 4-2 ring ID, 4-2 status, east port, 4-3 status, west port, 4-3 west port, 4-3 WTR, 4-2 delete, 4-12 edit, 4-12 protection switch commands clear, 4-5 forced, 4-5 lockout, 4-5 manual, 4-5 protection switch priorities, 4-5 remove node, 4-4 squelch table, 4-4 synchronize, 4-3, 4-12 Bridge and roll assignment details, 7-20 service, 6-21, 6-37, 7-10, 7-28 C CAC, see Connection admission control Capacity monitoring intervals, 8-5 print data, 8-6 refresh values, 8-6 reports SDH, 2-29 SONET, 2-29 reset counters, 8-6 samples, 8-5 save data, 8-6 VT/TU data viewing, 8-5 Card add, 3-11 CLEI, 5-3 customer tag, 5-3 delete, 3-12 international common identifier, 5-3 module ID, 5-3 part number, 5-3 serial number, 5-3 software version, 5-3 type BLSR ring, 4-2 Carrier Ethernet Protection Pair configuration ID, 4-31 name, 4-31 protection, 4-32 revertive, 4-31 role, 4-31 status, 4-32 WTR, 4-31 C-bit processing DS3 port, 5-13 Release TN4.0.x Turin Networks Index-3

Index CEPP see Carrier Ethernet Protection Pair Classifiers add, 6-49 configure, 6-49 parameters priority CoS, 6-50 priority IDP, 6-50 Clear protection switch command 1+1 APS, 4-24, 4-25 1+1 MSP, 4-24, 4-25 1+1 optimized protection, 4-36 BLSR ring, 4-5 equipment protection, 4-18 CLEI node, 3-7 CLEI, see Card Client type session list, 2-10 Clock mode, timing, 3-23 quality, timing, 3-23 Concatenation 1+1 path protection, 4-28 EOS port size, 5-64 type, 5-64 type, 6-55 Config tab add link, 3-15 BITS and derived DS1, 3-24 delete link, 3-18 DS3 Clear Channel port, 5-13 DS3-TMX port, 5-15 EC1 port, 5-19 map view, 1-37 node, 3-4 shelf view, 1-40 STM port, 5-41 Confirm password user domain, 2-6 node, 2-13 Connection admission control Ethernet, 6-45 Contact TransAccess 200 Mux, 5-77, 5-82 Control data SONET port, 5-26 STM port, 5-44 Counter, 6-76, 8-4 port performance monitoring, 8-3 Create EOS tab, 5-63 LAG tab, 5-71 node, 3-3 Crossover ETH100TX, 5-60 Current transmitter state, 5-24, 5-42, 5-43, 5-54, 5-55 Custom RED, see Ethernet port advanced Customer, 6-15, 6-29, 6-55 associations equipment, 2-31 links, 2-31 services, 2-31 create, 2-31 description, 2-31 DS1 port, 5-11 DS3 port, 5-14 DS3TMX port, 5-16 E1 port, 5-37 E3 port, 5-39 EC1 port, 5-21 Ethernet port, 5-54 LAG, 5-71 selecting DCS-384, 7-8 DCS-96, 7-26 SONET port, 5-26 STM port, 5-44 STS1TMX port, 5-16 tag card, 5-3 DS3TMX port, 5-16 EC1 port, 5-21 Ethernet port, 5-55 STM port, 5-44 STS1TMX port, 5-16 tagged, 5-55 Customer tag node, 3-8 Customize node groups, 2-16, 2-18 D Data communications channel, 5-26, 5-44 Database backups multiple servers, 2-25 DCC tunnel tab shelf view, 1-40 DCS node parameter, 3-5 DCS application multi-shelf DCS-384 matrix shelf, 7-2 DCS-IO shelf, 7-16 Index-4 Turin Networks Release TN4.0.x

Index single-shelf DCS-96 shelf, 7-23 DCS assignment details bridge and roll, 7-20 description, 7-20, 7-24, 7-25 endpoint, 7-20, 7-24, 7-25 forward path trace, 7-20 forward signal label, 7-20 MSAID, 7-20, 7-24, 7-25 protection, 7-21 rev path trace, 7-20 rev signal label, 7-21 Source and Dest PM template, 7-20 transmuxed, 7-20 DCS tab DCS-384 matrix shelf allocation subtab, 7-7 assignment subtab, 7-6, 7-14 services subtab, 7-8, 7-24 DCS-96 shelf services subtab, 7-26 DCS-IO shelf allocation subtab, 7-17 assignment details, 7-19 assignment subtab, 7-18 DCS-384 matrix shelf DCS services, 7-8, 7-24 definition, 7-2 hardware configuration, 7-4 MSAID allocation, 7-7 MSAID assignments, 7-6, 7-14 protection groups, 7-5 DCS-96 shelf DCS services, 7-26 definition, 7-23 DCS-IO shelf definition, 7-16 MSAID allocation, 7-17 MSAID assignments, 7-18 Delete card, 1-41, 1-44, 3-12 link, 3-18 node, 3-10 TransAccess 100 Mux, 5-75, 5-81 TransAccess 200 Mux, 5-75, 5-81 Derived DS1 outputs config tab, 3-24 Description assignment details, 7-20, 7-24, 7-25 Dest PM template, 6-22, 6-37, 7-10, 7-28 DestDS1Mapping, 6-22, 6-37, 7-10, 7-28 DestDS3Mapping, 6-22, 6-37, 7-10, 7-28 DestE1Mapping, 6-22, 6-37, 7-10, 7-28 Destination Node ID, 6-21, 6-36 Diagnostic description, 8-37, 8-41 tab shelf view, 1-40 Domain report services, 2-28 roles access rights, 2-5 user confirm password, 2-6 create, 2-6 group, 2-6 management by, 2-6 roles, 2-5, 2-8 set up, 2-6 timeout, 2-6 username, 2-6, 2-13 view session list, 2-2 DS1 card mapping, 5-10 numbering, 5-9 DS1 port AIS mask, 5-11 alarm profile, 5-11, 8-20 customer, 5-11 line build out, 5-11 line coding, 5-11 line format, 5-10 PM template, see Performance Monitoring valid signal time, 5-11 DS3 mapping DS3TMX port, 5-15 STS1TMX port, 5-15 DS3 module parameters switch to E3, 5-12 DS3 port AIS format, 5-14 AIS mask, 5-13 alarm profile, 5-14, 8-20 C-bit processing, 5-13 customer, 5-14 line build out, 5-14 line coding, 5-14 B3ZS, 5-14 line format, 5-13 PM template, see Performance Monitoring RDI, 5-13 signal level, 5-13 switch from EC1, 5-21 switch to EC1, 5-14 Release TN4.0.x Turin Networks Index-5

Index DS3/EC1 port test signal type, 8-39 DS3TMX line format subport, 5-17, 5-18 port AIS format, 5-16 alarm profile, 5-16 customer, 5-16 customer tag, 5-16 DS3 mapping, 5-15 line build out, 5-16 line coding, 5-16 line format, 5-15 PM template, 5-16 signal level, 5-15 subport mapping, 5-15 subport numbering, 5-15 subport alarm profile, 5-18 loopback, 5-18 PM template, 5-18 DS3TMX port AIS mask, 5-16 DUS SONET port, 5-25 STM port, 5-43 E E1 card configurable parameters E1 mapping, 5-33 E1 numbering, 5-32 E1 port AIS insertion, 5-11, 5-37 AIS mask, 5-36 alarm profile, 5-37, 8-20 customer, 5-37 line build out, 5-36 line coding, 5-36 line format, 5-36 PM template, see Performance Monitoring valid signal time, 5-37 E3 module parameters switch to DS3, 5-38 E3 port AIS mask, 5-39 alarm profile, 5-39, 8-20 customer, 5-39 line build out, 5-39 line coding, 5-39 line format, 5-39 PM template, see Performance Monitoring East port BLSR ring, 4-3 MS-SP ring, 4-3 SNCP ring, 4-10 UPSR ring, 4-10 EC1 port AIS mask, 5-19 alarm profile, 5-21 configuration, 5-19 customer, 5-21 customer tag, 5-21 line build out, 5-20 line coding, 5-19 line format, 5-19 SD BER, 5-20 SF BER, 5-20 signal level, 5-19 switch from DS3, 5-14 switch to DS3, 5-21 valid signal timer, 5-20 EMS Gateway IP address, 3-6 IP address, 3-6 Mask IP address, 3-6 Encapsulation type, 6-55 Endpoint assignment details, 7-20, 7-24, 7-25 summary, 9-1 Environmental alarms configuration, 3-7 EOS port endpoint, 5-64 parameters, 5-63 EOS port admin state, 5-64 advanced alarm profile, 5-65 Apply LCAS Hold Off, 5-65 Apply LCAS WTR, 5-65 GFP FCS insert, 5-65 LCAS, 5-65 PLCR Threshold, 5-66 PLCT Threshold, 5-65 PM template, 5-65 RSTP, 5-65 RSTP path cost, 5-65 RSTP port priority, 5-65 TE100 LCAS compatibility mode, 5-66 advanced parameters, 5-64 alarm profile, 5-64 SDH, 8-20 SONET, 8-20 Index-6 Turin Networks Release TN4.0.x

Index concatenation size, 5-64 type, 5-64 customer, 5-64 description, 5-63 direction, 5-64 traffic, 5-64 endpoint, 5-64 ID, 5-63 member#, 5-64 parameters, 5-63 queue, 5-66 Custom RED, 5-67 occupancy, 5-67 policy, 5-67 service group, 5-64 slot, 5-63 status, 5-69 active sink members, 5-69 active source members, 5-69 member number, 5-69 relative diff delay, 5-70 RSTP port state, 5-69 EOS port member alarm profile SDH, 8-20 SONET, 8-20 EOS port status RSTP port role, 5-69 EOS subtab, 5-63, 5-69 edit, 5-69 Equipment creating and deleting, 3-1 Equipment protection configuration card, 4-16 card selection, 4-16 ID, 4-16 name, 4-16 protection, 4-17 revertive, 4-16 role, 4-16 status, 4-17 WTR, 4-16 protection switch commands clear, 4-18 forced, 4-18 lockout, 4-18 manual, 4-18 protection switch priorities, 4-19 Equipped state card or port equipped, 5-2 non-equipped, 5-2 Ethernet alternate VLAN ethertype, 5-51 automatic laser shutdown, 5-54 configuration tab, 5-50 EOS subtab, 5-63 features, 6-53 connection admission control, 6-45 insert alternate VLAN ethertype FE, 5-51 FE EOS, 5-51 LCAS HO WTR, 5-51 LO holdoff, 5-50 LO WTR, 5-51 LO mapping, 5-50 MAC address aging, 5-50 table, 5-50 modules, 6-41 parameters, 5-49 tab shelf view, 1-40 Ethernet port advanced Advertise 1000M Full Duplex GBETX, 5-60 Advertise 1000M Half Duplex GBETX, 5-60 Advertise GBE RX PAUSE, 5-60 Advertise GBE TX PAUSE, 5-60 Advertise PAUSE RX GBE, 5-59 Advertise PAUSE TX GBE, 5-59 Advertise1000M Half Duplex GBE, 5-59 auto-negotiation, 5-59 custom RED, 5-62 EOS port queues, 5-67 FIFO shape enable, 5-62 FIFO shaping rate, 5-62 insert alternate VLAN ethertype, 5-61 manual crossover ETH100TX, 5-60 manual duplex ETH100TX, 5-60 manual duplex GBE, 5-60 manual pause ETH100TX, 5-60 manual pause GBE, 5-61 manual speed ETH100TX, 5-60 manual speed GBE, 5-60 queuing policy, 5-61 tagging, 5-55, 5-61 WFQ CoS weight, 5-62 advanced parameters, 5-58 alarm profile, 5-55, 8-20 auto-negotiation, 5-53 current transmitter state, 5-54, 5-55 customer, 5-54 Release TN4.0.x Turin Networks Index-7

Index customer tag, 5-55 customer-tagged, 5-55 jumbo frame size, 5-55 support, 5-54 manual duplex, 5-53 speed, 5-54 parameters, 5-53 PM template, see Performance Monitoring port-tagged, 5-55 recovery pulse width, 5-54 transmitter auto shutdown, 5-54, 5-55 transmitter state, 5-54 untagged, 5-55 Ethernet port advanced Advertise 1000M Full Duplex, GBE, 5-59 100M Full Duplex (ETH100TX), 5-59 100M Half Duplex (ETH100TX), 5-59 10M Full Duplex (ETH100TX), 5-59 10M Half Duplex (ETH100TX), 5-59 PAUSE (ETH100TX), 5-59 max info rate (Mbps), 5-58 burst size, 5-59 Ethernet service advanced parameters, 6-44 link integrity, 6-44 service VLAN ID, 6-44 create, 6-42 parameters, 6-42 classifier, 6-42 customer, 6-42 description, 6-42 endpoints, 6-42 name, 6-42 policers, 6-42 type, 6-42 port advanced parameters, 6-43 default priority bit, 6-43 MAC addresses, 6-43 marking bit, 6-43 override VLAN ID, 6-43 VLAN type, 6-43 Event categories, 8-26 filter, 8-34 logs, 8-26 reporting, 8-26 types, 8-26 Events column order, 8-29 detail view, 8-29, 8-32 grouping, 8-32 new window, 8-29, 8-32 refresh, 8-29, 8-32 set filters, 8-29, 8-32, 8-33 settings, 8-23, 8-29, 8-32, 8-35 save and import, 2-16 sorting, 8-29 tab map view, 1-37 shelf view, 1-40 Exercise protection switch command 1+1 APS, 4-25 1+1 MSP, 4-25 External alarms configuration, 3-7 timing BITS configuration, 3-22 framing format, 3-25 F Failure retry count, 6-22, 6-37, 7-10, 7-28 FIFO, 5-62 shape enable queuing policy, 5-62 Filter services, 6-66 Fixed-24Bit test signal type, 8-39 Force switch command BITS timing, 3-31, 3-32 Forced protection switch command 1+1 APS, 4-24, 4-25 1+1 MSP, 4-24, 4-25 1+1 optimized protection, 4-36 BLSR ring, 4-5 equipment protection, 4-18 Forward path format, 6-22, 6-38, 7-11, 7-28 Forward path trace, 6-22, 6-38, 7-11, 7-29 assignment details, 7-20 Forward signal label, 6-22, 6-38, 7-11, 7-29 assignment details, 7-20 Framing format external timing, 3-25 Functional groups assign domain users, 2-4 definition, 2-2, 2-7 roles, 2-8 Functional groups, see also Groups G GCM config tab, 5-5 Index-8 Turin Networks Release TN4.0.x

Index GCM A gateway IP address, 3-6 IP address, 3-6 MAC address, 3-6 mask IP address, 3-6 GCM B gateway IP address, 3-6 IP address, 3-6 MAC address, 3-6 mask IP address, 3-6 GFP FCS insert EOS port advanced, 5-65 Graphical user interface menu bar, 1-36 Groups add node, 2-18 domain users, 2-6 navigation tree, 2-22 node background images, 2-15 customize, 2-18 roles, 2-8 GUI conventions, 1-51 resizing windows, 1-52 scroll bars, 1-51 H Hierarchy alarms, 8-12 Historical report alarm, 2-28 data access, 2-25 event, 2-28 Hold off timer, 6-21, 6-36 Hop-by-hop service, 6-7 Host name, 1-18, 1-20, 1-21, 1-22 I ID 1+1 APS, 4-22, 4-31 1+1 optimized protection, 4-34 1+1 path protection, 4-28, 4-31 Carrier Ethernet Protection Pair, 4-31 equipment protection, 4-16 Input Sync Msgs SONET port, 5-24 STM port, 5-42 Insert alternate VLAN ethertype, 5-51, 5-61 International common identifier card, 5-3 International Common Identifier (ICI) node, 3-8 Internet Explorer web browser settings, 1-2 Interval capacity monitoring, 8-5 port performance monitoring, 6-76, 8-3, 8-4 IP address bp-dcn-ip, 3-5 EMS, 3-6 EMS gateway, 3-6 EMS mask, 3-6 GCM A, 3-6 GCM A gateway, 3-6 GCM A mask, 3-6 GCM B, 3-6 GCM B gateway, 3-6 GCM B mask, 3-6 Network Time Protocol, 3-6 node backplane DCN gateway, 3-6 node backplane DCN mask, 3-6 node-ip, 3-5, 3-9 session list, 2-10 TransAccess 200 Mux, 5-74, 5-77, 5-80 IP QoS, 3-35 J Jumbo frame Ethernet port size, 5-55 support, 5-54 L LAG advanced parameters, 5-72 part loss threshold, 5-72 description, 5-71 ID, 5-71 subtab, 5-71 LAG port alarm profile, 8-20 LCAS configuration, 6-55 EOS port advanced, 5-65 compatibility mode, 5-66 HO WTR, 5-51 LO Holdoff (100 ms), 5-50 LO WTR (min), 5-51 Line build out Release TN4.0.x Turin Networks Index-9

Index BITS timing, 3-25 DS1 port, 5-11 DS3 port, 5-14 DS3TMX port, 5-16 E1 port, 5-36 E3 port, 5-39 EC1 port, 5-20 Line coding DS1 port, 5-11 DS3 port, 5-14 DS3TMX port, 5-16 E1 port, 5-36 E3 port, 5-39 EC1 port, 5-19 STS1TMX port, 5-16 timing, 3-24 Line format DS1 port, 5-10 DS3 port, 5-13 DS3TMX port, 5-15 subport, 5-17, 5-18 E1 port, 5-36 E3 port, 5-39 EC1 port, 5-19 SONET port, 5-23 STM port, 5-41 STS1TMX port, 5-15 subport, 5-17, 5-18 Line timing configuration, 3-22, 3-27 SONET port, 5-23 source, 3-28 establishing, 3-27 SSM received, 3-28 transmitted, 3-28 status, 3-28 STM port, 5-41 Link add, 3-15 aggregation group, 5-71 customer, 5-71 description, 5-71 ID, 5-71 slot, 5-71 available bandwidth, 3-17 delete, 3-18 destination, 3-16 off page connector icon, 3-16 operational state, 3-17 set without DCC discovery, 3-15 source, 3-15 types, 3-15 add link, 3-16 Link, see also LAG LO mapping, 5-50 Load balance, 6-23, 6-38, 7-11, 7-29 Location node parameter, 3-5 Lockout protection switch command 1+1 APS, 4-24 1+1 MSP, 4-24 1+1 optimized protection, 4-36 BITS timing, 3-31 BLSR ring, 4-5 equipment protection, 4-18 Lockout switch command BITS timing, 3-32 Login dialog box advanced notification, 1-23 port number, 1-23 protocol, 1-23 host name, 1-18, 1-20, 1-21, 1-22 password, 1-18, 1-20, 1-21, 1-22 user name, 1-18, 1-20, 1-21, 1-22 Loopback diagnostic tests, 8-37 DS3TMX subport, 5-18 facility, 8-38 STS1TMX subport, 5-18 terminal, 8-38 tests performing, 8-39 M MAC address aging, 5-50 GCM A, 3-6 GCM B, 3-6 node backplane DCN, 3-6 port ID, 5-52 slot ID, 5-52 table, 5-50, 5-52 count, 5-53 port type, 5-52 service, 5-52 Management gateway node, 3-1 Management port TransAccess 200 Mux, 5-77 Management System event logs, 8-26 Manual duplex, 5-53 ETH100TX, 5-60 Index-10 Turin Networks Release TN4.0.x

Index GBE, 5-60 Manual pause ETH100TX, 5-60 GBE, 5-61 Manual protection switch command 1+1 APS, 4-24, 4-25 1+1 MSP, 4-24, 4-25 BLSR ring, 4-5 equipment protection, 4-18 Manual speed, 5-54 ETH100TX, 5-60 GBE, 5-60 Manual switch command BITS timing, 3-31, 3-32 Map view alarms tab, 1-37 change background, 1-38 config tab, 1-37 description, 1-36 events tab, 1-37 group map, 1-36 network map, 1-36 performance tab, 1-37 protection tab, 1-37 service tab, 1-37 shortcut menu, 1-37 Max Info Rate (Mbps), 5-58, 5-59 Max SD-BER-V, 6-23, 6-38, 7-11, 7-29 Max SF-BER-V, 6-23, 6-38, 7-12, 7-29 Maximum hop count, 6-23, 6-38, 7-11, 7-29 Member number EOS port, 5-64 EOS port status, 5-69 Menus, 1-44 admin, 1-48 alarm, 1-46 events, 1-46 file, 1-45 help, 1-51 provisioning, 1-51 service groups, 1-48 services, 1-47 view, 1-45 Module ID, 5-3 card, 5-3 Module ID card, 3-8 node, 3-8 MSAID assignment details, 7-20, 7-24, 7-25 DCS-384 allocation, 7-7 DCS-384 assignments, 7-6, 7-14 DCS-IO allocation, 7-17 DCS-IO assignments, 7-18 definition, 7-3 MS-SP ring configuration, 4-3 card type, 4-2 east port, 4-3 name, 4-2 node, 4-2 node ID, 4-2 protection, east port, 4-3 protection, west port, 4-3 revertive, 4-2 ring ID, 4-2 status, west port, 4-3 west port, 4-3 WTR, 4-2 delete, 4-12 edit, 4-12 protection switch commands clear, 4-5 forced, 4-5 lockout, 4-5 manual, 4-5 protection switch priorities, 4-5 remove node, 4-4 squelch table, 4-4 synchronize, 4-3, 4-12 Multiple servers backups, 2-25 N Name 1+1 APS, 4-22 1+1 optimized protection, 4-34 1+1 path protection, 4-28 BLSR ring, 4-2 Carrier Ethernet Protection Pair, 4-31 equipment protection, 4-16 MS-SP ring, 4-2 SNCP ring, 4-10 UPSR ring, 4-10 Navigation tree, 1-36 Netscape Navigator browser settings, 1-10 Network Time Protocol IP address, 3-6 Node access groups and rights, 2-12 backplane DCN gateway IP address, 3-6 MAC address, 3-6 Release TN4.0.x Turin Networks Index-11

Index mask IP address, 3-6 backplane IP address, 3-5 BLSR ring, 4-2 CLEI, 3-7 configurable parameters, 3-4 create, 3-3 customer tag, 3-8 deleting pre-provisioned, 3-10 group add, 2-18 background images, 2-15 customize, 2-18 ID, 3-4, 3-9 BLSR ring, 4-2 MS-SP ring, 4-2 TransAccess 200 Mux, 5-77, 5-82 International Common Identifier, 3-8 IP, 3-5, 3-9 address, 3-5 IP address, 3-9, 5-77, 5-82 module ID, 3-8 MS-SP ring, 4-2 name, 3-3 parameters alarm profile, 3-5 BP-DCN-IP, 3-5 DCS, 3-5 location, 3-5 node ID (node name), 3-4 node IP, 3-5 type, 3-5 part number, 3-7 report inventory, 2-28 serial number, 3-7 setting Proxy ARP, 3-8 SNCP ring, 4-10 UPSR ring, 4-10 user access, 2-14 change password, 2-3 confirm password, 2-13 create, 2-13 management by, 2-13 name, 2-13 roles, 2-13 security, 2-12 synchronization, 2-14 Notification login, 1-23 O Operational state card or port disabled, 5-2 enabled, 5-2 Output Sync Msgs SONET port, 5-25 STM port, 5-43 P Parameters Ethernet module, 5-49 SFP port, 5-56 XFP port, 5-56 Part Loss Threshold, see LAG Part number card, 5-3 node, 3-7 Password, 1-18, 1-20, 1-21, 1-22 change, 2-3 user, 2-6, 2-13 Path mapping, 6-23, 6-39, 7-12, 7-30 trace received, 6-75 Path DCC Configuration SONET port, 5-27 STM port, 5-45 Peak burst size, 6-47 information rate, 6-47 Performance tab map view, 1-37 shelf view, 1-40 Performance monitoring port counter, 8-3 interval, 6-76, 8-4 samples, 6-76, 8-4 reports see Reports service counter, 6-76, 8-4 template DS1 port, 5-11 DS3 port, 5-14 E1 port, 5-37 E3 port, 5-39 Ethernet port, 5-54 source, 6-24, 6-40, 7-13, 7-31 Source and Dest, 7-20 STM port, 5-44 viewing port PM data, 8-5 VT/TU capacity viewing, 8-5 PLCR Threshold, see EOS port advanced Index-12 Turin Networks Release TN4.0.x

Index PLCT Threshold, see EOS port advanced PM template DS3TMX port, 5-16 DS3TMX subport, 5-18 EOS port advanced, 5-65 STS1TMX port, 5-16 STS1TMX subport, 5-18 Policers, 6-48 create, 6-48 parameters card, 6-49 ID, 6-49 Poll interval admin menu, 5-75, 5-81 Port 1+1 optimized protection, 4-35 EOS, 5-63 ID MAC address, 5-52 number TransAccess 200 Mux, 3-9, 5-74, 5-80 user session, 1-23 Preprovisioning, 5-1 creating and deleting managed objects, 3-1 deleting nodes, 3-10 node name, 3-3 node type, 3-3 Priorities priority requests, 4-19 protection switching 1+1 APS, 4-25 1+1 MSP, 4-25 1+1 optimized protection, 4-36 BLSR ring, 4-5 equipment protection, 4-19 Protection 1+1 APS, 4-23, 4-32 1+1 MSP, 4-23 1+1 optimized protection, 4-35 1+1 path protection path, 4-28 port, 4-28 assignment details, 7-21 BLSR ring east port, 4-3 west port, 4-3 Carrier Ethernet Protection Pair, 4-32 equipment, 4-17 MS-SP ring east port, 4-3 west port, 4-3 rings delete, 4-12 edit, 4-12 synchronize, 4-12 tab map view, 1-37 shelf view, 1-40 Protection switch commands 1+1 path protection clear, 6-78 forced, 6-78 lockout, 6-78 manual, 6-78 BLSR ring clear, 4-5 forced, 4-5 lockout, 4-5 manual, 4-5 clear 1+1 APS, 4-24, 4-25 1+1 MSP, 4-24, 4-25 1+1 optimized protection, 4-36 BLSR ring, 4-5 equipment protection, 4-18 exercise 1+1 APS, 4-25 1+1 MSP, 4-25 forced 1+1 APS, 4-24, 4-25 1+1 MSP, 4-24, 4-25 1+1 optimized protection, 4-36 BLSR ring, 4-5 equipment protection, 4-18 lockout 1+1 APS, 4-24 1+1 MSP, 4-24 1+1 optimized protection, 4-36 BLSR ring, 4-5 equipment protection, 4-18 manual 1+1 APS, 4-24, 4-25 1+1 MSP, 4-24, 4-25 BLSR ring, 4-5 equipment protection, 4-18 MS-SP ring clear, 4-5 forced, 4-5 lockout, 4-5 manual, 4-5 Protocol HTTP, 1-23 HTTPS, 1-23 RMI, 1-23 user session, 1-23 Proxy ARP Release TN4.0.x Turin Networks Index-13

Index node set up, 3-8 Pseudo random bit sequence, 8-39 Q Quality of RES timing tab, 3-22 Queuing policy, 5-61 EOS, 5-67 FIFO, 5-61 shape enable, 5-62 shaping rate, 5-62 priority, 5-61 WFQ, 5-62 CoS weight, 5-62 R Read community TransAccess 200 Mux, 3-9, 5-74, 5-77, 5-80, 5-82 Recovery Pulse Width, 5-24, 5-42, 5-54 Redline circuit, see Service parameters Relative Diff Delay EOS port status, 5-70 Replace card, 1-41, 1-44 Report scheduler, 2-27 Reporting alarms and events, 8-26 Reports capacity monitoring SDH, 2-29 SONET, 2-29 creating, 2-25 generate, 2-25 period, 2-27 historical alarm, 2-28 event, 2-28 inventory node, 2-28 list, 2-26 performance monitoring DS1 port, 2-28 DS3 port, 2-28 E1 port, 2-28 E3 port, 2-28 EC1 port, 2-28 EOS, 2-28 Ethernet 10GE, 2-28 Ethernet NGE, 2-28 Ethernet port, 2-28 Ethernet service port, 2-28 SDH port, 2-29 SDH VC-11 path, 2-29 SDH VC-12 path, 2-29 SONET port, 2-29 STS path, 2-29 T100, 2-29 TA200, 2-29 VT path, 2-29 period length, 2-29 resource availability, 2-28 scheduled, 2-26 script files, 2-28 service availability, 2-28 domain, 2-28 endpoints, 2-28 source filter, 2-29 types, 2-25 Resize windows, 1-52 Resource advisory link, 3-17 availability report, 2-28 Restart card cold, 1-41, 1-44 warm, 1-41, 1-44 Rev path format, see Service parameters Rev path trace assignment details, 7-20 Rev path trace, see Service parameters Rev signal label assignment details, 7-21 Rev signal label, see Service parameters Revertive, 6-20, 6-35 1+1 APS, 4-22, 4-31 BLSR ring, 4-2 Carrier Ethernet Protection Pair, 4-31 equipment protection, 4-16 MS-SP ring, 4-2 timing, 3-23 Ring ID BLSR ring, 4-2 MS-SP ring, 4-2 SNCP ring, 4-10 UPSR ring, 4-10 Role 1+1 optimized protection, 4-34 Carrier Ethernet Protection Pair, 4-31 domain access rights, 2-5 user, 2-8 equipment protection, 4-16 node access rights user, 2-13 Index-14 Turin Networks Release TN4.0.x

Index Role-based Access Control definition, 2-2 example, 2-2 Role-based Access Control, see also Groups Round trip delay enable function, 6-23, 6-39, 7-12, 7-30 expected, 6-22, 6-37, 7-10, 7-28 RSTP configuration, 6-56 EOS port advanced, 5-65 path cost, 5-65 port priority, 5-65 path cost, 6-56 port EOS status, 5-69 role, 5-69 port priority, 6-56 EOS port advanced, 5-65 port state, 5-69 state EOS port, 5-69 virtual bridge, 5-65 S Samples, port see Performance monitoring Script file report, 2-28 Scroll bars, 1-51 SD BER EC1 port, 5-20 line, 5-25 SONET card path, 5-22 port, 5-25 STM card regenerator section, 5-40 STM port multiplex section, 5-43 SDH administrative state HO path, 6-75 LO path, 6-75 SDH port alarm profile, 8-20 performance tab, 8-2 Security user access groups, 2-11 domain, 2-1, 2-11 functional group, 2-2 node, 2-1, 2-11 Security monitoring access server-level, 2-5 Security roles see Domain, roles see Node, access Serial number card, 5-3 node, 3-7 Server alarm profile, 8-20 Service availability report, 2-28 configuration description, 6-53, 6-61, 6-71 creation parameters bandwidth, 6-15, 6-29 concatenation type, 6-55 customer, 6-15, 6-29, 6-55 encapsulation type, 6-55 LCAS configuration, 6-55 RSTP configuration, 6-56 RSTP path cost, 6-56 RSTP port priority, 6-56 delete, 6-66 endpoints, 9-1 endpoints (CTPs) report, 2-28 group create, 6-57 hop-by-hop, 6-7 show last error, 6-65 tab, 6-64 Service group EOS port, 5-64 parameters, see Service parameters Service parameters bridge and roll, 6-21, 6-37, 7-10, 7-28 count concecutive services, 6-58 creation bandwidth, 7-8, 7-26 customer, 7-8, 7-26 Dest PM template, 6-22, 6-37, 7-10, 7-28 DestDS1Mapping, 6-22, 6-37, 7-10, 7-28 DestDS3Mapping, 6-22, 6-37, 7-10, 7-28 DestE1Mapping, 6-22, 6-37, 7-10, 7-28 failure retry count, 6-22, 6-37, 7-10, 7-28 forward path format, 6-22, 6-38, 7-11, 7-28 forward path trace, 6-22, 6-38, 7-11, 7-29 forward signal label, 6-22, 6-38, 7-11, 7-29 group, 6-57 concat. size, 6-57 description, 6-57, 6-59 edit, 6-59 Release TN4.0.x Turin Networks Index-15

Index name, 6-57, 6-59 routing policy, 6-58 load balance, 6-23, 6-38, 7-11, 7-29 max hop count, 6-23, 6-38, 7-11, 7-29 max SD-BER-V, 6-23, 6-38, 7-11, 7-29 max SF-BER-V, 6-23, 6-38, 7-12, 7-29 path mapping, 6-23, 6-39, 7-12, 7-30 protection destination node ID, 6-21, 6-36 hold off timer, 6-21, 6-36 revertive, 6-20, 6-35 source node ID, 6-21, 6-36 WTR time, 6-20, 6-35 redline circuit, 6-23, 6-39, 7-12, 7-30 rev path format, 6-23, 6-39, 7-12, 7-30 rev path trace, 6-23, 6-39, 7-12, 7-30 rev signal label, 6-24, 6-39, 7-12, 7-30 round trip delay enable, 6-23, 6-39, 7-12, 7-30 expected, 6-22, 6-37, 7-10, 7-28 setup retry count, 6-24, 6-40, 7-13, 7-31 source PM template, 6-24, 6-40, 7-13, 7-31 sourceds1mapping, 6-24, 6-40, 7-13, 7-31 sourceds3mapping, 6-24, 6-40, 7-13, 7-31 sourcee1mapping, 6-24, 6-40, 7-13, 7-31 TMX port, 6-24, 6-40, 7-13, 7-31 transparency, 6-24, 6-40, 7-13, 7-31 unidirectional connections, 6-25, 6-40, 7-13, 7-31 Service performance monitoring counter, 6-76, 8-4 Service tab map view, 1-37 shelf view, 1-40 Services abort, 6-65 activate, 6-65 administrative state, 6-63 bandwidth of, 6-63 customer, 6-63 deactivate, 6-65 delete, 6-66 description, 6-63 edit, 6-66 filter, 6-65 grouping, 6-65 name, 6-62 operational state, 6-63 resize columns, 6-65 roll, 6-65 service state, 6-63 set filters, 6-66 show provisioned path, 6-65 show TxRx path, 6-64 sorting, 6-65 source endpoint, 6-62 system ID, 6-62 type, 6-63 view, 6-66 Session list client type, 2-10 IP address (hostname), 2-10 use, 2-2 user name currently online, 2-10 Setup retry count, see Service parameters Severity levels alarm and event defined, 8-12 alarms, 8-13 SF BER EC1 port, 5-20 line, 5-23 SONET card path, 5-22 port, 5-23 STM card regenerator section, 5-40 STM port multiplex section, 5-42 Shelf add card, 3-11 alarm profile, 8-20 name TransAccess 200 Mux, 5-74, 5-80 Shelf view description, 1-39 shortcut menu, 1-40, 1-43, 3-11 tab alarms, 1-39 config, 1-40 DCC tunnel, 1-40 diagnostic, 1-40 Ethernet, 1-40 events, 1-40 performance, 1-40 protection, 1-40 service, 1-40 timing, 1-40 Shortcut menu map view, 1-37 shelf view, 1-40, 1-43, 3-11 Signal level DS3 port, 5-13 DS3TMX port, 5-15 Index-16 Turin Networks Release TN4.0.x

Index EC1 port, 5-19 timer EC1 port, 5-20 Slot EOS port, 5-63 ID MAC address, 5-52 LAG, 5-71 SNCP ring configuration east port, 4-10 name, 4-10 node, 4-10 ring ID, 4-10 west port, 4-10 delete, 4-12 edit, 4-12 synchronize, 4-12 SNMP node agent port, 3-8 configuration, 3-8 Software upgrade abort download, 8-51 activation status, 8-49 time, 8-49 type, 8-49 base path, 8-48 clear activation time, 8-51 download time, 8-51 current compatibility identifier, 8-48 download status, 8-48 time, 8-48, 8-50 module identifier, 8-48 type, 8-48 password, 8-48 rel path, 8-48 automatically fill, 8-50 server IP address, 8-47 slot number, 8-48, 8-49 upgrade type, 8-48, 8-50 username, 8-48 Software version, 5-3 card, 5-3 SONET alarm profile port, 8-20 STS, 8-20 VT, 8-20 SONET card path SD BER, 5-22 SF BER, 5-22 SONET port AIS mask, 5-23 alarm profile, 5-26 configuration, 5-23 control data, 5-26 current transmitter state, 5-24 customer, 5-26 DUS, 5-25 line format, 5-23 SD BER, 5-25 SF BER, 5-23 timing, 5-23 path DCC configuration, 5-27 recovery pulse width, 5-24 SS bit transmit, 5-25 sync msgs input, 5-24 output, 5-25 terminate DCC, 5-26 transmitter auto shutdown, 5-24, 5-25 transmitter state, 5-24 Source line timing, 3-28 link, 3-16 Source and Dest PM template assignment details, 7-20 Source mapping, see Service parameters Source Node ID, 6-21, 6-36 Source PM template, 6-24, 6-40, 7-13, 7-31 SS bit transmit SONET port, 5-25 STM port, 5-43 SSM, see Synchronization status messages Starting AUG1 numbers VC3 paths, 6-34 VC4 paths, 6-34 Static route add to node, 3-20 Status 1+1 APS, 4-23 1+1 MSP, 4-23 1+1 optimized protection, 4-35 BLSR ring east port, 4-3 west port, 4-3 Carrier Ethernet Protection Pair, 4-32 equipment protection, 4-17 line timing, 3-28 Release TN4.0.x Turin Networks Index-17

Index StickyMode, 8-14 STM card regenerator section SD BER, 5-40 SF BER, 5-40 STM port AIS mask, 5-41 alarm profile, 5-44 config tab, 5-41 configuration, 5-41 control data, 5-44 current transmitter state, 5-42, 5-43 customer, 5-44 customer tag, 5-44 DUS, 5-43 line format, 5-41 line timing, 5-41 multiplex section SD BER, 5-43 SF BER, 5-42 output synchronization messages, 5-43 path DCC configuration, 5-45 PM template, see Performance Monitoring recovery pulse width, 5-42 SS bit transmit, 5-43 synchronization messages input, 5-42 output, 5-43 synchronization status message, 5-42 terminate DCC, 5-44 transmitter auto shutdown, 5-42, 5-43 transmitter state, 5-42 STS path administrative state, 6-75 STS1TMX line format subport, 5-18 port AIS format, 5-16 AIS mask, 5-16 alarm profile, 5-16 customer, 5-16 customer tag, 5-16 DS3 mapping, 5-15 line coding, 5-16 line format, 5-15 PM template, 5-16 subport mapping, 5-15 subport numbering, 5-15 subport alarm profile, 5-18 line format, 5-17 loopback, 5-18 PM template, 5-18 Sub shelf menu, 5-75, 5-76, 5-81 attach sub shelf, 5-76, 5-81 detach, 5-75, 5-76, 5-81 detach sub shelf, 5-81 launch sub shelf, 5-76 sync sub shelf alarms, 5-76, 5-81 TransAccess 200 Mux ID, 5-77, 5-82 IP address, 5-77, 5-82 type, 5-77, 5-82 Subport mapping DS3TMX port, 5-15 STS1TMX port, 5-15 numbering DS3TMX port, 5-15 STS1TMX port, 5-15 Summary service endpoints, 9-1 Switch to DS3, 5-38 E3, 5-12 Sync interval admin menu, 5-75, 5-81 sub shelf alarms, 5-76, 5-81 Synchronization alarm profiles, 8-21 BLSR ring, 4-3 MS-SP ring, 4-3 node user, 2-14 status message ignore received, 3-23 input, 5-24, 5-42 output, 5-25, 5-43 received by line timing, 3-28 SONET port, 5-24, 5-25 STM port, 5-42, 5-43 transmitted by line timing, 3-28 T T100 PM report, 2-29 TA200 PM report, 2-29 Tabs EOS create, 5-63 edit, 5-69 subtab, 5-69 Ethernet Index-18 Turin Networks Release TN4.0.x

Index configuration, 5-50 LAG create, 5-71 subtab, 5-71 STM port config, 5-41 Tagging, 5-55, 5-61 customer-tagged, 5-61 port-based, 5-61 service-tagged, 5-61 Templates description, 8-1 Terminate DCC SONET port, 5-26, 5-27 STM port, 5-44 Test Access ADM, 8-41 DCS3/1, 8-41 digital signals, 8-41 intrusive, 8-41 non-intrusive, 8-41 Test signal type, DS3/EC1 port, 8-39 Timeout domain user, 2-6 Timeout, see TransAccess 200 Mux Timing clock mode, 3-23 configuration, 3-22 BITS and derived DS1, 3-24 description, 3-21 line timing, 3-27 line coding, 3-24 mode, 3-22 Quality of RES, 3-22 tab description, 3-22 shelf view, 1-40 TMX port, 6-24, 6-40, 7-13, 7-31 Topology update, 4-7, 4-13 TransAccess 100 Mux add, 5-73, 5-79 alarm profile, 8-21 delete, 5-75, 5-81 Ethernet IP subnet, 5-74, 5-80 TransAccess 200 Mux add, 5-73, 5-79 alarm profile, 5-77, 5-82, 8-21 contact, 5-77, 5-82 delete, 5-75, 5-81 IP address, 5-74, 5-77, 5-80 location, 5-77, 5-82 management port, 5-77, 5-82 node ID, 5-77, 5-82 IP address, 5-77, 5-82 number of retries, 5-74, 5-77, 5-80, 5-83 port number, 3-9, 5-74, 5-80 read community, 3-9, 5-74, 5-77, 5-80, 5-82 shelf name, 5-74, 5-80 sub shelf ID, 5-77, 5-82 sub shelf IP address, 5-82 sub shelf type, 5-77, 5-82 timeout, 5-74, 5-77, 5-80, 5-82 trap port, 5-74, 5-80 trap receive port, 5-77, 5-82 write community, 3-9, 5-74, 5-77, 5-80, 5-82 Transmission path trace information viewing, 6-75 Transmitter auto shutdown, 5-24, 5-25, 5-42, 5-43, 5-54, 5-55 Transmitter state, 5-54 Ethernet port parameters, 5-54 SONET port, 5-24 STM port, 5-42 Transmuxed assignment details, 7-20 Transparency, 6-24, 6-40, 7-13, 7-31 Trap TransAccess 200 Mux port, 5-74, 5-80 receive port, 5-77, 5-82 Type node parameter, 3-5 U Unidirectional connections Connections unidirectional, 6-25, 6-40, 7-13, 7-31 Untagged, 5-55 Update topology, 4-7, 4-13 UPSR ring configuration east port, 4-10 name, 4-10 node, 4-10 ring ID, 4-10 west port, 4-10 delete, 4-12 edit, 4-12 synchronize, 4-12 User definition Release TN4.0.x Turin Networks Index-19

Index domain, 2-1, 2-11 node, 2-1, 2-11 name, 1-18, 1-20, 1-21, 1-22 domain, 2-6, 2-13 node user, 2-13 session list, 2-10 password, 2-6, 2-13 preferences save and import, 2-16 V Valid signal time DS1 port, 5-11 E1 port, 5-37 EC1 port, 5-20 VC3 paths, 6-34 VC4 paths, 6-34 VCAT, see Virtual concatenation Viewing alarms, 8-12 PM data port, 8-5 Virtual concatenation feature description, 6-53 VT path administrative state, 6-75 PM report, 2-29 W West port BLSR ring, 4-3 MS-SP ring, 4-3 SNCP ring, 4-10 UPSR ring, 4-10 WFQ CoS n Weight, 5-62 Working 1+1 path protection path, 4-28 port, 4-28 Write community TransAccess 200 Mux, 3-9, 5-74, 5-77, 5-80, 5-82 WTR 1+1 APS, 4-22 1+1 MSP, 4-22 1+1 optimized protection, 4-34 BLSR ring, 4-2 Carrier Ethernet Protection Pair, 4-31 equipment protection, 4-16 MS-SP ring, 4-2 time, 6-20, 6-35 Index-20 Turin Networks Release TN4.0.x

Visit our website at: www.turinnetworks.com Release TN4.0.x TransNav Management System Documentation 800-0007-TN40