transnav gui guide - force10€¦ · 17/3/2010 · configure web browser settings for internet...

TransNav Graphical UserInterface GuideRelease TN4.2.3 March 2010 Edition 1

Copyright © 2010 Force10 Networks, Inc.

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

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

TRANSNAV MANAGEMENT SYSTEM GUI REFERENCE GUIDE

Contents

Section 1 Installation and OverviewChapter 1 Installation for Windows Workstations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3Chapter 2 Installation for Solaris Workstations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11Chapter 3 Starting the Graphical User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-17Chapter 4 General Description of EMS Server GUI. . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-27Chapter 5 Managing TE-206 Nodes from TransNav . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-45

Section 2 Administrative TasksChapter 1 Managing Server Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3Chapter 2 Managing Node Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13Chapter 3 Using TransNav GUI with TN-Sight. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17Chapter 4 TransNav User Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-21Chapter 5 Generating and Viewing Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-33

Section 3 NetworkChapter 1 Creating and Deleting Equipment Using Preprovisioning . . . . . . . . . . . . . . . 3-3Chapter 2 Network Auto Discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-19Chapter 3 Node Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-21Chapter 4 DCC Tunnels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-33Chapter 5 Configuring IP Quality of Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-35

Section 4 Protection SwitchingChapter 1 BLSR and MS-SPRing Protection Groups . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3Chapter 2

Release TN4.2.3 Force10 Networks Page i

TransNav GUI Guide

UPSR and SNCP Ring Protection Groups . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11Chapter 3 Equipment Protection Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-17Chapter 4 1+1 MSP/APS Protection Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-23Chapter 5 1+1 Path Protection Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-29Chapter 6 Carrier Ethernet Protection Pair . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-31Chapter 7 1+1 Optimized Protection Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-35

Section 5 EquipmentChapter 1 Common Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3Chapter 2 SONET Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7Chapter 3 SDH Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-31Chapter 4 Ethernet Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-49Chapter 5 TransAccess 200 Mux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-73Chapter 6 TraverseEdge 50 (TE-50) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-79

Section 6 ServicesChapter 1 Service Creation Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5Chapter 2 SONET Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-19Chapter 3 SDH Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-31Chapter 4 Ethernet Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-43Chapter 5 VC-Bundles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-57Chapter 6 Service Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-69Chapter 7 Managing Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-73Chapter 8 Managing Service Paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-85

Section 7 DCS ApplicationsChapter 1 DCS-384 Matrix Shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3Chapter 2 DCS-IO Shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-19Chapter 3

Page ii Force10 Networks Release TN4.2.3

TransNav GUI Guide

DCS-96 Shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-27

Section 8 Maintenance and TestingChapter 1 Performance Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3Chapter 2 Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-15Chapter 3 Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-29Chapter 4 Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-39Chapter 5 Test Access. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-47Chapter 6 Software Upgrades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-53

Section 9 AppendicesAppendix A Service Endpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3

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

Release TN4.2.3 Force10 Networks Page iii

TransNav GUI Guide

Page iv Force10 Networks Release TN4.2.3

SECTION 1 INSTALLATION AND OVERVIEW

Contents

Chapter 1Installing the GUI on Windows Workstations

Before You Install the GUI Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3Configure Web Browser Settings for Internet Explorer . . . . . . . . . . . . . . . . . . 1-4Install the GUI Application on a Remote Windows Workstation . . . . . . . . . . . 1-8Uninstall the GUI from Windows Workstation . . . . . . . . . . . . . . . . . . . . . . . . . 1-10

Chapter 2GUI Installation for Solaris Workstations

Before You Install the GUI Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11Configure Window Manager Settings for Solaris. . . . . . . . . . . . . . . . . . . . . . . 1-12Install the GUI Application on a Solaris Workstation . . . . . . . . . . . . . . . . . . . . 1-13Uninstall the GUI from a Solaris Workstation . . . . . . . . . . . . . . . . . . . . . . . . . 1-16

Chapter 3General Description of EMS Server GUI

Map View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-18Shortcut Menus for Map View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-18Traverse Shelf View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-20Shortcut Menus for Shelf View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-22TE-100 Shelf View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-24Shortcut Menus for TE-100 Shelf View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-25Managing TE-206 Nodes from TransNav . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-27

TE-206 Settings Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-27Settings Requirements for Traverse and TE-100 Nodes. . . . . . . . . . . . . 1-27

GUI Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-28File Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-28View Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-28Alarms Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-29Events Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-29Services Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-30Service Groups Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-30Admin Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-31Provisioning Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-34Help Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-34GUI Conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-34Scroll Bars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-35Resizing Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-35

Chapter 4Starting the Graphical User Interface


TransNav GUI Guide Section 1 Installation and Overview

TransNav GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-37Node-level GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-37

Starting the GUI from the Management Server . . . . . . . . . . . . . . . . . . . . . . . . 1-38Starting the GUI Application on a Windows Platform . . . . . . . . . . . . . . . . . . . 1-40Starting the GUI Application on a Solaris Platform . . . . . . . . . . . . . . . . . . . . . 1-42TransNav Client Workstation GUI User Login . . . . . . . . . . . . . . . . . . . . . . . . . 1-44Guidelines to Starting the Node-level GUI. . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-46Install the Node-level GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-46Starting the Node-level GUI Application on a Windows Platform . . . . . . . . . . 1-47Node-level GUI User Login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-49Configuring DHCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-51

Chapter 5Node-Level GUI General Description

Node-Level Shelf View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-54Shortcut Menus for Shelf View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-55Node-level GUI Menu Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-56File Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-56View Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-56Alarms Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-57Events Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-57Admin Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-58Help Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-59GUI Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-59Scroll Bars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-59Resizing Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-60Customize System Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-60Saving User Preferences. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-61

Chapter 6Managing TE-206 Nodes from TransNav

Map View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-64Shortcut Menus for Map View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-65Traverse Shelf View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-68Shortcut Menus for Shelf View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-69TE-100 Shelf View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-72Shortcut Menus for TE-100 Shelf View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-73GUI Menus. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-74File Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-75View Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-75Alarm Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-76Events Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-76Services Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-77Service Groups Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-78Admin Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-78Provisioning Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-81Help Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-81


TransNav GUI Guide, Section 1 Installation and Overview

GUI Conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-81Scroll Bars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-82Resizing Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-82

Release TN4.2.3 Force10 Networks Page iii

TransNav GUI Guide Section 1 Installation and Overview

Page iv Force10 Networks Release TN4.2.3


Chapter 1 Installing the GUI on Windows Workstations

Introduction 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• Install the GUI Application on a Remote Windows Workstation• Uninstall the GUI from Windows Workstation

See Chapter 2—“GUI Installation for Solaris Workstations” for the procedures to install the GUI application on a Sun Solaris workstation.

Before You Install the GUI Application

To access the GUI on a computer other than the management server, install the GUI application onto the remote computer. Force10 recommends installing the GUI 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 Reference

GUI application requirements See the TransNav Management System Product Overview Guide, Section 2—Management System Planning, Chapter 1—“TransNav Management System Requirements”.

Windows configuration requirements for GUI application

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 to configure the environment.

Support for Citrix server Force10 supports using the GUI application on a Citrix server.

Starting the GUI application See Section 1—Installation and Overview, Chapter 4—“Starting the Graphical User Interface” for detailed procedures on starting the GUI application.

Release TN4.2.3 Force10 Networks Page 1-3

TransNav GUI Guide, Section 1: Installation and OverviewConfigure 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 to 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-4 Force10 Networks Release TN4.2.3

Chapter 1 Installing the GUI on Windows WorkstationsConfigure Web Browser Settings for Internet Explorer

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

Table 1-2 Set Web Browser Settings for Internet Explorer (continued)

Step Procedure


TransNav GUI Guide, Section 1: Installation and OverviewConfigure Web Browser Settings for Internet Explorer

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.


Step Procedure


Chapter 1 Installing the GUI on Windows WorkstationsConfigure Web Browser Settings for Internet Explorer

6 Restart your computer.

7 The Set Web Browser Settings for Internet Explorer procedure is complete.

Continue to the procedure: Install GUI on a Remote Windows Workstation.


Step Procedure


TransNav GUI Guide, Section 1: Installation and OverviewInstall the GUI Application on a Remote Windows Workstation

Install the GUI Application on a Remote Windows Workstation

Use this procedure to help you install the GUI application on a remote Windows workstation.

Table 1-3 Install GUI on a Remote Windows Workstation

Step Procedure

1 Review the section Before You Install the GUI Application before you start this procedure.

2 Verify that the management server is started. See Start the Server.

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.

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


Chapter 1 Installing the GUI on Windows WorkstationsInstall the GUI Application on a Remote Windows Workstation

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 Remote Windows Workstation procedure is complete.

Continue to the one of the procedures in Section 1—Installation and Overview, Chapter 4—“Starting the Graphical User Interface.”

Table 1-3 Install GUI on a Remote Windows Workstation (continued)

Step Procedure


TransNav GUI Guide, Section 1: Installation and OverviewUninstall 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 Force10 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.


SECTION 1INSTALLATION AND OVERVIEW

Chapter 2 GUI Installation for Solaris Workstations

Introduction 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• Install the GUI Application on a Solaris Workstation• Uninstall the GUI from a Solaris Workstation

See Chapter 1—“Installing the GUI on Windows Workstations” for the procedures to install the GUI application on a Windows workstation.

Before You Install the GUI Application

To access the GUI on a computer other than the management server, install the GUI application onto the remote computer. Force10 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 Reference

GUI application requirements See the TransNav Management System Product Overview Guide, Section 2—Management System Planning, Chapter 1—“TransNav Management System Requirements,” page 2-1.

Solaris configuration requirements for GUI application

If this is the first time you are installing the TransNav system on the workstation, configure the environment using the following procedure:• Configure Window Manager Settings for Solaris.

Starting the GUI application See Section 1—Installation and Overview, Chapter 4—“Starting the Graphical User Interface” for detailed procedures on starting the GUI application.


TransNav GUI Guide, Section 1: Installation and OverviewConfigure 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:

Figure 1-8 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.

Clear box


Chapter 2 GUI Installation for Solaris WorkstationsInstall 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-6 Install GUI on a Solaris Workstation

Step Procedure

1 Review the section Before You Install the GUI Application before you start this procedure.

2 Verify that the management server is started. See Table 2-14 Start the Server.

3 If this is the first time you are installing the application, complete the procedure, Configure Window Manager Settings for Solaris.

4 Open a terminal window and change to the directory where you want to install the GUI application.

5 Open an internet browser 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-9 TransNav Management System Splash Screen


TransNav GUI Guide, Section 1: Installation and OverviewInstall the GUI Application on a Solaris Workstation

6 Click the shelf icon to start the installation of the GUI application.

Figure 1-10 Shelf Icon on Splash Screen

7 Select the correct directory as the file location and click OK.

Figure 1-11 Solaris Client—Save As Dialog Box

8 A dialog box displays indicating the download progress.

The dialog box closes when the download is complete.

9 From a terminal window, change to the directory where you installed the setup file.

10 Change the file permissions to make the installation file executable:$ chmod +x NMSGUISetup.bin

11 Execute the installation:$ ./NMSGUISetup.bin

Table 1-6 Install GUI on a Solaris Workstation (continued)

Step Procedure


Chapter 2 GUI Installation for Solaris WorkstationsInstall the GUI Application on a Solaris Workstation

12 Follow the directions on the Installer Wizard until the GUI application is installed on your computer.

Figure 1-12 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 4—“Starting the Graphical User Interface.”

Table 1-6 Install GUI on a Solaris Workstation (continued)

Step Procedure


TransNav GUI Guide, Section 1: Installation and OverviewUninstall 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-7 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.



Chapter 3 General Description of EMS Server GUI

Introduction This chapter provides a description of the navigational components of the graphical user interface (GUI) on the TransNav management server. From this interface, you can manage Traverse, TraverseEdge, and TransAccess nodes. A subset of these GUI components are available on the Node-level GUI. For information on the Node-level GUI components, see Chapter 5—“Node-Level GUI General Description”

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-18) displays all the nodes in a network and is the initial display when you start the GUI.

The Traverse Shelf View (page 1-20) displays all the cards (modules) in a node and their associated ports.

The TE-100 Shelf View (page 1-24) displays the shelf view for the TE-100.

Managing TE-206 Nodes from TransNav indicates

This chapter also describes the following GUI features:• GUI Menus• GUI Conventions• Resizing Capabilities• Scroll Bars• Resizing Capabilities


TransNav GUI Guide, Section 1: Installation and OverviewMap View

Map View 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.”c• 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. • Service Group: Configure a number of services into groups on the node. See

Section 6—Services, Chapter 5—“Service Groups.”

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-13 Map View Shortcut Menu #1

Menu selections are:• Show Shelf View: View the selected shelf (node).• Delete Node: Delete the selected node (shelf).


Chapter 3 General Description of EMS Server GUIShortcut Menus for Map View

• Synchronize Node: Synchronize the node with the management server so the server contains the most recent node configuration and alarms information.

• 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 TA-200 or a TE-50 subshelf.

When you right-click the background image, the following menu displays:


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,” Create a Node.• Add Link: Add a physical link between ports. See Section 3—Network,

Chapter 1—“Creating and Deleting Equipment,” Add a Link.• Add Group: Create a new group of nodes or add a node to a group.• Change Background: Select to change the background map. To change the group

name, see the TransNav Management System Server Guide, Section 2—Management Server Procedures, Chapter 3—“Server Administration Procedures,” Customizing Background Images.

• Zoom In: Zoom in on the current view.• Zoom Out: Zoom out on the current view.• Restore: Restore the original view.


TransNav GUI Guide, Section 1: Installation and OverviewTraverse Shelf View

Traverse Shelf View

Shelf View displays all of the cards in a node and their associated ports. From the node-level GUI, this is the only view available. Available features are specific to maintenance tasks performed at the node level. Domain level users can use the TransNav server GUI to perform tasks at the network level. From the TransNav server GUI, 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.

Figure 1-15 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.

Currently selected object

Menu bar

BITS clock

Context-sensitive tab screen

Port LED status

ORAlarm

indicators


Chapter 3 General Description of EMS Server GUITraverse Shelf View

A shortcut menu also exists for Shelf View. For more information about the EMS server GUI features, see the TransNav Management System GUI Guide, Section 1—Installation and Overview, Chapter 3—“General Description of EMS Server GUI”. For information about the Node-level GUI features, see the TransNav Management System GUI Guide, Section 1—Installation and Overview, Chapter 5—“Node-Level GUI General Description”.

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.”• Events: Events on the selected card or port. See Section 8—Maintenance and

Testing, Chapter 3—“Events.”• Config: Configuration information on the selected card or port. See

Section 5 Equipment Configuration.• Diagnostic: Diagnostics tests on the selected port. See Section 8—Maintenance

and Testing, Chapter 4—“Diagnostics”.• Timing: Timing information on the selected card or port. See Section 3—Network,

Chapter 3—“Node Timing”.• DCC Tunnel: Configure DCC tunnels on the node. See Section 3—Network,

Chapter 4—“DCC Tunnels”.• Protection: Protection groups for the node. See Section 4 Protection Switching.• 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”.

• Ethernet: Configure EOS, LAG, and Policer on the node. See Section 5—Equipment, Chapter 4—“Ethernet Equipment”.

• 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 the TransNav Provisioning Guide, Section 2—Creating ADM Services, Chapter 1—“Service Provisioning Concepts.”.

• Service Group: Configure a number of services into groups on the node. See Section 6—Services, Chapter 5—“Service Groups.”

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.


TransNav GUI Guide, Section 1: Installation and OverviewShortcut Menus for Shelf View

Shortcut Menus 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-16 Shelf View Shortcut Menu #1

Menu selections for the TransNav GUI shortcut menu 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: Click to see a list of cards available to 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.


Chapter 3 General Description of EMS Server GUIShortcut Menus for Shelf View

When you right-click a slot occupied by a card, a different menu displays.


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.


TransNav GUI Guide, Section 1: Installation and OverviewTE-100 Shelf View

TE-100 Shelf View

When you double-click a TraverseEdge 100 (TE-100) 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.

Figure 1-18 TraverseEdge 100 Shelf View

See the TraverseEdge 100 User Guide for detailed information about installing and commissioning the TE-100.

Alarm summary tree

Network navigation tree


Optical Ports 1 and 2 (click for port configuration)

and SFP Ports

(click for SFP information)

External Synchronization

References A and B

Tributary Card Ports (6 FE, 2 GbE, 3 DS3, 28 DS1)


Chapter 3 General Description of EMS Server GUIShortcut Menus for TE-100 Shelf View

Shortcut Menus for TE-100 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




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.


TransNav GUI Guide, Section 1: Installation and OverviewShortcut Menus for TE-100 Shelf View




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



Chapter 3 General Description of EMS Server GUIManaging TE-206 Nodes from TransNav

Managing TE-206 Nodes from TransNav

TransNav can be used to manage TraverseEdge 206 (TE-206) nodes as either standalone nodes or in a network ring.

If the TE-206 is a standalone node in the Traverse network, it can be discovered from the TransNav GUI by selecting Admin > Discovery and entering the node IP address. For more information, see Chapter 3—“Using TransNav GUI with TN-Sight,” Provisioning TE-206 Nodes from TransNav.

Each time a TE-206 node or link is added or removed from the network, use the Rediscovery option from the Admin menu to manually notify the TransNav GUI to discover the changes.

Note: TE-100 nodes in the network must be upgraded to release TE3.2.3.

TE-206 Settings Requirements

The following rules apply if a TE-206 is included in a Traverse network ring: • The network ring must be of OC-48 interfaces. • Proxy ARP must be enabled on the Traverse gateway node• From TN-Sight, set the following values as indicated:

– DCC Type: Value for the SONET port must be set to Section on all east and west ports of nodes in the network ring. (Note: To change this value, the Control Data value on the SONET port must be disabled.)

– CRC Type: Value must be set to 32.– Enable PPP: Must be selected (enabled).

Figure 1-21 TE-206 DCC Settings for Management by TransNav

Settings Requirements for Traverse and TE-100 Nodes

For Traverse and TE-100 nodes, make sure the port parameters for the OC48 ports on either side of the TE-206 node are set as follows: • Terminate DCC: Set to Section on all east and west ports of nodes in the network

ring. • L2 Protocol: Set to PPP.

Note: To change the Terminate DCC and L2 Protocol values, the Control Data parameter must be set to disable. Re-enable the Control Data parameter after the changes are made to enable the DCC changes.


TransNav GUI Guide, Section 1: Installation and OverviewGUI Menus

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-28• View Menu, page 1-28• Alarms Menu, page 1-29• Events Menu, page 1-29• Services Menu, page 1-30• Service Groups Menu, page 1-30• Admin Menu, page 1-31• Provisioning Menu, page 1-34• Help Menu, page 1-34

File Menu Use the commands on the File menu to manage user preferences. See Section 2—Administrative Tasks, Chapter 4—“TransNav User Preferences,” page 2-23 for detailed information about these commands.

View Menu Use the commands on the View menu to set your screen to your required dimensions.

Figure 1-22 File Menu

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.

3. Exit. Exit the application and close the main window.

1.2.3.

Figure 1-23 View Menu

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.

5. Zoom Out - CTRL-O: Zoom out on the current view.

6. Restore - CTRL-C: Restore the view to the default setting.

1.2.3.4.5.6.


Chapter 3 General Description of EMS Server GUIEvents Menu

Alarms Menu Use the commands on the Alarms menu to help you manage information on the Alarms tab. See Section 8—Maintenance and Testing, Chapter 2—“Alarms,” page 8-15 for detailed information about the Alarms tab.

Events Menu 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-31 for detailed information about the Events tab.

Figure 1-24 Alarms Menu

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.

3. Acknowledge: Acknowledge the selected alarm.

4. Detail View: Display selected alarm details through the Alert Detail (View Main) dialog box.

1.2.3.4.

Figure 1-25 Events Menu

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.

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.

1.

2.

3.4.5.


TransNav GUI Guide, Section 1: Installation and OverviewServices Menu

Services Menu Use the commands on the Services menu to help you manage information on the Services tab. See Section 6 Services for detailed information on services.

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 5—“Service Groups” for detailed information about the Service Group tab.

Figure 1-26 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 TransNav Provisioning Guide, Section 2—Creating Service Applications, Chapter 2—“Bridging and Rolling Services” 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.

1.2.3.4.5.6.7.

8.9.

10.11.12.

Figure 1-27 Service 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.

1.

2.

3.4.5.


Chapter 3 General Description of EMS Server GUIAdmin Menu

Admin Menu Use the commands on the Admin menu of the TransNav server GUI 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.

Figure 1-28 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”.

2. Bandwidth Profiles: Create Ethernet bandwidth profiles on the TransNav management server.

3. Classifiers: Create Ethernet traffic management classifiers for 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 to disable and enable alarms. See Section 8—Maintenance and Testing, Chapter 2—“Alarms”.

6. Reports: Generate and define reports. See Section 2—Administrative Tasks, Chapter 5—“Generating and Viewing Reports”.

7. Customer: Define customer information. See Section 2—Administrative Tasks, Chapter 5—“Generating and Viewing Reports”.

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”.

9. Domain User: Define, change, or delete a domain user through pre-defined roles. See Section 2—Administrative Tasks, Chapter 1—“Managing Server Security”.

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”.

11. Current User: Display the current user name and change the password. See Section 2—Administrative Tasks, Chapter 1—“Managing Server Security”.

12. Session List: Display the current users on the management system.

1.2.3.4.5.6.7.

9.

11.12.

8.

10.

13..14.

15.16.17.

18.19.

20.21.22.23.24.

25.


TransNav GUI Guide, Section 1: Installation and OverviewAdmin Menu

13. Discovery: Enter the name or IP address of the Management Gateway Node(s). See Section 3—Network, Chapter 2—“Network Auto Discovery”.

14. Rediscovery: Use to rediscover TE-206 nodes or links that are added or removed from the network. This manually notifies TransNav to discover the changes. See Section 2—Administrative Tasks, Chapter 3—“Using TransNav GUI with TN-Sight.”

15. Show Empty Tunnels:

16. Service Availability Status Audit: Use to audit the availability status of each service in the network. The service availability status is corrected if necessary. An event is added to the event log indicating the start and completion information of the audit. For more information, see Section 6—Services, Chapter 6—“Managing Services,” Service Availability Status Audit.

17. SW Upgrade: Perform a software upgrade. See Section 8—Maintenance and Testing, Chapter 6—“Software Upgrades”.

18. SW Activation: Activate the software.

19. Node Backup Scheduler: Set up an automatic backup schedule for one or more nodes in the network. For more information, see the Operations and Maintenance Guide, Section 6—Routine Maintenance, Chapter 2—“Node Database Backup and Restore,” TE-206 Node Backups from the TransNav GUI.

20. IP Static Route Configuration: Add static routes to a node for management IP traffic.

21. DHCP Configuration: Configure a node to enable a user to manage the node with automatic IP configuration. For more information on setting up DHCP from the EMS server, see the TransNav Management System Server Guide, Section 2—Management Server Procedures, Chapter 3—“Server Administration Procedures,” Configuring DHCP.

22. OSI Static Route Configuration: Add static routes to a node for OSI (open system interconnection).

23. OSI Parameters Configuration: Configure a node to be an OSI gateway node.

24. 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”.


Chapter 3 General Description of EMS Server GUIAdmin Menu

25. Options: Turn on or off the audible alarm, set time zone and date format, and set the number of services (Services per page) for display options.

26. SNMP Configuration: Set the Traverse node SNMP agent read and write community strings, four trap destination IP addresses, ports, and trap community strings.

27. Attached Devices SNMP Parameters: Set the SNMP sub-shelf devices polling and synchronization intervals for the management server.


TransNav GUI Guide, Section 1: Installation and OverviewProvisioning Menu

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” for detailed information on creating and configuring equipment in the network.

Help Menu Use the commands on the Help menu to display the online help information for the graphical user interface.

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:

Figure 1-29 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”.

4. Add TE50: Add a TraverseEdge 50 sub-shelf to the management interface. To add a TraverseEdge 50 sub-shelf, see the TransNav Management System GUI Guide, Section 5—Equipment, Chapter 6—“TraverseEdge 50 (TE-50)”.

1.2.3.4.

Figure 1-30 Help Menu

1. On Application: Display help on the user interface application.

2. About: Display the management system version number.1.2.


Chapter 3 General Description of EMS Server GUIResizing Capabilities

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.

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.


TransNav GUI Guide, Section 1: Installation and OverviewResizing Capabilities



Chapter 4 Starting the Graphical User Interface

Introduction This chapter contains procedures on how to start the graphical user interface (GUI) for the TransNav management system and the node-level GUI.

TransNav GUI

• Starting the GUI from the Management Server• Starting the GUI Application on a Windows Platform• Starting the GUI Application on a Solaris Platform• TransNav Client Workstation GUI User Login

Force10 recommends using the server GUI application directly on the client workstation for faster initialization, operation, and response time. • For Windows workstations, see Chapter 1—“Installing the GUI on Windows

Workstations”.• For Solaris workstations, see Chapter 2—“GUI Installation for Solaris

Workstations”.

Node-level GUI

The node-level GUI, also called the craft GUI, is used on a client workstation for work at a remote site. Force10 recommends launching between 5 and 10 individual node-level GUIs simultaneously from a single laptop or PC on a Windows platform only; the actual number of GUIs you can start depends on the size of the node and the available RAM.

The node-level GUI is designed to provide faster initialization, operation, and response time for a specific node. DHCP can be configured from the TransNav EMS server or on the node to allow automatic IP configuration for a node user’s Windows computer using the cable jack on the front of the GCM. • Guidelines to Starting the Node-level GUI• Starting the Node-level GUI Application on a Windows Platform• Node-level GUI User Login • Configuring DHCP


TransNav GUI Guide, Section 1: Installation and OverviewStarting 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-8 Start the GUI Application from the Management Server

Step Procedure

1 Verify the management server is started. See the TransNav Management System Server Guide, Section 2—Management Server Procedures, Chapter 3—“Server Administration Procedures,” Start the Server Administration Tool.

2 In the Server Admin application, click Execution, then click Start GUI.

Figure 1-31 Server Admin Application—Start GUI


Chapter 4 Starting the Graphical User InterfaceStarting the GUI from the Management Server

3 The Login dialog box displays.

Figure 1-32 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 server system, enter localhost.• Connect to: Select Server (default) or Node.

Select Server from the drop-down menu to logon to the server GUI. Allows you to view all nodes and node groups in the network. If you are running the server or client from the server, Force10 recommends connecting to the server. Select Node from the drop-down menu to logon to the node-level GUI. If you select Node, you will only be able to view the shelf view of the selected node.

b. Click Login.

4 The Start the GUI Application from the Management Server procedure is complete.

Continue to the procedure Password Changes.

Table 1-8 Start the GUI Application from the Management Server (continued)

Step Procedure


TransNav GUI Guide, Section 1: Installation and OverviewStarting the GUI Application on a Windows Platform

Starting the GUI Application on a Windows Platform

To access the management software on a Windows client workstation (other than the management server), install the GUI application onto the remote computer. Use this procedure to start the GUI application on a remote computer.

Table 1-9 Start the GUI Application on a Windows Platform

Step Procedure


2 Verify the GUI application is installed. See the procedure, Chapter 1—“Installing the GUI on Windows Workstations,” Install the GUI Application on a Remote Windows Workstation.

3 From the Start menu, click Programs, Force10, then click TransNav(TM) GUI

.

.

Figure 1-33 Start Menu


Chapter 4 Starting the Graphical User InterfaceStarting the GUI Application on a Windows Platform







Select Server from the drop-down menu to logon to the server GUI. Allows you to view all nodes and node groups in the network. If you are running the server or client from the server, Force10 recommends connecting to the server. Select Node from the drop-down menu to logon to the node-level GUI. If you select Node, you will only be able to view the shelf view of the selected node.

b. Click Login.


Continue to the procedure, Password Changes.

Table 1-9 Start the GUI Application on a Windows Platform (continued)

Step Procedure


TransNav GUI Guide, Section 1: Installation and OverviewStarting 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—“GUI Installation for Solaris Workstations”.)

Use this procedure to start the GUI application on a remote computer.

Table 1-10 Start the GUI Application on a Solaris Platform

Step Procedure


2 Verify the GUI application is installed. See the procedure, Chapter 2—“GUI Installation for Solaris Workstations,” Install the GUI Application on a Solaris Workstation.

3 In a terminal window, change to the directory where you installed the GUI application.

4 Enter the following command:

$ ./ems_gui.sh


Chapter 4 Starting the Graphical User InterfaceStarting the GUI Application on a Solaris Platform







Select Server from the drop-down menu to logon to the server GUI. Allows you to view all nodes and node groups in the network. If you are running the server or client from the server, Force10 recommends connecting to the Server. Select Node from the drop-down menu to logon to the node-level GUI. If you select Node, you will only be able to view the shelf view of the selected node.

b. Click Login.


Continue to the procedure Password Changes.

Table 1-10 Start the GUI Application on a Solaris Platform (continued)

Step Procedure


TransNav GUI Guide, Section 1: Installation and OverviewTransNav Client Workstation GUI User Login

TransNav Client Workstation GUI User Login

Force10 recommends using the GUI application directly on the TransNav client workstation for faster initialization, operation, and response time. HTTPS security is also available.

When you start the GUI, the Login dialog box displays.

Figure 1-36 Login Dialog Box

Enter the following information in the Login dialog box:• User Name: Your user name as assigned by the system administrator. Default is

admin.• Password: Your user password as 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• Connect to: Select Server (default) or Node.

– Select Server from the drop-down menu to logon to the server GUI which allows you to view all nodes and node groups in the network. If you are running the server or the client from the server, Force10 recommends connecting to the server.

– Select Node from the drop-down menu to logon to the node-level GUI. If you select Node, you will only be able to view the shelf view of the selected node. .

• Advanced: When this check box is selected, the advanced settings display. This selection is available only if Server is selected in the Connect to parameter.

Important: For security reasons, Force10 recommends that you change the default User Name and/or Password. To create a new user account, see Domain Users or Node Users. To change the Password only, see Password Changes.


Chapter 4 Starting the Graphical User InterfaceTransNav Client Workstation GUI User Login

Figure 1-37 Login Dialog Box - Advanced Server Settings

When the Advanced check box is selected, you can view and change the following parameters for the EMS server:• Protocol: Select one of the following protocols:

– RMI (Remote Method Invocation) (default)– HTTP (Hyper Text Transfer Protocol)– HTTPS (Hyper Text Transfer Protocol Secure). Available only for clients

attached to a server. The server must have an HTTPS server key enabled; the client IP address must be enabled on the server. Client users must enter the IP address of the server with HTTPS enabled. For information on setting up the HTTPS server key, see Section 2—Management Server Procedures, Chapter 1—“Creating the Management Servers,” Configure HTTPS.

• Port Number: Enter a port number.• Notification (Informational only): A notification is any change to the server

database, such as new alarms or changes to configuration information. The TransNav GUI queries the server for new notifications every couple of seconds.

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.


TransNav GUI Guide, Section 1: Installation and OverviewGuidelines to Starting the Node-level GUI

Guidelines to Starting the Node-level GUI

Use the following guidelines to set up and start the node-level GUI.

Download a copy of the management system server software to a directory accessible by all users to download the node-level GUI. The server software can have a blank database.• Verify the node and server are using compatible versions of software. • For new installations, make sure the web browser settings for Internet Explorer

have been set up. For more information, see Chapter 1—“Installing the GUI on Windows Workstations,” Install the GUI Application on a Remote Windows Workstation.

• To access the node-level GUI from a remote computer using a jack on a GCM card, you must configure the DHCP on either the management server GUI or on the node-level GUI from the Admin menu.

• If DHCP is not configured, assign an IP address to the laptop. The GCM Gateway must have the same IP address as the GCM IP. The debug-gw IP address must also match the GCM IP address.

Install the Node-level GUI

A copy of the management system server software must be downloaded to a directory accessible by all users to download the node-level GUI. The server software can have a blank database. When the server software is downloaded, remote users can install the node-level GUI application to their laptop by opening a web browser window and entering http://<server name>:9090 in the locator bar.

For instructions on installing the GUI application, see Chapter 1—“Installing the GUI on Windows Workstations,” Install the GUI Application on a Remote Windows Workstation.


Chapter 4 Starting the Graphical User InterfaceStarting the Node-level GUI Application on a Windows Platform

Starting the Node-level GUI Application on a Windows Platform

To access the node-level GUI software on a Windows client workstation, install the GUI application onto the remote computer. Use this procedure to start the GUI application on a remote computer or locally on a laptop using a craft port to connect to a node GCM.

For information on installing the GUI, see Chapter 1—“Installing the GUI on Windows Workstations,” Install the GUI Application on a Remote Windows Workstation.

Table 1-11 Start the Node-level GUI Application on a Windows Platform

Step Procedure

1 Verify the GUI application is installed.

2 From the Start menu, click Programs, Force10, then click TransNav(TM) GUI.

Figure 5 Start Menu


TransNav GUI Guide, Section 1: Installation and OverviewStarting the Node-level GUI Application on a Windows Platform


Figure 6 GUI Login Dialog Box



Default is admin.• Host Name: Enter the IP address of the specific node to be accessed.• Connect to: Select Node from the drop-down menu to logon to the

node-level GUI and view the shelf view of the selected node. b. Click Login.

4 The Start the GUI Application on a Windows Platform procedure is complete.

Table 1-11 Start the Node-level GUI Application on a Windows Platform

Step Procedure


Chapter 4 Starting the Graphical User InterfaceNode-level GUI User Login

Node-level GUI User Login

Force10 recommends using the node-level 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 7 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: Enter the IP address of the specific node to be accessed. • Connect to: Select Node from the drop-down menu to logon to the node.

• Advanced: When this check box is selected, the advanced settings display.

Important: For security reasons, Force10 recommends that you change the default User Name and/or Password. To create a new user account, see the TransNav Management System GUI Guide, Section 2—Administrative Tasks, Chapter 1—“Managing Server Security” or Section 2—Administrative Tasks, Chapter 2—“Managing Node Security.”. To change the Password only, see Section 2—Administrative Tasks, Chapter 1—“Managing Server Security,” Password Changes.


TransNav GUI Guide, Section 1: Installation and OverviewNode-level GUI User Login

Figure 8 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: (Informational only) A notification is any change to the server

database, such as new alarms or changes to configuration information.

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.


Chapter 4 Starting the Graphical User InterfaceConfiguring DHCP

Configuring DHCP

Configuring DHCP from the TransNav server or from a node allows automatic IP configuration to a specified node. The server implementation is compliant with RFC213. Node-level users can then access the node via an Ethernet cable from the front Ethernet port on a GCM card.

From the TransNav GUI, you must click a node in Map View to select the node to be configured.

From the TransNav GUI or the node-level GUI, select DHCP Configuration from the Admin menu to display the DHCP Configuration dialog box.

Figure 9 DHCP Configuration Dialog Box

GCM-A: Select this tab to configure the settings for the GCM card in the left-side slot on the shelf.

GCM-B: Select this tab to configure the settings for the GCM card in the right-side slot on the shelf.

IP from: Enter an IP address in the range for the GCM being configured.

To determine the GCM IP address, from Shelf View click below the cards to display the Node view. Click the Config tab. The Node Configuration screen containing the IP address information displays.

IP to: Enter a subnet IP address in the range of the GCM being configured.

Gateway (Optional): Enter the IP address of the default gateway for the GCM being configured.

Lease time (sec): Enter the number of seconds the node can be accessed by a node user for each session. Default is 6000 seconds.

Enabled: Click the checkbox to enable the DHCP configuration on the selected GCM card.

Command buttons are as follows:

Show Lease: Displays a text box indicating the following information about a DHCP connection:

– the GCM’s ID/MAC address, IP address, Subnet Mask


TransNav GUI Guide, Section 1: Installation and OverviewConfiguring DHCP

– if the connection is In-Use (True or False)– the date/time when the connection (DHCP Lease) expires

Update: Update any changes made to the configuration.

Close: Close the DHCP Server Configuration dialog box.



Chapter 5 Node-Level GUI General Description

Introduction This document provides a description of the navigational components of the TransNav Node-level graphical user interface (GUI). Similar to the TransNav management system GUI, the Node-level graphical user interface (also called the Craft GUI) provides a shelf view of a Traverse node for easier maintenance. The Node-level GUI does not communicate with the TransNav server.

Any IP-based management connection can provide the communication path between the Node-level GUI and the Traverse system’s active GCM, including front-access craft Ethernet, Backplane Ethernet, DCC, and ECC.

Note: The Node-level GUI works only with Traverse nodes in this release. TE-100 and TE-206 nodes are not supported. The information in the Node-level GUI application is obtained directly from the Traverse platform. The Node-level GUI release must match the corresponding Traverse release.

This chapter describes the following features of the Node-level GUI:• Node-level GUI Menu Options• GUI Conventions• Resizing Capabilities• Scroll Bars• Resizing Capabilities

Release TN4.2.3 Force10 Networks Page 53

TransNav GUI Guide, Section 1: Installation and OverviewNode-Level Shelf View

Node-Level Shelf View

When you log onto a node using the node-level GUI, a Shelf View of the node displays all of the cards in the node and their associated ports.

Figure 6 Node-Level GUI Shelf View

The menu bar is context-sensitive. Commands are displayed in the drop-down menus of each menu option as available (highlighted) or unavailable (grayed out), depending on the selected object (card or port).

You can see which object is selected by the white rectangle around the object in the graphic and the name displayed in the top and bottom bars of the window. If no object is selected, the node name displays.

Context-sensitive tabs (in the bottom half of the screen) provide node, card, or port information on alarms, events, configuration information, protection, and services. 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. • Events: Events on the selected card or port. • Config: Configuration information on the selected card or port. • Diagnostic: Diagnostics tests on the selected port. • Timing: Timing information on the selected card or port. • DCC Tunnel: Configure DCC tunnels on the node. • Protection: Protection groups for the node.


Menu bar

BITS clock

Context-sensitive tab

screen

Port LED status

ORAlarm

indicators

Page 54 Force10 Networks Release TN4.2.3

Chapter 5 Node-Level GUI General DescriptionShortcut Menus for Shelf View

• Performance: Performance monitoring data for the selected card or port and capacity monitoring data for selected VT/TU cards.

• Ethernet: Configure EOS, LAG, and Policer on the node. • Test Access: Provides non-intrusive monitoring and intrusive split testing on

digital cross-connect and add-drop multiplexer systems. • Service: Services provided from the node. • Service Group: Configure a number of services into groups on the node.




Figure 7 Shelf View Shortcut Menu #1

Menu selections for the Node-level GUI shortcut menu are:• Add [card type] Cards: 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.


Figure 8 Shelf View Shortcut Menu #2

Menu selections are:• Delete Card: Delete the selected card.• Restart Card Warm: Restart the processor on the selected card (hitless).• Restart Card Cold: Restart the selected card.• Zoom In: Zoom in on the current view.


TransNav GUI Guide, Section 1: Installation and OverviewNode-level GUI Menu Options

• Zoom Out: Zoom out on the current view.• Restore: Restore the original view.

Node-level GUI Menu Options

Each menu option 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• View Menu• Alarms Menu• Events Menu• Admin Menu• Help Menu

File Menu Use the commands on the File menu to manage user preferences on the Node-level GUI.


Figure 9 File Menu

1. Save User Preferences. Save Alarms and Events sorting and filter settings under the current user name.

2. Exit. Exit the application and close the main window.1.2.

Figure 10 View Menu




1.2.3.


Chapter 5 Node-Level GUI General DescriptionEvents Menu

Alarms Menu Use the commands on the Alarms menu to help you manage information on the Alarms tab. For alarm definitions, see the Operations and Maintenance Guide, Section 1—Fault Management, Chapter 2—“Alarms, Events, and Recommended Actions.”

Events Menu Use commands on the Events menu to help you manage the information on the Events tab.

Figure 11 Alarms Menu




1.2.3.

Figure 12 Events Menu






1.

2.

3.4.5.



Admin Menu Use the commands on the Admin menu to perform maintenance functions on the node..

Figure 13 Admin Menu

1. Performance Templates: View performance monitoring and capacity monitoring (VT/TU only) templates.

2. Bandwidth Profiles: Create Ethernet bandwidth profiles on the node.

3. Classifiers: Create Ethernet traffic management classifiers on the node.

4. Alarm Profiles: Set alarm profiles, including severities, for non-service-affecting and service-affecting alarms; also to disable and enable alarms. For more information on alarms, see the TransNav Management System GUI Guide, Section 8—Maintenance and Testing, Chapter 2—“Alarms.”

5. Node User: Allows users with Administrator privileges to define, change, or delete a node user through pre-defined access groups.

6. Current User: Display the current user name and change the password.

7. Session List: View the current users on the node, the node they’re logged onto and the time they logged on.

8. SW Upgrade: Perform a software upgrade. See the TransNav Management System GUI Guide, Section 8—Maintenance and Testing, Chapter 6—“Software Upgrades,” page 8-57.


10. IP Static Route Configuration: Add stcatic routes to a node for management IP traffic.

11. DHCP Configuration: Configure a DHCP server on the node for automatic IP configuration of a remote computer. See the Node-level GUI Guide, Chapter 4—“Starting the Graphical User Interface,” Configuring DHCP.

12. OSI Static Route Configuration: Add static routes to a node for OSI (open system interconnection). See the TransNav Provisioning Guide, Section 1—Configuring the Network, Chapter 6—“Creating a Traverse OSI Gateway Node”

13. OSI Parameters Configuration: Configure a node to be an OSI gateway node. See the TransNav Management System GUI Guide, Section 3—Network, Chapter 6—“OSI Parameters Configuration.”

1.

2.3.

4.5.

6.7.

9.

11.

12.

8.

10.

13.14.

15.

16.17.


Chapter 5 Node-Level GUI General DescriptionScroll Bars


GUI Conventions





Scroll Bars The user interface displays 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.

14. 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 the TransNav Management System GUI Guide, Section 3—Network, Chapter 5—“Configuring IP Quality of Service,” page 3-39.

15. Options: Turn on or off the audible alarm, set time zone and date format, and set the number of services (services per page) for display options. This feature is GUI specific to the workstation on which it is set up.


17. Attached Devices SNMP Parameters: Set the SNMP sub-shelf devices polling and synchronization intervals for the node.

Figure 14 Help Menu

1. About: Display the version number of the Node-level GUI software currently in use.

1.


TransNav GUI Guide, Section 1: Installation and OverviewResizing Capabilities


You can resize the Shelf View and Tab screen areas.


Customize System Options

Customize the sound, time, and date options in the Node-level user interface. From the Admin menu, select Options to display the Options dialog box.

Figure 15 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.

Service List: The ability to set the number of services (Services per page) for display as a savable user profile option—with values of 100, 200 (default), 500, and 1000.


Close: Close the dialog box and return to the main menu.


Chapter 5 Node-Level GUI General DescriptionSaving User Preferences

Saving User Preferences

After logging on and setting your user preferences on the Node-level GUI, you can save the following user preferences:• Alarm and event filter and sort settings

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.

Command buttons are as follows:• Refresh List: Refresh the Available list with all user IDs.• Cancel: Cancel saving the user preferences and close the dialog box.


TransNav GUI Guide, Section 1: Installation and OverviewSaving User Preferences


SECTION 1INSTALLATION AND OVERVIEW

Chapter 6 Managing TE-206 Nodes from TransNav

Introduction This chapter provides a description of managing TraverseEdge 206 nodes from 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 displays all the nodes in a network and is the initial display when you start the GUI.

The Traverse Shelf View displays all the cards (modules) in a node and their associated ports.

The TE-100 Shelf View displays the shelf view for the TE-100.

This chapter also describes the following GUI features:• GUI Menus• GUI Conventions• Resizing Capabilities• Scroll Bars• Resizing Capabilities


TransNav GUI Guide, Section 1: Installation and OverviewMap View

Map View Available only from the server GUI, Map View displays all of the node groups and discovered nodes for a server when you first start the server GUI. 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 domain 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.

Figure 1-38 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.

Menu bar


Context-sensitive tabs

Alarm summary tree



Chapter 6 Managing TE-206 Nodes from TransNavShortcut Menus for Map View

The context-sensitive tabs provide server, node group, or node information on alarms, events, configuration information, protection, services, and service groups.

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 the TransNav

Provisioning Guide, Section 2—Creating ADM Services, Chapter 1—“Service Provisioning Concepts.”

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.


Menu selections are:


TransNav GUI Guide, Section 1: Installation and OverviewShortcut Menus for Map View

• 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.• 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 subshelf.

When you right-click the background image, the following menu displays:


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,” Create a Node.• Add Link: Add a physical link between ports. See Section 3—Network,

Chapter 1—“Creating and Deleting Equipment,” Add a Link, page 3-16.• Add Group: Create a new group of nodes or add a node to a group.• Change Background: Select to change the background map. To change the group

name, see the TransNav Management System Server Guide, Section 2—Management Server Procedures, Chapter 3—“Server Administration Procedures,” Customizing Background Images.

• Zoom In: Zoom in on the current view.• Zoom Out: Zoom out on the current view.• Restore: Restore the original view.


Chapter 6 Managing TE-206 Nodes from TransNavShortcut Menus for Map View


TransNav GUI Guide, Section 1: Installation and OverviewTraverse Shelf View

Traverse Shelf View

Shelf View displays all of the cards in a node and their associated ports. From the node-level GUI, this is the only view available. Available features are specific to maintenance tasks performed at the node level. Domain level users can use the TransNav server GUI to perform tasks at the network level. From the TransNav server GUI, 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.

Figure 1-41 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.


Menu bar

BITS clock


Port LED status

ORAlarm

indicators


Chapter 6 Managing TE-206 Nodes from TransNavShortcut Menus for Shelf View

A shortcut menu also exists for Shelf View. For more information about the EMS server GUI features, see the TransNav Management System GUI Guide, Section 1—Installation and Overview, Chapter 3—“General Description of EMS Server GUI”. For information about the Node-level GUI features, see the TransNav Management System GUI Guide, Section 1—Installation and Overview, Chapter 5—“Node-Level GUI General Description”.

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-15.• Events: Events on the selected card or port. See Section 8—Maintenance and

Testing, Chapter 3—“Events,” page 8-31.• Config: Configuration information on the selected card or port. See

Section 5—Equipment Configuration, page 5-3.• Diagnostic: Diagnostics tests on the selected port. See Section 8—Maintenance

and Testing, Chapter 4—“Diagnostics,” page 8-43.• Timing: Timing information on the selected card or port. See Section 3—Network,

Chapter 3—“Node Timing,” page 3-25.• DCC Tunnel: Configure DCC tunnels on the node. See Section 3—Network,

Chapter 4—“DCC Tunnels,” page 3-37.• Protection: Protection groups for the node. See Section 4—Protection Switching,

page 4-3.• 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-3.

• 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 the TransNav Provisioning Guide, Section 2—Creating ADM Services, Chapter 1—“Service Provisioning Concepts.”

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.




TransNav GUI Guide, Section 1: Installation and OverviewShortcut Menus for Shelf View




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.


Chapter 6 Managing TE-206 Nodes from TransNavShortcut Menus for Shelf View




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



TransNav GUI Guide, Section 1: Installation and OverviewTE-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.

Figure 1-44 TraverseEdge 100 Shelf View

See the TraverseEdge 100 User Guide for detailed information about installing and commissioning the TE-100.

Alarm summary tree



Optical Ports 1 and 2 (click for port configuration)

and SFP Ports

(click for SFP information)

External Synchronization

References A and B

Tributary Card Ports (6 FE, 2 GbE, 3 DS3, 28 DS1)


Chapter 6 Managing TE-206 Nodes from TransNavShortcut Menus for TE-100 Shelf View

Shortcut Menus for TE-100 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




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.


TransNav GUI Guide, Section 1: Installation and OverviewGUI Menus




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


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• View Menu• Alarm Menu• Events Menu• Services Menu• Service Groups Menu• Admin Menu


Chapter 6 Managing TE-206 Nodes from TransNavView Menu

• Provisioning Menu• Help Menu

File Menu Use the commands on the File menu to manage user preferences. See Section 2—Administrative Tasks, Chapter 4—“TransNav User Preferences,” page 2-23 for detailed information about these commands.


Figure 1-47 File Menu

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.

3. Exit. Exit the application and close the main window.

1.2.3.

Figure 1-48 View Menu

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.




1.2.3.4.5.6.


TransNav GUI Guide, Section 1: Installation and OverviewAlarm Menu

Alarm Menu Use the commands on the Alarms menu to help you manage information on the Alarms tab. See Section 8—Maintenance and Testing, Chapter 2—“Alarms,” page 8-15 for detailed information about the Alarm tab.

Events Menu 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-31 for detailed information about the Events tab.

Figure 1-49 Alarm Menu



3. Acknowledge: Acknowledge the selected alarm.


1.2.3.4.

Figure 1-50 Events Menu






1.

2.

3.4.5.


Chapter 6 Managing TE-206 Nodes from TransNavServices Menu

Services Menu Use the commands on the Services menu to help you manage information on the Services tab. See the TransNav Provisioning Guide, Section 2—Creating ADM Services, Chapter 1—“Service Provisioning Concepts.” for detailed information on services.

Figure 1-51 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 TransNav Provisioning Guide, Section 2—Creating Service Applications, Chapter 2—“Bridging and Rolling Services” 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.

1.2.3.4.5.6.7.

8.9.

10.11.12.


TransNav GUI Guide, Section 1: Installation and OverviewService 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 5—“Service Groups” for detailed information about the Service Group tab.

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.

Figure 1-52 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.

1.

2.

3.4.5.

Figure 1-53 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”.

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”.

6. Reports: Generate and define reports. See Section 2—Administrative Tasks, Chapter 5—“Generating and Viewing Reports”.

7. Customer: Define customer information. See Section 2—Administrative Tasks, Chapter 5—“Generating and Viewing Reports,” Adding Customer Information.

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”.

1.2.

3.4.5.

6.7.

9.

11.12.

8.

10.

13.14.15.

16.17.18.19.

20.21.22.


Chapter 6 Managing TE-206 Nodes from TransNavAdmin Menu

9. Domain User: Define, change, or delete a domain user through pre-defined roles. See Section 2—Administrative Tasks, Chapter 1—“Managing Server Security”.

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”.

11. Current User: Display the current user name and change the password. See Section 2—Administrative Tasks, Chapter 1—“Managing Server Security”.

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”.

14. SW Upgrade: Perform a software upgrade. See Section 8—Maintenance and Testing, Chapter 6—“Software Upgrades”.


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). See Section 3—Network, Chapter 6—“OSI Parameters Configuration”.

18. OSI Parameters Configuration: Configure a node to be an OSI gateway node. See the TransNav Provisioning Guide, Section 1—Configuring the Network, Chapter 6—“Creating a Traverse OSI Gateway Node”.

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”.

20. Options: Turn the audible alarm on or off, set time zone and date format and set the number of services (Services per page) for display options.


22. Attached Devices SNMP Parameters: Set the SNMP sub-shelf devices polling and synchronization intervals for the management server.


Chapter 6 Managing TE-206 Nodes from TransNavGUI Conventions

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” for detailed information on creating and configuring equipment in the network.


GUI Conventions





Figure 1-54 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”.

4. Add TE-50: Add a TraverseEdge 50 to the management interface. To add a TraverseEdge 50 sub-shelf device, see the TransNav Management System GUI Guide, Section 5—Equipment, Chapter 6—“TraverseEdge 50 (TE-50)”.

1.2.3.4.

Figure 1-55 Help Menu

1. On Application: Display help on the user interface application.

2. About: Display the management system version number.1.2.


TransNav GUI Guide, Section 1: Installation and OverviewScroll Bars

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.


You can resize the Map View, Shelf View, and Tab screen area for both views.



SECTION 2 ADMINISTRATIVE TASKS

Contents

Chapter 1Managing Server Security

Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1Security Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1Password Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3Guidelines to Managing Server Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4Domain User Access Roles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5Domain Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6Functional Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7Session List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10

Chapter 2Managing Node Security

Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11Security Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11Node User Access Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12Node Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13

Chapter 3Using TransNav GUI with TN-Sight

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17Access Roles on TN-Sight . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17Provisioning TE-206 Nodes from TransNav . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19TE-206 Alarms and Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-20TE-206 Node Database Backup and Restore . . . . . . . . . . . . . . . . . . . . . . . . . 2-20Removing TE-206 Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-20

Chapter 4TransNav User Preferences

Select Background Image for Map View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22Saving and Importing User Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-23Customize System Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-24Grouping Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-26Changing Node Group Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-33

Chapter 5Generating and Viewing Reports

Generating Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-35Guidelines to Scheduling a Performance Monitoring (PM) Report:. . . . . 2-36Report Schedulers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-37Report List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-38

Using the Report Scheduler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-38


TransNav GUI Guide Section 2 Administrative Tasks

Adding Customer Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-42Viewing Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-43

Viewing Reports Online . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-43Viewing Generated Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-44

Example Report Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-45Removing Generated Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-46


SECTION 2SECTION 2ADMINISTRATIVE TASKS

Chapter 1 Managing Server Security

Introduction 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• Password Changes• Guidelines to Managing Server Security• Domain User Access Roles• Domain Users• Functional Groups• Session List

Definitions 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.

Security Management

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), the command line interface (CLI), or the transaction language 1 (TL1) interface. 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 or TL1. Users can be assigned to one or more nodes in the network.


TransNav GUI Guide, Section 2: Administrative TasksSecurity Management

The ability to create, delete, and modify user accounts is available only to users in the Administrator role.

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.


Chapter 1 Managing Server SecurityPassword 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. A valid password is 6 to 10 characters

in length. It must contain at least one letter, one number and one of the following special characters: ! @ # $It must not contain the User ID, any TL-1 syntax, spaces or any of the following special characters: & \ : , “ = ;

• 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.


TransNav GUI Guide, Section 2: Administrative TasksGuidelines 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.

• A secure HTTP setting can be enabled on the server during setup that is available only for clients attached to a server. Setup requires enabling an HTTPS server key on the server and enabling the client IP address on the server. Client users must enter the IP address of the server that has HTTPS enabled. For information on setting up the HTTPS server key, see Chapter 1—“Creating the Management Servers,” Configure HTTPS.


Chapter 1 Managing Server SecurityDomain User Access Roles

Domain User 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:

You can access the Functional Groups Configuration dialog box from either the Domain User (Groups button) or Functional Groups selections on the TransNav Admin menu.

Table 2-1 Roles and Access Rights for Server Security

TransNav RolesCorresponding

TN-Sight / TE-206 User Accounts

Allowable Operations

Administrator User Account 1 Provision and view everything in the system, including all user account data and security logs.

Equipment Configuration Manager

User Account 3 Provision and view all node, card, port, and control plane parameters.

Service Configuration Manager

User Account 4 Provision and view all services.

Report Manager User Account 2 Create, schedule, and view reports.

Fault Manager User Account 2 Provision alarm severities; view alarm and event logs.

(Viewer) User Account 5 Default. View everything; cannot perform any operations.


TransNav GUI Guide, Section 2: Administrative TasksDomain 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:

User Name: Enter the user name. User names are case sensitive. They must be alphanumeric and from 2 to 32 characters in length. User names can contain no hyphens (-), spaces, or special characters such as @ $ % * &

Password: Enter the password. Passwords must be 6 to 10 characters in length. They must contain at least one letter, one number and one of the following special characters: ! @ # $

Passwords must not contain the User ID, any Tl-1 syntax, spaces, or any of the following special characters : & \ : , “ = ;

Confirm: Re-enter the password.

Timeout (min): Enter the number of minutes after which an unused session will be closed for the specified domain user. The default value is 120 minutes. Valid values are: • 0. Disables the feature. The session will never time out. • 5 minutes, in 1 minute increments.


Chapter 1 Managing Server SecurityFunctional Groups

A warning message appears two minutes before the session times out. A Session Terminated dialog box displays when the session times out. User preferences are not saved when a session times out.

Last Login: Indicates the last time and location the user logged into the system through the server CLI, Node CLI, or the Node-level GUI on a Traverse node. If a user is not logged in, the value is blank. This feature is not available for TE-100 or TE-206 node users.

Note: This information will only appear if the node software version matches the server software version. This parameter remains blank for users on nodes using previous software versions.

Description: Enter detail information about the user. Maximum length is 100 characters. Default is blank. This feature is not available for TE-100 or TE-206 node users.

Contact: Enter contact information for the user. Maximum length is 100 characters. Default is blank. This feature is not available for TE-100 or TE-206 node users.

Login Blocked: Select this checkbox to block the user from logging into the server. This feature is not available for TE-100 or TE-206 node users.

Note: To block all TransNav users simultaneously, use the Global Block User feature. For information, see the TransNav Management System Server Guide, Chapter 3—“Server Administration Procedures,” Global User Block.

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.• 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.

• Close: Save the changes and close the dialog box.

Force10 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 (RBAC). 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

Important: For security reasons, Force10 recommends using the value “0” with extreme caution.


TransNav GUI Guide, Section 2: Administrative TasksFunctional Groups

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

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.


Chapter 1 Managing Server SecurityFunctional Groups

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.• Close: 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, Force10 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.

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.


TransNav GUI Guide, Section 2: Administrative TasksSession 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.


Terminate: A domain administrator can choose to terminate a selected domain user’s session.

Cancel: Close the dialog box.



Chapter 2 Managing Node Security

Introduction 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• Node User Access Roles• Node Users

Definitions 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.

Security Management

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), the command line interface (CLI), or the transaction language 1 (TL1) interface. 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 or TL1. 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.


TransNav GUI Guide, Section 2: Administrative TasksNode User Access Roles

You can control node user access using Node User Access Roles. The Traverse has several pre-defined access groups.

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.

Node User Access Roles

The TransNav management system has the following built-in access roles for Node users whose allowable operations are defined below:

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.

Table 2-2 Access Groups and Access Rights for Node Security

Access Role Names Allowable Operations

Administrator 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.

User Manager Provision and view all user account data and security logs except Administrator role.

Fault Manager Provision alarm severities; view alarm and event logs.

Report Manager Create, schedule, and view reports.

(Viewer) Default. Can view everything, but cannot make any changes.


Chapter 2 Managing Node SecurityNode Users

Node Users A Node User manages any single node in a domain using the node-level CLI, TL1 interface, or Node-level GUI. 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:

User Name: Enter the user name. User names are case sensitive. They must be alphanumeric and from 2 to 32 characters in length. User names can contain no hyphens (-), spaces, or special characters such as @ $ % * &

Password: Enter the password. Passwords must be 6 to 10 characters in length. They must contain at least one letter, one number and one of the following special characters: ! @ # $

Passwords must not contain the User ID, any Tl-1 syntax, spaces, or any of the following special characters : & \ : , “ = ;

Confirm: Re-enter the password.


TransNav GUI Guide, Section 2: Administrative TasksNode Users

Timeout (min): Indicates when the node user’s session will end (timeout) after no activity. Default is 120 minutes. 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. A Session Terminated dialog box displays when the session times out. User preferences are not saved when a session times out.

Last Login: Indicates the last time and location the user logged into the system through the node TL1, node CLI, or the node-level GUI on a Traverse node. If a user is not logged in, the value is blank. This feature is not available for TE-100 or TE-206 node users.

Note: This information will only appear if the node software version matches the server software version. This parameter remains blank for users on nodes using a software version that does not match the server software version.

Description: Enter detail information about the node user. Maximum length is 100 characters. Default is blank. This feature is not available for TE-100 or TE-206 node users.

Contact: Enter contact information for the node user. Maximum length is 100 characters. Default is blank. This feature is not available for TE-100 or TE-206 node users.

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

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.

Important: For security reasons, Force10 recommends using the value “0” with extreme caution.


Chapter 2 Managing Node SecurityNode Users

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 3—“General Description of EMS Server GUI,” Scroll Bars. • 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 selected node user.• Close: Save the changes and close the dialog box.


TransNav GUI Guide, Section 2: Administrative TasksNode Users


SECTION 2ADMINISTRATIVE TASKS

Chapter 3 Using TransNav GUI with TN-Sight

Introduction (SONET network only) This chapter describes using the TransNav management system graphical user interface (GUI) in conjunction with the TransNav Sight (TN-Sight) web craft GUI to discover and manage Traverse, TE-100, and TE-206 nodes from a single server.

TransNav can be used to manage TE-206 nodes as either standalone nodes or in a network ring.

The following topics are covered in this chapter:• Prerequisites, page 2-19• Access Roles on TN-Sight, page 2-20• Provisioning TE-206 Nodes from TransNav, page 2-21• TE-206 Alarms and Events, page 2-22• TE-206 Node Database Backup and Restore, page 2-22• Removing TE-206 Nodes, page 2-22

Prerequisites Initial set up of TE-206 nodes must be completed prior to being discovered by the network and displaying on the TransNav GUI. For more information, see the following:• TraverseEdge 206 Hardware Installation Guide. Contains information on setting up

the TE-206 hardware. • TraverseEdge 206 Users Guide. For information on using the TE-206. • Section 1—Installation and Overview, Chapter 3—“General Description of EMS

Server GUI,” Managing TE-206 Nodes from TransNav. For information on required port settings for Traverse, TE-206, and TE-100 nodes.

• Section 3—Network, Chapter 2—“Network Auto Discovery,” Network Auto Discovery. For information on discovering the TE-206 on TransNav.

When DCC links are added or removed from the network, they must be rediscovered by the network using a manual procedure. From the TransNav GUI, select Admin, then select Rediscover. The rediscovery process takes a few minutes to complete. During this time, the links will appear to be unchanged.


TransNav GUI Guide, Section 2: Administrative TasksAccess Roles on TN-Sight

Access Roles on TN-Sight

Five built-in user accounts exist for managing TE-206 nodes from TransNav using the TN-Sight web craft GUI. Each user account is similar to one of the access roles defined for TransNav, although some differences exist. These differences are described below. At any time, a maximum of five TN-Sight sessions (per built-in user account) can be launched per node from TransNav.

The TransNav management system has the following built-in roles whose allowable operations are defined below for Domain users:

Table 2-3 Roles and Access Rights for Server Security

TransNav RolesCorresponding

TN-Sight / TE-206 User Accounts

Allowable Operations

Administrator User Account 1 Provision and view everything in the system, including all user account data and security logs.


User Account 3 Provision and view all node, card, port, and control plane parameters.


User Account 4 Provision and view all services.

Report Manager User Account 2 Create, schedule, and view reports.

Fault Manager User Account 2 Provision alarm severities; view alarm and event logs.

(Viewer) User Account 5 Default. View everything; cannot perform any operations.


Chapter 3 Using TransNav GUI with TN-SightProvisioning TE-206 Nodes from TransNav

Provisioning TE-206 Nodes from TransNav

After a TE-206 node is discovered by TransNav, double-click the node icon on the TransNav GUI. The TN-Sight web GUI displays with a graphical representation of the TE-206 node cassettes. For information on required settings for Traverse, TE-206 and TE-100 nodes to

Figure 2-8 TN-Sight Web Craft GUI

Click the Administration tab to provision the TE-206 node. For provisioning instructions, see the TraverseEdge 206 Users Guide.

Note: Preprovisioning of the TE-206 nodes from TransNav is not supported.

Note: End-to-end provisioning across TE-206 nodes is not supported in this release. For end-to-end provisioning, TE-206 nodes should be provisioned for each node hop-by-hop.


TransNav GUI Guide, Section 2: Administrative TasksTE-206 Alarms and Events

TE-206 Alarms and Events

Full alarm and event support, including acknowledging, filtering, and viewing alarms, is provided by TransNav for TE-206 nodes. Alarms and events are automatically re-synchronized when TE-206 nodes are discovered or rediscovered by TransNav.

Alarm profiles are currently not supported for TE-206 nodes. Changing the severity or a service affecting flag for an alarm for a TE-206 node must be done through the TN-Sight web GUI on per node basis. For more information, refer to the TraverseEdge 206 Users Guide.

For a full list of the TE-206 node alarms and events, including corresponding TransNav alarms, see the Operations and Maintenance Guide, Section 1—Fault Management, Chapter 1—“Managing Alarms and Events.”

TE-206 Node Database Backup and Restore

The TransNav management system can be configured to retain copies of each TE-206 node for backup purposes. Backup copies can be scheduled to run automatically at a specified time each week, or can be performed manually. For more information, see the Operations and Maintenance Guide, Section 6—Routine Maintenance, Chapter 2—“Node Database Backup and Restore.”

Removing TE-206 Nodes

TE-206 nodes can be removed from the TransNav network. If the node includes DCC, the DCC must be manually disabled prior to removing the node from TransNav. The node must also be removed from the Discovery list. To remove the node from the Discovery list, from the TransNav GUI menu select Admin, and then Discovery. The Discovery Sources View dialog box displays. Select the IP address of the node to be deleted and click Delete. Click Close to close the dialog box.

Figure 2-9 Deleting a TE-206 Node from TransNav

To complete the removal of the TE-206 node from the TransNav GUI, right-click the node and select Delete from the menu that displays.




Chapter 4 TransNav User Preferences

Introduction This chapter describes the following TransNav server GUI features:• Select Background Image for Map View• Saving and Importing User Preferences• Customize System Options• Grouping Nodes• Changing Node Group Names

TransNav GUI Guide, Section 2: Administrative TasksSelect Background Image for Map View


Select Background Image for Map View

Use this procedure to import a saved image file for the background image of the network or for any group in Map View on the TransNav server GUI. 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-4 Select Background Image for Map View

Step Procedure

1 In Map View on the TransNav GUI, right-click the background map and select Change Background.

2 The Load Background Image dialog box displays.

Figure 2-10 Load Background Image Dialog Box

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-25.

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.

Chapter 4 TransNav User PreferencesSaving and Importing User Preferences


Saving and Importing User Preferences

You can save and import the following user preferences on the TransNav GUI:• 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-11 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.

When you logout of the GUI, a prompt appears asking if you would like to save user preferences.

Note: If the GUI session times out from lack of use, the user preferences are not saved.

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.

TransNav GUI Guide, Section 2: Administrative TasksCustomize System Options


Customize System Options

Customize options such as the sound or date and time in the TransNav user interface for both the node (craft) GUI and the EMS GUI. From the Admin menu, select Options to display the Options dialog box.

Figure 2-12 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.

Service List: Set the number of services (services per page) to display each time you use the Service search feature. Valid values are: 100, 200 (default), 500, and 1000.

Chapter 4 TransNav User PreferencesCustomize System Options


VT Capability: Select this option to show VT/VC switching capability on the map. Each VT capable node will include a box with the letters “L” and “O” indicating low-order capability as shown.

Note: Depending on the size of your network and number of current users, a slight delay may occur when using this feature.


Close: Close the dialog box and return to the main menu.

TransNav GUI Guide, Section 2: Administrative TasksGrouping Nodes


Grouping Nodes

In a network containing multiple nodes, use the grouping feature on the TransNav GUI to collapse nodes into groups to make the network easier to manage. Groups are user-defined, allowing each user to group nodes and groups 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, Force10 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 at the level where they are added. Nodes and groups can be added to existing 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.

Table 2-5 Grouping Nodes

Step Procedure

1 In Map View on the TransNav GUI, right-click the background image and select Add Group from the menu.

Figure 2-13 Add Group - Network Level

2 A Group icon appears in the upper left corner of the Map View.

Figure 2-14 Group Icon

Group icon

Chapter 4 TransNav User PreferencesGrouping Nodes


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-15 Group Configuration

The Group Configuration screen displays. Change the name in the Group Name field. Click Apply.

4 Create a new node from Map View using one of the following steps:• Right-click any background map and select Add node.• 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.”

Repeat Step a for each node 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.

Table 2-5 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 available nodes displays. Select the node name to add to the group.

Figure 2-16 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.

6 To add a node or a group to another group, use either of the following steps:

Figure 2-17 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.


Step Procedure

Group icon



b. From the navigation tree, select the group to which you want to add a node or group and 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, select the first node, hold down the Shift key, then select 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.

7 The navigation tree displays the groups and nodes. Each group can be collapsed or expanded.

Figure 2-18 Navigation Tree and Group Icon


Step Procedure



8 Expand a group to display the nodes and groups it contains,

Figure 2-19 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.


Step Procedure



9 To remove a node or group from a group, use one of the following methods:

Figure 2-20 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 be removed, then click Remove. Repeat removing nodes or groups until all of the desired 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.


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.


Step Procedure

Chapter 4 TransNav User PreferencesChanging Node Group Names


Changing Node Group Names

In the TransNav GUI, it may be necessary to change the name of a node group if the group is moved or if user preferences are copied to a new user’s profile. Use the following procedure to change the node group name from Map View.

Table 2-6 Changing Node Group Names

Step Procedure

1 In Map View on the TransNav GUI, change the group name using one of the following methods:a. Select the group name in the navigation tree. b. Click the group icon.

2 Click the Config tab. The Group Configuration screen displays.

Figure 2-21 Group Configuration Screen

3 Change the name in the Group Name field. Click Apply.

4 The Changing Node Group Names procedure is complete.

1a

1b

TransNav GUI Guide, Section 2: Administrative TasksChanging Node Group Names


SECTION 2ADMINISTRATIVE TASKS

Chapter 5 Generating and Viewing Reports

Introduction This chapter includes the following topics that describe the steps to generate reports, create report templates, then view and remove reports using the Admin menu on the TransNav management system server GUI.

Note: These functions are not available from the Node-level GUI.

• Generating Reports• Using the Report Scheduler• Adding Customer Information • Viewing Reports• Example Report Output• Removing Generated Reports

Generating Reports

Generate a set of data in a particular format at specified intervals. The following report types 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 configuration statistics for all of the servers, Force10 recommends performing regular backups of the configuration files on each server. (Alarm and event data is not backed up.) 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 on the network that is accessible to all interested parties.

Note: In the event a backup fails, the system generates a log file; no alarms are generated.


TransNav GUI Guide, Section 2: Administrative TasksGenerating Reports

To monitor performance on any resource, know how to use the performance monitoring templates. See Section 8—Maintenance and Testing, Chapter 1—“Performance Monitoring”. To create or modify a monitoring template, see the Operations and Maintenance Guide, Section 2—Performance Monitoring, Chapter 1—“Managing Performance,” Creating or Modifying a Monitoring Template.

Guidelines to Scheduling a Performance Monitoring (PM) Report:

• Enable PM collection on the PM template (select Collect for specific parameters or Collect All) and set the template to an interface such as a service, card, or port.

• PM reports only show data from the time the PM collection is enabled. • PM reports do not show current buckets and only collect data on unlocked objects. • Two reports for the same report scheduler cannot be generated in the same minute.

Conflicts will occur in the automatic naming convention which includes the date, hour, and minute.

Generating reports is a two step setup process. First, the report parameters on the EMS server must be set to change the host server where the data is being reported, the directory where the reports are stored, and length of time data is stored. For more information, see the TransNav Management System Server Guide, Section 2—Management Server Procedures, Chapter 3—“Server Administration Procedures,” Setting Up Report Parameters. The second step is to set up the PM template for the report.

To set up the PM template for the report, first create a Report Scheduler to specify:• Generation Period: Indicates the report generation frequency (none, once, hourly,

daily, weekly, or monthly) and the next generation time.• Report Script: A SQL script which is run against the database in order to extract

the requested information. A script is one or more SQL statements and is stored in the Scripts directory.

• Report Source Filter: A filter which identifies the source of the information on the report. A general source filter identifies just the node; a detailed source identifies the node, slot, and port. (optional)

• Report Period: The number of hours the report covers. This is used with the following scripts: alert.sql, event.sql, resource_availability.sql, service_availability.sql, and all of the performance.sql scripts. Do not enter a value in this parameter if the report period is for 24 hours. This value is set in Report Parameter 1.

• Report Parameter 1: Specifies the period for all of the performance.sql reports. Enter 0 to specify 15 minutes; enter 1 to specify 24 hours.


Chapter 5 Generating and Viewing ReportsGenerating Reports

From Map View, select Admin, then Reports to display the Reports dialog box.

Figure 2-22 Reports Dialog Box

The Reports dialog box has two main sections: • Report Schedulers• Report List

Report Schedulers

Lists all the reports that are 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 for this section 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.


TransNav GUI Guide, Section 2: Administrative TasksUsing the Report Scheduler

• 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.

Report List

Lists all the reports that have been generated.

Command buttons for this section are as follows:• List All: List all generated reports.• View Report: View the report selected in the Report List box. An example event

report is shown in the topic, Example Report Output.

Note: If the file size of the report is over 500K, a error message appears. The file must be opened with a basic document editor such as NotePad or WordPad. Report output files are stored on the TransNav server in the /report/output directory. The report displays in the following format: <Report name>_mm.dd.yyyy_hh.mm• 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 pane, click Add. The Report Scheduler dialog box displays.

Figure 2-23 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.


Chapter 5 Generating and Viewing ReportsUsing the Report Scheduler

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.

Report Script: Select 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.

Note: Equipment monitoring events (_eq_performance.sql) 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. Equipment reports can only be run for Traverse nodes.

• alert.sql: Historical alarm report. Displays a record of alarm information, including alarm duration and clearing time.

• ds1_facility_performance1.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.

• eop_performance.sql: EOP (Ethernet over PDH) port performance monitoring report. Generates performance monitoring report for an EOP port.

• eos_performance.sql: EOS (Ethernet over SONET/SDH) port performance monitoring report. Generates performance monitoring report for an EOS port.

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”.


TransNav GUI Guide, Section 2: Administrative TasksUsing the Report Scheduler

• ethernet_10ge_eq_performance.sql: Equipment monitoring performance report for 1-port 10GbE and 10-port GbE.

• ethernet_eopdh_eq_performance.sql: Equipment monitoring performance report for EoPDH cards.

• 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.

• 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.

• sdh_facility_performance.sql: SDH port performance monitoring report.• sdh_highorderpath_performance.sql: SDH high order services performance

monitoring report. • sdh_loworderpath_performance.sql: SDH low order services 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.• 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_advanced.sql: Domain service report. Displays a snapshot of all the

services currently provisioned in the domain, including the current state for each service.

• service_availability.sql: Service availability report. Displays the amount and percentage of time that the service spent in the Enabled vs. Disabled state.

• 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.


Chapter 5 Generating and Viewing ReportsUsing the Report Scheduler

• sonet_vt_capacity_performance.sql: VT capacity performance report for SONET services. Generates a capacity monitoring report.

• te206_performance.sql: TE-206 performance monitoring report. Generates a performance monitoring report for all TE-206 nodes managed by TransNav.

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”.

Report Source Filter: Allows you to select the source of the information on the report. Valid selections are General Source Filter and Detailed Source Filter. • General Source Filter: Select to run the report run for a specific node in the

domain. The filter is a substring of the Source field parameter and works only if the correct filter is set. – Report Source Filter: Enter the node name of the node to run the report.

• Detailed Source Filter: Select to run a progressively specific report detailing a node name and slot or node name, slot, and port. – Node: Enter the user-defined name of the node.– Slot: Enter the slot number of the card in the shelf (e.g., s-12 for slot 12).– Port: Enter the specific port number on the card in the node. Report Period(hr): Indicates the time over which the report is generated, e.g., enter 4 to specify the report covers the last 4 hours. This parameter is used for the following reports: – alert.sql– event.sql– performance.sql (all performance.sql reports)– resource_availability.sql– service_availability.sql

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)

In another example for services, use the following syntax:

NodeId/slotNumber/<service member>/vlan-id

where:

NodeId is the user-defined name of the nodeslotNumber is the slot number of the card in the shelf (e.g., s-12 for slot 12)<service member> is the name of the service member<vlan-id> is the vlan ID of the service

To create the report, click OK. The scheduled report appears in the Report Schedulers pane. Once generated, the report displays in the Report List pane in the following format: <Report name>_mm.dd.yyyy_hh.mm


TransNav GUI Guide, Section 2: Administrative TasksAdding 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-24 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


Chapter 5 Generating and Viewing ReportsViewing Reports

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.

Viewing Reports

Reports can be viewed in either of two ways: online (Traverse nodes and TE-100 nodes only) or in a saved report that you can print. PM reports only show data from the time the PM collection is enabled and only collect data on unlocked objects.

Note: With Release TN4.2.1, reports for TE-206 nodes must be generated manually from the TransNav management system. The reports cannot be scheduled and output cannot be viewed online.

Viewing Reports Online

To view a card or port report online, from Shelf View select the card or port. Select the Performance tab. The Card or Port Performance Monitoring screen displays. Set the Interval (either 15 min or 24 hr), number of Samples to view, and then click Reset. The system begins collecting data for the current interval period. Click Refresh to view the data for the selected interval period.

The default number of Samples is four, however, five columns appear. At the point where Reset was selected, the values in the column appear as gray zeros with an asterisk at the right (0 *) which means the PM data for that interval was reset and the values currently shown are invalid. The zeros in the current column that data is being collected appear in green; the values in the columns with reported data appear in black.

Figure 2-25 Viewing Port Performance Monitoring Data Online

To view an EOS or EOP report online, from Shelf View select the Ethernet tab, then select the EOS or EOP subtab. Select the row of the EOS or EOP member that you want to view performance, and click the Performance button. The EOS or EOP Performance Monitoring screen displays. Set the Interval (either 15 min or 24 hr) period, number of Samples to view, and then click Reset. The system begins collecting data for the current interval period. Click Refresh to view the data for the selected interval period.


TransNav GUI Guide, Section 2: Administrative TasksViewing Reports

Viewing Generated Reports

Reports can be generated for printing either manually (required for TE-206 nodes) or scheduled to generate automatically. The output file is stored in the directory selected on the system server in the Execution Configuration dialog box. Reports are generated as .00 files. The file extension must be changed to .csv before the file can be opened as a Microsoft Excel spreadsheet and saved.

For more information to automatically generate a report, see Using the Report Scheduler.

To view a generated report, open Windows Explorer and access the directory where the TransNav server software is located. This should appear as EMS.xxx.abc where xxx.abc indicates the software release number.

Locate the /report/output directory. The generated report files are located in this directory.

The output files of all reports are retained in this folder until the value set in the ReportRemovalPeriod (days) parameter on the Execution Configuration dialog box is reached. After that value is reached, the system automatically deletes the files. For more information, see the TransNav Management System Server Guide, Section 2—Management Server Procedures, Chapter 3—“Server Administration Procedures,” Setting Up Report Parameters.

Figure 2-26 Report Output Location on EMS Server


Chapter 5 Generating and Viewing ReportsExample Report Output

Example Report Output

An example of an online event report is shown below.

Figure 2-27 Example Online 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.


TransNav GUI Guide, Section 2: Administrative TasksRemoving Generated Reports

An example of a generated report file that has been saved to an Excel spreadsheet is shown below.

Figure 2-28 Example of Report Opened in an Excel Spreadsheet

Removing Generated Reports

To manually remove generated reports, open Windows Explorer and access the directory where the TransNav server software is located. This should appear as EMS.xxx.abc where xxx.abc indicates the software release number.

Locate the /report/output directory. The generated report files are located in this directory. Remove the desired generated report files.

If the output file directory is on the TransNav server, the system automatically deletes all files after the value set in the ReportRemovalPeriod (days) parameter is reached. For more information, see the TransNav Management System Server Guide, Section 2—Management Server Procedures, Chapter 3—“Server Administration Procedures,” Setting Up Report Parameters.


SECTION 3 NETWORK

Contents

Chapter 1Creating and Deleting Equipment

Auto-discovery and Pre-provisioning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1Create a Node. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2Node Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3Configure the Traverse SNMP Agent Parameters . . . . . . . . . . . . . . . . . . . . . 3-7Delete a Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10Card Placement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10Creating, Replacing, or Deleting a Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11Add a Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11Delete a Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12Replace a Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13Creating or Deleting Links. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14Add a Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14View Available Resources on a Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-17Delete a Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18

Chapter 2Network Auto Discovery

Network Auto Discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-19Discovering TE-206 Nodes from TransNav. . . . . . . . . . . . . . . . . . . . . . . 3-21

Static Route Information List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-21

Chapter 3Node Timing

Pinouts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-23Provisioning Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-23

Global Timing Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-24External Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-26Line Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-29Line Facility Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-30Reference List Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-31Derived Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-32Protection Switching External Timing References . . . . . . . . . . . . . . . . . . . . . 3-33Protection Switching Line Timing References. . . . . . . . . . . . . . . . . . . . . . . . . 3-34

Chapter 4DCC Tunnels

DCC Tunnel Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-35


TransNav GUI Guide Section 3 Network

Chapter 5Configuring IP Quality of Service

Global Parameters Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-38Static Classifier Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-39Dynamic Classifier Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-41ACL (Access Control) Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-42Statistics Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-43

Chapter 6OSI Parameters Configuration

NET Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-46TTD Port Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-47TTD ACL Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-48TTD Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-49Man Area Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-50



SECTION 3 NETWORK

Chapter 1 Creating and Deleting Equipment

Introduction Equipment in a network includes nodes, links, cards (modules), ports and external devices. This chapter describes how to create and delete equipment, including the preprovisioning process. • Auto-discovery and Pre-provisioning• Create a Node• Node Parameters

– Configure the Traverse SNMP Agent Parameters• Delete a Node• Creating, Replacing, or Deleting a Card• Creating or Deleting Links• View Available Resources on a Link

Auto-discov-ery and Pre-provision-ing

Equipment configuration can be performed with or without the use of preprovisioning. 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. For information on configuring auto-discovery of nodes, see Chapter 2—“Network Auto Discovery”.

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

TransNav GUI Guide, Section 3: NetworkCreate a Node


preprovisioned, it is assigned default parameters. To change parameters from the default values, see Section 2—Configuring TDM Equipment.

Create 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 the server domain. Nodes can later be grouped to make the network easier to manage. For more information, see Section 2—Administrative Tasks, Chapter 4—“TransNav User Preferences,” Grouping Nodes.

Note: Force10 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, spaces, or special characters in this field. Node names are case sensitive. Verify the node name is identical to the node-id CLI parameter configured during node commissioning.

Important: Node names must begin with a letter. They cannot begin with a number.

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.

Chapter 1 Creating and Deleting EquipmentNode Parameters


MSAid Format: If this node is part of a DCS application, choose the MSAID format (preprovisioning only).• No-MSAid• MSAid-VT-Seq• 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 node ID, 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, —, Chapter 7—“Node Start-up and Initial

Configuration”.

To change the node attributes (other than the IP information), click the node in Map View and then 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: 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

TransNav GUI Guide, Section 3: NetworkNode Parameters


punctuation, spaces, or special characters in this field. Additionally, the Node ID is case sensitive. This parameter is required to commission the node and is set using the CLI.

Note: Node names must begin with a letter.

Node IP: 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 and is set using the CLI.

This address is also known as the Router ID in a data network environment.

Force10 recommends using 10.100.100.x where x is between 1 and 254. Use a unique number for each network node.

Force10 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 the TransNav Provisioning Guide, Section 7—DCS Applications.

BP DCN IP: 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). This is set through the CLI during network commissioning.

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.

Force10 recommends using a different subnet for each site.

Chapter 1 Creating and Deleting EquipmentNode Parameters


BP DCN Mask: Displays the mask IP address for the node BP DCN IP. The value depends on site practices. This is set through the CLI during network commissioning.

BP DCN Gateway: If the node is connected directly to a management server, this field is the address is the IP gateway of the management server. This is set through the CLI during network commissioning.

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: 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. This is set through the CLI during network commissioning.

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: Displays the mask IP address for the TransNav management server to which this node is connected. This is set through the CLI during network commissioning.

EMS Gateway: 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. This is set through the CLI during network commissioning.

The above parameter is required for each EMS IP; the value depends on site practices.

Remote ACO: Click this button to acknowledge an external alarm on the selected node.

TransNav GUI Guide, Section 3: NetworkNode Parameters


NTP (Network Time Protocol) IP 1 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.

NTP (Network Time Protocol) IP 2: 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.

Note: For instructions on setting the Primary 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.

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:

Chapter 1 Creating and Deleting EquipmentConfigure the Traverse SNMP Agent Parameters


• America/LosAngeles• America/Phoenix• America/Denver• America/Chicago• America/New-York

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.

Auto in service time (min): Set the amount of time, in minutes, to allow service affecting alarms to be reported. If no port-level or service-level service affecting alarms are reported within the set time, the port or service set up with automatic in service will be unlocked allowing alarms to be reported. Valid values are 0 to 99 hours in one-minute increments. The default value is 30 minutes.

Command buttons are as follows:• Security Warning: Enter a security warning message specific for this Traverse

node. for more information, see the TransNav Management System Server Guide, Section 2—Management Server Procedures, Chapter 3—“Server Administration Procedures,” Setting a Security Warning.

• 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

Force10 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.

TransNav GUI Guide, Section 3: NetworkConfigure the Traverse SNMP Agent Parameters


From Map View, select a node. From the Admin menu, click SNMP Configuration.

Figure 3-3 Admin Menu—SNMP Configuration

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: Displays the user-defined node name entered during node commissioning using the CLI.

Node IP: Displays the node IP address entered during node commissioning using the CLI.

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.

Chapter 1 Creating and Deleting EquipmentConfigure the Traverse SNMP Agent Parameters


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.


Apply: Click Apply to save changes and return to the main screen.

Done: Click Done to cancel changes and return to the main screen.

TransNav GUI Guide, Section 3: NetworkDelete a Node


Delete a Node 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 appears with the message “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.

Note: To verify the IP address of a node is deleted, from the server GUI select Admin, then Discovery. The Discovery Sources View dialog box displays. If the IP address of the deleted node is appears in the list, select the IP address to highlight it and click Delete. A confirmation dialog box appears with the message “Are you sure you would like to delete [node IP address]?” Click Yes to proceed with the delete command or No to cancel the request, then click Done.

If node deletion fails from the TransNav GUI, execute the delete node command from the server CLI to ensure that any residual node information is successfully deleted.

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.

Card Placement

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” before you add a card to, or replace a card in, a shelf.

Chapter 1 Creating and Deleting EquipmentAdd a Card


Creating, Replacing, or Deleting a Card

Use the following information to add, delete, or replace a card. • Add a Card• Delete a Card• Replace a Card

Add a Card From Shelf View, right-click the slot into which you want to add a card (module).

Figure 3-5 Shelf View—Add Card

Select a card name. The card, with its associated ports, displays in the selected slot.

TransNav GUI Guide, Section 3: NetworkDelete a Card


Delete a Card 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.

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.

Chapter 1 Creating and Deleting EquipmentReplace 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].

Note: Before removing a protection card in a Carrier Ethernet Protection Pair that is used in conjunction with link integrity, certain requirements must be met. For more information, see Section 7—Configuring Ethernet, Chapter 1—“Configuring Ethernet Overview,” Link Integrity Feature.

See Figure 3-6 Delete or Replace a Card.

TransNav GUI Guide, Section 3: NetworkCreating or Deleting Links


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.

Creating or Deleting Links

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 in this document.

Add a Link 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.

Chapter 1 Creating and Deleting EquipmentAdd a Link


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.

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 5—“Generating and Viewing Reports,” Adding Customer Information.

Click Add.

TransNav GUI Guide, Section 3: NetworkAdd a Link


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:

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

Operational State: Displays whether the link physically exists.• Enabled. Active physical fiber• Disabled. Preprovisioned link


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.

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.

Off page connector

Chapter 1 Creating and Deleting EquipmentView Available Resources on a Link


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)

TransNav GUI Guide, Section 3: NetworkDelete 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.

SECTION 3NETWORK

Chapter 2 Network Auto Discovery

Introduction This chapter describes the following administrative functions selected through the Admin menu on the TransNav management system graphical user interface (GUI):• Network Auto Discovery: Define the gateway node(s) in a domain and easily

identify nodes that have been automatically discovered in the network. • Static Route Information List: Add static routes to a node for management IP

traffic.

Network Auto Discovery

The TransNav management system discovers new nodes in the network, allowing each node in the network to identify the nodes to which it is physically connected. This node-to-node communication allows the entire Traverse network topology to be identified by the TransNav management system. Gateway nodes are manually defined on the Discovery List of the Discovery Sources View dialog box. Nodes that are automatically discovered are also listed on the Discovery List. Operators can select to put nodes listed on the Discovery List in Maintenance Mode to allow the management system to automatically poll the node and keep it synchronized with the server. Nodes can be removed from Maintenance Mode for scheduled maintenance or upgrade to prevent unnecessary alarms being sent to the server.

Note: Automatic polling of discovered nodes may slow system response on systems with a large number of nodes.


TransNav GUI Guide, Section 3: NetworkNetwork Auto Discovery

Logon to the TransNav GUI. From the Admin menu, select Discovery 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 Node IP Address box. This can be either the backplane IP address or the actual node IP address.

When an IP address is entered, no system check is performed to ensure it is a valid node IP address. If the IP address is invalid, for example if it is a server IP address, a COM alarm is generated.

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.”

Nodes that are automatically discovered by the system also display in the Discovery Sources View dialog box. The checkbox in the Auto discovered column is automatically selected by the system when the node is discovered. If Proxy ARP is enabled, the system also automatically discovers TE-100 and TE-206 nodes in the network.

To allow the management system to automatically monitor a node and keep it synchronized with the server, select the Maintenance mode checkbox for that node. Click Apply to apply the change. When maintenance is scheduled for the node, clear the checkbox and click Apply to prevent unnecessary alarms on the server.

Note: When DCC links are added or removed from the network, they must be rediscovered by the network. The rediscovery process will take a few minutes to complete. During this time, the links will appear to be unchanged. For TE-206 nodes, this must be done manually. From the TransNav GUI, select Admin, then select Rediscover.


Chapter 2 Network Auto DiscoveryStatic Route Information List

Discovering TE-206 Nodes from TransNav

For TE-206 nodes, only link information for adjacent TE-206 nodes is required to detect and provide TE-206 connectivity information to TransNav. A point-to-point protocol is used to discover links between Traverse nodes and TE-206 nodes. This protocol is enabled by default on OC-48 ports on Traverse nodes to allow link information to be exchanged between Traverse and TE-206 nodes. The point-to-point protocol is not supported on TE-206 nodes for OC-3 or OC-12 ports.

Note: The Admin menu includes a Rediscovery option. Use this option when a TE-206 node or link is added or removed to manually notify TransNav to discover the changes.

Command buttons are as follows:• Add: Add the node-ip in the Node IP Address field to the Discovery List.• Clear: Clear the entry in the Node IP Address field.• Delete: Delete the Node IP Address selected in the Discovery List.• Apply: Apply the changes made in the Maintenance mode column.• Done: Close the Discovery Sources View dialog box.

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.


TransNav GUI Guide, Section 3: NetworkStatic Route Information List

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.• Close: Close the Static Route Information List dialog box.


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 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-26• External Timing, page 3-28• Line Timing, page 3-31• Derived Timing, page 3-34• Protection Switching External Timing References, page 3-35• Protection Switching Line Timing References, page 3-36

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:• TransNav Provisioning Guide, Section 1—Configuring the Network,

Chapter 3—“Configuring Network Timing”.• TraverseEdge 100 User Guide, Chapter 26—“Configuring Network Timing”.


TransNav GUI Guide, Section 3: NetworkGlobal 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.

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). Valid values are:• 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-35.)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: Select the timing mode to be used for this node. • 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-28.

• Line Time: Receive timing signal from an OC line interfaces. To configure line timing, see Line Timing, page 3-31.

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.

Timing tab

Subtabs

Global options


Chapter 3 Node TimingGlobal Timing Options

• Sync-Trace Unknown: Synchronization traceability unknown. The BITS clock connected to the Traverse network may not have SSM enabled or Ignore SSMR may have been selected on the Traverse.

• Stratum 2 • Stratum 2• Transit Node: Indicates the lock providing timing to the node is of a Transit Clock

Node level (primarily used outside North America). • Stratum 3E• Stratum 3• SONET Min Clock• Stratum 4E• Stratum 4• Don’t Use for Sync (default DUS): Do not use for synchronization.

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 disables 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: The node will use provisioned priorities to select the best timing reference.• Clear (default): The node will use the SSM level to prioritize timing references.

Force10 recommends using this setting to allow SSM to function on the node to prevent timing loops.

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.


TransNav GUI Guide, Section 3: NetworkExternal Timing

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-28. • If Timing Mode is Line, see Line Timing, page 3-31.

Ext. Command: Displays any commands performed on timing source (Cleared, Lockout, Forced, or Manual). See Protection Switching External Timing References, page 3-35.

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.

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:

1. Click the Timing tab

2. Click the EXT subtab


Chapter 3 Node TimingExternal Timing

– PRC: Primary reference clock– Synch-Trace Unknown– Stratum 2– Transit Node– Stratum 3E– Stratum 3– SONET Minimum Clock (default). 2 ppm clock– Stratum 4e– Stratum 4– Don’t use for sync (DUS)

• 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. – Don’t use for sync (DUS).

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


TransNav GUI Guide, Section 3: NetworkExternal Timing

– Short Haul Tr62411 220ft– Short Haul Tr62411 330ft– Short Haul Tr62411 440ft– 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. • 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.


Chapter 3 Node TimingLine 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.

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-32 explains the information in the Line Facility area.• Reference List Options, page 3-33 explains the information in the Reference List

area.

Line Time Mode

Line Facility Data

Reference List Options

Check mark indicates active reference


TransNav GUI Guide, Section 3: NetworkLine 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.


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. • 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. • Synch-Trace Unknown• Stratum 2• Transit Node• Stratum 3E


Chapter 3 Node TimingReference List Options

• 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-36.

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.


TransNav GUI Guide, Section 3: NetworkDerived 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.

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-32 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-36.

Select External Out Enabled


Chapter 3 Node TimingProtection 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.


TransNav GUI Guide, Section 3: NetworkProtection 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.


SECTION 3NETWORK

Chapter 4 DCC Tunnels

Introduction The data communications channel (DCC) carries operations, administration, maintenance, and provisioning information between nodes in a network. You can use the section DCC of any SONET 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 TransNav Provisioning Guide, Section 1—Configuring the Network, Chapter 4—“Creating DCC Tunnels” for the procedures and guidelines to tunnel third-party DCC bytes.

DCC Tunnel Tab

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.


TransNav GUI Guide, Section 3: NetworkDCC 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.


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.


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.

This chapter contains the following topics:• Global Parameters Tab• Static Classifier Tab• Dynamic Classifier Tab• ACL (Access Control) Tab• Statistics Tab

See the TransNav Management System Product Overview Guide, Section 2—Management System Planning, Chapter 3—“IP Address Planning,” for information and procedures on provisioning IP Quality of Service.

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). Force10 strongly recommends that this IP address not be blocked. For more information on internet multicast addresses, see http://www.iana.org/assignments/multicast-addresses.


http://www.iana.org/assignments/multicast-addresses



TransNav GUI Guide, Section 3: NetworkGlobal 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 to 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.


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.


Chapter 5 Configuring IP Quality of ServiceStatic Classifier Tab

Static Classifier Tab

Use the Static Classifier tab to add and maintain individual IP addresses and corresponding subnet (wildcard) 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 the following parameters:

IP Address: The static IP address of the third-party equipment.

Subnet Mask: Indicates the corresponding Subnet Mask for the IP address.

Service Level: Indicates the service level of the IP address. The valid values are: • HiPriority• BestEffort (default)

Command buttons for the Static Classifier tab are as follows:

Add: Click Add to display the Add Static Classifier dialog box.

Delete: Select an IP Address and click Delete to remove the IP Address from the list.

Close: Click to save the changes and close the dialog box.


TransNav GUI Guide, Section 3: NetworkStatic Classifier Tab

To configure the parameters, click Add. The Add ACL dialog box displays.

Figure 3-24 Add Static Classifier Dialog Box

Command buttons for the Add Static Classifier dialog box are as follows:

Add: Enter the IP address, wildcard mask or service level priority to be added or changed. Click Add to add the entry to the Static Classifier tab screen.

Cancel: Click to cancel the changes and return to the Static Classifier tab.


Chapter 5 Configuring IP Quality of ServiceDynamic 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-25 IP QOS Configuration Panel—Dynamic Classifier Tab


Refresh: Refreshes the list of existing dynamic IP addresses.

Done: Close the dialog box and return to the main screen.


TransNav GUI Guide, Section 3: NetworkACL (Access Control) Tab

ACL (Access Control) 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.

In the IP QOS configuration panel dialog box, click the ACL tab.

Figure 3-26 IP QOS Configuration Panel—ACL Tab

The user can view and configure the following parameters:

IP Address: The IP Address on the access control list.

Wildcard Mask: Indicates the wildcard (ACL) mask for the IP address.

Control: Indicates the control permission for the IP Address. Valid values are:• Deny• Permit

Important: When enabling the IP QOS feature, Force10 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.


Chapter 5 Configuring IP Quality of ServiceStatistics Tab

Command buttons for the ACL tab are as follows:

Add: Click Add to display the Add ACL dialog box.

Delete: Remove the selected IP address from the list of address on the ACL tab.

To configure the parameters, click Add. The Add ACL dialog box displays.

Figure 3-27 Add ACL Dialog Box

Enter a new IP address, corresponding wildcard mask, and control permission to the access control list.

Command buttons for the Add ACL dialog box are as follows:

Add: Click Add to display the Add ACL dialog box. Enter a new IP address, corresponding wildcard mask, and control permission to the access control list.

Cancel: Cancel any changes and return to the ACL 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.


TransNav GUI Guide, Section 3: NetworkStatistics Tab

In the IP QOS configuration panel dialog box, click the Statistics tab.

Figure 3-28 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.


Reset: Reset the current statistics to zero.

Refresh: Refresh the current information.



SECTION 3NETWORK

Chapter 6 OSI Parameters Configuration

Introduction This chapter contains the following topics:• NET Tab, page 3-48• TTD Port Tab, page 3-49• TTD ACL Tab, page 3-50• TTD Tab, page 3-51• Man Area Tab, page 3-52

See the TransNav Provisioning Guide, Section 1—Configuring the Network, Chapter 6—“Creating a Traverse OSI Gateway Node” for information and procedures on provisioning the OSI DCC Gateway application.


TransNav GUI Guide, Section 3: NetworkNET Tab

NET Tab Click a node. From the Admin menu, click OSI Parameters Configuration. The OSI Parameters Configuration Panel dialog box appears.

Figure 3-29 OSI Parameters Configuration Panel—NET Tab

The NET tab allows the user to enter the following parameters:

Network Entity Title (NET) of the OSI network. Enter the NET address per the format specified in GR-253-CORE.

Node Type: Define the role of the node. Select one of the following values:• IS: Intermediate system• ES: End system


Apply: Click Apply to save the changes.

Cancel: Clear the NET field and replace the default value.


Chapter 6 OSI Parameters ConfigurationTTD Port Tab

TTD Port Tab On the OSI Parameters Configuration Panel dialog box, click the TTD Port tab.

Figure 3-30 OSI Parameters Configuration Panel—TTD Port Tab

This tab allows the user to view and configure the following parameters:

LV port number: Displays the LV port number. 3081 is default.

Raw port number: Displays the Raw port number. 3082 is default.

Telnet port number: Displays the telnet port number. 3083 is default.


Apply: Click Apply to save the changes.

Cancel: Click Cancel to clear the NET field and replace the default value.



TransNav GUI Guide, Section 3: NetworkTTD ACL Tab

TTD ACL Tab On the OSI Parameters Configuration Panel dialog box, click the TTD ACL tab.

Figure 3-31 OSI Parameters Configuration Panel—TTD ACL Tab


New: Add a new ACL to the list.

Add: Add a new ACL to the list.

Delete: Remove the selected ACL from the list.

Cancel: Cancel any changes and return to the main screen.



Chapter 6 OSI Parameters ConfigurationTTD Tab

TTD Tab On the OSI Parameters Configuration Panel dialog box, click the TTD tab.

Figure 3-32 OSI Parameters Configuration Panel—TTD Tab


New. Add a new TTD to the list. Edit the field that appears.

Add. After you click New to add the new TTD to the list.

Delete. Remove the selected TTD from the list.

Cancel. Cancel any changes and return to the main screen.



TransNav GUI Guide, Section 3: NetworkMan Area Tab

Man Area Tab On the OSI Parameters Configuration Panel dialog box, click the Man Area tab.

Figure 3-33 OSI Parameters Configuration Panel—Man Area Tab


New: Click to add a new manual area address to the Area Address list.

Add: After you enter a new manual area address, click Add to add the address to the list.

Delete: Remove the selected address from the list.

Cancel: Cancel any changes and return to the main screen.



SECTION 4 PROTECTION SWITCHING

Contents

Chapter 1BLSR and MS-SPRing Protection Groups

Create a BLSR or MS-SPRing Protection Group . . . . . . . . . . . . . . . . . . . . . . 4-1Synchronize Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4Operations Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4Protection Switch Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5Protection Switch Request Priorities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5Squelch Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6Updating a Topology (Adding a Node) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7

Chapter 2UPSR and SNCP Ring Protection Groups

Create a UPSR or SNCP Ring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9Ring Synchronize Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11SNCP/UPSR Protection Switch Commands . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11Synchronizing, Editing, and Deleting Configured Protection Rings. . . . . . . . . 4-12Updating a Topology (Adding a Node) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13

Chapter 3Equipment Protection Groups

Create an Equipment Protection Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15Equipment Protection Switch Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-18Protecting Card Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-18Working Card Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-18Request Priorities for Equipment Protection . . . . . . . . . . . . . . . . . . . . . . . . . . 4-19

Chapter 41+1 MSP/APS Protection Groups

Create a 1+1 MSP/APS Protection Group . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21Switching 1+1 APS Protection Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-24Protecting Port Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-24Working Port Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-25Request Priorities for 1+1 APS Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-25

Chapter 51+1 Path Protection Groups

Create a 1+1 Path Protection Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-27Protection Switching Path Protected Services . . . . . . . . . . . . . . . . . . . . . . . . 4-28

Chapter 6Carrier Ethernet Protection Pair

Ethernet Cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-29


TransNav GUI Guide Section 4 Protection Switching

Carrier Ethernet Protection Pair. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-30Inter-card Link Aggregation Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-30Creating a Carrier Ethernet Protection Pair . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-31

Chapter 71+1 Optimized Protection Groups

Create a 1+1 Optimized Protection Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-34Protection Switch Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-35Primary State Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-36Secondary State Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-36Request Priorities for 1+1 Optimized Protection . . . . . . . . . . . . . . . . . . . . . . . 4-36


SECTION 4PROTECTION SWITCHING

Chapter 1 BLSR and MS-SPRing Protection Groups

Introduction 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-3• Synchronize Status, page 4-6• Operations Menu, page 4-6• Protection Switch Commands, page 4-7• Protection Switch Request Priorities, page 4-7• Squelch Table, page 4-8• Updating a Topology (Adding a Node), page 4-9

For guidelines and procedures to provision a BLSR or MS-SPRing, see the TransNav Provisioning Guide, Section 3—Creating Protection Groups, Chapter 2—“Creating a BLSR/MS-SPRing Protection Group”.

Create a BLSR or MS-SPRing Protection Group

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.

Note: If the BLSR ring is carrying high order end-to-end services, the only protection options supported are Any or Full protection.

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


TransNav GUI Guide, Section 4: Protection SwitchingCreate 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.• 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.


Chapter 1 BLSR and MS-SPRing Protection GroupsCreate a BLSR or MS-SPRing Protection Group

• 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 TransNav Provisioning Guide

for procedures on adding a node.• Remove Node: Remove a node from the existing ring.


TransNav GUI Guide, Section 4: Protection SwitchingSynchronize 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-8.

• Clear. See Protection Switch Commands, page 4-7.• Lockout Protecting Ring. See Protection Switch Commands, page 4-7.• Forced (FS_R). See Protection Switch Commands, page 4-7.• Manual (MS_R). See Protection Switch Commands, page 4-7.


Chapter 1 BLSR and MS-SPRing Protection GroupsProtection Switch Request Priorities

Protection Switch Commands

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).

Protection Switch Request Priorities

Switching request priorities (from highest to lowest) for BLSR or MS-SP ring protection are:• Clear: User-initiated action.• Lockout of Protection (ring): 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.• No Request.


TransNav GUI Guide, Section 4: Protection SwitchingSquelch 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 the TransNav Provisioning Guide, Section 2—Creating ADM Services, Chapter 1—“Service Provisioning Concepts” 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.


Chapter 1 BLSR and MS-SPRing Protection GroupsUpdating a Topology (Adding a 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).

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).


TransNav GUI Guide, Section 4: Protection SwitchingUpdating a Topology (Adding a Node)



Chapter 2 UPSR and SNCP Ring Protection Groups

Introduction 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-11• Ring Synchronize Status, page 4-13• SNCP/UPSR Protection Switch Commands, page 4-13• Synchronizing, Editing, and Deleting Configured Protection Rings, page 4-14• Updating a Topology (Adding a Node), page 4-15

For guidelines and procedures to provision a UPSR or SNCP ring, see either the TransNav Provisioning Guide or TraverseEdge 100 User Guide.

Create a UPSR or SNCP Ring

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


TransNav GUI Guide, Section 4: Protection SwitchingCreate 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 TransNav Provisioning Guide.• Remove Node (available for existing rings only): Remove a node from the existing

ring.• Apply (available for existing rings only): Apply changes.


Chapter 2 UPSR and SNCP Ring Protection GroupsSNCP/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 7—“Managing Service Paths,” Showing TxRx Paths.


TransNav GUI Guide, Section 4: Protection SwitchingSynchronizing, 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-3.– UPSR Ring Configuration dialog box. See Create a UPSR or SNCP Ring,

page 4-11.• 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.


Chapter 2 UPSR and SNCP Ring Protection GroupsUpdating 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 the TransNav Provisioning Guide, Section 8—Changing Network Configurations, Chapter 1—“Adding a Node to a Protected Ring Configuration,” Add a Node to the Ring 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.


TransNav GUI Guide, Section 4: Protection SwitchingUpdating a Topology (Adding a Node)



Chapter 3 Equipment Protection Groups

Introduction 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-17• Equipment Protection Switch Commands, page 4-20• Protecting Card Commands, page 4-20• Working Card Commands, page 4-20• Request Priorities for Equipment Protection, page 4-21

Only the Traverse system supports configurable equipment protection switching. For guidelines and procedures to provision an equipment protection group, see the TransNav Provisioning Guide, Section 3—Creating Protection Groups, Chapter 4—“Creating Equipment Protection Groups”.

For an explanation of how the TE-100 supports equipment protection switching, see the TraverseEdge 100 User Guide, Section 2, Chapter 4—“Platform Description and Specifications”.

Create an Equipment Protection Group

From the Shelf View, click the Protection tab, select 1 for N equipment, and click Add.

Figure 4-12 Add an Equipment Protection Group


TransNav GUI Guide, Section 4: Protection SwitchingCreate 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.


Chapter 3 Equipment Protection GroupsCreate 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, Force10 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-20 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, NGE Plus, or EoPDH 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.


TransNav GUI Guide, Section 4: Protection SwitchingEquipment 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-20.• See Working Card Commands, page 4-20.


Protecting Card Commands

Right-click the protecting card to display the switch commands. See Request Priorities for Equipment Protection, page 4-21 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.

Working Card Commands

Right-click the working card to display the switch commands. For switching request priorities, see Request Priorities for Equipment Protection, page 4-21.• 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.


Chapter 3 Equipment Protection GroupsRequest 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


TransNav GUI Guide, Section 4: Protection SwitchingRequest Priorities for Equipment Protection



Chapter 4 1+1 MSP/APS Protection Groups

Introduction This chapter contains information on the following topics:• Create a 1+1 MSP/APS Protection Group, page 4-23• Switching 1+1 APS Protection Group, page 4-26• Protecting Port Commands, page 4-26• Working Port Commands, page 4-27• Request Priorities for 1+1 APS Protection, page 4-27

For guidelines and procedures to provision a facility protection group, see the TransNav Provisioning Guide or the TraverseEdge 100 User Guide.

Create a 1+1 MSP/APS Protection Group

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


TransNav GUI Guide, Section 4: Protection SwitchingCreate 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.


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.


Chapter 4 1+1 MSP/APS Protection GroupsCreate 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.

Status: Displays a blank field or one of the following switch commands (see Switching 1+1 APS Protection Group 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.


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









TransNav GUI Guide, Section 4: Protection SwitchingSwitching 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• Working Port Commands


Protecting Port Commands

Right-click the protecting port to display the switch commands. See Request Priorities for 1+1 APS Protection 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.


Chapter 4 1+1 MSP/APS Protection GroupsRequest 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.


Working Port Commands

Right-click the working port to display the switch commands. See Request Priorities for 1+1 APS Protection 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.


Request Priorities for 1+1 APS Protection

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. From the protect card, the priority

is in the following order: Lockout, Signal Fail, Forced, Signal Degrade, Manual. From the working card, the order of priority is: Forced, Signal Fail, Signal Degrade, Manual.

• 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.


TransNav GUI Guide, Section 4: Protection SwitchingRequest Priorities for 1+1 APS Protection

• 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)



Chapter 5 1+1 Path Protection Groups

Introduction 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-29• Protection Switching Path Protected Services, page 4-30

Only the Traverse system supports 1+1 path protection groups. For guidelines and procedures to provision a 1+1 path protection group, see the TransNav Provisioning Guide, Section 3—Creating Protection Groups, Chapter 7—“Creating a 1+1 Path Protection Group”.

Create a 1+1 Path Protection Group

From the Shelf View, Protection tab, select 1+1 Path, and click Add.

Figure 4-18 Create a 1+1 Path Protection Group


TransNav GUI Guide, Section 4: Protection SwitchingProtection 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.


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.


Protection Switching Path Protected Services

See Section 6—Services, Chapter 7—“Managing Service Paths,” Protection Switching Path-Protected Services for information on performing protection switching.



Chapter 6 Carrier Ethernet Protection Pair

Introduction Use a Carrier Ethernet Protection Pair (CEPP) with NGE Plus or EoPDH cards to create inter-card link aggregation groups and aggregate data from Ethernet ports on two cards to a single EOS link. CEPP can also be used on EOS or EOP links on two EoPDH cards.

Ensure that no services are activated on either the working or protecting card before creating a CEPP. Similarly, no Policers, LAGs, EOS ports, EOP ports or VRBs can be created on the working or protecting card before creating a CEPP.

This chapter contains information on the following topics:• Ethernet Cards• Carrier Ethernet Protection Pair• Inter-card Link Aggregation Groups• Creating a Carrier Ethernet Protection Pair

Ethernet Cards

Important: The information in this section strictly pertains to the following Traverse cards: Next Generation Ethernet Plus (NGE Plus), Ethernet over PDH (EoPDH):

Cards Card Types

NGE Plus Cards GBE4-FE16-TX / CEP GBE2T-GBE2F-FE16-TX / CEP

EoPDH Cards GBE4-FE16-TX-EoPDH GBE2T-GBE2F-FE16-TX-EoPDH


TransNav GUI Guide, Section 4: Protection SwitchingCarrier Ethernet Protection Pair

Carrier Ethernet Protection Pair

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 or EoPDH 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 on NGE cards. For EoPDH cards, a maximum of 128 ports are available. The ports can be either EOS, EOP, or a combination of EOS and EOP ports that total 128 ports. EOP ports are available on EoPDH cards only.

Inter-card Link Aggregation Groups

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 multiple ports on the same card or to link multiple 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 ports must always be the same type (either FE or GbE). An NGE Plus or EoPDH card can only be in one CEPP at a time.


Chapter 6 Carrier Ethernet Protection PairCreating 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:



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 card. Enter a number between 1 and 60; default is 5.

Role: Indicates the role of the card. Valid values are:• Protecting: Select the card protecting the active traffic.• Working: Select the card carrying active traffic.


TransNav GUI Guide, Section 4: Protection SwitchingCreating a Carrier Ethernet Protection Pair

Card: Indicates the slot and NGE Plus or EoPDH 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-26 for definitions):• Clear• Lockout• Forced• Signal Failed• Signal Degraded• Manual• Wait to restore

Protection: Displays Standby for the standby card and Active for the active card.


Create: Create the carrier ethernet protection pair.

Cancel: Cancel the protection pair information.



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-36• Primary State Commands, page 4-38• Secondary State Commands, page 4-38• Request Priorities for 1+1 Optimized Protection, page 4-38

For guidelines and procedures to provision an optimized protection group, see either the TransNav Provisioning Guide or TraverseEdge 100 User Guide.


TransNav GUI Guide, Section 4: Protection SwitchingCreate 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:


Locked Out: A checkmark in the box indicates if a lockout command is applied on either the primary or secondary sections.

Apply Command: Select to apply the command. Valid values are Select a Command, Clear, and Lockout. Default value is Select a Command.


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


Chapter 7 1+1 Optimized Protection GroupsProtection 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-37):• 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.


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-38• Secondary State Commands, page 4-38


TransNav GUI Guide, Section 4: Protection SwitchingPrimary State Commands

Primary State Commands

Right-click the primary facility to display the switch commands. See Request Priorities for 1+1 Optimized Protection, page 4-38 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.

Secondary State Commands

Right-click the secondary state port to display the switch commands. See Request Priorities for 1+1 Optimized Protection, page 4-38 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 for 1+1 Optimized Protection

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)


SECTION 5 EQUIPMENT

Contents

Chapter 1Common Equipment

When to Change Card Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3Protection Groups and Card Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3Equipment States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4Parameters Common to All Card Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5GCM Card Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6

Chapter 2SONET Equipment

DS1 Card Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8DS1 Numbering. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9DS1 Mapping. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10DS3 Framing Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10DS1 Port Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10DS3 Card Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12DS3CC Port Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13DS3TMX and STS1TMX Port Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15Subport Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17EC1 Port Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-19SONET (OC-N) Card Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-22SONET Port Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-23SFP Port Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-28

Chapter 3SDH Equipment

E1 Card Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-31E1 Numbering (Traverse only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-32E1 Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-33E1 Mapping and Patch Panel Ports (Traverse only) . . . . . . . . . . . . . . . . . . . . 5-34TE-100 Interface Card Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-35E1 Port Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-36E3 Card Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-38E3 Port Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-38SDH (STM) Card Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-40STM Port Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-41SFP Port Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-46

Chapter 4Ethernet Equipment

Ethernet Equipment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-49


TransNav GUI Guide Section 5 Equipment

Ethernet Card Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-50MAC Address Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-52Ethernet Port Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-53SFP / XFP Port Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-58Ethernet Port Advanced Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-59EOS Port Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-63EOS Port Advanced Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-65Ethernet or EOS Port Queues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-67EOS Port Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-69Link Aggregation Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-71LAG Advanced Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-72Link Aggregation Control Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-72

Chapter 5TransAccess 200 Mux

Add a TransAccess 200 Mux. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-73Delete a TransAccess 200 Mux. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-75TransNav System Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-75Navigate to a TransAccess 200 Mux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-76Menu Options on the Sub Shelf Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-76

Chapter 6TraverseEdge 50 (TE-50)

Add a TE-50. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-79Delete a TE-50. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-81TransNav System Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-81Navigate to the TE-50 Menu Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-82


SECTION 5EQUIPMENT CONFIGURATION

Chapter 1Common Equipment

Introduction 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-3• Protection Groups and Card Configuration, page 5-3• Equipment States, page 5-4

This chapter also explains all the parameters that appear on each card. See the following sections for specific details:• Equipment States, page 5-4

To create and delete equipment during the preprovisioning process, see Chapter 1—“Creating and Deleting Equipment.”

When to Change Card Parameters

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.

Protection Groups and Card Configuration

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.


TransNav GUI Guide, Section 5: Equipment ConfigurationEquipment States

Equipment States

Icons in the bottom left-hand corner of the Config tab indicate the state of the card or port.

Figure 5-1 Equipment States

Equipped State: Displays one of the following values:• Equipped: Indicates the equipped state of the card or port. When Equipped, the

equipment is present in the system.• Non-Equipped: When selected, indicates the card or port is Non-Equipped; the

equipment is not present in the system.

Operational State: Displays one of the following values:• 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 values 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.

Operational state

Equipped state

Administrative state


Chapter 1 Common EquipmentParameters 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 card.


TransNav GUI Guide, Section 5: Equipment ConfigurationGCM Card Parameters

Command buttons are as follows:Apply: Click to apply changes to any default values.Cancel: Click to return to default values.

GCM Card Parameters

See Equipment States, page 5-4 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

Figure 5-3 GCM Card Configuration Tab

For GCM cards with integrated optics, 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”• For STM interfaces, see Chapter 3—“SDH Equipment”

Additional parameter


SECTION 5EQUIPMENT

Chapter 2SONET Equipment

Introduction This chapter describes all the parameters that appear for each SONET card and port.• DS1 Card Parameters• DS1 Port Parameters• DS3 Card Parameters• DS3CC Port Parameters• DS3TMX and STS1TMX Port Parameters• Subport Parameters• EC1 Port Parameters• SONET (OC-N) Card Parameters• SONET Port Parameters• SFP Port Parameters

See Chapter 1—“Common Equipment” for a description of the parameters that apply to every card.


TransNav GUI Guide, Section 5: EquipmentDS1 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.

Figure 5-4 DS1 Card Configuration Tab

The DS1 card has three additional parameters to configure:• DS1 Numbering• DS1 Mapping• DS3 Framing Format

Configurable parameters


Chapter 2 SONET EquipmentDS1 Numbering

DS1 Numbering

Select how the DS1 signals map into a VC- or a VT-structured payload on this card. The list of mapping formats is in the table below. 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 (default) • Sequential

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





6 VTG6, VT1 VTG2, VT2
























TransNav GUI Guide, Section 5: EquipmentDS1 Mapping

DS1 Mapping 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.

DS3 Framing Format

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.

DS1 Port Parameters

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.


Chapter 2 SONET EquipmentDS1 Port Parameters

• Unframed: Upon detecting an LOF condition (in Unframed mode), the system does not:– Raise an LOF alarm– Propagate an AIS– Insert an RAI– Count OOF and SEF framing errors

Line Coding: Displays the line coding technique used for performance monitoring at the line layer. Select one of the following 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.

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” for information on how to use performance monitoring templates.

See the 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.


TransNav GUI Guide, Section 5: EquipmentDS3 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 and cannot be selected.

• 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, you can 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.


Chapter 2 SONET EquipmentDS3CC Port Parameters

DS3CC Port Parameters

The parameters in this section apply to DS3CC (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 the system does not process C-bits as shown in GR-499-CORE Table 10-14.



TransNav GUI Guide, Section 5: EquipmentDS3CC 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.

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.




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 and cannot be selected.



Chapter 2 SONET EquipmentDS3TMX 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, UTMX-24, or UTMX-48 card. Click the Config tab to display the Port Configuration screen.

Note: On UTMX-48 cards, ports 1 through 24 are physical ports that are in DS3TMX mode by default. Each DS3TMX port can be individually configured to operate in EC1, DS3-CC, E3-CC, DS3-TMX, or STS1-TMX mode. Ports 25 through 48 are logical ports and can only operate in STS1TMX mode.

Figure 5-8 DS3TMX Port Config Tab


Type: Displays port type (DS3TMX or STS1TMX)



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 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


TransNav GUI Guide, Section 5: EquipmentDS3TMX and STS1TMX Port Parameters

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.• 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 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.

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.




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


Chapter 2 SONET EquipmentSubport Parameters

• 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 and cannot be selected.


Subport Parameters

The parameters in this section apply to DS3TMX and STS1TMX ports. From Shelf View, click a port on the DS3TMX, UTMX-24, or UTMX-48 cards. 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 for physical ports. 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

If the DS3 Mapping on the parent TMX port is E1, select one of the following values in the Line Format column:


TransNav GUI Guide, Section 5: EquipmentSubport Parameters

• 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 portPM 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” for information on how to use performance monitoring templates.See the 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.


Chapter 2 SONET EquipmentEC1 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:


Type: Displays port type (EC1)



Line Format: Displays SONET

Signal Level: Displays DSX-3


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 Section 3—Network, 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• Transit Node: Transit Node Clock Traceable


TransNav GUI Guide, Section 5: EquipmentEC1 Port Parameters

• 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• None• Invalid

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 • None• Invalid

Valid Signal Timer (min): Indicates the number of minutes since the last detection of a valid incoming EC1 signal. Valid values are 0 through 2800. The default is 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


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


Chapter 2 SONET EquipmentEC1 Port Parameters



• 1E-6 (default): Value equals 1 x 10-6


Customer: Select from the list of defined customer profiles. Default is No Customer Selected. For details on creating customer profiles, see Adding Customer Information.

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.


See the Operations and Maintenance Guide for details on performance monitoring parameters for EC1 ports.



Command buttons are as follows:• Switch to DS3: Switch port from EC1 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.


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.


TransNav GUI Guide, Section 5: EquipmentSONET (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.

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




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)



Chapter 2 SONET EquipmentSONET 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)



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. 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



TransNav GUI Guide, Section 5: EquipmentSONET Port Parameters

SfBer-L: Measures the transmission quality (bit error ratio) of failed signals on the link. When the error rate crosses the value specified in this parameter, the system raises a signal failed bit error rate (BERSF-L) alarm and performs a protection switch.

Select one of the following values: • 1E-3 (default): Value equals 1 x 10-3



Transmitter State: Select one of the following:• On (default): Laser is turned on• Off: Laser is turned off

Transmitter Auto Shutdown: 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: 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 (DUS)



• 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.

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





Current Transmitter State: 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. The valid value is 16 bytes.

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). The valid value is 16 bytes.


TransNav GUI Guide, Section 5: EquipmentSONET Port Parameters

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.


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.


See the Operations and Maintenance Guide for details on performance monitoring parameters for SONET ports.


Alarm Profile: Select from the list of defined alarm profiles. Default is default.

Control Data : 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: 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.

Path DCC Configuration (TE-100 OC-3, and OC-12 interfaces only.): Click this button to configure the SONET paths to carry management traffic.

L2 Protocol: Determines the Layer 2 (L2) protocol for this port.



• PPP (default): Point-to-point protocol. Use PPP if this port is connected to another Traverse platform.

• LAPD: Link access procedure D-channel. Select LAPD if this port is connected to legacy third-party ADM equipment and this node is used as an OSI DCC gateway node.

LAPD Role: Select the role of this node in the OSI DCC gateway application:• Network• User

DWDM wl supp value: The DWDM wavelength supplied value.

LAPD Mode: Select the mode of this node in the OSI DCC gateway application.• AITS: Acknowledge information transfer service. Use this value if the value in L2

Protocol is LAPD.• UITS (default): Unacknowledge information transfer service. Use this value if the

value in L2 Protocol is PPP.

LAPD MTU: Indicates the maximum transmission unit for this node if the value in L2 Protocol is PPP. Default is 512.

DWDM wl: Select from the list of defined wavelength frequencies. For frequency to wavelength data, see the Traverse Product Overview Guide, Section 3—Card (Module) Descriptions, Chapter 5—“SONET/SDH Cards”.


configuration information has changed since the last time Apply was clicked, the button is grayed-out.



TransNav GUI Guide, Section 5: EquipmentSFP Port Parameters

SFP Port Parameters

On a Force10 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: Force10 does not support swapping of transceivers.

Figure 5-13 SFP Fields on Port Configuration Screen

The Port Configuration screen displays the following information. The values that display are provided by the transceiver manufacturer.

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; seen on Ethernet 10GbE or GbE-10 cards only), 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 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.

BitRate,Nominal (100Mbps): 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.


Chapter 2 SONET EquipmentSFP 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.


Refresh: Click to renew the data in the display.

Done: Close the dialog box and return to the main configuration screen.


SECTION 5EQUIPMENT

Chapter 3SDH Equipment

Introduction This chapter explains all the parameters that appear on each 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


E1 Card Parameters

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.

Figure 5-15 E1 Card Card Configuration Tab



TransNav GUI Guide, Section 5: EquipmentE1 Numbering (Traverse only)

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.

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


Chapter 3 SDH EquipmentE1 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:

20 7, 2 6, 3

21 7, 3 7, 3

Table 5-2 E1 Sequential and Non-Sequential Mapping Formats (continued)

E1 Port Sequential(TUG2#,TU12#)

Non-Sequential(TUG2#,TU12#)

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


TransNav GUI Guide, Section 5: EquipmentE1 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.

20 7, 2

21 7, 3

Table 5-3 DS3-structured VC3-mapped E1 channels (continued)

E1 port 6312 Kbps signal #, E1 channel #

Table 5-4 E1 Mapping and Patch Panel Ports

EI PortsPatch Panel Ports

DS3-Mapped 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


Chapter 3 SDH EquipmentTE-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


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.

Important: See the TraverseEdge 100 User Guide, —, Chapter 12—“Creating SDH Services” for guidelines on creating SDH services on a TE-100 system.

For all other parameters on the Interface Card, see Chapter 4—“Ethernet Equipment”.


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.



TransNav GUI Guide, Section 5: EquipmentE1 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:


Type: Displays port type (E1).



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


Chapter 3 SDH EquipmentE1 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.


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.


See the 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.





TransNav GUI Guide, Section 5: EquipmentE3 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:


Type: Displays port type (E3CC).



Chapter 3 SDH EquipmentE3 Port Parameters


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.

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.


See the Operations and Maintenance Guide for details on performance monitoring parameters for E3 ports.







TransNav GUI Guide, Section 5: EquipmentSDH (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.

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)



Chapter 3 SDH EquipmentSTM 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 Section 3—Network, 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.



TransNav GUI Guide, Section 5: EquipmentSTM 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



Transmitter State (Does not apply to STM-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



• 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





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. The valid value is 16 bytes.

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.

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


TransNav GUI Guide, Section 5: EquipmentSTM Port Parameters

the transmitter. If this port receives an incorrect identifier, the system raises an RS-TIM (Regenerator Section - Trace Identifier Mismatch alarm). The valid value is 16 bytes.

Rev Section Trace: The expected access point identifier to be received in the J0 byte. Enter an alphanumeric character string.

SS Bit Receive: Indicates the SS bit value that this interface is receiving.

Current Received Section Trace: Indicates the section trace currently being received.


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.


See the Operations and Maintenance Guide for details on performance monitoring parameters for STM ports.


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.• 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 DCC Configuration (TE-100 STM-1 and STM-4 interfaces only. Does not apply to STM-1E): Click this button to configure the STM path 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 5—“SONET/SDH Cards,” page 3-37.


configuration information has changed since the last time Apply was clicked, the button is grayed out.




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. The values that display are provided by the transceiver manufacturer.

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; seen on Ethernet 10GbE or GbE-10 cards only), 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 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.

BitRate,Nominal (100Mbps): Displays the nominal bit rate in increments of 100 Mbps.

Vendor PN: Displays the part number of the vendor of the hardware.


Chapter 3 SDH EquipmentSFP 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-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.


Refresh: Click to renew the data in the display.

Done: Close the dialog box and return to the main configuration screen.


SECTION 5EQUIPMENT

Chapter 4Ethernet Equipment

Introduction This chapter contains the following topics: • Ethernet Equipment• Ethernet Card Parameters• MAC Address Table• Ethernet Port Parameters• Ethernet Port Advanced Parameters• EOS Port Parameters• EOS Port Advanced Parameters• Ethernet or EOS Port Queues• EOS Port Status• Link Aggregation Group• LAG Advanced Parameters

Ethernet Equipment

This information also pertains to the Ethernet parameters on the TE-100 shelf unless noted otherwise.

+

Important: The information in this section strictly pertains to the following Traverse cards: Next Generation Ethernet (NGE), Next Generation Ethernet Plus (NGE Plus), 10GbE (1-port 10GbE), GbE-10 (10-port GbE), Ethernet over PDH (EoPDH).

Cards Card Types

NGE Cards GBE4-FE16-TX GBE2T-GBE2F-FE16-TX


10GBE Card 10GbE Not applicable

GBE-10 Card GbE-10 Not applicable



TransNav GUI Guide, Section 5: EquipmentEthernet 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, click this button to see a table that allows you to view and edit the learned MAC addresses for this card. See the topic MAC Address Table.

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.

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


Chapter 4 Ethernet EquipmentEthernet Card Parameters

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 Alternate 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.


TransNav GUI Guide, Section 5: EquipmentMAC 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, EOP, 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• EOP (Traverse only): Ethernet over PDH (EOP) ports


Chapter 4 Ethernet EquipmentEthernet Port Parameters

• ETH: ETH100TX interfaces• GBE: GbE ports• LAG (Traverse only): Link aggregation group ports

If an EOS or EOP port is created and assigned a specific Port ID, a MAC address will be assigned by the system. If the EOS or EOP port is deleted and then re-created with the same Port ID, it will have the same MAC address.


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.

Note: Not available for EOP ports on EoPDH cards. For information on EOP ports, refer to the TransNav Provisioning Guide, Section 7—Configuring Ethernet, Chapter 6—“Ethernet Over PDH (EOP)” for information on EOP ports.

Figure 5-26 Ethernet GBE Port Configuration Screen


TransNav GUI Guide, Section 5: EquipmentEthernet Port Parameters

Auto-negotiation (All TE-100 ports and Traverse cards except 10GbE): Specifies if the Auto-negotiation feature is 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 set in the Port configuration screen (speed and duplex attributes) or in the Advanced parameters (pause attribute) as applicable to the port type. See the topic Ethernet Port Advanced Parameters for explanations of the Pause 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). Manual Speed and Manual Duplex are defined in this section. See the topic Ethernet Port Advanced Parameters for explanations of the Pause parameters.

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 Crossover (Config tab): Controls the MDI/MDIX configuration of this port. – Enabled (default): Select to reverse the transmit and receive on this port. Turns

a straight-through cable into a crossover cable. The default FE port is MDI.– Disabled

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.

Important: By default, the Auto-negotiation feature is always enabled.

Force10 recommends that if the peer device is IEEE 802.3 compliant, the operator leave the Auto-negotiation feature enabled. Auto-negotiation is required for electrical GbE ports (IEEE 802.3 clause 40.5).

To avoid unpredictable system behavior, Force10recommends never disabling the Auto-negotiation feature for a port on a 10-port GbE card that has an electrical SFP installed instead of an optical SFP.



– 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.

Jumbo Frame Support (Traverse, GBE, and 10GbE 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.

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.

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.

Transmitter State (GBE and 10GbE 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 and 10GbE 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.


TransNav GUI Guide, Section 5: EquipmentEthernet Port Parameters

• 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.

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.

Current Transmitter State (Traverse, GBE and 10GbE only): 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.


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.




Advanced: Click to set advanced port parameters. See the topic Ethernet Port Advanced Parameters.

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.


TransNav GUI Guide, Section 5: EquipmentSFP / XFP Port Parameters

SFP / XFP Port Parameters

On a Force10node 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.

Figure 5-27 Pluggable Transceiver Fields on Port Configuration Screen

Important: Use SFPs or XFPs approved by Force10to avoid possible equipment damage that may occur, thus voiding any warranty.


Chapter 4 Ethernet EquipmentEthernet Port Advanced Parameters

Ethernet Port Advanced Parameters

The parameters in this topic apply to the following physical Ethernet ports on NGE, NGE Plus, 10GbE, GbE-10, and EoPDH cards only, unless otherwise noted: GBE, GBETX, ETH100TX, link aggregation groups (LAG), and Ethernet over SONET/SDH (EOS) ports.

Figure 5-28 Traverse NGE 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, and EOS ports: Enter an integer between 1 and 1000; default

is 1000.


TransNav GUI Guide, Section 5: EquipmentEthernet Port Advanced Parameters

If Auto-negotiation is turned off for this port, set the following values for Manual Pause:• Manual Pause (ETH100TX):

– Enabled (default): The system sends 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.

– Disabled: The system does not send a PAUSE frame. • Manual Pause: (optical GBE ports)

– 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.

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.


Chapter 4 Ethernet EquipmentEthernet 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.

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.

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.

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.

• 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.


TransNav GUI Guide, Section 5: EquipmentEthernet Port Advanced Parameters

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.


Chapter 4 Ethernet EquipmentEOS Port Parameters

EOS Port Parameters

An EOS port is a virtual 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.

For information about EOP ports, see the TransNav Provisioning Guide, Section 7—Configuring Ethernet, Chapter 6—“Ethernet Over PDH (EOP)”.

Figure 5-29 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-30 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, GbE-10, or EOPDH 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.


TransNav GUI Guide, Section 5: EquipmentEOS Port Parameters

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.On an EoPDH card, the maximum number of physical ports is 20; the maximum number of ports is 128. The maximum number of ports can be all EOS ports, all EOP ports, or a combination of EOS and EOP ports that total 128.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.

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, NGE Plus, and EoPDH 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 to control the suppression of alarms on the EOS port member.• Unlock (default)• Locked


Chapter 4 Ethernet EquipmentEOS Port Advanced Parameters

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.

Note: If the card or EOS port is in a Locked state, no alarms will be generated.

EOS Port Advanced Parameters

See the topic Ethernet Port Advanced Parameters for parameters common to all Ethernet port types.

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 removes any failed members from this service and

continues 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.


TransNav GUI Guide, Section 5: EquipmentEOS Port Advanced Parameters

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 TransNav Provisioning Guide, Chapter 9—“Rapid Spanning Tree Protocol”.

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 number between 0 and 192 on a 10GbE and GbE-10 card. On an EoPDH card, enter a number between 0 and 128 that equals the number of EOS ports provisioned on the 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. On an EoPDH card, enter a number between 0 and 128 that equals the number of EOS ports provisioned on the 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.


Chapter 4 Ethernet EquipmentEthernet or EOS Port Queues

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-31 Edit EOS Tab

The EOS Queue Status dialog box displays:

Figure 5-32 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, NGE Plus and EoPDH card 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.


TransNav GUI Guide, Section 5: EquipmentEthernet or EOS Port Queues

• Queue 2 Occupancy (Read-only): Displays the length of the queue in KB for Queue 2 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. • 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, an EOS port, or an EOP 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:


Refresh: Click Refresh to refresh the displayed data.

Done: Click Done to close the dialog box and return to the main screen.

Table 5-5 System Defaults for RED Thresholds

Link SpeedYellow 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


Chapter 4 Ethernet EquipmentEOS 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-33 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.


TransNav GUI Guide, Section 5: EquipmentEOS Port Status

TxLcasState (LCAS-enabled EOS ports only): 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• 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 64ms for NGE and NGE Plus cards and 128ms for GE cards.

Last Query (Read-only): The date and time of the last query on the status of the EOS port.


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-34) of less than 64 ms, and with excessive relative differential delay (Figure 5-35) of more than 64 ms. In Figure 5-35, 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.


Chapter 4 Ethernet EquipmentLink Aggregation Group

Figure 5-34 EOS Port Status with Normal Relative Differential Delay

Figure 5-35 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-36 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.


TransNav GUI Guide, Section 5: EquipmentLAG Advanced Parameters

• 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.

LAG Advanced Parameters

See the topic Ethernet Port Advanced Parameters 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.

Link Aggregation Control Protocol

For GbE-10 cards, the Link Aggregation Control Protocol (LACP) of a LAG is available. Link Aggregation Control Protocol (LACP) extends the LAG capabilities of the GbE-10 card on the Traverse system by providing coordinated link memberships of the LAG. This allows easier configuration when interoperating with non-Force10 equipment. LAGs must be set up on the GbE-10 card prior to configuring LACP.

For more information on LACP, see the TransNav Provisioning Guide, Section 7—Configuring Ethernet, Chapter 3—“Link Aggregation”.


SECTION 5EQUIPMENT

Chapter 5TransAccess 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

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 Attach Sub Shelf, then click TA200 to add a TransAccess 200 Mux system to the user interface.

Figure 5-37 Attach TA200 Sub Shelf

Important: Refer to the TransAccess 200 Mux Operations Manual 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.


TransNav GUI Guide, Section 5: EquipmentAdd a TransAccess 200 Mux

The Attach TA200 Shelf dialog box appears.

Figure 5-38 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 parameter.

If you select the Advanced checkbox, the following additional optional parameters display to define how the TransAccess 200 Mux is connected to the Traverse node through the TransNav management system.

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 alphanumeric 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 alphanumeric 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 3,000 to 90,000 milliseconds. The default value is 5,000 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.


Chapter 5 TransAccess 200 MuxTransNav System Parameters

Command buttons are as follows:• 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. If the Traverse node is a 20-slot shelf, the icon on the left displays. If the Traverse node is a 16-slot shelf, the icon on the right displays.

Figure 5-39 TransAccess 200 Mux in Map View


Delete a TransAccess 200 Mux

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.

TransNav System Parameters

From the Admin menu, click Attached Devices SNMP Parameters. The System Parameters Configuration dialog box displays.

Figure 5-40 System Parameters for TransAccess 200 Mux

Poll Interval. Defines how often the management server polls the TransAccess 200 Mux shelves attached to the Traverse to determine if the devices are still connected. Enter an integer between 60 and 1,000 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 21,600 seconds.


TransNav GUI Guide, Section 5: EquipmentNavigate 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-41 Launch TransAccess 200 Mux User Interface

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-42 TA200 Sub Shelf Configuration

Important: Refer to the TransAccess 200 Mux Operations Manual for parameter descriptions and procedures on how to configure this product.


Chapter 5 TransAccess 200 MuxMenu Options on the Sub Shelf Menu

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.

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 alphanumeric 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. The default is public.

Timeout. The period in milliseconds after which the TransNav server will disconnect a GUI session if no activity is detected. The range is 3,000 to 90,000 milliseconds. The default is 5,000 milliseconds.

Alarm Profile. Select the alarm profile of type ta200 to use with this TransAccess 200 Mux system. For information on alarm profiles, see Section 8—Maintenance and Testing, Chapter 2—“Alarms”.

Trap Receive Port (read only): The port on this device that receives SNMP traps. The default is 162.

Write Community: An alphanumeric 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. The default is public.

Number of Retries.The number of times the Traverse node tries to connect to the TransAccess 200 Mux node. The default is 5.


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.


TransNav GUI Guide, Section 5: EquipmentMenu Options on the Sub Shelf Menu


SECTION 5EQUIPMENT

Chapter 6TraverseEdge 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-82

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-43 Attach Sub Shelf

The Attach TE50 Shelf dialog box appears.

Important: The user MUST enable community access to ‘READ-WRITE’ on the TCP/IP configuration via the TE-50 telnet interface for alarms to display correctly on the TransNav management system.

Refer to the TraverseEdge 50 (TE-50) User Guide for parameter descriptions and procedures on how to configure this product.


TransNav GUI Guide, Section 5: EquipmentAdd a TE-50

Figure 5-44 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 alphanumeric 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 alphanumeric 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 3,000 to 90,000 milliseconds. The default is 5,000 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 port on the sub-shelf device that is receiving the SNMP traps. The default is 162.


Chapter 6 TraverseEdge 50 (TE-50)TransNav System Parameters

Command buttons are as follows:• Add: Click Add to add the TE-50 to the Traverse shelf. The Traverse node icon

changes to indicate there is a TE-50 shelf attached. If the Traverse node is a 20-slot shelf, the icon on the left displays. If the Traverse node is a 16-slot shelf, the icon on the right displays.

Figure 5-45 TE-50 in Map View


Delete a TE-50 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.

TransNav System Parameters

From the Admin menu, click Attached Devices SNMP Parameters. The System Parameters dialog box displays.

Figure 5-46 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.


TransNav GUI Guide, Section 5: EquipmentNavigate to the TE-50 Menu Options

Navigate to the TE-50 Menu Options

Click the Traverse node with the TE-50 attached, then right-click to display the shortcut menu. Click Sub Shelf to display the menu options.

Figure 5-47 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.

Sub Shelf Configuration. Opens the Sub Shelf Configuration dialog box.

Figure 5-48 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.


Chapter 6 TraverseEdge 50 (TE-50)Navigate to the TE-50 Menu Options

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 3,000 to 90,000 milliseconds. The default is 5,000 milliseconds.

Alarm Profile: Select the alarm profile of type te50 to use with this TE-50 system. For information on alarm profiles, see Section 8—Maintenance and Testing, Chapter 2—“Alarms”.

Trap Receive Port (read only): The port on this device that receives SNMP traps. The default is 162.

Write Community: An alphanumeric character string (public is the default) 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 parameter 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.


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.


TransNav GUI Guide, Section 5: EquipmentNavigate to the TE-50 Menu Options


SECTION 6 SERVICES

Contents

Chapter 1SONET Services

Create a SONET Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5Create SONET Service Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7Choose Endpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-8Configure Protection Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-9

General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-9SNCP/UPSR Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-10MSSP/BLSR Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-101+1 Path Protection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-10

Configure Advanced Parameters (Alphabetic Order) . . . . . . . . . . . . . . . . . . . 6-10

Chapter 2SDH Services

Create an SDH Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-16Create SDH Service Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-17Choose an Endpoint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-18Starting AUG1 Numbers for VC-3 Services . . . . . . . . . . . . . . . . . . . . . . . . . . 6-19Starting AUG1 Numbers for VC-4 Services . . . . . . . . . . . . . . . . . . . . . . . . . . 6-19Configure Protection Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-20

General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-20SNCP/UPSR Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-21MSSP/BLSR Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-211+1 Path Protection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-21

Configure Advanced Parameters (Alphabetic Order) . . . . . . . . . . . . . . . . . . . 6-22

Chapter 3Ethernet Services

Ethernet Cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-27Create an Ethernet Service and Configure Parameters . . . . . . . . . . . . . . . . . 6-28Creating a Multipoint ECC Service (Traverse only). . . . . . . . . . . . . . . . . . . . . 6-30Advanced Parameters Ethernet Service Ports (Traverse only). . . . . . . . . . . . 6-31Advanced Parameters Ethernet Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-32Guaranteed Data Rate and Ethernet Services . . . . . . . . . . . . . . . . . . . . . . . . 6-33Bandwidth Profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-34Bandwidth Profile Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-35Policers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-37Classifiers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-38TE-100 Classifiers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-39


TransNav GUI Guide Section 6 Services

Chapter 4VC-Bundles

Create a VC-bundle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-42Configure VCB Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-43Configure Advanced Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-43

Chapter 5Service Groups

Create Service Group Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-45Service Group Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-47Edit Service Group Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-47

Chapter 6Managing Services

Service Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-49Service Availability Status Audit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-53Service Shortcut Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-53Working with the Service List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-54

Sorting Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-54Resizing Columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-54Grouping Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-54Filtering Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-54

Setting Service Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-55Service Filters, Type Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-55Service Filters, Node Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-56Service Filters, Source Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-57Service Filters, Destination Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-58Service Filters, Customer Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-59Search for Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-60

Chapter 7Managing Service Paths

Showing TxRx Paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-63Transmit and Receive Paths for Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-64Refresh Status of Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-65Viewing Service Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-65Viewing Service Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-66Assigning or Suppressing Alarms to Path Endpoints . . . . . . . . . . . . . . . . . . . 6-66Retrieving Service Performance Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-69Protection Switching Path-Protected Services . . . . . . . . . . . . . . . . . . . . . . . . 6-71


SECTION 6 SERVICES

Chapter 1 SONET Services

Introduction This chapter explains the following topics for SONET services:• Create a SONET Service• Create SONET Service Parameters• Choose Endpoints• Configure Protection Parameters• Configure Advanced Parameters (Alphabetic Order)

See the TransNav Provisioning Guide or TraverseEdge 100 User Guide for guidelines and procedures to create or remove SONET services.

For information on Low Order end-to-end services, see the TransNav Provisioning Guidem Section 4—Creating Service Applications, Chapter 4—“Creating SONET Low Order End-to-End Services and Tunnels”.

Create a SONET Service

From the Service tab, select SONET and click Add.

Figure 6-1 Add SONET Service


TransNav GUI Guide, Section 6: ServicesCreate a SONET Service

The Creating SONET Service dialog box displays.

Figure 6-2 Creating SONET Service Dialog Box

On the Creating SONET Service dialog box, perform the following steps in order:1. Enter the name and configure general parameters. For more information, see

Create SONET Service Parameters.2. Select the endpoints of the service.

– For hop-by-hop services, see Choose Endpoints.– For end-to-end services, see Configure Advanced Parameters (Alphabetic

Order).3. Set the protection parameters of the service. See Configure Protection

Parameters.4. Configure other characteristics of the connection. For more information, see 1+1

Path Protection.5. Click Apply.


Chapter 1 SONET ServicesCreate SONET Service Parameters

Create SONET 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.

Note: The Service Name limit is 64 characters in length. The CLI does limit horizontal output to 12 characters. The CLI has no limit for a vertical output mode. The GUI provides the ability to stretch a column to display the full service name length.

Description: Enter the description of the service. Use alphanumeric characters, spaces, and single quotes 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

Note: EoPDH cards support only VT1.5, STS-1, and STS-3c bandwidths.

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).

Customer: Select a customer name from the drop-down list box. For details, see Adding Customer Information.

Endpoint Table: Select the endpoints of the service. • For hop-by-hop services, see Choose Endpoints.• For end-to-end services, see the endpoint information in the TransNav

Provisioning Guide, Section 9—Appendices, Appendix B—“Service Endpoints”.

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.

Command buttons are as follows:• Advanced: Configure the characteristics of the connection. See 1+1 Path

Protection.• 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.


TransNav GUI Guide, Section 6: ServicesChoose Endpoints

Choose Endpoints

In the Create Service screen, click a row in the EndPoint column of the endpoint table.

Figure 6-3 Choosing Endpoints for SONET Services

The Choose an EndPoint dialog box displays in the upper left corner of the computer screen.

From the endpoint navigation tree, click the node, card, and—depending on the card type—the port, STS, VTG, and VT.

For information on valid source and destination endpoints, see the TransNav Provisioning Guide, Section 9—Appendices, Appendix B—“Service Endpoints”.

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.


Chapter 1 SONET ServicesConfigure Protection Parameters

Configure Protection Parameters

On the Create Service screen, click the Protection field to display the Protection dialog box.

Figure 6-4 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

• 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. – Clear the checkbox for the Protect link or path to continue to carry traffic once

the failure condition no longer exists. • 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.


TransNav GUI Guide, Section 6: ServicesConfigure Advanced Parameters (Alphabetic Order)

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 Advanced. The Advanced Parameters dialog box displays. A sample screen is shown below. The parameters that appear on the dialog box depend on the type of service being configured.

.

Figure 6-5 STS 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.


Chapter 1 SONET ServicesConfigure Advanced Parameters (Alphabetic 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 TransNav Provisioning Guide, Section 2—Creating Service Applications, Chapter 2—“Bridging and Rolling Services” 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.


Expected RTD (TE-100 only): 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. • DS4NA Async(12): Asynchronous mapping for DS4NA or E4. • 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-6 (default): Value equals 1 x 10-6




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:




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

Payload Mapping: Maps the STS-1 or VC-3 payload as a clear-channel container with no VT or VC containers. The clear-channel container is capable of processing low order containers. When either endpoint is a card capable of processing low-order containers, all containers within the STS-1 or VC-3 will be available on that card as individual low-order CTPs.

Redline 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


Chapter 1 SONET ServicesConfigure Advanced Parameters (Alphabetic Order)

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

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.


See the Operations and Maintenance Guide 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 (high bandwidth services only): 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.


SECTION 6SERVICES

Chapter 2SDH Services

Introduction This chapter explains the provisioning parameters forthe 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 the TransNav Provisioning Guide for guidelines and procedures to create or remove these services.

This chapter includes the following topics:• Create an SDH Service• Create SDH Service Parameters• Choose an Endpoint• Configure Protection Parameters• Configure Advanced Parameters (Alphabetic Order)


TransNav GUI Guide, Section 6: ServicesCreate an SDH Service

Create an SDH Service

From the Service tab, select SDH, SDH-Endpoint, or SDH-Tunnel, and click Add.

Figure 6-6 Add SDH Service

The Create Service tab displays.

Figure 6-7 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 SDH Service Parameters.2. Select the endpoints of the service.

– For hop-by-hop services, see Choose an Endpoint.– For end-to-end services, see Chapter 1—“SONET Services,” Configure

Advanced Parameters (Alphabetic Order).3. Set the protection parameters of the service. See Configure Protection

Parameters.

1

2

4 5

3


Chapter 2 SDH ServicesCreate SDH Service Parameters

4. Configure other characteristics of the connection. For more information, see Configure Advanced Parameters (Alphabetic Order).

5. Click Apply.

Create SDH Service Parameters



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)

Note: EoPDH cards support only VC-12 and VC-11 bandwidths. • 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 1—“SONET Services,” Configure Advanced Parameters (Alphabetic Order).

Customer: Select a customer name from the drop-down list box.

Add Customer: Click to add a Customer. For details, see Section 2—Administrative Tasks, Chapter 5—“Generating and Viewing Reports,” Adding Customer Information.

Endpoint Table. Select the endpoints of the service. • For hop-by-hop services, see Choose an Endpoint.• For end-to-end services, see the information on VC11 and VC12 endpoints in the

TransNav Provisioning Guide, Section 9—Appendices, Appendix B—“Service Endpoints”.

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.

Command buttons are as follows:• Advanced: Configure the characteristics of the connection. For more information,

see Configure Advanced Parameters (Alphabetic Order).


TransNav GUI Guide, Section 6: ServicesChoose an Endpoint

• 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.

Choose an Endpoint

In the Create Service tab, click a row in the EndPoint column of the endpoint table.

Figure 6-8 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. For information on service endpoints, see the TransNav Provisioning Guide, Section 9—Appendices, Appendix B—“Service Endpoints”.

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.


Chapter 2 SDH ServicesStarting AUG1 Numbers for VC-4 Services

Starting AUG1 Numbers for VC-3 Services

The starting AUG1 number for VC-3 paths depends on the data rate of the interface (Source Port or Destination Port) and the AU-level mapping. The Traverse supports AU-3 and AU-4 mapping of VC-3 payloads. The following table lists all the valid starting AUG1 numbers for VC-3 services.

Starting AUG1 Numbers for VC-4 Services

The available values for the Source Path and Destination Path parameters depends on the bandwidth selected. For example, an STM-16 interface has a Source Path range of a-1 to a-16 if you select VC-4 in the Bandwidth parameter. If you select VC-4-4c in the Bandwidth parameter, the Source Path can be a-1, a-2, a-3, or a-4. The following

Table 6-1 Starting AUG1 Numbers for VC-3 Paths

BandwidthPath

STM-1 STM-4 STM-16 STM-16

VC-3 a-1 tug3-1/vc3tug3-2/vc3tug3-3/vc3vc3-1vc3-2vc3-3

a-1a-2

a-3

a-4

tug3-1/vc3tug3-2/vc3tug3-3/vc3a-1, vc3-1a-1, vc3-2a-1, vc3-3

a-1a-2

a-16


a-1a-2

a-64


Table 6-2 Starting AUG1 Numbers for VC-4 Paths

BandwidthPath

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


TransNav GUI Guide, Section 6: ServicesConfigure Protection Parameters

Configure Protection Parameters

On the Create Service screen, click the Protection field to display the Protection dialog box.

Figure 6-9 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

• 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. – Clear the checkbox for the Protect link or path to continue to carry traffic once

the failure condition no longer exists. • 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.


Chapter 2 SDH ServicesConfigure Protection Parameters

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 tab, click the Advanced button.The Advanced Parameters dialog box displays. A sample screen is shown below. The parameters that appear on the dialog box depend on the type of service being configured.

.












Chapter 2 SDH ServicesConfigure Advanced Parameters (Alphabetic Order)



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. • DS4NA Async(12): Asynchronous mapping for DS4NA or E4. • 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










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:










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


Chapter 2 SDH ServicesConfigure Advanced Parameters (Alphabetic Order)

• 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














SECTION 6SERVICES

Chapter 3 Ethernet Services

Introduction This chapter explains the provisioning parameters for all Ethernet service types.

This chapter contains the following topics:• Ethernet Cards• Create an Ethernet Service and Configure Parameters• Creating a Multipoint ECC Service (Traverse only)• Advanced Parameters Ethernet Service Ports (Traverse only)• Advanced Parameters Ethernet Service• Guaranteed Data Rate and Ethernet Services• Bandwidth Profiles• Bandwidth Profile Dialog Box• Policers• Classifiers• TE-100 Classifiers

Ethernet Cards

Important: See one of the following references for guidelines, detailed information, and procedures on how to create Ethernet services:• TransNav Provisioning Guide, Section 7— Configuring Ethernet• TraverseEdge 100 User Guide, Section 6— Creating Ethernet Services

Important: The information in this section strictly pertains to the following Traverse cards: Next Generation Ethernet (NGE), Next Generation Ethernet Plus (NGE Plus), 10GbE (1-port 10GbE), GbE-10 (10-port GbE), Ethernet over PDH (EoPDH).

Cards Card Types

NGE Cards GBE4-FE16-TX GBE2T-GBE2F-FE16-TX


10GBE Card 10GbE Not applicable


TransNav GUI Guide, Section 6: ServicesCreate an Ethernet Service and Configure Parameters

This information also pertains to the Ethernet parameters on the TE-100 shelf unless noted otherwise.

Create an Ethernet Service and Configure Parameters

From the Service tab, select Ethernet and click Add.

Figure 6-11 Add Ethernet Service

On the Creating Ethernet Service dialog box, configure the parameters for this service.

Figure 6-12 Creating Ethernet Service Dialog Box




GBE-10 Card GbE-10 Not applicable


Cards Card Types


Chapter 3 Ethernet ServicesCreate an Ethernet Service and Configure Parameters

In the Type parameter, select the type of Ethernet service: • Bridge• AggrBridge (aggregate bridge)• Line• Multipoint ECC (use with EOP ports only)

VLAN Configuration:

Select the VLAN configuration type for the port types on this service. The valid values are:• Multiple VLAN Provisioning mode: Default for any Ethernet services created

after release TR3.2.• Single VLAN ID: If this is an existing service created before release TR3.2, this

value is the default in order to preserve the existing VLAN configuration. Select one or both of the following:– C-VLAN ID Preservation: Select this check box to preserve VLAN IDs for a

range of customer-tagged port members. • C-VLAN ID for all C-Tagged Ports: Enter a set of VLAN IDs (6, 7, 8), a

range of VLAN IDs (1-27), or a combination of ranges and individual VLAN IDs (1-15, 18, 21-24, 19) to be preserved for use on this service.

NOTE: No two activated services can use the same C-VLAN ID numbers.– Use same S-VLAN ID: Select this check box to use the same VLAN ID for all

service-tagged ports. – S-VLAN ID for all S-Tagged Ports: If the Use the same S-VLAN ID check

box is selected, enter the VLAN ID to be used for all service-tagged ports on this service. If this value is not selected, you can enter different VLAN IDs for each service-tagged port member.

Each Ethernet card can support 20 active Bridge, Aggregate Bridge, and Line services simultaneously. Each 10GbE and GbE-10 card can support at least 256 active Bridge and Aggregate Bridge services simultaneously.

Each EoPDH card can support four Multipoint ECC services. Each node can support 16 Multipoint ECC services. For more information on Multipoint ECC services, see Creating a Multipoint ECC Service (Traverse only).

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 for more

information on classifiers.• Policer: Select a policer for this service port. See Policers for more information on

policers.


TransNav GUI Guide, Section 6: ServicesCreating a Multipoint ECC Service (Traverse only)

Creating a Multipoint ECC Service (Traverse only)

Multipoint ECC (Ethernet control channel) services connect traffic on IP packets between the Traverse system and multiple CPE devices using EOP ports with the same endpoint on EoPDH cards. Prior to creating a multipoint ECC service, the EOP ports must be set up, the EOP ports should have a VLAN ID, and must be customer-tagged. For more information on creating EOP ports, see the TransNav Provisioning Guide, Section 7—Configuring Ethernet, Chapter 6—“Ethernet Over PDH (EOP),” Creating EOP Ports.

Each EoPDH card can support 4 multipoint ECC services. Each node can support 16 multipoint ECC services.

From the Service tab, select Ethernet and click Add.

Figure 6-13 Add Ethernet Service

On the Creating Ethernet Service dialog box, configure the parameters for this service.

Figure 6-14 Creating Ethernet Service, Multipoint ECC


IP address: Enter the IP address of the Traverse interface to direct IP packets to and from the CPE device.



Chapter 3 Ethernet ServicesAdvanced Parameters Ethernet Service Ports (Traverse only)

Type: Select Multipoint ECC as the type of Ethernet service.


Subnet mask: Enter the subnet mask for your system. When used with the IP address entered in the IP address field, the direct connection created is advertised to all nodes in the Traverse system.

Note: The ECC and IP address for the CPE must be in the same subnet range.

Member port priority: Indicates the priority of this port member. This value is set by the VLAN ID, if any, entered for the port member. The combination of VLAN ID and EOP member ID are unique to this port member.

Card: Select the EoPDH card on which to create the ECC.

In the Endpoint table, select the endpoints for this service. The Source and Destination must be the same endpoint and must be the on the same EoPDH 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 for more

information on classifiers.• Policer: Select a policer for this service port. See Policers for more information on

policers.

Advanced Parameters Ethernet Service Ports (Traverse only)

Configure the Advanced Parameters of each service port. These parameters override the Advanced parameter configuration for the Ethernet service. Click the Advanced column in the Endpoint table for each service port.

Figure 6-15 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.


TransNav GUI Guide, Section 6: ServicesAdvanced Parameters Ethernet Service

• 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.

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.

Advanced Parameters Ethernet Service

Configure the advanced parameters of the Ethernet Line bridge service. Click the Advanced button to display the Advanced Parameters dialog box.

Figure 6-16 Advanced Parameter Ethernet Line Service

Configure the following Ethernet service parameters:

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, —, Chapter 6—“Ethernet Services,” Supported VLAN Tagging and Ethernet Service Combinations. 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 —, Chapter 6—“Ethernet Services,” Configurable VLAN IDs for valid VLAN IDs.

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


Chapter 3 Ethernet ServicesGuaranteed Data Rate and Ethernet Services

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 —, Chapter 6—“Ethernet Services,” Configurable VLAN IDs 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.

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).

Table 6-3 CAC Limits for Sum of Guaranteed Data Rates Sharing a Port

Port Type CAC limits in Mbps

VT-1.5 1.600

VT-2 2.176

STS-1 48.384

STS-3c 149.760


TransNav GUI Guide, Section 6: ServicesBandwidth Profiles

Bandwidth Profiles

From the Admin menu, click Bandwidth Profiles. The Bandwidth Profiles dialog box displays.

Note: Do not use more than 64 bandwidth profiles for NGE modules.

Figure 6-17 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.


Add: Select to add a new profile to the system. The Bandwidth Profile Configuration dialog box displays. See Bandwidth Profile Dialog Box.

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.


Chapter 3 Ethernet ServicesBandwidth 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-18 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-4. 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)


TransNav GUI Guide, Section 6: ServicesBandwidth Profile Dialog Box

The maximum Peak Burst Size of the NGE and EoPDH cards is 256 Kb. For a CIR/PIR of 1000, the maximum CBS/PBS the NGE and EoPDH cards 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.


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.

8 to <16 225 * (IR/8)

16 to <32 225 * (IR/16)

32 to <64 225 * (IR/32)

64 to <128 225 * (IR/64)

IR > 128 225 * (IR/128)

Table 6-4. Maximum Bandwidth Burst Size Parameters (continued)

Information Rate(IR in Mbps)

Maximum Burst Size(MBS in Kb)


Chapter 3 Ethernet ServicesPolicers

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.

Figure 6-19 Create Policer Tab

Enter the following parameters:

ID: Indicates the policer ID. Enter an integer between 1 and 1024.

Card: Select the card in the shelf on which to configure the policer.

User tag: Enter a 16-character name for this Policer ID. The Policer ID and User tag combination will be unique.

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-20 Current Class of Service Values Displayed


TransNav GUI Guide, Section 6: ServicesClassifiers


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-21 Classifier Configuration Dialog Box



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


Chapter 3 Ethernet ServicesTE-100 Classifiers


Synchronize: Select to synchronize the changes with the management server.


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 TE100 Classifiers. The TE100 Classifiers dialog box appears. Click Add to add a new classifier to the classifier list. The TE100 Classifier Configuration dialog box displays.

Figure 6-22 TE100 Classifier Configuration Dialog Box



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


Synchronize: Select to synchronize the changes with the management server.


Cancel: Select to cancel any changes, close the dialog box, and return to the TE100 Classifiers dialog box.


TransNav GUI Guide, Section 6: ServicesTE-100 Classifiers


SECTION 6SERVICES

Chapter 4 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• Configure VCB Parameters• Configure Advanced Parameters


TransNav GUI Guide, Section 6: ServicesCreate a VC-bundle

Create a VC-bundle

From the Service tab, select VCB and click Add.

Figure 6-23 Add VCB Service

The Create Service tab for VC-bundle service displays.

Figure 6-24 Create VCB Services

To create a VC bundle, follow these steps:1. Configure the Name, Description, and Customer parameters. Use alphanumeric

characters only. The Description field can also accept the single quote character. 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.

1

2 3

4


Chapter 4 VC-BundlesConfigure Advanced Parameters

Configure VCB 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 Section 2—Administrative Tasks, Chapter 5—“Generating and Viewing Reports,” Adding Customer Information.

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.

Configure Advanced Parameters

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-25 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.


TransNav GUI Guide, Section 6: ServicesConfigure Advanced Parameters

• 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).

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.


SECTION 6SERVICES

Chapter 5 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.

This chapter contains the following topics:• Create Service Group Tab• Service Group Tab• Edit Service Group Tab

Create Service Group Tab

Click the Service Group tab, then click Add. The Create Service Group tab appears.

Figure 6-26 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.

Important: See the TransNav Provisioning Guide, Section 7— Configuring Ethernet for guidelines, detailed information, and procedures on how to create service groups.


TransNav GUI Guide, Section 6: ServicesCreate Service Group Tab

Concat. Size: Select the bandwidth of the services.• STS-1• STS-3c• HO-VC-3• VC-4

Protection (informational only): Indicates the type of protection for the service group is Co-route which means all members follow the same route.

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 NGE, NGE Plus, 10GBE and GBE-10 cards on separate nodes.

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-27 Service Group Advanced Parameters Dialog Box

NGE Modules NGE Plus Modules Gigabit Ethernet Modules

GBE4-FE16-TX GBE4-FE16-TX / CEP 10GBE

GBE2T-GBE2F-FE16-TX GBE2T-GBE2F-FE16-TX / CEP GBE-10


Chapter 5 Service GroupsEdit Service Group Tab

For specific definitions of these parameters, see: • Section 6—Services, Chapter 1—“SONET Services,” Configure Protection

Parameters.• Section 6—Services, Chapter 2—“SDH Services,” Configure Advanced

Parameters (Alphabetic Order).

Click Done to return to the Create Service Groups tab on the main screen.

Service Group Tab

Click the Service Group tab to display the list of configured Service Groups.

Figure 6-28 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.

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-29 Edit Service Group Tab


TransNav GUI Guide, Section 6: ServicesEdit Service Group Tab

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 and the single quote character only. Do not use any other punctuation or special characters.


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.


SECTION 6 SERVICES

Chapter 6 Managing Services

Introduction This chapter includes the following topics:• Service Tab• Service Availability Status Audit• Service Shortcut Menu• Working with the Service List• Setting Service Filters• Search for Services

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 and identify the availability status of each service by status and by color.

Figure 6-30 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.


TransNav GUI Guide, Section 6: ServicesService Tab

Source, Destination: Displays the source or destination service endpoint in one of the following formats:

Format 1:NodeID/slot#Example: Node1/s-11

Format 2: NodeID/slot#/port#(portType)Example: Node1/s-11/p-1 Example: Node1/s-11/eos-1 Example: Node1/s-11/eop-1

Format 3:NodeID/slot#/port#/sts#Example: Node1/s-11 /p-1/sts-1

Format 4:NodeID/slot#/port#/sts#/vtg#/vt#Example: Node1/s-11 /p-1/sts-1/vtg-1/vt-1

For SONET-STS services with an Ethernet card as the source, the port number is zero (p0). This port refers to the virtual OC-48 interface on the backplane.

Type: Displays the type of service.• DS1: At least one DS1 port is an endpoint for the service.• DS1-Mux: One DS1 card is an endpoint for the service. The DS1 card is mapped

into VT.• DS1-Mux-DS3: One DS1 card is an endpoint for the service. The DS1 card is

multiplexed into DS3.• DS3-CC: One DS3CC port is an endpoint for the service.• DS3-Tmx: One DS3TMX port is an endpoint for the service.• E1: One E1 port is an endpoint for the service.• E1-Mux: One E1 card is an endpoint for the service.• E3-CC: One E3-CC card endpoint for the service.• Ethernet: Is one of the supported Ethernet service types.• SDH-VC11: One of the endpoints is an STM port.• SDH-VC12: One of the endpoints is an STM port.• SDH-VC3: One of the endpoints is an STM port.• SDH-VC3-Endpoint: One of the endpoints is an STM port.• SDH-VC3-Tunnel: One of the VC3 tunnel endpoints is an STM port.• SDH-VC4: One of the endpoints is an STM port.• SDH-VC4-Endpoint: One of the endpoints is an STM port.• SDH-VC4-Tunnel: One of the VC4 tunnel endpoints is an STM port.• SONET-STS: One of the endpoints is an OC or EC1 port.• SONET-Tunnel: One of the SONET tunnel endpoints is an OC port.• SONET-VT1.5: One of the endpoints is an OC port.


Chapter 6 Managing ServicesService Tab

• VC-Bundle: A VC-bundle service.• VC-Mux: One of the endpoints is an STM port.• VT-Mux: One of the endpoints is an OCR or EC1 port.• Unknown: One of the endpoints is of unknown origin.

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.

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.

Adm. State: Indicates the administrative state of the service. Select one of the following states:• Lock: Alarms on the service CTPs are suppressed. Availability Status processing is

suppressed. The Availability Status will always be Normal. • Unlock (default): Alarms on the service CTPs are not suppressed. Availability

Status processing is enabled. The Availability Status will be set to Normal, Degraded, or Failed as appropriate.

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-5 Possible Service States in Response to User Actions

User Action/Event Possible Service States

Provision service Provisioned

Activate Act. (Activation) In ProgressAct. (Activation) FailedActivated

Deactivate Deact. (Deactivation) In ProgressDeact. (Deactivation) Failed

Abort Abort In ProgressAbort Failed

Delete Del. (Deletion) In Progress

Node restart Pump Up In ProgressPump Up Failed


TransNav GUI Guide, Section 6: ServicesService Tab

Avail. Status (server GUI and server CLI only): Displays the failure status of services based on ITU-T X.731. Values are normal, degraded, and failed. Each value is color-coded as indicated:

normal: white backgrounddegraded: yellow backgroundfailed: red background

Note: Currently, the values of failed and degraded only display for services with all endpoints along the service path in this release (TR3.2.3) and only for the following services and service types:

– hop-by-hop services – end-to-end services– all Ethernet service types – the following SONET service types: DS1, DS1-MUX, DS3-CC, DS3-TMX,

VT1.5, and STSServices with endpoints on nodes with previous Traverse software releases will always have an Availability Status value of normal.For information on how the Alarm status (locked or unlocked) affects the availabiity status, see the description for Adm State above.For SONET and SDH protected services: – the degraded availability status indicates one or more SA alarms exist on

either of the services’ endpoints on the protection path. – the failed availability status indicates one or more service affecting (SA)

alarms exist on either of the services’ endpoints on the active working path. For Ethernet services: – the failed availability status displays on the service. The status indicates one or

more service affecting (SA) alarms exist on equipment supporting the service.– The degraded availability status displays on a service to indicate one or more

service affecting (SA) alarms exist:• on a service’s Ethernet port endpoint when the Ethernet port is not part of a

LAG • on the service’s LAG port endpoint, EOS port, or EOP port

Customer: Displays the customer name.

Description: Displays the description of the service.


Options: Set filters for services to be displayed. Displays the Service List Filters screen. See Setting Service Filters.

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.


Chapter 6 Managing ServicesService Shortcut Menu

Service Availability Status Audit

The service availability of each service in the network can be audited using the Service Availability Service Audit command from either the Admin menu on the management system GUI or the server CLI. When invoked, the Service Availability Service Audit audits the service availability status of each service in the network and corrects it if there are any errors. An event is added to the event log to show when the command was started and when it has completed.

This audit is similar to the Alarm Synchronization audit that can be performed on a node; both audits can be used in conjunction with each other. For more information about auditing alarms, see Section 8—Maintenance and Testing, Chapter 2—“Alarms,” Auditing the Alarms.

Service Shortcut Menu

Use the menu commands to perform actions on any provisioned service. To display the service menu, right-click the selected service in the service list:

Figure 6-31 Service Menu

You can execute the following commands from the service shortcut menu.

Show TxRx Path. Click this command to view both the active and standby paths in the transmit and receive directions. See Chapter 7—“Managing Service Paths.”

Show RSTP Port Info: Click this command to view information about the RSTP port.

Show Last Error. Click this command to show the last error the service encountered.

Tunnel: Select to display the available commands to perform on the service tunnel.Show Tunnel Constraints: Show the tunnel constraints on the selected low order service. Show Tunneled Services: Show all low-order services currently carried on the tunnel.

Activation: Select to display the available commands to perform on the service. Activate: Activate the selected service to start carrying traffic. Deactivate: Stop the selected service from carrying traffic.Abort: Abort in-progress service activation, deactivation, or deletion.

Admin State: Select to change the administrative state of the service.Lock: Suppress service CTP alarms and availabiity status processing.Unlock: Enable service CTP alarms and availabiity status processing.


TransNav GUI Guide, Section 6: ServicesWorking with the Service List

Bridge and Roll: Select the command to perform on the service. 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 TransNav Provisioning Guide, Section 2—Creating Service Applications, Chapter 2—“Bridging and Rolling Services”, 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.

Copy: Copy the selected 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 a range of services. Hold the Shift key down, then click specific services to select them. You can now activate, deactivate, or delete the selected group of services.

Filtering Services

Sort and view the services using the Options button. See Setting Service Filters.


Chapter 6 Managing ServicesService Filters, Type Tab

Setting Service Filters

There are two methods that can be used to filter services. The first is by selecting Options on the Service tab. This method filters the services displayed on the first page of the Service tab. The second method the service list search filter described in Search for Services. This method filters all of the services displayed on the Service tab.

You can control which services are displayed in the service list on the Service tab by setting filters. Set the filters by clicking Options on the Service tab.• Service Filters, Type Tab• Service Filters, Node Tab• Service Filters, Source Tab• Service Filters, Destination Tab• Service Filters, Customer Tab

Service Filters, Type Tab

From the Service tab, click Options. The Type tab displays allowing you to include or exclude specific service types from appearing in the service list on the Service tab.

Figure 6-32 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 type 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.


• Cancel: Do not save any configuration changes.

• Apply: Apply these service types to the filter.

• Done: Close the screen.

Active check box


TransNav GUI Guide, Section 6: ServicesService Filters, Node Tab

Service Filters, Node Tab

From the Service tab, click Options. Click the Node tab to display services on specific nodes.

Figure 6-33 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 Add>> to move it to the right box.

To remove a service 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.



• Apply: Apply these nodes to the filter.

• Done: Save the changes and close the screen.


Chapter 6 Managing ServicesService 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-34 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 Add>> 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.






TransNav GUI Guide, Section 6: ServicesService 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-35 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 destination node, click the node in the left box and click Add>> to move it to the right box.

To remove a service with a specific destination 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.






Chapter 6 Managing ServicesService 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-36 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 name in the left box and click Add>> to move it to the right box. Click Apply.


• Cancel: Do not save any configuration changes.• Apply: Apply these customers to the filter.• Done: Close the screen.


TransNav GUI Guide, Section 6: ServicesSearch for Services

Search for Services

Use the following procedure to search for specific services in the Traverse system.

Note: The use of wildcards (*) in the search filters is important to narrow the range of returned search values that include alphanumeric descriptions. For example, a wildcard search on *c*r* returns search results that include car, card, and accord.

Table 6-6 Search for Services

Step Procedure

1 Review the information in the topic Before You Begin.

2 From Map View or Shelf View, click the Service tab.

Figure 6-37 Select the Service Tab

3 Select the type of filter to be used as the first priority in the search and enter the appropriate search text (i.e., service identifier number, service name, etc.). The text is case-sensitive. Wildcards can be used where indicated for the following values.• ID: The alphanumeric service identifier assigned by the system in the

following format. Use wildcards (*) to search for specific identifiers. <Node name> <Unique service identification number for that node>

• Name: The alphanumeric name of the service. Use wildcards (*) to search for specific service names.

• Source: The alphanumeric source service endpoint in the following format. Use wildcards (*) to narrow your search for specific endpoints. NodeID / slot<Number><cardType> / port<Number><portType> / sts<Number>/ vtg<Number> / vt<Number>

For SONET-STS services with an Ethernet card as the source the port number is zero (p-0). This refers to the OC-48 interface on the backplane.


Chapter 6 Managing ServicesSearch for Services

• Destination: The alphanumeric destination service endpoint in the following format. Use wildcards (*) to narrow your search for specific destination endpoints. NodeID / slot-<Number><cardType> / port-<Number><portType> / sts-<Number> / vtg-<Number> / vt-<Number>

• Type: Select the type of service.• Operation State: The operative state of the service. Enabled indicates

the service is activated and is capable of carrying traffic. Disabled indicates the service is not activated.

• Admin State: The administrative state of the service. Valid values are Locked (the service is not activated to carry traffic) or Unlocked (the service is activated to carry traffic).

• Service State: The service state of the service. Valid values are:– Provision service– Activate– Deactivate– Abort– Delete– Node restart

• Availability Status: Indicates the failure status of the service as defined in ITU-T X.731. Valid values are Normal, Degraded, and Failed. The default is Normal.

Note: Only services created on nodes running Release TR3.2.3 or later will display as Degraded or Failed.

• Customer: The alphanumeric customer name. Use wildcards (*) to narrow your search for specific customers.

• Description: The alphanumeric description of the service. Use wildcards (*) to narrow your search for specific descriptions.

4 Select the type of filter for the Second search priority. The selected value must be different than the filter type selected in the First field. Enter the appropriate search text (i.e, service identifier number, service name, etc.). The text is case-sensitive.

Table 6-6 Search for Services (continued)

Step Procedure


TransNav GUI Guide, Section 6: ServicesSearch for Services

5 Click Search to begin the search.

Note: If a search is made and information changes, the Search button changes to Refresh and flashes on and off. Click Refresh to display the updated information and return to the first display page.

Note: If no text is entered for the First or Second filter selections, a complete list matching the selected filter types displays. For example, if the First filter selected is Name and the Second filter selected is Destination, when Search is clicked a complete list of the service names at the destination point displays.

6 Each page displays 100 services. If more than 100 services exist, use the Page button at the bottom of the screen to quickly move through the displayed information.

7 The Search for Services procedure is complete.

Table 6-6 Search for Services (continued)

Step Procedure


SECTION 6SERVICES

Chapter 7 Managing Service Paths

Introduction This chapter describes the following topics:• Showing TxRx Paths

– Viewing Service Alarms– Viewing Service Details– Assigning or Suppressing Alarms to Path Endpoints

• Retrieving Service Performance Data• Protection Switching Path-Protected Services

Showing TxRx Paths

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.

Figure 6-38 Path Display for Service Dialog Box

The Path Display for Service dialog box displays the following information:• Transmit and Receive Paths for Services• Refresh Status of Service

Context-sensitive tabs

Receive path

Transmit path

Refresh status


TransNav GUI Guide, Section 6: ServicesTransmit and Receive Paths for Services

• Service alarms, configuration, performance, and protection switching information on context-sensitive tabs– Viewing Service Alarms– Viewing Service Details– Assigning or Suppressing Alarms to Path Endpoints– Retrieving Service Performance Data– Protection Switching Path-Protected Services

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.


Chapter 7 Managing Service PathsViewing Service Alarms

Refresh Status of Service

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 minCommand 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.

Viewing Service Alarms

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.

Figure 6-39 Alarm Tab on Path Display for Service Screen

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” for a complete description of the Alarm tab.

Alarm tab


TransNav GUI Guide, Section 6: ServicesViewing Service Details

Viewing Service 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.

Figure 6-40 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 (connection termination point): Indicates the endpoint of the service.

VCX Card Used: The 5G VT/TU card 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 service and select Show TxRx Paths. The Path Display for Service dialog box displays. Click the CTP tab.

Figure 6-41 CTP Tab on Path Display for Service Dialog Box

Details tab

CTP tab


Chapter 7 Managing Service PathsAssigning or Suppressing Alarms to Path Endpoints

Click an endpoint in the Active Hop column. The CTP tab in the Path Display for Service dialog box allows you to view or provision the following fields:

Endpoint: Indicates the selected endpoint in the Active Hop column.

Alarm Profile: Assign an alarm profile to the endpoint. Select one of the following:• useParent: The endpoint inherits the alarm profile of the parent 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

For more information, see the Operations and Maintenance Guide, Section 1—Fault Management, Chapter 1—“Managing Alarms and Events”.

Click the CTP Status tab to view information about the status of the CTP.

Figure 6-42 CTP Status Dialog Box, Path Overhead Tab

Received/Transmitted Path Overhead Tab: 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 CTP Status Dialog Box, Automatic In Service Tab


TransNav GUI Guide, Section 6: ServicesAssigning or Suppressing Alarms to Path Endpoints

Automatic In Service Tab: Click to review the Automatic In Service status of the selected active hop. If enabled, alarms and performance monitoring reports will be automatically suppressed for the time remaining. (The timer value is set at the node level.) Locking the service restarts the timer.

Note: If the CTP is on a DS1-MUX, DS3-TMX, STS1-TMX or VT-MUX service, only the STS endpoint values display. Each STS endpoint has 28 VT1.5 endpoints associated with it which do not display. If the timer on any single VT1.5 endpoint reaches 0, the service will unlock, however, the STS endpoint status remains enabled indicating it should still be locked which is misleading. Unlock the service to see the VT1.5 endpoints with alarms.

Note: The Automatic in Service feature is not available on unidirectional services that originate on non-optical cards, such as DS-3. End-to-end services are unlocked at the source node. Because optical alarm monitoring is not performed on the source node for Ethernet and electrical cards, the services will never unlock by themselves.

The command buttons are as follows:• Refresh: Refresh the screen with the most recent data.• Close: Close the dialog box and return to the Path Display for Service screen.

Click the lock icon next to “Alarm Suppression” to enable or suppress alarms:• Unlocked: The endpoint is unlocked and alarms are enabled. • Locked: The endpoint is locked and alarms are 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.• Close: Close the Path Display for Service dialog box and return to the main

screen.


Chapter 7 Managing Service PathsRetrieving 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.

Note: The eop_pm and ethernet_eopdh_eq_pm templates are not supported on this feature.

Click a row in the Active Hop column at the top of the screen, then click Refresh to view the performance monitoring data for that hop. (For protected services, click a row in the Standby Hop column.)

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.


TransNav GUI Guide, Section 6: ServicesRetrieving Service Performance Data

The performance monitoring data is presented in table format with the following column headings:

Counter: Displays performance monitoring data for each service endpoint 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. • 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 previous dialog box.


Chapter 7 Managing Service PathsProtection Switching Path-Protected Services

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.

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 the Active Hop column2. On the Switch tab, select a path.3. From the Command parameter 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.


TransNav GUI Guide, Section 6: ServicesProtection Switching Path-Protected Services

– 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.


SECTION 7 DCS APPLICATIONS

Contents

Chapter 1DCS-384 Matrix Shelf

DCS-384 Matrix Shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2What is an MSAID?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3MSAID Formats. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3Commissioned Hardware Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4Protection Groups on a DCS-384 Matrix Shelf . . . . . . . . . . . . . . . . . . . . . . . . 7-5DCS-384 MSAID Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6DCS-384 MSAID Allocation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7DCS-384 Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-9Endpoints for DSC-384 Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-10Advanced Parameters (Alphabetic Order) . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-11DCS-384 Fragmentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-15DCS Service Search, Filter, Scroll and Sort Functions . . . . . . . . . . . . . . . . . . 7-16

Search and Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-16Page Scrolling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-17Sorting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-17

Chapter 2DCS-IO Shelf

DCS-IO Shelf. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-20DCS-IO MSAID Allocation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-21DCS-IO MSAID Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-22DCS-IO Assignment Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-24

Chapter 3DCS-96 Shelf

DCS-96 Shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-27DCS-96 Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-28DCS Assignment Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-29DCS-96 Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-30EndPoints for DSC-96 Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-32Advanced Parameters (Alphabetic Order) . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-33


TransNav GUI Guide Section 7 DCS Applications


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 from one to four DCS-IO shelves.

This chapter explains the configuration and following topics for DCS-384 matrix shelf:• DCS-384 Matrix Shelf, page 7-4• What is an MSAID?, page 7-5• MSAID Formats, page 7-5• Commissioned Hardware Configuration, page 7-6• Protection Groups on a DCS-384 Matrix Shelf, page 7-7• DCS-384 MSAID Assignments, page 7-8• DCS-384 MSAID Allocation, page 7-9• DCS-384 Services, page 7-11• Endpoints for DSC-384 Services, page 7-12• Advanced Parameters (Alphabetic Order), page 7-13• DCS-384 Fragmentation, page 7-17• DCS Service Search, Filter, Scroll and Sort Functions, page 7-18


TransNav GUI Guide, Section 7: DCS ApplicationsDCS-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 provide 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

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.

Node1 (DCS-384)

5G

VT

SW

W

5G

VT

SW

W

5G

VT

SW

W

5G

VT

SW

W

5G

VT

SW

W

2P

OC48

2P

OC48

5G

VT

SW

P

5G

VT

SW

W

5G

VT

SW

W

5G

VT

SW

W

5G

VT

SW

W1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20

GCM

GCM

2P

OC48

2P

OC48

2P

OC48

2P

OC48

2P

OC48

2P

OC48

DCS-IO shelves


Chapter 1 DCS-384 Matrix ShelfMSAID 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. Force10 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-Seq MSAID-VT-GR253 MSAID-VTG-VT

Payload Mapping

Payload Mapping

User Interface

User Interface User Interface

1 VTG1, VT1 VTG1, VT1 seq#1 gr253#1 VTG1, VT1




















TransNav GUI Guide, Section 7: DCS ApplicationsCommissioned Hardware Configuration

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.










Table 7-1 MSAID Formats

DS1 Channel

MSAID-VT-Seq MSAID-VT-GR253 MSAID-VTG-VT

Payload Mapping

Payload Mapping

User Interface

User Interface User Interface


Chapter 1 DCS-384 Matrix ShelfProtection 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.

Note: Protection groups 1 through 8 cannot be deleted.

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








PG13 1 for N equipment slots 1, 2, 3, 4, 5, 6, 7, 8, 9 slot 10


TransNav GUI Guide, Section 7: DCS ApplicationsDCS-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 move 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 16, port 1 sts-1, sts-2, sts-3, .. .sts-48 241, 242, 243, ... 288




Chapter 1 DCS-384 Matrix ShelfDCS-384 MSAID Allocation


Details: Select an endpoint on the Assignment subtab screen and click Details 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.

Click Show Tx/Rx Path to show the path display for service screen.

Click Apply to apply the changes or click Cancel to cancel the changes and return the the previous screen.

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. The MSAIDs are allocated for use with DSC services that are created using the DCS Services subtab.

Figure 7-6 DCS-384 MSAID Allocation


TransNav GUI Guide, Section 7: DCS ApplicationsDCS-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 nodeslot is the number of the slot in which the card is insertedport is the number of the port on the cardPortType is the speed of the SONET interfacea (allocated) represents that the port is already allocated to a resourcep (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 ]


Chapter 1 DCS-384 Matrix ShelfDCS-384 Services

DCS-384 Services

Click the DCS tab, then click the Services subtab.

Note: Corresponding MSAIDs are allocated for DCS services that are created using the DCS Services subtab. DCS services can be created using the Services tab, however, the corresponding allocated MSAID are not available for assignment.

Figure 7-7 DCS Tab, Services Subtab

From the DCS Services subtab, click Add. The Creating SONET Service dialog box displays.

.

Figure 7-8 Creating SONET Service Dialog Box

Use this screen to create hop-by-hop DCS services (switching one MSAID to another).



Bandwidth: Select the total bandwidth for the service: • VT1.5 (default)• STS-1

Strict: Not applicable for DCS services.


TransNav GUI Guide, Section 7: DCS ApplicationsEndpoints for DSC-384 Services


Endpoint: Select the endpoints of the service. See Endpoints for DSC-384 Services, page 7-12.

Protection: Click this field to open the Protection dialog box. Select a valid protection type for a SONET service on a DCS-384 matrix shelf. Valid types are:• Unprotected: default protection of 1+1 APS• 1+1 Path Protected: only to VT1.5 services.

Note: If another protection group type is selected (Any, Full, UPSR Ingress), the service may fail to activate.

If 1+1 Path Protected is selected, click the 1+1 Path Protected tab. Set the Hold Off Timer value. This allows line protection to switch first before the path switches.

Command buttons are as follows:• Advanced: Configure the characteristics of the connection. See Advanced

Parameters (Alphabetic Order), page 7-13.• 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 Creating SONET Service screen, click a row in the EndPoint column of the endpoint table.

Figure 7-9 Selecting Endpoints for DCS-384 Services

The Choose an EndPoint dialog box displays. 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 and close the dialog box.


Chapter 1 DCS-384 Matrix ShelfAdvanced Parameters (Alphabetic Order)

Advanced Parameters (Alphabetic Order)

On the Creating SONET Service dialog box, click the Advanced button.The Advanced Parameters dialog box displays. A sample screen is shown below. The parameters that appear on the dialog box depend on the type of service being configured.

.












TransNav GUI Guide, Section 7: DCS ApplicationsAdvanced Parameters (Alphabetic Order)















Chapter 1 DCS-384 Matrix ShelfAdvanced Parameters (Alphabetic Order)













TransNav GUI Guide, Section 7: DCS ApplicationsAdvanced Parameters (Alphabetic Order)















Chapter 1 DCS-384 Matrix ShelfDCS-384 Fragmentation

DCS-384 Fragmentation

In Shelf View for a DCS-384 matrix shelf, click the DCS tab, then click the Fragmentation subtab. The Fragmentation screen displays.

Figure 7-11 DCS Tab, Fragmentation Subtab

To display data, click Refresh. The following information displays:

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. Force10recommends performing a defragmentation operation at a threshold of 80%.

Defragmentation State: Displays the state of the defragmentation process on the card. Valid values are: • None: No defragmentation has been performed. • In Progress: Indicates when the defragmentation operation is being performed. • Complete: The defragmentation operation is complete.• Failed: Indicates the defragmentation operation failed for the selected card.

The date and time of the last time a refresh was performed displays at the bottom of the screen.


TransNav GUI Guide, Section 7: DCS ApplicationsDCS Service Search, Filter, Scroll and Sort Functions


Refresh: Click to refresh the screen with the latest data from the node.

Defragment: Select a slot number from the drop down menu at the right of the Defragment button, then click Defragment to start a defragment operation on a card.

Figure 7-12 DCS Tab, Fragmentation Subtab, Refreshed

DCS Service Search, Filter, Scroll and Sort Functions

Search and Filter

The TransNav system provides a service Search function with a First and Second filter parameter options and values with the same character set as that of the specific option chosen and wild card character capability (i.e., the asterisk * character).

Important: The search filter is based on an AND operator condition of the First and Second parameter values. The search result is also dependent on filter criteria set in the Service > Options > Service Lists Filter screen.

For example, the First parameter filter is based on the DCS service Source endpoint identifier and uses the wildcard capability. The Second parameter filter is based on the service name.

Figure 7-13 Service Filter Search


Chapter 1 DCS-384 Matrix ShelfDCS Service Search, Filter, Scroll and Sort Functions

Page Scrolling

The TransNav system provides a page navigation drop-down list and a services page screen scrolling function with page scrolling icons. The number of services per page is set by the general system Admin > Options > Service List parameter (see Section 2—Administrative Tasks, Chapter 4—“TransNav User Preferences,” Customize System Options)

Figure 7-14 Service Page Navigation Drop-down List

Figure 7-15 Scrolling Services Page Screen Buttons

Sorting

The TransNav system provides a services table column support using display indicators. The up arrow is for ascending results, and the down arrow is for descending results, or no arrow visible to indicate that no specific sort type is in use.

Note: While the column sort is in progress, an hour-glass icon is shown.

Figure 7-16 Column Sort Icon


TransNav GUI Guide, Section 7: DCS ApplicationsDCS Service Search, Filter, Scroll and Sort Functions


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-22• DCS-IO MSAID Allocation, page 7-23• DCS-IO MSAID Assignments, page 7-24• DCS-IO Assignment Details, page 7-26


TransNav GUI Guide, Section 7: DCS ApplicationsDCS-IO Shelf

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-17 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.

28P

DS1

W

28P

DS1

P

28P

DS1

W

28P

DS1

W

28P

DS1

P

2P

OC48

8P

OC3

8P

OC3

12P

DS3TMX

W

12P

DS3TMX

P

12P

DS3TMX

W

12P

DS3TMX

W

12P

DS3TMX

P

12P

DS3TMX

W

28P

DS1

W

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20

GCM+OC12

GCM+OC12

2P

OC48

Node2 (DCS-IO)OC-12 UPSR

DCS-384Matrix Shelf


Chapter 2 DCS-IO ShelfDCS-IO MSAID Allocation

DCS-IO MSAID Allocation

It is important to understand 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-9 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

For example, connect the OC-48 interfaces in slots 17 and 18 on the DCS-IO shelf 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 a row in the Port column to display the Choose a Port dialog box. Select working port. 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 nodeslot is the number of the slot in which the card is insertedport is the number of the port on the cardPortType is the speed of the SONET interfacea (active) represents the traffic on that port is receiving traffic from the working trafficp (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-9 for a detailed description of MSAID ranges on the DCS-384 matrix shelf.


TransNav GUI Guide, Section 7: DCS ApplicationsDCS-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.


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-18 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-23.

State: Displays the status of the assignment.

Description. Displays a user-defined alphanumeric character string to describe the assignments in the DCS application.


Chapter 2 DCS-IO ShelfDCS-IO MSAID Assignments


(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 TransNav Provisioning Guide, Section 2—Creating Service Applications, Chapter 2—“Bridging and Rolling Services” 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 DCS-IO Assignment Details, page 7-26.

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.


TransNav GUI Guide, Section 7: DCS ApplicationsDCS-IO Assignment Details

DCS-IO Assignment Details

On the DCS tab, Assignment subtab, click Add. The Assignment Details dialog box displays.

Figure 7-19 Choose an Endpoint and Assignment Details Dialog Boxes

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-23. 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.


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 TransNav Provisioning Guide, Section 2—Creating Service Applications, Chapter 2—“Bridging and Rolling Services” for detailed procedures on bridging and rolling services. for detailed procedures on bridging and rolling services.


Chapter 2 DCS-IO ShelfDCS-IO Assignment Details


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 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).


TransNav GUI Guide, Section 7: DCS ApplicationsDCS-IO Assignment Details


SECTION 7: DCS APPLICATIONS

Chapter 3 DCS-96 Shelf

Introduction This chapter explains the following topics for DCS-96 shelf:• DCS-96 Shelf, page 7-29• DCS-96 Assignments, page 7-30• DCS Assignment Details, page 7-31• DCS-96 Services, page 7-32• Advanced Parameters (Alphabetic Order), page 7-35

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-20 Single-Shelf DCS-96 Application

28P

DS1

W

28P

DS1

P

28P

DS1

W

28P

DS1

W

28P

DS1

P

5G

VT

SW

5G

VT

SW

8P

OC3

8P

OC3

12P

DS3TMX

W

12P

DS3TMX

P

12P

DS3TMX

W

12P

DS3TMX

W

12P

DS3TMX

P

12P

DS3TMX

W

28P

DS1

W

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20

GCM+OC12

GCM+OC12

Node1 (DCS-96)OC-12 UPSR


TransNav GUI Guide, Section 7: : DCS ApplicationsDCS-96 Assignments

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

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-21 DCS Tab, Assignments Subtab

The Assignment 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.


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-31.

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-31.


Chapter 3 DCS-96 ShelfDCS Assignment Details

DCS Assignment Details

In Shelf View, click the DCS tab to display the Assignment subtab, then click Add to add MSAID assignments to this DCS-96 shelf. The Assignment Details dialog box displays.

Figure 7-22 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.


Show TxRx Path: Click Show TxRx Path to display the Path Display for Service screen. See Section 6—Services, Chapter 7—“Managing Service Paths,” page 6-63 for information on this screen.

Apply: Click to save your changes and return to the Assignment subtab on the main screen.

Cancel: Click to cancel any changes and return to the Assignment subtab on the main screen.


TransNav GUI Guide, Section 7: : DCS ApplicationsDCS-96 Services

DCS-96 Services

Click the DCS tab, then click the Services subtab.

Figure 7-23 DCS Tab, Services Subtab

From the DCS Services subtab, click Add. The Creating SONET Service dialog box displays.

Figure 7-24 Create SONET Service

Use this screen to create DCS services in a DCS-96 shelf.



Bandwidth: Select the total bandwidth for the service: • VT1.5 (default)• STS-1

Strict: (Not applicable for DCS services).


Add Customer: Click to add a Customer. For details, see Section 2—Administrative Tasks, Chapter 5—“Generating and Viewing Reports,” Adding Customer Information.


Chapter 3 DCS-96 ShelfDCS-96 Services

EndPoint Table: Select the endpoints of the service. See EndPoints for DSC-96 Services, page 7-34.

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-35.• 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.


TransNav GUI Guide, Section 7: : DCS ApplicationsEndPoints 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-25 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.


Chapter 3 DCS-96 ShelfAdvanced Parameters (Alphabetic Order)

Advanced Parameters (Alphabetic Order)

On the Create DCS Service Tab, click the Advanced button.The Advanced Parameters dialog box displays. A sample screen is shown below. The parameters that appear on the dialog box depend on the type of service being configured.

.












TransNav GUI Guide, Section 7: : DCS ApplicationsAdvanced Parameters (Alphabetic Order)















Chapter 3 DCS-96 ShelfAdvanced Parameters (Alphabetic Order)













TransNav GUI Guide, Section 7: : DCS ApplicationsAdvanced Parameters (Alphabetic Order)















SECTION 8 MAINTENANCE AND TESTING

Contents

Chapter 1Performance Monitoring

Viewing PM Data for Ports and Other Equipment . . . . . . . . . . . . . . . . . . . . . . 8-2Viewing PM Data for Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3Viewing Capacity Monitoring Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5Performance Monitoring Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5Setting Default PM Thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-6Customizing Performance Thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-7Collecting PM Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-10

Chapter 2Alarms

Alarms Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-14Alarm List on the Alarms Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-16

Change Column Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-16Sorting Alarm List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-16StickyMode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-16

Viewing Alarm Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-17Auditing the Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-18Grouping Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-19Setting Alarm Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-19Alarm Filters, Source Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-20Alarm Filters, Probable Cause Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-20Alarm Filters, Time Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-21Alarm Filters, Severity Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-21Alarm Filters, Acknowledged By . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-22Viewing Existing Alarm Profiles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-23Creating New Alarm Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-24Sorting Alarm Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-26Saving and Importing User Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-26

Chapter 3Events

Event Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-30Provisioning events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-30Performance events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-30Security events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-30Normal operational events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-30Fault events (alarms). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-30

Event Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-30


TransNav GUI Guide Section 8 Maintenance and Testing

Events Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-32Event List on the Events Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-33

Changing Column Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-33Sorting Events List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-33

Changing Event Retrieval Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-34Viewing Event Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-35Grouping Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-36Setting Event Filters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-37Event Filters, Source Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-37Event Filters, Probable Cause Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-38Event Filters, Time Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-38Event Filters, Severity Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-39Saving and Importing User Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-39

Chapter 4Diagnostics

Facility Loopback Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-42Facility Loopback Tests on EOP Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-42Far-end Facility Loopback Tests on EOP Ports. . . . . . . . . . . . . . . . . . . . . . . . 8-43Terminal Loopback Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-43Remote Loopback Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-44Before Performing Loopback Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-44Performing Loopbacks from the Diagnostic Tab . . . . . . . . . . . . . . . . . . . . . . . 8-45Before Performing EOP Port Loopback Tests . . . . . . . . . . . . . . . . . . . . . . . . . 8-46Performing Loopbacks on EOP Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-46

Chapter 5Test Access

Test Access Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-49TAP Subtab Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-50Test Access Point List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-50TAP Configuration Area. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-51TAC Subtab Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-52Test Access Connection List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-52TAC Configuration Area. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-52

Chapter 6Software Upgrades

System Software Upgrades— Download . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-56System Software Upgrades— Activation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-57Bulk Config (Upgrade Helper) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-58Software Upgrade and Activation Shortcut Menus . . . . . . . . . . . . . . . . . . . . . 8-59


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• Viewing PM Data for Services• Viewing Capacity Monitoring Data• Performance Monitoring Templates• Setting Default PM Thresholds• Customizing Performance Thresholds• Collecting PM Data

See the Operations and Maintenance Guide for descriptions, ranges, default thresholds of performance monitoring and capacity monitoring parameters, and procedures on managing performance.


TransNav GUI Guide, Section 8: Maintenance and TestingViewing 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 200 Mux, or other external equipment) in Shelf View and then clicking the Performance tab.

Figure 8-1 DS1 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.

Counter: Displays performance monitoring registers for the entity. For descriptions of supported registers, see the Operations and Maintenance Guide, Section 2—Performance Monitoring, Chapter 1—“Managing Performance”.




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 hours, 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.


Chapter 1 Performance MonitoringViewing PM Data for Services

Command buttons are as follows:• Refresh: Refresh the Counters parameters 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.

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.

Note: The eop_pm and ethernet_eopdh_eq_pm templates are not supported on this feature.

Click a row in the Active Hop column at the top of the screen, then click Refresh to view the performance monitoring data for that hop. (For protected services, click a row in the Standby Hop column.)

Figure 8-2 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]


TransNav GUI Guide, Section 8: Maintenance and TestingViewing PM Data for Services

• 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 for each service endpoint 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.




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 previous dialog box.


Chapter 1 Performance MonitoringPerformance Monitoring Templates

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.

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.

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 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 current and previous.

3 Click Refresh to re-display updated capacity monitoring values.

Figure 8-3 Viewing VT/TU Capacity Monitoring Data

4 If you click Reset, an error message displays. The counters do not 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.


TransNav GUI Guide, Section 8: Maintenance and TestingSetting Default PM Thresholds

• To customize threshold values for performance monitoring parameters for equipment or services, see Customizing Performance Thresholds.

• 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.

To create or modify a monitoring template, see the Operations and Maintenance Guide, Section 2—Performance Monitoring, Chapter 1—“Managing Performance,” Creating or Modifying a Monitoring Template.

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-4 Performance Templates Dialog Box

On the Performance Templates 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.


Chapter 1 Performance MonitoringCustomizing Performance Thresholds

Figure 8-5 Set Default Thresholds

See the Operations and Maintenance Guide, Section 2—Performance Monitoring, Chapter 1—“Managing Performance”, 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.


TransNav GUI Guide, Section 8: Maintenance and TestingCustomizing Performance Thresholds


The PM Configuration Template dialog box appears.

Figure 8-7 Customize PM Thresholds

2a

1

3

2b 2c

4


Chapter 1 Performance MonitoringCustomizing Performance Thresholds

Figure 8-8 Customize Ethernet PM Thresholds

1. Type a unique name for the new template.2. Enter threshold values for 15-minute and 24-hour intervals. See the 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


TransNav GUI Guide, Section 8: Maintenance and TestingCollecting PM Data

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.


Click a template type and click Properties to open the selected template for editing.

See the Operations and Maintenance Guide for ranges and explanations of each parameter for each template type.

Figure 8-11 Collect PM Data


Chapter 1 Performance MonitoringCollecting PM Data

Click Collect All 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.

\


TransNav GUI Guide, Section 8: Maintenance and TestingCollecting PM Data



Chapter 2Alarms

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:• Alarms Tab• Alarm List on the Alarms Tab• Viewing Alarm Details• Auditing the Alarms• Grouping Alarms• Setting Alarm Filters• Viewing Existing Alarm Profiles• Creating New Alarm Profiles• Sorting Alarm Profiles• Saving and Importing User Preferences

See Chapter 3—“Events” for information on events.

See the Operations and Maintenance Guide, Section 1—Fault Management, Chapter 1—“Managing Alarms and Events”for a detailed list of alarms and recommended actions.


TransNav GUI Guide, Section 8: Maintenance and TestingAlarms 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-19• Grouping Alarms, page 8-21• Setting Alarm Filters, page 8-21• Viewing Existing Alarm Profiles, page 8-25

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.

If a node is reset, the time stamps on alarms that are generated after the reset occurs will display the time that the node was reset.

A port may also appear in the color of the most severe alarm existing on it. If there are no alarms associated with a port, the port icon will reflect the port LED status.


Chapter 2 AlarmsAlarms Tab

Figure 8-13 Port Icon Indicator

Port alarm

Port LED


TransNav GUI Guide, Section 8: Maintenance and TestingAlarm List on the Alarms Tab

Alarm List on the Alarms Tab

The alarm list is context-sensitive (see Alarms Tab, page 8-16): • 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.


Chapter 2 AlarmsViewing Alarm Details

If the StickyMode check box is selected, that alarm remains at the top of the list, while its severity changes from Critical to Clear.

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-14 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

Important: Force10 recommends opening a new window before selecting StickyMode so new alarms continue to be reported.


TransNav GUI Guide, Section 8: Maintenance and TestingAuditing the Alarms

• Probable Cause: Describes the probable cause of the alarm on two lines. The first line identifies the type of alarm (for example, DCCFAIL). The second line indicates if the alarm is Service Affecting or Not Service Affecting.

• Time: Time the alarm was created• Description: Description of the alarm• Severity: Severity of the alarm• Source: Source of the alarm• ServiceID: Service identification number• Acknowledged By: Name of the user who acknowledged the alarm• Annotations box: Enter annotations on the alarm• Affected Services: Identifies the availability status of the services affected by the

alarm. Each availability status type is color coded as follows: – Failed - red background– Normal - white background– Degraded - yellow background

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.• Refresh Services: Refresh the list of services affected by the alarm. • Acknowledge: Acknowledge the alarm. The acknowledgement is added to the

bottom box.• Done: Close the dialog box.

Auditing the Alarms

Perform an alarm audit from the management server to clear alarms on the node that do not exist and to raise alarms that are present but not shown. Alarm audits should also be performed when changes are made to the alarm profile settings to enable the changes to take effect. An event is added to the event log to show when this function has started and when it has completed.

This audit is similar to the Service Availability Status Audit that can be performed on a node; both audits can be used in conjunction with each other. For more information on the service availability status audit, see Section 6—Services, Chapter 6—“Managing Services,” Service Availability Status Audit.

To perform the audit, right-click a node on Map View from the GUI and select Alarm Audit from the menu that displays. For more information, see Section 1—Installation and Overview, Chapter 3—“General Description of EMS Server GUI.”


Chapter 2 AlarmsSetting Alarm Filters

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-15 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.

Setting Alarm Filters

On the Alarms tab, click Set Filters. The Alarm Filter (View Main) dialog box displays

.

Figure 8-16 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-22• Alarm Filters, Probable Cause Tab, page 8-22• Alarm Filters, Time Tab, page 8-23• Alarm Filters, Severity Tab, page 8-23• Alarm Filters, Acknowledged By, page 8-24


TransNav GUI Guide, Section 8: Maintenance and TestingAlarm Filters, Source Tab

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

This is the default tab when you click the Set Filters command button from the Alarms tab (Figure 8-16 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, type Cypress* in the Available Sources box and click the right arrow to include all alarm sources whose names begin with Cypress.

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-17 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.


Chapter 2 AlarmsAlarm Filters, Severity Tab

Alarm Filters, Time Tab

Click the Time tab to specify the time periods within which to display alarms.

Figure 8-18 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.

Alarm Filters, Severity Tab

Click the Severity tab to specify the severity of alarms you want to display.

Figure 8-19 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:


TransNav GUI Guide, Section 8: Maintenance and TestingAlarm Filters, Acknowledged By

• Critical• Major• Minor• Warning• Clear

Alarm Filters, Acknowledged By

Click the Acknowledged By tab to display alarms acknowledged by specific users.

Figure 8-20 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.


Chapter 2 AlarmsViewing 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-21 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 Operations and Maintenance Guide.• ds1_ptp: DS1 port• ds3_ptp: DS3 port• e1_ptp: E1 port• e3_ptp: E3 port• eop_ptp: Ethernet Over PDH port• eop_ctp: Ethernet Over PDH port member• eos: Ethernet Over SONET/SDH port• eos_ctp: Ethernet Over SONET/SDH port member• ethernet_ptp: Ethernet port• lag: link aggregation group• sdh_eos: SDH EOS port• sdh_eos_ctp: SDH EOS port member• sdh_hp: SDH high order path (VC4 or VC3)• sdh_lp: SDH VC3 low order path


TransNav GUI Guide, Section 8: Maintenance and TestingCreating New Alarm Profiles

• 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• 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 the Operations and Maintenance Guide, Section 1—Fault Management, Chapter 1—“Managing Alarms and Events”.

If changes are made to the settings of an alarm profile, perform an alarm audit to make the changes effective. For information on performing an alarm audit, see Auditing the Alarms.

To view the types of alarm profiles in alphabetical order, click the Type column header.

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 Operations and Maintenance Guide.

From the Admin menu, select Alarm Profiles. The Alarm Profiles dialog box displays.


Chapter 2 AlarmsCreating New Alarm Profiles

Figure 8-22 Alarm Profiles Dialog Box

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-23 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.


TransNav GUI Guide, Section 8: Maintenance and TestingSorting Alarm Profiles

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 the Operations and Maintenance Guide, Section 1—Fault Management, Chapter 1—“Managing Alarms and Events”.):• 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 the Operations and Maintenance Guide, Section 1—Fault Management, Chapter 1—“Managing Alarms and Events”.):• Critical• Major• Minor• Warning• Clear• Info

Service Affecting: Select the box to make the alarm service affecting. Clear the check box to make the alarm non-service affecting. For more information, see the Operations and Maintenance Guide, Section 1—Fault Management, Chapter 1—“Managing Alarms and Events”.

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

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 4—“TransNav User Preferences,” Saving and Importing User Preferences.


Chapter 2 AlarmsSaving and Importing User Preferences


TransNav GUI Guide, Section 8: Maintenance and TestingSaving and Importing User Preferences



Chapter 3Events

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-32• Event Logs, page 8-32• Event List on the Events Tab, page 8-35• Saving and Importing User Preferences, page 8-41

See Chapter 2—“Alarms,” page 8-15 for information on alarms.

See the Operations and Maintenance Guide for a detailed list of events and recommended actions.


TransNav GUI Guide, Section 8: Maintenance and TestingEvent Types

Event Types 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 events. The system raises an event, such as an alarm, when it first detects a fault condition. While the fault condition persists, the event is active. When the system detects that a fault condition no longer exists, it clears the even. The clearing may be automatic or a result of an operator action (e.g., replacing a bad card).

Event Logs All events (including alarm fault events) are logged on the Traverse General Control Card (GCM) or TraverseEdge 100 system card. The data from the log can be viewed using the node-level CLI or server-level CLI. 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 in the /report/output directory. This log provides easy access to information about recent events. Use the Report Scheduler to schedule a report to save the data in the Event Log.

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 log of events that occur on the node or server. If the Event Log is on the Traverse General Control Card (GCM) or TraverseEdge 100 System card, the last 300 events are logged. Events are kept for a maximum of 3 days with a maximum limit of 10,000 events possible. If the output file directory is on the TransNav server, the system automatically deletes all files after the value set in the ReportRemovalPeriod (days) parameter is reached. For more information, see the TransNav Management System Server Guide, Section 2—Management Server Procedures, Chapter 3—“Server Administration Procedures,” Setting Up Report Parameters.

Force10 recommends performing regular backups of the log files. Use the Report Scheduler to set up a regularly generated report on events. For details, see the TransNav Management System GUI Guide, Section 2—Administrative Tasks, Chapter 5—“Generating and Viewing Reports,” Generating Reports.


Chapter 3 EventsEvent Logs


TransNav GUI Guide, Section 8: Maintenance and TestingEvents 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-36• Viewing Event Details, page 8-37• Grouping Events, page 8-38• Setting Event Filters, page 8-39

Figure 8-24 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

the Wrap line in Description Column checkbox is selected in the Event Retrieval Settings (View Main) dialog box, shown in Figure 8-25.


Chapter 3 EventsEvent List on the Events Tab

Event List on the Events Tab

The event list is context-sensitive (see Events Tab, page 8-34). • 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 the Event Retrieval Settings View (Main) dialog box. See Changing Event Retrieval Settings, page 8-36.

• Refresh: Display events according to Event Retrieval Settings View (Main) dialog box (Figure 8-25).

• Detail View: View highlighted event details. Displays the Event Detail (View Main) dialog box. See Viewing Event Details, page 8-37.

• Set Filters: Set filters to display events. Displays the Event Filter (View Main) dialog box. See Setting Event Filters, page 8-39.

• New Window: Opens 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.


TransNav GUI Guide, Section 8: Maintenance and TestingChanging 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-25 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 on the Events tab, in the Desc column.

Command buttons are as follows:• Refresh Now: Retrieve events according to the settings in the dialog box.• Ok: Close the dialog box.


Chapter 3 EventsViewing 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-26 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.


TransNav GUI Guide, Section 8: Maintenance and TestingGrouping 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-27 Events Menu and Events Tab Shortcut Menu

Menu selections are as follows:• Set Filters: Displays the Event Filter (View Main) dialog box.• New Window: Opens 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 the 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: Displays events according to the Event Retrieval Settings (View Main) dialog box.


Chapter 3 EventsEvent Filters, Source Tab

Setting Event Filters

On the Events tab, click Set Filters. The Event Filter (View Main) dialog box displays.

Figure 8-28 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-39• Event Filters, Probable Cause Tab, page 8-40• Event Filters, Time Tab, page 8-40• Event Filters, Severity Tab, page 8-41

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.


TransNav GUI Guide, Section 8: Maintenance and TestingEvent 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-29 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-30 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.


Chapter 3 EventsSaving and Importing User Preferences

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.

Event Filters, Severity Tab

Click the Severity tab to specify the severity of events to display.

Figure 8-31 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


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 4—“TransNav User Preferences,” Saving and Importing User Preferences.


TransNav GUI Guide, Section 8: Maintenance and TestingSaving and Importing User Preferences



Chapter 4 Diagnostics

Introduction Perform diagnostic loopbacks to troubleshoot ports and link spans using the TransNav management system.

This chapter describes the following information:• Facility Loopback Tests• Facility Loopback Tests on EOP Ports • Terminal Loopback Tests• Remote Loopback Tests• Before Performing Loopback Tests• Performing Loopbacks from the Diagnostic Tab• Performing Loopbacks on EOP Ports

See the Operations and Maintenance Guide, Section 4—Diagnostics, Chapter 4—“Loopback Tests” for detailed procedures on performing diagnostics on the Traverse system.

WARNING! Loopback tests interrupt traffic flow; do not perform them on nodes providing service.


TransNav GUI Guide, Section 8: Maintenance and TestingFacility Loopback Tests

Facility Loopback Tests

In general, a facility loopback connects the incoming received signal to the associated transmitter in the return direction.

Figure 8-32 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 (LIU) on the card.

Note: Due to hardware limitations, DS1 alarm indication signals on DS3-TMX or STS1-TMX subports are not raised towards the far-end (network side) when any subports are in a facility loopback.

Facility Loopback Tests on EOP Ports

Facility loopback on an EOP port member occurs when a manual facility loopback is applied to the EOP member. The PDH signal, shown in red in the following diagram, sends a copy of a received PDH signal to the transmit PDH signal while continuing to forward the received PDH signal to the EOP port’s VCAT or GFP function.

Figure 8-33 EOP Port Member Facility Loopback

The system allows up to 16 concurrent facility loopback settings on any EOP port member.

Tributary card OC-N/STM-Ntransport card

LIU LIUAIS

Facility underloopback test

Test Set

NodeTN 00113

EoPDH card OC-N/STM-Ntransport card

LIUTest Set

PDHmember

OPS 00094

GFP,VCAT

EthernetSwitch

PDH payloadgenerated andconsumed here


Chapter 4 DiagnosticsTerminal Loopback Tests

Far-end Facility Loopback Tests on EOP Ports

Far-end facility loopback, also known as in-band loopback, applies only to DS1 and DS3 EOP port members. It is typically a diagnostic function initiated at a central office to observe the status of a link to a remote device by changing the state of the remote device. For this reason, the system initiates in-band loopback commands but does not respond to the command.

For instance, an operator activates a line service between an Ethernet port and an EOP port, then attaches an external Ethernet test unit. The operator then sets up the Far-end Loopback option on all members of a Traverse EOP port. Ethernet frames that egress the EOP port are GFP-encapsulated and VCAT-distributed among the EOP members. The PDH members are sent to the far-end. The Traverse system receives the PDH frames, reassembles and decapsulates them, and returns an intact copy of the original Ethernet frame to the external Ethernet test unit. The receipt of good frames at the test unit validates the EOP link.

To test a single EOP port member, the operator could remove it from its original EOP port via LCAS with no service outage, and insert the circuit to be tested into its own single-member EOP port.

Terminal Loopback Tests

In a terminal loopback, the signal that is about to be transmitted is connected to the associated incoming receiver.

Figure 8-34 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.

Tributarycard OC-N/STM-N

transport card

LIU

Facility underloopback test

Test Set

Node

Bridgedsignal

LIU


TransNav GUI Guide, Section 8: Maintenance and TestingRemote Loopback Tests

Remote Loopback Tests

Remote loopback applies only to DS3 ports. It allows network operators to initiate DS3 facility loopback on remote equipment, such as M13 multiplexers, that is connected to a DS3 port.

Figure 8-35 Remote Loopback

The Traverse system uses in-band loopback messages and procedures as defined in the ANSI.T1.107 standard document to perform the remote loopback tests on DS3 ports.

Before Performing Loopback Tests

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, select the port, click the Locked icon in the lower left corner to display the Unlocked icon, then click Apply.

Remote Equipmet Card

LIU

Facility under loopback test

LIU


Chapter 4 DiagnosticsPerforming Loopbacks from the Diagnostic Tab

Performing Loopbacks from the Diagnostic Tab

From Shelf View, click a port, then click the Diagnostic tab. The Port Diagnostic screen displays.

Note: These instructions apply for all ports except EOP ports. For instructions to perform loopbacks on EOP ports, see Performing Loopbacks on EOP Ports.

Figure 8-36 DS3-CC Port Diagnostic Tab

The Diagnostic tab allows you to view and set the following information:

Label: Displays the node name, slot number, port type, and port number.

Type: Displays the port type.



Loopback: Select the type of loopback to apply to this port.• Clear (default): Clear loopback command.• Facility: Perform a facility loopback on this port.• Remote: (DS3 cards only) Perform a loopback test on this port from a remote

location.• Terminal: Perform a terminal loopback on this port.

Loop Direction: Click to display a diagram that indicates the type of loopback selected.

Test Signal Type (for DS3 ports only): Select one of the following signal types:• Clear (default)• PRBS-15 (Pseudo random binary sequence): 215-1 PRBS• PRBS-23 (Pseudo random binary sequence): 223-1 PRBS • Fixed-24Bit: Repeating 24-bit pattern (101110111011101110111011)

Test Signal Status (for DS3-CC and DS3-TMX ports only): Click this button to display the test signal status on DS3-CC and DS3-TMX ports.

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.


TransNav GUI Guide, Section 8: Maintenance and TestingBefore Performing EOP Port Loopback Tests

Before Performing EOP Port Loopback Tests

If the facility under loopback test is a DS1 EOP port with contiguous concatenation and Line Framing set to SF, the loopback for that member cannot be set to Far-end Facility.

A facility under Facility or Far-end Facility loopback test must be changed to Clear before the type of loopback test can be changed.

Performing Loopbacks on EOP Ports

From Shelf View, click a port on an EoPDH card, then click the Ethernet tab. Next, click the EOP subtab and then Add. The Create EOP tab displays.

Note: If an EOP has already been created, select the EOP row to be edited and click Edit. The Edit EOP tab displays.

Figure 8-37 Create EOP Port Loopback Tab

The Create EOP tab allows you to view and set the following information:

Slot: Displays the slot number of this EOP port.

EOP Port Id: Displays the user-assigned ID number of this EOP port.

Description: Enter a brief description of this EOP port.

Customer: Enter or change the customer whose traffic will use this EOP port.

Tagging: Enter the tagging parameter for this EOP port. Valid values are: • Port-based • Customer-tagged • Service-tagged

Concatenation Type: Displays if this EOP port uses contiguous or virtual concatenation. Valid values are:• Virtual (Default)• Contiguous

PDH Member Type: Displays the bandwidth of the transport paths that are members of this EOP port. Valid values are:

For SONET:• DS1 • DS3


Chapter 4 DiagnosticsPerforming Loopbacks on EOP Ports

For SDH:• E1 • E3

Line Framing: Indicates the timing output of the PDH Member Type selected. Valid values are: • ESF • CBIT• Multiframe• G.832

AIS Format: Displays the Alarm Indication Signal format. Valid values are:• ONES: Unformatted all ones.• NAS: North American Standard. Indicates all C-bits are set to 0 and all X-bits are

set to 1 in a 1010... repeating sequence. A 1 follows each control bit position.

The information in the following table defines which parameters are available for each PDH Member Type.

Member PDH PM Template: Indicates the performance monitoring template used for this PDH member. Valid values are:

Table 8-2 PDH Port Parameter Availability

PDH Member Type

If LO Mapping is

If Concatenation Type is Line Framing AIS Format Loopback Types

DS1 VT15 / VC11 Virtual ESF (default) ONES (read-only)

Clear (default)FacilityFar-End FacilityContiguous ESF (default)

SF

E1 (VC-12) VT2 / VC12 Virtual Multiframe (default)

ONES (read-only)

Clear (default)Facility

Contiguous Multiframe (default)Basic

DS3 (STS-1) VT15 / VC11 Virtual CBIT (read-only)

NAS (read-only)

Clear (default)FacilityFar-End FacilityContiguous

E3 (VC-3) Virtual G.832 ONES (read-only)

Clear (default)Facility

Contiguous

PDH Member Type PDH PM Template

DS1 ds1_ptp_pm

E1 e1_ptp_pm

DS3 ds3_ptp_pm

E3 e3_ptp_pm


TransNav GUI Guide, Section 8: Maintenance and TestingPerforming Loopbacks on EOP Ports

Member#: Indicates the provisioned member number of this EOP port member.

EndPoint: Displays the endpoint for the EOP port member.

Direction: Indicates the direction the traffic travels on the EOP port member. Valid values are:• Receive• Transmit• Bidirectional

Admin State: Indicates the suppression of alarms on this EOP port member. Valid values are: • Lock• Unlock

Alarm Profile: Displays the alarm profile assigned to the EOP port member.

Loopback: Select the type of loopback to apply to this port.• Clear (default): Clear loopback command.• Facility: Perform a facility loopback on this port.• Far-End: Perform a terminal loopback on this port.

Command buttons are as follows:• VLAN Usage: Indicates the type of VLAN being used for this member service. • Queues: Click to view EOP queue status. • Status: Click to view EOP port status.• Advanced: Click to set advanced EOP port parameters. • Apply: Change the loopback status change request to the specified Loopback

parameter. • Cancel: Cancel loopback status change request and revert to Clear.



Chapter 5Test Access

Introduction (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 Operations and Maintenance Guide for complete information on the test access features.

Test Access Tab

From the Shelf View, click the Test Access tab. The Test Access Point screen displays.

Figure 8-38 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• TAC Subtab Parameters

1 (SDH network only) Test access is planned for a future release.


TransNav GUI Guide, Section 8: Maintenance and TestingTAP 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.

Figure 8-39 Test Access Point Screen

The Test Access Point screen displays. There are two parts to this screen: • Test Access Point List• TAP Configuration Area

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.

List

ConfigArea


Chapter 5 Test AccessTAP 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 other than the single quote.

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.


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.


TransNav GUI Guide, Section 8: Maintenance and TestingTAC Subtab Parameters

TAC Subtab Parameters

In Shelf View, click the Test Access tab, then click the TAC subtab. The Test Access Connection screen displays.

Figure 8-40 Test Access Connection Screen

The Test Access Connection screen allows you to view and configure the following parameters:• Test Access Connection List, page 8-54• TAC Configuration Area, page 8-54

Test Access Connection List

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-54, 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.

TAC Configuration Area

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 other than the single quote.

List

ConfigArea


Chapter 5 Test AccessTAC 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. The endpoint selection can be by DCS service name or the msaid/vtg/vt selection type.

Figure 8-41 DCS Service Name EndPoint Selection


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.


TransNav GUI Guide, Section 8: Maintenance and TestingTAC Configuration Area

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.



Chapter 6Software Upgrades

Introduction This chapter describes the following administrative functions selected through the Admin menu on the graphical user interface (GUI):• System Software Upgrades— Download• System Software Upgrades— Activation• Bulk Config (Upgrade Helper)• Software Upgrade and Activation Shortcut Menus

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, see the Operations and Maintenance Guide.

Important: To upgrade management server software, see the TransNav Management System Server Guide.


TransNav GUI Guide, Section 8: Maintenance and TestingSystem Software Upgrades— Download

System Software Upgrades— Download

Click a Traverse node in Map View. From the Admin menu, select SW Upgrade to display the SW Upgrade dialog box.

Figure 8-42 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.

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 upgradeBoth 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


Chapter 6 Software UpgradesSystem Software Upgrades— Activation

• D = software patch to build

Command buttons are as follows:• Bulk Config: Display the Bulk Config (Upgrade Helper) 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.

System Software Upgrades— Activation

Click a Traverse node in Map View. From the Admin menu, select SW Activation to display the SW Activation dialog box.

Figure 8-43 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:


TransNav GUI Guide, Section 8: Maintenance and TestingBulk Config (Upgrade Helper)

– 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: Force10 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.• Standby SW Version: Software version on standby (in the card backup partition)

for the upgrade.

Command buttons are as follows:• 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 Traverse node.

Figure 8-44 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.


Chapter 6 Software UpgradesSoftware Upgrade and Activation Shortcut Menus

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 the dialog box.

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-45 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-46 Software Activation Shortcut Menu

The shortcut menu includes:

Clear Activation Time: Clear the activation time that has been set for that card.


TransNav GUI Guide, Section 8: Maintenance and TestingSoftware Upgrade and Activation Shortcut Menus


INDEX

Numerics1+1 APS

configurationprotection, 4-25revertive, 4-24status, 4-25switch mode, 4-24WTR, 4-24

protection groupname, 4-24

protection switch commandsclear, 4-26, 4-27exercise, 4-27forced, 4-26, 4-27lockout, 4-26manual, 4-26, 4-27

protection switch priorities, 4-27switch mode, 4-24WTR, 4-24

1+1 MSPconfiguration

protection, 4-25status, 4-25switch mode, 4-24WTR, 4-24

protection switch commandsclear, 4-26, 4-27exercise, 4-27forced, 4-26, 4-27lockout, 4-26manual, 4-26, 4-27

protection switch priorities, 4-27switch mode, 4-24WTR, 4-24

1+1 optimized protectionconfiguration

ID, 4-36locked out, 4-36name, 4-36port, 4-37protection, 4-37role, 4-36status, 4-37WTR, 4-36

protection switch commandsclear, 4-38forced, 4-38lockout, 4-38

protection switch priorities, 4-381+1 path protection

configurationconcatenation, 4-30ID, 4-30name, 4-30protecting path, 4-30protecting port, 4-30working path, 4-30working port, 4-30

IDCarrier Ethernet Protection Pair, 4-33

protection switch commandsclear, 6-92forced, 6-92lockout, 6-92manual, 6-92

AAccess

groupsdefinition, 2-13node-level, 2-14rights, 2-14server-level, 2-7

rolesTE-206, 2-18

ActiveEOS port status

sink members, 5-69source members, 5-69

Addcard, 1-33, 1-36, 1-51, 1-54group, 1-30, 1-48link, 1-30, 1-48

destination, 3-16source, 3-15

node, 1-30, 1-48TE-50, 5-79TransAccess 200 Mux, 5-73

Admin menupoll interval

TE-50, 5-81TransAccess 200 Mux, 5-75

synch intervalTE-50, 5-81TransAccess 200 Mux, 5-75

Release TN4.2.3 Force10 Networks Index-1

Index

Administrativestate, 6-89

BITS timing, 3-26, 6-89card or port, 5-4EOS port, 5-64

Advanced parametersEOS port, 5-65Ethernet port, 5-58

Advertise1000M Full Duplex

GBE, 5-59GBETX, 5-60

1000M Half DuplexGBE, 5-59GBETX, 5-60

100M Full DuplexETH100TX, 5-59

100M Half DuplexETH100TX, 5-59

10M Full DuplexETH100TX, 5-59

10M Half DuplexETH100TX, 5-59

GBERX PAUSE, 5-60TX PAUSE, 5-60

pauseETH100TX, 5-59RX GBE, 5-59TX GBE, 5-59

AISformat

DS3 port, 5-14DS3TMX port, 5-16STS1TMX port, 5-16

insertionDS1 port, 5-11E1 port, 5-37

maskDS1 port, 5-11DS3 port, 5-13DS3TMX port, 5-16E1 port, 5-36E3 port, 5-39EC1 port, 5-19SONET port, 5-23STM port, 5-41STS1TMX port, 5-16

Alarmprofile

node parameter, 3-6Alarms

acknowledge, 8-20, 8-21

annotations, 8-20categories, 8-30change service-affecting, 8-27colors displayed, 8-17column order, 8-18configuration

environmental, 3-8external, 3-8

definitions, 8-16detail view, 8-19, 8-21generate

suppress, 5-65grouping, 8-20menu, 1-39, 1-57new window, 8-19, 8-21node group, 1-28, 1-46path endpoints

profile, 6-88suppression, 6-88

profilecreating, 8-24DS1 port, 5-11, 8-24DS3 port, 5-14, 8-24DS3TMX port, 5-16DS3TMX subport, 5-18E1 port, 5-37, 8-24E3 port, 5-39, 8-24EC1 port, 5-21EOS port, 5-65EOS port, advanced parameters, 5-65EOS port, SDH, 8-24EOS port, SONET, 8-24Ethernet port, 5-55, 8-24LAG, 8-24SDH port, 8-24server, 8-24SFP port, 5-28, 5-46, 5-56shelf, 8-24SONET port, 5-26, 8-24SONET STS, 8-24SONET VT, 8-24STM port, 5-44STS1TMX port, 5-16STS1TMX subport, 5-18synchronization, 8-25TE-50, 5-83TransAccess 200 Mux, 5-77, 8-25UTMX subport, 5-18XFP port, 5-28, 5-46, 5-56

reporting, 8-30hierarchy, 8-16

set filters, 8-19, 8-20, 8-21settings, 8-27, 8-38

Index-2 Force10 Networks Release TN4.2.3

Index

remote alarms, 3-7save and import, 2-22

severitychanging, 8-26levels, 8-17

sorting, 8-18, 8-25, 8-27StickyMode, 8-18tab

description, 8-17map view, 1-29, 1-47shelf view, 1-32, 1-50

types, 8-30view, 8-16

Alternate VLAN ethertypesee Ethernet

Apply LCASEOS port advanced

Hold Off, 5-65WTR, 5-65

Auto-discoverydelete link, 3-18nodes, 3-3pre-provisioned nodes, 3-11TE-206, 2-18

Automatic laser shutdownsee also Ethernet

Auto-negotiationEthernet port, 5-53parameters

Ethernet port, 5-59Available bandwidth

linkview, 3-17

BB3ZS

DS3 portline coding, 5-14

Backgroundchange map, 1-30, 1-48images

customizing, 2-21Backplane

IP addresscreate node, 3-6

Backupsconfiguration files, 2-33database

multiple servers, 2-33failure

generated log file, 2-33Bandwidth, 6-21, 6-33

profile, 6-50

configuration, 6-51parameters, 6-50

BITS timingadministrative state, 3-26clock quality, 3-23config tab, 3-24force switch command, 3-31, 3-32line build out, 3-25lockout switch command, 3-31, 3-32manual switch command, 3-31, 3-32

BLSR ringconfiguration

card type, 4-4east port, 4-5name, 4-4node, 4-4node ID, 4-4protection, east port, 4-5protection, west port, 4-5revertive, 4-4ring ID, 4-4status, east port, 4-5status, west port, 4-5west port, 4-4WTR, 4-4

delete, 4-14edit, 4-14protection switch commands

clear, 4-7forced, 4-7lockout, 4-7manual, 4-7

protection switch priorities, 4-7remove node, 4-6squelch table, 4-6synchronize, 4-5, 4-14

Bridge and rollMSAID assignment details

DCS, 7-24service, 6-25, 6-38, 7-13, 7-32

Bundle, see VC-bundle

CCAC, see Connection admission controlCapacity monitoring

intervals, 8-7print data, 8-8refresh values, 8-8reports

SDH, 2-38SONET, 2-38

samples, 8-7save data, 8-8


Index

VT/TU dataviewing, 8-7

Cardadd, 3-12administrative state, 5-4CLEIconfiguring

working card, 5-3customer tag, 5-5delete, 3-13equipped state, 5-4international common identifier, 5-5mode

switch, 5-51module ID, 5-5operational state, 5-4parameters

changing, 5-3common, 5-5GCM specific, 5-6

part number, 5-5preprovisioning, 5-3replace, 3-14serial number, 5-5software version, 5-5type

BLSR ring, 4-4Carrier Ethernet Protection Pair

card typesEoPDH, 4-31NGE Plus, 4-31

configuration1+1 APS protection, 4-34ID, 4-33name, 4-33revertive, 4-33role, 4-33status, 4-34WTR, 4-33

creating, 4-33description, 4-32LAG, 4-32WTR time, 4-33

C-bit processingDS3 port, 5-13

Classifieradd, 6-54configure, 6-54parameters, 6-54

Clearprotection switch command

1+1 APS, 4-26, 4-271+1 MSP, 4-26, 4-27

1+1 optimized protection, 4-38BLSR ring, 4-7equipment protection, 4-20

CLEICLEI, see Cardnode

displaying, 3-8Client type

session list, 2-12Clock

qualityBITS timing, 3-23

timingmode, 3-23quality, 3-23

Concatenation1+1 path protection, 4-30EOS port

size, 5-64type, 5-64

type, 6-59Config tab

BITS and derived DS1, 3-24DS3 Clear Channel port, 5-13DS3-TMX port, 5-15map view, 1-29, 1-47node, 3-5shelf view, 1-32, 1-50

Configurationglobal timing, 3-22port

EC1, 5-19Confirm password

userdomain, 2-8node, 2-15

Connectionsadmission control

Ethernet, 6-49unidirectional, 6-28, 6-41, 7-16, 7-35

Contactname

TransAccess 200 Mux, 5-77TE-50, 5-82

Control dataSONET port, 5-26STM port, 5-44

Counter, 6-90, 8-6port performance monitoring, 8-5

CreateEOS tab, 5-63LAG tab, 5-71node, 3-4


Index

CrossoverETH100TX, 5-60

CTPs, see Service endpointsCurrent

transmitter stateEthernet port, 5-54SONET port, 5-24STM port, 5-42

Current transmitter stateEthernet port, 5-55

Custom REDsee Ethernet port

Customer, 6-21, 6-33, 6-59associations

equipment, 2-39links, 2-39services, 2-39

create, 2-39description, 2-39DS1 port, 5-11DS3 port, 5-14DS3TMX port, 5-16E1 port, 5-37E3 port, 5-39EC1 port, 5-21Ethernet port, 5-54SONET port, 5-26STM port, 5-44STS1TMX port, 5-16tag

card, 5-5DS3TMX port, 5-16EC1 port, 5-21Ethernet port, 5-55node, 3-9STM port, 5-44STS1TMX port, 5-16

Customizenode groups, 2-22, 2-25

DData communications

channelSONET, 5-26

Databasebackups

multiple servers, 2-33DCC tunnel

tabshelf view, 1-32, 1-50

DCSapplication

DCS-384 matrix shelf definition, 7-4

DCS-96 shelf definition, 7-27DCS-IO shelf definition, 7-20multi-shelf, DCS-384 matrix shelf, 7-4multi-shelf, DCS-IO shelf, 7-20single-shelf, DCS-96 shelf, 7-27

DCS-384hardware configuration, 7-6MSAID allocation, 7-9MSAID assignments, 7-8, 7-16protection groups, 7-7service parameters, 7-11services, 7-10

DCS-96MSAID assignment details, 7-29MSAID assignments, 7-28service endpoints, 7-31services, 7-30

DCS-IOMSAID allocation, 7-21MSAID assignments, 7-22

MSAID assignmentDCS-IO protection, 7-25

MSAID assignment details, 7-23bridge and roll, 7-24description, 7-24endpoint, 7-24forward path trace, 7-24forward signal label, 7-24MSAID number, 7-24PM templates, 7-24reverse path trace, 7-24reverse signal label, 7-25transmuxed, 7-24

node parameters, 3-6service

search, 6-16DCS service

Search, 7-17DCS-IO

shelfMSAID assignments, 7-22

Deletecard, 1-34, 1-37, 1-52, 1-55node, 3-11TE-50, 5-81TransAccess 200 Mux, 5-75

DerivedDS1 outputs

config tab, 3-24Description

MSAID assignment detailsDCS, 7-24


Index

DestinationDest PM template, 6-25, 6-38, 7-13, 7-32mapping

DestDS1Mapping, 6-25, 6-38, 7-13, 7-32DestDS3Mapping, 6-25, 6-38, 7-13, 7-32DestE1Mapping, 6-25, 6-38, 7-13, 7-32

Node ID, 6-24, 6-37Diagnostics

description, 8-39, 8-47tab

shelf view, 1-32, 1-50Domain

reportservices, 2-37

rolesaccess rights, 2-7

userconfirm password, 2-8create, 2-8group, 2-8management by, 2-8roles, 2-7, 2-10set up, 2-8timeout, 2-8username, 2-8, 2-15view session list, 2-4

DS1card

mapping, 5-10numbering, 5-9

portAIS insertion, 5-11AIS mask, 5-11alarm profile, 5-11, 8-24customer, 5-11line build out, 5-11line coding, 5-11line format, 5-10PM template, see Performance Monitoringswitch to EC1, 5-14valid signal time, 5-11

DS3mapping

DS3TMX port, 5-15STS1TMX port, 5-15

module parametersswitch to E3, 5-12

portAIS format, 5-14AIS mask, 5-13alarm profile, 5-14, 8-24C-bit processing, 5-13customer, 5-14

line build out, 5-14line coding, 5-14line format, 5-13PM template, see Performance MonitoringRDI, 5-13signal level, 5-13switch from EC1, 5-21

DS3/EC1 porttest signal type, 8-42

DS3TMXline format

subport, 5-17, 5-18port

AIS format, 5-16AIS mask, 5-16alarm profile, 5-16customer, 5-16customer tag, 5-16DS3 mapping, 5-15line build out, 5-16line coding, 5-16line format, 5-15PM template, 5-16signal level, 5-15subport mapping, 5-16subport numbering, 5-15

subportalarm profile, 5-18loopback, 5-18PM template, 5-18

DUSSONET port, 5-25STM port, 5-43

EE1

cardmapping, 5-33parameters, 5-32

portAIS insertion, 5-37AIS mask, 5-36alarm profile, 5-37, 8-24customer, 5-37line build out, 5-36line coding, 5-36line format, 5-36PM template, see Performance Monitoringvalid signal time, 5-37

E3card parameters

switch to DS3, 5-38


Index

portAIS mask, 5-39alarm profile, 5-39, 8-24customer, 5-39line build out, 5-39line coding, 5-39line format, 5-39PM template, see Performance Monitoring

East portBLSR ring, 4-5MS-SP ring, 4-5SNCP ring, 4-12UPSR ring, 4-12

EC1port

AIS mask, 5-19alarm profile, 5-21configuration, 5-19customer, 5-21customer tag, 5-21line build out, 5-20line coding, 5-19line format, 5-19SD BER, 5-20SF BER, 5-20signal level, 5-19switch to DS3, 5-21valid signal timer, 5-20

EMSGateway IP address, 3-7IP address, 3-7Mask IP address, 3-7

Encapsulation type, 6-59Endpoint

MSAID assignment detailsDCS, 7-24

resource advisory, 6-6SDH, 9-11services

EOP on EoPDH cards, 9-8SDH on EoPDH cards, 9-14STS on EoPDH cards, 9-8VT1.5 on EoPDH cards, 9-8

summary, 9-3End-to-end service

creation model, 6-10Environmental

alarmsconfiguration, 3-8

EOPport

loopback, see LoopbackMAC address, 5-53

EoPDHendpoints

EOP, 9-8SDH services, 9-14STS, 9-8VT1.5, 9-8

multipoint ECC, 6-45, 6-46service

SDH restrictions, 9-14SONET restrictions, 9-8

EOSport

admin state, 5-64advanced parameters, 5-65alarm profile, 5-65, 8-24Apply LCAS Hold Off, 5-65Apply LCAS WTR, 5-65concatenation, 5-64customer, 5-64description, 5-64direction, 5-64direction, traffic, 5-64endpoint, 5-64GFP FCS insert, 5-65ID, 5-63LCAS, 5-65MAC address, 5-53member#, 5-64parameters, 5-63PLCR Threshold, 5-66PLCT Threshold, 5-66PM template, 5-65queue, 5-67queue occupancy, 5-67queue policy, 5-67queue, Custom RED, 5-68RSTP, 5-65RSTP path cost, 5-65RSTP port priority, 5-66service group, 5-64slot, 5-63status, 5-69TE100 LCAS compatibility mode, 5-66virtual RSTP bridge, 5-66

port memberalarm profile, 8-24

port statusactive source members, 5-69member number, 5-69relative differential delay, 5-70RSTP port role, 5-69RSTP port state, 5-69


Index

subtab, 5-63, 5-69edit, 5-69

EOS portstatus

active sink members, 5-69Equipment

creating and deleting, 3-3Equipment protection

configurationcard, 4-18card selection, 4-18ID, 4-18name, 4-18protection, 4-19revertive, 4-18role, 4-18status, 4-19WTR, 4-18

protection switch commandsclear, 4-20forced, 4-20lockout, 4-20manual, 4-20

protection switch priorities, 4-21Equipped state

card or port, 5-4Ethernet, 5-50

alternate VLAN ethertype, 5-51automatic laser shutdown, 5-54cards, 6-43configuration tab, 5-50EOS subtab, 5-63features, 6-57

connection admission control, 6-49LCAS

HO WTR, 5-51LO holdoff, 5-50LO WTR, 5-51

LO mapping, 5-50MAC address, 5-50

table, 5-52parameters, 5-49port

advanced tagging, 5-61Advertise 1000M Full Duplex GBETX, 5-60Advertise 1000M Full Duplex, GBE, 5-59Advertise 1000M Half Duplex GBE, 5-59Advertise 1000M Half Duplex GBETX, 5-60Advertise 100M Full Duplex (ETH100TX), 5-

59Advertise 100M Half Duplex (ETH100TX), 5-

59Advertise 10M Full Duplex (ETH100TX), 5-59

Advertise 10M Half Duplex (ETH100TX), 5-59Advertise GBE RX PAUSE, 5-60Advertise GBE TX PAUSE, 5-60Advertise PAUSE (ETH100TX), 5-59Advertise PAUSE RX GBE, 5-59Advertise PAUSE TX GBE, 5-59alarm profile, 5-55, 8-24auto-negotiation, 5-53, 5-59current transmitter state, 5-54, 5-55custom RED, 5-62customer, 5-54customer tag, 5-55FIFO shape enable, 5-62FIFO shaping rate, 5-62insert alternate VLAN ethertype, 5-61jumbo frame, 5-55jumbo framet, 5-55manual crossover ETH100TX, 5-60manual duplex, 5-53manual duplex ETH100TX, 5-60manual duplex GBE, 5-60manual pause ETH100TX, 5-60manual pause GBE, 5-61manual speed, 5-54manual speed ETH100TX, 5-60manual speed GBE, 5-60max info rate, 5-58max info rate, burst size, 5-59parameters, 5-53, 5-58PM template, see Performance Monitoringqueuing policy, 5-61recovery pulse width, 5-54tagging, 5-55transmitter auto shutdown, 5-54, 5-55transmitter state, 5-54VLAN, customer-tagged, 5-55VLAN, port-tagged, 5-55VLAN, service-tagged, 5-55VLAN, untagged, 5-55WFQ CoS weight, 5-62

service parameters, 6-44advanced, 6-48classifier, 6-45endpoints, 6-45multipoint ECC, 6-46policers, 6-45

service portadvanced parameters, 6-47

servicescreate, 6-44

tabshelf view, 1-32, 1-50


Index

Eventcategories, 8-30filter

setting, 8-36list

detail view, 8-32grouping, 8-35new window, 8-32refresh, 8-32set filters, 8-32settings, 8-32sorting, 8-32

logserver output, 8-30

logs, 8-30reporting, 8-30settings, 8-38tab

column order, 8-32map view, 1-29, 1-47shelf view, 1-32, 1-50

types, 8-30Events

settings, 8-27save and import, 2-22

Exercise protection switch command1+1 APS, 4-271+1 MSP, 4-27

Externalalarms

configuration, 3-8timing

BITS configuration, 3-22framing format, 3-25

FFacility

loopback, see LoopbackFailure retry count, 6-25, 6-38, 7-13, 7-32FIFO

shape enablequeuing policy, 5-62

Filterservices

setting, 6-79Fixed-24Bit test signal type, 8-42Force switch

commandBITS timing, 3-31, 3-32

Forced protection switch command1+1 APS, 4-26, 4-271+1 MSP, 4-26, 4-271+1 optimized protection, 4-38

BLSR ring, 4-7equipment protection, 4-20

Forwardpath

format, 6-25, 6-39, 7-13, 7-33trace, 6-25, 6-39, 7-13, 7-33

path traceMSAID assignment, DCS, 7-24

signal label, 6-25, 6-39, 7-13, 7-33DCS MSAID assignment, 7-24

Framing formatexternal timing, 3-25

Functional groupsassign

domain users, 2-6definition, 2-4, 2-9roles, 2-10see also Groups

GGCM

config tab, 5-6parameter

specific, 5-6GCM A

IP address, 3-7gateway, 3-7MAC address, 3-7mask, 3-7

GCM BIP address, 3-7

gateway, 3-7MAC address, 3-7mask, 3-7

GFPFCS insert

EOS port advanced, 5-65Graphical user interface

conventions, 1-43, 1-61resizing windows, 1-44, 1-62scroll bars, 1-43, 1-61

menu bar, 1-28, 1-46shelf view, 1-31, 1-49views

map view, 1-28, 1-46map view, shortcut menus, 1-29, 1-47navigation tree, 1-28, 1-46network map, 1-28, 1-46shelf shortcut menus, 1-32, 1-50TE-100 shelf, 1-53TE-100 shelf, shortcut menus, 1-36, 1-54


Index

Groupsadd

node, 2-25change name, 2-26configuration, 2-26domain users, 2-8functional

assign domain users, 2-6definition, 2-4

navigation tree, 2-28node

background images, 2-21change name, 2-32customize, 2-25

roles, 2-10role-based access control

HHierarchy

alarms, 8-16Historical

reportalarm, 2-37data access, 2-33event, 2-37

Hold off timer, 6-24, 6-37Hop-by-hop service, 6-11Host name, 1-19, 1-21, 1-24, 1-25

IID

1+1APS, 4-24optimized protection, 4-36path protection, 4-30

Carrier Ethernet Protection Pair, 4-33equipment protection, 4-18

Input Sync MsgsSONET port, 5-24STM port, 5-42

Insert alternate VLAN ethertypeEthernet port, 5-61TE-100, 5-51

International common identifiercard, 5-5node, 3-9

Internet Explorerweb browser settings, 1-4

Intervalcapacity monitoring, 8-7port

performance monitoring, 6-91, 8-5, 8-7

IP addressEMS, 3-7

gateway, 3-7mask, 3-7

gatewayEMS, 3-7GCM A, 3-7GCM B, 3-7

GCM A, 3-7gateway, 3-7mask, 3-7

GCM B, 3-7gateway, 3-7mask, 3-7

maskEMS, 3-7GCM A, 3-7GCM B, 3-7

Network Time Protocol, 3-7node

backplane DCN gateway, 3-7backplane DCN mask, 3-7

node-ip, 3-10session list, 2-12TE-50, 5-80TransAccess 200 Mux, 5-74, 5-77

IP QoS, 3-35

JJumbo frame

Ethernet portsize, 5-55support, 5-55

LLAG

advanced parameters, 5-72CEPP, 4-32customer, 5-71description, 5-71ID, 5-71part loss threshold, 5-72port

alarm profile, 8-24slot, 5-71subtab, 5-71

LCASconfiguration, 6-59EOS port advanced, 5-65

compatibility mode, 5-66Ethernet

HO WTR, 5-51


Index

LO Holdoff, 5-50LO WTR, 5-51

Linebuild out

BITS timing, 3-25DS1 port, 5-11DS3 port, 5-14DS3TMX port, 5-16E1 port, 5-36E3 port, 5-39EC1 port, 5-20

codingDS1 port, 5-11DS3 port, 5-14DS3TMX port, 5-16E1 port, 5-36E3 port, 5-39EC1 port, 5-19STS1TMX port, 5-16timing, 3-24

formatDS1 port, 5-10DS3 port, 5-13DS3TMX port, 5-15DS3TMX subport, 5-17, 5-18E1 port, 5-36E3 port, 5-39EC1 port, 5-19SONET port, 5-23STM port, 5-41STS1TMX port, 5-15STS1TMX subport, 5-17, 5-18UTMX subport, 5-17, 5-18

timingconfiguration, 3-22, 3-27establishing source, 3-27SONET port, 5-23source, 3-28SSM received, 3-28status, 3-28STM port, 5-41synchronization status message, 3-28

Linkadd, 3-15aggregation group

see LAGavailable bandwidth

view, 3-17delete, 3-18destination, 3-16off page connector icon, 3-16operational state, 3-17set without DCC discovery, 3-15

source, 3-15types, 3-15

data rate, 3-16Links

TE-206discovery, 2-18

LO mapping, 5-50Load balance, 6-26, 6-39, 7-14, 7-33Lockout protection switch command

1+1 APS, 4-261+1 MSP, 4-261+1 optimized protection, 4-38BITS timing, 3-31BLSR ring, 4-7equipment protection, 4-20

Lockout switch commandBITS timing, 3-32

Login dialog boxadvanced

notification, 1-26port number, 1-26protocol, 1-26

connect toserver, 1-19, 1-21, 1-24

host name, 1-19, 1-21, 1-24, 1-25password, 1-19, 1-21, 1-24, 1-25user name, 1-19, 1-21, 1-24, 1-25

Loopbackdiagnostic tests, 8-39DS3TMX subport, 5-18facility, 8-40

EOP, 8-40far-end facility

EOP, 8-41in-band

EOP, 8-41STS1TMX subport, 5-18terminal, 8-41tests

EOP ports, 8-43performing, 8-42

UTMX subport, 5-18

MMAC address

EOP port, 5-53EOS port, 5-53Ethernet, 5-50GCM A, 3-7GCM B, 3-7node backplane DCN, 3-7port ID, 5-52slot ID, 5-52


Index

tablecount, 5-53Ethernet, 5-52port type, 5-52service, 5-52

Managementgateway node, 3-3port

TransAccess 200 Mux, 5-77system

event logs, 8-30Manual

duplexETH100TX, 5-60GBE, 5-60

pauseETH100TX, 5-60

protection switch command1+1 APS, 4-26, 4-271+1 MSP, 4-26, 4-27BLSR ring, 4-7equipment protection, 4-20

speedETH100TX, 5-60

switch commandBITS timing, 3-31, 3-32

Manual pauseGBE, 5-61

Manual speedGBE, 5-60

Map viewalarms tab, 1-29, 1-47change background, 1-30, 1-48config tab, 1-29, 1-47description, 1-28, 1-46events tab, 1-29, 1-47group map, 1-28, 1-46network map, 1-28, 1-46performance tab, 1-29, 1-47protection tab, 1-29, 1-47service tab, 1-29, 1-47shortcut menu, 1-29, 1-47

Max SD-BER-V, 6-26, 6-39, 7-14, 7-33Max SF-BER-V, 6-26, 6-39, 7-14, 7-33Maximum hop count, 6-26, 6-39, 7-14, 7-33Member number

EOS port, 5-64status, 5-69

Menus, 1-37, 1-55admin, 1-41, 1-59alarm, 1-39, 1-57events, 1-39, 1-57file, 1-38, 1-56

help, 1-43, 1-61provisioning, 1-43, 1-61service groups, 1-40, 1-59services, 1-40, 1-58TE-50, 5-81view, 1-38, 1-56

Moduleadd, 3-12delete, 3-13ID, 5-5

node, 3-9replace, 3-14

MSAIDallocation

DCS-384 shelf, 7-9DCS-IO, 7-21

assignment details, 7-24assignments

DCS-384, 7-16DCS-384 shelf, 7-8DCS-96 shelf, 7-28

definition, 7-5supported formats, 7-5

MS-SP ringconfiguration, 4-5

card type, 4-4east port, 4-5name, 4-4node ID, 4-4protection, east port, 4-5protection, west port, 4-5revertive, 4-4ring ID, 4-4status, west port, 4-5west port, 4-4WTR, 4-4

configuration node, 4-4delete, 4-14edit, 4-14protection switch commands


protection switch priorities, 4-7remove node, 4-6squelch table, 4-6synchronize, 4-5, 4-14

Multiple serversbackups, 2-33

Multipoint ECCEoPDH, 6-45

create, 6-46


Index

NName

1+1 APS, 4-241+1 optimized protection, 4-361+1 path protection, 4-30BLSR ring, 4-4Carrier Ethernet Protection Pair, 4-33equipment protection, 4-18MS-SP ring, 4-4SNCP ring, 4-12UPSR ring, 4-12

Navigation treeGUI, 1-28, 1-46

Network Time ProtocolIP address, 3-7

Nodeaccess

groups and rights, 2-14auto-discovery, 3-3backplane DCN

mask IP address, 3-7BLSR ring, 4-4CLEI, 3-8create, 3-4customer tag, 3-9delete, 3-11deleting pre-provisioned, 3-11group

background images, 2-21change name, 2-32create, 2-25customize, 2-25

ID, 3-10BLSR ring, 4-4MS-SP ring, 4-4TE-50, 5-82TransAccess 200 Mux, 5-77

International common identifier, 3-9IP, 3-10IP address, 3-10

TE-50, 5-82module ID, 3-9MS-SP ring, 4-4name, 3-4parameters

alarm profile, 3-6backplane DCN, MAC address, 3-7backplane IP address, 3-6backplane IP address, DCN gateway, 3-7backplane IP address, DCN mask, 3-7backplane part number, 3-8configuring, 3-5DCS, 3-6

ID, 3-5IP address, 3-6location, 3-6node ID, 3-5node type, 3-6setting, 3-8

preprovisioningadd name, 3-4

remote ACO, 3-7report

inventory, 2-37serial number, 3-8setting Proxy ARP, 3-9SNCP ring, 4-12SNMP

agent port, 3-9UPSR ring, 4-12user

access, 2-16change password, 2-5confirm password, 2-15create, 2-15management by, 2-15name, 2-15roles, 2-16security, 2-14synchronization, 2-16

Notificationlogin, 1-26

OOperational

statecard or port, 5-4

Output Sync MsgsSTM port, 5-43

PParameters

cardcommon, 5-5

Ethernet module, 5-49GCM

specific, 5-6SFP port, 5-56XFP port, 5-56

parameters, 5-72Part Loss Threshold, see LAGPart number

card, 5-5node backplane, 3-8

Password, 1-19, 1-21, 1-24, 1-25


Index

change, 2-5user, 2-8, 2-15

PathDCC configuration

SONET port, 5-27STM port, 5-45

mapping, 6-26, 6-40, 7-14, 7-34overhead

transmission, 6-89trace

received, 6-89Performance

tabmap view, 1-29, 1-47shelf view, 1-32, 1-50

Performance monitoringport

counter, 8-5interval, 6-91, 8-7samples, 6-90, 8-6

reports, see Reportsservice counter, 6-90, 8-6template

DS1 port, 5-11DS3 portE1 port, 5-37E3 port, 5-39Ethernet portsource, 6-27, 6-41, 7-15, 7-35Source and Dest-DCS, 7-24STM port, 5-44

viewing port PM data, 8-7VT/TU capacity

viewing, 8-7PLCR Threshold, 5-66PLCR Threshold, see EOS portPLCT Threshold, 5-66PLCT Threshold, see EOS portPM template

DS3TMX port, 5-16DS3TMX subport, 5-18EOS port advanced, 5-65STS1TMX port, 5-16STS1TMX subport, 5-18UTMX subport, 5-18

Point-to-pointprotocol

discovering links, 2-18Policers

create, 6-53parameters, 6-53

Poll intervaladmin menu


Port1+1 optimized protection, 4-37administrative state, 5-4EOS, 5-63equipped state, 5-4ID

MAC address, 5-52number

TE-50, 5-80TransAccess 200 Mux, 3-10, 5-74user session, 1-26

operational state, 5-4Preprovisioning

card, 5-3creating and deleting managed objects, 3-3deleting nodes, 3-11node name, 3-4node type, 3-4

Prioritiespriority requests, 4-21protection switching

1+1 APS, 4-271+1 MSP, 4-271+1 optimized protection, 4-38BLSR ring, 4-7equipment protection, 4-21

Protection1+1 APS, 4-251+1 MSP, 4-251+1 optimized protection, 4-371+1 path protection

path, 4-30port, 4-30

BLSR ringeast port, 4-5west port, 4-5

Carrier Ethernet Protection Pair1+1 APS, 4-34

DCS-IOMSAID assignment, 7-25

equipment, 4-19MS-SP ring

east port, 4-5west port, 4-5

ringsdelete, 4-14edit, 4-14synchronize, 4-14


Index

tabmap view, 1-29, 1-47shelf view, 1-32, 1-50

Protection switch commands1+1 path protection


BLSR ringclear, 4-7forced, 4-7l ockout, 4-7manual, 4-7

clear1+1 APS, 4-26, 4-271+1 MSP, 4-26, 4-271+1 optimized protection, 4-38BLSR ring, 4-7equipment protection, 4-20

exercise1+1 APS, 4-271+1 MSP, 4-27

forced1+1 APS, 4-26, 4-271+1 MSP, 4-26, 4-271+1 optimized protection, 4-38BLSR ring, 4-7equipment protection, 4-20

lockout1+1 APS, 4-261+1 MSP, 4-261+1 optimized protection, 4-38BLSR ring, 4-7equipment protection, 4-20

manual1+1 APS, 4-26, 4-271+1 MSP, 4-26, 4-27BLSR ring, 4-7equipment protection, 4-20

MS-SP ringclear, 4-7forced, 4-7manual, 4-7

ProtocolHTTP, 1-26HTTPS, 1-26RMI, 1-26user session, 1-26

ProvisioningTE-206 nodes see TraverseEdge 206 Users Guide,

2-19

Proxy ARPnode set up, 3-9

Pseudo random bit sequence, 8-42

QQuality of RES

timing tab, 3-22Queuing policy, 5-61

EOS port, 5-67FIFO, 5-61

shape enable, 5-62shaping rate, 5-62

priority, 5-61WFQ, 5-62

CoS weight, 5-62

RRandom early discard

configurationdefaults, 5-68

Read communityTE-50, 5-80, 5-82TransAccess 200 Mux, 3-10, 5-74, 5-77

Recovery pulse widthEthernet port, 5-54SONET port, 5-24STM port, 5-42

RediscoveryTE-206, 2-18

Redline circuit, see Service parametersRelative Diff Delay

EOS port status, 5-70Remote ACO

node, 3-7Replace card, 1-34, 1-37, 1-52, 1-55Report scheduler, see ReportsReports

capacity monitoringSDH, 2-38SONET, 2-38

creating, 2-33example

Event, 2-43generate, 2-33

period, 2-36generated

location, 2-41historical

alarm, 2-37event, 2-37

inventorynode, 2-37


Index

list, 2-35performance monitoring

DS1 port, 2-37DS3 port, 2-37E1 port, 2-37E3 port, 2-37EC1 port, 2-37EOS, 2-37Ethernet 10GE, 2-38Ethernet NGE, 2-38Ethernet port, 2-38Ethernet service port, 2-38SDH port, 2-38SDH VC-11 path, 2-38SDH VC-12 path, 2-38SONET port, 2-38STS path, 2-38TE100, 2-38VT path, 2-38

period length, 2-39resource availability, 2-37scheduled, 2-35scheduler

usingscript files, 2-37service

availability, 2-37domain, 2-37endpoints, 2-37

source filter, 2-38TE-206

restrictions, 2-41types, 2-33viewing, 2-41

Reports, see also AlarmsReports, see also EventsResize

windows, 1-44, 1-62Resource

advisorylink, 3-17

availabilityreport, 2-37

Resource advisorydefinition, 6-6

Restart cardcold, 1-34, 1-37, 1-52, 1-55warm, 1-34, 1-37, 1-52, 1-55

Reversepath format see Service parameterspath trace

MSAID assignment, DCS, 7-24see also Service parameters

signal label see also Service parametersMSAID assignment, DCS, 7-25

Revertive1+1 APS, 4-24BLSR ring, 4-4Carrier Ethernet Protection Pair, 4-33equipment protection, 4-18MS-SP ring, 4-4service parameter, 6-23, 6-36timing, 3-23

Ring IDBLSR ring, 4-4MS-SP ring, 4-4SNCP ring, 4-12UPSR ring, 4-12

Role1+1 optimized protection, 4-36Carrier Ethernet Protection Pair, 4-33domain

access rights, 2-7user, 2-10

equipment protection, 4-18node

access rightsuser, 2-16

Role-based Access Controldefinition, 2-4example, 2-4see also Groups

Round trip delayenable function, 6-26, 6-40, 7-14, 7-34expected, 6-25, 6-38, 7-13, 7-32

RSTPconfiguration, 6-60EOS port advanced, 5-65

path cost, 5-65port priority, 5-66

path cost, 6-60port

EOS status, 5-69port priority, 6-60

EOS port advanced, 5-66virtual bridge, 5-66

SSamples, port see Performance monitoringScript file

report, 2-37Scroll bars, 1-43, 1-61SD BER

EC1 port, 5-20line, 5-25


Index

SONETcard path, 5-22port, 5-25

STM cardregenerator section, 5-40

STM portmultiplex section, 5-43

SDHadministrative state, 6-89port

alarm profile, 8-24performance tab, 8-4

serviceendpoints, 9-11

SearchDCS service, 6-16, 7-17

Securityroles

see Domain, rolessee Node, access

useraccess groups, 2-13domain, 2-3, 2-13functional group, 2-4node, 2-3, 2-13

Serial numbercard, 5-5node

displaying, 3-8Servers

alarm profile, 8-24Service

availability report, 2-37configuration

description, 6-57, 6-73, 6-85creation

process, 6-12creation parameters

bandwidth, 6-21, 6-33concatenation type, 6-59customer, 6-21, 6-33, 6-59encapsulation type, 6-59LCAS configuration, 6-59RSTP configuration, 6-60RSTP path cost, 6-60RSTP port priority, 6-60

delete, 6-79endpoints, 9-3

report, 2-37end-to-end

constraint types, 6-10creation model, 6-10

groupcreate, 6-69EOS port, 5-64parameters, see also Service parameters

hop-by-hopcreation model, 6-11

parametersbridge and roll, 6-25, 6-38, 7-13, 7-32Dest PM template, 6-25, 6-38, 7-13, 7-32DestDS1Mapping, 6-25, 6-38, 7-13, 7-32DestDS3Mapping, 6-25, 6-38, 7-13, 7-32DestE1Mapping, 6-25, 6-38, 7-13, 7-32failure retry count, 6-25, 6-38, 7-13, 7-32forward path format, 6-25, 6-39, 7-13, 7-33forward path trace, 6-25, 6-39, 7-13, 7-33forward signal label, 6-25, 6-39, 7-13, 7-33load balance, 6-26, 6-39, 7-14, 7-33max SD-BER-V, 6-26, 6-39, 7-14, 7-33max SF-BER-V, 6-26, 6-39, 7-14, 7-33maxiimum hop count, 6-26, 6-39, 7-14, 7-33path mapping, 6-26, 6-40, 7-14, 7-34protection, destination node ID, 6-24, 6-37protection, hold off timer, 6-24, 6-37protection, revertive, 6-23, 6-36protection, WTR time, 6-24, 6-37redline circuit, 6-26, 6-40, 7-14, 7-34reverse path format, 6-27, 6-40, 7-15, 7-34reverse path trace, 6-27, 6-40, 7-15, 7-34reverse signal label, 6-27, 6-40, 7-15, 7-34round trip delay, enable, 6-26, 6-40, 7-14, 7-34round trip delay, expected, 6-25, 6-38, 7-13, 7-

32setup retry count, 6-27, 6-41, 7-15, 7-35source node ID, 6-24, 6-37source PM template, 6-27, 6-41, 7-15, 7-35sourceDS1Mapping, 6-27, 6-41, 7-15, 7-35sourceDS3Mapping, 6-27, 6-41, 7-15, 7-35sourceE1Mapping, 6-27, 6-41, 7-15, 7-35TMX port, 6-27, 6-41, 7-15, 7-35transparency, 6-28, 6-41, 7-16, 7-35unidirectional connections, 6-28, 6-41, 7-16, 7-

35performance monitoring

counter, 6-90, 8-6SDH

endpoints, 9-11show last error, 6-77tab, 6-77

map view, 1-29, 1-47shelf view, 1-32, 1-50

VC-bundlecreate, 6-58


Index

VT MUXendpoint requirements, 9-8SDH endpoints, 9-12

Service parameterscount

concecutive services, 6-70endpoints

summary, 9-3group, 6-69

concat. size, 6-70description, 6-69, 6-72edit, 6-71name, 6-69, 6-72routing policy, 6-70

Servicesabort, 6-77activate, 6-77administrative state, 6-75bandwidth of, 6-75customer, 6-76deactivate, 6-77delete, 6-79description, 6-76edit, 6-79end-to-end, 6-11EoPDH

restrictions, 9-8, 9-14filter, 6-78grouping, 6-78multipoint ECC, 6-45

create, 6-46name, 6-74operational state, 6-75resize columns, 6-78roll, 6-78service state, 6-76set filters, 6-79show provisioned path, 6-77show TxRx path, 6-77sorting, 6-78source endpoint, 6-74system ID, 6-74type, 6-75view, 6-79

Sessionlist

client type, 2-12IP address, hostname, 2-12terminate user, 2-12time logged in, 2-12user name, currently online, 2-12

terminationsetting timeout, 2-8

Session listuse, 2-4

Setup retry count, see Service parametersSeverity levels

alarm and eventdefined, 8-16

alarms, 8-17SF BER

EC1 port, 5-20line, 5-24SONET

card path, 5-22port, 5-24

STM card, 5-40STM port

multiplex section, 5-42Shelf

alarm profile, 8-24name

TransAccess 200 Mux, 5-74view

GUI, 1-31, 1-49Shelf view

description, 1-31, 1-49shortcut menu, 1-32, 1-36, 1-50, 1-54, 3-12tab

alarms, 1-32, 1-50config, 1-32, 1-50DCC tunnel, 1-32, 1-50diagnostic, 1-32, 1-50Ethernet, 1-32, 1-50events, 1-32, 1-50performance, 1-32, 1-50protection, 1-32, 1-50service, 1-32, 1-50timing, 1-32, 1-50

Shortcut menumap view, 1-29, 1-47shelf view, 1-32, 1-36, 1-50, 1-54

Signallevel

DS3 port, 5-13DS3TMX port, 5-15EC1 port, 5-19

timerEC1 port, 5-20

SlotEOS port, 5-63ID

MAC address, 5-52SNCP ring

configurationeast port, 4-12


Index

name, 4-12node, 4-12ring ID, 4-12west port, 4-12

delete, 4-14edit, 4-14synchronize, 4-14

SNMPnode

agent port, 3-9configuration, 3-9

Software upgradeabort download, 8-57activation

status, 8-55time, 8-55type, 8-56

base path, 8-54card

identifier, 8-55type, 8-55

clearactivation time, 8-57download time, 8-57

current compatibility identifier, 8-55download

status, 8-54time, 8-54, 8-56

password, 8-54rel path, 8-54

automatically fill, 8-56server IP address, 8-54slot number, 8-54, 8-55upgrade type, 8-54, 8-56username, 8-54

Software versioncard, 5-5

SONETalarm profile

port, 8-24STS, 8-24VT, 8-24

card pathSD BER, 5-22SF BER, 5-22

portAIS mask, 5-23alarm profile, 5-26configuration, 5-23control data, 5-26current transmitter state, 5-24customer, 5-26DUS, 5-25

line format, 5-23line SD BER, 5-25line SF BER, 5-24line timing, 5-23path DCC configuration, 5-27recovery pulse width, 5-24SS bit transmit, 5-25sync msgs, output, 5-25sync msgs,input, 5-24terminate DCC, 5-26transmitter auto shutdown, 5-24, 5-25transmitter state, 5-24

Sourceline timing, 3-28Node ID, 6-24, 6-37PM template, 6-27, 6-41, 7-15, 7-35

Source mapping, see Service parametersSS bit transmit

SONET port, 5-25STM port, 5-43

SSM, see Synchronization status messagesStarting AUG1 numbers

VC3 paths, 6-35VC4 paths, 6-35

Static routeadd to node, 3-20

Status1+1 APS, 4-251+1 MSP, 4-251+1 optimized protection, 4-37BLSR ring

east port, 4-5west port, 4-5

Carrier Ethernet Protection Pair, 4-34equipment protection, 4-19line timing, 3-28

StickyMode see Alarms, StickyMode

STMcard parameters

SD BER, 5-40SF BER, 5-40

portAIS mask, 5-41alarm profile, 5-44config tab, 5-41configuration, 5-41control data, 5-44current transmitter state, 5-42, 5-43customer, 5-44customer tag, 5-44DUS, 5-43line format, 5-41


Index

line timing, 5-41multiplex section, SD BER, 5-43multiplex section, SF BER, 5-42output synchronization messages, 5-43path DCC configuration, 5-45PM template, see Performance Monitoringrecovery pulse width, 5-42SS bit transmit, 5-43synchronization messages, input, 5-42synchronization messages, output, 5-43synchronization messages, status, 5-42terminate DCC, 5-44transmitter auto shutdown, 5-42transmitter state, 5-42

STS pathadministrative state, 6-89

STS1TMXline format

subport, 5-18port

AIS format, 5-16AIS mask, 5-16alarm profile, 5-16customer, 5-16customer tag, 5-16DS3 mapping, 5-15line coding, 5-16line format, 5-15PM template, 5-16subport mapping, 5-16subport numbering, 5-15

subportalarm profile, 5-18line format, 5-17loopback, 5-18PM template, 5-18

Sub shelfmenu

attach sub shelf, TransAccess 200 Mux, 5-76attach TE-50 sub shelf, 5-82detach TE-50 sub shelf, 5-81detach TransAccess 200 Mux, 5-75, 5-76launch sub shelf, TransAccess 200 Mux, 5-76sync sub shelf alarms, TE-50, 5-82sync sub shelf alarms, TransAccess 200 Mux,

5-76TE-50, 5-81TransAccess 200 Mux, 5-75

TE-50ID, 5-82IP address, 5-82type, 5-82

TransAccess 200 Mux

ID, 5-77IP address, 5-77type, 5-77

Subportmapping

DS3TMX port, 5-16STS1TMX port, 5-16

numberingDS3TMX port, 5-15STS1TMX port, 5-15

Summaryservice endpoints, 9-3

Switchingcard mode, 5-51DS3 to E3, 5-12DS3 to EC1, 5-21E3 to DS3, 5-38EC1 to DS3, 5-21

Syncinterval, admin menu


sub shelf alarmsTE-50, 5-82TransAccess 200 Mux, 5-76

Synchronizationalarm profiles, 8-25BLSR ring, 4-5MS-SP ring, 4-5node user, 2-16status message

ignore received, 3-23input, 5-24, 5-42output, 5-25, 5-43received by line timing, 3-28SONET port, 5-24STM port, 5-42, 5-43transmitted by line timing, 3-28

TTabs

EOScreate, 5-63edit, 5-69subtab, 5-69

Ethernetconfiguration, 5-50

events, see Event tabLAG

create, 5-71subtab, 5-71

STM port config, 5-41


Index

Taggingcustomer-tagged, 5-61port-based, 5-61service-tagged, 5-61

TE-206access roles, 2-18auto-discovery, 2-18links

Traverse, 2-18PM report, 2-38provisioning

see TraverseEdge 206 Users Guide, 2-19TransNav

discovery on, 2-17initial setup, 2-17prerequisites, 2-17rediscovery, 2-18

user accounts, 2-18TE-50

add, 5-79alarm profile, 5-83contact, 5-82delete, 5-81IP address, 5-80location, 5-82management port, 5-82menu

options, 5-81node

ID, 5-82IP address, 5-82

number of retries, 5-80, 5-83port number, 5-80read community, 5-80, 5-82sub shelf ID, 5-82sub shelf IP address, 5-82sub shelf type, 5-82timeout, 5-80, 5-83trap port, 5-80trap receive port, 5-83write community, 5-80, 5-83

Templatesdescription, 8-3

Terminate DCCSONET port, 5-26STM port, 5-44

Test accessADM, 8-47DCS3/1, 8-47digital signals, 8-47intrusive, 8-47non-intrusive, 8-47

Test signal typeDS3/EC1 port, 8-42

Time logged insession list, 2-12

Time zonesetting, 3-8

Timeoutdomain user, 2-8see TE-50see TransAccess 200 Mux

Timingclock mode, 3-23configuration

BITS and derived DS1, 3-24description, 3-21global, 3-22line timing, 3-27

line coding, 3-24mode, 3-22Quality of RES, 3-22revertive, 3-23tab

description, 3-22shelf view, 1-32, 1-50

TMX port, 6-27, 6-41, 7-15, 7-35TN-Sight

use with TransNav, 2-17Topology

end-to-end, 6-11update, 4-9, 4-15

TransAccess 200 Muxadd, 5-73alarm profile, 5-77, 8-25contact name, 5-77delete, 5-75Ethernet IP subnet, 5-74IP address, 5-74, 5-77location, 5-77management port, 5-77node

ID, 5-77number of retries, 5-74, 5-77port number, 3-10, 5-74read community, 3-10, 5-74, 5-77shelf name, 5-74sub shelf ID, 5-77sub shelf type, 5-77timeout, 5-74, 5-77trap port, 5-74trap receive port, 5-77write community, 3-10, 5-74, 5-77

Transmission path trace informationviewing, 6-89


Index

Transmitterauto shutdown

Ethernet port, 5-54, 5-55SONET port, 5-24, 5-25STM port, 5-42

stateEthernet port, 5-54SONET port, 5-24STM port, 5-42

TransmuxMSAID assignment details

DCS, 7-24TransNav

rediscoveryTE-206, 2-18

TE-206auto-discovery, 2-18discovery, 2-17discovery prerequisites, 2-17nodes, 2-17

use with TN-Sight, 2-17Transparency, 6-28, 6-41, 7-16, 7-35Trap

TE-50port, 5-80receive port, 5-83

TransAccess 200 Muxport, 5-74receive port, 5-77

UUMX

line formatsubport, 5-17

Unidirectionalconnections, 6-28, 6-41, 7-16, 7-35

Updatetopology, 4-9, 4-15

UPSR ringconfiguration

east port, 4-12name, 4-12node, 4-12ring ID, 4-12west port, 4-12

delete, 4-14edit, 4-14synchronize, 4-14

Userdefinition

domain, 2-3, 2-13node, 2-3, 2-13

login name, 1-19

name, 1-21, 1-24, 1-25domain, 2-8, 2-15node user, 2-15session list, 2-12

password, 2-8, 2-15preferences

save and import, 2-22UTMX

line formatsubport, 5-18

subportalarm profile, 5-18loopback, 5-18PM template, 5-18

VValid signal time

DS1 port, 5-11E1 port, 5-37

Valid signal timerEC1 port, 5-20

VC3 paths, 6-35VC4 paths, 6-35VCAT, see Virtual concatenationVCB, see VC-bundleVC-bundle

createservice, 6-58

serviceadvanced parameters, 6-59configure, 6-59

Viewingalarms, 8-16PM data

port, 8-7Virtual

concatenationfeature description, 6-57

RSTPbridge, 5-66

VT MUXservice

endpoint requirements, 9-8SDH endpoints, 9-12

VT pathadministrative state, 6-89PM report, 2-38

WWest port

BLSR ring, 4-4MS-SP ring, 4-4


Index

SNCP ring, 4-12UPSR ring, 4-12

WFQCoS n Weight, 5-62

Working1+1 path protection

path, 4-30port, 4-30

Write communityTE-50, 5-80, 5-83TransAccess 200 Mux, 3-10, 5-74, 5-77

WTR1+1 APS, 4-241+1 MSP, 4-241+1 optimized protection, 4-36BLSR ring, 4-4Carrier Ethernet Protection Pair, 4-33equipment protection, 4-18MS-SP ring, 4-4time, 6-24, 6-37

Carrier Ethernet Protection Pair, 4-33


Index


transnav gui guide - force10€¦ · 17/3/2010 · configure web browser settings for internet...

Documents